From: Fernando Paredes <Fernando.Paredes@Sun.COM>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Toshiba keyboard lockups
Date: Wed, 09 Jun 2004 16:58:36 -0500 [thread overview]
Message-ID: <40C7880C.4000401@sun.com> (raw)
In-Reply-To: <200405121149.37334.rjwysocki@sisk.pl>
In case anyone's interested...
Applied these patches. Nothing while tail'ing /var/log/messages. Nothing
in the root console that I can see either.
Patched the source to 2.6.6. Still get the same lockups, totally random.
Any more ideas?
- Fernando
R. J. Wysocki wrote:
>On Wednesday 12 of May 2004 01:33, Fernando Paredes wrote:
>
>
>>There was a previous thread on this, last month.
>>
>>I updated to 2.6.6 and I still get these random lockups. Nothing in
>>dmesg or /var/log/messages. Too annoying as I have to reboot the machine
>>constantly. Does anyone know the status on this? Is t a toshiba hardware
>>bug (is that possible?) or a bug in serio.c or keybd.c?
>>
>>
>
>It's most probably Toshiba-related, because it does not happen on other
>hardware, it seems.
>
>I've got a simple patch from Grzegorz Kulewski to help trace the problem, but
>I haven't got a lockup since. The patch is as follows:
>
>--- /usr/src/linux-2.6.5/drivers/input/serio/serio.c.orig 2004-04-04
>05:36:15.000000000 +0200
>+++ /usr/src/linux-2.6.5/drivers/input/serio/serio.c 2004-04-09
>18:28:50.268521936 +0200
>@@ -166,6 +166,11 @@ static int serio_thread(void *nothing)
> static void serio_queue_event(struct serio *serio, int event_type)
> {
> struct serio_event *event;
>+
>+ if (event_type == SERIO_RESCAN || event_type == SERIO_RECONNECT) {
>+ printk(KERN_WARNING "serio: RESCAN || RECONNECT requested: %d!\n",
>event_type);
>+ dump_stack();
>+ }
>
> if ((event = kmalloc(sizeof(struct serio_event), GFP_ATOMIC))) {
> event->type = event_type;
>
>Please try to apply it and you should get something in the logs when a lockup
>occurs (ie. kernel warning + call trace).
>
>RJW
>
>-
>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/
>
>
>
--
<http://www.sun.com/software> <http://java.sun.com>
*Fernando Paredes
Identity & Collaboration
Sun Microsystems de México
Prol. Reforma #600-110, Col. Santa Fe, México D.F. 01210
Tel Dir: 52 + (55) 5258 6152
Fax: 52 + (55) 5258 6199*
next prev parent reply other threads:[~2004-06-09 21:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 23:33 Toshiba keyboard lockups Fernando Paredes
2004-05-12 9:49 ` R. J. Wysocki
2004-06-09 21:58 ` Fernando Paredes [this message]
2004-06-10 19:15 ` Oleg Drokin
2004-06-10 20:46 ` Jason Munro
2004-06-10 22:05 ` Fernando Paredes
2004-07-06 8:48 ` Ralf Hildebrandt
2004-07-12 9:20 ` Ralf Hildebrandt
2004-06-15 7:51 ` Sean Legassick
2004-06-17 22:37 ` Gabriel Lavoie
2004-06-19 18:36 ` Vojtech Pavlik
2004-06-19 19:48 ` 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=40C7880C.4000401@sun.com \
--to=fernando.paredes@sun.com \
--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