Created attachment 950763 [details] dmesg log Description of problem: kernel log attached Version-Release number of selected component (if applicable): 3.18.0-0.rc1.git2.2.fc22.1.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
somebody? anybody? this is pretty severe and.. irritating having to reboot every time after resume. I quite sure 3.17 kernels were ok. thanks
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
[28541.439927] r8169 0000:01:00.0: can't disable ASPM; OS doesn't have ASPM control [28541.495281] r8169 0000:01:00.0 eth0: RTL8168ep/8111ep at 0xffffc9000002a000, 14:58:d0:ba:fa:6a, XID 10200880 IRQ 49 [28541.495290] r8169 0000:01:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] [28541.507740] r8169 0000:01:00.0 enp1s0f0: renamed from eth0 [28541.532559] IPv6: ADDRCONF(NETDEV_UP): enp1s0f0: link is not ready [28541.590251] IPv6: ADDRCONF(NETDEV_UP): enp1s0f0: link is not ready [28542.736847] IPv6: ADDRCONF(NETDEV_UP): enp1s0f0: link is not ready [28542.797221] IPv6: ADDRCONF(NETDEV_UP): enp1s0f0: link is not ready [28545.667265] IPv6: ADDRCONF(NETDEV_CHANGE): enp1s0f0: link becomes ready [28687.180860] systemd-sysv-generator[8938]: Overwriting existing symlink /run/systemd/generator.late/netconsole.service with real service [28687.181235] systemd-sysv-generator[8938]: Overwriting existing symlink /run/systemd/generator.late/network.service with real service [28688.761060] systemd-sysv-generator[8962]: Overwriting existing symlink /run/systemd/generator.late/network.service with real service [28688.761177] systemd-sysv-generator[8962]: Overwriting existing symlink /run/systemd/generator.late/netconsole.service with real service [33248.123396] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x001d address=0x00000000035aa000 flags=0x0050]
hi devel, a few kernels after (4.3.0-0.rc0.git6.2.fc24.x86_64) and problem is still here. I've also reported similar(the same?) here: https://bugzilla.redhat.com/show_bug.cgi?id=1161484 is it not realtek driver? [17085.217490] xhci_hcd 0000:00:10.0: System wakeup disabled by ACPI [17085.217647] PM: noirq resume of devices complete after 12.177 msecs [17085.218244] PM: early resume of devices complete after 0.531 msecs [17085.219221] r8169 0000:01:00.0: System wakeup disabled by ACPI [17085.227486] sd 0:0:0:0: [sda] Starting disk [17085.228609] [drm] PCIE GART of 2048M enabled (table at 0x0000000000324000). [17085.228779] radeon 0000:00:01.0: WB enabled [17085.228786] radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff8804279e2c00 [17085.228789] radeon 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0xffff8804279e2c04 [17085.228792] radeon 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0xffff8804279e2c08 [17085.228795] radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff8804279e2c0c [17085.228797] radeon 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0xffff8804279e2c10 [17085.229442] radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000076c98 and cpu addr 0xffffc90002036c98 [17085.229763] radeon 0000:00:01.0: fence driver on ring 6 use gpu addr 0x0000000040000c18 and cpu addr 0xffff8804279e2c18 [17085.229765] radeon 0000:00:01.0: fence driver on ring 7 use gpu addr 0x0000000040000c1c and cpu addr 0xffff8804279e2c1c [17085.231341] [drm] ring test on 0 succeeded in 4 usecs [17085.231429] [drm] ring test on 1 succeeded in 3 usecs [17085.231444] [drm] ring test on 2 succeeded in 3 usecs [17085.231628] [drm] ring test on 3 succeeded in 4 usecs [17085.231636] [drm] ring test on 4 succeeded in 4 usecs [17085.277509] r8169 0000:01:00.0 enp1s0f0: link down [17085.277857] [drm] ring test on 5 succeeded in 2 usecs [17085.297902] [drm] UVD initialized successfully. [17085.318860] pciehp 0000:00:03.2:pcie04: Device 0000:02:00.0 already exists at 0000:02:00, cannot hot-add [17085.318864] pciehp 0000:00:03.2:pcie04: Cannot add device at 0000:02:00 [17085.319824] pciehp 0000:00:03.3:pcie04: Device 0000:03:00.0 already exists at 0000:03:00, cannot hot-add [17085.319828] pciehp 0000:00:03.3:pcie04: Cannot add device at 0000:03:00 [17085.320148] rtc_cmos 00:03: System wakeup disabled by ACPI [17085.408065] [drm] ring test on 6 succeeded in 10 usecs [17085.408076] [drm] ring test on 7 succeeded in 3 usecs [17085.408077] [drm] VCE initialized successfully. [17085.408259] [drm] ib test on ring 0 succeeded in 0 usecs [17085.443015] usb 5-5: reset high-speed USB device number 2 using ehci-pci [17085.685284] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [17085.685783] ata1.00: supports DRM functions and may not be fully accessible [17085.689846] ata1.00: disabling queued TRIM support [17085.695002] ata1.00: supports DRM functions and may not be fully accessible [17085.699197] ata1.00: disabling queued TRIM support [17085.703860] ata1.00: configured for UDMA/133 [17085.704023] ata1.00: Enabling discard_zeroes_data [17085.909643] [drm] ib test on ring 1 succeeded in 0 usecs [17086.411003] [drm] ib test on ring 2 succeeded in 0 usecs [17086.411322] [drm] ib test on ring 3 succeeded in 0 usecs [17086.411596] [drm] ib test on ring 4 succeeded in 0 usecs [17086.841476] psmouse serio3: synaptics: queried max coordinates: x [..5672], y [..4764] [17086.878773] psmouse serio3: synaptics: queried min coordinates: x [1360..], y [1160..] [17086.932528] [drm] ib test on ring 5 succeeded [17086.953467] [drm] ib test on ring 6 succeeded [17086.954256] [drm] ib test on ring 7 succeeded [17088.960249] r8169 0000:01:00.0 enp1s0f0: link up [17089.098952] ERROR @wl_wowl_ind_wake_reason : Unable to get wake reason, err = -95 [17089.098994] PM: resume of devices complete after 3877.160 msecs [17089.099811] PM: Finishing wakeup. [17089.099813] Restarting tasks ... [17089.100011] pci 0000:00:14.4: PCI bridge to [bus 04] [17089.100110] pci 0000:00:14.4: PCI bridge to [bus 04] [17089.100161] pci 0000:00:14.4: PCI bridge to [bus 04] [17089.101054] pci 0000:00:14.4: PCI bridge to [bus 04] (subtractive decode) [17089.101071] pci 0000:00:14.4: bridge window [io 0x0000-0x0cf7 window] (subtractive decode) [17089.101074] pci 0000:00:14.4: bridge window [io 0x0d00-0xffff window] (subtractive decode) [17089.101078] pci 0000:00:14.4: bridge window [mem 0x000a0000-0x000bffff window] (subtractive decode) [17089.101081] pci 0000:00:14.4: bridge window [mem 0x000c0000-0x000c3fff window] (subtractive decode) [17089.101084] pci 0000:00:14.4: bridge window [mem 0x000c4000-0x000c7fff window] (subtractive decode) [17089.101087] pci 0000:00:14.4: bridge window [mem 0x000c8000-0x000cbfff window] (subtractive decode) [17089.101090] pci 0000:00:14.4: bridge window [mem 0x000d0000-0x000d3fff window] (subtractive decode) [17089.101093] pci 0000:00:14.4: bridge window [mem 0x000d4000-0x000d7fff window] (subtractive decode) [17089.101096] pci 0000:00:14.4: bridge window [mem 0x000d8000-0x000dbfff window] (subtractive decode) [17089.101099] pci 0000:00:14.4: bridge window [mem 0x000dc000-0x000dffff window] (subtractive decode) [17089.101102] pci 0000:00:14.4: bridge window [mem 0x000e0000-0x000e3fff window] (subtractive decode) [17089.101105] pci 0000:00:14.4: bridge window [mem 0x000e4000-0x000e7fff window] (subtractive decode) [17089.101109] pci 0000:00:14.4: bridge window [mem 0x000e8000-0x000ebfff window] (subtractive decode) [17089.101112] pci 0000:00:14.4: bridge window [mem 0x000ec000-0x000effff window] (subtractive decode) [17089.101114] pci 0000:00:14.4: bridge window [mem 0x000f0000-0x000fffff window] (subtractive decode) [17089.101117] pci 0000:00:14.4: bridge window [mem 0xc0000000-0xdfffffff window] (subtractive decode) [17089.101120] pci 0000:00:14.4: bridge window [mem 0xf0000000-0xfed3ffff window] (subtractive decode) [17089.101123] pci 0000:00:14.4: bridge window [mem 0xfed45000-0xfffdffff window] (subtractive decode) [17089.101230] pci_bus 0000:04: Allocating resources [17089.101243] pci 0000:00:14.4: PCI bridge to [bus 04] [17089.101383] pci 0000:00:14.4: PCI bridge to [bus 04] [17089.101459] pci 0000:00:14.4: PCI bridge to [bus 04] [17089.104564] pci 0000:00:14.4: PCI bridge to [bus 04] [17089.104706] pci 0000:00:14.4: PCI bridge to [bus 04] [17089.104832] pci 0000:00:14.4: PCI bridge to [bus 04] [17089.110227] done. [17089.197119] IPv6: ADDRCONF(NETDEV_UP): enp1s0f0: link is not ready [17089.222623] IPv6: ADDRCONF(NETDEV_UP): enp1s0f0: link is not ready [17089.280102] r8169 0000:01:00.0 enp1s0f0: link down [17089.280108] r8169 0000:01:00.0 enp1s0f0: link down [17089.280242] IPv6: ADDRCONF(NETDEV_UP): enp1s0f0: link is not ready [17089.284921] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready [17089.366807] AMD-Vi: Event logged [INVALID_DEVICE_REQUEST device=00:00.1 address=0x000000fdf80c0020 flags=0x0a00] [17092.992647] r8169 0000:01:00.0 enp1s0f0: link up [17092.992668] IPv6: ADDRCONF(NETDEV_CHANGE): enp1s0f0: link becomes ready
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 22 kernel bugs. Fedora 22 has now been rebased to 4.2.3-200.fc22. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 23, and are still experiencing this issue, please change the version to Fedora 23. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.