All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Park <opengeometry@yahoo.ca>
To: linux-kernel@vger.kernel.org
Subject: WARNING: at kernel/workqueue.c:1217 worker_enter_idle+0xc8/0x140()
Date: Thu, 5 May 2011 23:10:06 -0400	[thread overview]
Message-ID: <20110506031006.GA16479@node1.opengeometry.net> (raw)

FYI... here is kernel trace that I got while booting 2.6.39-rc6:

------------[ cut here ]------------
WARNING: at kernel/workqueue.c:1217 worker_enter_idle+0xc8/0x140()
Hardware name: System Product Name
Modules linked in: powernow_k8 freq_table mperf snd_hda_codec_hdmi snd_hda_codec_analog raid456 async_pq async_xor xor async_memcpy async_raid6_recov raid6_pq async_tx md_mod rt61pci rt2x00pci rt2x00lib mac80211 cfg80211 psmouse snd_hda_intel ppdev parport_pc snd_hda_codec snd_hwdep parport evdev k10temp forcedeth rfkill snd_pcm nv_tco eeprom_93cx6 snd_timer asus_atk0110 mac_hid hwmon i2c_nforce2 serio_raw snd rtc_cmos processor thermal soundcore snd_page_alloc sg fan button
Pid: 387, comm: kworker/1:1 Not tainted 2.6.39-rc6 #3
Call Trace:
 [<ffffffff81041eeb>] ? warn_slowpath_common+0x7b/0xc0
 [<ffffffff81055ba8>] ? worker_enter_idle+0xc8/0x140
 [<ffffffff81058d50>] ? worker_thread+0x1d0/0x3d0
 [<ffffffff81033640>] ? __wake_up_common+0x50/0x80
 [<ffffffff81058b80>] ? rescuer_thread+0x2e0/0x2e0
 [<ffffffff81058b80>] ? rescuer_thread+0x2e0/0x2e0
 [<ffffffff8105c7f6>] ? kthread+0x96/0xa0
 [<ffffffff81656ed4>] ? kernel_thread_helper+0x4/0x10
 [<ffffffff8105c760>] ? kthread_worker_fn+0x170/0x170
 [<ffffffff81656ed0>] ? gs_change+0xb/0xb
---[ end trace 912cf20fdd777538 ]---

-- 
William

                 reply	other threads:[~2011-05-06  3:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20110506031006.GA16479@node1.opengeometry.net \
    --to=opengeometry@yahoo.ca \
    --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.