Boot hangs on ips0: resetting adapter, this may take up to 5 minutes

[John Baldwin]

On Saturday 04 March 2006 15:07, Oleg Sharoiko wrote:
> 
> On Fri, 3 Mar 2006, John Baldwin wrote:
> 
> JB>This is good.  Btw, the patch should apply cleanly to 6.x from yesterday.
> 
> Well, I forgot to mention that in all combinations I've only checked 6.x 
> I've also tried 7.x and it also works but I've checked only one kernel 
> and I don't remember was it UP or SMP kernel.

Ok, so i386 works fine.  (Patch was just committed to RELENG_6).

> With apic system hangs at 'lo0: bpf attached' just like I've mentioned in 
> my previouse letter. But with apic disabled I got this:
> 
> ips0: <Adaptec ServeRAID Adapter> mem 
> 0xd0300000-0xd0300fff,0xd4000000-0xd7ffffff irq 11 at device 1.0 on pci3
> ips0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xd0300000
> ips0: irq allocation failed
> panic: Assertion mtx_unowned(m) failed at 
> /usr/src-HEAD-20060228-223000UTC/sys/kern/kern_mutex.c:885
> cpuid = 0
> KDB: enter: panic
> [thread pid 0 tid 0 ]
> Stopped at      kdb_enter+0x31: leave   
> db> 
> 
> Boot logs are available:
> http://rsu.ru/~os/ips/boot.amd64.no_apic.HEAD-20060228-223000UTC.txt
> http://rsu.ru/~os/ips/boot.amd64.apic.HEAD-20060228-223000UTC.txt
> 
> Can I do anything else to help investigating this issue?

Your no apic case doesn't have ACPI in the kernel, and as such the kernel
doesn't succeed in routing interrupts at all.  You really should have
ACPI on for amd64 in both cases.  Do you have a dmesg from an i386 kernel
with APIC that I can compare with the amd64 dmesg with APIC?

-- 
John Baldwin <jhb at FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org