Bug 153171

Summary: scsi host6: runtime PM trying to activate child device host6 but parent (2-2:1.0) is not active
Product: IO/Storage Reporter: Cristian Aravena Romero (caravena)
Component: SCSIAssignee: linux-scsi (linux-scsi)
Status: NEW ---    
Severity: normal CC: chris.bainbridge, dev, mirh, mkp, regressions, smowerson
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: 4.8.0-040800rc2-lowlatency Subsystem:
Regression: No Bisected commit-id:
Attachments: dmesg_4.8.0-040800rc2-lowlatency
lspci -vvnn

Description Cristian Aravena Romero 2016-08-15 19:55:39 UTC
Created attachment 228931 [details]
dmesg_4.8.0-040800rc2-lowlatency

Mount USB Pendrive

dmesg:
[ 4630.693915] scsi host6: runtime PM trying to activate child device host6 but parent (2-2:1.0) is not active
Comment 1 Cristian Aravena Romero 2016-08-15 19:56:34 UTC
Created attachment 228941 [details]
lspci -vvnn
Comment 2 Martin K. Petersen 2016-08-19 02:17:59 UTC
>>>>> "Heiner" == Heiner Kallweit <hkallweit1@gmail.com> writes:

Heiner> This issue is fixed by patch scsi: "core: configure runtime pm
Heiner> before calling device_add in scsi_add_host_with_dma" I sent on
Heiner> Aug 3rd.

Severely lacking in the reviews department, though :(
Comment 3 Chris Bainbridge 2016-08-24 12:33:37 UTC
Error message present in 4.8.0-rc3
Error message disappears after applying fix https://patchwork.kernel.org/patch/9262149/ 
Would be good to merge the fix before 4.9.0 is released
Comment 4 The Linux kernel's regression tracker (Thorsten Leemhuis) 2016-09-11 11:43:06 UTC
(In reply to Martin K. Petersen from comment #2)
> Severely lacking in the reviews department, though :(
Martin, the reporter considers this a regression, but according to https://patchwork.kernel.org/patch/9262149/ you applied the fix to 4.9/scsi-queue – and it's not in mainline yet afaics. Was that an accident or do you think this is not serious enough and thus better dealt with in 4.9?
Comment 5 Martin K. Petersen 2016-09-14 17:03:19 UTC
I would like the change to get a bit of soak time before we backport it.
Comment 6 Christian Stadelmann 2016-10-02 18:27:23 UTC
I'm seeing the same dmesg output too, on 2 machines with 4.8.0 rc7 / rc8 kernels.

It seems like this bug is preventing me on these machines to use any USB thumb drives at all. In case anyone can confirm this I think it should go into 4.8.0 before release immediately.
Comment 7 Christian Stadelmann 2016-10-02 19:37:50 UTC
(In reply to Christian Stadelmann from comment #6)
> It seems like this bug is preventing me on these machines to use any USB
> thumb drives at all. In case anyone can confirm this I think it should go
> into 4.8.0 before release immediately.

Ok, I am not sure about this, there is a SELinux/Gnome issue involved and probably other stuff too. Manually mounting the device works fine. So no, this kernel issue is not preventing me from mounting the USB devices.
Comment 8 Cristian Aravena Romero 2016-10-02 22:45:17 UTC
*** Bug 175431 has been marked as a duplicate of this bug. ***
Comment 9 Christian Stadelmann 2016-10-04 12:06:52 UTC
(In reply to Christian Stadelmann from comment #6) 
> It seems like this bug is preventing me on these machines to use any USB
> thumb drives at all. In case anyone can confirm this I think it should go
> into 4.8.0 before release immediately.

Can somebody confirm or deny that this is preventing you from mounting any USB thumb drives?
Comment 10 Scott Mowerson 2016-10-18 10:18:27 UTC
This is preventing me from booting Ubuntu 16.10:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1631058?comments=all 

But I am not using a low-latency kernel.