All of lore.kernel.org
 help / color / mirror / Atom feed
From: rhirst@levanta.com (Richard Hirst)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] i801_smbus 0000:00:1f.3: Bus collision!
Date: Thu, 08 Sep 2005 17:51:34 +0000	[thread overview]
Message-ID: <20050908155100.GL8392@levanta.com> (raw)
In-Reply-To: <20050907213603.GW8392@levanta.com>

On Thu, Sep 08, 2005 at 09:56:29AM -0400, Yani Ioannou wrote:
> The bus collisions are expected - both the IPMI BMC (not bmcsensors
> directly) and the i2c modules you have loaded are competing for the
> smbus. However although I've done this (loaded both bmcsensors and i2c
> modules and got bus collisions) its never resulted in a lockup.

The code does this in i801_check_hststs():

        } else if (d->hststs & 0x08) {
                entry->result = -EIO;
                dev_err(&I801_dev->dev, "Bus collision!\n");
                /* Clock stops and slave is stuck in mid-transmission */
        } else if (d->hststs & 0x04) {

and on return from i801_check_hststs() can continue to poke at the
hardware.  That presumably breaks both this transaction and whatever
one it clashed with.  I'd taken the "slave is stuck" comment to be
pretty serious, and assumed this was a "shouldn't happen" error
condition.  Wouldn't it make more sense to use a semaphore or similar
to avoid even attempting the second transaction when the first is
in progress?

Richard


  parent reply	other threads:[~2005-09-08 17:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-07 23:36 [lm-sensors] i801_smbus 0000:00:1f.3: Bus collision! Richard Hirst
2005-09-08  2:06 ` Mark M. Hoffman
2005-09-08  9:54 ` Richard Hirst
2005-09-08 16:25 ` Yani Ioannou
2005-09-08 17:34 ` Richard Hirst
2005-09-08 17:51 ` Richard Hirst [this message]
2005-09-08 18:57 ` Mark M. Hoffman
2005-09-08 19:09 ` Yani Ioannou
2005-09-08 19:12 ` Mark M. Hoffman
2005-09-08 20:51 ` Richard Hirst

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=20050908155100.GL8392@levanta.com \
    --to=rhirst@levanta.com \
    --cc=lm-sensors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.