All of lore.kernel.org
 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>
Subject: Re: Linux kernel 3.x problems on PowerMac G5
Date: Sun, 03 Mar 2013 05:48:42 -0700	[thread overview]
Message-ID: <513346AA.5010309@mail.ru> (raw)
In-Reply-To: <1362288548.2969.13.camel@pasglop>

Benjamin Herrenschmidt wrote:
> On Sat, 2013-03-02 at 15:40 +0100, Phileas Fogg wrote:
>> recently i got a PowerMac G5 and installed Debian Linux 2.6.32 on it.
>> Everything works so far and Debian boots properly.
>>
>> Today i tried to boot Linux 3 on the machine and it doesn't boot.
>> The Linux 3 kernel was cross-compiled by me.
>>
>> On Linux 3.8.1 it hangs after this line:
>> ---
>> windfarm: Drive bay control loop started.
>>
>> And then i'm getting RCU stall call traces.
>>
>> On Linux 3.2 it hangs too but not at the same place.
>> It hangs after some SCSI message.
>>
>> Have anyone tested Linux 3 kernels on PowerMac G5 recently ?
>
> Hrm, this is odd. I do run pretty much every release on my G5's without
> problems... Can you send me your .config and then try with a
> g5_defconfig just to see if it makes a difference ?
>
> There *might* have been a problem on those older machines vs. the 64T
> address space patches, so maybe try back 3.6 and 3.7 and let me know,
> I'm still trying to get the right fix in (I know it breaks PS/3 under
> some circumstances).
>
> Cheers,
> Ben.
>
>


Reverted 64TB commit on Linux 3.8.1 and it didn't help, it still hangs.

Here is the RCU stall call trace:

BUG - soft lockup - CPU#1 stuck for 23s
Call trace:
padzero
load_elf_binary
search_binary_handler
load_script
search_binary_handler
do_execve_common
sys_execve
syscall_exit

Exception at kernel_execve
LR = run_init_process



regards

      reply	other threads:[~2013-03-03 12:49 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
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 [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=513346AA.5010309@mail.ru \
    --to=phileas-fogg@mail.ru \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.