On Sat, 19 May 2007 10:08:40 -0700 [EMAIL PROTECTED] wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=8510

A regression.

>            Summary: OHCI constantly attempts suspending root hub on ALi
>                     motherboard
>     Kernel Version: 2.6.22-rc2
>             Status: NEW
>           Severity: normal
>              Owner: [EMAIL PROTECTED]
>          Submitter: [EMAIL PROTECTED]
> 
> 
> Most recent kernel where this bug did *NOT* occur:
> 2.6.16.20
> 
> Distribution:
> Mandriva, kernel is vanilla kernel.org
> 
> Hardware Environment:
> Toshiba Portege 4000
> lspci:
> 00:00.0 Host bridge: ALi Corporation M1644/M1644T Northbridge+Trident (rev 01)
> 00:01.0 PCI bridge: ALi Corporation PCI to AGP Controller
> 00:02.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
> 00:04.0 IDE interface: ALi Corporation M5229 IDE (rev c3)
> 00:06.0 Multimedia audio controller: ALi Corporation M5451 PCI AC-Link 
> Controller Audio Device (rev 01)
> 00:07.0 ISA bridge: ALi Corporation M1533/M1535 PCI to ISA Bridge [Aladdin 
> IV/V/V+]
> 00:08.0 Bridge: ALi Corporation M7101 Power Management Controller [PMU]
> 00:0a.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] 
> (rev 08)
> 00:10.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller 
> (rev 01)
> 00:11.0 CardBus bridge: Toshiba America Info Systems ToPIC100 PCI to Cardbus 
> Bridge with ZV Support (rev 32)
> 00:11.1 CardBus bridge: Toshiba America Info Systems ToPIC100 PCI to Cardbus 
> Bridge with ZV Support (rev 32)
> 00:12.0 System peripheral: Toshiba America Info Systems SD TypA Controller 
> (rev 03)
> 01:00.0 VGA compatible controller: Trident Microsystems CyberBlade XPAi1 (rev 
> 82)
> 
> 
> Software Environment:
> swsusp
> 
> Problem Description:
> Kernel constantly tries suspend root hub which fails on this motherboard. 
> Initially it also output messages to dmesg every second; now message is no 
> more output but as debug shows kernel still constantly tries failed attepts. 
> Workaround is to disable wakeup via sysfs; it was suggested that proper fix 
> is 
> to blacklist the drievr. As far as I an tell neccessary infrastructure is now 
> available. Problem history:
> 
> Initial submission: http://marc.info/?t=115064417300001&r=1&w=2
> Later regression: http://marc.info/?t=116353774800002&r=1&w=2
> Patch for the regression: http://marc.info/?t=116353970700001&r=1&w=2
> 
> Steps to reproduce:
> Enable USB_DEBUG and check dmesg/syslog: 
> hub 1-0:1.0: hub_suspend
> ohci_hcd 0000:00:02.0: suspend root hub
> usb usb1: usb auto-suspend
> usb usb1: usb resume
> usb usb1: finish resume
> hub 1-0:1.0: hub_resume
> ohci_hcd 0000:00:02.0: wakeup root hub
> hub 1-0:1.0: state 7 ports 3 chg 0000 evt 0000
> ohci_hcd 0000:00:02.0: auto-stop root hub
> ohci_hcd 0000:00:02.0: auto-wakeup root hub
> ohci_hcd 0000:00:02.0: auto-stop root hub
> ohci_hcd 0000:00:02.0: auto-wakeup root hub
> 
> every second
> 
> dmesg and .config attached
> 
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to