[hardy] 2.6.24-15 fails to boot with saa7134(?)

[lnx]

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"

After updating the latest packages today the system did not reboot the kernel: vmlinuz-2.6.24-15-generic

I had to boot the 2.6.24-14-generic.

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux which is the sourcepackage for the kernel for Hardy.

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include as attachments the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
4. What happens when you try to boot 2.6.24-15?
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

[lnx (nwegener)]

Linux nobbi 2.6.24-14-generic #1 SMP Thu Apr 3 04:49:29 UTC 2008 i686 GNU/Linux

[lnx (nwegener)]

When trying to boot 2.6.24-15 the status bar stops at one point. After a timeout period the ubuntu screen disappears and the booting messages can be seen:

..
Starting kernel event manager [OK]
Loading hardware drivers [Fail]

That's it.

[renbag (renbag)]

I have a similar behaviour on my system.
Booting with kernel 2.6.24-15-generic hangs my machine at 'Loading hardware drivers...', then, after 3-4 min, the boot process continues, but after logging into gnome the following message appears: 'Failed to initialize HAL!' and there is no network and no sound.
This does not happen with kernel 2.6.24-14-generic.
I have attached the required informations.

[renbag (renbag)]

Since we both bug reporters have a SAA7130/SAA7133 Video Broadcast Decoder and from the relative log files, I guess that the problem is related to this card.

[renbag (renbag)]

... in fact, after removing that card, the 2.6.24-15-generic kernel boots normally.

[Brian Murray (brian-murray)]

It would be helpful if you were to boot without the 'quiet' and 'usplash' options, and submit a picture of the crash, so we can get a better error message out of your system. You can learn more about how to edit grub menu items at https://wiki.ubuntu.com/GrubHowto . Thanks in advance!

[Sylvain Pasche (sylvain-pasche)]

bug 213315 which has been marked as a duplicate of this one contains more detailed information. The kernel log with the oops: http://launchpadlibrarian.net/13163081/dmesg.log (and my lspci: http://launchpadlibrarian.net/13163095/lspci.log). My boot process was stuck the first time I restarted after the kernel upgrade, but then I manged to get the boot process to complete and grab the dmesg log. I'm not sure how I managed to get past the boot freeze (I tried to add a "debug" option on the grub command line, I'm not sure if this does anything).

But it would still be useful if other people experiencing problems confirm that they see the same kernel error.

[renbag (renbag)]

I booted my machine with kernel 2.6.24-15.27-generic, after removing the quiet and splash option.
This time the boot process did not stop, but I was presented with the screen showing the failsafe mode for X. The video card, the sound card and the network card were not recognized.
This behaviour is slightly different from what happened with 2.6.24-15.26-generic (described in comment 6), but the dmesg.log show the same errors about the saa7134 module. They were already reported in the attachment of comment 6, as the boot process restarted after 3-4 min of pause, and are similar to those reported by Sylvain.
Booting again with kernel 2.6.24-14.25-generic shows no problems.
These are the required information with the new kernel version:

Linux pcbrahms3 2.6.24-15-generic #1 SMP Mon Apr 7 16:37:53 UTC 2008 x86_64 GNU/Linux
Ubuntu 2.6.24-15.27-generic
lspci-vvnn.log, already reported in comment 6
dmesg.log, attached

[renbag (renbag)]

The bug is still present in kernel 2.6.24-16.30-generic.

[Marc climent (mcliment)]

Same problem here. It happens in 2.6.24-15 and -16. -14 boots fine. I don't understand exactly why it's going to expire.

This is: Linux cactus2 2.6.24-16-generic #1 SMP Thu Apr 10 12:47:45 UTC 2008 x86_64 GNU/Linux

I attach my dmesg, but it's similar to the one posted before.

As a temporary solution I've added:
blacklist saa7134
to /etc/modprobe.d/blacklist

[thom (tsk)]

Can I interest you in this message I found ?
It worked for me :-)
---------------------------------------------------------------
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/212960

dr_agon wrote : Solved? 2.6.24-15-generic: saa7134-alsa makes HAL to fail (permalink)

After reading the bug #212960 I just tried to install updated linux-ubuntu-modules-2.6.24-16-generic v.23ubuntu2 supplied by Stefan Bader in his repository (https://launchpad.net/~stefan-bader-canonical/+archive) and the problem is gone! I mean that I removed saa7134 from blacklist and everything loads fine, have no HAL error.
Thanks!
----------------------------------------------------------------