From owner-freebsd-alpha Tue Apr 18 9:44:15 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.thebiz.net (mx1.thebiz.net [216.238.0.20]) by hub.freebsd.org (Postfix) with SMTP id 3A1FD37B9E1 for ; Tue, 18 Apr 2000 09:44:11 -0700 (PDT) (envelope-from matt@thebiz.net) Received: (qmail 946 invoked from network); 18 Apr 2000 12:44:09 -0400 Received: from mail1.thebiz.net (172.16.0.179) by mx1.thebiz.net with SMTP; 18 Apr 2000 12:44:09 -0400 Received: (qmail 7304 invoked by uid 0); 18 Apr 2000 12:44:09 -0400 Received: from unknown (HELO mahatma) (216.238.1.20) by mail.thebiz.net with SMTP; 18 Apr 2000 12:44:09 -0400 Message-ID: <00c501bfa955$203546e0$1401eed8@mahatma> From: "Matthew Zahorik" To: Subject: HELP! Date: Tue, 18 Apr 2000 12:42:46 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a reliable kernel panic when copying a file. These are diskless servers. /etc is a MFS filesystem. /sandbox/etc is NFS mounted. [shell1]:DING~:~# cd /sandbox/etc [shell1]:12:00pm:/sandobx/etc# cp /etc/sshd_config . fatal kernel trap: trap entry = 0x2 (memory management fault) a0 = 0x0 a1 = 0x1 a2 = 0xffffffffffffffff pc = 0x0 ra = 0x1 curproc = 0xfffffe0011456e00 pid = 338, comm = cp ddbprinttrap from 0x0 ddbprinttrap(0x0, 0x1, 0xffffffffffffffff, 0x2) panic: trap panic Stopped at Debugger+0x2c: ldq ra,0(sp) <0xfffffe0012afd3f0>\ db> trace Debugger() at Debugger+0x2c panic() at panic+0x100 trap() at trap+0x610 XentMM() at XentMM+0x20 (null) at 0x1 db> You can cat/more, ls -l, and otherwise manipulate the file. You can't copy it for the life of me. (I haven't tried mv'ing it) I tried different destinations, like cp /etc/sshd_config /tmp and that still crashes. This was a 4.0-RELEASE kernel. I CVS'd out the current kernel (cd /usr/src, cvs co sys) just a couple of moments ago and tried that - no change, so it's not a bug that has a fix recently committed. These machines were really close to hitting production with FreeBSD instead of Linux on them, but I can't have people rebooting the machines at will (: Any pointers would be appreciated so I can fix this quickly. There's no PC, or any other address that points to the bad code, so I really can't track it down. Something is getting a null pointer, and crashing. Since it's bringing down the machine, I assume it is in the kernel space. (I assume a null pointer access in user space can't bring the machine down) My gut tells me it's MFS related. I can't reproduce this on my Intel boxes - either the bug doesn't exist or the setup isn't identical. - Matt -- Matthew Zahorik Director of Systems and Networking - BiznessOnline.com matt@thebiz.net President of AlbanyNet Inc. - a BiznessOnline subsidiary maz@albany.net Voice: (518) 292-1001 Fax: (518) 626-0793 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message