linux-kernel - Re: [Openipmi-developer] modprobe ipmi

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87iqjxzjz4.fsf@tac.ki.iif.hu>
Date:	Tue, 19 May 2009 08:26:39 +0200
From:	Ferenc Wagner <wferi@...f.hu>
To:	minyard@....org
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	openipmi-developer@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org
Subject: Re: [Openipmi-developer] modprobe ipmi_si hangs under 2.6.30-rc5

Corey Minyard <minyard@....org> writes:

> On Mon, May 18, 2009 at 07:33:23PM +0200, Ferenc Wagner wrote:
>> Andrew Morton <akpm@...ux-foundation.org> writes:
>> 
>>> Well there have only been a handful of changes to ipmi since 2.6.29. 
>>> Could you try a mini-bisection?
>>>
>>> Apply revert-1.patch, test
>>> Apply revert-2.patch, test
>>> Apply revert-3.patch, test
>>> Apply revert-4.patch, test
>> 
>> After applying revert-1.patch, modprobe runs OK:
>> 
>> [   86.968156] IPMI System Interface driver.
>> [   86.976276] ipmi_si: Trying SMBIOS-specified smic state machine at i/o address 0xecf4, slave address 0x20, irq 0
>> [   87.117630] ipmi: Found new BMC (man_id: 0x0002a2,  prod_id: 0x0000, dev_id: 0x00)
>> [   87.133078] IPMI smic interface initialized
>> 
>> I guess there's no point in trying the rest.
>
> I think I see the problem.  Can you try the patch at the end of the
> email?  I can't test it because I don't have an IPMI 1.0 sytem.

I tried your patch on top of 2.6.30-rc6.  Unfortunately it did not
help (nor made /proc/ipmi/ipmi0 appear at least).

>> 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?
-- 
Thanks,
Feri.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/