(Courriels de diversion: <planait@postdations-embranchements.com> <grills@infererions-estompera.com> <repliquais@coutes-sertis.com> <vidangera@dechaînez-deplacerent.com> <differentielles@interviewions-encans.com> <recycler@marquee-remontre.com> <siderais@decuver-depolitisees.com> <verdoyante@requisitionnant-certaines.com> <surpayerai@mimes-digeste.com> <correspondrons@ciselait-tripleras.com> )
Bonjour, j'ai déjà évoqué mon problème, mais il ne semble pas vouloir se
résoudre...
J'ai pourtant cherché un peu partout une réponse.
Bon, je récapitule :
Ordi : Athlon 1800+, Suse 9.2 (noyau mis à jour 2.6.8-24.11-default) sur hda.
hdb : MDK10.1
hdc graveur samsung (maitre)
hdd lecteur dvd samsung (esclave)
Le graveur est reconnu, configuré par Suse. Il marche très bien avec k3b, je
peux graver tout type de CD sans aucun problème (idem sous MDK10.1).
Le problème, au bout d'une certain temps, on va dire 3 à 4 heures durant
lesquelles l'ordi est allumé, et que je n'ai pas sollicité le graveur, il
m'est impossible de l'utiliser (ouvrir le graveur, pour y glisser un CD,
lancer k3b, ce-dernier bloque à la recherche des périphériques) sans avoir ,
au mieux à rebooter, au pire le reset.
Lorsque je sollicite l'ouverture du graveur, rien ne se passe, et au bout d'1
minute, un process se lance jusq'au blocage complet de l'ordinateur.
Je viens de découvrir dans le fichier /var/log/warn ceci :
---------------------------------------------------------------------------------------------------------------
Jan 25 11:33:33 rosebud kernel: end_request: I/O error, dev fd0, sector 0
Jan 25 11:33:33 rosebud kernel: end_request: I/O error, dev fd0, sector 0
Jan 25 11:33:33 rosebud kernel: ppa: Version 2.07 (for Linux 2.4.x)
Jan 25 11:34:03 rosebud kernel: hdc: irq timeout: status=0xd0 { Busy }
Jan 25 11:34:03 rosebud kernel: hdc: irq timeout: error=0x00
Jan 25 11:34:08 rosebud kernel: hdc: status timeout: status=0xd0 { Busy }
Jan 25 11:34:08 rosebud kernel: hdc: status timeout: error=0x00
Jan 25 11:34:08 rosebud kernel: hdc: drive not ready for command
Jan 25 11:34:09 rosebud kernel: hdc: ATAPI reset complete
Jan 25 11:34:39 rosebud kernel: hdc: irq timeout: status=0xd0 { Busy }
Jan 25 11:34:39 rosebud kernel: hdc: irq timeout: error=0x00
Jan 25 11:34:44 rosebud kernel: hdc: status timeout: status=0xd0 { Busy }
Jan 25 11:34:44 rosebud kernel: hdc: status timeout: error=0x00
Jan 25 11:34:44 rosebud kernel: hdc: drive not ready for command
Jan 25 11:34:44 rosebud kernel: hdc: ATAPI reset complete
-----------------------------------------------------------------------------------------------------------
cela résule ce qui s'est passé juste avant le dernier reset dû au graveur
bloqué. Je vois qu'on y parle d'irq de timeout sur mon hdc (graveur), mais
moi j'y pige que couic..
Je me pose cette question : sachant que graveur et dvd sont de la même marque,
serait-il possible qu'au niveau du hardware, samsung demande (par défaut) des
irq semblables pour les deux appareils, ce qui mettrait la pagaille chez
Suse ?
Quelqu'un saurait m'expliquer ce qu'il y a d'écrit dans ce fichier ?
Sur ma Mandrake, je n'ai pas ce problème...
mais le fichier dmesg me dit :
----------------------------------------------------------------------------------------------------------
Probing IDE interface ide1...
hdc: SAMSUNG CD-R/RW SW-252S, ATAPI CD/DVD-ROM drive
hdd: SAMSUNG DVD-ROM SD-616T, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
PCI: Found IRQ 3 for device 0000:00:10.0
IRQ routing conflict for 0000:00:10.0, have irq 5, want irq 3
IRQ routing conflict for 0000:00:10.1, have irq 5, want irq 3
IRQ routing conflict for 0000:00:10.2, have irq 5, want irq 3
IRQ routing conflict for 0000:00:10.3, have irq 5, want irq 3
uhci_hcd 0000:00:10.0: UHCI Host Controller
uhci_hcd 0000:00:10.0: irq 5, io base 0000d000
uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
PCI: Found IRQ 3 for device 0000:00:10.1
IRQ routing conflict for 0000:00:10.0, have irq 5, want irq 3
IRQ routing conflict for 0000:00:10.1, have irq 5, want irq 3
IRQ routing conflict for 0000:00:10.2, have irq 5, want irq 3
IRQ routing conflict for 0000:00:10.3, have irq 5, want irq 3
uhci_hcd 0000:00:10.1: UHCI Host Controller
uhci_hcd 0000:00:10.1: irq 5, io base 0000b800
uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
PCI: Found IRQ 3 for device 0000:00:10.2
IRQ routing conflict for 0000:00:10.0, have irq 5, want irq 3
IRQ routing conflict for 0000:00:10.1, have irq 5, want irq 3
IRQ routing conflict for 0000:00:10.2, have irq 5, want irq 3
IRQ routing conflict for 0000:00:10.3, have irq 5, want irq 3
uhci_hcd 0000:00:10.2: UHCI Host Controller
uhci_hcd 0000:00:10.2: irq 5, io base 0000b400
uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 3
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
PCI: Found IRQ 3 for device 0000:00:10.3
IRQ routing conflict for 0000:00:10.0, have irq 5, want irq 3
IRQ routing conflict for 0000:00:10.1, have irq 5, want irq 3
IRQ routing conflict for 0000:00:10.2, have irq 5, want irq 3
IRQ routing conflict for 0000:00:10.3, have irq 5, want irq 3
ehci_hcd 0000:00:10.3: EHCI Host Controller
ehci_hcd 0000:00:10.3: irq 5, pci mem f89e5000
ehci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 4
ehci_hcd 0000:00:10.3: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10
------------------------------------------------------------------------------------------------------------
donc, si je comprends, ici aussi un preobleme d'irq.
Chez Suse, dans bootmsg, voici ce que je trouve :
----------------------------------------------------------------------------------------------------------
<7>Probing IDE interface ide1...
<4>hdc: SAMSUNG CD-R/RW SW-252S, ATAPI CD/DVD-ROM drive
<4>hdd: SAMSUNG DVD-ROM SD-616T, ATAPI CD/DVD-ROM drive
<4>ide1 at 0x170-0x177,0x376 on irq 15
<7>Probing IDE interface ide2...
<7>ide2: Wait for ready failed before probe !
<7>Probing IDE interface ide3...
<7>ide3: Wait for ready failed before probe !
<7>Probing IDE interface ide4...
<7>ide4: Wait for ready failed before probe !
<7>Probing IDE interface ide5...
<7>ide5: Wait for ready failed before probe !
<6>USB Universal Host Controller Interface driver v2.2
<6>ACPI: PCI interrupt 0000:00:10.0[A] -> GSI 5 (level, low) -> IRQ 5
<6>uhci_hcd 0000:00:10.0: UHCI Host Controller
<6>uhci_hcd 0000:00:10.0: irq 5, io base 0000d000
<6>uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 1
<6>usb usb1: Product: UHCI Host Controller
<6>usb usb1: Manufacturer: Linux 2.6.8-24.11-default uhci_hcd
<6>usb usb1: SerialNumber: 0000:00:10.0
<6>hub 1-0:1.0: USB hub found
<6>hub 1-0:1.0: 2 ports detected
<6>ACPI: PCI interrupt 0000:00:10.1[B] -> GSI 5 (level, low) -> IRQ 5
<6>uhci_hcd 0000:00:10.1: UHCI Host Controller
<6>uhci_hcd 0000:00:10.1: irq 5, io base 0000b800
<6>uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 2
<6>usb usb2: Product: UHCI Host Controller
<6>usb usb2: Manufacturer: Linux 2.6.8-24.11-default uhci_hcd
<6>usb usb2: SerialNumber: 0000:00:10.1
<6>hub 2-0:1.0: USB hub found
<6>hub 2-0:1.0: 2 ports detected
<6>ACPI: PCI interrupt 0000:00:10.2[C] -> GSI 5 (level, low) -> IRQ 5
<6>uhci_hcd 0000:00:10.2: UHCI Host Controller
<6>uhci_hcd 0000:00:10.2: irq 5, io base 0000b400
<6>uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 3
<6>usb usb3: Product: UHCI Host Controller
<6>usb usb3: Manufacturer: Linux 2.6.8-24.11-default uhci_hcd
<6>usb usb3: SerialNumber: 0000:00:10.2
<6>hub 3-0:1.0: USB hub found
<6>hub 3-0:1.0: 2 ports detected
<6>usb 2-1: new full speed USB device using address 2
<6>usb 2-1: Product: Samsung ML-1510_700
<6>usb 2-1: Manufacturer: Samsung Electronics Co., Ltd.
<6>usb 2-1: SerialNumber: 2721BADWB09812B0
<6>usb 2-2: new low speed USB device using address 3
<6>usb 2-2: Product: ET-0405A-UV2.0-3
<6>usb 2-2: Manufacturer: WACOM
<6>drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 2 if 0 alt
0 proto 2 vid 0x04E8 pid 0x3242
<6>usbcore: registered new driver usblp
<6>drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
<6>usbcore: registered new driver hiddev
<4>usbhid: probe of 2-2:1.0 failed with error -5
<6>usbcore: registered new driver usbhid
<6>drivers/usb/input/hid-core.c: v2.0:USB HID core driver
<6>ACPI: PCI interrupt 0000:00:10.3[D] -> GSI 5 (level, low) -> IRQ 5
<6>ehci_hcd 0000:00:10.3: EHCI Host Controller
<6>ehci_hcd 0000:00:10.3: irq 5, pci mem f882a000
<6>ehci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 4
<6>ehci_hcd 0000:00:10.3: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10
<6>usb usb4: Product: EHCI Host Controller
<6>usb usb4: Manufacturer: Linux 2.6.8-24.11-default ehci_hcd
<6>usb usb4: SerialNumber: 0000:00:10.3
<6>hub 4-0:1.0: USB hub found
<6>hub 4-0:1.0: 6 ports detected
<6>usb 2-1: USB disconnect, address 2
<6>drivers/usb/class/usblp.c: usblp0: removed
<6>usb 2-2: USB disconnect, address 3
----------------------------------------------------------------------------------------------------------
là c'est la même chose ?
Enfin, si quelqu'un comprends et veut bien m'expliquer comment remédier à
cela, merci...
--
serge CARRERE
http://www.carrere.homelinux.com
--------------------------------------------------------------------
Les listes de diffusion occultes: <URL:http://www.CULTe.org/listes/>