public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Stian Jordet <liste@jordet.nu>
Cc: linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: Re: i2c_adapter i2c-0: Bus collision!
Date: Thu, 8 Jan 2004 23:05:59 +0100	[thread overview]
Message-ID: <20040108230559.05a5674c.khali@linux-fr.org> (raw)
In-Reply-To: <1073527236.624.7.camel@buick>

> i2c_adapter i2c-0: Bus collision! SMBus may be locked until next hard
> reset. (sorry!)
> 
> Kernel 2.6.0 with lm-sensors 2.8.2.

Are you able to reproduce the same behavior with kernel 2.4.24 and
lm-sensors 2.8.2?

> I get very weird results, especially on the fan, but others as well.
> Here are three runs of sensors:
> (...)

Could you provide a few outputs of "i2cdump 0 0x2d"? I wonder if this
will show read errors (as "XX") or simply changing values.

Does your BIOS provide a feature such as "Circle Of Protection" or
anything that sounds like "active" hardware monitoring? Is it enabled?

If you have any other chips (eeproms for example) on the bus, do you
observe similar behavior with these?

> It works fine with MBM in Windows. Well, MBM is having some troubles
> with the temperature (it gets lower and lower as time pass, and ends
> on about 8-9 degrees celsius. But fan and temperatures are read just
> fine, never any glitch. On thing thing though, the Vcore2 is 1,70. The
> Bios reports it correctly, but both MBM and LM-sensors says 1,50. Have
> no idea why. The 1,50 is static, never changes, while VCore1 (which
> ideally should be 1,75) varies from 1,75 to 1,79. In the BIOS both
> seem sane, and varies with 3-4 degrees.
> 
> I guess all these problems are because of the bus collision, which I
> have read usually happens because of bad boards. Which I admit that I
> do have, but it works in Windows :(

Which motherboard is it?

Did you have to enable any particular option in MBM?

> What are the most common reasons for the bus collisions (...)?

Bad brakes?

Just kidding... ;)

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

  reply	other threads:[~2004-01-08 22:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-08  2:00 i2c_adapter i2c-0: Bus collision! Stian Jordet
2004-01-08 22:05 ` Jean Delvare [this message]
2004-01-10  4:06   ` Stian Jordet
2004-01-17  2:00     ` Stian Jordet
2004-01-17  8:48       ` Jean Delvare
2004-01-19 14:08         ` Stian Jordet
2005-01-11 16:44         ` Stian Jordet
2005-01-12 20:23           ` Jean Delvare
2005-01-12 20:41             ` Stian Jordet

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=20040108230559.05a5674c.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liste@jordet.nu \
    --cc=sensors@stimpy.netroedge.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