Re: Fatal trap 12 panic in recent -current

On Tuesday 06 January 2004 16:21, John Baldwin wrote:
> On 04-Jan-2004 Michael McGoldrick wrote:
> > System was left idle for a few hours (in X, running Blender, mozilla,
> > xterms) doing nothing. System rebooted when I plugged in a umass device
> > (ipod, possibly unrelated). When it came back up, I got a backtrace, as
> > follows. FYI, sources as of Dec 30, running with Nvidia driver.
> >
> > panic: page fault
> > panic messages:
> > ---
> > Fatal trap 12: page fault while in kernel mode
> > fault virtual address   = 0x10
> > fault code              = supervisor read, page not present
> > instruction pointer     = 0x8:0xc0543343
> > stack pointer           = 0x10:0xc9f89c80
> > frame pointer           = 0x10:0xc9f89cac
> > 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         = 27 (swi8: tty:sio clock)
> > trap number             = 12
> > panic: page fault
> >
> > syncing disks, buffers remaining... 1295 1295 1295 1295 1295 1295 1295
> > 1295 129
> >  1295 1295 1295 1295 1295 1295 1295 1295 1295 1295 1295
> > giving up on 816 buffers
> > Uptime: 12h47m56s
> > Dumping 127 MB
> >  16 32 48 64 80 96 112
For what it is worth, I have started seeing this too, when my USB Zip is 
connected.  If I disconnect the drive the computer boots fine.
If the drive is connected, it panics like this somewhere in the middle of the 
boot process. (Of course only after mounting the partitions)
If I connect the drive while the system is running, I get the same panic.

I do not have access to more debug information at the moment, but will try to 
gather some tomorrow.

The system configuration is AMD XP1800+, 512Mb of RAM, KT600 chipset.
All system frequencies are appropriate and nothing is overclocked anywhere in 
the system.

-- 
Erik H. Bakke