From owner-freebsd-current Fri Mar 30 3: 1:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241]) by hub.freebsd.org (Postfix) with ESMTP id 06AF237B718 for ; Fri, 30 Mar 2001 03:01:21 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.pacbell.net ([207.214.149.180]) by mta5.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0GB000LIUBXA4O@mta5.snfc21.pbi.net> for current@freebsd.org; Fri, 30 Mar 2001 03:00:47 -0800 (PST) Received: by zippy.pacbell.net (Postfix, from userid 1000) id A6D8417C9; Fri, 30 Mar 2001 03:00:43 -0800 (PST) Date: Fri, 30 Mar 2001 03:00:43 -0800 From: Alex Zepeda Subject: panic with recent kernel.. To: current@freebsd.org Message-id: <20010330030043.A575@zippy.mybox.zip> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The box itself is a dual P2-450, and I was attempting to rebuild a KDE library (ah the joys of doing that), and monitoring stuff with top. The first odd thing I noticed was that some of the processes showed up with an state field (namely sed, and a few others I think). Eventually the box panic'd, and instead of dumping to the swap partition, it hung while trying to reset the ATA devices. The trace I got was: Stopped at p_cansee+0x16 pushl 0(%eax) p_cansee p_can sysctl_kern_proc sysctl_root userland_sysctl __sysctl syscall syscall_with_err_pushed zippy:~#uname -a FreeBSD zippy.mybox.zip 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Thu Mar 29 19:31:43 PST 2001 root@zippy.mybox.zip:/usr/src/sys/compile/ZIPPY_SMP i386 - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message