From owner-freebsd-hackers Sun May 2 19:54: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 08C0B14C1D for ; Sun, 2 May 1999 19:54:04 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id WAA27609; Sun, 2 May 1999 22:53:55 -0400 (EDT) Message-Id: <199905030253.WAA27609@cs.rpi.edu> To: freebsd-hackers@freebsd.org Cc: schimken@cs.rpi.edu, crossd@cs.rpi.edu Subject: 'nother NFS panic on 3.1-STABLE-Sun Mar 21 Date: Sun, 02 May 1999 22:53:54 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is another instance of the mbuf 32k problem that caused our previous crash, this time I have the crashdump. (BTW: I issued 'savecore' on the machine and it said "no coredump", yet I issued a dd bs=512 if=/dev/wd0s1b skip= OFFSET of=crashfile, and I have a valid core.) Below is what I find to be interesting in the PS output: USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND root 34338 39.2 0.0 296 0 ?? R - 0:00.00 (nfsd) 0 34338 34337 276 -6 0 296 0 - R ?? 0:00.00 (nfsd) root 167 0.0 0.0 262984 0 ?? Ss - 0:00.00 (rpc.statd) 0 167 1 0 2 0 262984 0 select Ss ?? 0:00.00 (rpc.statd) Does this sugggest anything to anyone? (We will be upgrading this machine shortly, I just hope to gather some insight as to what tripped this. Our new kernels will be config -g; strip --no-debug kernels :) -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message