registration error (rc -84) and -DSTP_OVERLOAD_THRESHOLD

registration error (rc -84) and -DSTP_OVERLOAD_THRESHOLD

[Daniel Migault]

Hi,

While running my tap script, I receive WARNINGs and would like to knwo 
how to consider them. Does it means that matching between source code 
and memory address presents dome differences? If so, is there any way to 
correct this mismatch ? How does it really impact the probe? For 
exmaple, does a probe on tcp_new_space for example don't consider the 
function ?

Pass 5: starting run.
WARNING: probe 
kernel.function("tcp_new_space@net/ipv4/tcp_input.c:4885") (address 
0xffffffff814064f0) registration error (rc -84)
WARNING: probe 
kernel.function("tcp_update_reordering@net/ipv4/tcp_input.c:935") 
(address 0xffffffff81404578) registration error (rc -84)
WARNING: probe 
kernel.function("tcp_should_expand_sndbuf@net/ipv4/tcp_input.c:4854") 
(address 0xffffffff814064f0) registration error (rc -84)
WARNING: probe 
kernel.function("ablkcipher_get_spot@crypto/ablkcipher.c:71") (address 
0xffffffff812059bc) registration error (rc -84)
[...]

By the way, I also noticed some problems with the 
-DSTP_OVERLOAD_THRESHOLD. The script does not run and sometime it may 
result by frezzing the OS. We don't have any problems with the 
-DSTP_NO_OVERLOAD option for example. I am using gcc version 4.6.0 
20110509 (Red Hat 4.6.0-7) (GCC).

stap -g --vp 00001 -DSTP_OVERLOAD_THRESHOLD script.stp

[root@fedora-amd64 systemtap.git]#
Pass 5: run failed.  Try again with another '--vp 00001' option.
[root@fedora-amd64 systemtap-script]#

Regards,

Daniel

Re: registration error (rc -84) and -DSTP_OVERLOAD_THRESHOLD

[Frank Ch. Eigler]

mglt.biz wrote:

> [...]  While running my tap script, I receive WARNINGs and would
> like to knwo how to consider them. [...]

> WARNING: probe
> kernel.function("tcp_new_space@net/ipv4/tcp_input.c:4885") (address
> 0xffffffff814064f0) registration error (rc -84)

This is an error (-EILSEQ) that comes from the kernel, most likely
arch/x86/kernel/kprobes.c.  It may be a somehow blacklisted function,
or perhaps a problem with the 'optimized kprobes' widget.  It may help
to get a vmlinux disassembly around that 0xffffffff814064f0 address.


> How does it really impact the probe? For exmaple, does a probe on
> tcp_new_space for example don't consider the function ?

That's correct, such a probe will just not be activated, and its
handler never run.


> By the way, I also noticed some problems with the
> -DSTP_OVERLOAD_THRESHOLD. The script does not run and sometime it
> may result by frezzing the OS. We don't have any problems with the
> -DSTP_NO_OVERLOAD option for example. [...]

We'd probably need some more details.  Mis-set THRESHOLD type values
should do no worse than abort the script prematurely.  Try 
   # stap -t -v
Share the script and its invocation.

- FChE

Re: registration error (rc -84) and -DSTP_OVERLOAD_THRESHOLD

[Richard W.M. Jones]

On Wed, Jun 01, 2011 at 09:37:31AM -0400, Frank Ch. Eigler wrote:
> 
> mglt.biz wrote:
> 
> > [...]  While running my tap script, I receive WARNINGs and would
> > like to knwo how to consider them. [...]
> 
> > WARNING: probe
> > kernel.function("tcp_new_space@net/ipv4/tcp_input.c:4885") (address
> > 0xffffffff814064f0) registration error (rc -84)
> 
> This is an error (-EILSEQ) that comes from the kernel, most likely
> arch/x86/kernel/kprobes.c.  It may be a somehow blacklisted function,
> or perhaps a problem with the 'optimized kprobes' widget.  It may help
> to get a vmlinux disassembly around that 0xffffffff814064f0 address.

