Hot-Docking/-Undocking Dell D630 from Docking Station

[Matthias Meier]

Hot-Undocking isn't performed properly on Dell D630,
neither while the system is running nor in standby mode (suspend to RAM)

A) Pushing the undock button while the system is running:
 - the Undock-LED at the docking station only flashes short (goes off and 1/2sec later on again).
 - in syslog the undocking event is recognized (see syslog below)
 - but after a while, the "kacpi_notify" process crashes (see syslog below)
 - then, the processor-load of "kacpi_notify" stays at 50%
 - until the notebook is removed from the docking station

B) Undocking in standby mode:
 - Undocking the system in standby mode (Suspend to RAM), and powering off-docked,
 - the X-Window-System will be locked (may be restarted in a virtual terminal by restarting gdm)
 - Even worse after redocking in standby agin: the USB ressources on the docking station arn't recognized again.
 - Otherwise, when redocking the running system, the system freezes often

Release: 8.04 "Ubuntu hardy (development branch)", but the problem also existed on older Releases (Gutsy, Feisty)
Package: linux-image ?

Syslog of after pushing the Undock-Button:

[11902.936932] ACPI: \_SB_.PCI0.PCIE.GDCK - undocking
[11960.997840] BUG: soft lockup - CPU#0 stuck for 11s! [kacpi_notify:53]
[11960.997846]
[11960.997848] Pid: 53, comm: kacpi_notify Not tainted (2.6.24-12-generic #1)
[11960.997850] EIP: 0060:[<c0236876>] EFLAGS: 00000246 CPU: 0
[11960.997856] EIP is at acpi_os_write_port+0xd/0x2c
[11960.997857] EAX: 00000087 EBX: 000000b2 ECX: 00000008 EDX: 000000b2
[11960.997859] ESI: 000000b2 EDI: f7d11cd8 EBP: f7c45118 ESP: f7d11be4
[11960.997861] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
[11960.997863] CR0: 8005003b CR2: 0838bd18 CR3: 377d2000 CR4: 00000690
[11960.997865] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
[11960.997867] DR6: ffff0ff0 DR7: 00000400
[11960.997886] [<c0242630>] acpi_ex_system_io_space_handler+0x3c/0x41
[11960.997900] [<c02425f4>] acpi_ex_system_io_space_handler+0x0/0x41
[11960.997904] [<c023b7fa>] acpi_ev_address_space_dispatch+0x162/0x1ab
[11960.997927] [<c023f716>] acpi_ex_access_region+0x203/0x217
[11960.997939] [<c02425f4>] acpi_ex_system_io_space_handler+0x0/0x41
[11960.997942] [<c023b7fa>] acpi_ev_address_space_dispatch+0x162/0x1ab
[11960.997953] [<c012465a>] task_rq_lock+0x4a/0x80
[11960.997967] [<c023f83d>] acpi_ex_field_datum_io+0x113/0x1a7
[11960.997973] [<c023f716>] acpi_ex_access_region+0x203/0x217
[11960.997992] [<c023fc31>] acpi_ex_write_with_update_rule+0x12a/0x132
[11960.998005] [<c023f83d>] acpi_ex_field_datum_io+0x113/0x1a7
[11960.998018] [<c023fed9>] acpi_ex_insert_into_field+0x2a0/0x2ab
[11960.998055] [<c023e47a>] acpi_ex_write_data_to_field+0x1fe/0x22c
[11960.998066] [<c0236aa2>] acpi_os_release_object+0x5/0x8
[11960.998082] [<c02428ce>] acpi_ex_store_object_to_node+0x72/0xab
[11960.998098] [<c0242a63>] acpi_ex_store+0xeb/0x23c
[11960.998115] [<c0240814>] acpi_ex_opcode_1A_1T_1R+0x416/0x561
[11960.998121] [<c024100c>] acpi_ex_resolve_operands+0x237/0x55b
[11960.998144] [<c0238f4f>] acpi_ds_exec_end_op+0xca/0x39b
[11960.998147] [<c0246f67>] acpi_ps_get_next_arg+0x1c6/0x227
[11960.998155] [<c0247640>] acpi_ps_complete_op+0x1f0/0x202
[11960.998163] [<c0247dbd>] acpi_ps_append_arg+0x16/0x75
[11960.998173] [<c0247bd6>] acpi_ps_parse_loop+0x584/0x722
[11960.998182] [<c02396ab>] acpi_ds_call_control_method+0x101/0x154
[11960.998197] [<c0247051>] acpi_ps_parse_aml+0x65/0x218
[11960.998211] [<c0248260>] acpi_ps_execute_method+0x111/0x1b1
[11960.998224] [<c0245641>] acpi_ns_evaluate+0x99/0xf0
[11960.998235] [<c02452a3>] acpi_evaluate_object+0x11b/0x1c0
[11960.998247] [<c0237555>] acpi_evaluate_integer+0x83/0xb6
[11960.998258] [<c0236aff>] acpi_os_execute_notify+0x0/0x2b
[11960.998262] [<f8d04040>] dock_present+0x1f/0x35 [dock]
[11960.998272] [<f8d04444>] dock_notify+0x32/0xc9 [dock]
[11960.998279] [<c023c273>] acpi_ev_notify_dispatch+0x4c/0x55
[11960.998285] [<c0236b21>] acpi_os_execute_notify+0x22/0x2b
[11960.998292] [<c013ddcf>] run_workqueue+0xbf/0x160
[11960.998304] [<c013e870>] worker_thread+0x0/0xe0
[11960.998309] [<c013e8f4>] worker_thread+0x84/0xe0
[11960.998315] [<c0141b80>] autoremove_wake_function+0x0/0x40
[11960.998324] [<c013e870>] worker_thread+0x0/0xe0
[11960.998329] [<c01418c2>] kthread+0x42/0x70
[11960.998331] [<c0141880>] kthread+0x0/0x70
[11960.998337] [<c0106677>] kernel_thread_helper+0x7/0x10
[11960.998348] =======================

[Leann Ogasawara (leannogasawara)]

Hi Matthias,

Thank you for taking the time to report this bug and helping to make Ubuntu better. Per the kernel team's bug policy, can you please attach the following information. Please be sure to attach each file as a separate attachment.

* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

It would be helpful if you attached a dmesg output which captures the errors you are seeing. For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

[Matthias Meier (matthias-j-meier)]

Appended are following Logs

After pushing the "disconnect" button on then Docking station:
- dmesg.log
- lspci-vvnn.log

1 minute later, Notebook still on docking station, after pushing the "disconnect" button a second time:
- dmesg.log2
- lspci-vvnn.log2

a seconds later, both keyboards hangs completely (the built in on the notbook and the external "logitech dinovo cordless" connected to the docking station via usb), and the fan begins to work (heavy load probably on kacpi_notify process).

[Matthias Meier (matthias-j-meier)]

Propably this bug is the same as
  Ubuntu Bug #189185 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/189185)
and
  Kernel.org Bug #9874 (http://bugzilla.kernel.org/show_bug.cgi?id=9874)

which discussion ends in following patch proposal:

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=7a8d37a37380e2b1500592d40b7ec384dbebe7a0

Any suggestions? Waiting and hoping on Kernel 2.6.25?

[Leann Ogasawara (leannogasawara)]

Hi Matthias,

Sorry for the delayed response. Yes, the patch you referenced will be available in Hardy+1 ie the Intrepid Ibex 8.10 release. However, if you'd be interested in testing the upstream kernel which contains this patch it would be good to have confirmation it does indeed resolve your issue. For help with building and running the upstream kernel, refer to: https://wiki.ubuntu.com/KernelTeam/GitKernelBuild . Thanks.

[Leann Ogasawara (leannogasawara)]

Hi Matthias,

The patch you referenced does appear to be in the Intrepid Ibex 8.10 kernel which is currently being pulled together. Would you care to test the Intrepid Ibex 8.10 kernel? It is currently available in the following PPA:

https://edge.launchpad.net/~kernel-ppa/+archive

If you are not familiar with how to install packages from a PPA basically do the following:

Create the file /etc/apt/sources.list.d/kernel-ppa.list to include the following two lines:

deb http://ppa.launchpad.net/kernel-ppa/ubuntu hardy main
deb-src http://ppa.launchpad.net/kernel-ppa/ubuntu hardy main

Then run the command:

sudo apt-get update

You should then be able to install the linux-image-2.6.25 kernel package. Please let us know your results. Thanks.

[Matthias Meier (matthias-j-meier)]

I installed as proposed linux-image-2.6.25-1-generic but that kernel didn't work reliable on my Dell Latitude D630:

- Sometimes after the boot process, the system doesn't show the login-screen. In this case, it is not possible to change to a virtual console as well.
- Standby mode doesn't work reliable: sometimes it doesn't enter standby-mode, or the system doesn't wake up (also blank screen and freezed).
- The externel DVI-Monitor is always blank, inspite of correct activiating the interface and display-mode with "xrandr"
- The old problem with the undock-key on the docking station still exists (after pushing the undock-key, the processor-load of "kacpi_notify" raises to 50%)

Therefore, I experimented again with the 2.6.24-kernel from hardy on my problem B) "Undocking in standby mode" and came to the following solutions:

