Portál AbcLinuxu, 7. května 2025 07:33
/dev/md/0 /boot /dev/md/1 / /dev/md/2 /backup /dev/sda4 swap /dev/sdb4 swap raidy jsem vytvořil příkazem mdadm --create parametry(chunk size je defaultní)Problém je, že systém ač běží, čas od času se po pár minutách prostě zasekne třeba na 40 vteřin a veškerá snaha o zápis na raid pole je marná, na další disk /dev/sdc1, který není v raidu to jde v pohodě. Kde je problém?
...
kobject_add failed for uhci_hcd with -EEXIST, don't try to register things with the same name in the same directory.
[<c03e86f7>] kobject_shadow_add+0x117/0x1a0
[<c013fba4>] mod_sysfs_setup+0x24/0xb0
[<c0141458>] sys_init_module+0x1648/0x1940
[<c0102ae8>] syscall_call+0x7/0xb
[<c0710000>] __mutex_lock_slowpath+0x40/0x90
=======================
kobject_add failed for uhci_hcd with -EEXIST, don't try to register things with the same name in the same directory.
[<c03e86f7>] kobject_shadow_add+0x117/0x1a0
[<c013fba4>] mod_sysfs_setup+0x24/0xb0
[<c0141458>] sys_init_module+0x1648/0x1940
[<c0102ae8>] syscall_call+0x7/0xb
[<c0710000>] __mutex_lock_slowpath+0x40/0x90
=======================
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
kobject_add failed for uhci_hcd with -EEXIST, don't try to register things with the same name in the same directory.
[<c03e86f7>] kobject_shadow_add+0x117/0x1a0
[<c013fba4>] mod_sysfs_setup+0x24/0xb0
[<c0141458>] sys_init_module+0x1648/0x1940
[<c0102ae8>] syscall_call+0x7/0xb
[<c0710000>] __mutex_lock_slowpath+0x40/0x90
=======================
kobject_add failed for uhci_hcd with -EEXIST, don't try to register things with the same name in the same directory.
[<c03e86f7>] kobject_shadow_add+0x117/0x1a0
[<c013fba4>] mod_sysfs_setup+0x24/0xb0
[<c0141458>] sys_init_module+0x1648/0x1940
[<c0102ae8>] syscall_call+0x7/0xb
[<c0710000>] __mutex_lock_slowpath+0x40/0x90
=======================
kobject_add failed for ehci_hcd with -EEXIST, don't try to register things with the same name in the same directory.
[<c03e86f7>] kobject_shadow_add+0x117/0x1a0
[<c013fba4>] mod_sysfs_setup+0x24/0xb0
[<c0141458>] sys_init_module+0x1648/0x1940
[<c0102ae8>] syscall_call+0x7/0xb
=======================
i2c_core: exports duplicate symbol i2c_smbus_write_i2c_block_data (owned by kernel)
intel_rng: FWH not detected
ACPI: PCI Interrupt 0000:00:1f.3[B] -> GSI 19 (level, low) -> IRQ 19
sd 2:0:0:0: Attached scsi generic sg0 type 0
sd 3:0:0:0: Attached scsi generic sg1 type 0
sd 4:0:0:0: Attached scsi generic sg2 type 0
iTCO_vendor_support: vendor-support=0
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.01 (21-Jan-2007)
iTCO_wdt: Found a ICH6 or ICH6R TCO device (Version=2, TCOBASE=0x7060)
iTCO_wdt: heartbeat value must be 2<heartbeat<39 (TCO v1) or 613 (TCO v2), using 30
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
....
ata3.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 frozen
ata3.00: cmd 61/08:00:bf:31:0f/00:00:00:00:00/40 tag 0 cdb 0x0 data 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3: soft resetting port
ata3: softreset failed (port busy but CLO unavailable)
ata3: softreset failed, retrying in 5 secs
ata3: hard resetting port
ata3: port is slow to respond, please be patient (Status 0x80)
ata3: port failed to respond (30 secs, Status 0x80)
ata3: COMRESET failed (device not ready)
ata3: hardreset failed, retrying in 5 secs
ata3: hard resetting port
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata3.00: configured for UDMA/133
ata3: EH complete
SCSI device sdc: 312581808 512-byte hdwr sectors (160042 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
kjournald starting. Commit interval 5 seconds
EXT3 FS on md0, internal journal
...
ata3: soft resetting port ata3: softreset failed (port busy but CLO unavailable) ata3: softreset failed, retrying in 5 secs ata3: hard resetting port ata3: port is slow to respond, please be patient (Status 0x80)Presne toto mi robilo na doske s AHCI SATA ovladacom v jadre 2.6.18.x. Od upgradu na 2.6.20.x to prestalo. Stavalo sa mi to na disku, na ktory sa pristupovalo iba obcas, takze ak ubehla prilis dlha doba od posledneho pristupu, tak sa nieco cestou uspalo a driver to nevedel korektne zobudit. Takze reset a potom to slo. Aky mas radic a driver na neho? Vela driverov cez libata su este iba EXPERIMENTAL a obcas aj v stych stabilnych sa najde chyba. Pripadne mozes skusit stare IDE (prip. SATA) drivery a nie cez libata.
21.7.2007 00:42
Luboš Doležel (Doli) | skóre: 98
| blog: Doliho blog
| Kladensko
21.7.2007 06:36
michich | skóre: 51
| blog: ohrivane_parky
Tiskni
Sdílej:
ISSN 1214-1267, (c) 1999-2007 Stickfish s.r.o.
21.7.2007 07:39