I'm also receiving these warnings.  My script attempts to add a probe
at every line in a module (yes, there's a good reason for it):

  probe module("ext2").statement ("*@*.c:*") {
    printf ("%s\n", pp());
  }

and I get maybe about 100 warnings like this:

  WARNING: probe module("ext2").statement("ext2_try_to_allocate_with_rsv@fs/ext2/balloc.c:1162") (address 0xffffffffa055f982) registration error (rc -84)
  WARNING: probe module("ext2").statement("ext2_new_blocks@fs/ext2/balloc.c:1270") (address 0xffffffffa055ff3b) registration error (rc -84)
  WARNING: probe module("ext2").statement("ext2_new_blocks@fs/ext2/balloc.c:1272") (address 0xffffffffa055ff3e) registration error (rc -84)
  WARNING: probe module("ext2").statement("ext2_new_blocks@fs/ext2/balloc.c:1277") (address 0xffffffffa055ffd4) registration error (rc -84)
  WARNING: probe module("ext2").statement("ext2_readdir@fs/ext2/dir.c:342") (address 0xffffffffa056098f) registration error (rc -84)
  WARNING: probe module("ext2").statement("ext2_find_entry@fs/ext2/dir.c:426") (address 0xffffffffa0560b28) registration error (rc -84)

Apart from the warnings, systemtap functions correctly.

Because these addresses are in a module, I couldn't work out the right
invocation of gdb / objdump to get it to disassemble those addresses.
But if you tell me how, I'll be glad to provide that information.

Fedora 15, 2.6.38.7-30.fc15.x86_64

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-p2v converts physical machines to virtual machines.  Boot with a
live CD or over the network (PXE) and turn machines into Xen guests.
http://et.redhat.com/~rjones/virt-p2v

Re: registration error (rc -84) and -DSTP_OVERLOAD_THRESHOLD

[Frank Ch. Eigler]

Hi, Rich -

> > > kernel.function("tcp_new_space@net/ipv4/tcp_input.c:4885") (address
> > > 0xffffffff814064f0) registration error (rc -84)
> > 
> > This is an error (-EILSEQ) that comes from the kernel, most likely
> > arch/x86/kernel/kprobes.c.  It may be a somehow blacklisted function,
> > or perhaps a problem with the 'optimized kprobes' widget.  It may help
> > to get a vmlinux disassembly around that 0xffffffff814064f0 address.
> 
> I'm also receiving these warnings.  My script attempts to add a probe
> at every line in a module (yes, there's a good reason for it):

(Neat, it'd be interesting to hear more of the story, once you're done.)

>   probe module("ext2").statement ("*@*.c:*") {
>     printf ("%s\n", pp());
>   }
> 
> and I get maybe about 100 warnings like this:
> 
>   WARNING: probe module("ext2").statement("ext2_try_to_allocate_with_rsv@fs/ext2/balloc.c:1162") (address 0xffffffffa055f982) registration error (rc -84)
>   WARNING: probe module("ext2").statement("ext2_new_blocks@fs/ext2/balloc.c:1270") (address 0xffffffffa055ff3b) registration error (rc -84)
>   [...]
> Apart from the warnings, systemtap functions correctly.
> 
> Because these addresses are in a module, I couldn't work out the right
> invocation of gdb / objdump to get it to disassemble those addresses.
> But if you tell me how, I'll be glad to provide that information.

You could rerun with stap -p2, when it tells you more about probe placement:

% stap -p2 -e 'probe module("ext2").statement ("*@*.c:*") {}'
[...]
module("ext2").statement("try_to_extend_reservation@fs/ext2/balloc.c") /* pc=.text+0xdb3 */ /* <- module("ext2").statement("*@*.c:*") */
module("ext2").statement("ext2_try_to_allocate_with_rsv@fs/ext2/balloc.c:1061") /* pc=.text+0xdbe */ /* <- module("ext2").statement("*@*.c:*") */
module("ext2").statement("try_to_extend_reservation@fs/ext2/balloc.c") /* pc=.text+0xdbe */ /* <- module("ext2").statement("*@*.c:*") */
[...]

Look for the pc=.text+0xdbe offset field in there.  That'd be area to sic objdump onto:
[...]
     db3:       48 89 df                mov    %rbx,%rdi
     db6:       41 89 cf                mov    %ecx,%r15d
     db9:       e8 00 00 00 00          callq  dbe <ext2_try_to_allocate_with_rsv+0x459>
                        dba: R_X86_64_PC32      rb_next-0x4
     dbe:       48 85 c0                test   %rax,%rax
     dc1:       4d 63 ff                movslq %r15d,%r15
[...]

(By the way, on my f13 x86-64 host, and rhel6 i686 vm's, I get none of
the -EILSEQ warnings.)


- FChE

Re: registration error (rc -84) and -DSTP_OVERLOAD_THRESHOLD

[Richard W.M. Jones]

On Tue, Jun 14, 2011 at 09:53:56AM -0400, Frank Ch. Eigler wrote:
> Look for the pc=.text+0xdbe offset field in there.  That'd be area
> to sic objdump onto:

What would I objdump?  /proc/kcore??  Can you show me an example
command line?

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine.  Supports Linux and Windows.
http://et.redhat.com/~rjones/virt-df/

Re: registration error (rc -84) and -DSTP_OVERLOAD_THRESHOLD

[Frank Ch. Eigler]

Hi -

On Tue, Jun 14, 2011 at 03:08:12PM +0100, Richard W.M. Jones wrote:
> On Tue, Jun 14, 2011 at 09:53:56AM -0400, Frank Ch. Eigler wrote:
> > Look for the pc=.text+0xdbe offset field in there.  That'd be area
> > to sic objdump onto:
> 
> What would I objdump?  /proc/kcore??  Can you show me an example
> command line?

% objdump -drS /lib/modules/`uname -r`/kernel/fs/ext2/ext2.ko

- FChE

Re: registration error (rc -84) and -DSTP_OVERLOAD_THRESHOLD

[Richard W.M. Jones]

On Tue, Jun 14, 2011 at 10:09:43AM -0400, Frank Ch. Eigler wrote:
> Hi -
> 
> On Tue, Jun 14, 2011 at 03:08:12PM +0100, Richard W.M. Jones wrote:
> > On Tue, Jun 14, 2011 at 09:53:56AM -0400, Frank Ch. Eigler wrote:
> > > Look for the pc=.text+0xdbe offset field in there.  That'd be area
> > > to sic objdump onto:
> > 
> > What would I objdump?  /proc/kcore??  Can you show me an example
> > command line?
> 
> % objdump -drS /lib/modules/`uname -r`/kernel/fs/ext2/ext2.ko

Oh I see.

stap after phase 2 shows this for one of the problematic probes:

module("ext2").statement("ext2_try_to_allocate_with_rsv@fs/ext2/balloc.c:1162") /* pc=.text+0x982 */ /* <- module("ext2").statement("*@*.c:*") */

and here is the disassembled code around that place in the module:

     972:       e8 00 00 00 00          callq  977 <ext2_try_to_allocate_with_rs
v+0x3ba>
                        973: R_X86_64_PC32      _raw_spin_trylock-0x4
     977:       85 c0                   test   %eax,%eax
     979:       48 8b 8d 50 ff ff ff    mov    -0xb0(%rbp),%rcx
     980:       74 4d                   je     9cf <ext2_try_to_allocate_with_rs
v+0x412>
     982:       44 29 f9                sub    %r15d,%ecx
     985:       48 89 df                mov    %rbx,%rdi
     988:       41 89 cf                mov    %ecx,%r15d
     98b:       e8 00 00 00 00          callq  990 <ext2_try_to_allocate_with_rsv+0x3d3>
                        98c: R_X86_64_PC32      rb_next-0x4
     990:       48 85 c0                test   %rax,%rax
     993:       4d 63 ff                movslq %r15d,%r15
     996:       48 8b 95 58 ff ff ff    mov    -0xa8(%rbp),%rdx
     99d:       75 06                   jne    9a5 <ext2_try_to_allocate_with_rsv+0x3e8>
     99f:       4c 01 7b 28             add    %r15,0x28(%rbx)

Here's another one picked at random:

module("ext2").statement("ext2_readdir@fs/ext2/dir.c:342") /* pc=.text+0x198f */ /* <- module("ext2").statement("*@*.c:*") */

    197e:       e9 8f 00 00 00          jmpq   1a12 <ext2_readdir+0x28c>
    1983:       45 8b 04 24             mov    (%r12),%r8d
    1987:       45 85 c0                test   %r8d,%r8d
    198a:       74 47                   je     19d3 <ext2_readdir+0x24d>
    198c:       45 31 c9                xor    %r9d,%r9d
    198f:       4d 85 ff                test   %r15,%r15
    1992:       74 10                   je     19a4 <ext2_readdir+0x21e>
    1994:       41 8a 44 24 07          mov    0x7(%r12),%al
    1999:       3c 07                   cmp    $0x7,%al
    199b:       77 07                   ja     19a4 <ext2_readdir+0x21e>
    199d:       0f b6 c0                movzbl %al,%eax
    19a0:       45 8a 0c 07             mov    (%r15,%rax,1),%r9b

HTH, Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine.  Supports Linux and Windows.
http://et.redhat.com/~rjones/virt-df/

Re: registration error (rc -84) and -DSTP_OVERLOAD_THRESHOLD

[Frank Ch. Eigler]

Hi -

rjones wrote:

> [...]
> module("ext2").statement("ext2_try_to_allocate_with_rsv@fs/ext2/balloc.c:1162") /* pc=.text+0x982 */ /* <- module("ext2").statement("*@*.c:*") */
> 
> and here is the disassembled code around that place in the module:
> 
> [...]
>      980:       74 4d                   je     9cf <ext2_try_to_allocate_with_rs
> v+0x412>
>      982:       44 29 f9                sub    %r15d,%ecx
> [...]

That doesn't look particularly scary.  However, recent versions of the
kernel have started to attempt manual decoding of the instruction
stream being kprobe'd in order to verify instruction boundaries.  It
could be that this check is not working correctly.

See kernel arch/x86/kernel/kprobes can_probe().  Unfortunately that
function is not particularly chatty about its error cases, and it's
marked __kprobes to prevent itself from being kprobed.  (That bit is
almost certainly unnecessary and counterproductive.)

If this is the problem, I believe a whole series of addresses past a
given troublemaker would exhibit this failure, on a per-function
basis.  Are the problem probe addresses in sequential sub-sequences?
Disassembling at the start would be helpful.

- FChE

Re: registration error (rc -84) and -DSTP_OVERLOAD_THRESHOLD

[Richard W.M. Jones]

[-- Attachment #1: Type: text/plain, Size: 6345 bytes --]

On Tue, Jun 14, 2011 at 11:51:25AM -0400, Frank Ch. Eigler wrote:
> Hi -
> 
> rjones wrote:
> 
> > [...]
> > module("ext2").statement("ext2_try_to_allocate_with_rsv@fs/ext2/balloc.c:1162") /* pc=.text+0x982 */ /* <- module("ext2").statement("*@*.c:*") */
> > 
> > and here is the disassembled code around that place in the module:
> > 
> > [...]
> >      980:       74 4d                   je     9cf <ext2_try_to_allocate_with_rs
> > v+0x412>
> >      982:       44 29 f9                sub    %r15d,%ecx
> > [...]
> 
> That doesn't look particularly scary.  However, recent versions of the
> kernel have started to attempt manual decoding of the instruction
> stream being kprobe'd in order to verify instruction boundaries.  It
> could be that this check is not working correctly.
> 
> See kernel arch/x86/kernel/kprobes can_probe().  Unfortunately that
> function is not particularly chatty about its error cases, and it's
> marked __kprobes to prevent itself from being kprobed.  (That bit is
> almost certainly unnecessary and counterproductive.)
> 
> If this is the problem, I believe a whole series of addresses past a
> given troublemaker would exhibit this failure, on a per-function
> basis.  Are the problem probe addresses in sequential sub-sequences?
> Disassembling at the start would be helpful.

Attached is the complete list of warnings.  Some of the addresses look
like they could come in sequences, while others not so much.

Disassembling super.c:1391 (pc=.text+0x63c2) through super.c:1429
(pc=.text+0x64da) looks like this:

    63a4:	31 c0                	xor    %eax,%eax
    63a6:	4c 8b 7f 18          	mov    0x18(%rdi),%r15
    63aa:	48 63 f6             	movslq %esi,%rsi
    63ad:	48 89 95 58 ff ff ff 	mov    %rdx,-0xa8(%rbp)
    63b4:	49 89 cc             	mov    %rcx,%r12
    63b7:	48 8b b4 f7 88 01 00 	mov    0x188(%rdi,%rsi,8),%rsi
    63be:	00 
    63bf:	48 89 fb             	mov    %rdi,%rbx
    63c2:	8a 4f 15             	mov    0x15(%rdi),%cl
    63c5:	48 8b 96 c8 00 00 00 	mov    0xc8(%rsi),%rdx
    63cc:	48 89 b5 50 ff ff ff 	mov    %rsi,-0xb0(%rbp)
    63d3:	49 39 d0             	cmp    %rdx,%r8
    63d6:	0f 8f fe 00 00 00    	jg     64da <ext2_quota_read+0x14f>
    63dc:	4b 8d 34 20          	lea    (%r8,%r12,1),%rsi
    63e0:	48 89 d0             	mov    %rdx,%rax
    63e3:	4d 89 c6             	mov    %r8,%r14
    63e6:	4c 29 c0             	sub    %r8,%rax
    63e9:	48 39 d6             	cmp    %rdx,%rsi
    63ec:	4c 0f 47 e0          	cmova  %rax,%r12
    63f0:	41 ff cf             	dec    %r15d
    63f3:	49 d3 fe             	sar    %cl,%r14
    63f6:	45 21 c7             	and    %r8d,%r15d
    63f9:	4d 89 e5             	mov    %r12,%r13
    63fc:	e9 c4 00 00 00       	jmpq   64c5 <ext2_quota_read+0x13a>
    6401:	4c 8b 4b 18          	mov    0x18(%rbx),%r9
    6405:	48 8b bd 50 ff ff ff 	mov    -0xb0(%rbp),%rdi
    640c:	48 8d 95 68 ff ff ff 	lea    -0x98(%rbp),%rdx
    6413:	31 c9                	xor    %ecx,%ecx
    6415:	4c 89 f6             	mov    %r14,%rsi
    6418:	48 c7 85 68 ff ff ff 	movq   $0x0,-0x98(%rbp)
    641f:	00 00 00 00 
    6423:	4c 89 4d 88          	mov    %r9,-0x78(%rbp)
    6427:	4c 89 8d 48 ff ff ff 	mov    %r9,-0xb8(%rbp)
    642e:	e8 00 00 00 00       	callq  6433 <ext2_quota_read+0xa8>
			642f: R_X86_64_PC32	ext2_get_block-0x4
    6433:	85 c0                	test   %eax,%eax
    6435:	4c 8b 8d 48 ff ff ff 	mov    -0xb8(%rbp),%r9
    643c:	79 07                	jns    6445 <ext2_quota_read+0xba>
    643e:	48 98                	cltq   
    6440:	e9 95 00 00 00       	jmpq   64da <ext2_quota_read+0x14f>
    6445:	4d 63 c7             	movslq %r15d,%r8
    6448:	48 8b 85 68 ff ff ff 	mov    -0x98(%rbp),%rax
    644f:	4d 89 ef             	mov    %r13,%r15
    6452:	4d 29 c1             	sub    %r8,%r9
    6455:	4d 39 e9             	cmp    %r13,%r9
    6458:	4d 0f 46 f9          	cmovbe %r9,%r15
    645c:	a8 20                	test   $0x20,%al
    645e:	75 10                	jne    6470 <ext2_quota_read+0xe5>
    6460:	48 8b bd 58 ff ff ff 	mov    -0xa8(%rbp),%rdi
    6467:	49 63 cf             	movslq %r15d,%rcx
    646a:	31 c0                	xor    %eax,%eax
    646c:	f3 aa                	rep stos %al,%es:(%rdi)
    646e:	eb 42                	jmp    64b2 <ext2_quota_read+0x127>
    6470:	48 8b 53 18          	mov    0x18(%rbx),%rdx
    6474:	48 8b bb f8 00 00 00 	mov    0xf8(%rbx),%rdi
    647b:	48 8b 75 80          	mov    -0x80(%rbp),%rsi
    647f:	4c 89 85 48 ff ff ff 	mov    %r8,-0xb8(%rbp)
    6486:	e8 00 00 00 00       	callq  648b <ext2_quota_read+0x100>
			6487: R_X86_64_PC32	__bread-0x4
    648b:	48 85 c0             	test   %rax,%rax
    648e:	4c 8b 85 48 ff ff ff 	mov    -0xb8(%rbp),%r8
    6495:	74 3c                	je     64d3 <ext2_quota_read+0x148>
    6497:	4c 89 c6             	mov    %r8,%rsi
    649a:	48 03 70 28          	add    0x28(%rax),%rsi
    649e:	49 63 cf             	movslq %r15d,%rcx
    64a1:	48 8b bd 58 ff ff ff 	mov    -0xa8(%rbp),%rdi
    64a8:	f3 a4                	rep movsb %ds:(%rsi),%es:(%rdi)
    64aa:	48 89 c7             	mov    %rax,%rdi
    64ad:	e8 7c fc ff ff       	callq  612e <brelse>
    64b2:	4d 63 ff             	movslq %r15d,%r15
    64b5:	49 ff c6             	inc    %r14
    64b8:	4c 01 bd 58 ff ff ff 	add    %r15,-0xa8(%rbp)
    64bf:	4d 29 fd             	sub    %r15,%r13
    64c2:	45 31 ff             	xor    %r15d,%r15d
    64c5:	4d 85 ed             	test   %r13,%r13
    64c8:	0f 85 33 ff ff ff    	jne    6401 <ext2_quota_read+0x76>
    64ce:	4c 89 e0             	mov    %r12,%rax
    64d1:	eb 07                	jmp    64da <ext2_quota_read+0x14f>
    64d3:	48 c7 c0 fb ff ff ff 	mov    $0xfffffffffffffffb,%rax
    64da:	48 81 c4 98 00 00 00 	add    $0x98,%rsp
    64e1:	5b                   	pop    %rbx
    64e2:	41 5c                	pop    %r12
    64e4:	41 5d                	pop    %r13
    64e6:	41 5e                	pop    %r14
    64e8:	41 5f                	pop    %r15
    64ea:	5d                   	pop    %rbp
    64eb:	c3                   	retq   

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-p2v converts physical machines to virtual machines.  Boot with a
live CD or over the network (PXE) and turn machines into Xen guests.
http://et.redhat.com/~rjones/virt-p2v

[-- Attachment #2: warnings.txt --]
[-- Type: text/plain, Size: 6850 bytes --]

WARNING: probe module("ext2").statement("ext2_try_to_allocate_with_rsv@fs/ext2/balloc.c:1125") (address 0xffffffffa055f605) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_try_to_allocate_with_rsv@fs/ext2/balloc.c:1162") (address 0xffffffffa055f982) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_new_blocks@fs/ext2/balloc.c:1270") (address 0xffffffffa055ff3b) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_new_blocks@fs/ext2/balloc.c:1272") (address 0xffffffffa055ff3e) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_new_blocks@fs/ext2/balloc.c:1277") (address 0xffffffffa055ffd4) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_find_entry@fs/ext2/dir.c:426") (address 0xffffffffa0560b28) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_add_link@fs/ext2/dir.c:530") (address 0xffffffffa0560fc5) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_add_link@fs/ext2/dir.c:532") (address 0xffffffffa0560fca) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_delete_entry@fs/ext2/dir.c:597") (address 0xffffffffa05611d3) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_delete_entry@fs/ext2/dir.c:616") (address 0xffffffffa05612aa) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_new_inode@fs/ext2/ialloc.c:300") (address 0xffffffffa0561ad2) registration error (rc -84)
WARNING: probe module("ext2").statement("find_group_orlov@fs/ext2/ialloc.c") (address 0xffffffffa0561ad2) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_new_inode@fs/ext2/ialloc.c:383") (address 0xffffffffa0561c82) registration error (rc -84)
WARNING: probe module("ext2").statement("find_group_other@fs/ext2/ialloc.c") (address 0xffffffffa0561c82) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_get_inode@fs/ext2/inode.c:1254") (address 0xffffffffa056356d) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_get_inode@fs/ext2/inode.c") (address 0xffffffffa056356d) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_iget@fs/ext2/inode.c:1320") (address 0xffffffffa0563b14) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_iget@fs/ext2/inode.c:1338") (address 0xffffffffa0563bb7) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_iget@fs/ext2/inode.c:1392") (address 0xffffffffa0563d39) registration error (rc -84)
WARNING: probe module("ext2").statement("__ext2_write_inode@fs/ext2/inode.c:1469") (address 0xffffffffa0563835) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_setattr@fs/ext2/inode.c:1540") (address 0xffffffffa0563ea0) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_setattr@fs/ext2/inode.c:1543") (address 0xffffffffa0563ea8) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_ioctl@fs/ext2/ioctl.c:30") (address 0xffffffffa056403d) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_ioctl@fs/ext2/ioctl.c:86") (address 0xffffffffa05641a1) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_ioctl@fs/ext2/ioctl.c:87") (address 0xffffffffa05641ab) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_quota_read@fs/ext2/super.c:1391") (address 0xffffffffa05653c2) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_quota_read@fs/ext2/super.c:1400") (address 0xffffffffa05653d3) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_quota_read@fs/ext2/super.c:1402") (address 0xffffffffa05653dc) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_quota_read@fs/ext2/super.c:1403") (address 0xffffffffa05653e0) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_quota_read@fs/ext2/super.c:1404") (address 0xffffffffa05653f9) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_quota_read@fs/ext2/super.c:1405") (address 0xffffffffa05653fc) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_quota_read@fs/ext2/super.c:1406") (address 0xffffffffa056544f) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_quota_read@fs/ext2/super.c:1407") (address 0xffffffffa0565401) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_quota_read@fs/ext2/super.c:1409") (address 0xffffffffa0565418) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_quota_read@fs/ext2/super.c:1410") (address 0xffffffffa0565423) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_quota_read@fs/ext2/super.c:1411") (address 0xffffffffa0565405) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_quota_read@fs/ext2/super.c:1412") (address 0xffffffffa0565433) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_quota_read@fs/ext2/super.c:1413") (address 0xffffffffa056543e) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_quota_read@fs/ext2/super.c:1414") (address 0xffffffffa056545c) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_quota_read@fs/ext2/super.c:1415") (address 0xffffffffa0565460) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_quota_read@fs/ext2/super.c:1418") (address 0xffffffffa056548b) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_quota_read@fs/ext2/super.c:1419") (address 0xffffffffa05654d3) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_quota_read@fs/ext2/super.c:1420") (address 0xffffffffa0565497) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_quota_read@fs/ext2/super.c:1421") (address 0xffffffffa05654aa) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_quota_read@fs/ext2/super.c:1423") (address 0xffffffffa05654c2) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_quota_read@fs/ext2/super.c:1424") (address 0xffffffffa05654b2) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_quota_read@fs/ext2/super.c:1425") (address 0xffffffffa05654b8) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_quota_read@fs/ext2/super.c:1426") (address 0xffffffffa05654b5) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_quota_read@fs/ext2/super.c:1428") (address 0xffffffffa05654ce) registration error (rc -84)
WARNING: probe module("ext2").statement("ext2_quota_read@fs/ext2/super.c:1429") (address 0xffffffffa05654da) registration error (rc -84)
Too many interrupts received, exiting.