From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: hid-dummy.ko Input/output error -- causing huge delays
Date: Wed, 4 Mar 2009 15:59:58 -0800 [thread overview]
Message-ID: <43e72e890903041559s4bfce44as5a2071f71d47ae15@mail.gmail.com> (raw)
In-Reply-To: <49AE4A2E.8090300@gmail.com>
On Wed, Mar 4, 2009 at 1:30 AM, Jiri Slaby <jirislaby@gmail.com> wrote:
> On 4.3.2009 02:38, Luis R. Rodriguez wrote:
>>
>> Well now I see FC10 say its starting udev and it just sits there
>> waiting for the same period of time so maybe it was that (?). But at
>> the console the hid-dummy is not the last message I see now, but I
>> guess I wouldn't because it returns 0 now huh.
>
> Sorry, I'm totally confused now :). What you wouldn't?
Hm?
Let me explain what I am concluding:
Whether or not return -EIO is used for the hid_dummy on my FC10 box I
get huge delay during bootup when starting udev. It sits there and
says:
Starting udev:
If hid-dummy return -EIO then immediately afterwards I see the error
for inserting it with the EIO error explained:
FATAL: Error inserting hid_dummy
(/lib/modules/2.6.29-rc7-wl/kernel/drivers/hid/hid-dummy.ko):
Input/output error
> Actually I saw similar behavior on one of my boxes. I'll recheck if it is
> still present.
Oh nice. Yeah so the huge delay seems to be unrelated to hid-dummy.
Luis
prev parent reply other threads:[~2009-03-05 0:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 1:37 hid-dummy.ko Input/output error -- causing huge delays Luis R. Rodriguez
2009-03-03 1:51 ` Luis R. Rodriguez
2009-03-03 11:43 ` Jiri Slaby
2009-03-04 0:07 ` Luis R. Rodriguez
2009-03-04 1:38 ` Luis R. Rodriguez
2009-03-04 9:30 ` Jiri Slaby
2009-03-04 23:59 ` Luis R. Rodriguez [this message]
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=43e72e890903041559s4bfce44as5a2071f71d47ae15@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=jirislaby@gmail.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;
as well as URLs for NNTP newsgroup(s).