Kernel oops following docking dell duo

[Danny Staple]

With a Dell Duo laptop when docking while turned on, I get a kernel oops.
This is Oneiric, upgraded from 11.04 NBR to Xubuntu desktop (I tried KDE desktop between).

Often (but not always) I get a kernel oops, related to ac notify.
Stack trace based on scanned screen - grepping for the trace in the var/log directory got me no joy after the reboot.

Note the odd intrusion of a mouse pointer - this there when it blows up.

Uname -a is:
"Linux danny-dell-duo 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:50:42 UTC 2011 i686 i686 i386 GNU/Linux"

lspci output for with and without dock to be attached.

Full model info on laptop:
Dell Inspiron Duo
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices: aplay: device_list:240: no soundcards found...
ApportVersion: 1.23-0ubuntu4
Architecture: i386
ArecordDevices: arecord: device_list:240: no soundcards found...
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 11.10
InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: Dell Inc. Inspiron 1090
Package: linux (not installed)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=828A11898A117ABD loop=/ubuntu/disks/root.disk ro quiet splash i8042.noloop=1 usbhid.quirks=0xeef:0x725e:0x40 vt.handoff=7
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
PulseSinks: Error: command ['pacmd', 'list-sinks'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
PulseSources: Error: command ['pacmd', 'list-sources'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-12-generic N/A
 linux-backports-modules-3.0.0-12-generic N/A
 linux-firmware 1.60
Tags: oneiric
Uname: Linux 3.0.0-12-generic i686
UpgradeStatus: Upgraded to oneiric on 2011-10-25 (63 days ago)
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video
dmi.bios.date: 01/07/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: Inspiron 1090
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A03
dmi.modalias: dmi:bvnDellInc.:bvrA03:bd01/07/2011:svnDellInc.:pnInspiron1090:pvrA03:rvnDellInc.:rnInspiron1090:rvrA03:cvnDellInc.:ct8:cvrA03:
dmi.product.name: Inspiron 1090
dmi.product.version: A03
dmi.sys.vendor: Dell Inc.

[Danny Staple (danny-orionrobots)]

Add first lspci (not docked):

[Danny Staple (danny-orionrobots)]

Hmm okay - lspci when docked/not docked is the same. Trying lsusb.

Diff is:

$ diff lsusb_*
10,11d9
< Bus 001 Device 010: ID 413c:a502 Dell Computer Corp.
< Bus 001 Device 012: ID 0572:1412 Conexant Systems (Rockwell), Inc.

Probably a red herring - given the stack trace indicates ac notification.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/908560/+editstatus and add the package name in the text box next to the word Package.

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

[Danny Staple (danny-orionrobots)]

Adding a likely package.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 908560

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Danny Staple (danny-orionrobots)]

apport information

[Danny Staple (danny-orionrobots)]

apport information

[Danny Staple (danny-orionrobots)]

apport information

[Danny Staple (danny-orionrobots)]

apport information

[Danny Staple (danny-orionrobots)]

apport information

[Danny Staple (danny-orionrobots)]

apport information

[Danny Staple (danny-orionrobots)]

apport information

[Danny Staple (danny-orionrobots)]

apport information

[Danny Staple (danny-orionrobots)]

apport information

[Danny Staple (danny-orionrobots)]

apport information

[Danny Staple (danny-orionrobots)]

apport information

[Danny Staple (danny-orionrobots)]

apport information

[Danny Staple (danny-orionrobots)]

apport information

[Danny Staple (danny-orionrobots)]

apport information

[Danny Staple (danny-orionrobots)]

apport information

[Danny Staple (danny-orionrobots)]

apport information

[Danny Staple (danny-orionrobots)]

apport information

[Danny Staple (danny-orionrobots)]

apport information

[Danny Staple (danny-orionrobots)]

apport information

[Danny Staple (danny-orionrobots)]

apport information

[teh603 (darth-giles)]

I'm having a similar problem with my Duo, except it also sometimes happens when I connect the AC adapter to the main power socket.

[Danny Staple (danny-orionrobots)]

@teh603 - I've had similar issues too, however, I'm not always able to get to the stack trace to prove it. It crashed a fair few times on me plugging that in. I've now taken the most recent updates, so I'll see if it happens then. It is not 100% reproducible though - it happens often enough to be annoying, roughly once every couple of days at the moment.

[teh603 (darth-giles)]

The way mine crashes, I'm just going to take a photo of the trace on the screen and see if that helps. At least next time I'm at home; my camera isn't with me because I'm at work. It looks like the Duo is having ACPI quirk issues the way the early Arrandale systems did- it seems to have wake from sleep to black screen issues and when it dumps to a text console it has a lot of ACPI and power management messages on it.

[Danny Staple (danny-orionrobots)]

If it helps - I popped mine screen out on the scanner for the screenshot. The flippy screen is handy for that.

[xavier raynaud (xraynaud)]

I have the same problem with my duo when i plug in/out the ac adaptor. A workaround is to shut down acpi at boot. However, without acpi, the duo cannot go into suspend/hibernate modes anymore.

[teh603 (darth-giles)]

Looks like your stack dump is identical to mine, so I shouldn't need to post it unless someone asks for it.

By the way, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/913848 is the one I filed on the black screen resume issue. The more attention we can get from Dell Duo users, the more heat we can get on these bugs and try to get them fixed.

[teh603 (darth-giles)]

Looks like this bug might be partially fixed in Precise, although the touchpad regression is downright frustrating.

[teh603 (darth-giles)]

Can anyone else confirm that this bug is partially fixed in Precise using the latest kernel build?

Although the ACPI now fails to properly track when the AC adapter is plugged in or not, but that's at least better than having to reboot.

[xavier raynaud (xraynaud)]

I can test it tonight but can you give more details of what you mean when you say "the touchpad regression is downright frustrating" and does hibernate /suspend works with the new kernel ?

[xavier raynaud (xraynaud)]

I tested kernel 3.2 from precise and it doesn't work for me.

[JJ Davis (jjdavis699-yahoo)]

I need help because this occurs with my duo everytime I plug/unplug my duo from the AC adapter. Can someone help me?

P.S. I'm new to this so I could use an explanation in simplest form

[teh603 (darth-giles)]

Ok, as someone posted in the UNR thread, here's the nitty gritty about what's going on here: https://bugzilla.kernel.org/show_bug.cgi?id=38782 . Now, for some reason the Kernel.org folks consider this bug "invalid," which seems like a bloody cop-out considering how quirky hardware doesn't stop Windows 7. There's a fix, and it doesn't seem too hard to implement, so why don't we create a PPA or something to implement it?

Only thing stopping me from implementing it myself is my absolute lack of programming skills. Trust me on this one; I'm about as hard on modern programming as Groo the Wanderer is on ships.

[penalvch (penalvch)]

Danny Staple, thank you for reporting this and helping make Ubuntu better. Upstream found this to be a BIOS bug. As per http://www.dell.com/support/drivers/us/en/19/DriverDetails/DriverFileFormats?DriverId=R302234 your BIOS is outdated. If you update your BIOS, is this oops reproducible?

[xavier raynaud (xraynaud)]

I have BIOS A06 and the problem is still there. I'm attaching the output from dmidecode.

[teh603 (darth-giles)]

I'm also running the latest BIOS, and the oops happens every time I plug it in while running. It also gives me a black screen of death if I try to resume from suspend or hibernate and have plugged or unplugged it.

Either way, "Flash your BIOS" isn't a solution. For every story I've heard of some problem getting fixed by a BIOS flash, I've heard ten of computers that got bricked because something stupidly trivial interrupted the flashing process. If it can be patched in software- and this can, because either MS or Dell has a working driver for Win7- then we need to patch it and stop telling people to brick their computers.

[penalvch (penalvch)]

xavier raynaud, please do not tack on your attachments to this bug.

xavier raynaud / teh603, you are welcome to file a new report via executing the following at the Terminal and feel free to subscribe me to it:
ubuntu-bug linux

Thanks!

[xavier raynaud (xraynaud)]

I have already filed a new bug #969865.

2012/4/12 Christopher M. Penalver <email address hidden>:
> xavier raynaud, please do not tack on your attachments to this bug.
>
> xavier raynaud / teh603, you are welcome to file a new report via executing the following at the Terminal and feel free to subscribe me to it:
> ubuntu-bug linux
>
> Thanks!
>
> ** Attachment removed: "dmidecode output"
>   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/908560/+attachment/2943190/+files/dmidecode_output
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/908560
>
> Title:
>  Kernel oops following docking dell duo
>
> Status in The Linux Kernel:
>  Invalid
> Status in “linux” package in Ubuntu:
>  Incomplete
>
> Bug description:
>  With a Dell Duo laptop when docking while turned on, I get a kernel oops.
>  This is Oneiric, upgraded from 11.04 NBR to Xubuntu desktop (I tried KDE desktop between).
>
>  Often (but not always) I get a kernel oops, related to ac notify.
>  Stack trace based on scanned screen - grepping for the trace in the var/log directory got me no joy after the reboot.
>
>  Note the odd intrusion of a mouse pointer - this there when it blows
>  up.
>
>  Uname -a is:
>  "Linux danny-dell-duo 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:50:42 UTC 2011 i686 i686 i386 GNU/Linux"
>
>  lspci output for with and without dock to be attached.
>
>  Full model info on laptop:
>  Dell Inspiron Duo
>  ---
>  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
>  AplayDevices: aplay: device_list:240: no soundcards found...
>  ApportVersion: 1.23-0ubuntu4
>  Architecture: i386
>  ArecordDevices: arecord: device_list:240: no soundcards found...
>  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
>  CRDA: Error: [Errno 2] No such file or directory
>  DistroRelease: Ubuntu 11.10
>  InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007)
>  MachineType: Dell Inc. Inspiron 1090
>  Package: linux (not installed)
>  ProcEnviron:
>   PATH=(custom, user)
>   LANG=en_GB.UTF-8
>   SHELL=/bin/bash
>  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=828A11898A117ABD loop=/ubuntu/disks/root.disk ro quiet splash i8042.noloop=1 usbhid.quirks=0xeef:0x725e:0x40 vt.handoff=7
>  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
>  PulseSinks: Error: command ['pacmd', 'list-sinks'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
>  PulseSources: Error: command ['pacmd', 'list-sources'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
>  RelatedPackageVersions:
>   linux-restricted-modules-3.0.0-12-generic N/A
>   linux-backports-modules-3.0.0-12-generic  N/A
>   linux-firmware                            1.60
>  Tags:  oneiric
>  Uname: Linux 3.0.0-12-generic i686
>  UpgradeStatus: Upgraded to oneiric on 2011-10-25 (63 ...

[teh603 (darth-giles)]

So why is this still listed as "incomplete" when we have good evidence there is a bug and we're still able to duplicate it, even with the latest BIOS?

[penalvch (penalvch)]

teh603, please stop posting comments here. If you have a problem in Ubuntu, please file a new report as requested of you in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/908560/comments/42 .

[Danny Staple (danny-orionrobots)]

As Xavier stated - an upgrade, that is not required for other systems is not really a solution. It is also not the solution. However, I would like to state that in precise, this seems to have stopped occurring, along with the extremely frustrating new problem of no hibernate functionality at all - rendering precise rather precisely useless on all mobile devices. Ubuntu is clearly not a suitable linux distro for the Dell Duo tablet device.

[Florian Echtler (floe)]

A proper fix for this is scheduled to be merged into kernel 3.6: http://git.kernel.org/?p=linux/kernel/git/lenb/linux.git;a=commit;h=f197ac13f6eeb351b31250b9ab7d0da17434ea36

Would be great to see this fix incorporated into Ubuntu kernels...