LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Kristoffer Ericson <kristoffer.ericson@gmail.com>
To: Jiri Kosina <jikos@jikos.cz>
Cc: Chris Holvenstot <cholvenstot@comcast.net>,
	Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.24-git15 Keyboard Issue?
Date: Wed, 6 Feb 2008 17:36:36 +0100	[thread overview]
Message-ID: <20080206173636.23f81913.Kristoffer.ericson@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0802061452210.30873@twin.jikos.cz>

On Wed, 6 Feb 2008 14:54:21 +0100 (CET)
Jiri Kosina <jikos@jikos.cz> wrote:

> On Wed, 6 Feb 2008, Chris Holvenstot wrote:
> 
> > On this system I am using a PS2 Keyboard - and let me stress that it is 
> > only occasionaly that it happens - I have had 2.6.24-git15 up for about 
> > 2 hours now and have only seen it about a dozen times. I also note one 
> > other thing - although my system is lightly loaded - at this time of day 
> > I am pretty much just using email on an AMD 64 X2 4600+ with 2 gigs of 
> > of memory - I have noticed several times that I will be typing away and 
> > nothing is appearing on the screen - and a few seconds later - boom - 
> > there it all is.
> 
> It could be some timing problem. Does this happen also in console, or 
> only when running X?
> 
> Could you please try to
> 
> - boot with 'nohpet' kernel parameter
> - taskset -p 0x00000002 <pid_of_Xserver> if this is a multi-CPU/core 
>   machine and you are experiencing the problems only in X
> 

Perhaps something to CC linux-input on?

> Thanks,
> 
> -- 
> Jiri Kosina
> --
> 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/

  reply	other threads:[~2008-02-06 16:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-06 13:02 Chris Holvenstot
2008-02-06 13:23 ` Mark Hounschell
2008-02-06 13:28 ` Jiri Kosina
2008-02-06 13:49   ` Chris Holvenstot
2008-02-06 13:54     ` Jiri Kosina
2008-02-06 16:36       ` Kristoffer Ericson [this message]
2008-02-06 17:24       ` Chris Holvenstot
2008-02-07  9:18         ` Jiri Kosina
2008-02-07  9:51           ` Chris Holvenstot
2008-02-07 10:44           ` Chris Holvenstot
2008-02-07 10:51             ` Jiri Kosina
2008-02-07 12:29               ` Thomas Gleixner
2008-02-07 15:07                 ` Chris Holvenstot
2008-02-07 16:13                   ` Thomas Gleixner
2008-02-07 16:45                     ` Chris Holvenstot
2008-02-07 17:46                       ` Thomas Gleixner
2008-02-08  5:36                         ` Chris Holvenstot
2008-02-09  9:56                           ` Thomas Gleixner
2008-02-09 10:37                             ` Chris Holvenstot
2008-02-09 13:59                               ` Thomas Gleixner
2008-03-28 10:15                                 ` Thomas Gleixner
2008-03-28 11:20                                   ` Chris Holvenstot
2008-03-28 11:24                                     ` Jiri Kosina
2008-03-28 11:34                                       ` Chris Holvenstot
2008-02-08 15:08                         ` Jiri Kosina
2008-02-08 23:25                           ` Jiri Kosina

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=20080206173636.23f81913.Kristoffer.ericson@gmail.com \
    --to=kristoffer.ericson@gmail.com \
    --cc=cholvenstot@comcast.net \
    --cc=jikos@jikos.cz \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: 2.6.24-git15 Keyboard Issue?' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).