From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Michael Buesch <mb@bu3sch.de>,
linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>
Subject: Re: Latest linus GIT freezes on my G4
Date: Fri, 07 Apr 2006 08:29:14 +0200 [thread overview]
Message-ID: <1144391354.30891.28.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0604021309560.3050@g5.osdl.org>
On Sun, 2006-04-02 at 13:10 -0700, Linus Torvalds wrote:
>
> On Sun, 2 Apr 2006, Michael Buesch wrote:
> >
> > Latest Linus-GIT tree freezes on boot on my
> > G4 PowerBook.
> > The last kernel messages are:
> >
> > GMT delta read from XPRAM: 0 minutes, DST: off
> > time_init: decrementer frequency = 18.432000 MHz
> > time_init: processor frequency = 1499.999994 MHz
>
> Hmm. Can you try the current one, which has a powerpc update.
>
> If that still doesn't fix it, doing a "git bisect" to find out where it
> started going south would be very very helpful.
Looks like it could be the idle loop that is broken... some quick tests
here seem to show that we die on the first msleep, wherever it comes
from (the above messages are not totally relevant because time_init just
happens to be just before console_init which kills the early boot
console, and the crash happens before radeonfb kicks in, which happens
much later).
I'm travelling so I really didn't have a chance to debug this yet
properly, it could be related to Paul's idle loop changes, or not ...
will get back to this next week. It seems like all powermac (or almost)
are broken at the moment.
Ben.
prev parent reply other threads:[~2006-04-07 6:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200604021801.42662.mb@bu3sch.de>
2006-04-02 20:10 ` Latest linus GIT freezes on my G4 Linus Torvalds
2006-04-07 6:29 ` Benjamin Herrenschmidt [this message]
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=1144391354.30891.28.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=paulus@samba.org \
--cc=torvalds@osdl.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).