[Bug 1631058] Re: scsi host6: runtime PM trying to activate child device host6 but parent (3-3:1.0) is not active

2016-10-17 Thread vmc
*** This bug is a duplicate of bug 1629714 *** https://bugs.launchpad.net/bugs/1629714 ** This bug has been marked a duplicate of bug 1629714 scsi host6: runtime PM trying to activate child device host6 but parent (3-1:1.0) is not active -- You received this bug notification because you

[Bug 1631058] Re: scsi host6: runtime PM trying to activate child device host6 but parent (3-3:1.0) is not active

2016-10-17 Thread scott mowerson
I am not running the low latency kernel, just generic kernel. I was successfully using both AMD CPU (proprietary driver) AND the NVIDIA proprietary driver. I tried tweaking the UEFI settings, but made things worse. So I switched the settings back. -- You received this bug notification because

[Bug 1631058] Re: scsi host6: runtime PM trying to activate child device host6 but parent (3-3:1.0) is not active

2016-10-17 Thread scott mowerson
I have this problem as well. Was already running 16.10 Development branch successfully, I think that when 16.10 was released that the next sudo apt update / upgrade changed something. I started getting errors that updates needed to be applied, but some lock file was read-only; then whole screen

[Bug 1631058] Re: scsi host6: runtime PM trying to activate child device host6 but parent (3-3:1.0) is not active

2016-10-14 Thread Vijay
I have a similar problem: I cannot even boot my computer(Thinkpad X220) from a live usb of 16.10. See this screenshot: http://imgur.com/a/nITS0 Apologies for the screen glare. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1631058] Re: scsi host6: runtime PM trying to activate child device host6 but parent (3-3:1.0) is not active

2016-10-12 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.8 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