public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nageswara R Sastry <rnsastry@linux.vnet.ibm.com>
To: Johannes Weiner <hannes@saeurebad.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org, balbir@linux.vnet.ibm.com,
	ego@linux.vnet.ibm.com, svaidy@linux.vnet.ibm.com,
	davej@codemonkey.org.uk,
	Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
	Alexey Starikovskiy <astarikovskiy@suse.de>
Subject: Re: [BUG] While changing the cpufreq governor, kernel hits a bug in workqueue.c
Date: Tue, 28 Oct 2008 08:59:45 +0530	[thread overview]
Message-ID: <49068729.6000304@linux.vnet.ibm.com> (raw)
In-Reply-To: <48EB2EDF.5000605@linux.vnet.ibm.com>

Nageswara R Sastry wrote:
> Any updates on this bug. Thanks in advance for your coordination.
> 
> Johannes Weiner wrote:
>>> I have not yet looked at cpufreq_conservative...
>>>
>>> Thanks for your patience and insistence,

 From long time I didn't see any activity related to this bug so posting 
again after testing on the latest stable kernel.

------------[ cut here ]------------
kernel BUG at kernel/workqueue.c:240!
invalid opcode: 0000 [#1] SMP
Modules linked in: cpufreq_powersave cpufreq_conservative 
cpufreq_userspace usb_ 
                                           storage usbhid ehci_hcd 
ohci_hcd uhci_hcd usbcore

Pid: 236, comm: kondemand/1 Not tainted (2.6.27.2 #1)
EIP: 0060:[<c0131c6e>] EFLAGS: 00010286 CPU: 1
EIP is at queue_delayed_work_on+0x24/0xa6
EAX: 00000000 EBX: c3a3c9d4 ECX: c3a3c9d4 EDX: 00000000
ESI: c3a3c9f0 EDI: f7a45658 EBP: 00000001 ESP: f7a53f3c
  DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
Process kondemand/1 (pid: 236, ti=f7a52000 task=f7904270 task.ti=f7a52000)
Stack: 00000000 f7a43d08 c3a3c9c0 f7ab5c68 c0424ee5 00000040 00000000 
00000001
        00000040 00000000 00000002 ffffffff 00000000 ffffffff c3a3c9d8 
f7a43d08
        c3a3c9d4 f7a53f9c c013156d 00000000 00000002 00000000 c013152f 
c0424cbb
Call Trace:
  [<c0424ee5>] do_dbs_timer+0x22a/0x24a
  [<c013156d>] run_workqueue+0xbf/0x18a
  [<c013152f>] run_workqueue+0x81/0x18a
  [<c0424cbb>] do_dbs_timer+0x0/0x24a
  [<c0131e25>] worker_thread+0x0/0xbd
  [<c0131ed8>] worker_thread+0xb3/0xbd
  [<c013423c>] autoremove_wake_function+0x0/0x2d
  [<c013418a>] kthread+0x38/0x5e
  [<c0134152>] kthread+0x0/0x5e
  [<c0104503>] kernel_thread_helper+0x7/0x10
  =======================
Code: 6c c0 e9 7a ff ff ff 55 89 c5 57 89 d7 56 53 89 cb 8d 71 1c f0 0f 
ba 29 00 
                              19 c0 31 d2 85 c0 0f 85 81 00 00 00 83 79 
1c 00 74 04 <0f> 0b eb fe 8d 41 04 39 
                                                           41 04 74 04 
0f 0b eb fe 8b 54 24 10 89
EIP: [<c0131c6e>] queue_delayed_work_on+0x24/0xa6 SS:ESP 0068:f7a53f3c
---[ end trace 69cb0cd122ebfb9d ]---


P.S. This time it took just 2 minutes to reproduce this bug. Previously 
it used to happen after 30 minutes.

Please let me know if you need more details.

Thanks a lot for your coordination.

Regards
R.Nageswara Sastry


  reply	other threads:[~2008-10-28  3:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23 10:51 [BUG] While changing the cpufreq governor, kernel hits a bug in workqueue.c Nageswara R Sastry
2008-06-23 15:26 ` Johannes Weiner
2008-06-24  9:17   ` Nageswara R Sastry
2008-06-25 19:47     ` Johannes Weiner
2008-06-25 20:00       ` Dave Jones
2008-06-26 12:18       ` Nageswara R Sastry
2008-06-26 13:31         ` Nageswara R Sastry
2008-06-27  4:12           ` Nageswara R Sastry
2008-07-01 14:00         ` Johannes Weiner
2008-07-04 13:56           ` Johannes Weiner
2008-07-07  9:48             ` Nageswara R Sastry
2008-07-07 11:07               ` Johannes Weiner
2008-07-08  5:52                 ` Nageswara R Sastry
2008-07-10 11:11                   ` Johannes Weiner
2008-07-15  3:42                     ` Nageswara R Sastry
2008-07-16 13:44                     ` Peter Zijlstra
2008-08-12  8:12                       ` Nageswara R Sastry
2008-08-12 21:29                         ` Johannes Weiner
2008-08-12 21:44                           ` Johannes Weiner
2008-10-07  9:41                             ` Nageswara R Sastry
2008-10-28  3:29                               ` Nageswara R Sastry [this message]
2008-07-07 11:19               ` Nageswara R Sastry

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=49068729.6000304@linux.vnet.ibm.com \
    --to=rnsastry@linux.vnet.ibm.com \
    --cc=astarikovskiy@suse.de \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=davej@codemonkey.org.uk \
    --cc=ego@linux.vnet.ibm.com \
    --cc=hannes@saeurebad.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=svaidy@linux.vnet.ibm.com \
    --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