SUPERH platform development
 help / color / mirror / Atom feed
* ape6evm boot problem in v3.19-rc2
@ 2014-12-29  3:06 Simon Horman
  2014-12-29 17:00 ` Geert Uytterhoeven
  0 siblings, 1 reply; 2+ messages in thread
From: Simon Horman @ 2014-12-29  3:06 UTC (permalink / raw)
  To: linux-sh


Hi,

I have observed a possible regression when booting the APE6EVM board using
ape6evm_defconfig on v3.19-rc2. This also appears to be present in
v3.19-rc1 but not v3.18.

At this time I have not bisected the problem or otherwise investigated
further.


Booting Linux on physical CPU 0x0
Initializing cgroup subsys cpu
Linux version 3.19.0-rc2 (horms@ayumi.isobedori.kobe.vergenet.net) (gcc version 4.6.3 (GCC) ) #347 SMP Mon Dec 29 11:51:59 JST 2014
CPU: ARMv7 Processor [412fc0f3] revision 3 (ARMv7), cr\x10c5307d
CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
Machine model: APE6EVM
Ignoring memory block 0x200000000 - 0x240000000
debug: ignoring loglevel setting.
Memory policy: Data cache writealloc
On node 0 totalpages: 262144
free_area_init_node: node 0, pgdat c0521800, node_mem_map eeffa000
  Normal zone: 1520 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 194560 pages, LIFO batch:31
  HighMem zone: 67584 pages, LIFO batch:15
PERCPU: Embedded 8 pages/cpu @eefe7000 s11520 r0 d21248 u32768
pcpu-alloc: s11520 r0 d21248 u32768 alloc=8*4096
pcpu-alloc: [0] 0 
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 260624
Kernel command line: console=ttySC0,115200 ignore_loglevel root=/dev/nfs ip=dhcp rw
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 1034052K/1048576K available (3773K kernel code, 220K rwdata, 980K rodata, 256K init, 188K bss, 14524K reserved, 0K cma-reserved, 270336K highmem)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xf0000000 - 0xff000000   ( 240 MB)
    lowmem  : 0xc0000000 - 0xef800000   ( 760 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
      .text : 0xc0008000 - 0xc04ad5a0   (4758 kB)
      .init : 0xc04ae000 - 0xc04ee000   ( 256 kB)
      .data : 0xc04ee000 - 0xc0525358   ( 221 kB)
       .bss : 0xc0525358 - 0xc055457c   ( 189 kB)
Hierarchical RCU implementation.
        RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=1.
RCU: Adjusting geometry for rcu_fanout_leaf\x16, nr_cpu_ids=1
NR_IRQS:16 nr_irqs:16 16
Architected cp15 timer(s) running at 13.00MHz (virt).
sched_clock: 56 bits at 13MHz, resolution 76ns, wraps every 2643056803840ns
Switching to timer-based delay loop, resolution 76ns
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 26.04 BogoMIPS (lpj\x101562)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
CPU: Testing write buffer coherency: ok
CPU0: update cpu_capacity 1024
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x40393df8 - 0x40393e50
Brought up 1 CPUs
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
sh-pfc pfc-r8a73a4: r8a73a4_pfc handling gpio 0 -> 329
sh-pfc pfc-r8a73a4: r8a73a4_pfc support registered
renesas_irqc renesas_irqc.0: failed to request IRQ
renesas_irqc: probe of renesas_irqc.0 failed with error -2
renesas_irqc renesas_irqc.1: failed to request IRQ
renesas_irqc: probe of renesas_irqc.1 failed with error -2
hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 8 bytes.
sh_cmt sh-cmt-48-gen2.1: ch0: failed to request irq 152
sh_cmt sh-cmt-48-gen2.1: ch0: registration failed
sh_cmt: probe of sh-cmt-48-gen2.1 failed with error -22
Switched to clocksource arch_sys_counter
NET: Registered protocol family 2
TCP established hash table entries: 8192 (order: 3, 32768 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP: reno registered
UDP hash table entries: 512 (order: 2, 16384 bytes)
UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
futex hash table entries: 256 (order: 2, 16384 bytes)
NFS: Registering the id_resolver key type
Key type id_resolver registered
Key type id_legacy registered
nfs4filelayout_init: NFSv4 File Layout Driver Registering...
bounce: pool size: 64 pages
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
sh-dma-engine sh-dma-engine.0: DMA failed requesting irq #252, error -22
sh-dma-engine: probe of sh-dma-engine.0 failed with error -22
SuperH (H)SCI(F) driver initialized
sh-sci sh-sci.0: ttySC0 at MMIO 0xe6c40000 (irq = 176, base_baud = 0) is a scifa
console [ttySC0] enabled
sh-sci sh-sci.1: ttySC1 at MMIO 0xe6c50000 (irq = 177, base_baud = 0) is a scifa
sh-sci sh-sci.2: ttySC2 at MMIO 0xe6c20000 (irq = 180, base_baud = 0) is a scifb
sh-sci sh-sci.3: ttySC3 at MMIO 0xe6c30000 (irq = 181, base_baud = 0) is a scifb
sh-sci sh-sci.4: ttySC4 at MMIO 0xe6ce0000 (irq = 182, base_baud = 0) is a scifb
sh-sci sh-sci.5: ttySC5 at MMIO 0xe6cf0000 (irq = 183, base_baud = 0) is a scifb
Unable to handle kernel NULL pointer dereference at virtual address 00000218
pgd = c0004000
[00000218] *pgd\0000000
Internal error: Oops: 5 [#1] SMP ARM
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.19.0-rc2 #347
Hardware name: ape6evm
task: ee81e9c0 ti: ee88a000 task.ti: ee88a000
PC is at irq_domain_activate_irq+0x2c/0x48
LR is at irq_startup+0x24/0x70
pc : [<c0065fc4>]    lr : [<c00637d4>]    psr: 600001d3
sp : ee88bd90  ip : 00000000  fp : c050d598
r10: 60000153  r9 : ee8e92b8  r8 : 000007f8
r7 : 00000000  r6 : 00000001  r5 : ee8271c0  r4 : ee8e9280
r3 : 00000200  r2 : 00000000  r1 : 00000001  r0 : 00000000
Flags: nZCv  IRQs off  FIQs off  Mode SVC_32  ISA ARM  Segment kernel
Control: 10c5307d  Table: 4000406a  DAC: 00000015
Process swapper/0 (pid: 1, stack limit = 0xee88a238)
Stack: (0xee88bd90 to 0xee88c000)
bd80:                                     00000000 ee8e9280 ee8e9280 c00637d4
bda0: eea42c00 ee8e9280 ee8e92e0 c00626c0 ee8efa80 ffffffed eea43ec0 eea43800
bdc0: eea42c00 ee8e9280 c0255c6c 00000084 00000000 eea43800 000007f8 c0062a1c
bde0: eea43800 ee8e5400 eea43cc0 ee8efb00 60000153 a0000153 00000011 c0256ecc
be00: eea43800 eea43800 ee9da0d8 ee8e5410 eea43cec 00000404 ee8efb00 eea43ce0
be20: 00000000 c0147124 ee9da178 00000001 00000000 c04e99ec ee8ea128 c04710f0
be40: ee8ea128 ee9da178 00000001 00000000 c04e99ec ffffffed ee8e5410 c0517b54
be60: 00000000 00000000 c04e99ec c0517b54 00000000 c0233a64 ee8e5410 c0549c0c
be80: c0549c18 c0232450 00000000 ee8e5410 c0517b54 ee8e5444 00000000 c04e2e20
bea0: 00000061 c0232600 c0517b54 00000000 c0232574 c0230e1c ee820c5c ee8bc434
bec0: c0517b54 ee993900 c0516880 c02315dc c045644c c04cc494 c0517b54 c0517b54
bee0: 00000000 c04e2e20 eeb3b240 c0232efc 00000000 c04cc494 00000000 c04aece4
bf00: 00000013 c0397aac ee833680 c0539118 c0525300 00000000 c0489c08 c013e478
bf20: 00000000 c04fea90 60000153 00000000 eeff15be 00000000 c0489c08 c003aeb4
bf40: c0474ee4 c04895f8 00000006 00000006 c04fea68 c04e3678 00000006 c04e3658
bf60: c0525380 c04ae584 c04e99ec 00000061 00000000 c04aeeac 00000006 00000006
bf80: c04ae584 c038c124 00000000 c038c124 00000000 00000000 00000000 00000000
bfa0: 00000000 c038c12c 00000000 c000ef78 00000000 00000000 00000000 00000000
bfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
bfe0: 00000000 00000000 00000000 00000000 00000013 00000000 00002000 00000000
[<c0065fc4>] (irq_domain_activate_irq) from [<c00637d4>] (irq_startup+0x24/0x70)
[<c00637d4>] (irq_startup) from [<c00626c0>] (__setup_irq+0x458/0x4bc)
[<c00626c0>] (__setup_irq) from [<c0062a1c>] (request_threaded_irq+0xb0/0x12c)
[<c0062a1c>] (request_threaded_irq) from [<c0256ecc>] (smsc911x_drv_probe+0x5b0/0x108c)
[<c0256ecc>] (smsc911x_drv_probe) from [<c0233a64>] (platform_drv_probe+0x30/0x80)
[<c0233a64>] (platform_drv_probe) from [<c0232450>] (driver_probe_device+0x118/0x23c)
[<c0232450>] (driver_probe_device) from [<c0232600>] (__driver_attach+0x8c/0x90)
[<c0232600>] (__driver_attach) from [<c0230e1c>] (bus_for_each_dev+0x54/0x88)
[<c0230e1c>] (bus_for_each_dev) from [<c02315dc>] (bus_add_driver+0xdc/0x1c4)
[<c02315dc>] (bus_add_driver) from [<c0232efc>] (driver_register+0x78/0xf4)
[<c0232efc>] (driver_register) from [<c04aece4>] (do_one_initcall+0x100/0x1c0)
[<c04aece4>] (do_one_initcall) from [<c04aeeac>] (kernel_init_freeable+0x108/0x1d4)
[<c04aeeac>] (kernel_init_freeable) from [<c038c12c>] (kernel_init+0x8/0xe4)
[<c038c12c>] (kernel_init) from [<c000ef78>] (ret_from_fork+0x14/0x3c)
Code: e3500000 0a000000 ebfffff5 e595300c (e5933018) 
---[ end trace 1b95e4eb9b4a058f ]---
Kernel panic - not syncing: Attempted

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: ape6evm boot problem in v3.19-rc2
  2014-12-29  3:06 ape6evm boot problem in v3.19-rc2 Simon Horman
@ 2014-12-29 17:00 ` Geert Uytterhoeven
  0 siblings, 0 replies; 2+ messages in thread
