From: Arjan van de Ven <arjan@infradead.org>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: "Jiri Slaby" <jirislaby@gmail.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
"Linux kernel mailing list" <linux-kernel@vger.kernel.org>
Subject: Re: kondemand: kernel BUG at kernel/workqueue.c:258!
Date: Thu, 29 Nov 2007 18:04:49 -0800 [thread overview]
Message-ID: <20071129180449.2fcecc83@laptopd505.fenrus.org> (raw)
In-Reply-To: <924EFEDD5F540B4284297C4DC59F3DEE2FA920@orsmsx423.amr.corp.intel.com>
On Thu, 29 Nov 2007 13:47:34 -0800
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com> wrote:
>
>
> >-----Original Message-----
> >From: Jiri Slaby [mailto:jirislaby@gmail.com]
> >Sent: Thursday, November 29, 2007 1:43 PM
> >To: Pallipadi, Venkatesh; Nakajima, Jun
> >Cc: Linux kernel mailing list
> >Subject: kondemand: kernel BUG at kernel/workqueue.c:258!
> >
> >Hi,
> >
> >while trying to evoke another bug by endlessly change
> >governors, this appeared:
> >kernel BUG at .../kernel/workqueue.c:258!
> >invalid opcode: 0000 [1] PREEMPT SMP
> >CPU 0
> >Modules linked in: iwl3945 mac80211 cfg80211 tun
> >cpufreq_userspace rfcomm
> >l2cap hci_usb bluetooth kvm_intel arc4 ecb blkcipher kvm cryptomgr
> >crypto_algapi acpi_cpufreq fglrx(P) asus_laptop sr_mod cdrom ehci_hcd
> >uhci_hcd battery
> >Pid: 443, comm: kondemand/0 Tainted: P 2.6.23 #38
>
> Kernel version?
on the same line as the tainted flag and 2 below the binary module that
is in use.... I assume Jiri is now working on reproducing this
untainted ... ;)
next prev parent reply other threads:[~2007-11-30 2:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 21:42 Jiri Slaby
2007-11-29 21:47 ` Pallipadi, Venkatesh
2007-11-29 21:55 ` Jiri Slaby
2007-11-30 2:04 ` Arjan van de Ven [this message]
2007-11-30 8:16 ` Jiri Slaby
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=20071129180449.2fcecc83@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=jirislaby@gmail.com \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=venkatesh.pallipadi@intel.com \
/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
all inboxes | Powered by JetHome®