From mboxrd@z Thu Jan 1 00:00:00 1970 From: rhirst@levanta.com (Richard Hirst) Date: Thu, 08 Sep 2005 20:51:30 +0000 Subject: [lm-sensors] i801_smbus 0000:00:1f.3: Bus collision! Message-Id: <20050908185048.GM8392@levanta.com> List-Id: References: <20050907213603.GW8392@levanta.com> In-Reply-To: <20050907213603.GW8392@levanta.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lm-sensors@vger.kernel.org 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: [] i801_start+0x2fd/0x375 [i2c_i801] [] i2c_start_entry+0x28/0x52 [i2c_core] [] i2c_non_blocking_op+0xbb/0xcf [i2c_core] [] start_resend+0x7d/0x99 [ipmi_smb] [] msg_done_handler+0x57/0x532 [ipmi_smb] [] printk+0xe/0x11 [] i801_block_next_byte+0xb7/0xfd [i2c_i801] [] i2c_entry_put+0x58/0x7c [i2c_core] [] i801_start+0x364/0x375 [i2c_i801] [] i2c_start_entry+0x28/0x52 [i2c_core] [] i2c_non_blocking_op+0xbb/0xcf [i2c_core] [] retry_timeout+0x47/0x6f [ipmi_smb] [] retry_timeout+0x0/0x6f [ipmi_smb] [] run_timer_softirq+0x123/0x145 [] __do_softirq+0x4c/0xb1 [] 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