Re: 2.6.24-rt1 SSttrraannggee keyboard behaviour

[Clark Williams]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Uli Brueggemann wrote:
 Hi,
 
 I'm trying to use 2.6.24-rt1 in combination with BruteFIR (audio). So
 far everything looks fine except:
 
 After starting BruteFIR (which is doing its job) after a while the
 keyboard responds like with double clicks. TTeeiibbllee. I cannot
 enter a command anymore. The running BruteFIR itself still is running
 stable.
  The system without starting BruteFIR keeps stable. BruteFIR itself is
 working fine with older kernels. Also with e.g. 2.6.24-rc3-zen3. So I
 guess the realtime patch is causing this.
 BTW Brutefir is using realtime priorities 1 to 4 and it also uses SCHED_FIFO.
 
 Any idea?
 
 Uli

Uli,

I've seen this behavior before; on my system in addition to the doubled 
keystrokes,
cursor animations were jerky.

Are you running on a 64-bit kernel, is your clocksource hpet and is vsyscall64 
on?

$ uname -m
x86_64
$ cat /sys/devices/system/clocksource/clocksource0/current_clocksource
hpet
$ cat /proc/sys/kernel/vsyscall64
1

If so, try putting this into your /etc/sysctl.conf and rebooting:

# vsyscall64 off
kernel.vsyscall64 = 0

You could try echoing 1 into /proc/sys/kernel/vsyscall64, but with the 
keyboard
doubling issue, it might be a problem :)

Clark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkejRsMACgkQHyuj/+TTEp14GgCg1PV1n23nDDJg8Bp6NTEXIUTQ
iukAoK56x+wQcZ8Z+YNea8glzIe41EpA
=ZKru
-END PGP SIGNATURE-
-
To unsubscribe from this list: send the line unsubscribe linux-rt-users in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.23-rc9-rt1

[Clark Williams]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Steven Rostedt wrote:
 
 grmbl grmbl!!!
 
 We are missing a match somewhere. Most likely in the suspend or resume
 code.  It's expected that if a CPU is idle with no ticks then the
 dynticks_progress_counter is even, otherwise it is odd. This check tells
 us that, in your case, this isn't the case. Which _is_ bad, and I wouldn't
 run it too long that way. It means that you can be getting false RCU grace
 period ends, which is not a good thing.
 
 I could put a hack in that fixes the issue when detected, and still prints
 out a warning. I'll do that for now, until we find the problem area. I
 think the first warning probably had the want that corrupted us, and then
 we got flooded with warnings because we never fixed the situation.
 
 Patch coming soon.
 
 -- Steve
 Ad infinitum. Not sure what you're looking for to be cleared in the enter 
 and exit
 functions, but it doesn't look like it's happening after a resume. Didn't 
 seem to
 affect the behavior of the kernel, since the network came up and I was able 
 to
 function normally (or as normally as I can function).
 
 I'd reboot if I were you ;-)

Oh, I did :)

I've since suspended and resumed a couple of more times and have not seen your 
RCU
warnings, so it's not completely reproduceable.

Got any debugging code you want me to add, in case it pops up again?

Clark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFHA51OHyuj/+TTEp0RAn6hAJwO3JHHk+2EVjpH7XcAYu+g5CC3DQCgj1lR
4Umv2vf2iDjxHNprCXfxhvI=
=SL/V
-END PGP SIGNATURE-
-
To unsubscribe from this list: send the line unsubscribe linux-rt-users in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html