All of lore.kernel.org
 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 18:52:49 +0200	[thread overview]
Message-ID: <4FBBC461.4060008@web.de> (raw)
In-Reply-To: <20120522155345.GC14339@google.com>

Tejun Heo wrote, on 05/22/12 17:53:
> Hello,
> 
> On Tue, May 22, 2012 at 05:30:37PM +0200, Jörg-Volker Peetz wrote:
>> Switching from self-compiled kernel 3.2 17 to a self compiled kernel 3.4.0,
>> a notebook HP Pavilion dv7 gets hard locked with a kernel panic, when trying to
>> start a web-cam video viewer (guvcview) for the built-in USB web-cam.
>>
>> Please find attached a (hand-typed) screen-shot of the text-console and the
>> kernel config.
>>
>> By the way, thank you for all the great work on Linux.
>> -- 
>> Best regards,
>> Jörg-Volker.
> 
>> BUG: Unable to handle kernel NULL pointer dereference at 0000000000000008
> ...
>> Code: 8b 7c 24 50 48 83 c4 58 c3 66 66 66 2e 0f 1f 84 00 00 00 00 00 48 8b 0f 31 c0 48 89 fa 48 89 ce 40 80 e6 00 83 e1 04 48 0f 45 c6 <48> 8b 70 08 65 8b 3c 25 60 cc 00 00 e9 b9 fc ff ff 66 0f 1f 84
>> RIP  [<ffffffff8103ed46>] delayed_work_timer_fn+0x16/0x30
> 
> So, that looks like get_work_cwq() returning NULL and then
> delayed_work_timer_fn() trying to dereference it.  Either work item is
> being corrupted (e.g. freed early) or somebody is mucking with the
> work item embedded in a delayed work item.
> 
> Something like the following may reveal the offending work function.
> 
> Thanks.
> 
> diff --git a/kernel/workqueue.c b/kernel/workqueue.c
> index 5abf42f..adc1057 100644
> --- a/kernel/workqueue.c
> +++ b/kernel/workqueue.c
> @@ -1101,6 +1101,10 @@ static void delayed_work_timer_fn(unsigned long __data)
>  	struct delayed_work *dwork = (struct delayed_work *)__data;
>  	struct cpu_workqueue_struct *cwq = get_work_cwq(&dwork->work);
>  
> +	if (!cwq)
> +		printk("XXX delayed_work_timer_fn: NULL cwq, fn=%pf\n",
> +		       dwork->work.func);
> +
>  	__queue_work(smp_processor_id(), cwq->wq, &dwork->work);
>  }
>  

Hello,

I tried the above patch but was not able to see a line beginning with "XXX", not
on the text-console nor in any log-file. After the hard-lock, I can see only the
console-screen which now changed slightly:

BUG: Unable to handle kernel NULL pointer dereference at 0000000000000008
IP: [<ffffffff8103ed60>] delayed_work_timer_fn+0x30/0x60
PGD 214fbc067 PUD 211c50067 PMD 0
Oops: 0000 [#1] SMP
CPU 1

...

Call Trace:
 <IRQ>
 [<ffffffff8103ed30>] ? __queu_work+0x320/0x320
 [<ffffffff810342c6>] ? run_timer_softirq+0x106/0x220
 [<ffffffff8105cc34>] ? tick_handle_oneshot_broadcast+0xb5/0xe0
 [<ffffffff8102f19d>] ? __do_softirq+0x8d/0x110
 [<ffffffff81069589>] ? handle_irq_event_percpu+0x79/0x140
 [<ffffffff813dfa8c>] ? call_softirq+0x1c/0x26
 [<ffffffff81003a8d>] ? do_softirq+0x4d/0x80
 [<ffffffff8102f495>] ? irq_exit+0xa5/0xb0
 [<ffffffff8100372b>] ? do_IRQ+0x5b/0xd0
 [<ffffffff813de227>] ? common_interrupt+0x67/0x67
 <EOI>
 [<ffffffff81009e60>] ? default_idle+0x20/0x40
 [<ffffffff81009ff8>] ? amd_e400_idle+0xa8/0xf0
 [<ffffffff8100a7a6>] ? cpu_idle+0xb6/0xd0

...

After that I have to press the power button until the computer switches off.
What else could I do?
-- 
Best regards,
Jörg-Volker.


  reply	other threads:[~2012-05-22 16:53 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-21  0:00 Linux 3.4 released 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 [this message]
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
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=4FBBC461.4060008@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.