mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Dieter N?tzel <Dieter.Nuetzel@hamburg.de>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.40 (-ac3) and 2.4.19-ck5: mousedev interfere with parport ;-(
Date: Mon, 7 Oct 2002 11:04:39 +0200	[thread overview]
Message-ID: <20021007110439.D63229@ucw.cz> (raw)
In-Reply-To: <200210060129.41010.Dieter.Nuetzel@hamburg.de>; from Dieter.Nuetzel@hamburg.de on Sun, Oct 06, 2002 at 01:29:40AM +0200

On Sun, Oct 06, 2002 at 01:29:40AM +0200, Dieter N?tzel wrote:
> While printing with latest hpijs-1.2.2-rss.1 (patched for older HP9xx 
> printers) at 1200x1200 DPI on 2.5.40-ac3 I found critical bug in the 
> "mousedev" module.
> 
> Symptoms:
> 
> Total system hang.
> Nothing in the logs :-(
> Reboot
> CUPS restart and boom, again and again,...
> 
> Then I went back to 2.4.19-ck5 and boom...
> Several hpijs-1.2.1/1.2.2 versions rechecked. -> Nothing.
> 
> After some thought.
> I have to use "mousedev" and "psmouse" modules since 2.5.40 (-ac3).
> Commented both in my "/etc/rc.d/boot.local" file and started 2.4.19-ck5, 
> again. Bingo ;-)
> 
> But what should I do with 2.5.40+?
> I need my mouse.
> 
> System:
> dual Athlon MP 1900+
> MSI MS-6501 (aka K7D Master-L), Rev 1.0, AMD 760MPX
> 
> Regards,
> 	Dieter
> 
> BTW 2.5.40 is so GREAT on my mixed server/desktop/3D graphics devel maschine.

Hmm how do you know it's mousedev? (99.9% it cannot be the problem.
psmouse could, theoretically, but it's still very unlikely).

Note that you exchanged the whole 2.5 kernel with a 2.4. The crash
could have been anywhere in the kernel, not just the psmouse/mousedev
modules.

-- 
Vojtech Pavlik
SuSE Labs

      reply	other threads:[~2002-10-07  8:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-05 23:29 Dieter Nützel
2002-10-07  9:04 ` Vojtech Pavlik [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021007110439.D63229@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=Dieter.Nuetzel@hamburg.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®