lkml.org 
[lkml]   [2004]   [Oct]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: PS2 mouse/kbd problems (gremlins?)
    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.
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 14:06    [W:0.029 / U:32.260 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site