Dell Latitude laptops freeze when docking/undocking.

[Jan Schneider]

Unfortunately this doesn't happen reproducable, yet regularly. If I put the laptop into the docking station, sometimes the system completely locks up. Not even SysRq works anymore (not that it would do what it should in Ubuntu, but that's another story).
There's not much in the logs either, unfortunately, this is all from kern.log:

Aug 7 14:02:50 tank kernel: [224970.438066] usb 1-3: USB disconnect, address 16
Aug 7 14:02:50 tank kernel: [224970.564100] usb 1-4: USB disconnect, address 17
Aug 7 14:02:50 tank kernel: [224970.564108] usb 1-4.1: USB disconnect, address18
Aug 7 14:02:51 tank kernel: [224970.625181] usb 1-4.3: USB disconnect, address19
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jan 22992 F.... knotify4
                      jan 23033 F.... pulseaudio
                      jan 23041 F.... kmix
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf6adc000 irq 21'
   Mixer name : 'Intel G45 DEVCTG'
   Components : 'HDA:111d76b2,1028024f,00100302 HDA:80862802,80860101,00100000'
   Controls : 24
   Simple ctrls : 15
DistroRelease: Ubuntu 10.04
Frequency: Once a day.
HibernationDevice: RESUME=UUID=793b7c91-6a66-4c1b-a63d-44ba490663fb
MachineType: Dell Inc. Latitude E6500
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: root=UUID=bf4ea0cc-a14c-49f1-8f2e-dc35f6c30a41 ro quiet splash
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5
Regression: No
RelatedPackageVersions: linux-firmware 1.34.1
Reproducible: No
Tags: lucid audio needs-upstream-testing
Uname: Linux 2.6.32-24-generic x86_64
UserGroups: adm admin cdrom dialout dip fuse libvirtd lpadmin mythtv plugdev sambashare
WpaSupplicantLog:

dmi.bios.date: 12/18/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0NY667
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA11:bd12/18/2008:svnDellInc.:pnLatitudeE6500:pvr:rvnDellInc.:rn0NY667:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E6500
dmi.sys.vendor: Dell Inc.

[Jan Schneider (yunosh)]

Here's some more useful information from a recent freeze. This time, the system didn't lock up completely, but I still wasn't able to correctly shut it down:

Aug 12 21:23:45 tank kernel: [178281.910322] PGD 0
Aug 12 21:23:45 tank kernel: [178281.910330] CPU 1
Aug 12 21:23:45 tank kernel: [178281.910331] Modules linked in: nls_iso8859_1 nl
s_cp437 vfat fat mmc_block aes_x86_64 aes_generic i915 drm binfmt_misc bnep ipt_
MASQUERADE bridge stp kvm_intel kvm input_polldev xt_tcpudp xt_DSCP xt_TCPMSS ip
t_LOG ipt_REJECT iptable_nat nf_nat iptable_mangle iptable_filter xt_multiport x
t_state xt_limit xt_conntrack nf_conntrack_ftp nf_conntrack_ipv4 nf_conntrack nf
_defrag_ipv4 ip_tables x_tables btusb uinput sbp2 lp snd_hda_intel snd_pcm_oss s
nd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss arc4 snd_seq_midi ecb snd_rawmidi
 snd_seq_midi_event uvcvideo iwlagn snd_seq compat_ioctl32 iwlcore joydev ppdev
video psmouse parport_pc led_class snd_timer snd_seq_device hid_microsoft output
 videodev v4l1_compat sdhci_pci sdhci ricoh_mmc serio_raw parport pcmcia intel_a
