Date: Fri, 8 Jul 2005 10:06:42 -0400 From: John Baldwin <jhb@FreeBSD.org> To: Mike Tancsa <mike@sentex.net> Cc: freebsd-current@FreeBSD.org Subject: Re: 6.0-CURRENT SNAP004 hangs on amr Message-ID: <200507081006.43609.jhb@FreeBSD.org> In-Reply-To: <6.2.1.2.0.20050707220038.08329918@64.7.153.2> References: <70e8236f05070208212e36c375@mail.gmail.com> <200507071658.27361.jhb@FreeBSD.org> <6.2.1.2.0.20050707220038.08329918@64.7.153.2>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 07 July 2005 10:09 pm, Mike Tancsa wrote: > At 04:58 PM 07/07/2005, John Baldwin wrote: > >Crud, it's off in the weeds. :( Can you do a boot -v and get the lines > > after 'pcib3:'? > > Here you go Ok, I see why it is badly confused in the non-APIC and non-ACPI case though I don't know why it is panicing. (FWIW, it is trying to route all interrupts to IRQ 14 because your $PIR is all busted *sigh*). BIOS writers suck. Anyway, I still need a simple matrix of what works and what doesn't work first (if I got one earlier I lost it): ACPI/APIC - amr0 gets no interrupts, hangs after boot ACPI/no-APIC - amr0 gets no interrupts, hangs after boot? no-ACPI/APIC - ??? no-ACPI/no-APIC - busted $PIR causes the code to go off into the weeds Is that summary more or less correct? Can you test the missing case? Also, is there any difference between 5.4 and 6.0 in this table? -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200507081006.43609.jhb>