mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andries Brouwer <aebr@win.tue.nl>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Dmitry Torokhov <dtor_core@ameritech.net>,
	linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: PS2 mouse/kbd problems (gremlins?)
Date: Thu, 7 Oct 2004 02:10:17 +0200	[thread overview]
Message-ID: <20041007001017.GF4523@pclin040.win.tue.nl> (raw)
In-Reply-To: <1097101822l.5054l.0l@werewolf.able.es>

On Wed, Oct 06, 2004 at 10:30:22PM +0000, J.A. Magallon wrote:
> 
> On 2004.10.06, Dmitry Torokhov wrote:
> >On Tuesday 05 October 2004 12:45 pm, J.A. Magallon wrote:
> >> Hi all...
> >> 
> >> I got time to track my ps2 problems. I run 2.6.9-rc2-mm[123] (that was
> >> enough).
> >> 
> >> Results:
> >> - mm1: mouse and kbd work ok, both in console and X
> >> - mm2: mouse works, no kbd. I had to unplug/plug the keyboard to get it
> >>   responding.
> >> - mm3: kbd ok, but ps2 mouse is sluggish.
> >> 
> >> In latest -rc3-mm2, behavior is like mm3 and above.
> >> 
> >
> >What about vanilla -rc3 and vanilla -rc3 with bk-input patch applied (if 
> >you
> >have some time of course). Do they exibit the same symptoms as -mm tree?
> >
> 
> Both rc3 and rc3-bk.input work. Even rc3-mm2 works, depending on how I boot 
> ;).
> This is getting really strange....look:
> 
> lrwxrwxrwx  1 root root      21 2004.10.05 14:16 vmlinuz -> 
> vmlinuz-2.6.9-rc3-mm2
> 
> lilo.conf:
> default="linux"
> append="psmouse.proto=exps"
> image=/boot/vmlinuz
>    label="linux"
> ...
> image=/boot/vmlinuz-2.6.9-rc3-mm2
>    label="linux-2.6.9-rc3-mm2"
> 
> If I boot with the default entry, mouse does not work. If I boot with
> the specific entry in lilo for rc3-mm2, it works.
> 
> dmesg diff:
> -Kernel command line: BOOT_IMAGE=linux ro root=801 psmouse.proto=exps 3
> +Kernel command line: BOOT_IMAGE=linux-2.6.9-rc3-mm2 ro root=801 
> 
> Somebody understands this ? Are there gremlins in my box ?

A week or so ago I had a problem and couldnt see which changeset
caused it. After a binary search it turned out to be the changeset
that changed the (length of the) kernel version string.
A wild pointer was harmless at first, but after shifting everything
by a few bytes it caused crashes.

Probably (hopefully) your problem is something entirely different,
but it is not impossible that kernel behaviour depends on kernel name.

  reply	other threads:[~2004-10-07  0:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-05 17:45 PS2 mouse/kbd problems J.A. Magallon
2004-10-06  4:32 ` Dmitry Torokhov
2004-10-06 22:30   ` PS2 mouse/kbd problems (gremlins?) J.A. Magallon
2004-10-07  0:10     ` Andries Brouwer [this message]
2004-10-07 22:31       ` J.A. Magallon

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=20041007001017.GF4523@pclin040.win.tue.nl \
    --to=aebr@win.tue.nl \
    --cc=akpm@osdl.org \
    --cc=dtor_core@ameritech.net \
    --cc=jamagallon@able.es \
    --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®