10.04b with 2.6.32-21 locks hard on startx on Thinkpad X40

[Alan Hoyle]

Binary package hint: linux-image-2.6.32-21-generic

I have a Thinkpad X40 and have 10.4b2 installed on it. If I let it boot into the most recent kernel 2.6.32-21, the machine locks up hard when it tries to start Xorg. I get a black screen and nothing happens. Keyboard is unresponsive: ctrl-alt-f1 doesn't switch, and even the capslock lights don't respond.

This occurs whether I'm doing a normal boot or if I do a recovery-mode boot and manually type "startx" at a command prompt.

If I override the default boot kernel and force grub2 to boot into 2.6.32-20, everything works fine.

lsb_release-rd reports:
Ubuntu lucid (development branch) 10.04

I guess this could be an Xorg issue, but it does work fine with the older kernel. The only weird thing about my startup parameters is the inclusion of "hpet=force" in the linux command line.

[Alan Hoyle (alanh)]

What logs should I look into or include to try and have this resolved?

[Markus Alexander Kuppe (c-launchpad-net-lemmster-de)]

Since this pretty much renders my machine useless, I'd suggest to bump up the importance level.

[Markus Alexander Kuppe (c-launchpad-net-lemmster-de)]

Note, I did not mean to imply that only because it renders _my_ machine non-bootable should the importance be increased. Rather because of the severity of the bug. :-o

[Alan Hoyle (alanh)]

I don't seem to have sufficient privileges to escalate the importance. Also, I do have an effective work-around in going with the previous version of the kernel.

[Markus Alexander Kuppe (c-launchpad-net-lemmster-de)]

That implies that you still have the previous version of the kernel installed.

[Geir Ove Myhr (gomyhr)]

If I remember correctly, booting with the kernel parameter i915.modset=1 should restore the 2.6.32-20 behaviour, since the only difference is that it defaults to 0 in 2.6.32-21 (for i8xx chipsets).

[Alan Hoyle (alanh)]

I tried putting i915.modset=1 into the GRUB_CMDLINE_LINUX in my /etc/default/grub. If I do that, I get the same behavior in 2.6.32-20 as I had in 2.6.32-21 (i.e. locks hard, non-responsive). (and yes, I still have the older kernel installed.)

As an aside, when I rebooted into recovery mode and tried the "failsafe graphics" mode, it did successfully start and the 3d netbook launcher was plenty fast.

[Alan Hoyle (alanh)]

Is there a log file that isn't zeroed at boot that would be useful for me to send?

[Jeremy Foshee (jeremyfoshee)]

Hi Alan,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 567914

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

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

[Markus Alexander Kuppe (c-launchpad-net-lemmster-de)]

linux-image-2.6.34-020634rc5-generic_2.6.34-020634rc5_i386.deb boots fine here. X does _not_ lock hard with it.

[Markus Alexander Kuppe (c-launchpad-net-lemmster-de)]

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: markus 1374 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 17'
   Mixer name : 'Analog Devices AD1981B'
   Components : 'AC97a:41445374'
   Controls : 28
   Simple ctrls : 20
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 1UHTB2WW-1.62'
   Mixer name : 'ThinkPad EC 1UHTB2WW-1.62'
   Components : ''
   Controls : 2
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
   Playback channels: Mono
   Limits: Playback 0 - 14
   Mono: Playback 9 [64%] [off]
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=0e545c0b-cc3d-46fa-a7f2-eed06d7255c9
Lsusb:
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: IBM 23718NG
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-20-generic root=UUID=15ff3267-0f15-48c1-a793-d6a0823c7330 ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-20.30-generic 2.6.32.11+drm33.2
Regression: Yes
RelatedPackageVersions: linux-firmware 1.34
Reproducible: Yes
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: lucid kconfig regression-potential needs-upstream-testing
Uname: Linux 2.6.32-20-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/21/2006
dmi.bios.vendor: IBM
dmi.bios.version: 1UETD3WW (2.08 )
dmi.board.name: 23718NG
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnIBM:bvr1UETD3WW(2.08):bd12/21/2006:svnIBM:pn23718NG:pvrThinkPadX40:rvnIBM:rn23718NG:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 23718NG
dmi.product.version: ThinkPad X40
dmi.sys.vendor: IBM

[Markus Alexander Kuppe (c-launchpad-net-lemmster-de)]

apport information

[Markus Alexander Kuppe (c-launchpad-net-lemmster-de)]

apport information

[Markus Alexander Kuppe (c-launchpad-net-lemmster-de)]

apport information

[Markus Alexander Kuppe (c-launchpad-net-lemmster-de)]

apport information

[Markus Alexander Kuppe (c-launchpad-net-lemmster-de)]

apport information

