Bug 43133 - Dell E6400 works with 3.x kernel un-docked but randomly hard freezes when in docking station
Summary: Dell E6400 works with 3.x kernel un-docked but randomly hard freezes when in ...
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: USB (show other bugs)
Hardware: i386 Linux
: P1 high
Assignee: Greg Kroah-Hartman
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-20 09:15 UTC by Danny Goodall
Modified: 2012-09-05 17:53 UTC (History)
1 user (show)

See Also:
Kernel Version: 3.4.0-rc2
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Danny Goodall 2012-04-20 09:15:18 UTC
Overview 
---
My Dell E6400 works without a problem when running kernel 3.0.0-16 when the laptop not in the docking station (Under Ubuntu 11.10). But when booted in the laptop docking station it boots and allow me to log in but somewhere between 30 seconds and 180 minutes it will ALWAYS hard freeze. More often than not this happens with 180 seconds. This manifests itself as the screen(s') contents frozen, keyboard unresponsive (No LED light response) and the only way to shutdown is to hold the power key for 5-10 seconds. 

I am able to run the same hardware configuration with Ubuntu 10.10 under kernel 2.6.35-32 with no problem - whether docked or un-docked.

Steps to reproduce
---
Boot laptop with a 3.x kernel when attached to docking station and within  (generally) 30-600 seconds the system will hang. (Although I have used the machine for several hours before it hung)

Actual results
---
System hung, screen froze and no response from the keyboard (including LED lights and ALT+Fn).

Expected results
---
System should run normally without hanging.

Build where it occurs
---
3.0.0.16
3.2.4
3.4.0rc2

Additional build where problem doesn't occur
---
2.6.35-32

Additional information
---
I am using Ubuntu and had contributed to a bug report on launchpad, see

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/908335

I was advised to try various things by a Canonical employee (Joseph Salisbury) after which he determined that this was an upstream issue and asked me to create a 'bug' at kernel.org here, which I am duly doing.

Joseph asked me to download and try 2 different, newer kernels which I did.

I tried both kernel 3.2.14 and 3.4.0rc2 and was able to reproduce the problem with both of those. 

As I was not able to link in my graphics driver I was dealing with a character login screen but the result was the same. If I booted with the machine out of my docking station then I was able to use each kernel for long periods of time without an issue. If I booted when attached to my docking station, between 30-600 seconds after booting the system froze as described above.
Comment 1 Danny Goodall 2012-04-28 08:08:24 UTC
An update on this issue. I have installed Ububtu 12.04 with kernel 3.2.0-24 and the problem is still present.

I have also set the importance field above to HIGH, it was previously normal, I do hope that this is a user-field and that this isn't reserved for internal use, but the description of the HIGH category more accurately reflects the impact of this issue.
Comment 2 Danny Goodall 2012-05-16 11:53:55 UTC
A further update. I once again tried 12.04 ubuntu with kernel 3.2.0-24 using the Nouveau drivers instead of the Nvidia-authored ones. The hanging still happens. 

I also note that a large number of users are also reporting SIMILAR issues with the same kernel is 12.04 Ubuntu here...

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/993187

I don't know if this is the same issue though as my hang is complete with no response.

Can somebody please advise what the next steps are with this report?

Some summary points.
- System will completely hang at some point EVERY time the system is run in the docking station under various 3.x kernels
- This means it is reproducible easily which should aid tracking the issue down.
- System runs without ANY such problems when running outside of the docking station with 3.x kernels
- System works fine in docking station and out of docking station on Ubuntu 10.10 under kernel 2.6.35-32
- Ubuntu has stopped support for 10.10 and I cannot upgrade any further because each upstream release has the issue detailed above.
- Issue does not appear to be related to graphics driver as the problem presents itself with both Nvidia and Nouveau drivers.
- Help please.
Comment 3 Danny Goodall 2012-05-19 12:12:35 UTC
A further update and confirmation that I have narrowed down the issue further and found a work-around. I'll explain the situation long-hand here in case others are searching for the same problem.

There appears to be a problem between the USB hub in the Dell PR02X docking station and any 3.x kernel I have tried in Ubuntu that results in a complete system freeze/hang.

My tests suggest that plugging any device into the USB port on the Dell PR02X docking station will result in a total system hang/freeze - usually within 5-10 minutes. It requires no system interaction - simply leaving the system at the login prompt is usually enough.

Removing the same devices from the USB port on the PR02X docking station and connecting them to the USB ports on the Dell laptop itself (Latitude E6410 in my case), sees the system work flawlessly. 

This works OK as a workaround and for the first time in over a year I am able to run my system docked with a 3.x kernel. But obviously this isn't perfect as I have to connect and disconnect my USB devices every time I take my laptop away from the dock - negating the benefit of a docking station.

As mentioned above, I appear to be able to readily reproduce these issues at will so if someone, anyone, is interested in pursuing it further let me know.

See my entries here for more details

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/908335

Thanks to Loius Henruiquez of Canonical for his help in narrowing this issue down.
Comment 4 Alan 2012-09-05 17:53:30 UTC
The next steps are to carry on talking to your distribution. This is just used to track bugs.

It might be worth discussing on linux-usb@vger.kernel.org especially now you understand what the trigger appears to be. That is a *huge* step into being able to identify an actual root cause.

Note You need to log in before you can comment on or make changes to this bug.