Re: PROBLEM: modprobe hang at startup (3.8.x, 3.9.x, IBM x3550)

2013-05-14 Thread Robert Norris
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 h

Re: PROBLEM: modprobe hang at startup (3.8.x, 3.9.x, IBM x3550)

2013-05-15 Thread Robert Norris
Hi Jean, On Wed, May 15, 2013 at 11:20:44AM +0200, Jean Delvare wrote: > Thanks a lot for reporting and even more for bisecting it, I know it > takes time. I apologize for the trouble. I suppose I should have been > a bit more cautious with the 63xxESB chips as they are a different > family of har

Re: PROBLEM: modprobe hang at startup (3.8.x, 3.9.x, IBM x3550)

2013-05-15 Thread Robert Norris
On Wed, May 15, 2013 at 09:49:23PM +0200, Jean Delvare wrote: > > Interrupt: pin B routed to IRQ 0 > > Hmm, this "IRQ 0" is quite odd. I'm wondering if this could be the > reason for this hang. Was it with the i2c-i801 driver loaded, or > blacklisted? Please check if it makes a difference. Th

Re: PROBLEM: modprobe hang at startup (3.8.x, 3.9.x, IBM x3550)

2013-05-17 Thread Robert Norris
On Fri, May 17, 2013 at 10:36:22AM +0200, Jean Delvare wrote: > IPMI is still likely to access the SMBus controller. If there's a BMC > in the machine, it can also access the SMBus slave with its own > controller. It would be good to rule this out by disabling IPMI > completely, removing the BMC fr

Re: PROBLEM: modprobe hang at startup (3.8.x, 3.9.x, IBM x3550)

2013-05-17 Thread Robert Norris
On Fri, May 17, 2013 at 05:54:33PM +0800, Daniel Kurtz wrote: > Was Robert able to get the system working without hangs by disabling > the IRQ feature of i2c-i801 module when it was builtin? Yes. There are no hangs when interrupts are explicitly disabled with disable_features=0x10 or when 6676a847

Re: PROBLEM: modprobe hang at startup (3.8.x, 3.9.x, IBM x3550)

2013-05-17 Thread Robert Norris
On Fri, May 17, 2013 at 10:49:28AM +0200, Jean Delvare wrote: > Hmm, can you please dump the PCI configuration space of the SMBus > controller? > > # /sbin/lspci -s 00:1f.3 -xxx 00:1f.3 SMBus: Intel Corporation 631xESB/632xESB/3100 Chipset SMBus Controller (rev 09) 00: 86 80 9b 26 41 05 80 02 09

Re: PROBLEM: modprobe hang at startup (3.8.x, 3.9.x, IBM x3550)

2013-05-17 Thread Robert Norris
On Fri, May 17, 2013 at 10:36:22AM +0200, Jean Delvare wrote: > IPMI is still likely to access the SMBus controller. If there's a BMC > in the machine, it can also access the SMBus slave with its own > controller. It would be good to rule this out by disabling IPMI > completely, removing the BMC fr

Re: PROBLEM: All CPUs in soft lockup

2013-03-27 Thread Robert Norris
On Wed, Mar 27, 2013, at 02:42 PM, li guang wrote: > seems tasks are hogging your cpu/memory resource, did you check status > your servicing processes? According to my monitoring I have plenty of CPU and memory free at the time the problem occurs. What specifically are you looking at the data I pr

Re: PROBLEM: All CPUs in soft lockup

2013-03-27 Thread Robert Norris
On Wed, Mar 27, 2013 at 12:55:41PM +1100, Robert Norris wrote: > The console shows a new "BUG: soft lockup" line every few seconds Looking closer, the whole thing starts with a _hard_ lockup. 2013-03-26T08:33:39.921834-04:00 imap30 kernel: [185090.090328] Watchdog detected hard