Date: Fri, 23 Jul 2004 21:26:13 +0100 From: "Markie" <mark.cullen@dsl.pipex.com> To: "Martin" <nakal@web.de> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Problems with interrupts on -CURRENT? Message-ID: <003901c470f3$4e05e6f0$f800000a@laptop> References: <1090606572.2670.15.camel@klotz.local> <000e01c470eb$d5b215e0$f800000a@laptop> <1090612034.3387.5.camel@klotz.local>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- From: "Martin" <nakal@web.de> To: "Markie" <mark.cullen@dsl.pipex.com> Cc: "FreeBSD Current" <freebsd-current@freebsd.org> Sent: Friday, July 23, 2004 8:47 PM Subject: Re: Problems with interrupts on -CURRENT? | Am Fr, den 23.07.2004 schrieb Markie um 21:32: | | > To get over the printer thing, which has done that interrupt storm thing for | > rather a long time with me but never this bad, I used polling mode instead with | > lptcontrol. Something like lptcontrol -p ... | | Earlier, when the kernel was more responsive, i've had interrupt | storms (lpt irq) when shutting down (only after printer has been used). | But printing worked in normal speed (printing a page took a few | seconds), but now it takes minutes (10-20 or so). Yup, my printer was ok on an older current but I still saw interrupt storm messages. Its running current just before the preemption went in and it takes .... well..... i've never left it to try and print something put it that way. Fortuantly I only really use the box for a print server so putting the printer on polling mode is a quick and easy solution for me :-) | | I will try to update now, but I think it can take until tomorrow. | | Martin | | | _______________________________________________ | freebsd-current@freebsd.org mailing list | http://lists.freebsd.org/mailman/listinfo/freebsd-current | To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?003901c470f3$4e05e6f0$f800000a>