tyrann27 Posted July 14, 2007 Share Posted July 14, 2007 Olla les INpactien Après un p'tit reboot, voici ce que je trouve dans une console : tyrann@sebastien:~$ Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] Oops: 0000 [#1] Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] SMP Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] CPU: 0 Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] EIP: 0060:[__block_write_full_page+225/864] Tainted: P VLI Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] EFLAGS: 00010297 (2.6.20-16-generic #2) Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] EIP is at __block_write_full_page+0xe1/0x360 Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] eax: 00000000 ebx: 00000000 ecx: 00000000 edx: 0000000c Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] esi: 0001000e edi: 00000000 ebp: c18d8cf0 esp: c1a4fdec Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] ds: 007b es: 007b ss: 0068 Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] Process pdflush (pid: 143, ti=c1a4e000 task=c1a78a90 task.ti=c1a4e000) Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] Stack: c1959230 00ffffff 0000000e c1927c10 c019c650 c13fbca0 00000000 004e22af Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] 00000000 dfdedc18 00001000 00000004 c18d8cf0 c13fbca0 00000000 c0198ab7 Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] c1a4ff64 00000286 c1a4ff64 c019c650 c13fbca0 c13fbca0 00000009 c1a4ff64 Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] Call Trace: Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] [blkdev_get_block+0/112] blkdev_get_block+0x0/0x70 Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] [block_write_full_page+247/256] block_write_full_page+0xf7/0x100 Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] [blkdev_get_block+0/112] blkdev_get_block+0x0/0x70 Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] [generic_writepages+525/816] generic_writepages+0x20d/0x330 Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] [blkdev_writepage+0/16] blkdev_writepage+0x0/0x10 Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] [do_writepages+43/80] do_writepages+0x2b/0x50 Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] [__writeback_single_inode+147/960] __writeback_single_inode+0x93/0x3c0 Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] [<f885afdd>] dm_table_any_congested+0xd/0x50 [dm_mod] Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] [<f8850ef8>] raid1_congested+0x38/0x90 [raid1] Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] [sync_sb_inodes+382/576] sync_sb_inodes+0x17e/0x240 Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] [writeback_inodes+153/208] writeback_inodes+0x99/0xd0 Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] [pdflush+0/512] pdflush+0x0/0x200 Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] [wb_kupdate+133/240] wb_kupdate+0x85/0xf0 Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] [pdflush+294/512] pdflush+0x126/0x200 Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] [wb_kupdate+0/240] wb_kupdate+0x0/0xf0 Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] [kthread+186/240] kthread+0xba/0xf0 Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] [kthread+0/240] kthread+0x0/0xf0 Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] [kernel_thread_helper+7/16] kernel_thread_helper+0x7/0x10 Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] ======================= Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] Code: 24 24 eb 21 77 06 3b 74 24 1c 76 1f 90 0f ba 33 01 90 0f ba 2b 00 8b 5b 04 39 5c 24 24 74 68 83 c6 01 83 d7 00 3b 7c 24 20 73 d9 <8b> 03 a8 20 75 e5 8b 03 a8 02 74 df 8b 54 24 28 3b 53 14 0f 85 Message from syslogd@localhost at Sat Jul 14 11:15:23 2007 ... localhost kernel: [ 90.128000] EIP: [__block_write_full_page+225/864] __block_write_full_page+0xe1/0x360 SS:ESP 0068:c1a4fdec Est-ce normal? La réponse est surement non Mais qu'est-ce que ça veut dire? Link to comment Share on other sites More sharing options...
tuXXX Posted July 14, 2007 Share Posted July 14, 2007 Je dirais que c'est un Oops noyau dans la gestion du disque dur. (sachant que un Oops c'est un peu comme un Kernel Panic mais en un poil moins grave (ie. tu peux peut-être encore utiliser la machine un minimum). Souvent ce sont des problèmes matériels ou des problèmes de drivers. Ça pourrait être la version du noyau, ça vaudrait le coup d'en essayer une autre à mon avis. Link to comment Share on other sites More sharing options...
tyrann27 Posted July 15, 2007 Author Share Posted July 15, 2007 utiliser la machine au minimum? Mais elle a pas été éteinte depuis hier et fonctionne à merveille! Si j'en crois ce qui est écrit, c'est un problème sur le raid... Faudrait p'tet que je check mes arrays et mes partoches ext3 aussi... En gros, y a t'il un grand pourcentage de chance qu'un de mes disques soit mort? Link to comment Share on other sites More sharing options...
tuXXX Posted July 15, 2007 Share Posted July 15, 2007 utiliser la machine au minimum? Ça peut varier entre "tout est planté y'a plus rien qui marche" à "aucun problème ça marche toujours aussi bien". Link to comment Share on other sites More sharing options...
tyrann27 Posted July 15, 2007 Author Share Posted July 15, 2007 Je crois que l'option 2 est au rdv... Merci tuXXX Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.