Bug 103731 - timeout on SSD and kernel 4.1.3 and >
Summary: timeout on SSD and kernel 4.1.3 and >
Status: NEW
Alias: None
Product: Platform Specific/Hardware
Classification: Unclassified
Component: x86-64 (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: fs_ext4@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-29 19:02 UTC by Giuseppe
Modified: 2016-11-29 14:41 UTC (History)
2 users (show)

See Also:
Kernel Version: >4.1.3
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Giuseppe 2015-08-29 19:02:47 UTC
there is an error in boot.-
this error generate a timeout of 4 seconds.
attach dmesg to clarify this bug (I have a SSD samsung 850 EVO and Fedora 22)


[    1.947795] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio4/input/input12
[    5.890091] ata1.00: qc timeout (cmd 0x2f)
[    5.890096] ata1.00: failed to get NCQ Send/Recv Log Emask 0x5
[    5.890099] ata1.00: ATA-9: Samsung SSD 850 EVO 250GB, EMT01B6Q, max UDMA/133
[    5.890102] ata1.00: 488397168 sectors, multi 1: LBA48 NCQ (depth 31/32)
[    5.890105] ata1.00: failed to get Identify Device Data, Emask 0x40
[    5.890111] ata1.00: failed to set xfermode (err_mask=0x40)
Comment 1 Eric Sandeen 2015-08-31 13:16:29 UTC
This behavior has nothing to do with ext4...
Comment 2 Giuseppe 2015-08-31 16:02:46 UTC
(In reply to Eric Sandeen from comment #1)
> This behavior has nothing to do with ext4...

I agree with you. probably is a communication error between SSD and kernel. Do I have to change the Component?
Comment 3 Eric Sandeen 2015-08-31 16:36:28 UTC
That would get the right eyes on it.  For some reason I can't admin these bugs, so yes, you'll have to do it.

Thanks,
-Eric
Comment 4 Giuseppe 2015-08-31 19:35:02 UTC
(In reply to Eric Sandeen from comment #3)
> That would get the right eyes on it.  For some reason I can't admin these
> bugs, so yes, you'll have to do it.
> 
> Thanks,
> -Eric


 done

thanks for the answers

Note You need to log in before you can comment on or make changes to this bug.