From: Geert Uytterhoeven @ 2014-12-29 17:00 UTC (permalink / raw)
  To: linux-sh

On Mon, Dec 29, 2014 at 4:06 AM, Simon Horman <horms@verge.net.au> wrote:
> I have observed a possible regression when booting the APE6EVM board using
> ape6evm_defconfig on v3.19-rc2. This also appears to be present in
> v3.19-rc1 but not v3.18.
>
> At this time I have not bisected the problem or otherwise investigated
> further.

> renesas_irqc renesas_irqc.0: failed to request IRQ
> renesas_irqc: probe of renesas_irqc.0 failed with error -2

Looks like another victim of 9a1091ef0017c40a ("irqchip: gic: Support
hierarchy irq domain."). On armadillo it was fixed in

commit d034f53cc6c5c09a4e10cb9716986f3844c58514
Author: Geert Uytterhoeven <geert+renesas@glider.be>
Date:   Wed Dec 17 14:40:42 2014 +0100

    ARM: shmobile: r8a7740: Instantiate GIC from C board code in legacy builds

    As of commit 9a1091ef0017c40a ("irqchip: gic: Support hierarchy irq
    domain."), armadillo-legacy hangs during boot with:

         sh-tmu.0: ch0: used for clock events
         sh-tmu.0: ch0: used for periodic clock events
         sh-tmu.0: ch0: failed to request irq 230
         sh-tmu.0: ch1: used as clock source
         sh-cmt-48.1: ch0: failed to request irq 90
         sh-cmt-48.1: ch0: registration failed
        earlytimer: unable to probe sh-cmt-48 early.
        Calibrating delay loop...

    This happens because the IRQ numbers of the GIC are now virtual, and no
    longer match the hardcoded hardware IRQ numbers in the platform board
    code.
    To fix this, instantiate the GIC from platform board code when compiling
    a legacy kernel, like is done on sh73a0 for kzm9g-legacy.

    Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
    Acked-by: Marc Zyngier <marc.zyngier@arm.com>
    Signed-off-by: Simon Horman <horms+renesas@verge.net.au>

On r8a73a4, irqchip_init() is not called explicitly, but by the ARM core
code, as r8a73a4 does not provide machine_desc.init_irq().
So it probably just needs its own machine_desc.init_irq() and register
the GIC from C code in the legacy case.

BTW, I expect kzm9g-reference to start suffering from this too, after Magnus'
multiplatform patch is applied and intc-sh73a0.c is no longer used for
-reference.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2014-12-29 17:00 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-12-29  3:06 ape6evm boot problem in v3.19-rc2 Simon Horman
2014-12-29 17:00 ` Geert Uytterhoeven

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox