linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Buesch <mb@bu3sch.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Powerbook shuts down hard when hot, patch found
Date: Sun, 30 Sep 2007 08:49:05 +1000	[thread overview]
Message-ID: <1191106145.28637.11.camel@pasglop> (raw)
In-Reply-To: <200709300026.07219.mb@bu3sch.de>


On Sun, 2007-09-30 at 00:26 +0200, Michael Buesch wrote:
> On Sunday 30 September 2007 00:19:53 Benjamin Herrenschmidt wrote:
> > 
> > > 
> > > 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.
> > 
> > Could be that we are creating a short by driving the output low, thus
> > causing the silicon to heat up, but that's strange.
> 
> Well. The machine needs to be hot in the first place to trigger it.
> If it's cold it boots and runs fine even with that patch.
> Even if I run it hot after boot it does not shutdown. It only shuts down
> on boot when this register is written and when it's hot at this point.

Well, it's possible that they have a too weak pull-up resistor on those
lines, and thus when asserted to 0, a significant current goes through
causing the whole thing to heat up. That heat added to the residual heat
of a hot boot becomes then enough to trigger the temperature sensor
threshold... just one possible explanation.

> That's why I thought about some silicon bug. Why only when it's hot? :)
> 
> > Also, the other change I made you do turns these into inputs, thus the
> 
> The _EN bits are already all cleared, as you can see in my printk dump.
> So clearing them has no effect, of course.
> So the ports are Inputs as default on boot.

Hrm, that's weird then, because in that case, changing the output bits
shouldn't have any effect, unless maybe on some chips, the EN bits are
flipped. I don't have anything specific about the rv350 tho.

Can you print which specific DDC register is doing that (it's called
twice right ?) and maybe do a patch preventing that write only for one
of them and let me know if it makes a difference.

> > DDL lines should be pulled up, unless ... the board doesn't have
> > pullups.
> 
> Well, I can't tell you :)

Heh

Ben.

  reply	other threads:[~2007-09-29 22:49 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
2007-09-29 22:19           ` Benjamin Herrenschmidt
2007-09-29 22:26             ` Michael Buesch
2007-09-29 22:49               ` Benjamin Herrenschmidt [this message]
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=1191106145.28637.11.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mb@bu3sch.de \
    /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).