From: Tom Duffy <tduffy@sun.com>
To: Andi Kleen <ak@suse.de>
Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: [discuss] [OOPS] powernow on smp dual core amd64
Date: Fri, 10 Jun 2005 11:46:36 -0700 [thread overview]
Message-ID: <1118429196.26791.15.camel@duffman> (raw)
In-Reply-To: <20050610165315.GI13234@wotan.suse.de>
[-- Attachment #1: Type: text/plain, Size: 3564 bytes --]
On Fri, 2005-06-10 at 18:53 +0200, Andi Kleen wrote:
> On Thu, Jun 09, 2005 at 04:46:19PM -0700, Tom Duffy wrote:
> > Got this panic when I recently upgraded my BIOS so that it supports k8
> > powernow on SMP dual-core.
>
> 2.6.12-rc has a dual core aware powernow k8 driver.
Despite the name of kernel, it is based off of 2.6.12-rc6.
Here is the panic on bootup.
Unable to handle kernel NULL pointer dereference at 0000000000000024 RIP:
<ffffffff8011dadc>{query_current_values_with_pending_wait+60}
PGD 3f255067 PUD 7fe7e067 PMD 0
Oops: 0002 [1] SMP
CPU 1
Modules linked in: mptscsih(U) mptbase(U) sd_mod scsi_mod
Pid: 33, comm: events/7 Not tainted 2.6.11-1.1381_FC5smp
RIP: 0010:[<ffffffff8011dadc>] sdb1 sdb2
<ffffffff8011dadc>{query_current_values_with_pending_wait+60}
RSP: 0018:ffff81007fd9fdc8 EFLAGS: 00010202
RAX: 000000000000000e RBX: 0000000000000000 RCX: 00000000c0010042
RDX: 0000000000000008 RSI: 0000000000000001 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffff81007fd9e000 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000080
R13: 0000000000000000 R14: 0000000000000292 R15: ffffffff80112950
FS: 00000000005a5858(0000) GS:ffffffff8050ec00(0000) knlGS:0000000000000000
CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 0000000000000024 CR3: 000000007fd76000 CR4: 00000000000006e0
Process events/7 (pid: 33, threadinfo ffff81007fd9e000, task ffff81007fd43070)
Stack: 0000000000000000 ffffffff8011e0b1 0000000000000001 ffff81007fa02d10
ffff81007fa02d40 ffffffff802e6f23 0000000000000000 0000000000000003
0000000000000001 0000000000000020
Call Trace:<ffffffff8011e0b1>{powernowk8_get+129} <ffffffff802e6f23>{cpufreq_get+115}
<ffffffff8011298a>{handle_cpufreq_delayed_get+58} <ffffffff8014b9dc>{worker_thread+476}
<ffffffff80134710>{default_wake_function+0} <ffffffff801326a3>{__wake_up_common+67}
<ffffffff8014b800>{worker_thread+0} <ffffffff80150469>{kthread+217}
<ffffffff80135c90>{schedule_tail+64} <ffffffff8010f76b>{child_rip+8}
<ffffffff8011d680>{flat_send_IPI_mask+0} <ffffffff80150390>{kthread+0}
<ffffffff8010f763>{child_rip+0}
Code: 89 47 24 89 57 20 31 c0 48 83 c4 08 c3 66 66 66 90 66 66 90
RIP <ffffffff8011dadc>{query_current_values_with_pending_wait+60} RSP <ffff81007fd9fdc8>
CR2: 0000000000000024
<3>Debug: sleeping function called from invalid context at include/linux/rwsem.h:43
in_atomic():0, irqs_disabled():1
Call Trace:<ffffffff8013abc5>{profile_task_exit+21} <ffffffff8013bfe2>{do_exit+34}
<ffffffff80267378>{do_unblank_screen+40} <ffffffff80124286>{do_page_fault+1926}
<ffffffff8035c032>{thread_return+0} <ffffffff8035c084>{thread_return+82}
<ffffffff8013433d>{activate_task+141} <ffffffff80112950>{handle_cpufreq_delayed_get+0}
<ffffffff8010f5b5>{error_exit+0} <ffffffff80112950>{handle_cpufreq_delayed_get+0}
<ffffffff8011dadc>{query_current_values_with_pending_wait+60}
<ffffffff8011e0b1>{powernowk8_get+129} <ffffffff802e6f23>{cpufreq_get+115}
<ffffffff8011298a>{handle_cpufreq_delayed_get+58} <ffffffff8014b9dc>{worker_thread+476}
<ffffffff80134710>{default_wake_function+0} <ffffffff801326a3>{__wake_up_common+67}
<ffffffff8014b800>{worker_thread+0} <ffffffff80150469>{kthread+217}
<ffffffff80135c90>{schedule_tail+64} <ffffffff8010f76b>{child_rip+8}
<ffffffff8011d680>{flat_send_IPI_mask+0} <ffffffff80150390>{kthread+0}
<ffffffff8010f763>{child_rip+0}
-tduffy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-06-10 18:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-09 23:46 [OOPS] powernow on smp dual core amd64 Tom Duffy
2005-06-10 16:53 ` [discuss] " Andi Kleen
2005-06-10 18:46 ` Tom Duffy [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-10 19:48 Langsdorf, Mark
2005-06-10 20:01 ` Andi Kleen
[not found] <84EA05E2CA77634C82730353CBE3A84301CFC14B@SAUSEXMB1.amd.com>
2005-06-13 21:27 ` Tom Duffy
2005-06-13 21:47 Langsdorf, Mark
2005-06-13 22:20 ` Tom Duffy
2005-06-13 22:38 ` Andi Kleen
2005-06-13 23:17 ` Zachary Amsden
2005-06-13 23:34 ` Andi Kleen
2005-06-13 22:44 Langsdorf, Mark
2005-06-13 22:47 ` Andi Kleen
2005-06-13 22:58 ` Tom Duffy
2005-06-13 23:35 ` Andi Kleen
2005-06-14 18:19 ` Tom Duffy
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=1118429196.26791.15.camel@duffman \
--to=tduffy@sun.com \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox