FS#38486 - [linux] 3.12: pciehp: cannot add device, already exists

Attached to Project: Arch Linux
Opened by Robert Orzanna (orschiro) - Monday, 13 January 2014, 13:10 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 02 October 2017, 13:10 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 5
Private No

Details

Description:

Currently, pciehp_resume will call pciehp_enable_slot() to add
device if there is a device in the slot. But if the device was
present before suspend, it's no necessary to add again. Now in
such case, there is some uncomfortable message like

Jan 13 13:59:04 thinkpad kernel: pciehp 0000:00:1c.1:pcie04: Device 0000:03:00.0 already exists at 0000:03:00, cannot hot-add
Jan 13 13:59:04 thinkpad kernel: pciehp 0000:00:1c.1:pcie04: Cannot add device at 0000:03:00

The discussion can be also found here: http://comments.gmane.org/gmane.linux.kernel.pci/19876

I am curious if the patch [1] can be integrated into the Arch Linux kernel

[1] http://us.generation-nt.com/patch-2-2-pci-pciehp-avoid-add-device-already-exist-during-pciehp-resume-help-211812872.html

Additional info:
* package version(s)
* config and/or log files etc.

3.12.7-1-ARCH

Steps to reproduce:

Resume from hibernation / suspension should show up the message in your journalctl logs.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Monday, 02 October 2017, 13:10 GMT
Reason for closing:  Fixed
Comment by Gerardo Exequiel Pozzi (djgera) - Thursday, 06 February 2014, 23:57 GMT
  • Field changed: Summary (pciehp: cannot add device, already exists → [linux] 3.12: pciehp: cannot add device, already exists)
  • Field changed: Status (Unconfirmed → Waiting on Response)
  • Field changed: Category (Packages: Core → Upstream Bugs)
  • Task assigned to Thomas Bächler (brain0), Tobias Powalowski (tpowa)
status with 3.13?
Comment by Robert Orzanna (orschiro) - Friday, 07 February 2014, 10:24 GMT
@Gerardo

I will let you know once 3.13 leaves testing. I am reluctant to install it from testing.

Can you provide more information on how it has potentially been fixed in 3.13?

Cheers

Robert
Comment by Robert Orzanna (orschiro) - Friday, 21 February 2014, 23:09 GMT
Error message still shows up with kernel 3.13

Feb 21 23:59:36 thinkpad kernel: pciehp 0000:00:1c.1:pcie04: Device 0000:03:00.0 already exists at 0000:03:00, cannot hot-add
Feb 21 23:59:36 thinkpad kernel: pciehp 0000:00:1c.1:pcie04: Cannot add device at 0000:03:00

~ uname -r
3.13.4-1-ARCH
Comment by mojtaba (mojtabazn) - Wednesday, 05 March 2014, 18:19 GMT
i have these errors too
pciehp 0000:00:1c.1:pcie04: Device 0000:03:00.0 already exists at 0000:03:00, cannot hot-add
Mar 05 21:30:13 mojtaba-n61jq kernel: pciehp 0000:00:1c.5:pcie04: Device 0000:08:00.0 already exists at 0000:08:00, cannot hot-add
Mar 05 21:30:13 mojtaba-n61jq kernel: pciehp 0000:00:1c.1:pcie04: Cannot add device at 0000:03:00
Mar 05 21:30:13 mojtaba-n61jq kernel: pciehp 0000:00:1c.5:pcie04: Cannot add device at 0000:08:00
Mar 05 21:30:13 mojtaba-n61jq kernel: pciehp 0000:00:1c.3:pcie04: Device 0000:07:00.0 already exists at 0000:07:00, cannot hot-add
Mar 05 21:30:13 mojtaba-n61jq kernel: pciehp 0000:00:1c.5:pcie04: Device 0000:08:00.0 already exists at 0000:08:00, cannot hot-add
Mar 05 21:30:13 mojtaba-n61jq kernel: pciehp 0000:00:1c.3:pcie04: Cannot add device at 0000:07:00
Mar 05 21:30:13 mojtaba-n61jq kernel: pciehp 0000:00:1c.5:pcie04: Cannot add device at 0000:08:00
Mar 05 21:30:13 mojtaba-n61jq kernel: pciehp 0000:00:1c.3:pcie04: Device 0000:07:00.0 already exists at 0000:07:00, cannot hot-add
Mar 05 21:30:13 mojtaba-n61jq kernel: pciehp 0000:00:1c.3:pcie04: Cannot add device at 0000:07:00
Mar 05 21:30:13 mojtaba-n61jq kernel: pciehp 0000:00:1c.1:pcie04: Device 0000:03:00.0 already exists at 0000:03:00, cannot hot-add
Mar 05 21:30:13 mojtaba-n61jq kernel: pciehp 0000:00:1c.1:pcie04: Cannot add device at 0000:03:00
3.13.5-1
Comment by Ivan Lyapunov (dront78) - Saturday, 29 March 2014, 06:02 GMT
the same here
[ 2510.943097] pciehp 0000:00:1c.1:pcie04: Device 0000:07:00.0 already exists at 0000:07:00, cannot hot-add
[ 2510.943171] pciehp 0000:00:1c.0:pcie04: Device 0000:02:00.0 already exists at 0000:02:00, cannot hot-add
[ 2510.943171] pciehp 0000:00:1c.4:pcie04: Device 0000:16:00.0 already exists at 0000:16:00, cannot hot-add
Comment by Schtiehve (schtiehve) - Thursday, 08 May 2014, 20:47 GMT
Same messages here
pciehp 0000:00:07.0:pcie04: Device 0000:04:00.0 already exists at 0000:04:00, cannot hot-add
pciehp 0000:00:07.0:pcie04: Cannot add device at 0000:04:00