gp mac80211 iTCO_wdt iTCO_vendor_support snd dcdbas usbhid pcspkr soundcore yent
a_socket rsrc_nonstatic pcmcia_core snd_page_alloc cfg80211 ohci1394 ieee1394 e1
000e fbcon tileblit font bitblit softcursor
Aug 12 21:23:45 tank kernel: [178281.910382] Pid: 13570, comm: dolphin Tainted:
G D W 2.6.28-15-generic #48-Ubuntu
Aug 12 21:23:45 tank kernel: [178281.910383] RIP: 0010:[<ffffffff8022f559>] [<ffffffff8022f559>] __ticket_spin_lock+0x9/0x20
Aug 12 21:23:45 tank kernel: [178281.910386] RSP: 0018:ffff8800c490bc58 EFLAGS: 00010282
Aug 12 21:23:45 tank kernel: [178281.910388] RAX: 0000000000000100 RBX: ffff8800494d2930 RCX: 00007ff986c81000
Aug 12 21:23:45 tank kernel: [178281.910390] RDX: ffff88004945fa20 RSI: ffff8801184ad3f8 RDI: 0000000000000040
Aug 12 21:23:45 tank kernel: [178281.910391] RBP: ffff8800c490bc58 R08: ffff8801184ad3f8 R09: 0000000000000003
Aug 12 21:23:45 tank kernel: [178281.910393] R10: 0000000000000002 R11: 0000000000000000 R12: ffff88011890b540
Aug 12 21:23:45 tank kernel: [178281.910394] R13: 0000000000000000 R14: 0000000000000040 R15: 0000000000000000
Aug 12 21:23:45 tank kernel: [178281.910397] FS: 0000000000000000(0000) GS:ffff88011b803a80(0000) knlGS:0000000000000000
Aug 12 21:23:45 tank kernel: [178281.910398] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Aug 12 21:23:45 tank kernel: [178281.910400] CR2: 0000000000000040 CR3: 0000000000201000 CR4: 00000000000026a0
Aug 12 21:23:45 tank kernel: [178281.910401] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug 12 21:23:45 tank kernel: [178281.910403] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Aug 12 21:23:45 tank kernel: [178281.910405] Process dolphin (pid: 13570, threadinfo ffff8800c490a000, task ffff88009788acc0)
Aug 12 21:23:45 tank kernel: [178281.910408] ffff8800c490bc68 ffffffff8069b839ffff8800c490bc98 ffffffff802c9b8e
Aug 12 21:23:45 tank kernel: [178281.910499] RSP <ffff8800c490bc58>
Aug 12 21:23:45 tank kernel: [178281.910503] ---[ end trace f5982ff97d01ddd8 ]---
Aug 12 21:23:47 tank kernel: [178283.984902] PGD 0
Aug 12 21:23:47 tank kernel: [178283.9850...

[DanielRoesler (diafygi)]

I can confirm this is happening with my Dell D630 in Karmic beta. Whenever I put it in the docking station, the entire screen freezes and all keys become unresponsive. I have to do a hard reboot to fix the problem.

This happens every time for me.

[Brian R (brian-rardin-deactivatedaccount-deactivatedaccount)]

Confirmed here too. Dell D630 Karmic 64bit and Dell D620 Karmic 32bit on Dell D/Port. Does not hang removing from the port replicator but does hang when placing back on the port replicator. No USB or other devices connected to the port replicator in either instance.

Happens every time on both platforms (32/64) on both machines (D630/D620)

[PaulReiber (paulreiber)]

Similar problem here; I have a Dell Latitude E6500 running Ubuntu 9.04_amd64 which I installed just last night.

I just now had a similar hang; I found this launchpad bug by searching for what I had found in /var/log/messages:
Oct 19 08:38:15 RStops-PBR kernel: [ 4864.877428] ACPI Error (evevent-0303): No installed handler for fixed event [00000002] [20080926]

HOWEVER... I hadn't removed the unit from the dock; it was simply running the "lattice" screensaver, which froze, displaying donuts onscreen. I had docked the unit before booting.

I'll do additional test w/ docking/undocking and add info if/when I learn anything new.

Here's hoping this is useful additional information.
-Paul

[PaulReiber (paulreiber)]

Followup:

Undocking/redocking worked just fine; no crash. I have very little hooked to my dock, however; just (a) power (b) an ethernet cable and (c) a USB mouse.

If you're seeing this freeze... do you have a lot of other stuff plugged into the dock? Consider using the process of elimination if so, to help isolate.

[Jan Schneider (yunosh)]

It's hard to isolate, because I don't see this with every docking.

For the record, I have power, dvi, usb mouse and usb keyboard connected to the dock.

[PaulReiber (paulreiber)]

Followup:

Multiple screen locks later, no more crash/hangs with the "lattice" screensaver either. Might be sporadic? Leaving the screensaver running for a longer period now (lunch!) as another test.
-pbr

P.S. though I've been running the lattice screensaver, I haven't seen the "donuts" version come up again since the crash. Maybe the lunch test will be more telling.

[PaulReiber (paulreiber)]

So nearly an hour of running the lattice screen saver, and no lock-up.
 This seems truly sporadic; I'll continue looking for other potential
causes.

Motivation: I hate it when an O.S. I've just installed crashes...
even if only once!

Best,
-Paul Reiber
http://bit.ly/reiber

[Jim Hunziker (landtuna)]

I get the crash with my D520 (need to use SysRq b to reboot) when the monitor attached to the docking station doesn't have the same screen resolution as the laptop. If I monitor is off entirely, I can dock and undock without a problem.

[PaulReiber (paulreiber)]

So I had another hang quite similar to the previous one.

The computer was doing very different things in the background; this
time, copying video files from one external USB hard drive to another.

I locked the screen because I was leaving my desk for a while, and
when I came back and moved the mouse, bam - the box locked up solid.

"The matrix" screensaver was running at the time.

Here's the only correlation I can think of: In both cases I had moved
the mouse, to interrupt the screensaver, when it locked up.

So I'm wondering if this has something to do with the logic that
breaks whichever screensaver is running.

Kind regards,
-Paul Reiber

[PaulReiber (paulreiber)]

On Wed, Nov 4, 2009 at 10:40 AM, Paul Reiber <email address hidden> wrote:
> So I had another hang quite similar to the previous one.
>
[...]
>
> Here's the only correlation I can think of:  In both cases I had moved
> the mouse, to interrupt the screensaver, when it locked up.
>
> So I'm wondering if this has something to do with the logic that
> breaks whichever screensaver is running.

This happened again today; I have 100% correlation now for this hang
being related to moving the mouse to exit the screensaver. This is a
pretty standard 9.04 install on a pretty standard Dell Latitude E6500
notebook computer.

I had the matrix screensaver running, and came back to my desk after
being away for maybe 5 minutes, and moved the mouse. Instead of
popping up a "password" dialog box, the computer locked up solid, with
a frozen matrix image onscreen. I did notice the hard-disk light
blipping approx. every 4-5 seconds; this is something it tends to do
when I have VirtualBox running, and it continued to blip even after
the machine had locked up solid.

But other than that the machine really was hosed; no Ctrl-alt-F1, no
Ctrl-alt-Backspace, no wifi light lighting if I flipped the wireless
killswitch to "on"... no suspend by hitting Fn-F1 (the moon icon)...
nothing. Oh... it DID let me change the screen brightness with the
Fn-uparrow and Fn--downarrow keys, and it DID adjust the brightness
down when I undocked it, and back up when I re-docked it. I'm
guessing none of that involves the kernel. Holding down the power
button for like 10 seconds was the final solution. Yuck.

I'll be happy to answer any further questions. I'm going to upgrade
to 9.10 sometime next week, so if you want me to assist by running any
tests or diagnostics please let me know ASAP.

Here's hoping this helps.
-Paul

[PaulReiber (paulreiber)]

FYI Yesterday afternoon I had a repeat of the exact same freeze.

Kind regards,
-Paul Reiber

[Steffen Torp (steffen-ubuntu)]

Confirmed on a brand new Dell Latitude E6500, with a fresh install of Ubuntu 9.10 64 bit. Oddly enough, after the fresh install docking went smoothly. After a couple of days, external mouse and keyboard did not connect when docking. For the last two days (after using it for two weeks) the whole computer freezes completely when docking. This happens regardless of docking with lid closed or open, and screensaver on or off.

[SPGWhistler (spgwhistler)]

I have a dell latitude d630 with ubuntu 9.10.

My system 100% freezes when I dock - only resolvable by a hard reset.

The docking station has two monitors connected to it. So when I dock, my screen resolution should go from 1440x900 to 3360x1860.

I am convinced this is something to do with the video card and the xorg configuration, but that is the best I can figure out.

[Stephan Trebels (ncubede)]

Got a E6500 (8GB) with 9.10 64bit here. Intermittent complete freeze (especially when any power management happening, I initially thought this was suspend to something, but it also happens while I'm typing).

Additionally I have intermittent USB host controller process errors regardless which type of device is attached. Is this also in place for other people? Messages like the below happen in the log then:

[21670.277650] uhci_hcd 0000:00:1d.0: host controller process error, something bad happened!
[21670.277679] uhci_hcd 0000:00:1d.0: host controller halted, very bad!
[21670.277732] uhci_hcd 0000:00:1d.0: HC died; cleaning up
[21670.277777] usb 6-1: USB disconnect, address 2
[21670.373614] usb 6-2: USB disconnect, address 3

I tried a new BIOS (A18, which helped a bit), I tried various kernels (-16 and -18 seem to be better than -17), but the intermittent freezes are extremely annoying...

[Jeremy Foshee (jeremyfoshee)]

Hi Jan,

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 410285

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.]

[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.]

[Jan Schneider (yunosh)]

This still happens with the latest Kernel version for Lucid. I'm running 2.6.32-22-generic at the moment.

[Montel Edwards (montel)]

I too can confirm this.

I have found out that if I put the system on standby before I dock it, it works fine.
I also have to put it on standby when undocking also.

[Jeremy Foshee (jeremyfoshee)]

Jan,
    Please answer the questions I put forward in my previous. There are several major items that I asked from you.

Montel, and others seemingly affected by this issue, Please file new bugs for your specific hardware. This is per the kernel team policy on bug duplicates which applies here as well: https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs

Thanks!

~JFo

[Jan Schneider (yunosh)]

apport information

[Jan Schneider (yunosh)]

apport information

[Jan Schneider (yunosh)]

apport information

[Jan Schneider (yunosh)]

apport information

[Jan Schneider (yunosh)]

apport information

[Jan Schneider (yunosh)]

apport information

[Jan Schneider (yunosh)]

apport information

[Jan Schneider (yunosh)]

apport information

[Jan Schneider (yunosh)]

apport information

[Jan Schneider (yunosh)]

apport information

[Jan Schneider (yunosh)]

apport information

[Jan Schneider (yunosh)]

apport information

[Jan Schneider (yunosh)]

apport information

[Jan Schneider (yunosh)]

apport information

[Jan Schneider (yunosh)]

apport information

[Jan Schneider (yunosh)]

apport information

[Jan Schneider (yunosh)]

apport information

[Jan Schneider (yunosh)]

apport information

[Jan Schneider (yunosh)]

apport information

[Jan Schneider (yunosh)]

Hope this helps. And no, I can't test the mainline builds.

[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 development release http://cdimage.ubuntu.com/daily-live/current/ . 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.]

[vhellmet (vhellmet)]

I can confirm this with Ubuntu 10.10 on a Latitude E6410 laptop.

[PaulReiber (paulreiber)]

LinkedIn
------------

Bug,

I'd like to add you to my professional network on LinkedIn.

- Paul

Paul Reiber
Linux Specialist at Rackspace Hosting
San Antonio, Texas Area

Confirm that you know Paul Reiber:
https://www.linkedin.com/e/8wwr7o-gzm0t24l-2p/isd/6236735106/d3_isp-Z/?hs=false&tok=2k7xsEysoBB581

--
You are receiving Invitation to Connect emails. Click to unsubscribe:
http://www.linkedin.com/e/8wwr7o-gzm0t24l-2p/XXVn_Yu8-XPXfdcZu9XaBAo8wuRHXf9TduOFAIC/goo/410285%40bugs%2Elaunchpad%2Enet/20061/I2167185066_1/?hs=false&tok=00QEnhTj4BB581

(c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA.

[penalvch (penalvch)]

Jan Schneider, thank you for reporting this bug 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 capture the oops entirely following https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Capturing_OOPs ? 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 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.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Riono (thecrapfreezer)]

Same problem showed up on my Sony Vaio VGN-SR21M/s. If I try to dock when system is still running, the system will freeze. The same happens if I try to undock the running system.

Ubuntu 12.04

[penalvch (penalvch)]

Riono, if you are having a problem in Ubuntu, please file a new report by executing the following via the Terminal and feel free to subscribe me to it:
ubuntu-bug linux

Thanks!

[Michael (michaeljt)]

I am seeing what looks very much like this issue on a Dell Latitude E6410 running Quantal (previously with Precise). I get a hard hang (caps lock LED does not respone) reasonably repeatably after docking *with the laptop screen open* and moving the mouse. I tried installing a self-built kernel with panic-on-hard-hang enabled, but it sadly failed to panic. Is there any way I can check whether this is indeed the same issue? If so, can I provide any useful information which is not already available?

[penalvch (penalvch)]

Michael, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.