mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Grzegorz Kulewski <kangur@polcom.net>
To: "R. J. Wysocki" <rjwysocki@sisk.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.[45]-.*: weird behavior
Date: Sun, 4 Apr 2004 13:21:13 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0404041248400.7155@alpha.polcom.net> (raw)
In-Reply-To: <200404040109.13414.rjwysocki@sisk.pl>

Maybe you should check IRQ sharing with ps port (if it is ps keyboard). Is 
it different under >=2.6.4-mm than under other kernels?

And maybe you should add boot options to turn ACPI and other similar 
options off.

And what video card are you using? There were some problems with S3 and 
other cards / XFree86 implementations in the past. Maybe kernel change is 
just exposing the problemm, not producing it? What about starting X with 
vesa or other "generic" driver insead of driver for your card.

I tried hard to reproduce your problem on my Athlon 32 box with 
2.6.5-rc3-mm4 but with no luck. I have some problems with this kernel, as 
with other kernels past 2.6.4 (for example I cannot mount any non root non 
virtual fs :)), but not this kind of problem. If I remember good I had one 
keyboard lockup under X in last month, but this was on 2.6.2-rc2-mm? 
kernel (probalby) after exiting from game (aa) and keyboard did not 
unlock (but I didint wait 30 sec - I do not have enough amount of 
patience :)). This problem never happened again.

What are exact steps to reproduce your problem?

And maybe the common thing with these two configurations is the 
SMP<->preemprion. These two are very similar in producing problems and if 
I remember good you have preemtion enabled on the laptop. Can you 
reproduce the problem without it?

I also found the patch for kernel stack in proc - it is here:

  http://thebsh.namesys.com/snapshots/LATEST/extra/a_04-proc-stack.patch

there is also iowait-reason and sleep-stat patch in the same directory.

And maybe try to reproduce the problem with 2.6.5 without mm. People like 
to have reports about "stable" kernels :)


good luck

Grzegorz Kulewski


PS. I am compiling 2.6.5 too to check if it works better for me.


  reply	other threads:[~2004-04-04 11:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-03 19:22 R. J. Wysocki
2004-04-03 19:50 ` Grzegorz Kulewski
2004-04-03 21:36   ` R. J. Wysocki
2004-04-03 22:15     ` Grzegorz Kulewski
2004-04-03 23:09       ` R. J. Wysocki
2004-04-04 11:21         ` Grzegorz Kulewski [this message]
2004-04-05 10:29           ` R. J. Wysocki

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=Pine.LNX.4.58.0404041248400.7155@alpha.polcom.net \
    --to=kangur@polcom.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjwysocki@sisk.pl \
    /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®