From owner-freebsd-current Tue Nov 7 8:42:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from tkc.att.ne.jp (tkc.att.ne.jp [165.76.16.7]) by hub.freebsd.org (Postfix) with ESMTP id 09A3437B479 for ; Tue, 7 Nov 2000 08:42:31 -0800 (PST) Received: from work.mzaki.nom (169.pool8.ipctokyo.att.ne.jp [165.76.204.169]) by tkc.att.ne.jp (8.8.8+Spin/3.6W-CONS(10/06/00)) id BAA26801; Wed, 8 Nov 2000 01:42:28 +0900 (JST) Date: Wed, 08 Nov 2000 01:42:27 +0900 Message-ID: <86itpzybrg.wl@tkc.att.ne.jp> From: Motomichi Matsuzaki To: current@freebsd.org Subject: Re: irq7 panic In-Reply-To: In your message of "Tue, 7 Nov 100 07:39:25 -0600 (CST)" <200011071339.HAA08324@ppp-207-193-0-166.kscymo.swbell.net> References: <200011071339.HAA08324@ppp-207-193-0-166.kscymo.swbell.net> X-Mailer: Wanderlust/1.1.1 (Purple Rain) XEmacs/21.1 (Channel Islands) MIME-Version: 1.0 (generated by WEMI 1.13.7 - "Shimada") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At Tue, 7 Nov 100 07:39:25 -0600 (CST), Jim Bryant wrote: > I've been getting a hard panic/page fault whenever attempting to print > for a few weeks now. I have the same problem on the i386/SMP from Oct 10 to date. Sep 23 world works fine. dmesg: ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 I've found that it happens during the function fork_trampoline(), and caused by calling indefinite function which shoud be set by cpu_set_fork_handler(). When I request printing (lpr), the interrupt threads (irq7: lpt0) is create, then call the function, but there is no effective codes, and panic. -- Motomichi Matsuzaki Dept. of Biological Sciences, Grad. School of Science, Univ. of Tokyo, Japan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message