Re: Negociation SATA

étrangement, je n'ai plus de trace du disque dans les logs depuis que j'ai essayé de brancher mon disque sur un autre port SATA (mais le disque n'était alors plus vu lors de la POST donc je l'ai remis sur le port 1).

Par contre, je viens de découvrir ça dans les logs:

Nov 27 12:27:41 localhost kernel: [55608.577053] ------------[ cut here ]------------
Nov 27 12:27:41 localhost kernel: [55608.577063] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x257/0x260()
Nov 27 12:27:41 localhost kernel: [55608.577067] Hardware name: System Product Name
Nov 27 12:27:41 localhost kernel: [55608.577070] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
Nov 27 12:27:41 localhost kernel: [55608.577073] Modules linked in: r8169 mii fuse ipv6 ext2 snd_hda_codec_hdmi snd_hda_codec_via nvidia(P) snd_hda_intel snd_hda_codec snd_hwdep snd_pcm firewire_ohci snd_timer firewire_core snd soundcore evdev crc_itu_t iTCO_wdt pcspkr i7core_edac edac_core psmouse serio_raw iTCO_vendor_support i2c_i801 snd_page_alloc i2c_core asus_atk0110 processor button ext4 mbcache jbd2 crc16 pata_acpi sd_mod pata_jmicron ahci libahci libata ehci_hcd scsi_mod usbcore [last unloaded: mii]
Nov 27 12:27:41 localhost kernel: [55608.577126] Pid: 0, comm: swapper Tainted: P I 3.1.2-1-ARCH #1
Nov 27 12:27:41 localhost kernel: [55608.577129] Call Trace:
Nov 27 12:27:41 localhost kernel: [55608.577132] <IRQ> [<ffffffff81061b9f>] warn_slowpath_common+0x7f/0xc0
Nov 27 12:27:41 localhost kernel: [55608.577147] [<ffffffff8122c684>] ? timerqueue_add+0x74/0xc0
Nov 27 12:27:41 localhost kernel: [55608.577153] [<ffffffff81061c96>] warn_slowpath_fmt+0x46/0x50
Nov 27 12:27:41 localhost kernel: [55608.577159] [<ffffffff81094d92>] ? clockevents_program_event+0x62/0xa0
Nov 27 12:27:41 localhost kernel: [55608.577165] [<ffffffff813642c7>] dev_watchdog+0x257/0x260
Nov 27 12:27:41 localhost kernel: [55608.577171] [<ffffffff81071e61>] run_timer_softirq+0x131/0x440
Nov 27 12:27:41 localhost kernel: [55608.577176] [<ffffffff81364070>] ? qdisc_reset+0x50/0x50
Nov 27 12:27:41 localhost kernel: [55608.577184] [<ffffffff810691c0>] __do_softirq+0xb0/0x270
Nov 27 12:27:41 localhost kernel: [55608.577188] [<ffffffff8140c6ac>] call_softirq+0x1c/0x30
Nov 27 12:27:41 localhost kernel: [55608.577191] [<ffffffff81016a15>] do_softirq+0x65/0xa0
Nov 27 12:27:41 localhost kernel: [55608.577193] [<ffffffff810696ce>] irq_exit+0x9e/0xc0
Nov 27 12:27:41 localhost kernel: [55608.577195] [<ffffffff8140cf63>] do_IRQ+0x63/0xe0
Nov 27 12:27:41 localhost kernel: [55608.577198] [<ffffffff81409bae>] common_interrupt+0x6e/0x6e
Nov 27 12:27:41 localhost kernel: [55608.577199] <EOI> [<ffffffff8108a71d>] ? notifier_call_chain+0x4d/0x70
Nov 27 12:27:41 localhost kernel: [55608.577205] [<ffffffff81279eab>] ? intel_idle+0xcb/0x120
Nov 27 12:27:41 localhost kernel: [55608.577207] [<ffffffff81279e8d>] ? intel_idle+0xad/0x120
Nov 27 12:27:41 localhost kernel: [55608.577210] [<ffffffff8131d6a6>] cpuidle_idle_call+0xc6/0x350
Nov 27 12:27:41 localhost kernel: [55608.577212] [<ffffffff81013229>] cpu_idle+0xc9/0x120
Nov 27 12:27:41 localhost kernel: [55608.577216] [<ffffffff813e6862>] rest_init+0x96/0xa4
Nov 27 12:27:41 localhost kernel: [55608.577218] [<ffffffff8194fc15>] start_kernel+0x3bf/0x3cc
Nov 27 12:27:41 localhost kernel: [55608.577221] [<ffffffff8194f347>] x86_64_start_reservations+0x132/0x136
Nov 27 12:27:41 localhost kernel: [55608.577223] [<ffffffff8194f140>] ? early_idt_handlers+0x140/0x140
Nov 27 12:27:41 localhost kernel: [55608.577225] [<ffffffff8194f44d>] x86_64_start_kernel+0x102/0x111
Nov 27 12:27:41 localhost kernel: [55608.577227] ---[ end trace a7919e7f17c0a727 ]---

A ce moment là, j'étais entrain de tester différentes combinaison de vitesse et de duplex. A noter qu'en retournant à 10Mbits full duplex, cette fois-ci cela ne fonctionnait plus et j'ai du rebooter la machine pour à nouveau récupérer le réseau en 10Mbits full.

Pour en revenir au disque, finalement smartctl indique quand même quelques bricoles:

SMART Error Log Version: 1
ATA Error Count: 185 (device log contains only the most recent five errors)
 CR = Command Register [HEX]
 FR = Features Register [HEX]
 SC = Sector Count Register [HEX]
 SN = Sector Number Register [HEX]
 CL = Cylinder Low Register [HEX]
 CH = Cylinder High Register [HEX]
 DH = Device/Head Register [HEX]
 DC = Device Command Register [HEX]
 ER = Error register [HEX]
 ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 185 occurred at disk power-on lifetime: 7504 hours (312 days + 16 hours)
 When the command that caused the error occurred, the device was active or idle.
 After command completion occurred, registers were:
 ER ST SC SN CL CH DH
 -- -- -- -- -- -- --
 84 51 00 00 00 00 a0
 Commands leading to the command that caused the error were:
 CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
 -- -- -- -- -- -- -- -- ---------------- --------------------
 ec 00 00 00 00 00 a0 08 00:00:00.958 IDENTIFY DEVICE
 ef 03 42 00 00 00 a0 08 00:00:00.958 SET FEATURES [Set transfer mode]
 ef 10 02 00 00 00 a0 08 00:00:00.958 SET FEATURES [Reserved for Serial ATA]
 27 00 00 00 00 00 e0 08 00:00:00.958 READ NATIVE MAX ADDRESS EXT
 ec 00 00 00 00 00 a0 08 00:00:00.958 IDENTIFY DEVICE
Error 184 occurred at disk power-on lifetime: 7504 hours (312 days + 16 hours)
 When the command that caused the error occurred, the device was active or idle.
 After command completion occurred, registers were:
 ER ST SC SN CL CH DH
 -- -- -- -- -- -- --
 84 51 00 00 00 00 a0
 Commands leading to the command that caused the error were:
 CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
 -- -- -- -- -- -- -- -- ---------------- --------------------
 ec 00 00 00 00 00 a0 08 00:00:00.947 IDENTIFY DEVICE
 ef 03 42 00 00 00 a0 08 00:00:00.947 SET FEATURES [Set transfer mode]
 ef 10 02 00 00 00 a0 08 00:00:00.947 SET FEATURES [Reserved for Serial ATA]
 27 00 00 00 00 00 e0 08 00:00:00.947 READ NATIVE MAX ADDRESS EXT
 ec 00 00 00 00 00 a0 08 00:00:00.947 IDENTIFY DEVICE
Error 183 occurred at disk power-on lifetime: 7504 hours (312 days + 16 hours)
 When the command that caused the error occurred, the device was active or idle.
 After command completion occurred, registers were:
 ER ST SC SN CL CH DH
 -- -- -- -- -- -- --
 84 51 00 00 00 00 a0
 Commands leading to the command that caused the error were:
 CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
 -- -- -- -- -- -- -- -- ---------------- --------------------
 ec 00 00 00 00 00 a0 08 00:00:00.925 IDENTIFY DEVICE
 00 10 00 00 00 00 00 08 00:00:00.925 NOP [Reserved subcommand]
 00 00 00 00 00 00 00 08 00:00:00.925 NOP [Abort queued commands]
 00 00 00 00 00 00 00 08 00:00:00.925 NOP [Abort queued commands]
 00 00 08 90 52 4c 40 08 00:00:00.915 NOP [Abort queued commands]
Error 182 occurred at disk power-on lifetime: 7504 hours (312 days + 16 hours)
 When the command that caused the error occurred, the device was active or idle.
 After command completion occurred, registers were:
 ER ST SC SN CL CH DH
 -- -- -- -- -- -- --
 84 51 00 00 00 00 a0
 Commands leading to the command that caused the error were:
 CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
 -- -- -- -- -- -- -- -- ---------------- --------------------
 ec 00 00 00 00 00 a0 08 00:00:00.841 IDENTIFY DEVICE
 ef 03 42 00 00 00 a0 08 00:00:00.841 SET FEATURES [Set transfer mode]
 ef 10 02 00 00 00 a0 08 00:00:00.841 SET FEATURES [Reserved for Serial ATA]
 27 00 00 00 00 00 e0 08 00:00:00.841 READ NATIVE MAX ADDRESS EXT
 ec 00 00 00 00 00 a0 08 00:00:00.841 IDENTIFY DEVICE
Error 181 occurred at disk power-on lifetime: 7504 hours (312 days + 16 hours)
 When the command that caused the error occurred, the device was active or idle.
 After command completion occurred, registers were:
 ER ST SC SN CL CH DH
 -- -- -- -- -- -- --
 84 51 00 00 00 00 a0
 Commands leading to the command that caused the error were:
 CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
 -- -- -- -- -- -- -- -- ---------------- --------------------
 ec 00 00 00 00 00 a0 08 00:00:00.812 IDENTIFY DEVICE
 00 00 e0 00 70 e0 40 08 00:00:00.812 NOP [Abort queued commands]
 00 00 08 f0 6f e0 40 08 00:00:00.812 NOP [Abort queued commands]
 60 00 08 f0 6f e0 40 08 00:00:00.807 READ FPDMA QUEUED
 60 90 08 f0 6f e0 40 08 00:00:00.812 READ FPDMA QUEUED

ça donne l'impression d'un problème de lien SATA mais je n'en suis pas certain. En plus, depuis que j'ai tripoter un peu le cable SATA, j'ai plus plus rien dans les logs par rapport au disque.

Mais je reste persuadé qu'il y a un lien avec mon problème réseau. Les points communs que je voit sont:
- le southbridge
* contrôleur réseau intégré qui ne fait plus de link en 100Mbits mais ok en 10Mbits
* contrôleur réseau en pci qui link en 100Mbits mais qui ne peut rien pinger même dans le lan (unreachable) sauf en 10Mbits (et à condition manifestement de ne pas trop le faire switcher de vitesse)
* problème d'accès disque
- l'alimentation
* une faiblesse de l'alimentation pourrait également être une explication à mes problèmes mais les tensions sont ok.