From: Parag Warudkar <kernel-stuff@comcast.net>
To: linux-kernel@vger.kernel.org, alex-kernel@digriz.org.uk,
jun.nakajima@intel.com, Linus Torvalds <torvalds@osdl.org>
Subject: OOPS: 2.6.16-rc6 cpufreq_conservative
Date: Sat, 18 Mar 2006 15:25:14 -0500 [thread overview]
Message-ID: <200603181525.14127.kernel-stuff@comcast.net> (raw)
I can reproduce the below OOPS by doing
$ modprobe cpufreq_conservative
$ echo conservative > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
$ echo conservative > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
Which brings up a question - Do we really support difference scaling governors
for different cpu cores?
This is a Centrino Duo Laptop.
Unable to handle kernel NULL pointer dereference at virtual address 0000001c
printing eip:
f834e6d0
*pde = 00000000
Oops: 0000 [#1]
PREEMPT SMP
Modules linked in: cpufreq_conservative oprofile ntfs snd_pcm_oss
snd_mixer_oss snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device eth1394
ohci1394 i2c_i801 i2c_core hw_random ipw3945 ieee80211 ieee80211_crypt
firmware_class snd_hda_intel snd_hda_codec snd_pcm snd_timer snd
snd_page_alloc i915 drm cpufreq_ondemand speedstep_centrino b44
CPU: 1
EIP: 0060:[<f834e6d0>] Not tainted VLI
EFLAGS: 00010206 (2.6.16-rc6 #3)
EIP is at dbs_check_cpu+0x220/0x400 [cpufreq_conservative]
eax: 00000000 ebx: 00000001 ecx: 00000001 edx: 7840d1bc
esi: 78445730 edi: 00000002 ebp: 78445730 esp: 7a1c1ef0
ds: 007b es: 007b ss: 0068
Process events/1 (pid: 9, threadinfo=7a1c0000 task=7a33fa90)
Stack: <0>7840d1bc 00000002 00000001 7a2d3a80 00000000 f834f704 7a1aa1c0
00000000
f834e938 00000000 00000202 7a1c0000 f834f700 78132869 00000000 00000000
18a60e00 7a1aa1d0 7a1aa1e8 f834e8b0 00000202 7a1c0000 7a1aa1d8 7a1aa1d0
Call Trace:
[<f834e938>] do_dbs_timer+0x88/0xc0 [cpufreq_conservative]
[<78132869>] run_workqueue+0x79/0xf0
[<f834e8b0>] do_dbs_timer+0x0/0xc0 [cpufreq_conservative]
[<78132a38>] worker_thread+0x158/0x180
[<7811b0d0>] default_wake_function+0x0/0x20
[<7811b0d0>] default_wake_function+0x0/0x20
[<781328e0>] worker_thread+0x0/0x180
[<7813664c>] kthread+0xbc/0x100
[<78136590>] kthread+0x0/0x100
[<78101285>] kernel_thread_helper+0x5/0x10
Code: 0f bc c0 83 f8 03 bb 02 00 00 00 0f 4c d8 83 fb 01 77 49 89 ee 8d b6 00
00 00 00 8b 04 9d 04 80 44 78 bf 02 00 00 00 01 f0 8b 00 <8b> 40 1c 89 7c 24
04 c7 04 24 bc d1 40 78 89 04 9d 48 fa 34 f8
next reply other threads:[~2006-03-18 20:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-18 20:25 Parag Warudkar [this message]
2006-03-18 21:40 ` OOPS: 2.6.16-rc6 cpufreq_conservative Linus Torvalds
2006-03-18 22:09 ` Parag Warudkar
2006-03-18 23:12 ` Linus Torvalds
2006-03-18 22:26 ` Parag Warudkar
2006-03-19 0:53 ` Andrew Morton
2006-03-19 2:38 ` Linus Torvalds
2006-03-19 5:08 ` Paul Jackson
2006-03-19 17:43 ` Linus Torvalds
2006-03-19 18:46 ` Linus Torvalds
2006-03-19 19:02 ` Linus Torvalds
2006-03-19 19:33 ` Linus Torvalds
2006-03-19 19:40 ` Al Viro
2006-03-19 20:01 ` Linus Torvalds
2006-03-19 20:31 ` Linus Torvalds
2006-03-19 20:47 ` Andrew Morton
2006-03-19 22:18 ` Linus Torvalds
2006-03-19 22:35 ` Andrew Morton
2006-03-19 22:55 ` Linus Torvalds
2006-03-19 22:46 ` Linus Torvalds
2006-03-19 23:04 ` Andrew Morton
2006-03-19 20:57 ` Parag Warudkar
2006-03-20 6:12 ` Willy Tarreau
2006-03-20 6:26 ` Linus Torvalds
2006-03-20 7:18 ` Willy Tarreau
2006-03-21 6:32 ` Willy Tarreau
2006-03-20 8:22 ` Peter T. Breuer
2006-03-19 6:34 ` Parag Warudkar
2006-03-19 12:00 ` Alexander Clouter
2006-03-19 14:06 ` Parag Warudkar
2006-03-19 17:34 ` Alexander Clouter
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=200603181525.14127.kernel-stuff@comcast.net \
--to=kernel-stuff@comcast.net \
--cc=alex-kernel@digriz.org.uk \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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