Bug Report kern/98694 (please help)

[John Baldwin]

On Friday 09 June 2006 10:42, Lars Köller wrote:
> ----------
> 
> Hi John,
> 
> thanks for your help!
> 
> In reply to John Baldwin who wrote:
>  
> > > Sophos only supports FBSD 5 now, so we have no posibility to play around
> > > with 6.1.
> > > 
> > > It would be very nice if someone could give us som support, to fix the 
> > problem.
> > > 
> > > Many thanks and best regards
> > 
> > The clock handling changes in 6 that would fix your problem are too big to 
> > backport to 5.x I'm afraid.  I can look at your panic in the non-ACPI case 
if 
> 
> O.k. as stated above, it's not an option for us cause of the sophos 
> support. No hotfix possible? ;-)

No, not really.  You'd be much better off using compat5x on 6.1 to run sophos.

> > you can capture a dmesg with ACPI disabled (including the panic messages) 
> > over a serial console.
> 
> No problem comming soon ......
> 
> Copyright (c) 1992-2006 The FreeBSD Project.                                    
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
>         The Regents of the University of California. All rights reserved.
> FreeBSD 5.5-RELEASE-p1 #3: Tue Jun  6 15:52:17 CEST 2006
>     root at pmx2.hrz.uni-bielefeld.de:/opt/tmp/obj/usr/src/sys/PMX
> Timecounter "i8254" frequency 1193182 Hz quality 0
> CPU: Intel(R) Xeon(TM) CPU 2.40GHz (2400.10-MHz 686-class CPU)
>   Origin = "GenuineIntel"  Id = 0xf27  Stepping = 7
>   
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>
>   Hyperthreading: 2 logical CPUs
> real memory  = 2147483648 (2048 MB)
> avail memory = 2095943680 (1998 MB)
> MPTable: <FSCD1409 PRIMERGY    >
> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
>  cpu0 (BSP): APIC ID:  6
>  cpu1 (AP): APIC ID:  0
> ioapic0: Assuming intbase of 0
> ioapic1: Assuming intbase of 16
> ioapic0 <Version 1.1> irqs 0-15 on motherboard
> ioapic1 <Version 1.1> irqs 16-31 on motherboard
> npx0: <math processor> on motherboard
> npx0: INT 16 interface
> cpu0 on motherboard
> cpu1 on motherboard
> pcib0: <MPTable Host-PCI bridge> pcibus 0 on motherboard
> pci0: <PCI bus> on pcib0
> pci0: <display, VGA> at device 4.0 (no driver attached)
> atapci0: <ServerWorks CSB6 UDMA100 controller> port 
0x1400-0x140f,0x376,0x170-0x
> 177,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0
> ata0: channel #0 on atapci0
> ata1: channel #1 on atapci0
> ohci0: <OHCI (generic) USB controller> mem 0xf8021000-0xf8021fff irq 9 at 
device
>  15.2 on pci0
> usb0: OHCI version 1.0, legacy support
> usb0: SMM does not respond, resetting
> usb0: <OHCI (generic) USB controller> on ohci0
> usb0: USB revision 1.0
> uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> uhub0: 4 ports with 4 removable, self powered
> isab0: <PCI-ISA bridge> at device 15.3 on pci0
> isa0: <ISA bus> on isab0
> pcib3: <MPTable Host-PCI bridge> pcibus 3 on motherboard
> pci3: <PCI bus> on pcib3
> asr0: <Adaptec Caching SCSI RAID> mem 
0xfc000000-0xfdffffff,0xfb000000-0xfbfffff
> f,0xfa500000-0xfa5fffff irq 24 at device 8.0 on pci3
> asr0: ADAPTEC 2010S FW Rev. FS11, 2 channel, 256 CCBs, Protocol I2O
> pcib4: <ServerWorks host to PCI bridge(unknown chipset)> pcibus 4 on 
motherboard
> pir0: <PCI Interrupt Routing Table: 16 Entries> on motherboard
> $PIR: BIOS IRQ 24 for 3.8.INTA is not valid for link 0x18
> pci4: <PCI bus> on pcib4
> 
> 
> Fatal trap 9: general protection fault while in kernel mode
> cpuid = 0; apic id = 06
> instruction pointer     = 0x58:0x3a73
> stack pointer           = 0x10:0xeda
> frame pointer           = 0x10:0xf16
> code segment            = base 0xc00f0000, limit 0xffff, type 0x1b
>                         = DPL 0, pres 1, def32 0, gran 0
> processor eflags        = interrupt enabled, resume, IOPL = 0
> current process         = 0 (swapper)
> trap number             = 9
> panic: general protection fault
> cpuid = 0
> Uptime: 1s
> Automatic reboot in 15 seconds - press a key on the console to abort
> 
> 
> Have a nice weekend

Hmm, this is a panic inside your BIOS. :(  Generally these are rather hard to 
debug.

-- 
John Baldwin