mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jörg-Volker Peetz" <jvpeetz@web.de>
To: linux-kernel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 3.4 released
Date: Tue, 22 May 2012 21:50:10 +0200	[thread overview]
Message-ID: <4FBBEDF2.8060803@web.de> (raw)
In-Reply-To: <CAOS58YPMh_hbJ4a49j4p9H68n8U1LzMUuaxmHx57gVTkmfxF6A@mail.gmail.com>

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?

-- 
Best regards,
Jörg-Volker.



  reply	other threads:[~2012-05-22 19:50 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-21  0:00 Linus Torvalds
2012-05-21 11:38 ` Josh Boyer
2012-05-21 15:20   ` Linus Torvalds
2012-05-21 16:41     ` Josh Boyer
2012-05-21 18:04       ` Tobias Klausmann
2012-05-22 15:30 ` Jörg-Volker Peetz
2012-05-22 15:53   ` Tejun Heo
2012-05-22 16:52     ` Jörg-Volker Peetz
2012-05-22 17:03       ` Tejun Heo
2012-05-22 18:26         ` Jörg-Volker Peetz
2012-05-22 18:35           ` Tejun Heo
2012-05-22 19:50             ` Jörg-Volker Peetz [this message]
2012-05-23  6:34               ` Yong Zhang
2012-05-23 12:33                 ` Jörg-Volker Peetz
2012-05-23 18:24               ` Tejun Heo
2012-05-23 19:56                 ` Jörg-Volker Peetz
2012-05-23 20:26                   ` Tejun Heo
2012-05-25  7:25                     ` Takashi Iwai
2012-05-25 15:33                       ` Jörg-Volker Peetz
2012-05-25 16:06                         ` Takashi Iwai
2012-05-25 18:41                           ` Jörg-Volker Peetz
2012-05-27 13:03                             ` Jörg-Volker Peetz
2012-05-28  5:16                               ` Takashi Iwai
2012-06-06 11:11                                 ` freeze hard-lock with 3.5-rc1 with dynpm for radeon GPU [was Re: Linux 3.4 released] Jörg-Volker Peetz
2012-08-09  6:47                                 ` 3.5 kernel NULL pointer dereference net_tx_action Jörg-Volker Peetz
2012-08-10  8:45                                   ` Jörg-Volker Peetz
2012-05-28  5:16                               ` Linux 3.4 released Takashi Iwai
2012-05-25 16:06                         ` Takashi Iwai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FBBEDF2.8060803@web.de \
    --to=jvpeetz@web.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome