On Thu, 12 Apr 2007, Jiri Kosina wrote: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.
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.