Chez JL

Joliciel Libre

Accueil > Informatique > GNU/Linux > Debian > Divers problèmes Debian

Divers problèmes Debian

mardi 26 novembre 2013, par JL

 fd0 read error

http://forum.hardware.fr/hfr/OSAlternatifs/Logiciels-2/grub2-read-error-sujet_70884_1.htm

Au démarrage, grub fait le message

fd0 : read error

Puis le démarrage continue correctement.
Pour ne plus avoir le message, et si le lecteur disquette n’est plus utilisé, désacrtiver le lecteur disquette dans le bios.

 task blocked for more than 120 seconds

Message d’erreur dans /var/log/syslog :

INFO: task mandb:7753 blocked for more than 120 seconds.
[383040.964130] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[383040.964163] mandb           D 00015c05     0  7753   7748 0x00000000
[383040.964178]  f4d026e0 00000086 a9a388c6 00015c05 f4412000 00000000 00015c05 c1481ac0
[383040.964196]  f4d02890 c1481ac0 00001c18 00000000 f4c9dee0 f6e7b668 f6dd34b8 00000003
[383040.964212]  f6e7b668 00000003 00e34ed0 f4b1fdcc c1053bc4 00018bd7 f79f0ac0 00000000
[383040.964230] Call Trace:
[383040.964254]  [<c1053bc4>] ? timekeeping_get_ns+0x11/0x55
[383040.964267]  [<c105401f>] ? ktime_get_ts+0x7a/0x82
[383040.964281]  [<c12c2d24>] ? io_schedule+0x4a/0x5f
[383040.964301]  [<c10ea946>] ? sleep_on_buffer+0x5/0x8
[383040.964311]  [<c12c3084>] ? __wait_on_bit+0x2f/0x54
[383040.964322]  [<c10ea941>] ? wait_on_buffer+0x18/0x18
[383040.964332]  [<c12c3104>] ? out_of_line_wait_on_bit+0x5b/0x63
[383040.964343]  [<c10ea941>] ? wait_on_buffer+0x18/0x18
[383040.964354]  [<c104d9dd>] ? autoremove_wake_function+0x29/0x29
[383040.964366]  [<c10ea927>] ? __wait_on_buffer+0x18/0x1a
[383040.964422]  [<f82cf3d7>] ? ext3_bread+0x3a/0x54 [ext3]
[383040.964444]  [<f82d0da2>] ? htree_dirblock_to_tree+0x27/0xee [ext3]
[383040.964469]  [<f82d205b>] ? ext3_htree_fill_tree+0x120/0x196 [ext3]
[383040.964490]  [<f82cac49>] ? free_rb_tree_fname+0x2e/0x6c [ext3]
[383040.964510]  [<f82cac49>] ? free_rb_tree_fname+0x2e/0x6c [ext3]
[383040.964530]  [<f82cb024>] ? ext3_readdir+0x1a6/0x5ab [ext3]
[383040.964543]  [<c10d6d92>] ? do_filp_open+0x23/0x5c
[383040.964554]  [<c10d8b24>] ? sys_ioctl+0x67/0x67
[383040.964567]  [<c1122058>] ? fsnotify_perm+0x4e/0x5a
[383040.964578]  [<c10d8dbb>] ? vfs_readdir+0x64/0x88
[383040.964587]  [<c10d8b24>] ? sys_ioctl+0x67/0x67
[383040.964597]  [<c10d8f36>] ? sys_getdents64+0x64/0xa6
[383040.964611]  [<c12c835f>] ? sysenter_do_call+0x12/0x28

Source :
http://blog.ronnyegner-consulting.de/2011/10/13/info-task-blocked-for-more-than-120-seconds/

Correction :

vi /etc/sysctl.conf
vm.dirty_ratio=10

sysctl -p