Forum |  HardWare.fr | News | Articles | PC | S'identifier | S'inscrire | Shop Recherche
4502 connectés 

  FORUM HardWare.fr
  Linux et OS Alternatifs

  [Resolu] [Debian] Se met en veille tout seul, impossible d'y acceder !

 
 


Dernière réponse
Sujet : [Resolu] [Debian] Se met en veille tout seul, impossible d'y acceder !
angel92 Bon en faite, le probleme venai du bios, je ne sais pas pourquoi mais la mise en veille du disque dur imposée par le bios fesait bugué Debian !
 
Bref, voila maintenant tout marche comme il faut !
Merci quand meme de votre aide !

Votre réponse
Nom d'utilisateur    Pour poster, vous devez être inscrit sur ce forum .... si ce n'est pas le cas, cliquez ici !
Le ton de votre message                        
                       
Votre réponse
[b][i][u][strike][spoiler][fixed][cpp][url][email][img][*]   
 
   [quote]
 
Options

 
Vous avez perdu votre mot de passe ?


Vue Rapide de la discussion
angel92 Bon en faite, le probleme venai du bios, je ne sais pas pourquoi mais la mise en veille du disque dur imposée par le bios fesait bugué Debian !
 
Bref, voila maintenant tout marche comme il faut !
Merci quand meme de votre aide !
angel92 je met un petit up parce mon serveur bug toujours :(
angel92 personne ne serai d'ou est ce que cela vient ?
angel92 nop j'ai po compilé de new noyau, j'ai install débian, pi postgre avec apt c'es tout.
 
voila ce qu'il ya dans /var/log/message
 

Citation :


May 30 11:19:41 localhost kernel: apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16)
May 30 11:38:40 localhost -- MARK --
May 30 11:58:40 localhost -- MARK --
May 30 12:18:40 localhost -- MARK --
May 30 12:38:40 localhost -- MARK --
May 30 12:58:40 localhost -- MARK --
May 30 13:11:24 localhost kernel: Sony CDU-535: probing base address 340
May 30 13:11:32 localhost kernel: Did not find a Sony CDU-535 drive
May 30 13:11:32 localhost kernel: sbpcd-0 [01]:  sbpcd.c v4.63 Andrew J. Kroll <ag784@freenet.buffalo.edu> Wed Jul 26 04:24:10 EDT 2000
May 30 13:11:32 localhost kernel: sbpcd-0 [02]:  Scanning 0x340 (LaserMate)...
May 30 13:12:05 localhost kernel: sbpcd-0 [03]:  Scanning 0x340 (SoundBlaster)...
May 30 13:12:37 localhost kernel: sbpcd-0 [04]:  No drive found.
May 30 13:12:37 localhost kernel: sbpcd-0 [01]:  sbpcd.c v4.63 Andrew J. Kroll <ag784@freenet.buffalo.edu> Wed Jul 26 04:24:10 EDT 2000
May 30 13:12:37 localhost kernel: sbpcd-0 [02]:  Scanning 0x340 (LaserMate)...
May 30 13:13:10 localhost kernel: sbpcd-0 [03]:  Scanning 0x340 (SoundBlaster)...
May 30 13:13:42 localhost kernel: sbpcd-0 [04]:  No drive found.
May 30 13:13:43 localhost kernel: sbpcd-0 [01]:  sbpcd.c v4.63 Andrew J. Kroll <ag784@freenet.buffalo.edu> Wed Jul 26 04:24:10 EDT 2000
May 30 13:13:43 localhost kernel: sbpcd-0 [02]:  Scanning 0x340 (LaserMate)...
May 30 13:14:15 localhost kernel: sbpcd-0 [03]:  Scanning 0x340 (SoundBlaster)...
May 30 13:14:48 localhost kernel: sbpcd-0 [04]:  No drive found.
May 30 13:14:48 localhost kernel: sbpcd-0 [01]:  sbpcd.c v4.63 Andrew J. Kroll <ag784@freenet.buffalo.edu> Wed Jul 26 04:24:10 EDT 2000
May 30 13:14:48 localhost kernel: sbpcd-0 [02]:  Scanning 0x340 (LaserMate)...
May 30 13:15:20 localhost kernel: sbpcd-0 [03]:  Scanning 0x340 (SoundBlaster)...
May 30 13:15:53 localhost kernel: sbpcd-0 [04]:  No drive found.
May 30 13:15:53 localhost kernel: sbpcd-0 [01]:  sbpcd.c v4.63 Andrew J. Kroll <ag784@freenet.buffalo.edu> Wed Jul 26 04:24:10 EDT 2000
May 30 13:15:53 localhost kernel: sbpcd-0 [02]:  Scanning 0x340 (LaserMate)...
May 30 13:16:26 localhost kernel: sbpcd-0 [03]:  Scanning 0x340 (SoundBlaster)...
May 30 13:16:58 localhost kernel: sbpcd-0 [04]:  No drive found.
May 30 13:17:04 localhost kernel: mcd: initialisation failed - No mcd device at 0x300 irq 11
May 30 13:17:14 localhost kernel: SJCD: Sanyo CDR-H94A cdrom driver version 1.7.
May 30 13:17:14 localhost kernel: SJCD: Resetting: .......... reset failed, no drive found.
May 30 13:17:14 localhost kernel: Trying to free nonexistent resource <00000340-00000343>
May 30 13:38:44 localhost -- MARK --


 
 
