Date: Thu, 16 Dec 2010 17:40:15 GMT From: Alexander Motin <mav@FreeBSD.org> To: freebsd-amd64@FreeBSD.org Subject: Re: amd64/148526: [ahci] ahci driver does not boot on AMD chip Message-ID: <201012161740.oBGHeFLb044357@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR amd64/148526; it has been noted by GNATS. From: Alexander Motin <mav@FreeBSD.org> To: Yury <yury@gorodok.net> Cc: Andriy Gapon <avg@freebsd.org>, bug-followup@freebsd.org Subject: Re: amd64/148526: [ahci] ahci driver does not boot on AMD chip Date: Thu, 16 Dec 2010 19:39:50 +0200 On 16.12.2010 19:11, Andriy Gapon wrote: > on 09/12/2010 19:08 Yury said the following: >> Here they are, message files. >> >> The "bad" file is messages during boot try with the ahci driver, and the "good" >> one is the backed up kernel version with ata driver. In the "bad" boot try >> messages last lines could repeat infinitely. And, as I can see there are some >> 'time-out' messages in "good" variant, but everything works just fine. BIOS was >> updated to 15.06. >> >> Only differences in kernel config files are: >> >> < device ata >> < device atadisk >> --- >> > #device ata >> > #device atadisk >> >> < ##device ahci >> < device atapicd >> --- >> > device ahci >> > #device atapicd >> > > Yury, > will you be able to test ahci with this hardware using stable/8? I can see interrupt status bit set here. Timeout in that case may mean that interrupt was not delivered/handled for some reason. Could you check if this controller supports MSI interrupts with `pciconf -lvbc`? If it does and driver uses it - you may try to disable it by setting loader tunable `hint.ahci.0.msi=0'. It could also be useful to enable verbose kernel messages at boot menu. -- Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201012161740.oBGHeFLb044357>