FS#32703 - [linux] 3.6.6 panic on reboot (Dell Latitude E6520)

Attached to Project: Arch Linux
Opened by Amitav (amitavmohanty01) - Friday, 16 November 2012, 10:12 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Monday, 21 January 2013, 15:11 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
Every third boot on my Dell Latitude E6520 ends up a kernel panic. However, when I restart the system, it works fine. Sometimes, there are a couple of subsequent reboot that cause kernel panics and the next works fine. I am attaching a screenshot of the kernel panic.

Additional info:
* package version(s)
uname -a
Linux ARCH 3.6.6-1-ARCH #1 SMP PREEMPT Mon Nov 5 11:57:22 CET 2012 x86_64 GNU/Linux

nvidia-304.64-1

* config and/or log files etc.
During boot, I get the following messages:

Nov 16 11:07:32 ARCH kernel: pnp 00:0b: [irq 23]
Nov 16 11:07:32 ARCH kernel: pnp 00:0b: Plug and Play ACPI device, IDs SMO8800 (active)
Nov 16 11:07:32 ARCH kernel: ACPI Error: Invalid/unsupported resource descriptor: Type 0x00 (20120711/utresrc-650)
Nov 16 11:07:32 ARCH kernel: pnp 00:0c: can't evaluate _CRS: 12311
Nov 16 11:07:32 ARCH kernel: system 00:0c: Plug and Play ACPI device, IDs PNP0c01 (active)
Nov 16 11:07:32 ARCH kernel: pnp: PnP ACPI: found 13 devices
Nov 16 11:07:32 ARCH kernel: ACPI: ACPI bus type pnp unregistered
Nov 16 11:07:32 ARCH kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
   kpanic.jpg (793 KiB)
This task depends upon

Closed by  Gerardo Exequiel Pozzi (djgera)
Monday, 21 January 2013, 15:11 GMT
Reason for closing:  Fixed
Additional comments about closing:  seems to be fixed in kernel 3.6.11
Comment by Amitav (amitavmohanty01) - Friday, 16 November 2012, 10:18 GMT
Not sure if it is relevant but https://lkml.org/lkml/2012/2/1/193 and https://lkml.org/lkml/2012/1/19/463 might be useful.
Comment by Lauri Niskanen (Ape) - Thursday, 13 December 2012, 14:12 GMT
Please try acpi=off as kernel parameter.
Comment by Amitav (amitavmohanty01) - Friday, 14 December 2012, 13:32 GMT
I tried with acpi=off but shutdown did not work. So I do not think it is the solution.
Comment by Mark E. Lee (bluerider) - Thursday, 17 January 2013, 19:07 GMT
Can you post your kernel options?
Comment by Amitav (amitavmohanty01) - Friday, 18 January 2013, 06:01 GMT
kernel /boot/vmlinuz-linux root=/dev/sda7 resume=/dev/sda6 ro reboot=pci init=/usr/lib/systemd/systemd
Comment by Mark E. Lee (bluerider) - Saturday, 19 January 2013, 06:41 GMT
Try passing this parameter as well : "pci=noacpi" to your kernel boot lines.
See <https://bbs.archlinux.org/viewtopic.php?pid=1120762#p1120762> for more information
Comment by Mark E. Lee (bluerider) - Saturday, 19 January 2013, 06:44 GMT
Your particular error seems related to a device designed by ST Microelectronics. It is a device for detecting free falls of your notebook, possibly to protect spinning hard disks.

See this site for more information :
<http://beecherbowers.com/2010/05/26/dell-latitude-e6510-unknown-device-acpi-smo8800/>
Comment by Amitav (amitavmohanty01) - Sunday, 20 January 2013, 08:22 GMT
I am now using 3.6.11 kernel and the issue has not appeared recently. I tried with pci=noacpi and the system works fine with it. So, I can't say for certain if the issue is solved.
Comment by Mark E. Lee (bluerider) - Sunday, 20 January 2013, 14:54 GMT
Did you try booting with the 3.6.11 kernel without "pci=noacpi"?
Comment by Amitav (amitavmohanty01) - Sunday, 20 January 2013, 18:41 GMT
Yes, even without the kernel parameters for pci, it works fine.

Is there a way I can be certain whether my system has that accelerometer or not?
Comment by Mark E. Lee (bluerider) - Sunday, 20 January 2013, 19:43 GMT
According to your previous kernel logs, the accelerometer was detected. Either kernel added support for the accelerometer, or they disabled it via a patch (since you didn't need pci=nacpi).

If you would like to check if the accelerometer can be used by the Arch Linux OS, you would need to find out where the device's events are being posted (usually somewhere in /dev/). Doing a simple bing search doesn't turn up any information relating to Linux and Dell's Fast Response free-fall sensor userspace tools for Linux. So even if the sensor is reporting events, there doesn't seem to be any software (to my knowledge) that supports it.
Comment by Mark E. Lee (bluerider) - Sunday, 20 January 2013, 19:45 GMT
If your computer is booting fine with a kernel update, you should request to close the bug as solved (solution was kernel update to 3.6.11).
Comment by Amitav (amitavmohanty01) - Monday, 21 January 2013, 06:27 GMT
pnp 00:0b: Plug and Play ACPI device, IDs SMO8800 (active)
ACPI Error: Invalid/unsupported resource descriptor: Type 0x00 (20120711/utresrc-650)
pnp 00:0c: can't evaluate _CRS: 12311
system 00:0c: Plug and Play ACPI device, IDs PNP0c01 (active)
pnp: PnP ACPI: found 13 devices
ACPI: ACPI bus type pnp unregistered
pci 0000:00:01.0: PCI bridge to [bus 01]

Yes, I can see the device now but the issue seems to be solved. I will request to close the bug.

Loading...