[Markus Alexander Kuppe (c-launchpad-net-lemmster-de)]

apport information

[Markus Alexander Kuppe (c-launchpad-net-lemmster-de)]

apport information

[Markus Alexander Kuppe (c-launchpad-net-lemmster-de)]

apport information

[Markus Alexander Kuppe (c-launchpad-net-lemmster-de)]

apport information

[Markus Alexander Kuppe (c-launchpad-net-lemmster-de)]

apport information

[Markus Alexander Kuppe (c-launchpad-net-lemmster-de)]

apport information

[Markus Alexander Kuppe (c-launchpad-net-lemmster-de)]

apport information

[Markus Alexander Kuppe (c-launchpad-net-lemmster-de)]

apport information

[Markus Alexander Kuppe (c-launchpad-net-lemmster-de)]

apport information

[Markus Alexander Kuppe (c-launchpad-net-lemmster-de)]

apport information

[Markus Alexander Kuppe (c-launchpad-net-lemmster-de)]

apport information

[Markus Alexander Kuppe (c-launchpad-net-lemmster-de)]

apport information

[Markus Alexander Kuppe (c-launchpad-net-lemmster-de)]

linux-image-2.6.32-0206321203-generic from kernel mainline also works fine here.

[Keiron Walsh (keiron-alevelpsychology)]

This bug is also present in the new Ubuntu 10.04 cd, which just hangs with a blank screen for me.

It is probably under-reported because a lot of less technical people will just have a computer that doesn't work, so they can't report it.

[Alan Hoyle (alanh)]

Keiron,

Are you getting this with an installed 10.04 or are you just booting
in live-cd mode? I'm just wondering if it's possible to test without
having to reinstall my whole system (I'm on an older SSD and want to
minimize full reinstalls unless absolutely necessary).

-alan
--
  - Alan Hoyle - <email address hidden> - http://www.alanhoyle.com/ -

On Sat, May 1, 2010 at 6:31 AM, Keiron Walsh
<email address hidden> wrote:
> This bug is also present in the new Ubuntu 10.04 cd, which just hangs
> with a blank screen for me.
>
> It is probably under-reported because a lot of less technical people
> will just have a computer that doesn't work, so they can't report it.
>
> --
> 10.04b with 2.6.32-21 locks hard on startx
> https://bugs.launchpad.net/bugs/567914
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Tim Keen (tim-keen)]

I can confirm this is a problem on other X40's. I've been successfully running 9.10 on my X40. When 10.4 was released a few days ago, I upgraded using the standard distribution upgrade procedure. Upon reboot, the laptop was bricked. It displays the Ubuntu logo (with dots) for a second or two, then black screen. No keyboard response. Have to power it down. I tried burning a 10.4 Desktop CD, to see if I could try a recovery procedure, but I get the same issue. I cannot run the CD in install nor in live cd mode, as it hangs with a black screen a few seconds later. Clearly this seems like a kernel issue. I haven't been able to get into it far enough to access any logs. I'll be trying a 9.10 CD today.

At a minimum, X40 users should *NOT* install or upgrade to 10.4 unless they want to brick their laptop. Not until a kernel fix/work-around is found.

[Keiron Walsh (keiron-alevelpsychology)]

I am getting this on both upgrade to 10.04 and on live cd. On the
upgrade I can fall back to the old kernel and it works fine. It's just
annoying that I have to select a different option in GRUB.

I have tried a "nomodeset" option to try to boot the live cd, but
still get the same problem. This was suggested on an Ubuntu forum.

Hope that helps

Keiron

---------------------------------
http://alevelpsychology.co.uk

On 3 May 2010, at 16:05, Alan Hoyle <email address hidden> wrote:

> Keiron,
>
> Are you getting this with an installed 10.04 or are you just booting
> in live-cd mode? I'm just wondering if it's possible to test without
> having to reinstall my whole system (I'm on an older SSD and want to
> minimize full reinstalls unless absolutely necessary).
>
>
> -alan
> --
> - Alan Hoyle - <email address hidden> - http://www.alanhoyle.com/ -
>
>
> On Sat, May 1, 2010 at 6:31 AM, Keiron Walsh
> <email address hidden> wrote:
>> This bug is also present in the new Ubuntu 10.04 cd, which just hangs
>> with a blank screen for me.
>>
>> It is probably under-reported because a lot of less technical people
>> will just have a computer that doesn't work, so they can't report it.
>>
>> --
>> 10.04b with 2.6.32-21 locks hard on startx
>> https://bugs.launchpad.net/bugs/567914
>> You received this bug notification because you are a direct
>> subscriber
>> of the bug.
>>
>
> --
> 10.04b with 2.6.32-21 locks hard on startx
> https://bugs.launchpad.net/bugs/567914
> You received this bug notification because you are a direct subscriber
> of the bug.

