Jiri Kosina wrote:
> On Thu, 12 Apr 2007, Jiri Kosina wrote:
>
>   
>> CONFIG_IPMI_SI=y
>> hangs upon boot on the already mentioned printk from ipmi_si. With
>> CONFIG_IPMI_SI=m
>> the boot succeeds. When manually trying to modprobe ipmi_si after that, 
>> the modprobe itself hangs, but the machine remains usable otherwise.
>>     
>
> Actually, after approximately 6 minutes 30 seconds, the modprobe finishes 
> with -ENODEV and the following is spitted into dmesg:
>
> ipmi_si: There appears to be no BMC at this location
> ACPI: PCI interrupt for device 0000:02:00.4 disabled
> ipmi_si: Unable to find any System Interface(s)
>
> Anyway I just checked that I get precisely the same behavior with plain 
> 2.6.21-rc6, so we can rule out -mm with this issue.
>
> It's possible that this system has some broken KCS. I will try to narrow 
> this down.
>   
My guess is that this system spaces out its KCS registers, but there 
appears to be no way to specify register spacing or offsets with PCI.  
That would mean that the configuration register appears operational to 
the driver, but the data register is returning bogus data.  Thus it 
appears "sort of" working to the driver, and it takes a long time to 
time out.

I'm pretty sure it's possible to test to figure out where the registers 
are really located.  However, I have no way to test this change.  All 
the other configuration methods have a way to discover this information.

Jiri, we should probably take this offline if you want to continue to 
work on it.

Thanks,

-corey

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to