From: Lee Revell <rlrevell@joe-job.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Oops with oprofile + RT preempt 2.6.11-rc2-RT-V0.7.37-01
Date: Sun, 13 Feb 2005 01:07:15 -0500 [thread overview]
Message-ID: <1108274835.3739.2.camel@krustophenia.net> (raw)
Are there any known incompatibilities with oprofile and the RT preempt patch?
Lee
Oops: 0000 [#1]
PREEMPT
Modules linked in: realtime commoncap af_packet via_rhine mii crc32 ehci_hcd usbhid uhci_hcd usbcore via_
agp agpgart evdev snd_rtctimer snd_emu10k1_synth snd_emu10k1 snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_emux_synth snd_seq_virmidi s
nd_seq_midi_emul snd_seq_midi snd_rawmidi snd_seq_oss snd_seq_midi_event snd_seq snd_timer snd_seq_device snd_hwdep snd_util_mem snd snd_page_
alloc
CPU: 0
EIP: 0060:[oprofilefs_str_to_user+21/64] Not tainted VLI
EFLAGS: 00010246 (2.6.11-rc2-RT-V0.7.37-01)
EIP is at oprofilefs_str_to_user+0x15/0x40
eax: 00000000 ebx: 00000000 ecx: ffffffff edx: 00000000
esi: d593b6a0 edi: 00000000 ebp: cb966f6c esp: cb966f68
ds: 007b es: 007b ss: 0068 preempt: 00000001
Process cat (pid: 3290, threadinfo=cb966000 task=d083ce10)
Stack: cb966fa8 cb966f90 c01529ec 00000000 0804d038 00001000 cb966fa8 d593b6a0
fffffff7 0804d038 cb966fbc c0152cc1 d593b6a0 0804d038 00001000 cb966fa8
00000000 00000000 00000000 00000003 00001000 cb966000 c01026a4 00000003
Call Trace:
[show_stack+133/160] show_stack+0x85/0xa0 (32)
[show_registers+299/400] show_registers+0x12b/0x190 (40)
[die+219/384] die+0xdb/0x180 (52)
[do_page_fault+824/1629] do_page_fault+0x338/0x65d (212)
[error_code+43/48] error_code+0x2b/0x30 (64)
[vfs_read+188/320] vfs_read+0xbc/0x140 (36)
[sys_read+65/112] sys_read+0x41/0x70 (44)
[syscall_call+7/11] syscall_call+0x7/0xb (-4028)
---------------------------
| preempt count: 00000002 ]
| 2-level deep critical section nesting:
----------------------------------------
.. [die+56/384] .... die+0x38/0x180
.....[do_page_fault+824/1629] .. ( <= do_page_fault+0x338/0x65d)
.. [print_traces+19/80] .... print_traces+0x13/0x50
.....[show_stack+133/160] .. ( <= show_stack+0x85/0xa0)
Code: 89 43 44 89 53 48 89 d8 8b 5d fc 89 ec 5d c3 8d b4 26 00 00 00 00 55 89 e5 57 e8 ab 49 ee ff 8b 55
08 31 c0 b9 ff ff ff ff 89 d7 <f2> ae f7 d1 49 51 52 8b 45 14 8b 7d 10 50 57 8b 4d 0c 51 e8 73
<1>BUG: Unable to handle kernel NULL pointer dereference at virtual address 00000000
printing eip:
c02284a5
*pde = 00000000
next reply other threads:[~2005-02-13 6:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-13 6:07 Lee Revell [this message]
2005-02-13 13:00 ` Oops with oprofile + RT preempt 2.6.11-rc2-RT-V0.7.37-01 Philippe Elie
2005-02-13 13:30 ` Ingo Molnar
2005-02-14 0:55 ` Lee Revell
2005-02-14 1:16 ` Dave Jones
2005-02-17 20:05 ` Lee Revell
2005-02-17 20:11 ` Ingo Molnar
2005-02-13 13:02 ` Ingo Molnar
2005-02-13 13:15 ` Peter Zijlstra
2005-02-13 13:16 ` Ingo Molnar
2005-02-13 13:20 ` Peter Zijlstra
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=1108274835.3739.2.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.