[Alan Hoyle (alanh)]

I also get the "Ubuntu logo (with dots)" during the boot. To me, it looks like the Ubuntu Logo is lower resolution than the normal XGA.

[Keiron Walsh (keiron-alevelpsychology)]

Yes, I get exactly the same - pixelated logo, then a pattern of dots
before the screen blanks.

---------------------------------
http://alevelpsychology.co.uk

On 4 May 2010, at 19:48, Alan Hoyle <email address hidden> wrote:

> I also get the "Ubuntu logo (with dots)" during the boot. To me, it
> looks like the Ubuntu Logo is lower resolution than the normal XGA.
>
> --
> 10.04b with 2.6.32-21 locks hard on startx
> https://bugs.launchpad.net/bugs/567914
> You received this bug notification because you are a direct subscriber
> of the bug.

[Markus Alexander Kuppe (c-launchpad-net-lemmster-de)]

FWIW: Same behavior with 2.6.32-22.

[Alan Hoyle (alanh)]

By the way, it appears that the "3d" netbook launcher I mention above
is actually the 2d one. (I have another bug in about the launcher
running slowly under certain circumstances: [Bug 570144])

[Alan Hoyle (alanh)]

I changed the status to "confirmed" as there appear to be two other folks who have the exact same issue and have uploaded the requested information. I do not know if that was really my place to do this or if that is something that a developer should do.

[Tim Keen (tim-keen)]

I've been able to access the hidden menu in grub2 and successfully boot the previous kernel, 2.6.31-21, without issue. I am currently using that kernel now and have configured grub2 to always boot that. Kernel 2.6.32-21 (also apparently the one used on the 10.4 cd), however, locks up on the splash screen. The following isn't a permanent fix, obviously, but may help those with bricked x40's like mine: (1) Press ESC during boot to get the hidden boot menu in grub2 (grub2 boots directly into the current selection without a menu by default) (2) select 2.6.31-21, assuming it's available (it was for me, but I upgraded from 9.10), (3) assuming you can get in, sudo vi /etc/default/grub and add/change the following:
GRUB_DEFAULT=saved
GRUB_SAVEDEFAULT=true

Then, sudo update-grub.

That should cause grub2 to save the last selected menu option as the default so that, basically, you boot into the last known good (successful) kernel. Not a solution for this bug, just a work-around for now.

[Scrl (scrl)]

Hi, I have an Acer TravelMate 242 and I have just upgraded to Lucid using the automatic upgrade wizard. I think that I have encountered exactly the same issue as described here. When I try to boot kernel 2.6.32-22 I end up with a blank screen and bricked computer - even Ctrl+Alt+F1 does nothing. It seems that CPU is doing something, as fans start to rev up soon, but I have left the computer for some time and it did not help. I was able to boot successfully using old 2.6.31-21 kernel.

[Keiron Walsh (keiron-alevelpsychology)]

2.6.31-21 didn't work for me

On 8 May 2010 21:10, Scrl <email address hidden> wrote:

> Hi, I have an Acer TravelMate 242 and I have just upgraded to Lucid
> using the automatic upgrade wizard. I think that I have encountered
> exactly the same issue as described here. When I try to boot kernel
> 2.6.32-22 I end up with a blank screen and bricked computer - even
> Ctrl+Alt+F1 does nothing. It seems that CPU is doing something, as fans
> start to rev up soon, but I have left the computer for some time and it
> did not help. I was able to boot successfully using old 2.6.31-21
> kernel.
>
> --
> 10.04b with 2.6.32-21 locks hard on startx on Thinkpad X40
> https://bugs.launchpad.net/bugs/567914
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Alan Hoyle (alanh)]

I also tried 2.6.32-22 and that shows the same issue as 2.6.32-21.
 2.6.32-20-generic continues to work for me.

I was unable to get the GRUB_DEFAULT=saved // GRUB_SAVEDEFAULT=true to work
for me though. I did the update-grub and I've tried rebooting several
times. Is there a way to check what grub thinks it should boot next is?
where is the GRUB_DEFAULT saved?

-a

[penalvch (penalvch)]

Alan Hoyle, thank you for reporting this and helping make Ubuntu better. 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 report the results following https://wiki.ubuntu.com/DebuggingKernelBoot ? As well, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

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

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

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[Alan Hoyle (alanh)]

At some point between 2010 and today (probably in the 10.10 timeframe, but I'm not 100% sure), the kernels started working for me. I'm running the most recent version of 11.10 with no problems.

I, personally, am unsubscribing from this bug and there is no reason to keep it open on my account.

[penalvch (penalvch)]

Alan Hoyle, this bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.