From owner-freebsd-current@FreeBSD.ORG Sat Sep 18 14:44:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1B9A16A4CE for ; Sat, 18 Sep 2004 14:44:10 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 916E943D31 for ; Sat, 18 Sep 2004 14:44:10 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) i8IEiAKV017836; Sat, 18 Sep 2004 07:44:10 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)i8IEi97f017835; Sat, 18 Sep 2004 07:44:09 -0700 (PDT) (envelope-from sgk) Date: Sat, 18 Sep 2004 07:44:09 -0700 From: Steve Kargl To: Martin Message-ID: <20040918144409.GA17802@troutmask.apl.washington.edu> References: <41417326.1000309@withagen.nl> <1095437354.1094.4.camel@klotz.local> <20040917164527.GB12002@troutmask.apl.washington.edu> <1095507437.922.3.camel@klotz.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1095507437.922.3.camel@klotz.local> User-Agent: Mutt/1.4.1i X-Mailman-Approved-At: Sat, 18 Sep 2004 15:26:29 +0000 cc: "Boris B. Samorodov" cc: Ian FREISLICH cc: FreeBSD Current Subject: Re: [SOLVED] Interrupt storm detected on "irq7: lpt0" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Sep 2004 14:44:10 -0000 On Sat, Sep 18, 2004 at 01:43:29PM +0200, Martin wrote: > Am Fr, den 17.09.2004 schrieb Steve Kargl um 18:45: > > > lptcontrol -e > > Almost! But thanks, you gave me the right hint. > > For me "lptcontrol -p" works. > > Does it have something to do with > "options DEVICE_POLLING" enabled in my kernel? > I don't know the answer. My printer went from printing at a good clip to molasses. I finally realized that the driver was set in interrupt mode. In my investigation I recalled the lptcontrol command and now the printer is happy again. -- Steve