From: Corey Minyard <minyard@acm.org>
To: Ferenc Wagner <wferi@niif.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
openipmi-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [Openipmi-developer] modprobe ipmi_si hangs under 2.6.30-rc5
Date: Wed, 20 May 2009 11:34:11 -0500 [thread overview]
Message-ID: <4A143103.9050302@acm.org> (raw)
In-Reply-To: <87ljoriwcw.fsf@tac.ki.iif.hu>
Ferenc Wagner wrote:
> Corey Minyard <minyard@acm.org> writes:
>
>
>> I know what is happening now. Can you try the attached patch? I'm
>> disabling the requeue and discarding the message when an IPMB message
>> is received before everything is initialized. If you don't, the code
>> will not deliver any messages because something is already in the
>> queue.
>>
>
> Yep, that fixed it, modprobe runs through now!
>
Thanks for testing this.
>
>> Ferenc Wagner wrote:
>>
>>
>>> My concern is that it does something too often, not letting the CPU
>>> enter deep sleep states, perhaps. Or is that also an artifact of
>>> debugging?
>>>
>> No, it's an artifact of a lousy hardware interface. Very few IPMI
>> interfaces support interrupts, so they have to be polled :(.
>>
>
> I'd say this isn't an artifact but the sad truth itself. Just out of
> interest, how often does the driver wake up to check the inteface?
>
I'd have to agree.
When idle, the driver wakes up every 10ms to check for something on the
driver. When a message is in transit, it's every jiffie.
-corey
next prev parent reply other threads:[~2009-05-20 16:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 21:28 modprobe ipmi_si hangs under 2.6.30-rc5 Ferenc Wagner
2009-05-17 0:09 ` Andrew Morton
2009-05-18 17:33 ` Ferenc Wagner
2009-05-18 18:40 ` [Openipmi-developer] " Corey Minyard
2009-05-19 6:26 ` Ferenc Wagner
2009-05-19 21:38 ` Corey Minyard
2009-05-20 16:15 ` Ferenc Wagner
2009-05-20 16:34 ` Corey Minyard [this message]
2009-05-21 9:47 ` Ferenc Wagner
2009-05-21 12:37 ` Corey Minyard
2009-05-27 12:10 ` Bela Lubkin
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=4A143103.9050302@acm.org \
--to=minyard@acm.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=wferi@niif.hu \
/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).