From owner-freebsd-bugs Sun Oct 22 13:40: 5 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 365C437B4D7 for ; Sun, 22 Oct 2000 13:40:02 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id NAA20915; Sun, 22 Oct 2000 13:40:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Sun, 22 Oct 2000 13:40:01 -0700 (PDT) Message-Id: <200010222040.NAA20915@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: John Baldwin Subject: Re: kern/21929: lpd cause system crash Reply-To: John Baldwin Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/21929; it has been noted by GNATS. From: John Baldwin To: Paul van der Zwan Cc: wkwu@csie.nctu.edu.tw, freebsd-gnats-submit@freebsd.org Subject: Re: kern/21929: lpd cause system crash Date: Sun, 22 Oct 2000 13:34:37 -0700 (PDT) On 22-Oct-00 Paul van der Zwan wrote: > > I am having the same problem, code in inthand_add causes a trap 12. > This happens regularly when printing a file. > > I also noted that when I run systat -vm some interrupt vectors are marked as > stray and used by a device. Look at irq 0 and 6 in the output below. > Might this be related to the changes in intr_machdep.? made in september ?? > I never had these panics before I built and installed a new current about 3 > weeks ago. Notice the stray counts are 0. I.e., you are't having any stray counts at the moment. If you have 1 stray interrupt during boot then these stray entries will show up forever in vmstat even thugh you aren't getting any more stray interrupts. How do you know that the code in inthand_add() is causing a trap 12 btw? A stack trace and the trap message would be most helpful. -- John Baldwin -- 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 majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message