[arch-general] Update to 184.108.40.206-1 & LTS 220.127.116.11-1 killed dmraid box??
rogutes at googlemail.com
Wed Aug 18 07:18:00 EDT 2010
David C. Rankin (2010-08-17 14:45):
> On 08/17/2010 01:44 PM, David C. Rankin wrote:
> >On 08/17/2010 01:27 PM, David C. Rankin wrote:
> >>I'll go see if I can rebuild with the ahci module loaded in the initramfs and
> >>see if that helps. But regardless, there is a bug somewhere. LTS boots fine in
> >>this config and 18.104.22.168 doesn't??
> >adding ahci to the MODULES line in mkinitcpio.conf and rebuilding the initramfs
> >made no difference. The box still freezes on boot at the very beginning of the
> >boot process with:
> >Booting 'Arch Linux on Archangel'
> >root (hd1,5)
> >Filesystem Type ext2fs, partition type 0x83
> >kernel /vmlinuz26 root=/dev/mapper/nvidia_baaccajap5 ro debug
> >[Linux-BzImage, setup=0x3200, size=0x1ff440]
> >showing on the screen. The box sits like that for 30-60 seconds and then
> >automagically reboots. Booting back into LTS works fine. I guess we need to open
> >a report on this one....
> Added as: http://bugs.archlinux.org/task/20499
It's strange that the kernel locks up so soon.
The bug report won't be useful until you test the newest kernel releases
(22.214.171.124 or 126.96.36.199). For the report to be interesting to Arch
developers, you should test against 188.8.131.52, because 2.6.34 has been
superseded by it.
If only a testing machine is affected, you could simply wait until 2.6.35
leaves testing/, update and see what happens.
-- Rogutės Sparnuotos
More information about the arch-general