Date: Tue, 24 Jul 2007 10:33:50 +0200 From: Gary Jennejohn <gary.jennejohn@freenet.de> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: panic when printing Message-ID: <20070724103350.7f9aac40.gary.jennejohn@freenet.de> In-Reply-To: <200707231804.14770.jhb@freebsd.org> References: <20070703114248.37a2019b.garyj@jennejohn.org> <200707231804.14770.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 23 Jul 2007 18:04:14 -0400 John Baldwin <jhb@freebsd.org> wrote: > On Tuesday 03 July 2007 05:42:48 am Gary Jennejohn wrote: > > I haven't seen this reported before. > > > > Trying to print to my parallel printer with a -current kernel from > > July 2 (amd64) results in a kernel panic. A kernel from June 16 > > (i386) does not cause a panic. > > > > If I boot with the printer turned on then the kernel sees it (PnP) > > with no problem. Just printing causes a panic. > > > > BTW this kernel is using the SMP-scheduler from Jeff Roberson, but > > IIRC a different kernel (June 29) w/o that scheduler also panics. > > > > I can't say whether it's amd64-specific or just due to recent > > changes to the sources. I'm rather reluctant to generate a new i386 > > kernel to check that, but I could be persuaded to do it. > > > > Below a typescript of a very limited kgdb session: > > You got an interrupt after the lpt driver removed its handler. > Really the ppbus device should not be so stupid and should have its > own interrupt handler that routes interrupts to the "active" child. > [snip kgdb output] Exactly. If I disable the interrupt in device.hints I can print wth no problems. I suspect that this problem exists for i386 also. --- Gary Jennejohn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070724103350.7f9aac40.gary.jennejohn>