Boot fails after kernel upgrade to 2.6.32-21generic on Ubuntu Lucid Beta2

[AM]

Boot fails completely after kernel upgrade to 2.6.32-21generic, giving no sign of intelligible activities. No log is recorded nor any console progress can be shown on boot, only an empty screen.

The system is a Sony Vaio laptop model VGN-B1XP that otherwise works very well and had a clean install of Ubuntu 10.04 Lucid Lynx Beta 2 alternate 386, that worked nice with kernel 2.6.32-19 from Beta 2. Earlier test of Beta 1 worked fine up to kernel 2.6.32-20, but also stopped working after upgrade to the kernel 2.6.32-21 generic.

Hopefully our kernel and distro heroes can solve this serious fault. It threats to undermine confidence of a LTS-release.
Sorry but I cannot provide other details since there are no logs of those boot attempts. I could not find a way to file this bug from the menu.

[AM (macchi)]

Hopefully our kernel and distro heroes can solve this serious fault. It threats to undermine confidence of a LTS-release.
Sorry but I cannot provide other details since there are no logs of those boot attempts. I could not find a way to file this bug from the menu.

[Philip Muškovac (yofel)]

Hi, can you try to hold left shift pressed after the bios screen on boot to get to the GRUB menu, select an older kernel to boot and see if that works? Thanks.

[Hamish Twaddle (hamish-twaddle)]

I have the same problem with a Acer TravelMate 2308. The new kernel 2.6.32-21generic fails but the older kernel but I can boot just fine with the 2.6.32-20generic kernel.

[AM (macchi)]

Hello Philip,

Yes the only immediate solution is to get to grub menu and boot the previous kernel (in my case the 2.6.32-19
My temporary workaround has been to remove the latest kernel, linux-image-2.6.32-21.

I get no logs from the boot and NO signs of life, that is blackscreen (backlight on), no console, no disk activity.
This is a serious problem and I hope it will be solved soon!

[ynsta (stanypub)]

Same problem with a Sony vaio VGN-B1XP and kernel 2.6.32-21.

The graphical boot is in lower resolution than with the previous kernel and there is strange colors on screen before it freeze.

The last init shown in the terminal is cups.

The Problem persists with kernel 2.6.32-22.

[J.L.P. López de Victoria (grupotux-gmail)]

Same problem on a Compaq Presario 2200 notebook. Both 2.6.32-21 and 2.6.32-22 fail to boot. Screen is dark, backlight on, no disk activity.

[Brian Norris (computersforpeace)]

I'm also on a Compaq Presario 2200 notebook. I've just upgraded to 10.04 and so I only have the option of the downloading the Ubuntu 2.6.32-21 or 2.6.32-22 kernel. I can bring the system up slowly--i.e. from GRUB, choose to start in single user mode then go to multiuser w/o GUI--with no problems until I force gdm to start. Then it freezes/black screen as above.

So from single user mode, also I viewed my logs, and it doesn't seem that anything for booting to GUI mode. It must crash very early in the boot process?

I can try and provide more info if necessary, as this is still labeled Incomplete.

[Brian Norris (computersforpeace)]

It seems like the following page describes the issue:

https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes

Does that mean there's no bug-fix, just a set of configuration changes or workarounds to try?

[Brian Norris (computersforpeace)]

I believe this problem is a direct result of the "fix" for this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/563277

[penalvch (penalvch)]

Antonio Macchi III, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11.1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]