On 18-Dec-00 Doug Barton wrote:
> I built -current world and kernel around 3am PST sunday morning with up
> to date sources. Later that same day I added Poul-Henning's console
> logging patch. Just a few minutes ago I had a lockup and panic that
> thankfully produced a kernel core to work with. It looks like this is
> not related to phk's patch, but rather to an NFS issue that I've seen
> before. I was copying a 23M file over NFS (mounted via amd) when this
> lockup and panic happened.
> My workstation is the NFS client, running -current. The NFS server is
> running FreeBSD 3.5.1-STABLE-1014 #0: Mon Oct 16 00:00:13 PDT 2000. If
> anyone wants me to do more debugging with this, let me know. I'm going
> out in a bit, but I will likely be available later tonight or tomorrow.
Grog had a similar panic on IRC the other day:
>#7 0xc021c857 in nfs_msg (p=0x0, server=0xc0bf0cf2 "slave:/usr/home",
> msg=0xc02ba748 "not responding") at
The 'p' parameter is a process that is supposed to be making the request, and
thus is going to receive a console message to its tty about the server going
away. Note that 'p' is NULL. This leads to a NULL dereference in tprintf().
The 'p' comes from some type of NFS request structure. That is as far as I
could take it however..
>#8 0xc021b742 in nfs_timer (arg=0x0) at
>#9 0xc01956d8 in softclock (dummy=0x0) at
>#10 0xc01834f4 in sithd_loop (dummy=0x0) at
John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message