Subject: Re: 1.3.3 crash
To: None <Havard.Eidnes@runit.sintef.no>
From: Jukka Marin <jmarin@pyy.jmp.fi>
List: port-i386
Date: 01/04/1999 16:26:34
On Mon, Jan 04, 1999 at 02:08:46PM +0100, Havard.Eidnes@runit.sintef.no wrote:
> > I upgraded our ppp/mail server to 1.3.3 and the system paniced
> > after 2 days of uptime (this system had uptimes of over 60 days
> > before):
> 
> I don't think of myself as a guru, so you're probably well advised
> to send any follow-up to this back to port-i386.  However, if I were
> to look at this I would probably need a stack backtrace.  I think
> (and hope) you can get it with gdb:
> 
> # gdb -q netbsd.1
> (gdb) target kcore netbsd.1.core
> (gdb) where
> 
> The second argument to vm_fault has a "funny" prefix, apparently
> part of "0xdeadbeef", a common constant in NetBSD used for "this
> pointer has now been invalidated", but apparently access was still
> attempted through it.  Can you say "driver and/or kernel memory
> management bug"?  (I knew you could. ;-)

Hmm.. Didn't help too much:

# gdb -q netbsd.1         
(no debugging symbols found)...(gdb) target kcore netbsd.1.core
panic: trap
#0  0x6 in ?? ()
(gdb) where
#0  0x6 in ?? ()
#1  0xf01cea83 in cpu_reboot ()
#2  0xf0121d81 in panic ()
#3  0xf01d4f36 in trap ()


:-(

  -jm