Date: Sat, 13 Jan 2001 20:13:27 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: John Baldwin <jhb@FreeBSD.ORG>, Jordan Hubbard <jkh@winston.osd.bsdi.com> Cc: current@FreeBSD.ORG Subject: RE: Anybody else seeing a broken /dev/lpt with SMP on -current? Message-ID: <p05001902b686ad0d2404@[128.113.24.47]> In-Reply-To: <XFMail.010112185559.jhb@FreeBSD.org> References: <XFMail.010112185559.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 6:55 PM -0800 1/12/01, John Baldwin wrote: >On 13-Jan-01 Jordan Hubbard wrote: > > If anybody wants a fuller traceback then I'll compile up a kernel > > with debugging symbols, but it's going to be pretty sparse anyway > > since it basically only shows the trap() from the page fault and > > the subsequent panic. > >All the other traces show the kernel having returned to an address >that is beyond the end of the kernel (which causes the page fault) >meaning that the stack is fubar'd, so the trace isn't meaningful >anyways. :( Knowing how and why the lpd interrupt handler trashes >the stack is the useful info, and with the stack already trashed, >I don't know of an easy way to figure that out. Do you really mean the "lpd interrupt handler", or do you mean the "lpt interrupt handler"? Does this problem only happen when lpd is sending data thru /dev/lpt? -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu 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?p05001902b686ad0d2404>