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 20:51:30 +0000 [thread overview]
Message-ID: <20050908185048.GM8392@levanta.com> (raw)
In-Reply-To: <20050907213603.GW8392@levanta.com>
On Thu, Sep 08, 2005 at 01:12:34PM -0400, Mark M. Hoffman wrote:
> Richard's symptoms seem to implicate the i2c-i801 and i2c-core patches.
Yeah, got a stack trace at the point where it starts recursing
down the stack:
Call Trace:
[<f89e4bb7>] i801_start+0x2fd/0x375 [i2c_i801]
[<f8a0ede6>] i2c_start_entry+0x28/0x52 [i2c_core]
[<f8a1010c>] i2c_non_blocking_op+0xbb/0xcf [i2c_core]
[<f8ea5960>] start_resend+0x7d/0x99 [ipmi_smb]
[<f8ea52d9>] msg_done_handler+0x57/0x532 [ipmi_smb]
[<c011e09c>] printk+0xe/0x11
[<f89e4680>] i801_block_next_byte+0xb7/0xfd [i2c_i801]
[<f8a0eec0>] i2c_entry_put+0x58/0x7c [i2c_core]
[<f89e4c1e>] i801_start+0x364/0x375 [i2c_i801]
[<f8a0ede6>] i2c_start_entry+0x28/0x52 [i2c_core]
[<f8a1010c>] i2c_non_blocking_op+0xbb/0xcf [i2c_core]
[<f8ea525a>] retry_timeout+0x47/0x6f [ipmi_smb]
[<f8ea5213>] retry_timeout+0x0/0x6f [ipmi_smb]
[<c012548a>] run_timer_softirq+0x123/0x145
[<c0122094>] __do_softirq+0x4c/0xb1
[<c0105db7>] do_softirq+0x41/0x48
so it looks like there is now a path where a request can fail
in i2c_start() which causes it to start the next request
which calls i2c_start() ... etc.
Pretty clear this is most likely an issue with the patches I'm
using. Thanks to you both for the helpful responses.
Richard
prev parent reply other threads:[~2005-09-08 20: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
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 [this message]
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=20050908185048.GM8392@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.