Bug 14786

What m/b ?

can you attach dmesg from both 3.10 and 3.14 and lspcidrake -v

CC: (none) => tmb

Created attachment 5697 [details]
lspci and dmesg

Yeah, just as I suspected you have one of the problematic jmicron controllers...

from dmesg:

First its correctly identified:
[    0.723592] pata_jmicron 0000:03:00.1: enabling device (0000 -> 0001)
[    0.723608] pata_jmicron 0000:03:00.1: PCI->APIC IRQ transform: INT B -> IRQ 16
[    0.723942] scsi2 : pata_jmicron
[    0.724051] scsi3 : pata_jmicron
[    0.724089] ata3: PATA max UDMA/100 cmd 0xec00 ctl 0xe880 bmdma 0xe400 irq 16
[    0.724091] ata4: PATA max UDMA/100 cmd 0xe800 ctl 0xe480 bmdma 0xe408 irq 16
[    0.878518] ata3.00: ATAPI: HL-DT-ST DVDRAM_GSA-H40N, RA00, max UDMA/66
[    0.884515] ata3.00: configured for UDMA/66
[    1.275026] tsc: Refined TSC clocksource calibration: 2599.999 MHz
[    2.275095] Switched to clocksource tsc


Then it goes downhill:
[    5.884034] ata3.00: qc timeout (cmd 0xa0)
[    5.884039] ata3.00: TEST_UNIT_READY failed (err_mask=0x4)
[    6.044510] ata3.00: configured for UDMA/66
[   11.044048] ata3.00: qc timeout (cmd 0xa0)
[   11.044053] ata3.00: TEST_UNIT_READY failed (err_mask=0x4)
[   11.044057] ata3.00: limiting speed to UDMA/66:PIO3
[   11.204509] ata3.00: configured for UDMA/66
[   16.204034] ata3.00: qc timeout (cmd 0xa0)
[   16.204038] ata3.00: TEST_UNIT_READY failed (err_mask=0x4)
[   16.204041] ata3.00: disabled
[   16.204063] ata3: soft resetting link
[   16.355088] ata3: EH complete


There are some fixes coming in upstream that should probably be backported, I'll have a look on it...

you also forgot the "-v" part of lspcidrake, so I cant see exact pci ids, so please provide it again

 1468.155591] ata9.00: ATAPI: HL-DT-ST DVDRAM_GSA-H40N, RA00, max UDMA/66
[ 1468.161551] ata9.00: configured for UDMA/66
[ 1473.161069] ata9.00: qc timeout (cmd 0xa0)
[ 1473.161075] ata9.00: TEST_UNIT_READY failed (err_mask=0x5)
[ 1473.321564] ata9.00: configured for UDMA/66
[ 1478.321054] ata9.00: qc timeout (cmd 0xa0)
[ 1478.321072] ata9.00: TEST_UNIT_READY failed (err_mask=0x5)
[ 1478.321078] ata9.00: limiting speed to UDMA/66:PIO3
[ 1478.481551] ata9.00: configured for UDMA/66
[ 1483.481055] ata9.00: qc timeout (cmd 0xa0)
[ 1483.481073] ata9.00: TEST_UNIT_READY failed (err_mask=0x5)
[ 1483.481077] ata9.00: disabled

Still an issue.

03:00.0 SATA controller: JMicron Technology Corp. JMB361 AHCI/IDE (rev 02) (prog-if 01 [AHCI 1.0])
        Subsystem: ASUSTeK Computer Inc. Device 8387
        Physical Slot: 0-2
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at faefe000 (32-bit, non-prefetchable) [size=8K]
        Expansion ROM at faee0000 [disabled] [size=64K]
        Capabilities: [68] Power Management version 2
        Capabilities: [50] Express Legacy Endpoint, MSI 01
        Kernel driver in use: ahci

03:00.1 IDE interface: JMicron Technology Corp. JMB361 AHCI/IDE (rev 02) (prog-if 85 [Master SecO PriO])
        Subsystem: ASUSTeK Computer Inc. Device 8387
        Physical Slot: 0-2
        Flags: bus master, fast devsel, latency 0, IRQ 16
        I/O ports at ec00 [size=8]
        I/O ports at e880 [size=4]
        I/O ports at e800 [size=8]
        I/O ports at e480 [size=4]
        I/O ports at e400 [size=16]
        Capabilities: [68] Power Management version 2
        Kernel driver in use: pata_jmicron
        Kernel modules: pata_jmicron, pata_acpi, ata_generic, jmicron, ide_pci_generic

Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Status: NEW => RESOLVED
Resolution: (none) => OLD

Dup to a still open bug report (by the same reporter), this issue is still live

*** This bug has been marked as a duplicate of bug 19599 ***

CC: (none) => thierry.vignaud
Resolution: OLD => DUPLICATE