From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Shane Shrybman <shrybman@aei.ca>, Ingo Molnar <mingo@elte.hu>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] voluntary-preempt-2.6.8-rc2-L2 PS2 keyboard gone south
Date: Sun, 01 Aug 2004 02:24:00 +0200 [thread overview]
Message-ID: <1091319840.2386.3.camel@teapot.felipe-alfaro.com> (raw)
In-Reply-To: <1091246222.1677.65.camel@mindpipe>
On Fri, 2004-07-30 at 23:57 -0400, Lee Revell wrote:
> On Fri, 2004-07-30 at 21:13, Felipe Alfaro Solana wrote:
> > On Fri, 2004-07-30 at 20:05 -0400, Lee Revell wrote:
> > > On Fri, 2004-07-30 at 19:21, Felipe Alfaro Solana wrote:
> > > > On Fri, 2004-07-30 at 13:38 -0400, Shane Shrybman wrote:
> > > >
> > > > > > M5 does that differently, yes - so could you try it? If you still get
> > > > > > problems, does this fix it:
> > > > >
> > > > > Ok, M5 locked up the whole machine within a few seconds of starting X.
> > > >
> > > > Me too, with voluntary-preempt=3... It seems I can trigger this randomly
> > > > by heavily moving the mouse around while logging in into my KDE session.
> > > >
> > > > However, with voluntary-preempt=2 I've been unable to lock the machine
> > > > yet.
> > >
> > > It looks like this is a mouse problem, I have a PS/2 keyboard and USB
> > > mouse and have not had any problems yet with M5. I also found that with
> > > L2, I could toggle Caps Lock fast enough to get significantly 'ahead' of
> > > it, this no longer happens with M5.
> >
> > I have a PS/2 keyboard and a USB mouse.
>
> Weird. This is my setup also, and I have had no problems since
> installing M5.
>
> Try:
>
> Option "NoAccel"
>
> in section "Device" of your XF86Config. Also try commenting out:
>
> Load "dri"
>
> in the "Module" section.
>
> This will ensure that the X server is not accessing hardware directly.
> Normally this should not be a problem but a buggy video driver can cause
> problems. On my machine, having 2D acceleration enabled caused
> interrupts from other devices to be lost when dragging a window.
>
> Also, is the machine pingable after it locks up?
Curiously, the machine is pingable, but I can't ssh/telnet into it: no
data is received from the locked machine.
next prev parent reply other threads:[~2004-08-01 0:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-30 14:06 Shane Shrybman
2004-07-30 15:20 ` Ingo Molnar
2004-07-30 17:38 ` Shane Shrybman
2004-07-30 23:21 ` Felipe Alfaro Solana
2004-07-31 0:05 ` Lee Revell
2004-07-31 1:13 ` Felipe Alfaro Solana
2004-07-31 3:57 ` Lee Revell
2004-08-01 0:24 ` Felipe Alfaro Solana [this message]
2004-08-01 0:32 ` Lee Revell
2004-08-01 1:11 ` Felipe Alfaro Solana
2004-08-01 10:49 ` Ingo Molnar
2004-07-31 3:54 ` Shane Shrybman
[not found] ` <1091246621.1677.71.camel@mindpipe>
[not found] ` <1091267282.1768.8.camel@teapot.felipe-alfaro.com>
[not found] ` <1091296615.1677.283.camel@mindpipe>
[not found] ` <1091320571.2445.6.camel@teapot.felipe-alfaro.com>
2004-08-01 0:46 ` Lee Revell
2004-08-01 1:14 ` Felipe Alfaro Solana
2004-07-30 18:03 ` Lee Revell
2004-07-30 21:31 ` Shane Shrybman
2004-07-30 21:46 ` Lee Revell
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=1091319840.2386.3.camel@teapot.felipe-alfaro.com \
--to=felipe_alfaro@linuxmail.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rlrevell@joe-job.com \
--cc=shrybman@aei.ca \
/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®