Re: [BISECTED] v4.3-rc5: OMAP1 boot hang

[Jon Hunter]

On 13/11/15 00:57, Russell King - ARM Linux wrote:
> On Wed, Nov 11, 2015 at 11:44:44PM +0200, Aaro Koskinen wrote:
>> Hi,
>>
>> Any suggestions how to debug this further? This happens also with v4.3
>> final. Is the CPU_SW_DOMAIN_PAN supposed to work with this CPU?
>>
>> I tried to disable various drivers (e.g. NAND, USB) and it still
>> hangs... And it seems always at the same printk time stamp (roughly at
>> 25 seconds).
> 
> No idea what so ever, and I have zero knowledge of this ARM925 thing -
> never had one, and never seen any specs on it.  The weird thing is
> that it's not producing any oops dump - I guess the kernel is totally
> dead and unresponsive.  I'd ask if you have a heartbeat LED, but I'd
> guess the answer will be that the hardware is too limited.

Both the 1510 and 5910 had the ARM925T CPU. Probably the best source of
info is the 5910 documentation [0], specifically the MPU subsystem
document [1]. Hope this helps.

Jon

[0] http://www.ti.com/product/OMAP5910/technicaldocuments
[1] http://www.ti.com/lit/pdf/spru671
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [BISECTED] v4.3-rc5: OMAP1 boot hang

[Russell King - ARM Linux]

On Wed, Nov 11, 2015 at 11:44:44PM +0200, Aaro Koskinen wrote:
> Hi,
> 
> Any suggestions how to debug this further? This happens also with v4.3
> final. Is the CPU_SW_DOMAIN_PAN supposed to work with this CPU?
> 
> I tried to disable various drivers (e.g. NAND, USB) and it still
> hangs... And it seems always at the same printk time stamp (roughly at
> 25 seconds).

No idea what so ever, and I have zero knowledge of this ARM925 thing -
never had one, and never seen any specs on it.  The weird thing is
that it's not producing any oops dump - I guess the kernel is totally
dead and unresponsive.  I'd ask if you have a heartbeat LED, but I'd
guess the answer will be that the hardware is too limited.

Any additional information you can give might help, but I wouldn't hold
out any hopes...

-- 
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [BISECTED] v4.3-rc5: OMAP1 boot hang

[Aaro Koskinen]

Hi,

Any suggestions how to debug this further? This happens also with v4.3
final. Is the CPU_SW_DOMAIN_PAN supposed to work with this CPU?

I tried to disable various drivers (e.g. NAND, USB) and it still
hangs... And it seems always at the same printk time stamp (roughly at
25 seconds).

A.

