Bug 118973

Summary: [acpi]: Kernel panic with acpi boot
Product: Base System Reporter: Gabor Molnar <mggabro>
Component: kernAssignee: freebsd-acpi (Nobody) <acpi>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 7.0-BETA4   
Hardware: Any   
OS: Any   

Description Gabor Molnar 2007-12-23 17:20:01 UTC 
Kernel panic if I booting the GENERIC kernel with ACPI.

Here is a picture:
http://195.228.66.5/pic/panic.jpg (Sorry, not good quality, create with mobile phone)

and my Dmesg with no-ACPI kernel:

Copyright (c) 1992-2007 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 is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.0-BETA4 #0: Sun Dec  2 19:19:04 UTC 2007
    root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 5600+ (2814.44-MHz 686-class CPU)
  Origin = "AuthenticAMD"  Id = 0x40f33  Stepping = 3
  Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
  Features2=0x2001<SSE3,CX16>
  AMD Features=0xea500800<SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow!>
  AMD Features2=0x1f<LAHF,CMP,SVM,ExtAPIC,CR8>
  Cores per package: 2
real memory  = 2147418112 (2047 MB)
avail memory = 2091892736 (1994 MB)
MPTable: <OEM00000 PROD00000000>
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
ioapic0: Changing APIC ID to 2
ioapic0: Assuming intbase of 0
ioapic0 <Version 1.1> irqs 0-23 on motherboard
kbd1 at kbdmux0
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
cpu0 on motherboard
powernow0: <PowerNow! K8> on cpu0
cpu1 on motherboard
powernow1: <PowerNow! K8> on cpu1
pcib0: <MPTable Host-PCI bridge> pcibus 0 on motherboard
pci0: <PCI bus> on pcib0
pci0: <memory, RAM> at device 0.0 (no driver attached)
isab0: <PCI-ISA bridge> at device 1.0 on pci0
isa0: <ISA bus> on isab0
pci0: <serial bus, SMBus> at device 1.1 (no driver attached)
pci0: <memory, RAM> at device 1.2 (no driver attached)
ohci0: <OHCI (generic) USB controller> mem 0xfd002000-0xfd002fff irq 10 at device 2.0 on pci0
ohci0: [GIANT-LOCKED]
ohci0: [ITHREAD]
usb0: OHCI version 1.0, legacy support
usb0: <OHCI (generic) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: <nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
uhub0: 10 ports with 10 removable, self powered
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xfd003000-0xfd0030ff irq 11 at device 2.1 on pci0
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb1: EHCI version 1.0
usb1: companion controller, 10 ports each: usb0
usb1: <EHCI (generic) USB 2.0 controller> on ehci0
usb1: USB revision 2.0
uhub1: <nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb1
uhub1: 10 ports with 10 removable, self powered
atapci0: <nVidia nForce MCP55 UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 4.0 on pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci0
ata1: [ITHREAD]
atapci1: <nVidia nForce MCP55 SATA300 controller> port 0xa000-0xa007,0xa400-0xa403,0xa800-0xa807,0xac00-0xac03,0xb000-0xb00f mem 0xfd004000-0xfd004fff irq 15 at device 5.0 on pci0
atapci1: [ITHREAD]
ata2: <ATA channel 0> on atapci1
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci1
ata3: [ITHREAD]
atapci2: <nVidia nForce MCP55 SATA300 controller> port 0xb400-0xb407,0xb800-0xb803,0xbc00-0xbc07,0xc000-0xc003,0xc400-0xc40f mem 0xfd000000-0xfd000fff irq 10 at device 5.1 on pci0
atapci2: [ITHREAD]
ata4: <ATA channel 0> on atapci2
ata4: [ITHREAD]
ata5: <ATA channel 1> on atapci2
ata5: [ITHREAD]
atapci3: <nVidia nForce MCP55 SATA300 controller> port 0xc800-0xc807,0xcc00-0xcc03,0xd000-0xd007,0xd400-0xd403,0xd800-0xd80f mem 0xfd001000-0xfd001fff irq 11 at device 5.2 on pci0
atapci3: [ITHREAD]
ata6: <ATA channel 0> on atapci3
ata6: [ITHREAD]
ata7: <ATA channel 1> on atapci3
ata7: [ITHREAD]
pcib1: <MPTable PCI-PCI bridge> at device 6.0 on pci0
pci1: <PCI bus> on pcib1
pci1: <multimedia, audio> at device 7.0 (no driver attached)
pci1: <input device> at device 7.1 (no driver attached)
fwohci0: <1394 Open Host Controller Interface> mem 0xfc005000-0xfc0057ff,0xfc000000-0xfc003fff irq 5 at device 7.2 on pci1
fwohci0: [FILTER]
fwohci0: OHCI version 1.10 (ROM=0)
fwohci0: No. of Isochronous channels is 4.
fwohci0: EUI64 00:02:3c:00:91:04:90:c3
fwohci0: Phy 1394a available S400, 2 ports.
fwohci0: Link S400, max_rec 2048 bytes.
firewire0: <IEEE1394(FireWire) bus> on fwohci0
dcons_crom0: <dcons configuration ROM> on firewire0
dcons_crom0: bus_addr 0x138c000
fwe0: <Ethernet over FireWire> on firewire0
if_fwe0: Fake Ethernet address: 02:02:3c:04:90:c3
fwe0: Ethernet address: 02:02:3c:04:90:c3
fwip0: <IP over FireWire> on firewire0
fwip0: Firewire address: 00:02:3c:00:91:04:90:c3 @ 0xfffe00000000, S400, maxrec 2048
sbp0: <SBP-2/SCSI over FireWire> on firewire0
fwohci0: Initiate bus reset
fwohci0: BUS reset
fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode
xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0x8800-0x887f mem 0xfc004000-0xfc00407f irq 5 at device 8.0 on pci1
miibus0: <MII bus> on xl0
ukphy0: <Generic IEEE 802.3u media interface> PHY 24 on miibus0
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
xl0: Ethernet address: 00:0a:5e:64:db:9e
xl0: [ITHREAD]
pcib2: <MPTable PCI-PCI bridge> at device 15.0 on pci0
pci2: <PCI bus> on pcib2
vgapci0: <VGA-compatible display> port 0x9000-0x907f mem 0xf8000000-0xf8ffffff,0xe0000000-0xefffffff,0xf9000000-0xf9ffffff irq 7 at device 0.0 on pci2
pmtimer0 on isa0
orm0: <ISA Option ROM> at iomem 0xd0000-0xd07ff pnpid ORM0000 on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: [ITHREAD]
psm0: model IntelliMouse, device ID 3
ppc0: parallel port not found.
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 8250 or not responding
sio0: [FILTER]
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
unknown: <PNP0303> can't assign resources (port)
unknown: <PNP0c01> can't assign resources (memory)
unknown: <PNP0f13> can't assign resources (irq)
Timecounters tick every 1.000 msec
firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me)
firewire0: bus manager 0 (me)
acd0: DVDR <PIONEER DVD-RW DVR-111D/1.23> at ata0-master UDMA66
ad1: 76318MB <SAMSUNG SP0842N BH100-50> at ata0-slave UDMA100
SMP: AP CPU #1 Launched!
Trying to mount root from ufs:/dev/ad1s1a 