- wake-up after standby is working correctly...
-> if changing the display mode from "external-DVI-display only" to "both display mode" (internal LCD and external DVI) *before* going to standby.

- The wireless keyboard/mouse (connected via Logitech usb-receiver) will work after standby...
-> if executing a "lsusb" after wake up
(the first "lsusb" after standby shows no usb-devices at all; after this first "lsusb" all usb-devices are shown and my wireless keyboard/mouse is working correctly)

To execute "lsusb" automaticlly after standby, I created following script in

File: "/etc/pm/sleep.d/99-lsusb.sh"

#! /bin/bash
[ "$1" == resume ] && lsusb >/dev/null

[Ashwin (cybernytrix)]

I have a Dell D620 laptop with dock. Today morning I docked it and tried to update and it seems it got stuck. I was able to get some info out of dmesg:

[ 575.343213] BUG: soft lockup - CPU#1 stuck for 11s! [kacpi_notify:51]
[ 575.343220]
[ 575.343222] Pid: 51, comm: kacpi_notify Tainted: P (2.6.24-18-generic #1)
[ 575.343225] EIP: 0060:[<c023a636>] EFLAGS: 00000246 CPU: 1
[ 575.343231] EIP is at acpi_os_write_port+0xd/0x2c
[ 575.343232] EAX: 00000087 EBX: 000000b2 ECX: 00000008 EDX: 000000b2
[ 575.343234] ESI: 000000b2 EDI: f7d0fcd8 EBP: f7c45d20 ESP: f7d0fbe4
[ 575.343236] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
[ 575.343238] CR0: 8005003b CR2: b7c17000 CR3: 265a4000 CR4: 00000690
[ 575.343240] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
[ 575.343241] DR6: ffff0ff0 DR7: 00000400
[ 575.343260] [<c02463f0>] acpi_ex_system_io_space_handler+0x3c/0x41
[ 575.343275] [<c02463b4>] acpi_ex_system_io_space_handler+0x0/0x41
[ 575.343279] [<c023f5ba>] acpi_ev_address_space_dispatch+0x162/0x1ab
[ 575.343300] [<c02434d6>] acpi_ex_access_region+0x203/0x217
[ 575.343311] [<c02463b4>] acpi_ex_system_io_space_handler+0x0/0x41
[ 575.343316] [<c023f5ba>] acpi_ev_address_space_dispatch+0x162/0x1ab
[ 575.343326] [<c014a288>] tick_program_event+0x38/0x60
[ 575.343340] [<c02435fd>] acpi_ex_field_datum_io+0x113/0x1a7
[ 575.343347] [<c02434d6>] acpi_ex_access_region+0x203/0x217
[ 575.343365] [<c02439f1>] acpi_ex_write_with_update_rule+0x12a/0x132
[ 575.343378] [<c02435fd>] acpi_ex_field_datum_io+0x113/0x1a7
[ 575.343390] [<c0243c99>] acpi_ex_insert_into_field+0x2a0/0x2ab
[ 575.343420] [<c024223a>] acpi_ex_write_data_to_field+0x1fe/0x22c
[ 575.343429] [<c023a862>] acpi_os_release_object+0x5/0x8
[ 575.343443] [<c024668e>] acpi_ex_store_object_to_node+0x72/0xab
[ 575.343456] [<c0246823>] acpi_ex_store+0xeb/0x23c
[ 575.343472] [<c02445d4>] acpi_ex_opcode_1A_1T_1R+0x416/0x561
[ 575.343479] [<c0244dcc>] acpi_ex_resolve_operands+0x237/0x55b
[ 575.343501] [<c023cd0f>] acpi_ds_exec_end_op+0xca/0x39b
[ 575.343504] [<c024ad27>] acpi_ps_get_next_arg+0x1c6/0x227
[ 575.343511] [<c024b400>] acpi_ps_complete_op+0x1f0/0x202
[ 575.343519] [<c024bb7d>] acpi_ps_append_arg+0x16/0x75
[ 575.343531] [<c024b996>] acpi_ps_parse_loop+0x584/0x722
[ 575.343542] [<c023d46b>] acpi_ds_call_control_method+0x101/0x154
[ 575.343557] [<c024ae11>] acpi_ps_parse_aml+0x65/0x218
[ 575.343571] [<c024c020>] acpi_ps_execute_method+0x111/0x1b1
[ 575.343584] [<c0249401>] acpi_ns_evaluate+0x99/0xf0
[ 575.343595] [<c0249063>] acpi_evaluate_object+0x11b/0x1c0
[ 575.343608] [<c023b315>] acpi_evaluate_integer+0x83/0xb6
[ 575.343620] [<c023a8bf>] acpi_os_execute_notify+0x0/0x2b
[ 575.343624] [<f8b46040>] dock_present+0x1f/0x35 [dock]
[ 575.343635] [<f8b46444>] dock_notify+0x32/0xc9 [dock]
[ 575.343645] [<c0240033>] acpi_ev_notify_dispatch+0x4c/0x55
[ 575.343653] [<c023a8e1>] acpi_os_execute_notify+0x22/0x2b
[ 575.343660] [<c013ce8f>] run_workqueue+0xbf/0x160
[ 575.343674] [<c013d930>] worker_thread+0x0/0xe0
[ 575.343680] [<c013d9b4>] worker_thread+0x84/0xe0
[ 575.343687] [<c0140c40>] autoremove_wake_functi...

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Matthias Meier (matthias-j-meier)]

