Messages in this thread | | | Date | Wed, 23 May 2012 14:34:21 +0800 | From | Yong Zhang <> | Subject | Re: Linux 3.4 released |
| |
On Tue, May 22, 2012 at 09:50:10PM +0200, J�rg-Volker Peetz wrote: > Tejun Heo wrote, on 05/22/12 20:35: > > Hello, > > > > On Tue, May 22, 2012 at 11:26 AM, J?rg-Volker Peetz <jvpeetz@web.de> wrote: > >> Also with this second patch I wasn't able to see any output beginning with "XXX > >> delayed_work_timer_fn:". It should appear in the system log or on the text-console? > > > > Hmmm... it should appear on the console but your printk setting might > > be different. Can you please prepend KERN_CRIT before the printk > > format string? So that it looks like printk(KERN_CRIT "XXX: ..."). > > > > Thanks. > > > > Hello, > > no, changing to printk(KERN_CRIT "XXX: ...", ...) in kernel/workqueue.c didn't > print anything I could read. Would it appear before the "panic screen"? But I'm > not able to scroll back. > The Panic screen starts with > > BUG: Unable to handle kernel NULL pointer dereference at 0000000000000008 > IP: [<ffffffff8103eef1>] delayed_work_timer_fn+0x13/0x70 > > and the Call Trace with > > Call Trace: > <IRQ> > [<ffffffff81056fbf>] ? ktime_get+0x5f/0xf0 > [<ffffffff810342c6>] ? run_timer_softirq+0x106/0x220 > [<ffffffff8105cc44>] ? tick_handle_oneshot_broadcast+0xc4/0xe0 > > Do I need special settings in the kernel config?
Maybe you can enable CONFIG_DEBUG_OBJECTS_WORK and give another try.
Thanks, Yong
> > -- > Best regards, > J?rg-Volker. > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/
-- Only stand for myself -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |