Messages in this thread | | | Date | Wed, 15 May 2013 09:16:26 +1000 | From | Robert Norris <> | Subject | Re: PROBLEM: modprobe hang at startup (3.8.x, 3.9.x, IBM x3550) |
| |
On Mon, May 13, 2013 at 11:22:32AM +1000, Robert Norris wrote: > We have a number of Intel x3550 servers (Intel 5000-series). They've > been running 3.7.2 fine. > > In the last week I've run 3.8.11, 3.8.12 and 3.9.2 on them. All have > long hangs at boot, and later hung tasks in modprobe.
I bisected this and tracked it to this commit:
commit 6676a847d48ac48908cf467b42da9045b5463a6e Author: Jean Delvare <khali@linux-fr.org> Date: Sun Dec 16 21:11:55 2012 +0100
i2c-i801: Enable interrupts for all post-ICH5 chips
I did not receive a single bug report after interrupt support was added for a limited number of chips. So I'd say the code is good and should be enabled for all supported chips, that is: ICH5 and later.
Signed-off-by: Jean Delvare <khali@linux-fr.org> Reviewed-by: Daniel Kurtz <djkurtz@chromium.org>
I've tested by building 3.9.2 with that single commit reverted, and it boots without issue.
According to lspci I have:
00:1f.3 SMBus: Intel Corporation 631xESB/632xESB/3100 Chipset SMBus Controller (rev 09)
Which has PCI ID 0x269b (ie PCI_DEVICE_ID_INTEL_ESB2_17).
For now I will either revert this commit in my kernel builds or blacklist the module on these machines (I haven't decided which I prefer yet).
Obviously, I can reproduce this reliably, and am happy to test.
Cheers, Rob N.
| |