Date: Tue, 6 Dec 2005 14:38:31 -0800 From: "Robert Faulds" <Robert.Faulds@voxify.com> To: "John Baldwin" <jhb@freebsd.org> Cc: freebsd-acpi@freebsd.org Subject: RE: Tyan Tiget S5351-i7322 hangs with ACPI (AMD64 or i386) Message-ID: <331CA3AB8A236A488C92DEC289C7D04D016425A0@Deliverance.voxify.com>
next in thread | raw e-mail | index | archive | help
> From: John Baldwin [mailto:jhb@freebsd.org] > Sent: Tuesday, December 06, 2005 12:20 PM > To: Robert Faulds > Cc: freebsd-acpi@freebsd.org > Subject: Re: Tyan Tiget S5351-i7322 hangs with ACPI (AMD64 or i386) > > > Well, option 2 does disable APIC. The acpi hint alone does not. So, it seems =20 > that you have problems if you use APIC, and don't have problems if you > disable APIC, and ACPI has no real bearing. It sounds like perhaps your BIOS > is not giving us the right information about how the interrupts are=20 > connected. Have you tried plugging the devices into mpt0 rather than mpt1 > btw? As it is, you can try to override your BIOS to set the IRQ for mpt1=20 > manually to try to figure out what IRQ it is really routed to. (If there is > a BIOS update that might also fix this problem.) I'd try IRQs 24-47 (on your > second ioapic) first. You can try an IRQ by setting this in the loader > before boot (this would use IRQ 24 for mpt1): >=20 > hw.pci3.3.INTB.irq=3D24 > Thanks. I had started doing that with no luck. Unfortunately, I'm at the latest BIOS Tyan offers and it has no provision for forcing interrupts. I had moved the disks to channel 2 because I had an older CDROM on the first (external connector) and thought it might be a conflict (SCSI3 vs SCSI1). No luck there either. At this point I believe the most efficient use of my time will be to ship these all back and get them replaced with something a bit more compliant. Thanks for all the help and advice, Robert =20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?331CA3AB8A236A488C92DEC289C7D04D016425A0>