From: William Cohen <wcohen@nc.rr.com>
To: eranian@hpl.hp.com
Cc: William Cohen <wcohen@redhat.com>,
perfctr-devel@lists.sourceforge.net, perfmon@napali.hpl.hp.com,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Perfctr-devel] 2.6.15-rc5-git3 perfmon2 new code base + libpfm
Date: Tue, 20 Dec 2005 16:05:02 +0000 [thread overview]
Message-ID: <43A82BAE.1010008@nc.rr.com> (raw)
In-Reply-To: <20051215231510.GC18796@frankl.hpl.hp.com>
Stephane Eranian wrote:
> Will,
>
> Ok, I found the two bugs you ran into. I also found
> a third one somewhat similar.
>
> Could you try the attached patch on top of what
> you have?
>
> I will check all the copy_from/to() tomorrow.
>
> Thanks.
Have you tried running the examples without the kernel module installed?
I think that one of the tracebacks in the earlier email was due to that.
Like the following:
Dec 20 10:39:01 trek kernel: Call Trace:
Dec 20 10:39:01 trek kernel: [<c0201ee7>] __pfm_create_context+0x167/0x440
Dec 20 10:39:01 trek kernel: [<c010400c>] __switch_to+0x15c/0x220
Dec 20 10:39:01 trek kernel: [<c0203f98>] sys_pfm_create_context+0x78/0xe0
Dec 20 10:39:01 trek kernel: [<c010569d>] syscall_call+0x7/0xb
I tried the patch. Things are still not working on the p6 machine with
the module installed. for "./task_smpl ls". The associated kernel backtrace:
Dec 20 10:29:47 trek kernel: Unable to handle kernel paging request at
virtual address 6b6b6ba7
Dec 20 10:29:47 trek kernel: printing eip:
Dec 20 10:29:47 trek kernel: c0202b51
Dec 20 10:29:47 trek kernel: *pde = 00000000
Dec 20 10:29:47 trek kernel: Oops: 0000 [#1]
Dec 20 10:29:47 trek kernel: SMP
Dec 20 10:29:47 trek kernel: Modules linked in: perfmon_p6 ipv6 lp
autofs4 rfcomm l2cap bluetooth sunrpc ipt_REJECT ipt_state ip_conntrack
nfnetlink iptable_filter ip_tables dm_mirror dm_mod video button battery
ac parport_pc parport snd_cs46xx snd_seq_dummy snd_emu10k1_synth
snd_emux_synth snd_seq_virmidi snd_seq_midi_emul snd_seq_oss
snd_seq_midi_event snd_emu10k1 snd_seq snd_rawmidi snd_pcm_oss
snd_seq_device snd_mixer_oss snd_ac97_codec snd_ac97_bus snd_pcm
snd_util_mem emu10k1_gp floppy gameport 3c59x snd_hwdep snd_timer snd
snd_page_alloc soundcore mii uhci_hcd hw_random i2c_i801 shpchp i2c_core
ext3 jbd
Dec 20 10:29:47 trek kernel: CPU: 1
Dec 20 10:29:47 trek kernel: EIP: 0060:[<c0202b51>] Not tainted VLI
Dec 20 10:29:47 trek kernel: EFLAGS: 00010282 (2.6.15-rc5-git3-perfop)
Dec 20 10:29:47 trek kernel: EIP is at pfm_smpl_fmt_put+0x11/0x60
Dec 20 10:29:47 trek kernel: eax: d6cc3ab0 ebx: 6b6b6b6b ecx:
d8be87a0 edx: d8be8900
Dec 20 10:29:47 trek kernel: esi: d2434000 edi: 00000001 ebp:
00000001 esp: d707cee0
Dec 20 10:29:47 trek kernel: ds: 007b es: 007b ss: 0068
Dec 20 10:29:47 trek kernel: Process task_smpl (pid: 2574,
threadinfo×07c000 taskÖcc3ab0)
Dec 20 10:29:47 trek kernel: Stack: 00000001 c0205813 c0156569 6b000246
c1336ae0 d2ab36e8 d2ab375c d7203548
Dec 20 10:29:47 trek kernel: 00000286 00000000 00000010 00000010
d2ab375c d2b8ab58 d7203548 c0172475
Dec 20 10:29:47 trek kernel: 00000000 d2ab36e8 d7f8fb68 d2b8ab58
d245dc7c d2f18664 d7276d9c 00000001
Dec 20 10:29:47 trek kernel: Call Trace:
Dec 20 10:29:47 trek kernel: [<c0205813>] pfm_close+0x113/0x3d0
Dec 20 10:29:47 trek kernel: [<c0156569>] poison_obj+0x29/0x60
Dec 20 10:29:47 trek kernel: [<c0172475>] __fput+0xb5/0x1a0
Dec 20 10:29:47 trek kernel: [<c01625e9>] remove_vma+0x39/0x50
Dec 20 10:29:47 trek kernel: [<c016477b>] exit_mmap+0xab/0x100
Dec 20 10:29:47 trek kernel: [<c0123423>] mmput+0x33/0xa0
Dec 20 10:29:47 trek kernel: [<c0128816>] do_exit+0xf6/0x3d0
Dec 20 10:29:47 trek kernel: [<c0109da8>] do_syscall_trace+0x218/0x22a
Dec 20 10:29:47 trek kernel: [<c0128b67>] do_group_exit+0x37/0xa0
Dec 20 10:29:47 trek kernel: [<c010569d>] syscall_call+0x7/0xb
Dec 20 10:29:47 trek kernel: Code: 00 01 00 00 ff 00 b8 80 4c 44 c0 e8
aa d2 16 00 89 d8 5b c3 31 db eb ee 89 f6 85 c0 53 89 c3 74 39 b8 80 4c
44 c0 e8 6f d2 16 00 <8b> 53 3c 85 d2 74 1b b8 00 f0 ff ff 21 e0 8b 40
10 c1 e0 07 8d
Dec 20 10:29:47 trek kernel: <1>Fixing recursive fault but reboot is
needed!
-Will
WARNING: multiple messages have this Message-ID (diff)
From: William Cohen <wcohen@nc.rr.com>
To: eranian@hpl.hp.com
Cc: William Cohen <wcohen@redhat.com>,
perfctr-devel@lists.sourceforge.net, perfmon@napali.hpl.hp.com,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Perfctr-devel] 2.6.15-rc5-git3 perfmon2 new code base + libpfm available
Date: Tue, 20 Dec 2005 11:05:02 -0500 [thread overview]
Message-ID: <43A82BAE.1010008@nc.rr.com> (raw)
In-Reply-To: <20051215231510.GC18796@frankl.hpl.hp.com>
Stephane Eranian wrote:
> Will,
>
> Ok, I found the two bugs you ran into. I also found
> a third one somewhat similar.
>
> Could you try the attached patch on top of what
> you have?
>
> I will check all the copy_from/to() tomorrow.
>
> Thanks.
Have you tried running the examples without the kernel module installed?
I think that one of the tracebacks in the earlier email was due to that.
Like the following:
Dec 20 10:39:01 trek kernel: Call Trace:
Dec 20 10:39:01 trek kernel: [<c0201ee7>] __pfm_create_context+0x167/0x440
Dec 20 10:39:01 trek kernel: [<c010400c>] __switch_to+0x15c/0x220
Dec 20 10:39:01 trek kernel: [<c0203f98>] sys_pfm_create_context+0x78/0xe0
Dec 20 10:39:01 trek kernel: [<c010569d>] syscall_call+0x7/0xb
I tried the patch. Things are still not working on the p6 machine with
the module installed. for "./task_smpl ls". The associated kernel backtrace:
Dec 20 10:29:47 trek kernel: Unable to handle kernel paging request at
virtual address 6b6b6ba7
Dec 20 10:29:47 trek kernel: printing eip:
Dec 20 10:29:47 trek kernel: c0202b51
Dec 20 10:29:47 trek kernel: *pde = 00000000
Dec 20 10:29:47 trek kernel: Oops: 0000 [#1]
Dec 20 10:29:47 trek kernel: SMP
Dec 20 10:29:47 trek kernel: Modules linked in: perfmon_p6 ipv6 lp
autofs4 rfcomm l2cap bluetooth sunrpc ipt_REJECT ipt_state ip_conntrack
nfnetlink iptable_filter ip_tables dm_mirror dm_mod video button battery
ac parport_pc parport snd_cs46xx snd_seq_dummy snd_emu10k1_synth
snd_emux_synth snd_seq_virmidi snd_seq_midi_emul snd_seq_oss
snd_seq_midi_event snd_emu10k1 snd_seq snd_rawmidi snd_pcm_oss
snd_seq_device snd_mixer_oss snd_ac97_codec snd_ac97_bus snd_pcm
snd_util_mem emu10k1_gp floppy gameport 3c59x snd_hwdep snd_timer snd
snd_page_alloc soundcore mii uhci_hcd hw_random i2c_i801 shpchp i2c_core
ext3 jbd
Dec 20 10:29:47 trek kernel: CPU: 1
Dec 20 10:29:47 trek kernel: EIP: 0060:[<c0202b51>] Not tainted VLI
Dec 20 10:29:47 trek kernel: EFLAGS: 00010282 (2.6.15-rc5-git3-perfop)
Dec 20 10:29:47 trek kernel: EIP is at pfm_smpl_fmt_put+0x11/0x60
Dec 20 10:29:47 trek kernel: eax: d6cc3ab0 ebx: 6b6b6b6b ecx:
d8be87a0 edx: d8be8900
Dec 20 10:29:47 trek kernel: esi: d2434000 edi: 00000001 ebp:
00000001 esp: d707cee0
Dec 20 10:29:47 trek kernel: ds: 007b es: 007b ss: 0068
Dec 20 10:29:47 trek kernel: Process task_smpl (pid: 2574,
threadinfo=d707c000 task=d6cc3ab0)
Dec 20 10:29:47 trek kernel: Stack: 00000001 c0205813 c0156569 6b000246
c1336ae0 d2ab36e8 d2ab375c d7203548
Dec 20 10:29:47 trek kernel: 00000286 00000000 00000010 00000010
d2ab375c d2b8ab58 d7203548 c0172475
Dec 20 10:29:47 trek kernel: 00000000 d2ab36e8 d7f8fb68 d2b8ab58
d245dc7c d2f18664 d7276d9c 00000001
Dec 20 10:29:47 trek kernel: Call Trace:
Dec 20 10:29:47 trek kernel: [<c0205813>] pfm_close+0x113/0x3d0
Dec 20 10:29:47 trek kernel: [<c0156569>] poison_obj+0x29/0x60
Dec 20 10:29:47 trek kernel: [<c0172475>] __fput+0xb5/0x1a0
Dec 20 10:29:47 trek kernel: [<c01625e9>] remove_vma+0x39/0x50
Dec 20 10:29:47 trek kernel: [<c016477b>] exit_mmap+0xab/0x100
Dec 20 10:29:47 trek kernel: [<c0123423>] mmput+0x33/0xa0
Dec 20 10:29:47 trek kernel: [<c0128816>] do_exit+0xf6/0x3d0
Dec 20 10:29:47 trek kernel: [<c0109da8>] do_syscall_trace+0x218/0x22a
Dec 20 10:29:47 trek kernel: [<c0128b67>] do_group_exit+0x37/0xa0
Dec 20 10:29:47 trek kernel: [<c010569d>] syscall_call+0x7/0xb
Dec 20 10:29:47 trek kernel: Code: 00 01 00 00 ff 00 b8 80 4c 44 c0 e8
aa d2 16 00 89 d8 5b c3 31 db eb ee 89 f6 85 c0 53 89 c3 74 39 b8 80 4c
44 c0 e8 6f d2 16 00 <8b> 53 3c 85 d2 74 1b b8 00 f0 ff ff 21 e0 8b 40
10 c1 e0 07 8d
Dec 20 10:29:47 trek kernel: <1>Fixing recursive fault but reboot is
needed!
-Will
next prev parent reply other threads:[~2005-12-20 16:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 10:46 2.6.15-rc5-git3 perfmon2 new code base + libpfm available Stephane Eranian
2005-12-15 10:46 ` Stephane Eranian
2005-12-15 21:22 ` [Perfctr-devel] 2.6.15-rc5-git3 perfmon2 new code base + libpfm William Cohen
2005-12-15 21:22 ` [Perfctr-devel] 2.6.15-rc5-git3 perfmon2 new code base + libpfm available William Cohen
2005-12-15 21:59 ` Stephane Eranian
2005-12-15 21:59 ` Stephane Eranian
2005-12-15 22:23 ` [Perfctr-devel] 2.6.15-rc5-git3 perfmon2 new code base + libpfm William Cohen
2005-12-15 22:23 ` [Perfctr-devel] 2.6.15-rc5-git3 perfmon2 new code base + libpfm available William Cohen
2005-12-15 23:15 ` Stephane Eranian
2005-12-15 23:15 ` Stephane Eranian
2005-12-20 16:05 ` William Cohen [this message]
2005-12-20 16:05 ` William Cohen
2005-12-20 16:54 ` Matthew Wilcox
2005-12-20 16:54 ` Matthew Wilcox
2005-12-20 18:07 ` 2.6.15-rc6 updated perfmon2 patch Stephane Eranian
2005-12-20 18:07 ` Stephane Eranian
2005-12-21 22:09 ` new 2.6.15-rc6 " Stephane Eranian
2005-12-21 22:09 ` Stephane Eranian
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=43A82BAE.1010008@nc.rr.com \
--to=wcohen@nc.rr.com \
--cc=eranian@hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perfctr-devel@lists.sourceforge.net \
--cc=perfmon@napali.hpl.hp.com \
--cc=wcohen@redhat.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 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.