From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Alan Jenkins <sourcejedi.lkml@googlemail.com>,
Matthew Garrett <mjg59@srcf.ucam.org>,
mingo@elte.hu
Subject: Re: EeePC 900 trackpad often not detected at boot in 2.6.30-rc4
Date: Wed, 20 May 2009 06:47:39 +0100 [thread overview]
Message-ID: <20090520054739.GA31552@sucs.org> (raw)
In-Reply-To: <20090520024658.GD17649@dtor-d630.eng.vmware.com>
On Tue, May 19, 2009 at 07:47:08PM -0700, Dmitry Torokhov wrote:
>
> It is just unfortunate scheduling that messes us up:
The really frustrating thing is that for a time this was happening quite
consistently leading me to believe it was a kernel issue...
> > [ 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.
It's worth noting that this kernel is stuffed full of debugging options
as is running on an EeePC 900 with 900Mhz Celeron. I am also using the
following boot parameters:
root=/dev/sdb2 cfg80211.ieee80211_regdom=GB usb_storage.delay_use=0
cfg80211 pcie_aspm=force pcie_aspm.policy=powersave fastboot ro
rootfstype=ext2
> In the meantime, the patch below should fix work around that delay.
This one could be tough to test unless there is a way of forcing the
awkward scheduling...
--
Sitsofe | http://sucs.org/~sits/
next prev parent reply other threads:[~2009-05-20 5:47 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 [this message]
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
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=20090520054739.GA31552@sucs.org \
--to=sitsofe@yahoo.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mjg59@srcf.ucam.org \
--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).