linux-kernel - Re: radeonfb i2c regression post-2.6.18.

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] [day] [month] [year] [list]

Message-Id: <1195943135.7195.61.camel@pasglop>
Date:	Sun, 25 Nov 2007 09:25:35 +1100
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Jean Delvare <khali@...ux-fr.org>
Cc:	Michael Buesch <mb@...sch.de>,
	Roger Leigh <rleigh@...nlatter.ukfsn.org>,
	linux-kernel@...r.kernel.org, Dennis Munsie <dmunsie@...ropia.com>
Subject: Re: radeonfb i2c regression post-2.6.18.


> Very strange indeed. Another possibility is that there is a hardware
> monitoring chip connected to one of the Radeon adapter's I2C buses, and
> that holding the I2C lines prevents reading from it, so whatever is
> responsible for controlling the temperature prefers to play it safe and
> shuts everything down. Somehow it seems more realistic than an actual
> overheating (3 seconds is a very short period of time for that), but
> we'd need the exact schematics of the hardware, and the details of the
> thermal control system, to validate this theory.
> 
> Anyway, no need to worry anymore now that the bug is fixed :)

Actually, that's a possibility yes, though generally Apple put all temp.
monitoring chips elsewhere, it could well be the case.

Ben.


-
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/