Follow up to

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Greetings,


I've been getting hot-add errors for a device on suspend/resume cycles
and the closest I've found to a resolution was a patch submitted to
this list:
- http://thread.gmane.org/gmane.linux.kernel/1834517

There's a kernel bug here where I've been trying to make headway but
thought I'd ping this list as it seemed relevant:
- https://bugzilla.kernel.org/show_bug.cgi?id=74471

The closest other reports I can find are here:
- https://bugs.archlinux.org/task/38486
- https://bbs.archlinux.org/viewtopic.php?pid=1314282#p1314282

This is on Arch linux.

$ uname -a
Linux 4.5.0-1-ARCH #1 SMP PREEMPT Tue Mar 15 09:41:03 CET 2016 x86_64 GNU/Linux


Example dmesg output:

$ dmesg |grep hot-add
[   43.105083] pciehp 0000:3d:03.0:pcie24: Device 0000:60:00.0 already
exists at 0000:60:00, cannot hot-add
[   43.208376] pciehp 0000:3d:03.0:pcie24: Device 0000:60:00.0 already
exists at 0000:60:00, cannot hot-add
[ 2223.875613] pciehp 0000:3d:03.0:pcie24: Device 0000:60:00.0 already
exists at 0000:60:00, cannot hot-add
[ 2223.982274] pciehp 0000:3d:03.0:pcie24: Device 0000:60:00.0 already
exists at 0000:60:00, cannot hot-add


Device info (let me know if -vv or -vvv is preferred)

$ sudo lspci -v
60:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd.
RTS5249 PCI Express Card Reader (rev 01)
Subsystem: Hewlett-Packard Company Device 2253
Physical Slot: 0-2
Flags: bus master, fast devsel, latency 0, IRQ 10
Memory at cc000000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Device Serial Number 00-00-00-01-00-4c-e0-00
Capabilities: [158] Latency Tolerance Reporting
Capabilities: [160] L1 PM Substates
Kernel modules: rtsx_pci

I noticed that on Arch the patch referenced above isn't applied, so
I'm not sure if it was ever integrated or not. I made the changes
contained in v2 manually, and am still experiencing the errors. That
said, they don't seem to affect anything noticeable other than showing
up when I move the mouse to disable xscreensaver (though that's gone
away recently).

If it's nothing to be concerned with, at the least I can add a comment
to kernel bug so that others who find it won't be worried. It'd be
nice to have an official resolution somewhere on the internet.


Thanks fo for taking a look,

John
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux