All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julian Margetson <runaway@candw.ms>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, Ian Munsie <imunsie@au1.ibm.com>
Subject: Re: Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board
Date: Wed, 18 Feb 2015 15:45:27 -0400	[thread overview]
Message-ID: <54E4EBD7.5000307@candw.ms> (raw)
In-Reply-To: <1424045921.3018.4.camel@ellerman.id.au>

[-- Attachment #1: Type: text/plain, Size: 2967 bytes --]

On 2/15/2015 8:18 PM, Michael Ellerman wrote:
> On Sun, 2015-02-15 at 08:16 -0400, Julian Margetson wrote:
>> Hi
>>
>> I am unable to get any kernel beyond  the 3.16 branch working on an
>> Acube Sam460ex
>>   AMCC 460ex based motherboard. Kernel  up 3.16.7-ckt6 working.
> Does reverting b0345bbc6d09 change anything?
>
>> [    6.364350] snd_hda_intel 0001:81:00.1: enabling device (0000 -> 0002)
>> [    6.453794] snd_hda_intel 0001:81:00.1: ppc4xx_setup_msi_irqs: fail mapping irq
>> [    6.487530] Unable to handle kernel paging request for data at address 0x0fa06c7c
>> [    6.495055] Faulting instruction address: 0xc032202c
>> [    6.500033] Vector: 300 (Data Access) at [efa31cf0]
>> [    6.504922]     pc: c032202c: __reg_op+0xe8/0x100
>> [    6.509697]     lr: c0014f88: msi_bitmap_free_hwirqs+0x50/0x94
>> [    6.515600]     sp: efa31da0
>> [    6.518491]    msr: 21000
>> [    6.521112]    dar: fa06c7c
>> [    6.523915]  dsisr: 0
>> [    6.526190]   current = 0xef8bab00
>> [    6.529603]     pid   = 115, comm = kworker/0:1
>> [    6.534163] enter ? for help
>> [    6.537054] [link register   ] c0014f88 msi_bitmap_free_hwirqs+0x50/0x94
>> [    6.543811] [efa31da0] c0014f78 msi_bitmap_free_hwirqs+0x40/0x94 (unreliable)
>> [    6.551001] [efa31dc0] c001aee8 ppc4xx_setup_msi_irqs+0xac/0xf4
>> [    6.556973] [efa31e00] c03503a4 pci_enable_msi_range+0x1e0/0x280
>> [    6.563032] [efa31e40] f92c2f74 azx_probe_work+0xe0/0x57c [snd_hda_intel]
>> [    6.569906] [efa31e80] c0036344 process_one_work+0x1e8/0x2f0
>> [    6.575627] [efa31eb0] c003677c worker_thread+0x2f4/0x438
>> [    6.581079] [efa31ef0] c003a3e4 kthread+0xc8/0xcc
>> [    6.585844] [efa31f40] c000aec4 ret_from_kernel_thread+0x5c/0x64
>> [    6.591910] mon>  <no input ...>
>
> cheers
>
>
>
Managed to do a third git bisect  with the following results .

git bisect bad
9279d3286e10736766edcaf815ae10e00856e448 is the first bad commit
commit 9279d3286e10736766edcaf815ae10e00856e448
Author: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Date:   Wed Aug 6 16:10:16 2014 -0700

     lib: bitmap: change parameter of bitmap_*_region to unsigned
     
     Changing the pos parameter of __reg_op to unsigned allows the compiler
     to generate slightly smaller and simpler code.  Also update its callers
     bitmap_*_region to receive and pass unsigned int.  The return types of
     bitmap_find_free_region and bitmap_allocate_region are still int to
     allow a negative error code to be returned.  An int is certainly capable
     of representing any realistic return value.
     
     Signed-off-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>
     Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
     Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

:040000 040000 4f560a7caaba2d05c146a3cea27e0d93739d950c c3d4539acad26667a2d78844ead7b75af753f41e M	include
:040000 040000 7a6fb894aac2a1d4e72f8e36b7c6de3c24509ad3 31d756da185e07d2de090c9e6aeb12689d58d310 M	lib



[-- Attachment #2: Type: text/html, Size: 4129 bytes --]

  reply	other threads:[~2015-02-18 19:45 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-15 12:16 Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board Julian Margetson
2015-02-16  0:18 ` Michael Ellerman
2015-02-18 19:45   ` Julian Margetson [this message]
2015-02-19  0:13     ` Michael Ellerman
2015-02-19  1:36       ` Julian Margetson
2015-02-19  2:56         ` Michael Ellerman
2015-02-19  3:25           ` Julian Margetson
2015-02-20 19:25             ` Julian Margetson
2015-02-24  0:32               ` Michael Ellerman
2015-02-24  2:22                 ` Julian Margetson
2015-02-24 11:08                 ` Julian Margetson
2015-02-24 19:14                   ` Gerhard Pircher
2015-02-24 20:26                     ` Julian Margetson
2015-02-25 13:26                       ` Julian Margetson
2015-02-25 13:32                         ` Julian Margetson
2015-03-04 11:46                         ` Julian Margetson
2015-03-04 23:52                           ` Michael Ellerman
2015-03-05 11:15                             ` Julian Margetson
2015-03-07 16:10                               ` Julian Margetson
2015-03-10  0:30                                 ` Michael Ellerman
2015-03-10  0:53                                   ` Julian Margetson
     [not found]                 ` <45dfe4c8990.73f22654@smtp.gmail.com>
2015-02-24 19:05                   ` Julian Margetson
2015-02-19 15:57           ` Julian Margetson
     [not found]           ` <54EB253F.9020704@candw.ms>
2015-02-23 15:07             ` Problems with DRI " Julian Margetson
2015-02-23 17:43             ` Julian Margetson
2015-02-24 11:12               ` Julian Margetson
2015-02-24 18:57                 ` Julian Margetson
2015-02-24 20:28                   ` Julian Margetson
2015-02-25 13:25                     ` Julian Margetson
2015-02-25 13:31                       ` Julian Margetson
2015-03-07 16:05                       ` Julian Margetson
2016-02-02 13:54           ` commit 9178ba294b6839eeff1a91bed95515d783f3ee6c Julian Margetson
2016-08-05 11:26           ` Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board Julian Margetson
2015-02-19  2:20     ` Julian Margetson
2015-02-18 20:13   ` Julian Margetson
2015-04-27 10:59   ` Kernel 4.1-rc1 build fails on Sam460ex amcc 460ex powerpc Canyonlands Julian Margetson
2015-04-28  1:12     ` Michael Ellerman
2015-04-28  3:49       ` Tejun Heo
2015-05-04 17:18         ` Andy Shevchenko
2015-05-04 18:13           ` Tejun Heo

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=54E4EBD7.5000307@candw.ms \
    --to=runaway@candw.ms \
    --cc=imunsie@au1.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /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.