linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Phileas Fogg <phileas-fogg@mail.ru>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
	Denis Kirjanov <kirjanov@gmail.com>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Aaro Koskinen <aaro.koskinen@iki.fi>
Subject: Re: Linux kernel 3.x problems on PowerMac G5
Date: Mon, 04 Mar 2013 06:03:49 +1100	[thread overview]
Message-ID: <1362337429.2969.17.camel@pasglop> (raw)
In-Reply-To: <51333F1C.4080605@mail.ru>

On Sun, 2013-03-03 at 05:16 -0700, Phileas Fogg wrote:
> i'm testing currently with slightly modified g5_defconfig. I enabled
> the Ralink driver for my USB WLAN NIC and some other stuff, nothing 
> fancy. Anyways, i'm sending you config for 3.0.67. Linux 3.0.67 hangs on 
> my machine too.
> 
> I cloned your GIT powerpc repository and at the moment bisecting and
> trying to find the commit which causes trouble on my machine.
> 
> I have already found out that
> the commit 27d934b28752b860cba6c0d77ea4598861d80998 is OK
> but
> the commit 0bd41dfc9fbbcf174d5336c1c9fc5ba917519761 is NOT.
> The problem appeared between Linux 2.6.39 and Linux-3.0-rc1.
> 
> Just my typical luck with PowerPC :) First PS3 and now G5.
> 
> I will report back as soon as i find the commit which causes the hangs.

Thanks. It looks like a bisection might indeed be the way to go... 

Out of curiosity, have you tried without some of your additional drivers ?
Maybe one of them is the culprit...

Cheers,
Ben.

  reply	other threads:[~2013-03-03 19:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-02 14:40 Linux kernel 3.x problems on PowerMac G5 Phileas Fogg
2013-03-02 14:13 ` Aaro Koskinen
2013-03-02 15:23   ` Phileas Fogg
     [not found]   ` <5132198C.8050300__15885.293405927$1362234296$gmane$org@mail.ru>
2013-03-02 16:22     ` Andreas Schwab
2013-03-03  5:31       ` Benjamin Herrenschmidt
2013-03-03  8:23         ` Denis Kirjanov
2013-03-03  9:38           ` Benjamin Herrenschmidt
2013-03-03 12:16             ` Phileas Fogg
2013-03-03 19:03               ` Benjamin Herrenschmidt [this message]
2013-03-03 19:16                 ` Phileas Fogg
2013-03-03 19:24                   ` Benjamin Herrenschmidt
2013-03-07 20:08                     ` Phileas Fogg
2013-03-07 20:22                       ` Benjamin Herrenschmidt
2013-03-07 21:07                         ` Phileas Fogg
2013-03-10  0:26                         ` Phileas Fogg
2013-03-10  0:45                           ` Benjamin Herrenschmidt
2013-03-10  7:53                             ` Phileas Fogg
2013-03-10 10:19                             ` Phileas Fogg
2013-03-10 10:53                             ` Phileas Fogg
2013-03-10 12:52                               ` Benjamin Herrenschmidt
2013-03-11 19:31                                 ` Phileas Fogg
2013-03-03  5:29 ` Benjamin Herrenschmidt
2013-03-03 12:48   ` Phileas Fogg

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=1362337429.2969.17.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=aaro.koskinen@iki.fi \
    --cc=kirjanov@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=phileas-fogg@mail.ru \
    --cc=schwab@linux-m68k.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).