Kernel 2.6.31+22

Support Debian
#1

Depuis le passage au nouveau Kernel voici le message d’erreure qui apparait :

Nov 25 15:08:17 xsre kernel: [    8.165582] hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }                             
Nov 25 15:08:17 xsre kernel: [    8.165728] hdc: possibly failed opcode: 0xa0                                                                  
Nov 25 15:08:17 xsre kernel: [    8.165769] hdc: drive not ready for command                                                                   
Nov 25 15:08:17 xsre kernel: [    8.165837] hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }                             
Nov 25 15:08:17 xsre kernel: [    8.165965] hdc: possibly failed opcode: 0xa0                                                                  
Nov 25 15:08:17 xsre kernel: [    8.166005] hdc: drive not ready for command                                                                   
Nov 25 15:08:17 xsre kernel: [    8.166072] hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }                             
Nov 25 15:08:17 xsre kernel: [    8.166201] hdc: possibly failed opcode: 0xa0                                                                  
Nov 25 15:08:17 xsre kernel: [    8.166242] hdc: drive not ready for command                                                                   
Nov 25 15:08:17 xsre kernel: [    8.166311] hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }                             
Nov 25 15:08:17 xsre kernel: [    8.166440] hdc: possibly failed opcode: 0xa0                                                                  
Nov 25 15:08:17 xsre kernel: [    8.166482] hdc: drive not ready for command                                                                   
Nov 25 15:08:17 xsre kernel: [    8.166549] hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }                             
Nov 25 15:08:17 xsre kernel: [    8.166679] hdc: possibly failed opcode: 0xa0                                                                  
Nov 25 15:08:17 xsre kernel: [    8.166719] hdc: drive not ready for command                                                                   
Nov 25 15:08:17 xsre kernel: [    8.166786] hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }                             
Nov 25 15:08:17 xsre kernel: [    8.166914] hdc: possibly failed opcode: 0xa0                                                                  
Nov 25 15:08:17 xsre kernel: [    8.166955] hdc: drive not ready for command                                                                   
Nov 25 15:08:17 xsre kernel: [    8.167022] hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }                             
Nov 25 15:08:17 xsre kernel: [    8.167151] hdc: possibly failed opcode: 0xa0                                                                  
Nov 25 15:08:17 xsre kernel: [    8.167192] hdc: drive not ready for command                                                                   
Nov 25 15:08:17 xsre kernel: [    8.167260] hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }                             
Nov 25 15:08:17 xsre kernel: [    8.167389] hdc: possibly failed opcode: 0xa0                                                                  
Nov 25 15:08:17 xsre kernel: [    8.167430] hdc: drive not ready for command                                                                   
Nov 25 15:08:17 xsre kernel: [    8.167497] hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }                             
Nov 25 15:08:17 xsre kernel: [    8.167625] hdc: possibly failed opcode: 0xa0                                                                  
Nov 25 15:08:17 xsre kernel: [    8.167666] hdc: drive not ready for command                                                                   
Nov 25 15:08:17 xsre kernel: [    8.167733] hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }                             
Nov 25 15:08:17 xsre kernel: [    8.167862] hdc: possibly failed opcode: 0xa0                                                                  
Nov 25 15:08:17 xsre kernel: [    8.167902] hdc: drive not ready for command                                                                   
Nov 25 15:08:17 xsre kernel: [    8.167969] hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }                             
Nov 25 15:08:17 xsre kernel: [    8.168121] hdc: possibly failed opcode: 0xa0                                                                  
Nov 25 15:08:17 xsre kernel: [    8.168163] hdc: drive not ready for command                                                                   
Nov 25 15:08:17 xsre kernel: [    8.168234] hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }                             
Nov 25 15:08:17 xsre kernel: [    8.168363] hdc: possibly failed opcode: 0xa0                                                                  
Nov 25 15:08:17 xsre kernel: [    8.168403] hdc: drive not ready for command                                                                   
Nov 25 15:08:17 xsre kernel: [    8.168512] hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }                             
Nov 25 15:08:17 xsre kernel: [    8.168641] hdc: possibly failed opcode: 0xa0                                                                  
Nov 25 15:08:17 xsre kernel: [    8.168683] hdc: drive not ready for command                                                                   
Nov 25 15:08:17 xsre kernel: [   13.172019] hdc: status timeout: status=0xd0 { Busy }                                                          
Nov 25 15:08:17 xsre kernel: [   13.172095] hdc: possibly failed opcode: 0xa0                                                                  
Nov 25 15:08:17 xsre kernel: [   13.172138] hdc: DMA disabled                                                                                  
Nov 25 15:08:17 xsre kernel: [   13.172165] hdc: drive not ready for command                                                                   
Nov 25 15:08:17 xsre kernel: [   13.220041] hdc: ATAPI reset complete

quelqu’un aurait une solution ? :smiley:

#2

[quote=“Excess”]Depuis le passage au nouveau Kernel voici le message d’erreure qui apparait :

Nov 25 15:08:17 xsre kernel: [    8.165582] hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }                             
Nov 25 15:08:17 xsre kernel: [    8.165728] hdc: possibly failed opcode: 0xa0                                                                  
Nov 25 15:08:17 xsre kernel: [    8.168683] hdc: drive not ready for command                                                                   
Nov 25 15:08:17 xsre kernel: [   13.172019] hdc: status timeout: status=0xd0 { Busy }                                                          
Nov 25 15:08:17 xsre kernel: [   13.172095] hdc: possibly failed opcode: 0xa0                                                                  
Nov 25 15:08:17 xsre kernel: [   13.172138] hdc: DMA disabled                                                                                  
Nov 25 15:08:17 xsre kernel: [   13.172165] hdc: drive not ready for command                                                                   
Nov 25 15:08:17 xsre kernel: [   13.220041] hdc: ATAPI reset complete

quelqu’un aurait une solution ? :smiley:[/quote]

Vérifie ton fstab et tant que t’y est c’est quoi hdc chez toi un disque ou un lecteur car il me semble que tu as perdu le support du dit hdc

#3

Salut merci pour ta réponse.
C’est un disque chez moi et de toute façon je n’ai pas touché au matos donc :unamused:
Enfin je ne comprend pas d’où cela peut provenir, je suis le seul à avoir ce problème à ce que je vois :confused:

#4

Pour sur je suis passé il y a quelques jours au 2.6.31 en SID et la seule chose que j’ai redouter c’était le changement de grub à grub2 le kernel n’a pas broncher.

#5

Salut,
Idem, je suis passé en 2.6.31 et y suis resté pendant quelques semaines, sans pb. (3 disques Sata & 1 Ide)
2.6.32 depuis quelques temps sans soucis non plus.

#6

Moi il n’y a aucun problème avec GRUB2 (je ne pense pas que ce soit en rapport avec) ça fait plusieurs semaines que je l’utilises mais c’est seulement depuis la mise à jour du kernel il y a moins de deux semaines il me semble.

#7

Salut,
Idem, je suis passé en 2.6.31 et y suis resté pendant quelques semaines, sans pb. (3 disques Sata & 1 Ide)
2.6.32 depuis quelques temps sans soucis non plus.[/quote]

Je dit rien de plus mais je fais la mise à jour du kernel de mon laptop à l’instant et aucun souci :stuck_out_tongue:

#8

Chanceux va ! :stuck_out_tongue:

Bon bah je vais signaler le bug