also my Thinkpad Edge E135 sometimes Doesn't wake from suspend when it does it shows the message above.
Comment by Schtiehve (schtiehve) - Thursday, 08 May 2014, 22:08 GMT
Same messages here
pciehp 0000:00:07.0:pcie04: Device 0000:04:00.0 already exists at 0000:04:00, cannot hot-add
pciehp 0000:00:07.0:pcie04: Cannot add device at 0000:04:00

also my Thinkpad Edge E135 sometimes Doesn't wake from suspend when it does it shows the message above.
Comment by Tobias Powalowski (tpowa) - Wednesday, 13 August 2014, 07:03 GMT
Status on 3.16?
Comment by Ivan Lyapunov (dront78) - Friday, 15 August 2014, 13:40 GMT
Linux 3.16.1-1-ARCH #1 SMP PREEMPT Thu Aug 14 07:40:19 CEST 2014 x86_64 GNU/Linux
[ 84.696709] pciehp 0000:00:1c.0:pcie04: Device 0000:02:00.0 already exists at 0000:02:00, cannot hot-add
[ 84.696709] pciehp 0000:00:1c.0:pcie04: Cannot add device at 0000:02:00
[ 84.696724] pciehp 0000:00:1c.1:pcie04: Device 0000:07:00.0 already exists at 0000:07:00, cannot hot-add
[ 84.696724] pciehp 0000:00:1c.1:pcie04: Cannot add device at 0000:07:00
[ 84.696724] pciehp 0000:00:1c.4:pcie04: Device 0000:16:00.0 already exists at 0000:16:00, cannot hot-add
[ 84.696724] pciehp 0000:00:1c.4:pcie04: Cannot add device at 0000:16:00

may be this could help
[ 403.802171] sdhci-pci 0000:16:00.0: no hotplug settings from platform
[ 403.802171] pci 0000:16:00.2: no hotplug settings from platform
[ 403.802171] jmb38x_ms 0000:16:00.3: no hotplug settings from platform
[ 403.802171] pci 0000:16:00.4: no hotplug settings from platform


the messages appears both the same after standby and after hibernate
Comment by okto simaia (okto) - Tuesday, 26 August 2014, 23:35 GMT
Still having this problem, surprised such a giant bug hasn't been squashed yet.

Linux Rivet-Ball 3.16.1-1-ARCH #1 SMP PREEMPT Thu Aug 14 07:48:39 CEST 2014 i686 GNU/Linux
Comment by Robert Orzanna (orschiro) - Wednesday, 27 August 2014, 06:20 GMT
Can confirm. Same error message also on 3.16.1-1-ARCH.
Comment by david ta (dataP) - Tuesday, 02 December 2014, 20:55 GMT
Same here on my laptop, when I woke up, I need to reboot to use my sd card reader.

[ 1124.311784] pciehp 0000:00:1c.1:pcie04: Device 0000:05:00.0 already exists at 0000:05:00, cannot hot-add
[ 1124.311785] pciehp 0000:00:1c.1:pcie04: Cannot add device at 0000:05:00
[ 1124.411747] dpm_run_callback(): pci_pm_resume+0x0/0xb0 returns -110
[ 1124.411749] PM: Device 0000:05:00.0 failed to resume async: error -110

3.17.4-1-ARCH #1 SMP PREEMPT Fri Nov 21 21:14:42 CET 2014 x86_64 GNU/Linux
Comment by Francis Herne (FLHerne) - Monday, 29 December 2014, 01:38 GMT
Still occurs for me with 3.18.1
Comment by Mohit (mohit310) - Saturday, 17 January 2015, 00:42 GMT
I'm having the same issue with nouveau with 3.18.1


