Newsgroup: it.comp.os.linux.sys
Titolo: Bug del Kernel o Fs danneggiato?

Ciao, mi dareste un parere su questi log del kernel,
Io penso sia colpa degli HD ma non ne sono certo
poichè il kernel mi da un avviso di bug:
Apr 12 08:12:24 mmsc4 kernel: ------------[ cut here ]------------
Apr 12 08:12:24 mmsc4 kernel: kernel BUG at fs/jbd/journal.c:1763!
Log Completi del crash:
Apr 12 04:03:27 mmsc4 kernel: Unable to handle kernel paging request at
virtual address 8999af50
Apr 12 04:03:27 mmsc4 kernel:  printing eip:
Apr 12 04:03:27 mmsc4 kernel: c01651ca
Apr 12 04:03:27 mmsc4 kernel: *pde = 00000000
Apr 12 04:03:27 mmsc4 kernel: Oops: 0000 [#1]
Apr 12 04:03:27 mmsc4 kernel: Modules linked in: md5 ipv6 autofs4 sunrpc
iptable_filter ip_tables e100 mii floppy sg microcode dm_mod video button
battery ac ext3 jbd sym53c8xx scsi_transport_spi sd_mod scsi_mod
Apr 12 04:03:27 mmsc4 kernel: CPU:    0
Apr 12 04:03:27 mmsc4 kernel: EIP:    0060:[<c01651ca>]    Not tainted VLI
Apr 12 04:03:27 mmsc4 kernel: EFLAGS: 00010293   (2.6.10-1.771_FC2)
Apr 12 04:03:27 mmsc4 kernel: EIP is at __block_write_full_page+0xb5/0x2aa
Apr 12 04:03:27 mmsc4 kernel: eax: 0002201b   ebx: 8999af50   ecx: 00000000
edx: c999af50
Apr 12 04:03:27 mmsc4 kernel: esi: 00300005   edi: 00000000   ebp: c1133f60
esp: c1931dcc
Apr 12 04:03:27 mmsc4 kernel: ds: 007b   es: 007b   ss: 0068
Apr 12 04:03:27 mmsc4 kernel: Process pdflush (pid: 146, threadinfo=c1931000
task=c191c620)
Apr 12 04:03:27 mmsc4 kernel: Stack: 00000000 c999af50 00d3269d 00000000
00000000 c0169f77 f47cad94 0000000d
Apr 12 04:03:27 mmsc4 kernel:        c1133f60 f47cae74 f47cad94 c0166578
c1931f5c c014a45e c1931f5c c0169f77
Apr 12 04:03:27 mmsc4 kernel:        c1133f60 c1931f5c f47cae74 c19d1a8c
c018aebe 00000003 00000000 00000001
Apr 12 04:03:27 mmsc4 kernel: Call Trace:
Apr 12 04:03:27 mmsc4 kernel:  [<c0169f77>] blkdev_get_block+0x0/0x4d
Apr 12 04:03:27 mmsc4 kernel:  [<c0166578>] block_write_full_page+0x9c/0xa5
Apr 12 04:03:27 mmsc4 kernel:  [<c014a45e>] pagevec_lookup_tag+0x1b/0x25
Apr 12 04:03:27 mmsc4 kernel:  [<c0169f77>] blkdev_get_block+0x0/0x4d
Apr 12 04:03:27 mmsc4 kernel:  [<c018aebe>] mpage_writepages+0x1b3/0x301
Apr 12 04:03:27 mmsc4 kernel:  [<c016a077>] blkdev_writepage+0x0/0xc
Apr 12 04:03:27 mmsc4 kernel:  [<c01450ad>] do_writepages+0x1b/0x29
Apr 12 04:03:27 mmsc4 kernel:  [<c0188d12>] __sync_single_inode+0xc4/0x2a7
Apr 12 04:03:27 mmsc4 kernel:  [<c01890ec>]
__writeback_single_inode+0x1f7/0x1ff
Apr 12 04:03:27 mmsc4 kernel:  [<c0124bf1>] process_timeout+0x0/0x5
Apr 12 04:03:27 mmsc4 kernel:  [<c0248d90>] blk_congestion_wait+0x72/0x7c
Apr 12 04:03:27 mmsc4 kernel:  [<c013376c>]
autoremove_wake_function+0x0/0x2d
Apr 12 04:03:27 mmsc4 kernel:  [<c018929e>] sync_sb_inodes+0x1aa/0x358
Apr 12 04:03:27 mmsc4 kernel:  [<c0145eee>] pdflush+0x0/0x1e
Apr 12 04:03:27 mmsc4 kernel:  [<c0189625>] writeback_inodes+0x1d9/0x370
Apr 12 04:03:27 mmsc4 kernel:  [<c0144f4f>] wb_kupdate+0x7b/0xe0
Apr 12 04:03:27 mmsc4 kernel:  [<c0145d6e>] __pdflush+0x2f2/0x472
Apr 12 04:03:27 mmsc4 kernel:  [<c0145f08>] pdflush+0x1a/0x1e
Apr 12 04:03:27 mmsc4 kernel:  [<c0144ed4>] wb_kupdate+0x0/0xe0
Apr 12 04:03:27 mmsc4 kernel:  [<c0145eee>] pdflush+0x0/0x1e
Apr 12 04:03:27 mmsc4 kernel:  [<c0132f61>] kthread+0x69/0x91
Apr 12 04:03:27 mmsc4 kernel:  [<c0132ef8>] kthread+0x0/0x91
Apr 12 04:03:27 mmsc4 kernel:  [<c01011dd>] kernel_thread_helper+0x5/0xb
Apr 12 04:03:27 mmsc4 kernel: Code: 75 08 0f 0b e8 06 43 d2 31 c0 8b 55 0c
89 d3 89 54 24 04 3b 7c 24 0c 72 12 77 06 3b 74 24 08 76 0a 0f ba 33 01 0f
ba 2b 00 eb 44 <8b> 03 a8 10 75 3e 8b 03 a8 02 74 38 6a 01 89 f9 89 f2 53 8b
44
Apr 12 08:12:24 mmsc4 kernel:  <0>Assertion failure in
__journal_remove_journal_head() at fs/jbd/journal.c:1763: "jh->b_jcount >=
0"
Apr 12 08:12:24 mmsc4 kernel: ------------[ cut here ]------------
Apr 12 08:12:24 mmsc4 kernel: kernel BUG at fs/jbd/journal.c:1763!
Apr 12 08:12:24 mmsc4 kernel: invalid operand: 0000 [#2]
Apr 12 08:12:24 mmsc4 kernel: Modules linked in: md5 ipv6 autofs4 sunrpc
iptable_filter ip_tables e100 mii floppy sg microcode dm_mod video button
battery ac ext3 jbd sym53c8xx scsi_transport_spi sd_mod scsi_mod
Apr 12 08:12:24 mmsc4 kernel: CPU:    0
Apr 12 08:12:24 mmsc4 kernel: EIP:    0060:[<f889666e>]    Not tainted VLI
Apr 12 08:12:24 mmsc4 kernel: EFLAGS: 00010216   (2.6.10-1.771_FC2)
Apr 12 08:12:24 mmsc4 kernel: EIP is at
__journal_remove_journal_head+0x2b/0x120 [jbd]
Apr 12 08:12:24 mmsc4 kernel: eax: 00000066   ebx: dca4aa1c   ecx: d1d39d1c
edx: f8898048
Apr 12 08:12:24 mmsc4 kernel: esi: c999ae4c   edi: d1d39d7c   ebp: d1d39d80
esp: d1d39d18
Apr 12 08:12:24 mmsc4 kernel: ds: 007b   es: 007b   ss: 0068
Apr 12 08:12:24 mmsc4 kernel: Process java (pid: 3343, threadinfo=d1d39000
task=eec921b0)
Apr 12 08:12:24 mmsc4 kernel: Stack: f8898048 f8896cf7 f8897f94 000006e3
f889855e c999ae4c d1d39d78 f889678f
Apr 12 08:12:24 mmsc4 kernel:        c999ae4c f8891b98 00000000 f8892327
00000000 f6641000 f6641000 dea4aa1c
Apr 12 08:12:24 mmsc4 kernel:        00000000 ee78f300 f88924e2 d1d39d78
d1d39d7c 000d407c dea4aa7c dea4ab6c
Apr 12 08:12:24 mmsc4 kernel: Call Trace:
Apr 12 08:12:24 mmsc4 kernel:  [<f889678f>]
journal_remove_journal_head+0x2c/0x43 [jbd]
Apr 12 08:12:24 mmsc4 kernel:  [<f8891b98>] __try_to_free_cp_buf+0x3c/0x63
[jbd]
Apr 12 08:12:24 mmsc4 kernel:  [<f8892327>] __flush_buffer+0xf0/0x103 [jbd]
Apr 12 08:12:24 mmsc4 kernel:  [<f88924e2>] log_do_checkpoint+0x1a8/0x2c5
[jbd]
Apr 12 08:12:24 mmsc4 kernel:  [<f8891d19>] __log_wait_for_space+0x15a/0x1e8
[jbd]
Apr 12 08:12:24 mmsc4 kernel:  [<f888c5ec>] start_this_handle+0x547/0x624
[jbd]
Apr 12 08:12:24 mmsc4 kernel:  [<c01754de>] filldir64+0x0/0xd9
Apr 12 08:12:24 mmsc4 kernel:  [<f88c6081>] ext3_dx_readdir+0x13f/0x18a
[ext3]
Apr 12 08:12:24 mmsc4 kernel:  [<f88c608e>] ext3_dx_readdir+0x14c/0x18a
[ext3]
Apr 12 08:12:24 mmsc4 kernel:  [<c01754de>] filldir64+0x0/0xd9
Apr 12 08:12:24 mmsc4 kernel:  [<f888c778>] journal_start+0x78/0x9e [jbd]
Apr 12 08:12:24 mmsc4 kernel:  [<f88ca5f2>] ext3_dirty_inode+0x24/0x63
[ext3]
Apr 12 08:12:24 mmsc4 kernel:  [<c01889f0>] __mark_inode_dirty+0x28/0x24f
Apr 12 08:12:24 mmsc4 kernel:  [<c017f239>] update_atime+0x76/0x9e
Apr 12 08:12:24 mmsc4 kernel:  [<c01754de>] filldir64+0x0/0xd9
Apr 12 08:12:24 mmsc4 kernel:  [<c017526e>] vfs_readdir+0x86/0x9a
Apr 12 08:12:24 mmsc4 kernel:  [<c017561d>] sys_getdents64+0x66/0xa0
Apr 12 08:12:24 mmsc4 kernel:  [<c0103473>] syscall_call+0x7/0xb
Apr 12 08:12:24 mmsc4 kernel: Code: 56 89 c6 53 8b 58 28 83 7b 04 00 79 29
68 5e 85 89 f8 68 e3 06 00 00 68 94 7f 89 f8 68 f7 6c 89 f8 68 48 80 89 f8
e8 70 55 88 c7 <0f> 0b e3 06 94 7f 89 f8 83 c4 14 ff 46 0c 83 7b 04 00 0f 85
da
Apr 12 09:20:35 mmsc4 kernel: klogd 1.4.1, log source = /proc/kmsg started.
Apr 12 09:20:35 mmsc4 kernel: Linux version 2.6.10-1.771_FC2
(
bhco...@porky.build.redhat.com
) (gcc version 3.3.3 20040412 (Red Hat
Linux 3.3.3-7)) #1 Mon Mar 28 00:50:14 EST 2005
------------------------ FINE LOG ---------------------------------------
Caratteristiche del server:
------------------------------------------------
cat cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 15
model           : 2
model name      : Intel(R) Pentium(R) 4 CPU 2.40GHz
stepping        : 7
cpu MHz         : 2396.567
cache size      : 512 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 mtrr pge mca cmov pat
pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
bogomips        : 4734.97
------------------------------------------------
cat meminfo
MemTotal:      1027700 kB
MemFree:        537048 kB
Buffers:         71164 kB
Cached:         164892 kB
SwapCached:          0 kB
Active:         290348 kB
Inactive:       144548 kB
HighTotal:      122816 kB
HighFree:          140 kB
LowTotal:       904884 kB
LowFree:        536908 kB
SwapTotal:     2048276 kB
SwapFree:      2048276 kB
Dirty:             116 kB
Writeback:           0 kB
Mapped:         258236 kB
Slab:            46868 kB
CommitLimit:   2562124 kB
Committed_AS:   412460 kB
PageTables:       2132 kB
VmallocTotal:   114680 kB
VmallocUsed:      2428 kB
VmallocChunk:   111736 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     4096 kB
------------------------------------------------
uname -a
Linux mmsc4 2.6.10-1.771_FC2 #1 Mon Mar 28 00:50:14 EST 2005 i686 i686 i386
GNU/Linux
Fedora Core2
------------------------------------------------
 cat /etc/fstab
LABEL=/                 /                       ext3    defaults        1 1
LABEL=/boot             /boot                   ext3    defaults        1 2
none                    /dev/pts                devpts  gid=5,mode=620  0 0
none                    /dev/shm                tmpfs   defaults        0 0
LABEL=/home             /home                   ext3    defaults        1 2
none                    /proc                   proc    defaults        0 0
none                    /sys                    sysfs   defaults        0 0
LABEL=/tmp              /tmp                    ext3    defaults        1 2
LABEL=/var              /var                    ext3    defaults        1 2
/dev/sda3               swap                    swap    defaults        0 0
/dev/cdrom              /mnt/cdrom              udf,iso9660
noauto,owner,kudzu,ro 0 0
------------------------------------------------
df
Filesystem        blocchi di   1K   Usati Disponib. Uso% Montato su
/dev/sda2             10080520   4640788   4927664  49% /
/dev/sda1               101086     11049     84818  12% /boot
none                    513848         0    513848   0% /dev/shm
/dev/sda7             54481976    972284  50742096   2% /home
/dev/sda6              2016016     32848   1880756   2% /tmp
/dev/sda5             10080488    404576   9163844   5% /var
------------------------------------------------
Ci gira Qmail + Spamassassin + Resin java webserver + Tomcat.
E' il caso di passare al Kernel 2.6.11.7 ?
Grazie per la pazienza :-)
                                            -- Yena --

> Bug del Kernel o Fs danneggiato?
Forse entrambi, visto che un fs inconsistente non deve causare OOPS, di più
non posso dedurre
Ciao,
-- 
Daniele Orlandi

 Ciao,
ciao
-- 
Ranger!
ranger chiocciol@ 
racine.ra.it

 E' il caso di passare al Kernel 2.6.11.7 ?
E' quello che farei al posto tuo.
-- 
Lorenzo

 andasse in panic per un fs corrotto!
Attento, una cosa è un panic a seguito di un errore, magari, sul filesystem
montato come root. Ricordo che, per esempio, ext2/3 prevede come
comportarsi in caso di errore, tra:
                   continue    Continue normal execution.
                   remount-ro  Remount filesystem read-only.
                   panic       Cause a kernel panic.
Una cosa diversa è, invece, generare un OOPS da BUG()
Ciao,
-- 
Daniele Orlandi

 ha scritto nel messaggio
news:aj60j2-...@odyssey.tux.lan...

Ok proviamo col 2.6.11.7 :-)
Grazie a tutti
                                -- Yena --