From: Jean Delvare <khali@linux-fr.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Stephen Hemminger <shemminger@vyatta.com>, linux-kernel@vger.kernel.org
Subject: Re: [bug] CONFIG_I2C_VIAPRO=y breaks skge
Date: Thu, 29 Jan 2009 16:14:18 +0100 [thread overview]
Message-ID: <20090129161418.5ced2911@hyperion.delvare> (raw)
In-Reply-To: <20090129142759.GR24391@elte.hu>
On Thu, 29 Jan 2009 15:27:59 +0100, Ingo Molnar wrote:
>
> * Jean Delvare <khali@linux-fr.org> wrote:
> > This VIA chipset is the bridge over which the bugs run. Blaming on it
> > for the problem you've hit would be similar to blaming the USB host
> > controller driver for a bug that is in the USB keyboard or mouse driver.
> >
> > The "other I2C drivers" don't run frequently at all now that you've
> > disabled i2c-viapro. Without an I2C bus to probe on the machine, these
> > drivers don't do anything.
>
> ah, okay - i see - what i thought to be a surgical workaround has cut off
> the whole leg. Will go back to find the ailing muscle instead.
Exactly.
> > So, again, if you are still willing to help me solve the problem, please
> > boot the bad kernel and run:
> >
> > $ ls -l /sys/bus/i2c/devices/*/driver
> >
> > Then we'll know which drivers attached to I2C devices on your SMBus.
> > Figuring out which one shouldn't have will likely be straightforward.
>
> will take some time - but i'll revisit it.
>
> Could you give me a short list of I2C driver .config options i should
> disable one by one (instead of viapro) ?
I can't tell you before you give me the output of
ls -l /sys/bus/i2c/devices/*/driver
for the broken system.
--
Jean Delvare
prev parent reply other threads:[~2009-01-29 15:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 15:13 [bug] CONFIG_I2C_VIAPRO=y breaks skge Ingo Molnar
2009-01-27 15:27 ` Jean Delvare
2009-01-27 15:44 ` Ingo Molnar
2009-01-27 17:26 ` Jean Delvare
2009-01-29 13:49 ` Ingo Molnar
2009-01-29 14:15 ` Jean Delvare
2009-01-29 14:27 ` Ingo Molnar
2009-01-29 15:14 ` Jean Delvare [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=20090129161418.5ced2911@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=shemminger@vyatta.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