From: Robert Norris <robn@opera.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: Daniel Kurtz <djkurtz@chromium.org>,
linux-kernel@vger.kernel.org,
Linux I2C <linux-i2c@vger.kernel.org>
Subject: Re: PROBLEM: modprobe hang at startup (3.8.x, 3.9.x, IBM x3550)
Date: Fri, 17 May 2013 22:18:19 +1000 [thread overview]
Message-ID: <20130517121819.GA3165@pyro.melbourne.osa> (raw)
In-Reply-To: <20130517103622.5000d277@endymion.delvare>
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 from the machine if it has one, and
> checking if it makes the issue go away or not.
This ended up being easier than I thought. The BMC can't be physically
removed, but there is a jumper on the board to disable it. We flipped it
and got a message during POST about it not being present. Additionally
all IPMI functions did nothing (hung, but interruptable) which is what
you'd expect. I think it really is disabled.
In this state, I re-ran the previous tests, with identical results. That
is:
- "modprobe i2c_i801" succeeds
- "modprobe i2c_i801 disable_features=0x10" succeeds
- With interrupts disabled, "modprobe ics932s401"
- With interrupts enabled, "modprobe ics932s401" hangs
- With interrupts enabled, "i2cget 4 0x50 0x00" hangs
I'll leave the BMC disabled for now in case that's important for further
testing. If you need other tests run with the BMC enabled, I'll use a
differen machine.
Cheers,
Rob.
next prev parent reply other threads:[~2013-05-17 12:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 1:22 PROBLEM: modprobe hang at startup (3.8.x, 3.9.x, IBM x3550) Robert Norris
2013-05-14 23:16 ` Robert Norris
2013-05-15 9:20 ` Jean Delvare
2013-05-15 11:27 ` Robert Norris
2013-05-15 19:49 ` Jean Delvare
2013-05-16 3:44 ` Robert Norris
2013-05-17 8:36 ` Jean Delvare
2013-05-17 9:22 ` Martin Mokrejs
2013-05-17 9:47 ` Jean Delvare
2013-05-17 9:54 ` Daniel Kurtz
2013-05-17 10:26 ` Robert Norris
2013-05-17 10:24 ` Robert Norris
2013-05-17 12:18 ` Robert Norris [this message]
2013-05-17 8:49 ` Jean Delvare
2013-05-17 10:27 ` Robert Norris
2013-05-17 10:56 ` Jean Delvare
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130517121819.GA3165@pyro.melbourne.osa \
--to=robn@opera.com \
--cc=djkurtz@chromium.org \
--cc=khali@linux-fr.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox