linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Hugh Dickins <hughd@google.com>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: Jens Axboe <jaxboe@fusionio.com>,
	linux-kernel@vger.kernel.org,
	kevin diggs <diggskevin38@gmail.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [regression] 2.6.39-rc[1-3] fail to boot on G5 PowerMac
Date: Thu, 14 Apr 2011 14:25:31 -0700	[thread overview]
Message-ID: <BANLkTimykvKp=bwsFyNE9fWqcE9Ffws6bA@mail.gmail.com> (raw)
In-Reply-To: <1302771756.15520.100.camel@thor.local>

On Thu, Apr 14, 2011 at 2:02 AM, Michel D=C3=A4nzer <michel@daenzer.net> wr=
ote:
> On Mit, 2011-04-13 at 18:43 -0500, kevin diggs wrote:
>>
>> On Wed, Apr 13, 2011 at 6:21 PM, Benjamin Herrenschmidt
>> <benh@kernel.crashing.org> wrote:
>> > On Wed, 2011-04-13 at 12:52 -0500, kevin diggs wrote:
>> >> > Actually I do get a crash in X later on... something in the radeon
>> >> DRM
>> >> > interrupt code is getting what looks like a NULL dereference. I'll
>> >> try
>> >> > to dig that one later on. I don't know if it's related to your
>> >> problem
>> >> > at all though.
>> >> >
>> >> In this context, what does 'crash' mean? The X thingy goes down? Or
>> >> the whole OS?
>> >
>> > Depends, with xmon enabled you get into xmon :-) Dunno if the oops is
>> > fatal but it could be.
>> >
>> > Cheers,
>> > Ben.
>> >
>> >
>>
>> As I think I have the same hardware as you (7,3, radeon 9600) If you
>> can tell me how to reproduce it maybe I can poke around a little.
>> Thus, at least temporarily, freeing you up for other stuff.
>>
>> I kinda need a break from fighting with GCC.
>
> FWIW, the problem Ben refers to might be fixed in current mainline by
> commit d87dfdbfc91c5e37288e7e8f7afdd992ba61a60d which reverts
> 69a07f0b117a40fcc1a479358d8e1f41793617f2 .

Mikael,

Something worth trying: turn off CONFIG_IDE.  That's what I need to
boot 2.6.39-rc[1-3] on PowerPC G5.

I know Jens has been fixing problems with IDE versus his plug/unplug
changes, but it's still not fixed for me in rc3.

In other mail http://lkml.org/lkml/2011/4/14/614
I see Linus recommending his post-rc3 commit 6631e635c65d
but I've not tried that myself yet.

Hugh

  reply	other threads:[~2011-04-14 21:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-12 17:30 [regression] 2.6.39-rc[1-3] fail to boot on G5 PowerMac Mikael Pettersson
2011-04-12 18:59 ` kevin diggs
2011-04-12 22:09 ` Benjamin Herrenschmidt
2011-04-12 23:55   ` Benjamin Herrenschmidt
2011-04-13  8:16     ` Mikael Pettersson
2011-04-13  8:58       ` Benjamin Herrenschmidt
2011-04-13 17:52         ` kevin diggs
2011-04-13 23:21           ` Benjamin Herrenschmidt
2011-04-13 23:43             ` kevin diggs
2011-04-14  9:02               ` Michel Dänzer
2011-04-14 21:25                 ` Hugh Dickins [this message]
2011-04-14 21:54                   ` Benjamin Herrenschmidt
2011-04-17  3:16                     ` Hugh Dickins
2011-04-17  7:00                       ` Jens Axboe
2011-04-17 17:47                         ` Hugh Dickins
2011-04-14 22:14                   ` Mikael Pettersson

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='BANLkTimykvKp=bwsFyNE9fWqcE9Ffws6bA@mail.gmail.com' \
    --to=hughd@google.com \
    --cc=diggskevin38@gmail.com \
    --cc=jaxboe@fusionio.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mikpe@it.uu.se \
    /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).