The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Robert Norris <robn@opera.com>
Cc: 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 10:49:28 +0200	[thread overview]
Message-ID: <20130517104928.5b135a4f@endymion.delvare> (raw)
In-Reply-To: <20130516034455.GA19452@pyro.melbourne.osa>

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, that one hangs. The hung task handler picked it up after a few
> minutes.

Hmm, can you please dump the PCI configuration space of the SMBus
controller?

# /sbin/lspci -s 00:1f.3 -xxx

It might be that you have interrupts routed to SMI# instead of the
regular IRQ line. The driver is supposed to disable interrupt support
in that case, but I have never tested it.

Thanks,
-- 
Jean Delvare

  parent reply	other threads:[~2013-05-17  8:49 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
2013-05-17  8:49           ` Jean Delvare [this message]
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=20130517104928.5b135a4f@endymion.delvare \
    --to=khali@linux-fr.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robn@opera.com \
    /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