[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071124232035.0f46d530@hyperion.delvare>
Date: Sat, 24 Nov 2007 23:20:35 +0100
From: Jean Delvare <khali@...ux-fr.org>
To: Michael Buesch <mb@...sch.de>
Cc: benh@...nel.crashing.org,
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.
On Sat, 24 Nov 2007 15:18:26 +0100, Michael Buesch wrote:
> On Friday 23 November 2007 23:29:28 Jean Delvare wrote:
> > Out of curiosity, what kind of crash was it? I admit that I can't see
> > how the code could crash.
>
> It's not the code that crashes. It's the hardware that turns off the machine.
> It only happens if I boot the machine and only if it's hot at this
> time. Some hardware will turn off the hardware two or three seconds
> after the radeon driver was loaded.
> It seems to be some overheating protection that's going crazy.
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 :)
--
Jean Delvare
-
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/
Powered by blists - more mailing lists