Bug 24232 - usb crashes on macbookpro7,1 (was working on 2.6.35)
Summary: usb crashes on macbookpro7,1 (was working on 2.6.35)
Status: RESOLVED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: USB (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Greg Kroah-Hartman
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-02 20:45 UTC by panard
Modified: 2010-12-08 23:57 UTC (History)
0 users

See Also:
Kernel Version: 2.6.36
Subsystem:
Regression: Yes
Bisected commit-id:

Attachments
dmesg (97.91 KB, text/plain)
2010-12-02 20:45 UTC, panard 		Details
lsusb crash (3.77 KB, text/plain)
2010-12-02 20:47 UTC, panard 		Details
/proc/bus/usb/devices (5.78 KB, text/plain)
2010-12-02 20:48 UTC, panard 		Details
Add an attachment (proposed patch, testcase, etc.)

Description panard 2010-12-02 20:45:41 UTC 
Created attachment 38852 [details]
dmesg

Since 2.6.36, the usb seems broken on my powerbook7,1.
While dmesg first indicates standard messages, things start getting wrong when detecting usb devices :
[    0.621097] usb 1-6: new high speed USB device using ehci_hcd and address 2
[    0.672339] ehci_hcd 0000:00:04.1: port 6 high speed
[    0.672343] ehci_hcd 0000:00:04.1: GetStatus port:6 status 001005 0  ACK POWER sig=se0 PE CONNECT
[    0.736363] ehci_hcd 0000:00:04.1: set dev address 2 for port 6
[    0.742055] ehci_hcd 0000:00:04.1: Sending LPM 0x04001285 to port 6
[    0.753305] ehci_hcd 0000:00:04.1: LPM port:6 status 4001285 2  ACK POWER sig=se0 LPM SUSPEND PE CONNECT
[    0.753307] ehci_hcd 0000:00:04.1: LPM: device does not ACK, disable LPM -110
[    0.754090] ehci_hcd 0000:00:04.1: detected XactErr len 0/8 retry 1
(then a _lot_ of XactErr errors)

lsusb crashes too (log attached).
Comment 1 panard 2010-12-02 20:47:25 UTC 
Created attachment 38862 [details]
lsusb crash
Comment 2 panard 2010-12-02 20:48:31 UTC 
Created attachment 38872 [details]
/proc/bus/usb/devices
Comment 3 Greg Kroah-Hartman 2010-12-08 23:57:55 UTC 
Should be working in 2.6.37-rc5 now.
Note You need to log in before you can comment on or make changes to this bug.