[Bug 243401] [patch] ahci driver problems with Marvell 88SE9230 (Dell BOSS-S1)
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Fri Jan 1 22:06:00 UTC 2021
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243401
--- Comment #6 from Peter Eriksson <pen at lysator.liu.se> ---
Yes, I've since changed my patch a bit so that it:
Only sets the timeout to 5000 (from 1000) if:
1) quirk AHCI_Q_SLOWDEV (a new one) is set - only set on the Marvell 88SE9230
2) only does this _after_ the first status change occurs (0x0000000 ->
0x00000001)
Now the trace looks something like this (some more debugging prints added):
ahcich14: AHCI reset...
ahcich14: AHCI engine: stopping
ahcich14: stopping AHCI engine: ci: -1 -> 0 at time 10us
ahcich14: stopping AHCI engine: sact: -1 -> 0 at time 10us
ahcich14: stopping AHCI engine: ccs: -1 -> 0 at time 10us
ahcich14: stopping AHCI engine: cr: -1 -> 0 at time 10us
ahcich14: AHCI engine stopped at time 10us
ahcich14: SATA changed status 0x00000000 -> 0x00000001 at time=100us
ahcich14: SATA changed status 0x00000001 -> 0x00000133 at time=212500us
ahcich14: SATA connect status 0x00000133 at time=212500us
ahcich14: AHCI reset: device found
ahcich14: AHCI reset: device ready after 0ms
ahcich14: AHCI engine(fbs=1): starting
ahcich15: AHCI reset...
ahcich15: AHCI engine: stopping
ahcich15: stopping AHCI engine: ci: -1 -> 0 at time 10us
ahcich15: stopping AHCI engine: sact: -1 -> 0 at time 10us
ahcich15: stopping AHCI engine: ccs: -1 -> 0 at time 10us
ahcich15: stopping AHCI engine: cr: -1 -> 0 at time 10us
ahcich15: AHCI engine stopped at time 10us
ahcich15: SATA changed status 0x00000000 -> 0x00000001 at time=100us
ahcich15: SATA changed status 0x00000001 -> 0x00000133 at time=221400us
ahcich15: SATA connect status 0x00000133 at time=221400us
ahcich15: AHCI reset: device found
ahcich15: AHCI reset: device ready after 0ms
ahcich15: AHCI engine(fbs=1): starting
ahcich16: AHCI reset...
ahcich16: AHCI engine: stopping
ahcich16: stopping AHCI engine: ci: -1 -> 0 at time 10us
ahcich16: stopping AHCI engine: sact: -1 -> 0 at time 10us
ahcich16: stopping AHCI engine: ccs: -1 -> 0 at time 10us
ahcich16: stopping AHCI engine: cr: -1 -> 0 at time 10us
ahcich16: AHCI engine stopped at time 10us
ahcich16: SATA changed status 0x00000000 -> 0x00000113 at time=100us
ahcich16: SATA connect status 0x00000113 at time=100us
ahcich16: AHCI reset: device found
ahcich16: AHCI reset: device ready after 0ms
ahcich16: AHCI engine(fbs=1): starting
Btw,
I've been testing some different variants of settings for this controller - for
example I removed the quirk (ALTSIG) to see if that would make any difference
but it doesn't seem to matter if it's set or not. Anyone know where that quirk
comes from?
I'll upload a cleaned up version of an improved patch soon.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list