From owner-freebsd-current Fri Jan 12 19: 6:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 259C637B400; Fri, 12 Jan 2001 19:05:55 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0D35sa13985; Fri, 12 Jan 2001 19:05:54 -0800 (PST) Date: Fri, 12 Jan 2001 19:05:54 -0800 From: Alfred Perlstein To: John Baldwin Cc: Jordan Hubbard , current@FreeBSD.ORG Subject: Re: Anybody else seeing a broken /dev/lpt with SMP on -current? Message-ID: <20010112190554.E7240@fw.wintelcom.net> References: <18670.979354005@winston.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.ORG on Fri, Jan 12, 2001 at 06:55:59PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * John Baldwin [010112 18:56] wrote: > > On 13-Jan-01 Jordan Hubbard wrote: > > I've actually been seeing this for about 2 months now but only just > > now got motivated enough to enable crashdumps and get some information > > on what happens whenver I try to use the printer attached to my (sadly :) > > -current SMP box: > > > > All the other traces show the kerenl having returned to an address that is > beyongd 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 > teh stack already trashed, I don't know of an easy way to figure that out. > Suggestions welcome. printf(9) :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message