panic on 6.4-R in ioapic_get_vector() during device probe

[John Baldwin]

On Thursday 18 June 2009 10:05:14 am pluknet wrote:
> 2009/6/18 John Baldwin <jhb at freebsd.org>:
> > On Wednesday 17 June 2009 8:13:31 am pluknet wrote:
> >> Hi.
> >>
> >> This is on 6.4-RELEASE-p5
> >>
> >> Early in boot (probably due to network outage)::
> >> Hit [Enter] to boot immediately, or any other key for command prompt.
> >> Booting [/boot/kernel/kernel]...
> >> /boot/kernel/acpi.ko text*0x44f40 |
> >> readin failed
> >>
> >> elf32*loadimage: read failed
> >> GDB: no debug ports present
> >>
> >> and then..
> >>
> >>
> >> Timecounter "i8254" frequency 1193182 Hz quality 0
> >> CPU: Intel(R) Xeon(R) CPU           E5440  @ 2.83GHz (2826.26-MHz 
686-class
> > CPU)
> >>   Origin = "GenuineIntel"  Id = 0x1067a  Stepping = 10
> >>
> > 
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C
> >> MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
> >>
> > 
Features2=0x40ce3bd<SSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA
> >> ,<b19>,<b26>>
> >>   AMD Features=0x20000000<LM>
> >>   AMD Features2=0x1<LAHF>
> >>   Cores per package: 4
> >> real memory  = 3220992000 (3071 MB)
> >> avail memory = 3150835712 (3004 MB)
> >> FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
> >>  cpu0 (BSP): APIC ID:  0
> >>  cpu1 (AP): APIC ID:  1
> >>  cpu2 (AP): APIC ID:  2
> >>  cpu3 (AP): APIC ID:  3
> >>  cpu4 (AP): APIC ID:  4
> >>  cpu5 (AP): APIC ID:  5
> >>  cpu6 (AP): APIC ID:  6
> >>  cpu7 (AP): APIC ID:  7
> >> user VMEM accounting on
> >> ioapic0: Assuming intbase of 0
> >> MPTable: Ignoring interrupt entry for missing ioapic0
> >> ioapic0 <Version 2.0> irqs 0-23 on motherboard
> >
> > The 'ignoring interrupt entry' message is very odd.  Can you get output
> > from 'mptable'?
> 
> I'm afraid that panic was only once and due to acpi.ko network load problem.
> I can boot this box with acpi opted out explicitly  if it makes sense,
> also in order to reproduce those conditions.

Ah, ok.  Your MP Table is just plain busted so you will get this panic if you 
boot with ACPI disabled.  You can just compile ACPI into your kernel to 
ensure you never boot without it.

-- 
John Baldwin