linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Sitsofe Wheeler <sitsofe@yahoo.com>,
	linux-kernel@vger.kernel.org,
	Alan Jenkins <sourcejedi.lkml@googlemail.com>,
	Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: EeePC 900 trackpad often not detected at boot in 2.6.30-rc4
Date: Wed, 20 May 2009 10:38:46 +0200	[thread overview]
Message-ID: <20090520083846.GH6736@elte.hu> (raw)
In-Reply-To: <20090520024658.GD17649@dtor-d630.eng.vmware.com>


* Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:

> On Mon, May 18, 2009 at 10:42:10AM +0100, Sitsofe Wheeler wrote:
> > On Mon, May 18, 2009 at 09:41:46AM +0100, Sitsofe Wheeler wrote:
> > > 
> > > And of course just as soon as I finish building a new kernel the issue
> > > disappears. Even in older kernels that were seemingly showing the
> > > problem all the time. Sigh.
> > 
> > After numerous reboots I finally managed to reproduce the problem the
> > original way with your patch installed. I have no idea what the
> > necessary triggers are but I suspect it involves suspend to ram...
> > 
> 
> It is just unfortunate scheduling that messes us up:
> 
> > [    4.267050] drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [113]
> > [    4.270440] drivers/input/serio/i8042.c: d4 -> i8042 (command) [116]
> > [    4.271016] drivers/input/serio/i8042.c: f2 -> i8042 (parameter) [116]
> > [    4.274883] ALSA device list:
> > [    4.274963]   #0: HDA Intel at 0xf7eb8000 irq 16
> > [    4.275258] TCP cubic registered
> > [    4.276597] NET: Registered protocol family 17
> > [    4.276802] Using IPI Shortcut mode
> > [    4.279191]   Magic number: 9:810:70
> > [    4.279548] rtc_cmos 00:03: setting system clock to 2009-05-18 09:03:27 UTC (1242637407)
> > [    4.281412] drivers/input/serio/i8042.c: fa <- i8042 (interrupt, 1, 12) [127]
> > [    4.283338] drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [129]
> > [    5.406620] libps2: errorneously fail 754 command
> 
> As you can see the device responded to our command and interrupt 
> fired at 4.28 but for some reason the thread did not get woken up 
> until 5.40, second and a half later... Crazy if you ask me.
> 
> Ingo, do you have any idea why would it not be woken up for so 
> long???

possibly something else was running (looping?) in that time? A more 
detailed trace would tell i guess.

	Ingo

  parent reply	other threads:[~2009-05-20  8:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-11  7:21 EeePC 900 trackpad often not detected at boot in 2.6.29-rc4 Sitsofe Wheeler
2009-05-13  3:20 ` Dmitry Torokhov
2009-05-13 18:53   ` EeePC 900 trackpad often not detected at boot in 2.6.30-rc4 Sitsofe Wheeler
2009-05-13 19:19     ` Sitsofe Wheeler
2009-05-16  3:27       ` Dmitry Torokhov
2009-05-16  3:29         ` Dmitry Torokhov
2009-05-18  8:41           ` Sitsofe Wheeler
2009-05-18  9:42             ` Sitsofe Wheeler
2009-05-20  2:47               ` Dmitry Torokhov
2009-05-20  5:47                 ` Sitsofe Wheeler
2009-05-20  7:25                   ` Dmitry Torokhov
2009-05-26 22:20                     ` Sitsofe Wheeler
2009-05-28 15:54                       ` Dmitry Torokhov
2009-05-28 16:42                         ` Sitsofe Wheeler
2009-05-28 16:49                           ` Dmitry Torokhov
2009-05-29  9:31                             ` Sitsofe Wheeler
2009-05-29 14:39                               ` Dmitry Torokhov
2009-05-20  8:38                 ` Ingo Molnar [this message]
2009-05-26 22:14                   ` Sitsofe Wheeler

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=20090520083846.GH6736@elte.hu \
    --to=mingo@elte.hu \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=sitsofe@yahoo.com \
    --cc=sourcejedi.lkml@googlemail.com \
    /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).