Re: [patch] voluntary-preempt-2.6.8-rc2-L2 PS2 keyboard gone south

[Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>]

On Sat, 2004-07-31 at 20:32 -0400, Lee Revell wrote:
> On Sat, 2004-07-31 at 20:24, Felipe Alfaro Solana wrote:
> > 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.
> 
> Hmm.  Maybe the problem is filesystem or disk related.  Is your root
> partition on IDE or SCSI?  It could be a SCSI problem.

No SCSI. Only 2 IDE drives, 1 ATAPI DVD and 1 ATAPI CD-RW.

> Are you running software or hardware RAID?

No.

> This is the same behavior you get when, for example, a disk dies.

I have 2 identical UDMA 120GB Seagate disks which are 1 month old, so I
guess it's not a problem with bad hardware.

It turns out that my lock ups where related to APIC. Disabling APIC
seems to get rid of those lock ups.