Date: Tue, 21 Jan 1997 17:59:36 +0100 (MET) From: Christoph Kukulies <kuku@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org Subject: panic in nfs_rcvunlock Message-ID: <199701211659.RAA28953@gilberto.physik.rwth-aachen.de>
next in thread | raw e-mail | index | archive | help
On one machine which runs a Jan 13 1997 3.0 kernel I just got a panic and since I'm running this kernel under ddb I want to report the back- trace even if it may not be very significant. I was experimenting with aliased interfaces and an NFS server was unreachable when I decided to sync ; sync ; reboot the machine - it was already hanging with 'nfs server not responding'. It's a 486DX4/133 w/ 64MB, ASUS SP3G. Whilst it was shutting down it panicked into ddb with the following backtrace: panic nfs_rcvunlock nfs_reply nfs_request nfs_lookup namei lstat syscall Xsyscall syscall 190 eip=0xdcd5 ebp=0xefbfdc18 The eip address doesn't seem to point into any valid kernel address. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199701211659.RAA28953>