linux-kernel - Re: [bug] CONFIG_I2C

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090129134916.GK24391@elte.hu>
Date:	Thu, 29 Jan 2009 14:49:16 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Jean Delvare <khali@...ux-fr.org>
Cc:	Stephen Hemminger <shemminger@...tta.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [bug] CONFIG_I2C_VIAPRO=y breaks skge


* Jean Delvare <khali@...ux-fr.org> wrote:

> > > What I2C chip drivers did you include in your kernel? Presumably 
> > > this is a random config, so I can imagine that there is a chip on 
> > > the SMBus to which an I2C chip driver would have bound and that is 
> > > causing the problem, rather than i2c-viapro itself.
> > 
> > Correct, i found it via random config testing. x86 defconfig + VIAPRO 
> > enabled boots fine so it indeed could be interaction between i2c 
> > drivers.
> 
> Is there anything like a x86 defconfig? I didn't know. [...]

Yes. Type "make defconfig" in the kernel source top directory, on an x86 
box.

> > Anyway, this bug is not a big deal - i can work it around locally by 
> > excluding VIAPRO on that box. If you'd like to figure out why this 
> > happens that would be preferred of course, and i can send any debug 
> > info you need.
> 
> Well my guess is that you have included an I2C chip driver with a weak 
> detection routine. More likely this is a typical case of "if it hurts, 
> don't do it". But maybe we can improve the help text or default, or even 
> disable probing for these devices.
> 
> At this point I am reasonably certain that the i2c-viapro driver is 
> innocent.

i've excluded the VIAPRO driver on that box (and only the VIAPRO driver - 
i.e. all those other I2C drivers still run frequently) - and the problem 
has not reoccured in about ~1000 bootups.

Combined with the fact that this box has a VIA chipset, does that not 
implicate the viapro driver, at least to a certain degree?

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/