Le a du avoir lieu vers 13h38 quoi.
_darkalt3_ T'as installé un nouveau noyau ?
Tu as recompilé un noyau toi même ?
 
que donne /var/log/messages ?
angel92 alors la j'en ai pas la moindre idée !
_darkalt3_ Alors à ton avis c'est quoi toutes ces erreurs ?
angel92 voila ce qu'il se passe entre 2 boots, a mon avis faut voire vers la fin.
 

Citation :


May 30 12:09:01 localhost /USR/SBIN/CRON[1405]: (root) CMD (  [ -d /var/lib/php4 ] && find /var/lib/php4/ -type f -cmin +$(/usr/lib/php4/maxlifetime) -print0 | xargs -r -0 rm)
May 30 12:17:01 localhost /USR/SBIN/CRON[1416]: (root) CMD (   run-parts --report /etc/cron.hourly)
May 30 12:18:37 localhost dhclient: DHCPREQUEST on eth0 to 10.0.0.138 port 67
May 30 12:18:37 localhost dhclient: DHCPACK from 10.0.0.138
May 30 12:18:37 localhost dhclient: bound to 10.0.0.4 -- renewal in 3600 seconds.
May 30 12:38:40 localhost -- MARK --
May 30 12:39:01 localhost /USR/SBIN/CRON[1428]: (root) CMD (  [ -d /var/lib/php4 ] && find /var/lib/php4/ -type f -cmin +$(/usr/lib/php4/maxlifetime) -print0 | xargs -r -0 rm)
May 30 12:58:40 localhost -- MARK --
May 30 13:09:02 localhost /USR/SBIN/CRON[1443]: (root) CMD (  [ -d /var/lib/php4 ] && find /var/lib/php4/ -type f -cmin +$(/usr/lib/php4/maxlifetime) -print0 | xargs -r -0 rm)
May 30 13:11:24 localhost kernel: Sony CDU-535: probing base address 340
May 30 13:11:32 localhost kernel: Did not find a Sony CDU-535 drive
May 30 13:11:32 localhost insmod: /lib/modules/2.4.27-1-386/kernel/drivers/cdrom/sonycd535.o: init_module: Input/output error
May 30 13:11:32 localhost insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.       You may find more information in syslog or the output from dmesg
May 30 13:11:32 localhost insmod: /lib/modules/2.4.27-1-386/kernel/drivers/cdrom/sonycd535.o: insmod block-major-24 failed
May 30 13:11:32 localhost kernel: sbpcd-0 [01]:  sbpcd.c v4.63 Andrew J. Kroll <ag784@freenet.buffalo.edu> Wed Jul 26 04:24:10 EDT 2000
May 30 13:11:32 localhost kernel: sbpcd-0 [02]:  Scanning 0x340 (LaserMate)...
May 30 13:12:05 localhost kernel: sbpcd-0 [03]:  Scanning 0x340 (SoundBlaster)...
May 30 13:12:37 localhost kernel: sbpcd-0 [04]:  No drive found.
May 30 13:12:37 localhost insmod: /lib/modules/2.4.27-1-386/kernel/drivers/cdrom/sbpcd.o: init_module: Input/output error
May 30 13:12:37 localhost insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.       You may find more information in syslog or the output from dmesg
May 30 13:12:37 localhost insmod: /lib/modules/2.4.27-1-386/kernel/drivers/cdrom/sbpcd.o: insmod block-major-25 failed
May 30 13:12:37 localhost kernel: sbpcd-0 [01]:  sbpcd.c v4.63 Andrew J. Kroll <ag784@freenet.buffalo.edu> Wed Jul 26 04:24:10 EDT 2000
May 30 13:12:37 localhost kernel: sbpcd-0 [02]:  Scanning 0x340 (LaserMate)...
May 30 13:13:10 localhost kernel: sbpcd-0 [03]:  Scanning 0x340 (SoundBlaster)...
May 30 13:13:42 localhost kernel: sbpcd-0 [04]:  No drive found.
May 30 13:13:43 localhost insmod: /lib/modules/2.4.27-1-386/kernel/drivers/cdrom/sbpcd.o: init_module: Input/output error
May 30 13:13:43 localhost insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.       You may find more information in syslog or the output from dmesg
May 30 13:13:43 localhost insmod: /lib/modules/2.4.27-1-386/kernel/drivers/cdrom/sbpcd.o: insmod block-major-25 failed
May 30 13:13:43 localhost kernel: sbpcd-0 [01]:  sbpcd.c v4.63 Andrew J. Kroll <ag784@freenet.buffalo.edu> Wed Jul 26 04:24:10 EDT 2000
May 30 13:13:43 localhost kernel: sbpcd-0 [02]:  Scanning 0x340 (LaserMate)...
May 30 13:14:15 localhost kernel: sbpcd-0 [03]:  Scanning 0x340 (SoundBlaster)...
May 30 13:14:48 localhost kernel: sbpcd-0 [04]:  No drive found.
May 30 13:14:48 localhost insmod: /lib/modules/2.4.27-1-386/kernel/drivers/cdrom/sbpcd.o: init_module: Input/output error
May 30 13:14:48 localhost insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.       You may find more information in syslog or the output from dmesg
May 30 13:14:48 localhost insmod: /lib/modules/2.4.27-1-386/kernel/drivers/cdrom/sbpcd.o: insmod block-major-25 failed
May 30 13:14:48 localhost kernel: sbpcd-0 [01]:  sbpcd.c v4.63 Andrew J. Kroll <ag784@freenet.buffalo.edu> Wed Jul 26 04:24:10 EDT 2000
May 30 13:14:48 localhost kernel: sbpcd-0 [02]:  Scanning 0x340 (LaserMate)...
May 30 13:15:20 localhost kernel: sbpcd-0 [03]:  Scanning 0x340 (SoundBlaster)...
May 30 13:15:53 localhost kernel: sbpcd-0 [04]:  No drive found.
May 30 13:15:53 localhost insmod: /lib/modules/2.4.27-1-386/kernel/drivers/cdrom/sbpcd.o: init_module: Input/output error
May 30 13:15:53 localhost insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.       You may find more information in syslog or the output from dmesg
May 30 13:15:53 localhost insmod: /lib/modules/2.4.27-1-386/kernel/drivers/cdrom/sbpcd.o: insmod block-major-25 failed
May 30 13:15:53 localhost kernel: sbpcd-0 [01]:  sbpcd.c v4.63 Andrew J. Kroll <ag784@freenet.buffalo.edu> Wed Jul 26 04:24:10 EDT 2000
May 30 13:15:53 localhost kernel: sbpcd-0 [02]:  Scanning 0x340 (LaserMate)...
May 30 13:16:26 localhost kernel: sbpcd-0 [03]:  Scanning 0x340 (SoundBlaster)...
May 30 13:16:58 localhost kernel: sbpcd-0 [04]:  No drive found.
May 30 13:16:58 localhost insmod: /lib/modules/2.4.27-1-386/kernel/drivers/cdrom/sbpcd.o: init_module: Input/output error
May 30 13:16:58 localhost insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.       You may find more information in syslog or the output from dmesg
May 30 13:16:58 localhost insmod: /lib/modules/2.4.27-1-386/kernel/drivers/cdrom/sbpcd.o: insmod block-major-25 failed
May 30 13:16:58 localhost insmod: /lib/modules/2.4.27-1-386/kernel/drivers/cdrom/cdu31a.o: init_module: Input/output error
May 30 13:16:58 localhost insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.       You may find more information in syslog or the output from dmesg
May 30 13:16:58 localhost insmod: /lib/modules/2.4.27-1-386/kernel/drivers/cdrom/cdu31a.o: insmod block-major-15 failed
May 30 13:17:04 localhost kernel: mcd: initialisation failed - No mcd device at 0x300 irq 11
May 30 13:17:04 localhost /USR/SBIN/CRON[1479]: (root) CMD (   run-parts --report /etc/cron.hourly)
May 30 13:17:04 localhost insmod: /lib/modules/2.4.27-1-386/kernel/drivers/cdrom/mcd.o: init_module: Input/output error
May 30 13:17:04 localhost insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.       You may find more information in syslog or the output from dmesg
May 30 13:17:04 localhost insmod: /lib/modules/2.4.27-1-386/kernel/drivers/cdrom/mcd.o: insmod block-major-23 failed
May 30 13:17:14 localhost kernel: SJCD: Sanyo CDR-H94A cdrom driver version 1.7.
May 30 13:17:14 localhost kernel: SJCD: Resetting: .......... reset failed, no drive found.
May 30 13:17:14 localhost kernel: Trying to free nonexistent resource <00000340-00000343>
May 30 13:17:14 localhost insmod: /lib/modules/2.4.27-1-386/kernel/drivers/cdrom/sjcd.o: init_module: Input/output error
May 30 13:17:14 localhost insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.       You may find more information in syslog or the output from dmesg
May 30 13:17:14 localhost insmod: /lib/modules/2.4.27-1-386/kernel/drivers/cdrom/sjcd.o: insmod block-major-18 failed
May 30 13:17:28 localhost kernel: optcd: unknown drive detected; aborting
May 30 13:17:28 localhost insmod: /lib/modules/2.4.27-1-386/kernel/drivers/cdrom/optcd.o: init_module: Input/output error
May 30 13:17:28 localhost insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.       You may find more information in syslog or the output from dmesg
May 30 13:17:28 localhost insmod: /lib/modules/2.4.27-1-386/kernel/drivers/cdrom/optcd.o: insmod block-major-17 failed
May 30 13:18:37 localhost dhclient: DHCPREQUEST on eth0 to 10.0.0.138 port 67
May 30 13:18:37 localhost dhclient: DHCPACK from 10.0.0.138
May 30 13:18:37 localhost dhclient: bound to 10.0.0.4 -- renewal in 3600 seconds.
May 30 13:38:44 localhost -- MARK --
May 30 13:39:01 localhost /USR/SBIN/CRON[1505]: (root) CMD (  [ -d /var/lib/php4 ] && find /var/lib/php4/ -type f -cmin +$(/usr/lib/php4/maxlifetime) -print0 | xargs -r -0 rm)
 
_darkalt3_ genre donner ce qui se passe dans le syslog avant la mise en veille, ou checker tout autre log qui pourrait donner une information interessante.
 
sinon dans le bios, etc, toutes les mises en veilles sont désactivées ?
angel92 keske je doi vérifier dans ce dossier ?
_darkalt3_ /var/log ?
angel92 un petit up !
angel92 VOila, mon serveur sous debian fait des siennes.
Il se met tout seul en veille toutes les 30 ou 20 minutes, et aprés impossible d'acceder au pc, ni par le réseau, ni sur le pc lui meme.
 
A quoi cela est due ?

Forum MesDiscussions.Net, Version 2010.2
(c) 2000-2011 Doctissimo

Copyright © 1997-2025 Groupe LDLC (Signaler un contenu illicite / Données personnelles)