Re: omap: panda rcu stall on 3.10.1
On 08/30/2013 10:10 AM, jean-philippe francois wrote: 2013/8/30 Christian Hoffmann chrmhoffm...@gmail.com: This also went to: linaro-ker...@lists.linaro.org Hi, current linaro kernel on 13.07 (3.10.1.0-1-linaro-omap) shows stack below. System is generally quite unstable. Light usage (postfix+dovecot...) Full dmesg here: https://dl.dropboxusercontent.com/u/21820416/rcu.stall.panda Hi, Does it happen when run with nohlt in the kernel command line ? Hi, the panda is much more stable (up now for 2 or three days) with nohlt. No sign of stack traces or RCU stalls. Thank you. Chris -- 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
omap: panda rcu stall on 3.10.1
This also went to: linaro-ker...@lists.linaro.org
Hi,
current linaro kernel on 13.07 (3.10.1.0-1-linaro-omap) shows stack
below. System is generally quite unstable. Light usage (postfix+dovecot...)
Full dmesg here:
https://dl.dropboxusercontent.com/u/21820416/rcu.stall.panda
Rgds,
Chris
[ 4538.880432] INFO: rcu_sched detected stalls on CPUs/tasks: { 1}
(detected by 0, t=2103 jiffies, g=1649, c=1648, q=18)
[ 4538.891723] Backtrace for cpu 0 (current):
[ 4538.891723] CPU: 0 PID: 0 Comm: swapper/0 Not tainted
3.10.1.0-1-linaro-omap #1ubuntu1~ci+130723003933-Ubuntu
[ 4538.891754] [c001175d] (unwind_backtrace+0x1/0x9c) from
[c000f625] (show_stack+0x11/0x14)
[ 4538.891815] [c000f625] (show_stack+0x11/0x14) from [c00106d5]
(smp_send_all_cpu_backtrace+0x49/0x98)
[ 4538.891815] [c00106d5] (smp_send_all_cpu_backtrace+0x49/0x98) from
[c007c755] (rcu_check_callbacks+0x439/0x4ac)
[ 4538.891815] [c007c755] (rcu_check_callbacks+0x439/0x4ac) from
[c0036599] (update_process_times+0x2d/0x4c)
[ 4538.891876] [c0036599] (update_process_times+0x2d/0x4c) from
[c005fcfd] (tick_sched_handle+0x35/0x40)
[ 4538.891906] [c005fcfd] (tick_sched_handle+0x35/0x40) from
[c005feed] (tick_sched_timer+0x31/0x54)
[ 4538.891937] [c005feed] (tick_sched_timer+0x31/0x54) from
[c004532b] (__run_hrtimer+0x5b/0x138)
[ 4538.891937] [c004532b] (__run_hrtimer+0x5b/0x138) from [c0045bcb]
(hrtimer_interrupt+0xdb/0x22c)
[ 4538.891967] [c0045bcb] (hrtimer_interrupt+0xdb/0x22c) from
[c0010e13] (twd_handler+0x1b/0x28)
[ 4538.891998] [c0010e13] (twd_handler+0x1b/0x28) from [c00783b9]
(handle_percpu_devid_irq+0x4d/0xac)
[ 4538.891998] [c00783b9] (handle_percpu_devid_irq+0x4d/0xac) from
[c0075ead] (generic_handle_irq+0x19/0x24)
[ 4538.892028] [c0075ead] (generic_handle_irq+0x19/0x24) from
[c000d16d] (handle_IRQ+0x29/0x68)
[ 4538.892059] [c000d16d] (handle_IRQ+0x29/0x68) from [c00084db]
(gic_handle_irq+0x27/0x50)
[ 4538.892059] [c00084db] (gic_handle_irq+0x27/0x50) from [c045315b]
(__irq_svc+0x3b/0x5c)
[ 4538.892059] Exception stack(0xc06e3f68 to 0xc06e3fb0)
[ 4538.892059] 3f60:
c06e2000 c075f130
[ 4538.892120] 3f80: c06e2000 c075ea93 c075f130 c06ea594 c045c2e0
c06e2000 c0fe5908 c06e3fb0
[ 4538.892120] 3fa0: c007bab1 c0058b48 400f0133
[ 4538.892120] [c045315b] (__irq_svc+0x3b/0x5c) from [c0058b48]
(cpu_startup_entry+0xbc/0x164)
[ 4538.892120] [c0058b48] (cpu_startup_entry+0xbc/0x164) from
[c06735f9] (start_kernel+0x251/0x2ac)
[ 4538.892120]
[ 4538.892120] sending IPI to all other CPUs:
[ 4538.892211] IPI backtrace for cpu 1
[ 4538.892211]
[ 4538.892242] CPU: 1 PID: 2064 Comm: clamd Not tainted
3.10.1.0-1-linaro-omap #1ubuntu1~ci+130723003933-Ubuntu
[ 4538.892242] task: edb09500 ti: ec91e000 task.ti: ec91e000
[ 4538.892272] PC is at 0xb6e2f0d4
[ 4538.892272] LR is at 0xb6eeec01
[ 4538.892272] pc : [b6e2f0d4]lr : [b6eeec01]psr: 000f0130
[ 4538.892272] sp : be8b472c ip : 62323337 fp : 684a
[ 4538.892303] r10: 0084d750 r9 : 0200 r8 : e86d6a2f
[ 4538.892303] r7 : 0a0a0a0a r6 : 69393e32 r5 : 0080bf24 r4 : 0080bf28
[ 4538.892333] r3 : 81010100 r2 : 6438 r1 : 000a r0 : 0080bf24
[ 4538.892333] Flags: nzcv IRQs on FIQs on Mode USER_32 ISA Thumb
Segment user
[ 4538.892333] Control: 50c5387d Table: acbd404a DAC:
[ 4538.892364]
[ 4538.892364] R8: 0xe86d69af:
[ 4538.892364] 69ac 6a6f7254 412e6e61 746e6567 3939332d 00303934
b1aa3270 2506 47a83ca7
[ 4538.892395] 69cc e4ebc453 91ad979e 23363f8b fd49d9d0 773b48ba
ad58f7d3 04c351eb 96e4414f
[ 4538.892395] 69ec 7e1a3ac7 f39072a5 e362cedb b119b3e0 b595375e
b2137762 b19f99a8 b10dc638
[ 4538.892395] 6a0c 1806 2e6e6957 6a6f7254 412e6e61 746e6567
3939332d 00303534 b23ade28
[ 4538.892395] 6a2c 1806 2e6e6957 6a6f7254 462e6e61 61656b61
37342d76 00373131 ac58376e
[ 4538.892395] 6a4c 72542e6e 6e616a6f 3434382e 35313336 3e55c600
412e6eb2 72617764 61472e65
[ 4538.892517] 6a6c 6176656d 2d65636e 34393132 55b20037 1604b173
2e6e6957 6a6f7254 462e6e61
[ 4538.892547] 6a8c 61656b61 37342d76 00343131 b652e2c0 72542e6e
6e616a6f 7075532e 756a7265
[ 4538.892547] 6aac 322d6e61 fb003731 15b23a2b 2e6e6957 6a6f7254
412e6e61 746e6567 3939332d
[ 4538.892547] CPU: 1 PID: 2064 Comm: clamd Not tainted
3.10.1.0-1-linaro-omap #1ubuntu1~ci+130723003933-Ubuntu
[ 4538.892547] [c001175d] (unwind_backtrace+0x1/0x9c) from
[c000f625] (show_stack+0x11/0x14)
[ 4538.892639] [c000f625] (show_stack+0x11/0x14) from [c0010819]
(handle_IPI+0xd5/0x158)
[ 4538.892669] [c0010819] (handle_IPI+0xd5/0x158) from [c00084ff]
(gic_handle_irq+0x4b/0x50)
[ 4538.892669] [c00084ff] (gic_handle_irq+0x4b/0x50) from [c0453369]
(__irq_usr+0x49/0x60)
[ 4538.892700] Exception stack(0xec91ffb0 to 0xec91fff8)
[ 4538.892700] ffa0: 0080bf24
000a 6438 81010100
[ 4538.892730] ffc0: 0080bf28 0080bf24 69393e32 0a0a0a0a e86d6a2f
0200 0084d750 684a
[ 4538.892730] ffe0: 62323337 be8b472c b6eeec01 b6e2f0d4 000f0130
Fwd: Re: current panda omap kernel stacks
Hi, please see the current issues I found on panda running 3.10.1.0-1-linaro-omap https://dl.dropboxusercontent.com/u/21820416/panda.syslog.gz https://dl.dropboxusercontent.com/u/21820416/panda-dmesg System is generally very unstable. RCU stall sent in different thread Chris Original Message Subject:Re: current panda omap kernel stacks Date: Tue, 27 Aug 2013 21:11:12 +0200 From: Christian Hoffmann chrmhoffm...@gmail.com To: linaro-ker...@lists.linaro.org Forgot to attach syslog here: https://dl.dropboxusercontent.com/u/21820416/panda.syslog.gz On Tue, Aug 27, 2013 at 9:09 PM, Christian Hoffmann chrmhoffm...@gmail.com mailto:chrmhoffm...@gmail.com wrote: Sorry to reply to myself, but after a while the panda doesn't reply any more over network and the syslog has lots of entries like this one: Aug 27 13:00:38 panda kernel: [87136.303894] [c044c1e9] (__schedule_bug+0x39/0x50) from [c045219f] (__schedule+0x51f/0x5c4) Aug 27 13:00:38 panda kernel: [87136.303924] [c045219f] (__schedule+0x51f/0x5c4) from [c045250b] (schedule_preempt_disabled+0xf/0x10) Aug 27 13:00:38 panda kernel: [87136.303924] [c045250b] (schedule_preempt_disabled+0xf/0x10) from [c0058bbb] (cpu_startup_entry+0x12f/0x164) Aug 27 13:00:38 panda kernel: [87136.303955] [c0058bbb] (cpu_startup_entry+0x12f/0x164) from [80448ea9] (0x80448ea9) Aug 27 13:00:38 panda kernel: [87136.307403] BUG: scheduling while atomic: swapper/1/0/0x Aug 27 13:00:38 panda kernel: [87136.313781] Modules linked in: snd_soc_omap_abe_twl6040 snd_soc_omap_mcpdm snd_soc_twl6040 snd_soc_omap snd_soc_omap_mcbsp snd_soc_core snd_compress regmap_spi snd_pcm snd_page_alloc snd_timer snd soundcore gator Aug 27 13:00:38 panda kernel: [87136.313842] CPU: 1 PID: 0 Comm: swapper/1 Tainted: GW3.10.1.0-1-linaro-omap #1ubuntu1~ci+130723003933-Ubuntu Aug 27 13:00:38 panda kernel: [87136.313842] [c001175d] (unwind_backtrace+0x1/0x9c) from [c000f625] (show_stack+0x11/0x14) Aug 27 13:00:38 panda kernel: [87136.313873] [c000f625] (show_stack+0x11/0x14) from [c044c1e9] (__schedule_bug+0x39/0x50) Aug 27 13:00:38 panda kernel: [87136.313903] [c044c1e9] (__schedule_bug+0x39/0x50) from [c045219f] (__schedule+0x51f/0x5c4) Aug 27 13:00:38 panda kernel: [87136.313934] [c045219f] (__schedule+0x51f/0x5c4) from [c045250b] (schedule_preempt_disabled+0xf/0x10) Aug 27 13:00:38 panda kernel: [87136.313934] [c045250b] (schedule_preempt_disabled+0xf/0x10) from [c0058bbb] (cpu_startup_entry+0x12f/0x164) Aug 27 13:00:38 panda kernel: [87136.313964] [c0058bbb] (cpu_startup_entry+0x12f/0x164) from [80448ea9] (0x80448ea9) Aug 27 13:00:38 panda kernel: [87136.317382] BUG: scheduling while atomic: swapper/1/0/0x Aug 27 13:00:38 panda kernel: [87136.323760] Modules linked in: snd_soc_omap_abe_twl6040 snd_soc_omap_mcpdm snd_soc_twl6040 snd_soc_omap snd_soc_omap_mcbsp snd_soc_core snd_compress regmap_spi snd_pcm snd_page_alloc snd_timer snd soundcore gator Aug 27 13:00:38 panda kernel: [87136.323822] CPU: 1 PID: 0 Comm: swapper/1 Tainted: GW3.10.1.0-1-linaro-omap #1ubuntu1~ci+130723003933-Ubuntu Aug 27 13:00:38 panda kernel: [87136.323822] [c001175d] (unwind_backtrace+0x1/0x9c) from [c000f625] (show_stack+0x11/0x14) Aug 27 13:00:38 panda kernel: [87136.323822] [c000f625] (show_stack+0x11/0x14) from [c044c1e9] (__schedule_bug+0x39/0x50) Aug 27 13:00:38 panda kernel: [87136.323883] [c044c1e9] (__schedule_bug+0x39/0x50) from [c045219f] (__schedule+0x51f/0x5c4) Aug 27 13:00:38 panda kernel: [87136.323913] [c045219f] (__schedule+0x51f/0x5c4) from [c045250b] (schedule_preempt_disabled+0xf/0x10) Aug 27 13:00:38 panda kernel: [87136.323913] [c045250b] (schedule_preempt_disabled+0xf/0x10) from [c0058bbb] (cpu_startup_entry+0x12f/0x164) Aug 27 13:00:38 panda kernel: [87136.323944] [c0058bbb] (cpu_startup_entry+0x12f/0x164) from [80448ea9] (0x80448ea9) Aug 27 13:00:38 panda kernel: [87136.327392] BUG: scheduling while atomic: swapper/1/0/0x Aug 27 13:00:38 panda kernel: [87136.333770] Modules linked in: snd_soc_omap_abe_twl6040 snd_soc_omap_mcpdm snd_soc_twl6040 snd_soc_omap snd_soc_omap_mcbsp snd_soc_core snd_compress regmap_spi snd_pcm snd_page_alloc snd_timer snd soundcore gator Rgds, Chris On Tue, Aug 27, 2013 at 8:50 AM, Christian Hoffmann chrmhoffm...@gmail.com mailto:chrmhoffm...@gmail.com wrote: Hi, running the current panda linaro kernel 3.10.1.0-1-linaro-omap from linaro release 13.07, I run into a few kernel stacks. Eg.: [33222.473022] [ cut here ] [33222.473052] WARNING: at /build/buildd/linux-linaro-omap-3.10.1-3.10.1.0/kernel/timer.c:1122 call_timer_fn+0x81
Re: CPU_IDLE causes random reboots on custom 4430
On 09/23/2012 06:11 PM, Shilimkar, Santosh wrote: On Sat, Sep 22, 2012 at 10:41 PM, Chris Hoffmann chrmhoffm...@gmail.com wrote: On 09/22/2012 07:45 AM, Shilimkar, Santosh wrote: On Sat, Sep 22, 2012 at 4:19 AM, Chris Hoffmann chrmhoffm...@gmail.com wrote: Hi, We're trying to get a custom 4430 board (aka. nook tablet with OMAP4430 ES2.3 HS TWL6030 ES2.1) working with p-android-omap-3.0 on android jelly bean. The board works quite well, but we experience random hangs and the watchdog kicks the board to reboot. On the same kernel, you should have support for the persistent log. You might want to check the output. That should give you pointers on what CPU was doing before the freeze which resulted in reboot. Hi, I have some problems to provide logs. If I add -DDEBUG to cpuidle44xx.o the problem doesn't seem to occur. It could be that printk-ing alleviates the issue. Also the watchdog seems to shutdown the device rather than rebooting it (or it hangs?) and then I can't provide /proc/last_kmsg. How could I provide more info? Check if you have /sys/kernel/debug/persistent_trace available on your kernel. This generally helps whenever there are hangs, the last call stack is stored on memory and on the reboot it can be cat'ed to see if some useful information about hang is available. Hi Santosh, all, the p-android-omap-3.0 doesn't have the persistent_trace but I was able to backport it from 3.4 without major issues (only tricky part is that in p-android-3.4 there's no apparent user of that device in omapzoom kernel). The problem is now that the omap-watchdog doesn't kick the device to reboot but rather to shutdown, so I still have no trace. Soft-rebooting shows that I can get persistent_trace. Switching the persistent tracer to ecc=true does not help as it seems to overload the device completely when activating the tracing. Rgds, Chris -- 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
DSS: kernel p-android-3.0 hangs when omapdss.debug is enabled.
Hi, we're currently porting a 2.6.35 android kernel for a custom omap4430 board (aka nook tablet) to version 3.0.x. We're experiencing random hangs with no trace in the dmesg/last_kmsg or on serial console. Being desperate to find the cause, I tried to put omapdss.debug=y but unfortunately now the kernel hangs on boot. Putting on lock debugging, I can see the following in last_kmsg: ... [ 17.161529] omapdss MANAGER: configure_manager(2) [ 17.166625] omapdss MANAGER: configure manager wbc-shadow_dirty = 0 [ 17.173370] omapdss DISPC: GO LCD2 [ 17.177368] omapdss MANAGER: configure manager wbc-shadow_dirty = 0 [ 17.184143] omapdss MANAGER: configure manager wbc-shadow_dirty = 0 [ 17.191192] omapdss MANAGER: configure manager wbc-shadow_dirty = 0 [ 37.691680] BUG: spinlock lockup on CPU#0, BootAnimation/276, e5fbfd74 [ 37.699035] Backtrace: [ 37.701965] [c006c204] (dump_backtrace+0x0/0x114) from [c06613e8] (dump_stack+0x20/0x24) [ 37.710998] r6: r5:e5438000 r4:e5fbfd74 r3:0002 [ 37.717651] [c06613c8] (dump_stack+0x0/0x24) from [c032a604] (do_raw_spin_lock+0x11c/0x180) [ 37.727081] [c032a4e8] (do_raw_spin_lock+0x0/0x180) from [c066b74c] (_raw_spin_lock_irqsave+0x74/0x80) [ 37.737426] r9:e5438000 r8:0004 r7:0002 r6:c009f18c r5:280b0193 [ 37.744995] r4:e5fbfd74 [ 37.748107] [c066b6d8] (_raw_spin_lock_irqsave+0x0/0x80) from [c009f18c] (complete+0x28/0x68) [ 37.757690] r6:e5fbfd70 r5:00040080 r4:e5fbfd74 [ 37.763031] [c009f164] (complete+0x0/0x68) from [c0348388] (dispc_irq_wait_handler.27590+0x18/0x1c) [ 37.773162] r6:c0e5850c r5:00040080 r4:e5439d98 [ 37.778594] [c0348370] (dispc_irq_wait_handler.27590+0x0/0x1c) from [c0348200] (omap_dispc_irq_handler+0xb0/0x220) [ 37.790130] [c0348150] (omap_dispc_irq_handler+0x0/0x220) from [c0108acc] (handle_irq_event_percpu+0x84/0x2dc) [ 37.801300] [c0108a48] (handle_irq_event_percpu+0x0/0x2dc) from [c0108d70] (handle_irq_event+0x4c/0x6c) [ 37.811737] [c0108d24] (handle_irq_event+0x0/0x6c) from [c010b530] (handle_fasteoi_irq+0xcc/0x174) [ 37.821777] r6:e5438000 r5:c08a2cac r4:c08a2c60 r3: [ 37.828338] [c010b464] (handle_fasteoi_irq+0x0/0x174) from [c01082fc] (generic_handle_irq+0x40/0x54) [ 37.838562] r5:c0061158 r4:c08b4260 [ 37.842681] [c01082bc] (generic_handle_irq+0x0/0x54) from [c0062354] (asm_do_IRQ+0x5c/0xbc) [ 37.852111] [c00622f8] (asm_do_IRQ+0x0/0xbc) from [c066c58c] (__irq_svc+0x4c/0xec) ... Full dmesg is here: https://dl.dropbox.com/u/21820416/crash-dss-debug.dmesg Kernel source is very close to p-android-3.0. It can be found here: https://github.com/Kuzma30/kernel3NookTablet/tree/jellybean Used config: cyanogenmod_acclaim_defconfig. We have made some slight modifications to dss (for DSI2/lcd2/vsync2). For quick comparison, I put diff off drivers/video/omap2 here: https://dl.dropbox.com/u/21820416/dss.diff Please also note that we have a boxer as display (https://github.com/Kuzma30/kernel3NookTablet/blob/jellybean/drivers/video/omap2/displays/panel-boxer.c). Kind regards, Chris -- 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
mbox: possible deadlock
Hi,
Trying to find a hanging reason for a custom omap4430 board (aka nook
tablet), I stumled over a possible circular locking problem on
startup:
...
4[ 12.078216]
4[ 12.078247] ===
4[ 12.087341] [ INFO: possible circular locking dependency detected ]
4[ 12.094329] 3.0.31+ #2
4[ 12.097290] ---
4[ 12.104278] kworker/0:1/58 is trying to acquire lock:
4[ 12.110168] ((mq-work)){+.+.+.}, at: [c00d2fb0]
wait_on_work+0x0/0x1cc
4[ 12.118621]
4[ 12.118621] but task is already holding lock:
4[ 12.125549] (mbox_configured_lock){+.+.+.}, at: [c009ddd4]
omap_mbox_put+0x34/0x100
4[ 12.135009]
4[ 12.135040] which lock already depends on the new lock.
...
4[ 12.504486] Chain exists of:
4[ 12.504486] (mq-work) -- rproc-lock -- mbox_configured_lock
4[ 12.515899]
4[ 12.518127] Possible unsafe locking scenario:
4[ 12.518127]
4[ 12.524963]CPU0CPU1
4[ 12.530242]
4[ 12.535369] lock(mbox_configured_lock);
4[ 12.540344]lock(rproc-lock);
4[ 12.547485]lock(mbox_configured_lock);
4[ 12.555389] lock((mq-work));
4[ 12.559539]
4[ 12.559539] *** DEADLOCK ***
4[ 12.559539]
4[ 12.566589] 3 locks held by kworker/0:1/58:
4[ 12.571502] #0: (pm){.+.+..}, at: [c00d34b8]
process_one_work+0x124/0x590
4[ 12.580322] #1: ((dev-power.work)){+.+...}, at: [c00d34b8]
process_one_work+0x124/0x590
4[ 12.590850] #2: (mbox_configured_lock){+.+.+.}, at:
[c009ddd4] omap_mbox_put+0x34/0x100
4[ 12.601165]
Full dmesg can be found here:
https://dl.dropbox.com/u/21820416/mbox-deadlock.dmesg
For the record: Kernel source is very close to p-android-3.0. It can
be found here:
https://github.com/Kuzma30/kernel3NookTablet/tree/jellybean
Used config: cyanogenmod_acclaim_defconfig.
Kind regards,
Chris
--
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: DSS: kernel p-android-3.0 hangs when omapdss.debug is enabled.
On 09/02/2012 06:35 PM, Dimitar Dimitrov wrote: On Sunday 02 September 2012 15:25:09 Christian Hoffmann wrote: Hi, we're currently porting a 2.6.35 android kernel for a custom omap4430 board (aka nook tablet) to version 3.0.x. We're experiencing random hangs with no trace in the dmesg/last_kmsg or on serial console. Being desperate to find the cause, I tried to put omapdss.debug=y but unfortunately now the kernel hangs on boot. Putting on lock debugging, I can see the following in last_kmsg: ... [ 17.161529] omapdss MANAGER: configure_manager(2) [ 17.166625] omapdss MANAGER: configure manager wbc-shadow_dirty = 0 [ 17.173370] omapdss DISPC: GO LCD2 [ 17.177368] omapdss MANAGER: configure manager wbc-shadow_dirty = 0 [ 17.184143] omapdss MANAGER: configure manager wbc-shadow_dirty = 0 [ 17.191192] omapdss MANAGER: configure manager wbc-shadow_dirty = 0 [ 37.691680] BUG: spinlock lockup on CPU#0, BootAnimation/276, e5fbfd74 [ 37.699035] Backtrace: [ 37.701965] [c006c204] (dump_backtrace+0x0/0x114) from [c06613e8] (dump_stack+0x20/0x24) [ 37.710998] r6: r5:e5438000 r4:e5fbfd74 r3:0002 [ 37.717651] [c06613c8] (dump_stack+0x0/0x24) from [c032a604] (do_raw_spin_lock+0x11c/0x180) [ 37.727081] [c032a4e8] (do_raw_spin_lock+0x0/0x180) from [c066b74c] (_raw_spin_lock_irqsave+0x74/0x80) [ 37.737426] r9:e5438000 r8:0004 r7:0002 r6:c009f18c r5:280b0193 [ 37.744995] r4:e5fbfd74 [ 37.748107] [c066b6d8] (_raw_spin_lock_irqsave+0x0/0x80) from [c009f18c] (complete+0x28/0x68) [ 37.757690] r6:e5fbfd70 r5:00040080 r4:e5fbfd74 [ 37.763031] [c009f164] (complete+0x0/0x68) from [c0348388] (dispc_irq_wait_handler.27590+0x18/0x1c) [ 37.773162] r6:c0e5850c r5:00040080 r4:e5439d98 [ 37.778594] [c0348370] (dispc_irq_wait_handler.27590+0x0/0x1c) from [c0348200] (omap_dispc_irq_handler+0xb0/0x220) [ 37.790130] [c0348150] (omap_dispc_irq_handler+0x0/0x220) from [c0108acc] (handle_irq_event_percpu+0x84/0x2dc) [ 37.801300] [c0108a48] (handle_irq_event_percpu+0x0/0x2dc) from [c0108d70] (handle_irq_event+0x4c/0x6c) [ 37.811737] [c0108d24] (handle_irq_event+0x0/0x6c) from [c010b530] (handle_fasteoi_irq+0xcc/0x174) [ 37.821777] r6:e5438000 r5:c08a2cac r4:c08a2c60 r3: [ 37.828338] [c010b464] (handle_fasteoi_irq+0x0/0x174) from [c01082fc] (generic_handle_irq+0x40/0x54) [ 37.838562] r5:c0061158 r4:c08b4260 [ 37.842681] [c01082bc] (generic_handle_irq+0x0/0x54) from [c0062354] (asm_do_IRQ+0x5c/0xbc) [ 37.852111] [c00622f8] (asm_do_IRQ+0x0/0xbc) from [c066c58c] (__irq_svc+0x4c/0xec) ... Full dmesg is here: https://dl.dropbox.com/u/21820416/crash-dss-debug.dmesg Kernel source is very close to p-android-3.0. It can be found here: https://github.com/Kuzma30/kernel3NookTablet/tree/jellybean Used config: cyanogenmod_acclaim_defconfig. We have made some slight modifications to dss (for DSI2/lcd2/vsync2). For quick comparison, I put diff off drivers/video/omap2 here: https://dl.dropbox.com/u/21820416/dss.diff Please also note that we have a boxer as display (https://github.com/Kuzma30/kernel3NookTablet/blob/jellybean/drivers/video/ omap2/displays/panel-boxer.c). Kind regards, Chris -- 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 Could you try the following v3.0 patch: http://review.omapzoom.org/#/c/26235/ Regards, Dimitar Hi, Thank you, very much. This indeed makes the omapdss.debug=y work. I had to rebase the change a bit as we also have this one: OMAPFB: Select correct VSYNC IRQ based on DSS channel in place. Thanks again! Rgds, Chris -- 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
