public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech-AlSwsSmVLrQ@public.gmane.org>
To: Bernd Schubert
	<Bernd.Schubert-ZRyP5vvp4SQZDP5dtiX3a0ZMdOyQQXjt@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: psmouse.c, throwing 3 bytes away
Date: Mon, 9 Feb 2004 00:30:52 +0100	[thread overview]
Message-ID: <20040208233052.GA17570@ucw.cz> (raw)
In-Reply-To: <20040208230314.GA21937-XPbICIHHaRhIi1TGZYQs7PQvEQgnY+0MepZhswDD4dQ@public.gmane.org>

On Mon, Feb 09, 2004 at 12:03:14AM +0100, Bernd Schubert wrote:

> On Sun, Feb 08, 2004 at 11:19:32PM +0100, aeriksson-97jfqw80gc6171pxa8y+qA@public.gmane.org wrote:
> > 
> > > 
> > > > Problem still occurs :-(
> > > 
> > > I have good news - I've managed to reliably reproduce the bug on my
> > > machine and that means I now have a good chance to find and fix it.
> > > 
> > 
> > Another data point. I just tried switching to a non-preempt kernel as
> > was suggested by someone. The problem still occurs.

> Hello,
> 
> on IBM Thinkpads R31 this is also easiliy to reproduce:
> 
> For 2.6. one only needs to read from /proc/apm or /proc/acpic/...
> and the mouse becomes crazy and one gets the throwing 2 bytes away
> messages in the log files. By fast reading in an endless loop even
> input from the keyboard is ignored.
> 
> For 2.4. this only happens on reading from /proc/apm, somehow acpi is not
> affected in 2.4. kernel versions.
> 
> Well, for R31's it is said that it is the bad bios, but maybe its
> related? Any ideas why it doesn't happen with acpi and 2.4.? 

There are many reasons why it can happen. I'm currently debugging the
one where no APM or ACPI or anything else is needed.

> My knowlege of the kernel interals is quite low and pretty much limited
> to the basic vfs area, so could you please give me some good advises how to
> debug this?

You can enable DEBUG in i8042.c, and then look at 'dmesg' when the
problem happens. There will be a missing byte in the stream ...

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

  parent reply	other threads:[~2004-02-08 23:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040208215935.GA13280@ucw.cz>
     [not found] ` <20040208221933.92D0B3F1B@latitude.mynet.no-ip.org>
     [not found]   ` <20040208221933.92D0B3F1B-hJetzOkQQ2D26ODOwDBsm7iufofboIZS@public.gmane.org>
2004-02-08 23:03     ` psmouse.c, throwing 3 bytes away Bernd Schubert
     [not found]       ` <20040208230314.GA21937-XPbICIHHaRhIi1TGZYQs7PQvEQgnY+0MepZhswDD4dQ@public.gmane.org>
2004-02-08 23:30         ` Vojtech Pavlik [this message]
     [not found]           ` <20040208233052.GA17570-+ZI9xUNit7I@public.gmane.org>
2004-02-09 12:43             ` roychris
2004-02-09 15:12             ` roychris

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=20040208233052.GA17570@ucw.cz \
    --to=vojtech-alswssmvlrq@public.gmane.org \
    --cc=Bernd.Schubert-ZRyP5vvp4SQZDP5dtiX3a0ZMdOyQQXjt@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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