From: Michael Buesch <mb@bu3sch.de>
To: benh@kernel.crashing.org
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Powerbook shuts down hard when hot, patch found
Date: Sat, 29 Sep 2007 23:53:06 +0200 [thread overview]
Message-ID: <200709292353.06476.mb@bu3sch.de> (raw)
In-Reply-To: <1191102715.28637.0.camel@pasglop>
On Saturday 29 September 2007 23:51:55 Benjamin Herrenschmidt wrote:
>
> On Sat, 2007-09-29 at 13:22 +0200, Michael Buesch wrote:
> > On Saturday 29 September 2007 13:06:59 Michael Buesch wrote:
> > > > This is very strange... Can you try also clearing VGA_DDC_CLK_OUT_EN and
> > > > VGA_DDC_DATA_OUT_EN and the same time and see if that helps ?
> > >
> > > It still triggers the bug then.
> >
> > I tried something else.
> > I removed the write and only added a printk with a register read
> > to print the contents (DDC REG IS 0x...) . This is the result:
> >
> > [ 0.431304] PCI: Enabling device 0000:00:10.0 (0006 -> 0007)
> > [ 0.626866] radeonfb (0000:00:10.0): Invalid ROM signature 303 should be 0xaa55
> > [ 0.626877] radeonfb: Retrieved PLL infos from Open Firmware
> > [ 0.626887] radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=203.00 Mhz, System=392.00 MHz
> > [ 0.626897] radeonfb: PLL min 12000 max 35000
> > [ 0.627194] DDC REG IS 0x00000303
> > [ 0.763751] i2c-adapter i2c-2: unable to read EDID block.
> > [ 0.983746] i2c-adapter i2c-2: unable to read EDID block.
> > [ 1.203745] i2c-adapter i2c-2: unable to read EDID block.
> > [ 1.280001] DDC REG IS 0x00000000
> > [ 1.620189] ieee1394: Host added: ID:BUS[0-00:1023] GUID[001124fffed98036]
> > [ 1.670984] radeonfb: Monitor 1 type LCD found
> > [ 1.670992] radeonfb: EDID probed
> > [ 1.670997] radeonfb: Monitor 2 type no found
> > [ 1.671012] radeonfb: Using Firmware dividers 0x0002008e from PPLL 0
> > [ 1.671075] radeonfb: Dynamic Clock Power Management enabled
> > [ 1.712658] Console: switching to colour frame buffer device 160x53
> > [ 1.735555] radeonfb: Backlight initialized (radeonbl0)
> > [ 1.735746] radeonfb (0000:00:10.0): ATI Radeon NP
> > [ 1.738776] Generic RTC Driver v1.07
> > [ 1.738995] Macintosh non-volatile memory driver v1.1
> > ...
> >
> > Note that the function is called twice. Is that correct?
>
> Yes. That's expected, with different registers though.
>
> I don't quite get what's going on. I'll have to figure that out with ATI
> if they bother helping...
This all smells to me like a silicon bug, so I'd start searching
in the silicon erratas. But I'm not sure, of course. It's also strange
that it depends on temperature. (That's why I first expected the PMU
would cause this).
Thanks for your help.
--
Greetings Michael.
next prev parent reply other threads:[~2007-09-29 21:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 21:32 Powerbook shuts down hard when hot, patch found Michael Buesch
2007-09-28 23:04 ` Benjamin Herrenschmidt
2007-09-29 11:06 ` Michael Buesch
2007-09-29 11:22 ` Michael Buesch
2007-09-29 21:51 ` Benjamin Herrenschmidt
2007-09-29 21:53 ` Michael Buesch [this message]
2007-09-29 22:19 ` Benjamin Herrenschmidt
2007-09-29 22:26 ` Michael Buesch
2007-09-29 22:49 ` Benjamin Herrenschmidt
2007-09-30 10:13 ` Michael Buesch
2007-09-30 10:16 ` Michael Buesch
2007-10-01 8:00 ` Michel Dänzer
2007-10-01 20:58 ` Michael Buesch
2007-10-02 6:43 ` Michel Dänzer
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=200709292353.06476.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).