From: Grzegorz Kulewski <kangur@polcom.net>
To: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.5: keyboard lockup on a Toshiba laptop
Date: Wed, 7 Apr 2004 13:31:39 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.58.0404071324050.10871@alpha.polcom.net> (raw)
In-Reply-To: <20040407110608.GR20293@charite.de>
Ok, that should be easy to debug... I hope :-)
Try to apply this patch to check what kernel part call connect function
too many times. (Maybe it is some power management stuff?)
WARNING
It is my first "public" patch and I even not compiled it so maybe some
headers should be declared. But if it will compile and run, it should
display nice callstack in log for you for each call to this function.
happy testing
Grzegorz
--- linux-2.6.5/drivers/input/keyboard/atkbd.c.orig 2004-04-04
05:37:43.000000000 +0200
+++ linux-2.6.5/drivers/input/keyboard/atkbd.c 2004-04-07
14:23:26.719121672 +0200
@@ -679,6 +679,8 @@
{
struct atkbd *atkbd;
int i;
+
+ dump_stack();
if (!(atkbd = kmalloc(sizeof(struct atkbd), GFP_KERNEL)))
return;
next prev parent reply other threads:[~2004-04-07 11:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 10:22 2.6.5: keyboard lockup on a Toshiba laptop R. J. Wysocki
2004-04-07 10:33 ` Grzegorz Kulewski
2004-04-07 10:39 ` Ralf Hildebrandt
2004-04-07 10:51 ` Grzegorz Kulewski
2004-04-07 10:56 ` Ralf Hildebrandt
[not found] ` <20040407105522.GN20293@charite.de>
2004-04-07 11:03 ` Grzegorz Kulewski
2004-04-07 11:06 ` Ralf Hildebrandt
2004-04-07 11:31 ` Grzegorz Kulewski [this message]
2004-04-09 14:12 ` R. J. Wysocki
2004-04-09 16:30 ` Grzegorz Kulewski
2004-04-07 11:21 ` R. J. Wysocki
2004-04-07 11:30 ` Vojtech Pavlik
2004-04-15 18:54 ` Ralf Hildebrandt
2004-04-15 19:47 ` Vojtech Pavlik
2004-04-07 10:47 ` Meelis Roos
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.0404071324050.10871@alpha.polcom.net \
--to=kangur@polcom.net \
--cc=Ralf.Hildebrandt@charite.de \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).