On Tue, Oct 13, 2015 at 10:30:46AM +0300, Aaro Koskinen wrote:
> Hi,
> 
> Amstrad E3 / OMAP1 boot hangs, and I bisected it to
> a5e090acbf545c0a3b04080f8a488b17ec41fe02 ("ARM: software-based
> priviledged-no-access support").
> 
> Below is the boot log. Disabling CPU_SW_DOMAIN_PAN helps.
> 
> Uncompressing Linux... done, booting the kernel.
> [0.00] Booting Linux on physical CPU 0x0
> [0.00] Initializing cgroup subsys cpu
> [0.00] Linux version 4.3.0-rc5-e3-los_df2ad+ (aaro@amd-fx-6350) (gcc 
> version 5.2.0 (GCC) ) #1 Tue Oct 13 10:08:05 EEST 2015
> [0.00] CPU: ARM925T [54029252] revision 2 (ARMv4T), cr=317f
> [0.00] CPU: VIVT data cache, VIVT instruction cache
> [0.00] Machine: Amstrad E3 (Delta)
> [0.00] Ignoring memory below PHYS_OFFSET: 0x0200-0x1000
> [0.00] Memory policy: Data cache writethrough
> [0.00] On node 0 totalpages: 8192
> [0.00] free_area_init_node: node 0, pgdat c0427018, node_mem_map 
> c1fb7000
> [0.00]   Normal zone: 64 pages used for memmap
> [0.00]   Normal zone: 0 pages reserved
> [0.00]   Normal zone: 8192 pages, LIFO batch:0
> [0.00] OMAP1510
> [0.00]  revision 2 handled as 15xx id: bc058c9b93111a16
> [0.00] Clocks: ARM_SYSST: 0x1000 DPLL_CTL: 0x2cb3 ARM_CKCTL: 0x250e
> [0.00] Clocking rate (xtal/DPLL1/MPU): 12.0/150.0/150.0 MHz
> [0.00] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
> [0.00] pcpu-alloc: [0] 0 
> [0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
> pages: 8128
> [0.00] Kernel command line: mem=32M console=tty 
> console=ttyS0,115200n8 root=/dev/ram0 initrd=0x11c0,2894948 
> initcall_debug=1 loglevel=9
> [0.00] PID hash table entries: 128 (order: -3, 512 bytes)
> [0.00] Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
> [0.00] Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
> [0.00] Memory: 25136K/32768K available (3074K kernel code, 141K 
> rwdata, 864K rodata, 140K init, 212K bss, 7632K reserved, 0K cma-reserved)
> [0.00] Virtual kernel memory layout:
> [0.00] vector  : 0x - 0x1000   (   4 kB)
> [0.00] fixmap  : 0xffc0 - 0xfff0   (3072 kB)
> [0.00] vmalloc : 0xc280 - 0xff00   ( 968 MB)
> [0.00] lowmem  : 0xc000 - 0xc200   (  32 MB)
> [0.00] modules : 0xbf00 - 0xc000   (  16 MB)
> [0.00]   .text : 0xc0008000 - 0xc03e0ec4   (3940 kB)
> [0.00]   .init : 0xc03e1000 - 0xc0404000   ( 140 kB)
> [0.00]   .data : 0xc0404000 - 0xc04277e0   ( 142 kB)
> [0.00].bss : 0xc04277e0 - 0xc045c9c0   ( 213 kB)
> [0.00] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
> [0.00] NR_IRQS:16 nr_irqs:16 16
> [0.00] Total of 64 interrupts in 2 interrupt banks
> [0.000131] sched_clock: 32 bits at 6MHz, resolution 166ns, wraps every 
> 357913940908ns
> [0.000382] clocksource: mpu_timer2: mask: 0x max_cycles: 
> 0x, max_idle_ns: 318543407797 ns
> [0.001561] Console: colour dummy device 80x30
> [0.009527] console [tty0] enabled
> [0.010230] Calibrating delay loop... 74.13 BogoMIPS (lpj=370688)
> [0.100420] pid_max: default: 32768 minimum: 301
> [0.101672] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
> [0.102202] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 
> bytes)
> [0.108589] CPU: Testing write buffer coherency: ok
> [0.111741] calling  init_static_idmap+0x0/0x11c @ 1
> [0.112570] Setting up static identity map for 0x10008400 - 0x1000842c
> [0.113178] initcall init_static_idmap+0x0/0x11c returned 0 after 0 usecs
> [0.113812] calling  spawn_ksoftirqd+0x0/0x30 @ 1
> [0.115210] initcall spawn_ksoftirqd+0x0/0x30 returned 0 after 0 usecs
> [0.115820] calling  init_workqueues+0x0/0x2ec @ 1
> [0.120426] initcall init_workqueues+0x0/0x2ec returned 0 after 9765 usecs
> [0.121133] calling  rand_initialize+0x0/0x34 @ 1
> [0.122426] initcall rand_initialize+0x0/0x34 returned 0 after 0 usecs
> [0.126229] devtmpfs: initialized
> [0.136417] calling  ipc_ns_init+0x0/0x44 @ 1
> [0.136959] initcall ipc_ns_init+0x0/0x44 returned 0 after 0 usecs
> [0.137461] calling  init_mmap_min_addr+0x0/0x2c @ 1
> [0.137893] initcall init_mmap_min_addr+0x0/0x2c returned 0 after 0 usecs
> [0.138440] calling  net_ns_init+0x0/0x1c8 @ 1
> [0.139019] initcall net_ns_init+0x0/0x1c8 returned 0 after 0 usecs
> [0.140507] calling  ptrace_break_init+0