-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
David Brownell wrote: | On Monday 03 January 2005 5:05 pm, you wrote: | |>David Brownell wrote: |>| It's something wierd that started a while back, and so far |>| it doesn't make sense to me. But see below, and please |>| try the patch I've attached. If it fails, please send |>| the full CONFIG_USB_DEBUG output showing the error (as |>| below) and contents of /sys/class/usb_host/usb4/registers |>| after the fault. |> |>I've tried the patch and it failed. |> |>http://www.dune.net/linux/laptop/dmesg-usbdebug-ehcipatch.gz | | | I get a 404 error when I try that ...
of course! very sorry, that's the internal host/network. the useful one is
http://arrakis.dhis.org/linux/laptop/dmesg-usbdebug-ehcipatch.gz
| | | |>the debug output is here: |> |>archon usb4 # cat registers |>bus pci, device 0000:00:1d.7 (driver 26 Oct 2004) |>EHCI 1.00, hcd state 0 |>structural params 0x00103206 |>capability params 0x00006871 |>status 1004 Halt PCD |>command 080000 (park)=0 ithresh=8 period=1024 HALT |>intrenable 00 |>uframe 0000 |>port 1 status 003030 POWER OWNER sig=se0 OCC OC |>port 2 status 003030 POWER OWNER sig=se0 OCC OC |>port 3 status 003000 POWER OWNER sig=se0 |>port 4 status 003000 POWER OWNER sig=se0 |>port 5 status 003000 POWER OWNER sig=se0 |>port 6 status 003000 POWER OWNER sig=se0 |>irq normal 0 err 0 reclaim 0 (lost 0) |>complete 0 unlink 0 |>archon usb4 # |> |>|>hub 4-0:1.0: individual port over-current protection |>|>hub 4-0:1.0: Single TT |>|>hub 4-0:1.0: TT requires at most 8 FS bit times |>|>hub 4-0:1.0: power on to power good time: 20ms |>|>hub 4-0:1.0: local power source is good |>|>hub 4-0:1.0: enabling power on all ports |>|>hub 4-0:1.0: state 5 ports 6 chg ffff evt ffff |>|>ehci_hcd 0000:00:1d.7: GetStatus port 1 status 001030 POWER sig=se0 OCC OC |>|>hub 4-0:1.0: over-current change on port 1 |>| |>| |>| Seems like a lot of people who get this error get it along with |>| an "overcurrent" error on port 1, right after the chip has been |>| initialized. |> |>These overcurrent warnings/errors also happen sometimes on windows when changing |>between battery and AC power or removing battery. Not very reproducible. |> |>| I suspect the problem comes as a side effect of something |>| else. It could be board-related, but it doesn't seem |>| to be chip-related. I've seen reports of this with |>| ALI, NEC, and Intel chips, but it doesn't happen for |>| me with ALI or NEC chips; and plenty of folk are using |>| those chips without seeing this problem. |> |>unlucky me :-( |> |>I'll try to help on anything that's needed, on my free time, of course. |> |>thanks for the help. |> |>regards, |>pedro venda. |>-- |> |>Pedro Joćo Lopes Venda |>email: [EMAIL PROTECTED] |>http://arrakis.dhis.org |> |> |>------------------------------------------------------- |>The SF.Net email is sponsored by: Beat the post-holiday blues |>Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. |>It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt |>_______________________________________________ |>linux-usb-devel@lists.sourceforge.net |>To unsubscribe, use the last form field at: |>https://lists.sourceforge.net/lists/listinfo/linux-usb-devel |>
- --
Pedro Joćo Lopes Venda email: [EMAIL PROTECTED] http://arrakis.dhis.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFB2oyzeRy7HWZxjWERAgbMAJ9pfiZGJQDe84F4cx14N4XQ6mWcEACgkWtx lfT7hAEyLThyiex+eRgWYd8= =arN1 -----END PGP SIGNATURE-----
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
