[Dell Latitude 5520] System locks up when trying to reboot

[Jeff Lane ]

12.04 LTS installed on a Latitude 5520. The system locks up every time it tries to reboot. This only occurs on reboot, when shutting down, it seems to be OK. Odd behaviour and this is the only machine I've tested thus far that shows this behaviour.

I've tried rebooting via the menu option (clicking "Restart" on the Shutdown popup) and using the reboot command via cli. I tried multiple times via each method and every time I tried rebooting, the system would lock up during the shutdown part of the reboot. I also tried a full shutdown several times, using the menu option and using the shutdown command via cli, and those ALWAYS worked.

When this occurs, there appears to be nothing useful written to syslog, unfortunately. Here's a snipped from syslog on the last attempt:

STARTING REBOOT NOW
May 2 18:28:24 201011-6894 kernel: Kernel logging (proc) stopped.
May 2 18:28:24 201011-6894 rsyslogd: [origin software="rsyslogd" swVersion="5.8.6" x-pid="957" x-info="http://www.rsyslog.com"] exiting on signal 15.
May 2 18:33:38 201011-6894 kernel: imklog 5.8.6, log source = /proc/kmsg started.
May 2 18:33:38 201011-6894 rsyslogd: [origin software="rsyslogd" swVersion="5.8.6" x-pid="926" x-info="http://www.rsyslog.com"] start
May 2 18:33:38 201011-6894 rsyslogd: rsyslogd's groupid changed to 103
May 2 18:33:38 201011-6894 rsyslogd: rsyslogd's userid changed to 101
May 2 18:33:38 201011-6894 rsyslogd-2039: Could not open output pipe '/dev/xconsole' [try http://www.rsyslog.com/e/2039 ]
May 2 18:33:38 201011-6894 acpid: 35 rules loaded
May 2 18:33:38 201011-6894 acpid: waiting for events: event logging is off
May 2 18:33:38 201011-6894 kernel: [ 0.000000] Initializing cgroup subsys cpuset

The last line is right where I had power cycled the machine and restarted it.

The hang during reboot is permanent, I have to power-cycle to recover the system.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-23-generic 3.2.0-23.36
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu5
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 1571 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xe3d40000 irq 46'
   Mixer name : 'Intel CougarPoint HDMI'
   Components : 'HDA:111d76e7,1028049a,00100102 HDA:14f12c06,14f1000f,00100000 HDA:80862805,80860101,00100000'
   Controls : 37
   Simple ctrls : 13
Date: Wed May 2 18:34:25 2012
HibernationDevice: RESUME=UUID=868af3aa-4176-4851-b2c9-751e7a041708
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: Dell Inc. Latitude E5520
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=fed222cc-eae0-4ae1-b961-780ab553226e ro quiet splash initcall_debug vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-23-generic N/A
 linux-backports-modules-3.2.0-23-generic N/A
 linux-firmware 1.79
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/22/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A00
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA00:bd02/22/2011:svnDellInc.:pnLatitudeE5520:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5520
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

[Jeff Lane  (bladernr)]

also, for the record, this is system 201011-6894

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). 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.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc5-precise/

[Thibault Lemaitre (thibault.lemaitre)]

I'm affected too by this bug but I have a Latitude D830.
Moreover I have this problem for both restart and shutdown: really not convinient!
I was using Ubuntu 11.04 before the 12.04, on the same computer, and never had this kind of problem

[Thibault Lemaitre (thibault.lemaitre)]

More information about this bug: I did an update some days ago and my computer was able to shutdown after this one.

Unfortunately, after this only one successful shutdown I came back to the same situation: unable to shutdown my computer.

I'm gonna install another Ubuntu 12.04 on my pc to test safely the latest upstream kernel in few days.

[Anthony Wong (anthonywong)]

@Thibault, do you still have the issue with the latest 12.04 updates?

[Thibault Lemaitre (thibault.lemaitre)]

Yes I still have this problem. It doesn't occur each time I try to stop my laptop but almost. For example I updated my computer on the 1st august and could stop my computer after it, but couldn't stop my computer the 2nd august.

I will try the upstream kernel (as Joseph suggest) this week-end.

[Ming Lei (tom-leiming)]

On Sat, Aug 4, 2012 at 12:46 AM, Thibault Lemaitre
<email address hidden> wrote:
> Yes I still have this problem. It doesn't occur each time I try to stop
> my laptop but almost. For example I updated my computer on the 1st
> august and could stop my computer after it, but couldn't stop my
> computer the 2nd august.
>
> I will try the upstream kernel (as Joseph suggest) this week-end.

Also, could you run 'reboot' inside a VGA console via 'ctrl+alt+F1' and
post the log in monitor so that we can see what is wrong during shutdown?

Thanks,

[Jonathan Nieder (jrnieder)]

Reminiscent of the infamous Dell VT-d reboot bug: https://bugzilla.kernel.org/show_bug.cgi?id=42542

[Thibault Lemaitre (thibault.lemaitre)]

Good news : this bug seems to be solved in the upstream kernel. I tried the Mainline kernel v3.4-rc6-precise (06-May-2012 22:56) [1] as I didn't found the *image*.deb in the v3.4-rc7-precise folder.

