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: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Denis Kirjanov <kirjanov@gmail.com>,
	Andreas Schwab <schwab@linux-m68k.org>,
	Aaro Koskinen <aaro.koskinen@iki.fi>
Subject: Re: Linux kernel 3.x problems on PowerMac G5
Date: Sun, 10 Mar 2013 01:26:35 +0100	[thread overview]
Message-ID: <513BD33B.7020305@mail.ru> (raw)
In-Reply-To: <1362687724.6977.1.camel@pasglop>

On 03/07/2013 09:22 PM, Benjamin Herrenschmidt wrote:
> On Thu, 2013-03-07 at 21:08 +0100, Phileas Fogg wrote:
>> 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 ?
>
> Did git bisect go down a merge commit ? It does for me if I try that and
> asks to test that merge first. If you get that wrong it can get very
> confused.
>
> That's all I can think of... do you have the bisection log just in
> case ?
>
> Also you can use gitk -- arch/powerpc to look at the changes to powerpc
> code and try manually random points before/after that if you think
> bisect isn't doing the right thing.
>
> Cheers,
> Ben.
>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>

Hi,

i managed to find the bad commit after a couple of days bisecting.


----------------------------
44ae3ab3358e962039c36ad4ae461ae9fb29596c is the first bad commit
commit 44ae3ab3358e962039c36ad4ae461ae9fb29596c
Author: Matt Evans <matt@ozlabs.org>
Date:   Wed Apr 6 19:48:50 2011 +0000

     powerpc: Free up some CPU feature bits by moving out MMU-related 
features

     Some of the 64bit PPC CPU features are MMU-related, so this patch moves
     them to MMU_FTR_ bits.  All cpu_has_feature()-style tests are moved to
     mmu_has_feature(), and seven feature bits are freed as a result.

     Signed-off-by: Matt Evans <matt@ozlabs.org>
     Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
--------------------------------




Actually, there are 2 problems i found.
The first problem occurs when i enable IDE CDROM driver on my machine.
The following commit causes hangs on my machine at boot:



----------------------
commit 5b03a1b140e13a28ff6be1526892a9dc538ddef6
Author: Tejun Heo <tj@kernel.org>
Date:   Wed Mar 9 19:54:27 2011 +0100

     ide: Convert to bdops->check_events()

     Convert ->media_changed() to the new ->check_events() method.  The
     conversion is mostly mechanical.  The only notable change is that
     cdrom now doesn't generate any event if @slot_nr isn't CDSL_CURRENT.
     It used to return -EINVAL which would be treated as media changed.  As
     media changer isn't supported anyway, this doesn't make any
     difference.

     This makes ide emit the standard disk events and allows kernel event
     polling.  Currently, only MEDIA_CHANGE event is implemented.  Adding
     support for EJECT_REQUEST shouldn't be difficult; however, given that
     ide driver is already deprecated, it probably is best to leave it
     alone.

     Signed-off-by: Tejun Heo <tj@kernel.org>
----------------------------




If i disable IDE CDROM driver then the Linux kernel boots again
and then it hits the commit 44ae3ab3358e962039c36ad4ae461ae9fb29596c
and hangs again :)

The commit eca590f402332ab873d13f2d8d00fa0b91cfff36 which is before
the commit 44ae3ab3358e962039c36ad4ae461ae9fb29596c works fine,
i tested it myself to be on the safe side.



Regards

  parent reply	other threads:[~2013-03-10  0:27 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
2013-03-07 20:22                       ` Benjamin Herrenschmidt
2013-03-07 21:07                         ` Phileas Fogg
2013-03-10  0:26                         ` Phileas Fogg [this message]
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=513BD33B.7020305@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).