I can confirm, as others have mentioned, that this bug affects AMD
systems as well. All of my symptoms were identical to others reported.
I chose to downgrade yaird to testing and this resolved the problem (now
running 2.6.14-5). I appears to me that the patch mentioned above
doesn't apply
Erik van Konijnenburg wrote:
To help pin down the cause, could you post the output of:
uname -a
dpkg -l yaird
yaird -v -o crap.img 2.6.14-2-686
yaird -v -o crap.img 2.6.14-5-686
(assuming these are the last kernel that boots and the first that works)
To avoid
Package: linux-image-2.6.14-2-686
Version: 2.6.14-5
Severity: critical
Justification: breaks the whole system
Right after I upgraded linux-image-2.6.14-2-686 to 2.6.14-5 and rebooted, boot
is interrupted with repeated messages:
/bin/cat: /sys/block/hda/hda1/dev: No such file or directory
until
Paulo Marcel Coelho Aragao wrote:
Package: linux-image-2.6.14-2-686
Version: 2.6.14-5
Severity: critical
Justification: breaks the whole system
Right after I upgraded linux-image-2.6.14-2-686 to 2.6.14-5 and rebooted, boot
is interrupted with repeated messages:
/bin/cat:
On Mon, Dec 12, 2005 at 12:34:11AM -0200, Paulo Marcel Coelho Aragao wrote:
Package: linux-image-2.6.14-2-686
Version: 2.6.14-5
Severity: critical
Justification: breaks the whole system
Right after I upgraded linux-image-2.6.14-2-686 to 2.6.14-5 and rebooted,
boot
is interrupted with
On Mon, Dec 12, 2005 at 04:33:29AM +0100, Cesare Leonardi wrote:
Paulo Marcel Coelho Aragao wrote:
Package: linux-image-2.6.14-2-686
Version: 2.6.14-5
Severity: critical
Justification: breaks the whole system
Right after I upgraded linux-image-2.6.14-2-686 to 2.6.14-5 and rebooted,
6 matches
Mail list logo