Experiences with Intrepid Ibex 8.10 using kernel image 2.6.27-2-generic:

Problem A) "Undocking/Docking when system is running" _still exists_:
--> though the Undock-LED goes off after pushing the Undock-switch, the system freezes sometimes when undocking or redocking hot

Problem B) "Undocking in standby mode" seems to be *solved*:
--> But _only_ if the Notebook-Display is _switched on_ by CRT/LCD-Hotkey before going to standby mode!

-> Even better: the USB-Problem after resuming docked with the external USB-Keybpard/Mouse seems to be _solved_ (see comment from 2008-05-30).

Many thanks to Ubuntu and Linux Kernel Teams,
Matthias

PS:Booting Intrepid respectively Kernel >= 2.6.25 is only possible with boot splash disabled. Otherwise the system locks completely.

[lilbudda (cory-meisch-gmail)]

I can confirm that hotdocking my Lattitude d530 will cause a system freeze as well.

[jbwiv (bugs-sourceillustrated)]

This affects me as well....Latitude D630 and Intrepid Ibex ( 2.6.27-7-generic #1 SMP)

[Steve Conklin (sconklin)]

I'm not 100% certain that it's the same problem, but I just added a patch to solve a very similar problem on a different model. That bug report is here:

https://bugs.launchpad.net/ubuntu/+bug/41091

The test kernel for that bug is here:
http://people.ubuntu.com/~sconklin/41091/

It would be very helpful if you could test this and see whether it also resolves your problem.

[Chris Peach (peachris+ubuntu)]

I have the same hardware and had the same problems as the original bug reporter. Initially with Hardy, docking was just a little unreliable, but at least in builds 2.6.24-22 and 2.6.24-23, docking became unusable because it always locked up the system (no matter whether hot, suspended or hibernated docking).

Now I have tried the test kernel Steve recommended on 2008-11-28 <http://people.ubuntu.com/~sconklin/41091/>. It resolves all my docking problems. Now I am using a more recent version I found at <http://people.ubuntu.com/~sconklin/22070/> which also works just fine.

Question: How do I get security updates for this kernel? The kernel-ppa repository recommended above seems to be empty.

[Matthias Meier (matthias-j-meier)]

 the current Kernel (2.6.27-11-generic) seems to be quite stable - at least on my system. The only problem with docking/undocking I have is the serial interface (ttyS0) on the docking station. After undocking/docking ttyS0 is no more working.

[wseemann (wseemann)]

So are there any actual patches(that will be released through ubuntu's updates) being put into place for this. I'm running a Hardy install and this is quite annoying.

[Leann Ogasawara (leannogasawara)]

As you can see in comment 17 of this bug:

https://bugs.edge.launchpad.net/ubuntu/+bug/204210/comments/17

Steve pointed to bug 41091which contained a set of patches which solved a similar issue. Those patches have since been released as a stable update for the Intrepid kernel. Also @Matthias Meier (the original bug reporter) has commented that the latest 2.6.27-11 kernel for Intrepid seems quite stable. As a result I'm marking this bug Fix Released for Intrepid. If anyone else is still experiencing issue with the latest kernel, please open a new report. Thanks.

[wseemann (wseemann)]

I appreciate the response, however as you can see in my comment, I'm using Hardy. Since Hardy does not use the Intrepid kernel we still need an official patch for Hardy. I think this is important since many people rely on a stable LTS and don't want to hack in an intrepid kernel to their Hardy install.