Date: Wed, 08 Nov 2000 01:42:27 +0900 From: Motomichi Matsuzaki <mzaki@e-mail.ne.jp> To: current@freebsd.org Subject: Re: irq7 panic Message-ID: <86itpzybrg.wl@tkc.att.ne.jp> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, At Tue, 7 Nov 100 07:39:25 -0600 (CST), Jim Bryant <jbryant@ppp-207-193-0-166.kscymo.swbell.net> 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: <Parallel port> 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: <PLIP network interface> on ppbus0 lpt0: <Printer> on ppbus0 lpt0: Interrupt-driven port ppi0: <Parallel I/O> 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 <mzaki@e-mail.ne.jp> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86itpzybrg.wl>