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 Jean Delvare
On Fri, 17 May 2013 20:27:06 +1000, Robert Norris wrote: > 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

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 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: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 Daniel Kurtz
On Fri, May 17, 2013 at 4:36 PM, Jean Delvare wrote: > Hi Robert, > > On Thu, 16 May 2013 13:44:55 +1000, Robert Norris wrote: >> 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 thi

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

2013-05-17 Thread Jean Delvare
On Fri, 17 May 2013 11:22:17 +0200, Martin Mokrejs wrote: > Hi, > while you are chasing some problem with i2c_801 I would like to mention > that I never got an answer on the thread https://lkml.org/lkml/2013/1/23/405 > about a kmemleak reported by kernel . Maybe this could give you a hint? > If t

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

2013-05-17 Thread Martin Mokrejs
Hi, while you are chasing some problem with i2c_801 I would like to mention that I never got an answer on the thread https://lkml.org/lkml/2013/1/23/405 about a kmemleak reported by kernel . Maybe this could give you a hint? If these do not overlap I would be anyways glad to receive an answer via

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

2013-05-17 Thread Jean Delvare
On Thu, 16 May 2013 13:44:55 +1000, Robert Norris wrote: > > Then do a simple read from a random address > > with: > > # i2cget 4 0x50 0x00 > > (Adjust the bus number as needed.) > > I am curious if this will hang as well or only when accessing the > > clock chip at address 0x69. > > Yep

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

2013-05-17 Thread Jean Delvare
Hi Robert, On Thu, 16 May 2013 13:44:55 +1000, Robert Norris wrote: > 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-i

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-15 Thread Jean Delvare
Robert, On Wed, 15 May 2013 21:27:41 +1000, Robert Norris wrote: > On Wed, May 15, 2013 at 11:20:44AM +0200, Jean Delvare wrote: > > Can you share the full output of lspci -s 00:1f.3 -vv? > > 00:1f.3 SMBus: Intel Corporation 631xESB/632xESB/3100 Chipset SMBus > Controller (rev 09) > Subsyste

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 Jean Delvare
Hi Robert, Adding the linux-i2c list to Cc. On Wed, 15 May 2013 09:16:26 +1000, Robert Norris wrote: > 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'v