Date: Mon, 5 May 2008 20:52:29 +0200 From: David Naylor <naylor.b.david@gmail.com> To: "Alexander Sack" <pisymbol@gmail.com> Cc: freebsd-current@freebsd.org, freebsd-questions@freebsd.org Subject: Re: ATA and APIC IRQ conflict Message-ID: <200805052052.34147.naylor.b.david@gmail.com> In-Reply-To: <3c0b01820805031617i4dc19c92tf65c8a167b881172@mail.gmail.com> References: <200805031525.07086.naylor.b.david@gmail.com> <3c0b01820805031617i4dc19c92tf65c8a167b881172@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart12739952.ZLan05Ci3H Content-Type: multipart/mixed; boundary="Boundary-01=_ud1HIfsuz1Svlrj" Content-Transfer-Encoding: 7bit Content-Disposition: inline --Boundary-01=_ud1HIfsuz1Svlrj Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 04 May 2008 01:17:16 you wrote: > David: > > On Sat, May 3, 2008 at 9:25 AM, David Naylor <naylor.b.david@gmail.com>=20 wrote: > > I am trying to install FreeBSD on a gigabyte board (based on nForce 65= 0i > > chipset (with MCP51 controller)) however no SATA hard drives are > > detected. However, if APIC is disabled then I have access to the hard > > drives (and only one CPU). It has been suggested that it is an IRQ > > conflict (or something else related to APIC). > > I'll bet its interrupt routing more than IRQ conflicts (which these > days on a modern system really doesn't make sense). More than likely > there is some funkiness going on with the BIOS's ACPI tables (I would > start with the MADT and verify its entries look kosher). Considering that the system works with APIC disabled I think you are right.= I=20 am learning on the fly here, sorry. There does not appear to be any BIOS options except for the suspend state,= =20 currently set to S1? (And a few power-on options, all disabled) > Though it could be a power management problem and have nothing to do > with interrupts (though with the SATA hard drives not being detected I > would guess its interrupts). Both linux and windows vista run on this system without a problem... Except= =20 when I reboot from FreeBSD then windows BSOD's and linux keeps resetting at= a=20 (without ever actually booting). After having run FreeBSD I need to do a=20 system power down (not just a reboot) then the problem disappears. =20 Also even with APIC disabled FreeBSD fails to detect my second CD ROM drive= =20 (both are IDE) and it fails to read the first one. =20 > > Could someone please point me in the right direction so that I could t= ry > > fix this problem (i.e. how to change the IRQ of the ATA drivers or where > > to fiddle with APIC to try get it to work?) > > I would read this: > > http://www.freebsd.org/doc/en/books/handbook/acpi-debug.html Done quickly... Thanks for the pointer. =20 > I would definitely set ACPI_DEBUG=3D1 and go from there. Perhaps if you > can start dumping the AML on your system (acpidump) and any messages > you get on the console (dmesg etc.) you can post them here. Also let > us know what kind of BIOS options you have revolving ACPI, power > management, and any legacy settings (e.g. MPS Table options if any). Please see attached for the information (if anyone can't access them please= =20 e-mail me and I'll send you a copy) If you really need the dmesg with APIC enabled please let me know (it is no= t=20 easy since neither hard drives or cd drives are working but I think I have = a=20 plan... :-) In loader.conf: hint.apic.0.disabled=3D1 debug.acpi.layer=3D"ACPI_ALL_COMPONENTS ACPI_ALL_DRIVERS" debug.acpi.level=3D"ACPI_LV_ERROR ACPI_LV_WARN" And sysctl hw.acpi: hw.acpi.supported_sleep_state: S1 S4 S5 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: NONE hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 1 hw.acpi.s4bios: 0 hw.acpi.verbose: 1 hw.acpi.disable_on_reboot: 0 hw.acpi.handle_reboot: 0 hw.acpi.reset_video: 0 hw.acpi.cpu.cx_lowest: C1 > Without more information its hard to say what exactly is your problem > other than disabling ACPI kinda fixes it. > > Also, PLEASE CHECK GIGABYTE's motherboard web page for any BIOS > updates that have been released. Typically BIOS updates fix these > kinds of problems. I doubt it is a BIOS specific problem since this is the second board (first= =20 one was from Asus) that has this problem. Just to be safe I flashed the BI= OS=20 to the latest one, no luck :-( Thank you for your help. =20 David P.S. I think this is better suited for currect@? So I have CC'ed that mail= ing=20 list. =20 --Boundary-01=_ud1HIfsuz1Svlrj-- --nextPart12739952.ZLan05Ci3H Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBIH1dyUaaFgP9pFrIRAmMDAJ92QPm+ptOAYsBuLl8/JZM+o3zzQgCgg+Ps rK7KM6VQiA/bqK2pZL3vdoA= =/1j3 -----END PGP SIGNATURE----- --nextPart12739952.ZLan05Ci3H--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200805052052.34147.naylor.b.david>