linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Phileas Fogg <phileas-fogg@mail.ru>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
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: Thu, 07 Mar 2013 21:08:11 +0100	[thread overview]
Message-ID: <5138F3AB.5040401@mail.ru> (raw)
In-Reply-To: <1362338657.2969.20.camel@pasglop>

On 03/03/2013 08:24 PM, Benjamin Herrenschmidt wrote:
> On Sun, 2013-03-03 at 20:16 +0100, Phileas Fogg wrote:
>> Benjamin Herrenschmidt wrote:
>>> 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.
>>>
>>
>> Not yet, will do.
>> But I tested the official Debian Wheezy RC netinstall CD with Linux 3.2,
>> it has the same problem and hangs at boot on my machine.
>
> Ok, so it's definitely something about your configuration. Maybe
> something in the 11,2 support code chokes on single-chip configs, I
> don't have one of them to test, both mines are dual chip (ie. quad
> core).
>
> But it does look like a regression that should be bisectable, so let me
> know went you're done there and what you get.
>
> Cheers,
> Ben.
>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>

Hi,

i'm completely confused now.
I did a bisect between the following 2 commits: 
61c4f2c81c61f73549928dfd9f3e8f26aa36a8cf (good) Linux 2.6.39
and
55922c9d1b84b89cb946c777fddccb3247e7df2c (bad)  Linux 3.0-rc1
Both commist were tested by me on my machine. And Linux 3.0-rc1 hangs
on my machine but Linux 2.6.39 works fine.

And the bisect couldn't find the commit which causes hangs on my machine.
All commits which were provided by the bisect were bad.
And the commit before tha last bad bisect commit was bad too.
I did bisect several times, and got the same results.

Fo testing i used linux-3.0.y branch of
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git.

Did i miss something or do something wrong here ?

Regards

  reply	other threads:[~2013-03-07 20:09 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
2013-03-03 19:16                 ` Phileas Fogg
2013-03-03 19:24                   ` Benjamin Herrenschmidt
2013-03-07 20:08                     ` Phileas Fogg [this message]
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=5138F3AB.5040401@mail.ru \
    --to=phileas-fogg@mail.ru \
    --cc=aaro.koskinen@iki.fi \
    --cc=benh@kernel.crashing.org \
    --cc=kirjanov@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --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).