* 2.6.11: kernel BUG at fs/jbd/checkpoint.c:247!
@ 2005-06-03 21:13 Frank Elsner
2005-06-03 23:33 ` Andrew Morton
2005-06-08 15:36 ` Jan Kara
0 siblings, 2 replies; 6+ messages in thread
From: Frank Elsner @ 2005-06-03 21:13 UTC (permalink / raw)
To: linux-kernel
I'm not a kernel hacker. Maybe some of you knows what happened :-)
Jun 3 04:04:54 seymour kernel: kernel BUG at fs/jbd/checkpoint.c:247!
Jun 3 04:04:54 seymour kernel: invalid operand: 0000 [#1]
Jun 3 04:04:54 seymour kernel: PREEMPT SMP
Jun 3 04:04:54 seymour kernel: Modules linked in: radeon nfsd exportfs lockd pa
rport_pc lp parport tun autofs4 sunrpc ipt_REJECT ipt_LOG ipt_state iptable_filt
er iptable_nat ip_conntrack ip_tables vfat fat video button battery ac uhci_hcd
ehci_hcd snd_emu10k1 snd_rawmidi snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pc
m snd_timer snd_page_alloc snd_util_mem snd_hwdep snd soundcore natsemi sym53c8x
x scsi_transport_spi
Jun 3 04:04:54 seymour kernel: CPU: 1
Jun 3 04:04:54 seymour kernel: EIP: 0060:[<c019c730>] Not tainted VLI
Jun 3 04:04:54 seymour kernel: EFLAGS: 00010296 (2.6.11)
Jun 3 04:04:54 seymour kernel: EIP is at __flush_buffer+0xfa/0x157
Jun 3 04:04:54 seymour kernel: eax: 0000005a ebx: d0d968cc ecx: c0331714
edx: 00000206
Jun 3 04:04:54 seymour kernel: esi: e8fbdd30 edi: 00000000 ebp: e8fbdd34
esp: e8fbdcd8
Jun 3 04:04:54 seymour kernel: ds: 007b es: 007b ss: 0068
Jun 3 04:04:54 seymour kernel: Process updatedb (pid: 18466, threadinfo=e8fbc00
0 task=f7496550)
Jun 3 04:04:54 seymour kernel: Stack: c02f6ad4 c02e16a3 c02f56ce 000000f7 c02f5
6e2 f7cdc000 ed7876ec d0d968cc
Jun 3 04:04:54 seymour kernel: ed78771c f7cdc000 c019c832 e8fbdd2c e8fbd
d30 c1808060 c011a74b c1808060
Jun 3 04:04:54 seymour kernel: f7cdc0e4 e8fbc000 0006c901 f0a4de9c f6d9d
b80 0000003c 00000001 d0d968cc
Jun 3 04:04:54 seymour kernel: Call Trace:
Jun 3 04:04:54 seymour kernel: [<c019c832>] log_do_checkpoint+0xa5/0x1be
Jun 3 04:04:54 seymour kernel: [<c011a74b>] finish_task_switch+0x30/0x6d
Jun 3 04:04:54 seymour kernel: [<c019c334>] __log_wait_for_space+0x90/0xaa
Jun 3 04:04:54 seymour kernel: [<c0197c44>] start_this_handle+0xec/0x371
Jun 3 04:04:54 seymour kernel: [<c01b8284>] copy_to_user+0x2b/0x3d
Jun 3 04:04:54 seymour kernel: [<c018a9c2>] call_filldir+0x6c/0xaf
Jun 3 04:04:54 seymour kernel: [<c016893e>] filldir64+0x0/0xd0
Jun 3 04:04:54 seymour kernel: [<c018ab0e>] ext3_dx_readdir+0x109/0x1b5
Jun 3 04:04:54 seymour kernel: [<c016893e>] filldir64+0x0/0xd0
Jun 3 04:04:54 seymour kernel: [<c0197f8b>] journal_start+0x8f/0xb1
Jun 3 04:04:54 seymour kernel: [<c0160893>] cp_new_stat64+0xf0/0x102
Jun 3 04:04:54 seymour kernel: [<c018f572>] ext3_dirty_inode+0x27/0x82
Jun 3 04:04:54 seymour kernel: [<c01765cf>] __mark_inode_dirty+0xaf/0x1c3
Jun 3 04:04:54 seymour kernel: [<c0124086>] current_fs_time+0x50/0x5a
Jun 3 04:04:54 seymour kernel: [<c016f666>] update_atime+0x57/0x97
Jun 3 04:04:54 seymour kernel: [<c016870e>] vfs_readdir+0x66/0x68
Jun 3 04:04:54 seymour kernel: [<c0168a7a>] sys_getdents64+0x6c/0xbe
Jun 3 04:04:54 seymour kernel: [<c0103dc5>] sysenter_past_esp+0x52/0x75
Jun 3 04:04:54 seymour kernel: Code: 44 24 10 e2 56 2f c0 c7 44 24 0c f7 00 00
00 c7 44 24 08 ce 56 2f c0 c7 44 24 04 a3 16 2e c0 c7 04 24 d4 6a 2f c0 e8 d7 35
f8 ff <0f> 0b f7 00 ce 56 2f c0 e9 3b ff ff ff c7 44 24 10 4c 8f 2f c0
Jun 3 04:04:54 seymour kernel: <6>note: updatedb[18466] exited with preempt_co
unt 2
Regards _____________________________________________________________
Frank Elsner / |
_____________/ Snail Mail: Moltkestr. 28 A |
| D-12203 Berlin(-Lichterfelde) |
| Phone: +49 30 834 66 30 Germany |
| eMail: Frank@moltke28.B.Shuttle.DE |
| http://www.B.Shuttle.DE/moltke28 ______________________________|
|______________________________________________| Anders wär' nämlich schlecht
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.6.11: kernel BUG at fs/jbd/checkpoint.c:247!
2005-06-03 21:13 2.6.11: kernel BUG at fs/jbd/checkpoint.c:247! Frank Elsner
@ 2005-06-03 23:33 ` Andrew Morton
2005-06-04 9:15 ` Frank Elsner
2005-06-08 15:36 ` Jan Kara
1 sibling, 1 reply; 6+ messages in thread
From: Andrew Morton @ 2005-06-03 23:33 UTC (permalink / raw)
To: Frank Elsner; +Cc: linux-kernel
Frank Elsner <frank@moltke28.B.Shuttle.DE> wrote:
>
> Jun 3 04:04:54 seymour kernel: kernel BUG at fs/jbd/checkpoint.c:247!
We're hoping that this is fixed now. How repeatable is it for you?
Please test
ftp://ftp.kernel.org/pub/linux/kernel/v2.6/testing/linux-2.6.12-rc5.tar.bz2
plus
ftp://ftp.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.12-rc5-git8.bz2
Thanks.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.6.11: kernel BUG at fs/jbd/checkpoint.c:247!
2005-06-03 23:33 ` Andrew Morton
@ 2005-06-04 9:15 ` Frank Elsner
2005-06-04 10:07 ` Andrew Morton
0 siblings, 1 reply; 6+ messages in thread
From: Frank Elsner @ 2005-06-04 9:15 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
On Fri, 3 Jun 2005 16:33:56 -0700 Andrew Morton <akpm@osdl.org> wrote:
> Frank Elsner <frank@moltke28.B.Shuttle.DE> wrote:
> >
> > Jun 3 04:04:54 seymour kernel: kernel BUG at fs/jbd/checkpoint.c:247!
>
> We're hoping that this is fixed now. How repeatable is it for you?
I fear I can't reproduce it.
It occured for the first time since I'm runnning linux-2.6.11.
I'm now using linux-2.6.11.11.
> Please test
>
> ftp://ftp.kernel.org/pub/linux/kernel/v2.6/testing/linux-2.6.12-rc5.tar.bz2
> plus
> ftp://ftp.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.12-rc5-git8.bz2
Thanks for dealing with the problem and the hint(s).
I don't understand the current numbering scheme.
Is linux-2.6.12-rcX better than linux-2.6.11.xx?
Linux-2.6.12-rcX is 3 days older than linux-2.6.11.11!
Shall I go to linux-2.6.12-rcX or stay with linux-2.6.11.11?
--Frank
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.6.11: kernel BUG at fs/jbd/checkpoint.c:247!
2005-06-04 9:15 ` Frank Elsner
@ 2005-06-04 10:07 ` Andrew Morton
0 siblings, 0 replies; 6+ messages in thread
From: Andrew Morton @ 2005-06-04 10:07 UTC (permalink / raw)
To: Frank Elsner; +Cc: linux-kernel
Frank Elsner <frank@moltke28.B.Shuttle.DE> wrote:
>
> Shall I go to linux-2.6.12-rcX or stay with linux-2.6.11.11?
2.6.12-rcx, please. The 2.6.11 stream is a maintenance branch based upon
the now-very-old 2.6.11. There has been no attempt (yet) to fix this bug
in the 2.6.11 stream.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.6.11: kernel BUG at fs/jbd/checkpoint.c:247!
2005-06-03 21:13 2.6.11: kernel BUG at fs/jbd/checkpoint.c:247! Frank Elsner
2005-06-03 23:33 ` Andrew Morton
@ 2005-06-08 15:36 ` Jan Kara
2005-06-08 16:02 ` Frank Elsner
1 sibling, 1 reply; 6+ messages in thread
From: Jan Kara @ 2005-06-08 15:36 UTC (permalink / raw)
To: Frank Elsner; +Cc: linux-kernel
> I'm not a kernel hacker. Maybe some of you knows what happened :-)
Looks like a bug in the kernel :). Can you please try 2.6.12-rc5 or
newer? It should contain several fixes in this area.
Thanks for report
Honza
> Jun 3 04:04:54 seymour kernel: kernel BUG at fs/jbd/checkpoint.c:247!
> Jun 3 04:04:54 seymour kernel: invalid operand: 0000 [#1]
> Jun 3 04:04:54 seymour kernel: PREEMPT SMP
> Jun 3 04:04:54 seymour kernel: Modules linked in: radeon nfsd exportfs lockd pa
> rport_pc lp parport tun autofs4 sunrpc ipt_REJECT ipt_LOG ipt_state iptable_filt
> er iptable_nat ip_conntrack ip_tables vfat fat video button battery ac uhci_hcd
> ehci_hcd snd_emu10k1 snd_rawmidi snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pc
> m snd_timer snd_page_alloc snd_util_mem snd_hwdep snd soundcore natsemi sym53c8x
> x scsi_transport_spi
> Jun 3 04:04:54 seymour kernel: CPU: 1
> Jun 3 04:04:54 seymour kernel: EIP: 0060:[<c019c730>] Not tainted VLI
> Jun 3 04:04:54 seymour kernel: EFLAGS: 00010296 (2.6.11)
> Jun 3 04:04:54 seymour kernel: EIP is at __flush_buffer+0xfa/0x157
> Jun 3 04:04:54 seymour kernel: eax: 0000005a ebx: d0d968cc ecx: c0331714
> edx: 00000206
> Jun 3 04:04:54 seymour kernel: esi: e8fbdd30 edi: 00000000 ebp: e8fbdd34
> esp: e8fbdcd8
> Jun 3 04:04:54 seymour kernel: ds: 007b es: 007b ss: 0068
> Jun 3 04:04:54 seymour kernel: Process updatedb (pid: 18466, threadinfo=e8fbc00
> 0 task=f7496550)
> Jun 3 04:04:54 seymour kernel: Stack: c02f6ad4 c02e16a3 c02f56ce 000000f7 c02f5
> 6e2 f7cdc000 ed7876ec d0d968cc
> Jun 3 04:04:54 seymour kernel: ed78771c f7cdc000 c019c832 e8fbdd2c e8fbd
> d30 c1808060 c011a74b c1808060
> Jun 3 04:04:54 seymour kernel: f7cdc0e4 e8fbc000 0006c901 f0a4de9c f6d9d
> b80 0000003c 00000001 d0d968cc
> Jun 3 04:04:54 seymour kernel: Call Trace:
> Jun 3 04:04:54 seymour kernel: [<c019c832>] log_do_checkpoint+0xa5/0x1be
> Jun 3 04:04:54 seymour kernel: [<c011a74b>] finish_task_switch+0x30/0x6d
> Jun 3 04:04:54 seymour kernel: [<c019c334>] __log_wait_for_space+0x90/0xaa
> Jun 3 04:04:54 seymour kernel: [<c0197c44>] start_this_handle+0xec/0x371
> Jun 3 04:04:54 seymour kernel: [<c01b8284>] copy_to_user+0x2b/0x3d
> Jun 3 04:04:54 seymour kernel: [<c018a9c2>] call_filldir+0x6c/0xaf
> Jun 3 04:04:54 seymour kernel: [<c016893e>] filldir64+0x0/0xd0
> Jun 3 04:04:54 seymour kernel: [<c018ab0e>] ext3_dx_readdir+0x109/0x1b5
> Jun 3 04:04:54 seymour kernel: [<c016893e>] filldir64+0x0/0xd0
> Jun 3 04:04:54 seymour kernel: [<c0197f8b>] journal_start+0x8f/0xb1
> Jun 3 04:04:54 seymour kernel: [<c0160893>] cp_new_stat64+0xf0/0x102
> Jun 3 04:04:54 seymour kernel: [<c018f572>] ext3_dirty_inode+0x27/0x82
> Jun 3 04:04:54 seymour kernel: [<c01765cf>] __mark_inode_dirty+0xaf/0x1c3
> Jun 3 04:04:54 seymour kernel: [<c0124086>] current_fs_time+0x50/0x5a
> Jun 3 04:04:54 seymour kernel: [<c016f666>] update_atime+0x57/0x97
> Jun 3 04:04:54 seymour kernel: [<c016870e>] vfs_readdir+0x66/0x68
> Jun 3 04:04:54 seymour kernel: [<c0168a7a>] sys_getdents64+0x6c/0xbe
> Jun 3 04:04:54 seymour kernel: [<c0103dc5>] sysenter_past_esp+0x52/0x75
> Jun 3 04:04:54 seymour kernel: Code: 44 24 10 e2 56 2f c0 c7 44 24 0c f7 00 00
> 00 c7 44 24 08 ce 56 2f c0 c7 44 24 04 a3 16 2e c0 c7 04 24 d4 6a 2f c0 e8 d7 35
> f8 ff <0f> 0b f7 00 ce 56 2f c0 e9 3b ff ff ff c7 44 24 10 4c 8f 2f c0
> Jun 3 04:04:54 seymour kernel: <6>note: updatedb[18466] exited with preempt_co
> unt 2
>
--
Jan Kara <jack@suse.cz>
SuSE CR Labs
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.6.11: kernel BUG at fs/jbd/checkpoint.c:247!
2005-06-08 15:36 ` Jan Kara
@ 2005-06-08 16:02 ` Frank Elsner
0 siblings, 0 replies; 6+ messages in thread
From: Frank Elsner @ 2005-06-08 16:02 UTC (permalink / raw)
To: Jan Kara; +Cc: linux-kernel
On Wed, 8 Jun 2005 17:36:15 +0200 Jan Kara <jack@suse.cz> wrote:
> > I'm not a kernel hacker. Maybe some of you knows what happened :-)
> Looks like a bug in the kernel :). Can you please try 2.6.12-rc5 or
> newer? It should contain several fixes in this area.
I'm currently running 2.6.12-rc5 as suggested by Andrew Morton
on Sat, 4 Jun 2005 03:07:40 -0700.
Thanks for dealing with the problem.
--Frank Elsner
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2005-06-08 16:10 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-06-03 21:13 2.6.11: kernel BUG at fs/jbd/checkpoint.c:247! Frank Elsner
2005-06-03 23:33 ` Andrew Morton
2005-06-04 9:15 ` Frank Elsner
2005-06-04 10:07 ` Andrew Morton
2005-06-08 15:36 ` Jan Kara
2005-06-08 16:02 ` Frank Elsner
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®