Sorry for my english, but I hope, you understand me.

How-To-Repeat: Boot with ACPI GENERIC kernel.
Comment 1 Remko Lodder freebsd_committer freebsd_triage 2007-12-23 17:21:06 UTC 
Responsible Changed
From-To: freebsd-i386->freebsd-acpi

reassign to acpi group
Comment 2 Rui Paulo 2007-12-23 18:02:45 UTC 
At Sun, 23 Dec 2007 17:13:12 GMT,
Gabor Molnar wrote:
> 
> 
> >Number:         118973
> >Category:       i386
> >Synopsis:       Kernel panic with acpi boot
> >Confidential:   no
> >Severity:       critical
> >Priority:       low
> >Responsible:    freebsd-i386
> >State:          open
> >Quarter:        
> >Keywords:       
> >Date-Required:
> >Class:          sw-bug
> >Submitter-Id:   current-users
> >Arrival-Date:   Sun Dec 23 17:20:01 UTC 2007
> >Closed-Date:
> >Last-Modified:
> >Originator:     Gabor Molnar
> >Release:        7.0-BETA4
> >Organization:
> >Environment:
> >Description:
> Kernel panic if I booting the GENERIC kernel with ACPI.
> 
> Here is a picture:
> http://195.228.66.5/pic/panic.jpg (Sorry, not good quality, create
> with mobile phone)

This seems to be a problem with the acpi_hpet driver.
Could you please try booting with "hint.acpi_hpet.0.disabled=1" ? This
way, you should be able to boot with ACPI enabled.
Escape to the boot loader prompt and type:
setenv hint.acpi_hpet.0.disabled=1

I believe your hardware must have some problem that's causing a
divide-by-zero trap. If possible, could you please provide us a
backtrace from where the panic has originated?


See
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/acpi-debug.html

--
Rui Paulo
Comment 3 Andriy Gapon freebsd_committer freebsd_triage 2010-12-05 14:49:50 UTC 
State Changed
From-To: open->closed

Feedback timeout.