Hello
I am on Athlon 1Gz, kernel 2.4.8. I was running a perl pgm with a
lot of disk access, deletions and symlinks creations... Maybe It is due
to the kernel version. Could you please inform me if must upgrade to a
more recent kernel ?
Thanks a lot
the kernel logs are :
in errors logs
Oct 18 17:31:16 tadorne kernel: Assertion failure in
journal_revoke_Rb5884a32() at revoke.c:307:
"!(__builtin_constant_p(BH_Revoked) ?
constant_test_bit((BH_Revoked),(&bh->b_state)) :
variable_test_bit((BH_Revoked),(&bh->b_state)))"
Oct 18 17:41:30 tadorne kernel: task `ip' exit_signal 17
in reparent_to_init
in warnings logs
Oct 18 17:31:16 tadorne kernel: kernel BUG at revoke.c:307!
Oct 18 17:31:16 tadorne kernel: invalid operand: 0000
Oct 18 17:31:16 tadorne kernel: CPU: 0
Oct 18 17:31:16 tadorne kernel: EIP:
0010:[af_packet:__insmod_af_packet_O/lib/modules/2.4.8-26mdk/kernel/net/pac+-616196/96]
Oct 18 17:31:16 tadorne kernel: EIP: 0010:[<c90428fc>]
Oct 18 17:31:16 tadorne kernel: EFLAGS: 00210286
Oct 18 17:31:16 tadorne kernel: eax: 0000001c ebx: c46b9b40 ecx:
c025dddc edx: 00002a05
Oct 18 17:31:16 tadorne kernel: esi: c7a32200 edi: 0000000b ebp:
c46b9b40 esp: c46bbd48
Oct 18 17:31:16 tadorne kernel: ds: 0018 es: 0018 ss: 0018
Oct 18 17:31:16 tadorne kernel: Process rm (pid: 20317,
stackpage=c46bb000)
Oct 18 17:31:16 tadorne kernel: Stack: c90465ec 00000133 00000000
c75bf8c0 c7860500 c75bf7a0 c904bffc c7860500
Oct 18 17:31:16 tadorne kernel: 0008850c c46b9b40 00000000
0000050b c3b70e40 c67f2140 c903ee11 c5f3de68
Oct 18 17:31:16 tadorne kernel: 000883ec 00000000 c7a32200
c7860500 c903ee11 c7860500 0008850c c75bf8c0
Oct 18 17:31:16 tadorne kernel: Call Trace:
[af_packet:__insmod_af_packet_O/lib/modules/2.4.8-26mdk/kernel/net/pac+-600596/96]
[af_packet:__insmod_af_packet_O/lib/modules/2.4.8-26mdk/kernel/net/pac+-577540/96]
[af_packet:__insmod_af_packet_O/lib/modules/2.4.8-26mdk/kernel/net/pac+-631279/96]
[af_packet:__insmod_af_packet_O/lib/modules/2.4.8-26mdk/kernel/net/pac+-631279/96]
[af_packet:__insmod_af_packet_O/lib/modules/2.4.8-26mdk/kernel/net/pac+-568894/96]
Oct 18 17:31:16 tadorne kernel: Call Trace: [<c90465ec>]
[<c904bffc>]
[<c903ee11>] [<c903ee11>] [<c904e1c2>]
Oct 18 17:31:16 tadorne kernel:
[af_packet:__insmod_af_packet_O/lib/modules/2.4.8-26mdk/kernel/net/pac+-573744/96]
[af_packet:__insmod_af_packet_O/lib/modules/2.4.8-26mdk/kernel/net/pac+-631279/96]
[af_packet:__insmod_af_packet_O/lib/modules/2.4.8-26mdk/kernel/net/pac+-568571/96]
[af_packet:__insmod_af_packet_O/lib/modules/2.4.8-26mdk/kernel/net/pac+-567492/96]
[af_packet:__insmod_af_packet_O/lib/modules/2.4.8-26mdk/kernel/net/pac+-634236/96]
[af_packet:__insmod_af_packet_O/lib/modules/2.4.8-26mdk/kernel/net/pac+-633972/96]
Oct 18 17:31:16 tadorne kernel: [<c904ced0>] [<c903ee11>]
[<c904e305>] [<c904e73c>] [<c903e284>] [<c903e38c>]
Oct 18 17:31:16 tadorne kernel:
[af_packet:__insmod_af_packet_O/lib/modules/2.4.8-26mdk/kernel/net/pac+-577337/96]
[af_packet:__insmod_af_packet_O/lib/modules/2.4.8-26mdk/kernel/net/pac+-576968/96]
[af_packet:__insmod_af_packet_O/lib/modules/2.4.8-26mdk/kernel/net/pac+-528032/96]
[af_packet:__insmod_af_packet_O/lib/modules/2.4.8-26mdk/kernel/net/pac+-528032/96]
[iput+232/448] [d_delete+76/112]
Oct 18 17:31:16 tadorne kernel: [<c904c0c7>] [<c904c238>]
[<c9058160>] [<c9058160>] [<c01458a8>] [<c0143d4c>]
Oct 18 17:31:16 tadorne kernel: [vfs_unlink+331/384]
[sys_unlink+153/256] [system_call+51/64]
Oct 18 17:31:16 tadorne kernel: [<c013d41b>] [<c013d4e9>]
[<c0106ec3>]
Oct 18 17:31:16 tadorne kernel:
Oct 18 17:31:16 tadorne kernel: Code: 0f 0b 58 5a 0f ab 7b 18 b8 0c 00
00 00 0f ab 43 18 85 ed 74
Hi, On Thu, Oct 18, 2001 at 05:58:16PM +0200, Marc Tommasi wrote:> I am on Athlon 1Gz, kernel 2.4.8. I was running a perl pgm with a > lot of disk access, deletions and symlinks creations... Maybe It is due > to the kernel version. Could you please inform me if must upgrade to a > more recent kernel ?Yes, indeed. We fixed this, and metadata-rich operations such as large amounts of symlink and directory activity are exactly the sorts of things that would have triggered the bug. Cheers, Stephen
Stephen C. Tweedie:> > Yes, indeed. We fixed this, and metadata-rich operations such as > large amounts of symlink and directory activity are exactly the sorts > of things that would have triggered the bug. >And are recent ac patches enough, or are the ext3-2.4-0.9* patches required as well?
Hi, On Thu, Oct 18, 2001 at 01:29:22PM -0400, John Ruttenberg wrote:> Stephen C. Tweedie: > > > > Yes, indeed. We fixed this, and metadata-rich operations such as > > large amounts of symlink and directory activity are exactly the sorts > > of things that would have triggered the bug. > > > > And are recent ac patches enough, or are the ext3-2.4-0.9* patches required as > well?The current -ac contains ext3-0.9.12, which has the fix. Cheers, Stephen