Bug 6907 - "ata6.00: failed to IDENTIFY" dmesg error on Sugarbay
Summary: "ata6.00: failed to IDENTIFY" dmesg error on Sugarbay
Status: RESOLVED WORKSFORME
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-meta-intel (show other bugs)
Version: 1.7
Hardware: x86 x86_64
: Medium normal
Target Milestone: 1.8
Assignee: Nitin Kamble
QA Contact: Lucian Musat
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-10-29 12:19 UTC by Lucian Musat
Modified: 2015-01-02 18:02 UTC (History)
1 user (show)

See Also:
OS type for building Yocto: ---
Type of Regression: New (Never tested)
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lucian Musat 2014-10-29 12:19:53 UTC
Tested Image: http://yocto-ab-master.jf.intel.com/pub/releases/yocto-meta-intel-2.0-rc3-dizzy-1.7-rc5/machines/sugarbay/core-image-sato-sdk-sugarbay.hddimg

Meta-intel 2.0 rc3 commit 002bef4c2a59e95503a2bb7729e7749cd5a9f65b
Poky dizzy 1.7 rc5 commit 924da20c6f2f183fa7e930e4c3c6b14c090acbe5
meta-qt3 commit 3016129d90b7ac8517a5227d819f10ad417b5b45

Hardware: Sugarbay, Core i7-2600
Error source: DMESG

The error was cought by the log parser automated test.

Central error: [    5.752012] ata6.00: failed to IDENTIFY (I/O error, err_mask=0x4)

***********************

[    0.755641] sd 1:0:0:0: [sda] Attached SCSI disk

[    1.020838] usb 1-1: new high-speed USB device number 2 using ehci-pci

[    1.135703] hub 1-1:1.0: USB hub found

[    1.135898] hub 1-1:1.0: 6 ports detected

[    1.238932] usb 2-1: new high-speed USB device number 2 using ehci-pci

[    1.310950] tsc: Refined TSC clocksource calibration: 3392.293 MHz

[    1.353800] hub 2-1:1.0: USB hub found

[    1.353999] hub 2-1:1.0: 8 ports detected

[    2.311646] Switched to clocksource tsc

[    5.751998] ata6.00: qc timeout (cmd 0xa1)

[    5.752012] ata6.00: failed to IDENTIFY (I/O error, err_mask=0x4)

[    6.312298] ata6: SATA link down (SStatus 0 SControl 300)

[    6.312309] ata6.00: link offline, clearing class 3 to NONE

[    6.312402] md: Waiting for all devices to be available before autodetect

[    6.312406] md: If you don't use raid, use raid=noautodetect

[    6.312687] md: Autodetecting RAID arrays.

[    6.312691] md: Scanned 0 and added 0 devices.

[    6.312693] md: autorun ...

[    6.312694] md: ... autorun DONE.

[    6.336030] kjournald starting.  Commit interval 5 seconds

[    6.336400] EXT3-fs (sda3): using internal journal



I am logging this error here to know if it is a real bug or something that needs to be whitelisted in the test's filters.
Comment 1 Nitin Kamble 2015-01-02 18:02:25 UTC
I am not able to reproduce this error on my sugarbay platform. This looks like related to the actual hardware issue on your platform.