Panic during 'shutdown -p' on 5.3-RC1

From: Garance A Drosihn <drosih_at_rpi.edu>
Date: Fri, 22 Oct 2004 19:04:01 -0400
At 1:33 PM -0600 10/22/04, Scott Long wrote:
>Garance A Drosihn wrote:
>>
>>Would this problem cause any panics during 'shutdown -p' processing?
>>I just loaded up a brand new machine with 5.3-RC1, and it works fine
>>except that it almost always panics when I do a 'shutdown -p'.  I
>>just finished building a new world to make sure I have all the
>>latest changes, but I haven't installed that yet.  Should I rebuild
>>the kernel with this change included?
>
>I would tend to suspect ACPI here.  Do you have kind of DDB info
>from the panic?

Okay, I just rebuilt it with all the latest updates from RELENG_5_3 ,
and here is a panic message from 'shutdown -p now':

  - - - - - - -
System shutdown time has arrived
Stopping inetd.
Shutting down daemon processes: thttpd

Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x1c
fault code              = supervisor write, page not present
instruction pointer     = 0x8:0xc057dbbf
stack pointer           = 0x10:0xe3d08784
frame pointer           = 0x10:0xe3d08790
code segment            = base 0x0, limit 0xfffff, type 0x1b
                         = DPL 0, pres 1, def32 1, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 278 (syslogd)
trap number             = 12
panic: page fault
cpuid = 0
Uptime: 2m30s
  - - - - - - -

There is a long pause after the "down daemon processes: thttpd"
line, and nothing else is printed on either the serial console
or the main console.  This situation could be a problem, because
the machine is left running.  The reason I'm doing the shutdown
is because my office is getting too warm, and I really want the
machine to be *off* after the powerdown request.

I don't know if there is anything more I can do (wrt debugging),
given that the system has mostly shut down at that point.  I'll
try it again and see what happens if I send it a serial break.
I should also note that it does not always die with current
process=(syslogd).  I know one time it was listed as something
like "(irq23: vr0)".  vr0 is the ethernet interface which is
actually hooked up and configured.

Here is /var/run/dmesg.boot :
  - - - - - - -
Copyright (c) 1992-2004 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.3-RC1 #2: Fri Oct 22 16:48:29 EDT 2004
     root_at_santropez.netel.rpi.edu:/usr/obj/usr/src/sys/Athlon3k-5x
ACPI APIC Table: <KM400  AWRDACPI>
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) XP 3000+ (2166.44-MHz 686-class CPU)
   Origin = "AuthenticAMD"  Id = 0x6a0  Stepping = 0
 
Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
   AMD Features=0xc0400000<AMIE,DSP,3DNow!>
real memory  = 1006567424 (959 MB)
avail memory = 975495168 (930 MB)
ioapic0 <Version 0.3> irqs 0-23 on motherboard
npx0: [FAST]
npx0: <math processor> on motherboard
npx0: INT 16 interface
acpi0: <KM400 AWRDACPI> on motherboard
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0
cpu0: <ACPI CPU> on acpi0
acpi_tz0: <Thermal Zone> on acpi0
acpi_button0: <Power Button> on acpi0
acpi_button1: <Sleep Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
agp0: <VIA Generic host to PCI bridge> mem 0xe0000000-0xe7ffffff at 
device 0.0 on pci0
pcib1: <PCI-PCI bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
pci1: <display, VGA> at device 0.0 (no driver attached)
atapci0: <SiI 3112 SATA150 controller> port 
0xd400-0xd40f,0xd300-0xd303,0xd200-0xd207,0xd100-0xd103,0xd000-0xd007 
mem 0xee083000-0xee0831ff irq 16 at device 5.0 on pci0
ata2: channel #0 on atapci0
ata3: channel #1 on atapci0
rl0: <RealTek 8139 10/100BaseTX> port 0xd500-0xd5ff mem 
0xee080000-0xee0800ff irq 18 at device 7.0 on pci0
miibus0: <MII bus> on rl0
rlphy0: <RealTek internal media interface> on miibus0
rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
rl0: Ethernet address: 00:50:22:e3:db:67
atapci1: <VIA 6420 SATA150 controller> port 
0xdb00-0xdbff,0xda00-0xda0f,0xd900-0xd903,0xd800-0xd807,0xd700-0xd703,0xd600-0xd607 
irq 20 at device 15.0 on pci0
ata4: channel #0 on atapci1
ata5: channel #1 on atapci1
atapci2: <VIA 8237 UDMA133 controller> port 
0xdc00-0xdc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 15.1 on 
pci0
ata0: channel #0 on atapci2
ata1: channel #1 on atapci2
uhci0: <VIA 83C572 USB controller> port 0xdd00-0xdd1f irq 21 at 
device 16.0 on pci0
uhci0: [GIANT-LOCKED]
usb0: <VIA 83C572 USB controller> on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: <VIA 83C572 USB controller> port 0xde00-0xde1f irq 21 at 
device 16.1 on pci0
uhci1: [GIANT-LOCKED]
usb1: <VIA 83C572 USB controller> on uhci1
usb1: USB revision 1.0
uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2: <VIA 83C572 USB controller> port 0xdf00-0xdf1f irq 21 at 
device 16.2 on pci0
uhci2: [GIANT-LOCKED]
usb2: <VIA 83C572 USB controller> on uhci2
usb2: USB revision 1.0
uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhci3: <VIA 83C572 USB controller> port 0xe000-0xe01f irq 21 at 
device 16.3 on pci0
uhci3: [GIANT-LOCKED]
usb3: <VIA 83C572 USB controller> on uhci3
usb3: USB revision 1.0
uhub3: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
pci0: <serial bus, USB> at device 16.4 (no driver attached)
isab0: <PCI-ISA bridge> at device 17.0 on pci0
isa0: <ISA bus> on isab0
pci0: <multimedia, audio> at device 17.5 (no driver attached)
vr0: <VIA VT6102 Rhine II 10/100BaseTX> port 0xe200-0xe2ff mem 
0xee082000-0xee0820ff irq 23 at device 18.0 on pci0
miibus1: <MII bus> on vr0
ukphy0: <Generic IEEE 802.3u media interface> on miibus1
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
vr0: Ethernet address: 00:11:09:31:80:67
fdc0: <floppy drive controller> port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0
fdc0: [FAST]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x30 on acpi0
sio0: type 16550A, console
sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
ppc0: <ECP parallel printer port> port 0x778-0x77b,0x378-0x37f irq 7 
drq 3 on acpi0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/9 bytes threshold
ppbus0: <Parallel port bus> on ppc0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
atkbdc0: <Keyboard controller (i8042)> port 0x64,0x60 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: model Generic PS/2 mouse, device ID 0
pmtimer0 on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x100>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounter "TSC" frequency 2166436961 Hz quality 800
Timecounters tick every 10.000 msec
acd0: CDRW <AOPEN COM5232/AAH/1.06> at ata0-master UDMA33
ad4: 114473MB <WDC WD1200JD-00GBB0/02.05D02> [232581/16/63] at 
ata2-master SATA150
Mounting root from ufs:/dev/ad4s2a

-- 
Garance Alistair Drosehn            =   gad_at_gilead.netel.rpi.edu
Senior Systems Programmer           or  gad_at_freebsd.org
Rensselaer Polytechnic Institute    or  drosih_at_rpi.edu
Received on Fri Oct 22 2004 - 21:04:04 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:19 UTC