Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752518Ab2EWMdX (ORCPT <rfc822;w@1wt.eu>);
	Wed, 23 May 2012 08:33:23 -0400
Received: from plane.gmane.org ([80.91.229.3]:36379 "EHLO plane.gmane.org"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1750963Ab2EWMdW (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Wed, 23 May 2012 08:33:22 -0400
X-Injected-Via-Gmane: http://gmane.org/
To: linux-kernel@vger.kernel.org
From: =?UTF-8?B?SsO2cmctVm9sa2VyIFBlZXR6?= <jvpeetz@web.de>
Subject: Re: Linux 3.4 released
Date: Wed, 23 May 2012 14:33:04 +0200
Message-ID: <4FBCD900.1000605@web.de>
References: <CA+55aFwaobhbBZkE1LTyQJYhk8w8zk-cyOXXuXfPyE=BXzT3PA@mail.gmail.com> <4FBBB11D.7020904@web.de> <20120522155345.GC14339@google.com> <4FBBC461.4060008@web.de> <20120522170320.GD14339@google.com> <jpglns$1uj$1@dough.gmane.org> <CAOS58YPMh_hbJ4a49j4p9H68n8U1LzMUuaxmHx57gVTkmfxF6A@mail.gmail.com> <4FBBEDF2.8060803@web.de> <20120523063421.GA23937@zhy>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Complaints-To: usenet@dough.gmane.org
Cc: linux-kernel@vger.kernel.org
X-Gmane-NNTP-Posting-Host: p5b371840.dip.t-dialin.net
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.4) Gecko/20120510 Icedove/10.0.4
In-Reply-To: <20120523063421.GA23937@zhy>
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1843
Lines: 51

Yong Zhang wrote, on 05/23/12 08:34:
> 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
> 

Hello,

with the patch of Tejun Heo and CONFIG_DEBUG_OBJECTS_WORK enabled via "make
nconfig" doesn't show any output line beginning with "XXX".

-- 
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/