tir, 2002-10-08 kl. 19:25 skrev Vojtech Pavlik:
> On Tue, Oct 08, 2002 at 07:18:06PM +0200, Stian Jordet wrote:
> > tir, 2002-10-08 kl. 10:17 skrev Vojtech Pavlik:
[snip]
> > > I really wonder what your keyboard sends for those keys. To avoid the
> > > freeze (and rescanning of the keyboard), you should be able to
> > > comment-out these lines in atkbd.c:
> > > 
> > >          case ATKBD_KEY_BAT:
> > >                  serio_rescan(atkbd->serio);
> > >                  return;
> > >  
> > It didn't help at all. I just tried 2.5.41 instead of .40, and now I get
> > an Oops. Earlier it just froze. Should I write it down?
> 
> Yes!
It won't oops anymore (?) This is really weird, I don't know what I did
last night, I was terribly tired, so that must be the reason. .41 and
your alt-alt patch, does NOT crash my computer now. No oops, nothing.
Attached is a parts of my syslog with debug enabled (and with your
alt-alt patch). I logged in, did a echo cut-here >> /var/log/syslog to
know what to send you (didn't want everyone at lkml to know my root
password, for instance). Then I did this:

Right Shift+Pageup
Right Shift+Pageup
Right Shift+Pagedown
Right Shift+Pagedown
Left Shift+Pageup
Left Shift+Pageup
Left Shift+Pagedown
Left Shift+Pagedown
Right Shift+Pageup
Right Shift+Pageup
Right Shift+Pagedown
Right Shift+Pagedown
Left Shift+Pageup
Left Shift+Pageup
Left Shift+Pagedown
Left Shift+Pagedown

ARROW-UP (to get the echo-line back)
ENTER (to make a new mark in syslog).

What I have attached is what is between those cut-here marks.

When I press the right-shift and Page up, I first get unknown scancode
0x1b6. Then, I'll get 0x1aa on every button I press untill I started to
press the left-shift instead. After that, the right shift works like it
should. I'm totally confused. But I guess you're better reading the logs
than I'm. 

> > I'm starting to feel a little embarassed since I'm the only one with
> > this problem. It's not reallt a big deal, I can boot with i8042_direct,
> > and it works fine.
> 
> Once 2.5 is more public, more people will be bitten by the problem you
> have, so we need to fix it. Thanks a lot for your cooperation, and
> please pardon my confusion about who sumbitted which problem, and if I
> solved it already. :)
Well, as I'm still the only one with the problem, I'm very, very
greatful you're taking the time to try to solve this :) Sorry for the
delay.

Best regards,
Stian Jordet