Jan 16 19:27:00 mk-asus kernel: firewire_core 0000:07:01.0: rediscovered device fw0
Jan 16 19:27:00 mk-asus kernel: pciehp 0000:00:01.0:pcie04: Device 0000:01:00.0 already exists at 0000:01:00, cannot hot-add
Jan 16 19:27:00 mk-asus kernel: pciehp 0000:00:01.0:pcie04: Cannot add device at 0000:01:00
Jan 16 19:27:00 mk-asus kernel: nouveau [ DRM] re-enabling device...
Jan 16 19:27:00 mk-asus kernel: nouveau [ DRM] resuming kernel object tree...
Jan 16 19:27:00 mk-asus kernel: rtc_cmos 00:01: System wakeup disabled by ACPI
Jan 16 19:27:00 mk-asus kernel: nouveau [ VBIOS][0000:01:00.0] running init tables
Jan 16 19:27:00 mk-asus kernel: ite-cir 00:06: activated
Jan 16 19:27:00 mk-asus kernel: nouveau [ VOLT][0000:01:00.0] GPU voltage: 1050000uv
Jan 16 19:27:00 mk-asus kernel: nouveau [ PTHERM][0000:01:00.0] fan management: automatic
Jan 16 19:27:00 mk-asus kernel: nouveau [ CLK][0000:01:00.0] --: core 275 MHz shader 550 MHz memory 300 MHz
Jan 16 19:27:00 mk-asus kernel: nouveau [ DRM] resuming client object trees...
Jan 16 19:27:00 mk-asus kernel: nouveau [ DRM] resuming display...
Jan 16 19:27:00 mk-asus kernel: nouveau [ DRM] resuming console...
Jan 16 19:27:00 mk-asus kernel: PM: resume of devices complete after 1678.910 msecs
Jan 16 19:27:00 mk-asus kernel: PM: Finishing wakeup.
Jan 16 19:27:00 mk-asus rtkit-daemon[411]: The canary thread is apparently starving. Taking action.
Jan 16 19:27:00 mk-asus rtkit-daemon[411]: Demoting known real-time threads.
Jan 16 19:27:00 mk-asus rtkit-daemon[411]: Successfully demoted thread 418 of process 410 (/usr/bin/pulseaudio).
Jan 16 19:27:00 mk-asus rtkit-daemon[411]: Successfully demoted thread 416 of process 410 (/usr/bin/pulseaudio).
Jan 16 19:27:00 mk-asus rtkit-daemon[411]: Successfully demoted thread 410 of process 410 (/usr/bin/pulseaudio).
Jan 16 19:27:00 mk-asus rtkit-daemon[411]: Demoted 3 threads.
Jan 16 19:27:00 mk-asus systemd-logind[237]: Lid opened.
Jan 16 19:27:00 mk-asus systemd-sleep[590]: System resumed.
-- Subject: System sleep state suspend left
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The system has now left the suspend sleep state.
Jan 16 19:27:00 mk-asus systemd-logind[237]: Operation finished.
Jan 16 19:27:01 mk-asus kernel: Restarting tasks ... done.
Jan 16 19:27:01 mk-asus kernel: sdhci-pci 0000:07:01.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jan 16 19:27:01 mk-asus kernel: sdhci-pci 0000:07:01.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jan 16 19:27:01 mk-asus kernel: sdhci-pci 0000:07:01.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jan 16 19:27:00 mk-asus NetworkManager[236]: <info> wake requested (sleeping: yes enabled: yes)
Jan 16 19:27:00 mk-asus NetworkManager[236]: <info> waking up...
Jan 16 19:27:00 mk-asus NetworkManager[236]: <info> (enp6s0): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
Jan 16 19:27:01 mk-asus kernel: sdhci-pci 0000:07:01.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jan 16 19:27:02 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH TLB flush idle timeout fail
Jan 16 19:27:02 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_STATUS : 0x01000001 BUSY ROP
Jan 16 19:27:02 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS0: 0x00000000
Jan 16 19:27:02 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS1: 0x00000000
Jan 16 19:27:02 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS2: 0x00200000 ROP
Jan 16 19:27:04 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH TLB flush idle timeout fail
Jan 16 19:27:04 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_STATUS : 0x01000001 BUSY ROP
Jan 16 19:27:04 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS0: 0x00000000
Jan 16 19:27:04 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS1: 0x00000000
Jan 16 19:27:04 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS2: 0x00200000 ROP
Jan 16 19:27:04 mk-asus kernel: IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jan 16 19:27:04 mk-asus NetworkManager[236]: <info> (enp6s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jan 16 19:27:06 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH TLB flush idle timeout fail
Jan 16 19:27:06 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_STATUS : 0x01000001 BUSY ROP
Jan 16 19:27:06 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS0: 0x00000000
Jan 16 19:27:06 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS1: 0x00000000
Jan 16 19:27:06 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS2: 0x00200000 ROP
Jan 16 19:27:06 mk-asus kernel: sched: RT throttling activated
Jan 16 19:27:06 mk-asus NetworkManager[236]: <info> (enp6s0): preparing device
Jan 16 19:27:06 mk-asus NetworkManager[236]: <info> (wlp3s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jan 16 19:27:06 mk-asus kernel: r8169 0000:06:00.0 enp6s0: link down
Jan 16 19:27:06 mk-asus kernel: iwlwifi 0000:03:00.0: L1 Disabled - LTR Disabled
Jan 16 19:27:06 mk-asus kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Jan 16 19:27:08 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH TLB flush idle timeout fail
Jan 16 19:27:08 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_STATUS : 0x01000001 BUSY ROP
Jan 16 19:27:08 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS0: 0x00000000
Jan 16 19:27:08 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS1: 0x00000000
Jan 16 19:27:08 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS2: 0x00200000 ROP
Jan 16 19:27:08 mk-asus NetworkManager[236]: <info> (wlp3s0): preparing device
Jan 16 19:27:08 mk-asus NetworkManager[236]: <info> NetworkManager state is now DISCONNECTED
Jan 16 19:27:10 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH TLB flush idle timeout fail
Jan 16 19:27:12 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_STATUS : 0x01000001 BUSY ROP
Jan 16 19:27:12 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS0: 0x00000000
Jan 16 19:27:12 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS1: 0x00000000
Jan 16 19:27:12 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS2: 0x00200000 ROP
Jan 16 19:27:12 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH TLB flush idle timeout fail
Jan 16 19:27:12 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_STATUS : 0x01000001 BUSY ROP
Jan 16 19:27:12 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS0: 0x00000000
Jan 16 19:27:12 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS1: 0x00000000
Jan 16 19:27:12 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS2: 0x00200000 ROP
Jan 16 19:27:14 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH TLB flush idle timeout fail
Jan 16 19:27:14 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_STATUS : 0x01000001 BUSY ROP
Jan 16 19:27:14 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS0: 0x00000000
Jan 16 19:27:14 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS1: 0x00000000
Jan 16 19:27:14 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS2: 0x00200000 ROP
Jan 16 19:27:16 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH TLB flush idle timeout fail
Jan 16 19:27:16 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_STATUS : 0x01000001 BUSY ROP
Jan 16 19:27:16 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS0: 0x00000000
Jan 16 19:27:16 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS1: 0x00000000
Jan 16 19:27:16 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS2: 0x00200000 ROP
Jan 16 19:27:18 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH TLB flush idle timeout fail
Jan 16 19:27:18 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_STATUS : 0x01000001 BUSY ROP
Jan 16 19:27:18 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS0: 0x00000000
Jan 16 19:27:18 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS1: 0x00000000
Jan 16 19:27:18 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS2: 0x00200000 ROP
Jan 16 19:27:20 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH TLB flush idle timeout fail
Jan 16 19:27:20 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_STATUS : 0x01000001 BUSY ROP
Jan 16 19:27:20 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS0: 0x00000000
Jan 16 19:27:20 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS1: 0x00000000
Jan 16 19:27:20 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS2: 0x00200000 ROP
Jan 16 19:27:22 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH TLB flush idle timeout fail
Jan 16 19:27:22 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_STATUS : 0x01000001 BUSY ROP
Jan 16 19:27:22 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS0: 0x00000000
Jan 16 19:27:22 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS1: 0x00000000
Jan 16 19:27:22 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS2: 0x00200000 ROP
Jan 16 19:27:24 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH TLB flush idle timeout fail
Jan 16 19:27:24 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_STATUS : 0x01000001 BUSY ROP
Jan 16 19:27:24 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS0: 0x00000000
Jan 16 19:27:24 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS1: 0x00000000
Jan 16 19:27:24 mk-asus kernel: nouveau E[ PGRAPH][0000:01:00.0] PGRAPH_VSTATUS2: 0x00200000 ROP

Comment by Hussam Al-Tayeb (hussam) - Friday, 15 July 2016, 20:48 GMT
The second patch in https://bugzilla.kernel.org/show_bug.cgi?id=74471 fixes this issue for me and I have posted asking if the author plans on merging it upstream at some point.
Comment by mattia (nTia89) - Sunday, 01 October 2017, 15:34 GMT
is this issue still valid?
Comment by Robert Orzanna (orschiro) - Monday, 02 October 2017, 12:16 GMT
I cannot reproduce it anymore.
Comment by Hussam Al-Tayeb (hussam) - Monday, 02 October 2017, 12:57 GMT
It could be hardware specific. I stopped seeing it when I got a new computer earlier this year and moved the hard disks without upgrading the kernel.

Loading...