I was able to reboot, and halt my computer without problems (via the menu on the top right corner). I tried to reboot from a VGA console (I discover the name) but it went back to the "Alt + F7" view before I was able to read something.

[1] : http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc6-precise/

[Thibault Lemaitre (thibault.lemaitre)]

I forgot something. I used the i386 image and headers as it's the architecture of my laptop

[Ming Lei (tom-leiming)]

On Tue, Aug 7, 2012 at 5:57 AM, Thibault Lemaitre
<email address hidden> wrote:
> Good news : this bug seems to be solved in the upstream kernel. I tried
> the Mainline kernel v3.4-rc6-precise (06-May-2012 22:56) [1] as I didn't
> found the *image*.deb in the v3.4-rc7-precise folder.
>
> I was able to reboot, and halt my computer without problems (via the
> menu on the top right corner). I tried to reboot from a VGA console (I
> discover the name) but it went back to the "Alt + F7" view before I was
> able to read something.

Please run below command to disable gdm first,

            sudo mv /etc/init/gdm.conf /etc/init/gdm.conf.disabled

then press 'ctrl+alt+F1' during ubuntu boot to enter console.
After login to console, please type below to enable kernel
message switch:

            sudo echo 9 > /proc/sys/kernel/printk

then run 'reboot' to get the kernel log.

After completing the process above, you can restore your gdm
configuration to enable gdm again.

Thanks,

[Thibault Lemaitre (thibault.lemaitre)]

I've just tried what you tell Ming and it seems I didn't do the things perfectly.

First I disabled lightdm, and not gdm: ok

After a reboot, once loged on my pc on the tty1, I try the command:
                        sudo echo 9 > /proc/sys/kernel/printk
Here is the problem, it answers me:
                       bash: /proc/sys/kernel/printk: Permission non accordée (not allowed)

I however tried a reboot and I attach the two syslog files I found in the folder /var/log/ to this message. Maybe useless, I don't know cause I don't understand everything I did.

[Ming Lei (tom-leiming)]

On Wed, Aug 8, 2012 at 12:24 AM, Thibault Lemaitre
<email address hidden> wrote:
> I've just tried what you tell Ming and it seems I didn't do the things
> perfectly.
>
> First I disabled lightdm, and not gdm: ok
>
> After a reboot, once loged on my pc on the tty1, I try the command:
> sudo echo 9 > /proc/sys/kernel/printk
> Here is the problem, it answers me:

If so, just run 'sudo su -' first, then run below:

        #echo 9 > /proc/sys/kernel/printk

Thanks,

[Thibault Lemaitre (thibault.lemaitre)]

The sudo su works better. Good idea.

So, I give you the new syslog files. For information, I did my reboot today at almost 20:30.

[Ming Lei (tom-leiming)]

On Wed, Aug 8, 2012 at 2:46 AM, Thibault Lemaitre
<email address hidden> wrote:
> The sudo su works better. Good idea.
>
> So, I give you the new syslog files. For information, I did my reboot
> today at almost 20:30.
>
> ** Attachment added: "syslog.tar.gz"
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/993610/+attachment/3251699/+files/syslog.tar.gz

The above log is not very useful, since the important log can't be written into
syslog if 'reboot' hangs.

So could you post the log in the screen when 'reboot' hangs?

Either captured photo or text you input is OK.

Thanks,

[Thibault Lemaitre (thibault.lemaitre)]

Ok, I will then try another time to reboot and take a picture or a a
video of my screen, but it goes really fast.

Thibault Lemaitre

Le 09/08/2012 04:31, Ming Lei a écrit :
> On Wed, Aug 8, 2012 at 2:46 AM, Thibault Lemaitre
> <email address hidden> wrote:
>> The sudo su works better. Good idea.
>>
>> So, I give you the new syslog files. For information, I did my reboot
>> today at almost 20:30.
>>
>> ** Attachment added: "syslog.tar.gz"
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/993610/+attachment/3251699/+files/syslog.tar.gz
> The above log is not very useful, since the important log can't be written into
> syslog if 'reboot' hangs.
>
> So could you post the log in the screen when 'reboot' hangs?
>
> Either captured photo or text you input is OK.
>
>
> Thanks,
>

[Thibault Lemaitre (thibault.lemaitre)]

I did two tests. One with the kernel installed with Ubuntu 12.04 (3.2.0-23-generic-pae) and the mainline kernel (3.4.0-030400rc6-generic-pae). I attach the important images of these tests. For information, I was able to reboot my computer with the both kernel. I don't know why when I log in with lightdm I can't reboot.

[Ming Lei (tom-leiming)]

@Thibault

I understand the log of 'Reboot test 20120811.tar.lzma' is captured when the system can reboot well,
so I am wondering how we can use the log in good case to troubleshoot the problem.

thanks

[Jeff Lane  (bladernr)]

Leaving this as incomplete for the moment, but we don't want this to disappear. I've added Jeff and Greg to the subscriber list, they should have access to this hardware in the Lexington Lab...

Guys, can you help Ming Lei with this bug?

[Thibault Lemaitre (thibault.lemaitre)]

I waited some days to post it, to be sure. This bug is fixed on my laptop since few days. So, I don't understand why status is changed to "Won't Fix"?

I'm able to shutdown it without problem.
I'll try to restart it many times during the next days and give you the result here.