[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <4A1326C5.4010308@acm.org>
Date: Tue, 19 May 2009 16:38:13 -0500
From: Corey Minyard <minyard@....org>
To: Ferenc Wagner <wferi@...f.hu>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
openipmi-developer@...ts.sourceforge.net,
linux-kernel@...r.kernel.org, dann frazier <dannf@...com>
Subject: Re: [Openipmi-developer] modprobe ipmi_si hangs under 2.6.30-rc5
Ferenc Wagner wrote:
> Corey Minyard <minyard@....org> writes:
>
>
Sorry, I've been slow, but I just got back from a week out of the
country and I'm trying to catch up.
>
>
> I tried your patch on top of 2.6.30-rc6. Unfortunately it did not
> help (nor made /proc/ipmi/ipmi0 appear at least).
>
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.
>
>>> When loading with debug options, it still produces insane amount of
>>> debug messages continuously (first 671 lines of it attached).
>>>
>> Yes, full debugging generates a ton of output, it logs everything it does
>> in that case.
>>
>
> 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 :(.
-corey
View attachment "ipmi-fix-channel_init_with_ipmi_v1_0.patch" of type "text/x-diff" (1694 bytes)
Powered by blists - more mailing lists