Crash due to SATA 3 issue in Skylake chip

[ernest]

Minor bug - I have an annoying work around

ASRock Z170 Extreme7+ Mboard has 10 SATA 3 ports off 2 controller chips CPU is Skylake 6700. One SATA chip does 6 ports in pairs which also serve as either SATA Express or M.2 drive controllers. these are SATA 3-0 to SATA 3-5, other has 4 SATA ports. System worked in Win 7, but when booting to Kubuntu 16.10 it kept coming crashing during boot with an error of 'Unable to initiate SATA child Parent inactive.' I tried every possible combination, and eventually got the system to load by placing an Optical drive as SAT 3-0, and writing off one of the SATA Express links. Once I got it going I started adding drives back in one at a time, and hit the same problem when I got to the first SATA port on the 2nd chip, and optical drive plugged in there soon fixed that.

Another issue was I couldn't create an M.2 drive as the system drive while there was a hard drive connected to the system. Cut it back to just the optical and the M.2 and it let me use the M.2 as the system drive.

System now working with SATA 3-0 as optical, SATA 3-1 as 2TB HDD, SATA 3-2/3 as 500GB M.2, SATA 3 -4/5 as 500GB M.2, SATA 3A-0 as optical, SATA 3A-2 as 2TB HDD. Tested, as soon as I move an optical from the first SATA port for the chip I get the error message during the boot-up and it doesn't load. Switch back and it loads OK. I've a work around, but it costs me a SATA Express line. However, you may see others with Skylake chips havign the same issue.

I suspect it's an issue with the package checking the hardware during the boot-up, but don't know enough to say for sure.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1633776

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[ernest (ernest-bywater)]

G'day Brad,

I tried that and got an error message telling me I have to get and install 'python-apport' before it can be run. That being the case I'm not sure any logs from it will be of use. 1. Because it wasn't logging when the issue happened, and 2. because the problem was occurring before Kubuntu started to load. Also, because I've worked around the issue, I really don't want to introduce it again, just in case the work around was a fluke.

The first dozen or so times was before I could even get the Kubuntu DVD to load so I could install the OS. After I finally got it to load by fooling around with what was and wasn't connected to the system I did get it to load, and later had the same boot issue when I started connecting the drives back to the system, and I got the same error message until I got it to boot with the work around mentioned. The message was: 'trying to activate child device but parent is not active'

Checking the Kernel Log in KSystemlog I found this section, and think it may apply to the problem (but not sure):

17/10/2016 11:52 PM usb-storage 2-1.4 .0: USB Mass Storage device detected
17/10/2016 11:52 PM scsi host10 usb-storage 2-1.4:1.0
17/10/2016 11:52 PM scsi host10 runtime PM trying to activate child device host10 but parent (2-1.4:1.0) is not active
17/10/2016 11:52 PM usbcore registered new interface driver usb-storage
17/10/2016 11:52 PM usbcore registered new interface driver uas
17/10/2016 11:52 PM usb 1-3.3 new high-speed USB device number 6 using xhci_hcd
17/10/2016 11:52 PM usb 1-3.3 New USB device found, idVendor=058f, idProduct=6366
17/10/2016 11:52 PM usb 1-3.3 New USB device strings: Mfr=1, Product=2, SerialNumber=3
17/10/2016 11:52 PM usb 1-3.3 Product: Mass Storage Device
17/10/2016 11:52 PM usb 1-3.3 Manufacturer: Generic
17/10/2016 11:52 PM usb 1-3.3 SerialNumber: 058F0O1111B1
17/10/2016 11:52 PM usb-storage 1-3.3 .0: USB Mass Storage device detected
17/10/2016 11:52 PM scsi host11 usb-storage 1-3.3:1.0
17/10/2016 11:52 PM scsi host11 runtime PM trying to activate child device host11 but parent (1-3.3:1.0) is not active
17/10/2016 11:52 PM clocksource Switched to clocksource tsc
17/10/2016 11:52 PM usb 2-5.4 new SuperSpeed USB device number 5 using xhci_hcd
17/10/2016 11:52 PM usb 2-5.4 New USB device found, idVendor=174c, idProduct=55aa
17/10/2016 11:52 PM usb 2-5.4 New USB device strings: Mfr=2, Product=3, SerialNumber=1
17/10/2016 11:52 PM usb 2-5.4 Product: YLT-C00002
17/10/2016 11:52 PM usb 2-5.4 Manufacturer: ULT-Best
17/10/2016 11:52 PM usb 2-5.4 SerialNumber: 123456789069
17/10/2016 11:52 PM usb-storage 2-5.4 .0: USB Mass Storage device detected
17/10/2016 11:52 PM usb-storage 2-5.4 .0: Quirks match for vid 174c pid 55aa: 400000
17/10/2016 11:52 PM scsi host12 usb-storage 2-5.4:1.0
17/10/2016 11:52 PM scsi host12 runtime PM trying to activate child device host12 but parent (2-5.4:1.0) is not active

Having spent over 18 hours getting the system working the way I want it to I'm very hesitant to play with it too much, but will do anything I can to help track it down.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc1/

[ernest (ernest-bywater)]

G'day Joseph,

I've never done a kernel change before. Not even sure how many or which files from that page I should be downloading. Please confirm if I should be loading both of these files, or just one, or what else for a 64 bit build. Also please confirm I'll be able to recover back to the current set up if I want to. I'm concerned because of the hassles I had to get operational in the first place.

linux-headers-4.9.0-040900rc1-generic_4.9.0-040900rc1.201610151630_amd64.deb

linux-image-4.9.0-040900rc1-generic_4.9.0-040900rc1.201610151630_amd64.deb

Ernest

[ernest (ernest-bywater)]

G'day Joseph,

I forgot to add in my above comment that the error occurs BEFORE I get to the Boot Menu, and the instruction page for the mainstream kernels says I get a choice AT the boot menu. With that being the case, is this still like to provide any useful information?

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]