R. J.
Ok that took care of the Kernel Panic, Now I'm seeing messages like
below :
psr : 00001010095a6010 ifs : 800000000000058e ip : [<a000000208f86850>]
Tainted: G D NX (3.0.13-0.27.1.2.LEI-default)
ip is at aufs_fsync_nondir+0x630/0x740 [aufs]
unat: 0000000000000000 pfs : 000000000000058e rsc : 0000000000000003
rnat: 0000000000000001 bsps: e0000000011c1390 pr : 5595565a695a6999
ldrs: 0000000000000000 ccv : 0000000000000001 fpsr: 0009804c0270033f
csd : 0000000000000000 ssd : 0000000000000000
b0 : a000000208f86850 b6 : a00000010050e960 b7 : a00000010065c020
f6 : 1003e00000018eb874e90 f7 : 1003e000000000000031e
f8 : 1003e00000018eb874b72 f9 : 1003e0000000000000001
f10 : 000000000000000000000 f11 : 000000000000000000000
r1 : a000000101700190 r2 : 000000000000ef4c r3 : 000000000000fffe
r8 : 000000000000004f r9 : 0000000000000000 r10 : 0000000000ffffff
r11 : 0000000000000000 r12 : e00000141686fe00 r13 : e000001416860000
r14 : 000000000000ef4c r15 : a0000001014bed88 r16 : fffffffffffc1390
r17 : a0000001014bed80 r18 : a000000101500c70 r19 : 0000000000000000
r20 : a000000101522720 r21 : a000000101513858 r22 : e00000141225fe18
r23 : 0000000000000001 r24 : e0000000011c1390 r25 : e000000001200000
r26 : fffffffffffc0400 r27 : a0000001014e78f0 r28 : a00000010065a600
r29 : 0000000000000100 r30 : a000000101cd5020 r31 : a000000100c164e8
Call Trace:
[<a000000100016720>] show_stack+0x80/0xa0
sp=e00000141686f9c0 bsp=e0000014168612b0
[<a000000100016d80>] show_regs+0x640/0x920
sp=e00000141686fb90 bsp=e000001416861258
[<a000000100027f10>] die+0x190/0x2e0
sp=e00000141686fba0 bsp=e000001416861218
[<a0000001000280b0>] die_if_kernel+0x50/0x80
sp=e00000141686fba0 bsp=e0000014168611e0
[<a000000100970cd0>] ia64_bad_break+0x470/0x760
sp=e00000141686fba0 bsp=e0000014168611b8
[<a00000010000bf40>] ia64_native_leave_kernel+0x0/0x270
sp=e00000141686fc30 bsp=e0000014168611b8
[<a000000208f86850>] aufs_fsync_nondir+0x630/0x740 [aufs]
sp=e00000141686fe00 bsp=e000001416861148
[<a0000001002b75d0>] vfs_fsync_range+0xb0/0xe0
sp=e00000141686fe30 bsp=e000001416861110
[<a0000001002b7640>] vfs_fsync+0x40/0x60
sp=e00000141686fe30 bsp=e0000014168610e8
[<a0000001002b7b50>] do_fsync+0x50/0x80
sp=e00000141686fe30 bsp=e0000014168610c0
[<a0000001002b7c10>] sys_fsync+0x30/0x60
sp=e00000141686fe30 bsp=e000001416861068
[<a00000010000bdc0>] ia64_ret_from_syscall+0x0/0x20
sp=e00000141686fe30 bsp=e000001416861068
[<a000000000040720>] __kernel_syscall_via_break+0x0/0x20
sp=e000001416870000 bsp=e000001416861068
Thanks
JJ
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Friday, March 15, 2013 1:45 PM
To: Jemiolo, John
Cc: [email protected]
Subject: Re: Kernel panic with aufs3.0 on ia64
"Jemiolo, John":
> The source appears to be available from:
> http://gitorious.org/opensuse/ker=
> nel/commits/SLE11-SP2
I see four methods are added in struct address_space_operations.
Didn't you see the error message at the top of the crash msg?
For your modified kernel, you need to add these lines in your
fs/aufs/dynop.c:dy_aop(). You will easily decide the place where in the
function.
DySetAop(swap_activate);
DySetAop(swap_deactivate);
DySetAop(swap_writepage);
DySetAop(swap_readpage);
J. R. Okajima
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
