Date: Fri, 2 Jun 2000 23:12:32 -0500 From: "Kevin M. Dulzo" <kdulzo@caffeine.gerp.org> To: Sparhawk <sparhawk@sparhawk.bc.ca> Cc: freebsd-stable@freebsd.org, freebsd-alpha@freebsd.org Subject: Re: Reboots on Alpha System running 4.0 Stable Message-ID: <20000602231231.A19283@caffeine.gerp.org> In-Reply-To: <4.3.2.20000531202654.01750668@192.168.1.69>; from sparhawk@sparhawk.bc.ca on Wed, May 31, 2000 at 09:03:17PM -0700 References: <4.3.2.20000531202654.01750668@192.168.1.69>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 31, 2000 at 09:03:17PM -0700, Sparhawk wrote: > I updated from 4.0 RELEASE to STABLE about 3 or 4 days ago on my Digital > AlphaServer 400 4/233, since then I have noticed a few reboots. The > following Message appears in my log file. I am running an opennap napster > server on the machine. > > Any ideas what might be causing this? > > Sparhawk > sparhawk@sparhawk.bc.ca > > Jun 2 04:13:55 wintermute /kernel: > Jun 2 04:13:55 wintermute /kernel: fatal kernel trap: > Jun 2 04:13:55 wintermute /kernel: > Jun 2 04:13:55 wintermute /kernel: trap entry = 0x2 (memory management fault) > Jun 2 04:13:55 wintermute /kernel: a0 = 0x61feffa59f0 > Jun 2 04:13:55 wintermute /kernel: a1 = 0x1 > Jun 2 04:13:55 wintermute /kernel: a2 = 0x0 > Jun 2 04:13:55 wintermute /kernel: pc = 0xfffffc00003cd520 > Jun 2 04:13:55 wintermute /kernel: ra = 0xfffffc00003b8a60 > Jun 2 04:13:55 wintermute /kernel: curproc = 0xfffffe000aca44c0 > Jun 2 04:13:55 wintermute /kernel: pid = 356, comm = opennap > Jun 2 04:13:55 wintermute /kernel: > Jun 2 04:13:55 wintermute /kernel: panic: trap > Jun 2 04:13:55 wintermute /kernel: > Jun 2 04:13:55 wintermute /kernel: syncing disks... 22 22 22 22 22 22 22 > 22 22 > 22 22 22 22 22 22 22 22 22 22 22 > Jun 2 04:13:55 wintermute /kernel: giving up on 22 buffers > Jun 2 04:13:55 wintermute /kernel: Uptime: 13h30m36s > Jun 2 04:13:55 wintermute /kernel: Automatic reboot in 15 seconds - press > a key > on the console to abort > Jun 2 04:13:55 wintermute /kernel: Rebooting... > I have had the same issue, I thought it was due to nullfs mounts, so I removed them. a gdb showed an unknown symbol point in it wierd heuristic error as well in gdb -k. I rebuilt a kernel with nullfs build in to hopefully have the symbol show up next time I try them...but I lost the kernel.debug for the core files. I will follow up with a set if it occurs again. In my case cvsup caused one (last known symbol was in ufs something read or write) and cp caused another...no debug info. Just thought Id let it be known thats not an isolated error. Mines a PC164 at 500MHz underclocked to 466. -Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000602231231.A19283>