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: Tue, 3 Mar 2009 17:38:32 -0800 [thread overview]
Message-ID: <43e72e890903031738w12a726d4ga3f998d8e4263a73@mail.gmail.com> (raw)
In-Reply-To: <43e72e890903031607k4e2ce36csb7c48de2f01a6de6@mail.gmail.com>
On Tue, Mar 3, 2009 at 4:07 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> On Tue, Mar 3, 2009 at 3:43 AM, Jiri Slaby <jirislaby@gmail.com> wrote:
>> On 3.3.2009 02:51, Luis R. Rodriguez wrote:
>>>
>>> On Mon, Mar 2, 2009 at 5:37 PM, Luis R. Rodriguez<mcgrof@gmail.com>
>>> wrote:
>>>>
>>>> FATAL: Error inserting hid_dummy
>>>> (/lib/modules/2.6.29-rc6-wl/kernel/drivers/hid/hid-dummy.ko):
>>>> Input/output error
>>>>
>>>> I remember reading a thread where you said this was non-fatal and that
>>>> hid-dummy.ko would go away. On my system, every now in a blue moon the
>>>> above causes a huge delay during the bootup sequence. I'm talking
>>>> about a full 1-2 minute delay. Why is the delay so sporadic?
>>>
>>> s/once in a blue moon/often/
>>>
>>> as it seems I get this now upon every reboot.
>>
>> So I suppose the problem goes away, when you change -EIO to 0 in
>> drivers/hid/hid-dummy.c
>
> Yeap.
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.
Luis
next prev parent reply other threads:[~2009-03-04 1:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 1:37 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 [this message]
2009-03-04 9:30 ` Jiri Slaby
2009-03-04 23:59 ` Luis R. Rodriguez
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=43e72e890903031738w12a726d4ga3f998d8e4263a73@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
all inboxes | Powered by JetHome®