Thanks Alan: FYI, the last log message i sent you is with CONFIG_USB_DEBUG turned on ! I used "ehci_dbg" macro (or whatever else), but the messages were not showing up even with CONFIG_USB_DEBUG set. So I had to use "printk" instead. Any explaination for this?
lei ----- Original Message ----- From: "Alan Stern" <[EMAIL PROTECTED]> To: "Lei Sun" <[EMAIL PROTECTED]> Cc: <Linux-usb-users@lists.sourceforge.net> Sent: Thursday, March 15, 2007 11:07 AM Subject: Re: [Linux-usb-users] problem with EHCI controller > On Wed, 14 Mar 2007, Lei Sun wrote: > >> Here is the log with more debug messages. > > But you didn't have CONFIG_USB_DEBUG turned on! Well, never mind. > >> in ehci_hub_status_data() , both ports status are 0x1000, and VBUS power >> is >> still off. > > On the contrary, 0x1000 means that VBUS power is on. Or at least, that's > what it is supposed to mean. If the power really is off, then your host > controller isn't working right. That could be the reason for your > problem. > >> for another different flash drive , in ehci_irq() the status read is >> 0x1002 >> . > > That's not necessarily wrong, but 0x1802 would be better. > >> Thanks! >> lei >> >> ehci_hcd: block sizes: qh 128 qtd 96 itd 192 sitd 96 >> PCI: enabling device 0000:00:0d.2 (0140 -> 0142) >> PCI: Enabling bus mastering for device 0000:00:0d.2 >> ehci_hcd 0000:00:0d.2: EHCI Host Controller >> ehci_hcd 0000:00:0d.2: new USB bus registered, assigned bus number 1 >> PCI: Enabling Mem-Wr-Inval for device 0000:00:0d.2 >> ehci_hcd 0000:00:0d.2: irq 28, io mem 0x4b002000 >> ehci_hcd 0000:00:0d.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 >> usb usb1: Product: EHCI Host Controller >> usb usb1: Manufacturer: Linux 2.6.17.8 ehci_hcd >> usb usb1: SerialNumber: 0000:00:0d.2 >> usb usb1: uevent >> usb usb1: configuration #1 chosen from 1 choice >> usb 1-0:1.0: uevent >> hub 1-0:1.0: USB hub found >> hub 1-0:1.0: 2 ports detected >> <5>ehci_irq: status=0x00000004 addr=0x4b002024 >> PCD deteted, i=2 >> command=10009 >> status=0 reset_done=0 >> status=1803 reset_done=0 > > Okay, 0x1803 is good. > >> ohci_hcd: block sizes: ed 64 td 64 >> PCI: enabling device 0000:00:0d.0 (0140 -> 0142) >> PCI: Enabling bus mastering for device 0000:00:0d.0 >> ohci_hcd 0000:00:0d.0: OHCI Host Controller >> ohci_hcd 0000:00:0d.0: new USB bus registered, assigned bus number 2 >> ohci_hcd 0000:00:0d.0: irq 28, io mem 0x4b000000 >> ehci_hub_status_data: ports 0: status=0x1000 >> ehci_hub_status_data: ports 1: status=0x1000 > > 0x1000 is bad. The status should still be 0x1803. If the VBUS power was > off, it could explain this error. > > Alan Stern > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
