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.


** Changed in: linux (Ubuntu)
       Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633776

Title:
  Crash due to SATA 3 issue in Skylake chip

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633776/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to