Linux version 2.6.31-12.fc12.i686 (mockbuild@x86-4.fedora.phx.redhat.com) (gcc version 4.4.1 20090911 (Red Hat 4.4.1-13) (GCC) ) #1 SMP Mon Sep 14 02:27:06 EDT 2009 itrace.exp occasionally triggers this beauty: stap_966b4a66c1cd6e6c80c3b6b206f6649b_1372: systemtap: 0.9.9/0.142, base: f7d38000, memory: 24576+24576+1344+13600 data+text+ctx+net, probes: 5 ------------[ cut here ]------------ kernel BUG at kernel/exit.c:1048! invalid opcode: 0000 [#1] SMP last sysfs file: /sys/module/virtio_pci/sections/__mcount_loc Modules linked in: stap_966b4a66c1cd6e6c80c3b6b206f6649b_1372 uprobes netconsole iptable_nat nf_nat nfsd exportfs configfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc ipv6 dm_multipath uinput ppdev 8139too parport_pc i2c_piix4 i2c_core parport 8139cp virtio_balloon mii floppy virtio_pci [last unloaded: stap_5c4d9350d00a175dc03e834cff7f9622_1041] Pid: 7248, comm: ls_1401 Tainted: G W (2.6.31-12.fc12.i686 #1) EIP: 0060:[<c04489eb>] EFLAGS: 00210282 CPU: 3 EIP is at do_group_exit+0x2d/0x99 EAX: f2208000 EBX: f634b700 ECX: c046fe51 EDX: 4483a0fe ESI: 4483a0fe EDI: f23adfb4 EBP: f23adea0 ESP: f23ade90 DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Process ls_1401 (pid: 7248, ti=f23ac000 task=f2208000 task.ti=f23ac000) Stack: d33a9351 4483a0fe f23adf08 f23adfb4 f23adecc c04547d3 00200246 f6346e00 <0> f23adf88 f634b700 f6347304 d33a9351 f23adfb4 00000000 00000000 f23adfac <0> c0402c3f 00000000 d33a9351 f23adefc 00200246 d33a9351 f2208000 00000006 Call Trace: [<c04547d3>] ? get_signal_to_deliver+0x333/0x35b [<c0402c3f>] ? do_notify_resume+0x87/0x7a7 [<c046f084>] ? trace_hardirqs_off_caller+0x26/0xb7 [<c046f12e>] ? trace_hardirqs_off+0x19/0x2c [<c0403b58>] ? work_notifysig+0x13/0x1b Code: e5 57 56 53 83 ec 04 0f 1f 44 00 00 89 c6 65 a1 14 00 00 00 89 45 f0 31 c0 89 f2 64 a1 00 d0 ae c0 84 d2 8b 98 ec 03 00 00 79 04 <0f> 0b eb fe f6 43 58 08 75 06 83 7b 50 00 74 35 8b 73 48 eb 29 EIP: [<c04489eb>] do_group_exit+0x2d/0x99 SS:ESP 0068:f23ade90
Created attachment 4200 [details] generated c code for likely failing itrace test case
(In reply to comment #1) > Created an attachment (id=4200) > generated c code for likely failing itrace test case Is this C code the original output from a test script or has the C code been modified by hand?
*** Bug 10216 has been marked as a duplicate of this bug. ***
I've been working on diagnosing this problem. Some progress appears likely by revising the utrace callbacks and synchronization logic.
incomplete work snapshotted in pr10653-itrace-crashes branch
Hi, Frank. I saw the note you posted to the utrace-devel and systemtap mailing lists on Saturday. I presume you were directing that note at the x86 utrace folks. But if there's anything that I can do to help -- like running tests or collecting debug info -- please let me know.
believe fixed with commit d3b2005