You are not logged in.

#1 2012-10-15 21:28:03

skunk_junior
Member
Registered: 2010-04-25
Posts: 20

unable to boot after kernel 3.5.6-1 -> 3.6.2-1. Kernel regression?

I did a pacman -Syu (log here: http://pastebin.com/raw.php?i=Gn9jdJtK) during which the linux kernel was updated.  When trying to reboot, the boot process stopped with something that looked suspiciously like a kernel panic (where can I find/get logs?), then it said that it was waiting 10 seconds for device UUID=... (my arch linux root) and then dropped to a rescue shell.

I found, though, that the UUID in /boot/grub/grub.cfg (given as kernel parameter) is the right one (booting into another os on another partition and doing ls /dev/disk/by-uuid showed the right UUID) and it should not be damaged etc, as I can read data and also the grub config file resides on this partition.

I suppose this has something to do with the new kernel, but I'm no expert at all and grateful for any help...

Edit:  The Error looks like this one
http://comments.gmane.org/gmane.linux.ide/53065
Unfortunately I cannot disable the IDE controller in Bios, as suggested in the link (I have a HP compaq nx6325 with ATA disk).

Last edited by skunk_junior (2012-10-17 21:12:53)


It's not a bug -- it's a feature!

Offline

#2 2012-10-15 21:36:41

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,468

Re: unable to boot after kernel 3.5.6-1 -> 3.6.2-1. Kernel regression?

Sounds like the interface isn't in the initramfs. Make sure all the necessary hooks are in mkinitcpio.conf.

Online

#3 2012-10-17 20:18:43

skunk_junior
Member
Registered: 2010-04-25
Posts: 20

Re: unable to boot after kernel 3.5.6-1 -> 3.6.2-1. Kernel regression?

Scimmia wrote:

Sounds like the interface isn't in the initramfs. Make sure all the necessary hooks are in mkinitcpio.conf.

I did not touch the file mkinitcpio.conf.  The very same configuration was ok for the previous kernel(s).  Checking /var/log/pacman.log, I see that the hooks parsed then were the same as last time.  In fact the logs look identical but for the version number of the kernel.  And I did not change my system (same laptop, same hard disk, no change in the partition table, ...), so the hooks should be fine (and the log does not report errors building the kernel...);

HOOKS="base udev autodetect pata scsi sata filesystems usbinput fsck"

It's not a bug -- it's a feature!

Offline

#4 2012-10-17 21:53:44

skunk_junior
Member
Registered: 2010-04-25
Posts: 20

Re: unable to boot after kernel 3.5.6-1 -> 3.6.2-1. Kernel regression?

Ok, downgrading the kernel to 3.5.6-1 ``solved'' the problem.

See this post
http://sch1zo.github.com/blog/2012/05/0 … s-and-lvm/
for how to downgrade with a more exotic setup.


It's not a bug -- it's a feature!

Offline

#5 2012-10-25 13:24:20

vaxr
Member
Registered: 2012-10-25
Posts: 2

Re: unable to boot after kernel 3.5.6-1 -> 3.6.2-1. Kernel regression?

Thanks. I had the same problem, and downgrading to 3.5.6-1 fixed it.

Some of my SATA devices were apparently recognized by udev, while others (among those the root drive) weren't.

Offline

#6 2012-10-26 13:42:32

Painless
Member
Registered: 2006-02-06
Posts: 233

Re: unable to boot after kernel 3.5.6-1 -> 3.6.2-1. Kernel regression?

Offline

#7 2012-10-27 11:06:32

vaxr
Member
Registered: 2012-10-25
Posts: 2

Re: unable to boot after kernel 3.5.6-1 -> 3.6.2-1. Kernel regression?

Thanks. Removing PATA doesn't work for me -- in fact, it stops the setup with the old kernel from working as well.

However, the new kernel 3.6.3 seems to work just fine like 3.5.6 did, with PATA. So it seems an upgrade solved it.

Offline

#8 2012-10-29 13:29:30

Painless
Member
Registered: 2006-02-06
Posts: 233

Re: unable to boot after kernel 3.5.6-1 -> 3.6.2-1. Kernel regression?

Alas, even with the latest kernel, my old Dell Lattitude c640 still requires the 'modprobe.blacklist=pata_acpi' kernel parameter in order to boot.  I haven't tried removing PATA altogether as that seems a little drastic.

Offline

#9 2012-11-02 15:03:05

lesto
Member
Registered: 2010-07-13
Posts: 115

Re: unable to boot after kernel 3.5.6-1 -> 3.6.2-1. Kernel regression?

Offline

#10 2012-11-02 18:16:06

skunk_junior
Member
Registered: 2010-04-25
Posts: 20

Re: unable to boot after kernel 3.5.6-1 -> 3.6.2-1. Kernel regression?

I don't think so:
- It's another kernel version
- the problem is CPU and not disk related

The only similarities I can see are, that it's a kernel bug and that an update solved it...


It's not a bug -- it's a feature!

Offline

Board footer

Powered by FluxBB