Matthew Dillon wrote: > :Alexander Polakov <[email protected]> added the comment: > : > :I changed value to 1000 on line 143 and added ahci_os_sleep(1000) before re= > :turn=20 > :in ahci_init. Still panics. > > Rumko is now getting a panic with a AHCI1.0 Intel chipset with the > changes that he was NOT getting before the changes. > > The results are very similar to what you got... what appears to be > random memory corruption and in Rumko's case an immediate machine > reboot and the BIOS configuration got messed up as well. > > I feel they must be related issues. If Rumko and I can figure out > which change caused his machine to stop booting it may give me a > good idea where to look for the problem you are reporting. > > What is really annoying to me is that the NATA driver is able to > attach with its AHCI sub-driver. I don't know what I am doing > different that is causing the breakage.
Perhaps your "if intel but AHCI is not enabled then write some value to
a particular config register" change. I'm thinking there's more work to
do to kick the chip into AHCI mode and not confuse the BIOS; besides
that, I think it's not clean. If the device doesn't advertise itself as
being an AHCI subclass, then don't try to force it.
Cheers,
--
Thomas E. Spanjaard
[email protected]
[email protected]
signature.asc
Description: OpenPGP digital signature
