Panic during 'shutdown -p' on 5.3-RC1

[Garance A Drosihn]

At 7:04 PM -0400 10/22/04, Garance A Drosihn wrote:
>
>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.

"Nothing happens", even after multiple serial breaks.

Here's the panic message I got this time.  It is perhaps
interesting that this time I entered the 'shutdown -p' command
over an ssh connection.  On the previous panic, I had entered the
command from the serial console.

  - - - - - - -
syslogd: exiting on signal 15
Waiting (max 60 seconds) for system process `vnlru' to stop...done
Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining...3 3 2 3 2 1 0 0 0 done
No buffers busy after final sync
Uptime: 40m56s


Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x8
fault code              = supervisor read, page not present
instruction pointer     = 0x8:0xc0680cc7
stack pointer           = 0x10:0xe2281cb8
frame pointer           = 0x10:0xe2281cd8
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         = 33 (irq23: vr0)
trap number             = 12
panic: page fault
cpuid = 0
Uptime: 41m2s
  - - - - - - -

I have only seen these panics during 'shutdown -p', and I think I
always see *some* panic message from a 'shutdown -p'.

-- 
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