X not available after 2.6.32-22 kernel update

[Brian McCullough]

(Affects Ubuntu 10.04 LTS)

After an advised system update that included a new kernel build (2.6.32-22 generic), X only initializes correctly in 25% - 33% of cases. The rest of the time, the system either hangs on boot or (more often) offers a command-line-only login.

Editing the GRUB menu to default to kernel 2.6.32-21 generic resolves the issue reliably (so far).

I was not able to run ubuntu-bug as described due to browser unavailability, and the Apport report file I saved was apparently deleted on reboot under the older kernel. uname-a.log, version.log, dmesg.log, and lspci-vnvn.log (all captured under 2.6.32-22 command-line session) are attached.

[Sven Kalinowski (info-svenkalinowski)]

I recognize, you are using the nvidia-driver. Could this be a duplicate of Bug #575997 ?

[Jeremy Foshee (jeremyfoshee)]

[This is an automated message. Apologies if it has reached you inappropriately.]

This bug was reported against the linux-meta package when it likely should have been reported against the linux package instead. We are automatically transitioning this to the linux kernel package so that the appropriate teams are notified and made aware of this issue.

If this bug really is a bug in the linux-meta package you can move it back to linux-meta and tag it kj-linux-meta, or contact us on the #ubuntu-kernel channel on the FreeNode IRC server. Thanks.

[Brian McCullough (eclipse-ix)]

Hi, Sven:

It's difficult for me to tell. I installed the update through the Update
Manager as part of the normal recommended update process. Usually, when
Update Manager recommends a kernel update, the appropriate linux-headers
package is installed along with the kernel itself, so I wasn't sure
whether this was the same bug or not.

Thank you for your help!

-- Brian McCullough

On 05/08/2010 03:05 PM, Sven Kalinowski wrote:
> I recognize, you are using the nvidia-driver. Could this be a duplicate
> of Bug #575997 ?
>
>

[Brian McCullough (eclipse-ix)]

Hi again:

I finally remembered to double-check in Synaptic. It appears that the
headers for 2.6.32.22 are correctly installed.

-- Brian M.

On 05/08/2010 11:25 PM, Brian McCullough wrote:
> Hi, Sven:
>
> It's difficult for me to tell. I installed the update through the Update
> Manager as part of the normal recommended update process. Usually, when
> Update Manager recommends a kernel update, the appropriate linux-headers
> package is installed along with the kernel itself, so I wasn't sure
> whether this was the same bug or not.
>
> Thank you for your help!
>
> -- Brian McCullough
>
> On 05/08/2010 03:05 PM, Sven Kalinowski wrote:
>
>> I recognize, you are using the nvidia-driver. Could this be a duplicate
>> of Bug #575997 ?
>>
>>
>>
>

[Stenten (stenten)]

2.6.32-22 Changelog:
linux (2.6.32-22.33) lucid-proposed; urgency=low

  [ Andy Whitcroft ]

  * SAUCE: ACPI: EC: Allow multibyte access to EC (v3)
    - LP: #526354

  [ Tim Gardner ]

  * ubuntu: rtl8192se -- update to version 0015.0127.2010
    - LP: #567016
 -- Andy Whitcroft <email address hidden> Mon, 19 Apr 2010 11:06:35 +0100

[Stenten (stenten)]

You can add Apport information to this bug by booting into the -22 kernel and typing "apport-collect 577559" in a Terminal (which is good, because that's all you can boot into! :) )

[Stenten (stenten)]

Try booting the -22 kernel with "noacpi":
1) Hold down Shift while booting to get to grub
2) With the -22 kernel highlighted, hit 'e'.
3) Add "noacpi" after "quiet splash".
4) Ctrl+x to boot.

You're not going to like it, but for this bug to have a good chance of being fixed, you need to reliably figure out what causes -22 to boot normally, to a tty, and freeze. Is there anything different about these situations? What programs are running? etc.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]