From owner-freebsd-current Mon Feb 12 19:30:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from syncopation-01.iinet.net.au (syncopation-01.iinet.net.au [203.59.24.37]) by hub.freebsd.org (Postfix) with SMTP id F0A1137B4EC for ; Mon, 12 Feb 2001 19:30:37 -0800 (PST) Received: (qmail 21624 invoked by uid 666); 13 Feb 2001 03:36:58 -0000 Received: from reggae-14-207.nv.iinet.net.au (HELO elischer.org) (203.59.77.207) by mail.m.iinet.net.au with SMTP; 13 Feb 2001 03:36:58 -0000 Message-ID: <3A88A3DA.BA099619@elischer.org> Date: Mon, 12 Feb 2001 19:02:50 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: "Alexander N. Kabaev" Cc: Alexander Leidinger , current@FreeBSD.ORG Subject: Re: Lpt driver broken? References: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Alexander N. Kabaev" wrote: > > > But I remember some posts about a lpt panic some days ago. I tried to > > compile a new kernel because I think this is resolved, but I have to > > solve some problems with my system at the moment. > > My -CURRENT used to crash every time lpr has been used but the panic went away > when John Baldwin committed his ithread cleanup megapatch: > > jhb 2001/02/09 09:47:47 PST > > Modified files: > sys/i386/i386 nexus.c > sys/i386/isa intr_machdep.c intr_machdep.h ithread.c > Log: > Use the MI ithread helper functions in the x86 interrupt code. > > The kernel from Feb 9 worked just fine for me, but then the following > commit has been made and the system started to crash again: > > jhb 2001/02/09 18:41:51 PST > > Modified files: > sys/i386/isa ithread.c > Log: > Re-enable preemption on interrupts. My last commit accidentally reverted > it as I was playing with some other ways of doing kernel preemption. > > Revision Changes Path > 1.14 +9 -2 src/sys/i386/isa/ithread.c > > If you badly need your printer to work, you can simply revert this patch. Looking at these patches, it seems that this patch doesn't actually CAUSE the problem, but, rather, 'allows it to be noticed'. BDE made an analysis I think in January some time but I didn't really follow it because it didn't effect me at the time (no printer). I'm not completely sure if that was the same problem though. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message