Ugh. Nightmare. The USB controller in AMD chipset seems to be a buggy piece of garbage that's making me tear my hair out. Every single soft reboot, without fail, it falls over totally. The only way to get it to behave itself again is to power cycle the entire machine - not just soft power off, but physically remove all power. Wish I'd gone with Intel.
Announcement
Collapse
No announcement yet.
Gigabyte GA-MA770T-UD3P
Collapse
X
-
I'm not having USB issues with a Biostar AMD 770 board. The USB performance on the SB700 probably isn't as good as some other SB's, but it's good enough for my purposes.
You might also consider an add-in PCI-e USB card.
EDIT: Oh, and have you updated the BIOS?Last edited by DanL; 18 November 2009, 10:10 PM.
-
I had a similar problem with my Gigabyte board, sometimes attached USB devices were not recognized, the problem disappeared over time, and I haven't seen it for a while. I do have this in my dmesg though:
Code:ehci_hcd 0000:00:12.2: applying AMD SB600/SB700 USB freeze workaround
Comment
-
Originally posted by StringCheesian View PostFalls over how, exactly? I'm wondering if it is anything I would notice if I were to buy that board.
Originally posted by monraaf View PostI had a similar problem with my Gigabyte board, sometimes attached USB devices were not recognized, the problem disappeared over time, and I haven't seen it for a while. I do have this in my dmesg though:
Code:ehci_hcd 0000:00:12.2: applying AMD SB600/SB700 USB freeze workaround
Comment
-
The errata from AMD still says this from the SB700 series Errata,
Transmission Errors on Packet Identifier May Cause USB? Host Controller To Reinitialize Device
Description:
When receiving a packet identifier (PID) from a USB device while performing asynchronous data transfers, the SouthBridge’s USB host controller may not compare the packet type field to its check bits if the incoming packet type decodes as a STALL handshake. If transmission errors on an incoming packet cause a different packet type field in a PID to match the encoding for a STALL handshake, the SouthBridge may relay the STALL handshake to the application layer instead of ignoring the packet.
Potential Effect on System:
USB host driver software may act on an erroneous STALL handshake and perform a device re-initialization. USB devices should respond to this re-initialization and resume normal operation after a brief delay. If a device is unable to respond correctly to the re-initialization it may disconnect from the host unexpectedly.
Suggested Workaround:
None.
Fix Planned:
Under consideration for a future release.
Comment
-
Originally posted by deanjo View PostThe errata from AMD still says this from the SB700 series Errata,
It's a long time known issue with AMD chipsets and has yet to be resolved. Hopefully they get that fixed in their SB800 series along with their AHCI issues.
There's some errata where the "EHCI Dynamic Clock Gating" feature breaks stuff on resume from S4/S5, which I suppose could be what I'm seeing.
Comment
Comment