Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262316AbUDDLVv (ORCPT ); Sun, 4 Apr 2004 07:21:51 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262293AbUDDLVv (ORCPT ); Sun, 4 Apr 2004 07:21:51 -0400 Received: from [80.72.36.106] ([80.72.36.106]:64454 "EHLO alpha.polcom.net") by vger.kernel.org with ESMTP id S262322AbUDDLVW (ORCPT ); Sun, 4 Apr 2004 07:21:22 -0400 Date: Sun, 4 Apr 2004 13:21:13 +0200 (CEST) From: Grzegorz Kulewski To: "R. J. Wysocki" Cc: linux-kernel@vger.kernel.org Subject: Re: 2.6.[45]-.*: weird behavior In-Reply-To: <200404040109.13414.rjwysocki@sisk.pl> Message-ID: References: <200404032122.54823.rjwysocki@sisk.pl> <200404032314.27866.rjwysocki@sisk.pl> <200404040109.13414.rjwysocki@sisk.pl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2012 Lines: 49 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. - 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/