You are not logged in.

#1 2017-05-27 11:32:56

DevilDust
Member
Registered: 2017-05-27
Posts: 9

RTNL: assertion failed

I am getting the messages:

RTNL: assertion failed at net/core/dev.c (2325)
RTNL: assertion failed at net/core/dev.c (2367)

Every time I try to hibernate, it hangs with these messages and I am forced to turn the PC off manually. When I turn the PC on again, it successfully restores from hibernate.

I also get theses messages sometimes when I put the PC to sleep and wake it up. But this does not happen often. In this case, I am forced to reboot the machine and lose my saved session.

I tried looking for solutions to this problem but I cannot find any good sources of help.

This is contained in the output of dmesg:

[  279.770283] RTNL: assertion failed at net/core/dev.c (2325)
[  279.770285] CPU: 1 PID: 119 Comm: kworker/u8:7 Tainted: P           O    4.11.2-1-ARCH #1
[  279.770286] Hardware name: Gigabyte Technology Co., Ltd. Z97X-Gaming 5/Z97X-Gaming 5, BIOS F5 05/30/2014
[  279.770291] Workqueue: events_unbound async_run_entry_fn
[  279.770292] Call Trace:
[  279.770297]  dump_stack+0x63/0x81
[  279.770299]  netif_set_real_num_tx_queues+0x111/0x1b0
[  279.770302]  __alx_open+0x1b4/0x4b0 [alx]
[  279.770305]  alx_resume+0x3d/0x40 [alx]
[  279.770307]  pci_pm_restore+0x7a/0xb0
[  279.770308]  ? pci_pm_suspend_noirq+0x190/0x190
[  279.770311]  dpm_run_callback+0x53/0x180
[  279.770312]  device_resume+0xe1/0x200
[  279.770314]  async_resume+0x1d/0x50
[  279.770316]  async_run_entry_fn+0x37/0x150
[  279.770319]  process_one_work+0x1e0/0x490
[  279.770321]  worker_thread+0x48/0x4e0
[  279.770323]  kthread+0x125/0x140
[  279.770325]  ? process_one_work+0x490/0x490
[  279.770326]  ? kthread_create_on_node+0x70/0x70
[  279.770328]  ret_from_fork+0x2c/0x40
[  279.770330] RTNL: assertion failed at net/core/dev.c (2367)
[  279.770331] CPU: 1 PID: 119 Comm: kworker/u8:7 Tainted: P           O    4.11.2-1-ARCH #1
[  279.770332] Hardware name: Gigabyte Technology Co., Ltd. Z97X-Gaming 5/Z97X-Gaming 5, BIOS F5 05/30/2014
[  279.770334] Workqueue: events_unbound async_run_entry_fn
[  279.770334] Call Trace:
[  279.770335]  dump_stack+0x63/0x81
[  279.770337]  netif_set_real_num_rx_queues+0x78/0x80
[  279.770339]  __alx_open+0x1c2/0x4b0 [alx]
[  279.770341]  alx_resume+0x3d/0x40 [alx]
[  279.770342]  pci_pm_restore+0x7a/0xb0
[  279.770343]  ? pci_pm_suspend_noirq+0x190/0x190
[  279.770345]  dpm_run_callback+0x53/0x180
[  279.770346]  device_resume+0xe1/0x200
[  279.770348]  async_resume+0x1d/0x50
[  279.770350]  async_run_entry_fn+0x37/0x150
[  279.770352]  process_one_work+0x1e0/0x490
[  279.770354]  worker_thread+0x48/0x4e0
[  279.770355]  kthread+0x125/0x140
[  279.770357]  ? process_one_work+0x490/0x490
[  279.770358]  ? kthread_create_on_node+0x70/0x70
[  279.770360]  ret_from_fork+0x2c/0x40

Last edited by DevilDust (2017-05-27 13:19:12)

Offline

#2 2017-05-27 13:15:18

loqs
Member
Registered: 2014-03-06
Posts: 17,199

Re: RTNL: assertion failed

Please use code tags for output rather than quote tags.  Is this a new issue that started after some upgrade or has it always been present?

Offline

#3 2017-05-27 13:23:23

DevilDust
Member
Registered: 2017-05-27
Posts: 9

Re: RTNL: assertion failed

As far as I'm aware, it's always been present.

Offline

#4 2017-05-27 13:31:03

loqs
Member
Registered: 2014-03-06
Posts: 17,199

Re: RTNL: assertion failed

What is the oldest kernel version you have used on the system?  ( to determine how long the issue has been present for in the kernel )
Edit:
If you unload the alx kernel module before hibernation does it hibernate correctly?

Last edited by loqs (2017-05-27 13:35:36)

Offline

#5 2017-05-27 16:32:25

DevilDust
Member
Registered: 2017-05-27
Posts: 9

Re: RTNL: assertion failed

upgraded linux (4.10.6-1 -> 4.10.8-1)
upgraded linux (4.10.8-1 -> 4.10.9-1)
upgraded linux (4.10.9-1 -> 4.10.10-1)
upgraded linux (4.10.10-1 -> 4.10.11-1)
upgraded linux (4.10.11-1 -> 4.10.13-1)
upgraded linux-firmware (20170309.695f2d6-1 -> 20170422.ade8332-1)
upgraded linux (4.10.13-1 -> 4.11.2-1)

Unloading alx makes no difference.

Offline

#6 2017-05-27 16:44:28

loqs
Member
Registered: 2014-03-06
Posts: 17,199

Re: RTNL: assertion failed

Does the dmesg output change if alx was not loaded when you hibernate?
Edit:
All the kernels with the issue have been 4.10 and 4.11 series can you try the linux-lts package which is currently on the 4.9 series.

Last edited by loqs (2017-05-27 16:46:16)

Offline

#7 2017-05-27 20:23:17

DevilDust
Member
Registered: 2017-05-27
Posts: 9

Re: RTNL: assertion failed

The dmesg output does change; the messages are not longer there.

I tried using linux-lts. The messages no longer appear but it just hangs with

[    OK    ] Reached target Swap.

at which point I have to manually turn off the PC.

Last edited by DevilDust (2017-05-28 00:33:44)

Offline

#8 2017-05-28 00:34:25

loqs
Member
Registered: 2014-03-06
Posts: 17,199

Re: RTNL: assertion failed

DevilDust wrote:

The dmesg output does change; the messages are not longer there.

That would indicate to me the alx module is not the cause of the issue unfortunately that was also the only lead I could find from the dmesg.
Could you post the journal contents showing what is logged between hibernate being requested and the system hibernating.

Offline

#9 2017-05-28 00:53:02

DevilDust
Member
Registered: 2017-05-27
Posts: 9

Re: RTNL: assertion failed

Here is the journal:

May 28 01:49:04 main org_kde_powerdevil[627]: powerdevil: Suspend session triggered with QMap(("Explicit", QVariant(bool, true))("Type", QVariant(uint, 2)))
May 28 01:49:04 main org_kde_powerdevil[627]: powerdevil: Suspend session triggered with QMap(("Explicit", QVariant(bool, true))("SkipFade", QVariant(bool, true))("Type", QVariant(uint, 2)))
May 28 01:49:04 main org_kde_powerdevil[627]: powerdevil: Starting Login1 suspend job
May 28 01:49:04 main kdeinit5[564]: bluedevil: About to suspend
May 28 01:49:04 main ksmserver[584]: lock called
May 28 01:49:04 main ksmserver[584]: Lock window Id:  20971526
May 28 01:49:04 main ksmserver[584]: CreateNotify: 20971526
May 28 01:49:04 main ksmserver[584]: CreateNotify: 20971528
May 28 01:49:04 main ksmserver[584]: UnmapNotify: 20971526
May 28 01:49:04 main ksmserver[584]: Error loading text-to-speech plug-in "flite"
May 28 01:49:04 main ksmserver[584]: CreateNotify: 125829123
May 28 01:49:04 main ksmserver[584]: CreateNotify: 125829126
May 28 01:49:04 main ksmserver[584]: CreateNotify: 125829128
May 28 01:49:04 main ksmserver[584]: CreateNotify: 125829130
May 28 01:49:04 main ksmserver[584]: CreateNotify: 125829132
May 28 01:49:04 main ksmserver[584]: MapNotify: 125829130
May 28 01:49:04 main ksmserver[584]: MapNotify: 20971526
May 28 01:49:04 main ksmserver[584]: CreateNotify: 125829134
May 28 01:49:04 main systemd[1]: Reached target Sleep.
May 28 01:49:04 main kernel: PM: Hibernation mode set to 'platform'
May 28 01:49:04 main systemd[1]: Starting Hibernate...
May 28 01:49:04 main systemd-sleep[2206]: Suspending system...
May 28 01:49:04 main org_kde_powerdevil[627]: powerdevil: ACTIVE SESSION PATH CHANGED: "/"
May 28 01:49:04 main org_kde_powerdevil[627]: powerdevil: Switched to inactive session - leaving unchanged
May 28 01:49:04 main kernel: PM: Syncing filesystems ... 
May 28 01:50:06 main kernel: PM: done.
May 28 01:50:06 main kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
May 28 01:50:06 main kernel: PM: Marking nosave pages: [mem 0x00000000-0x00000fff]
May 28 01:50:06 main kernel: PM: Marking nosave pages: [mem 0x00058000-0x00058fff]
May 28 01:50:06 main kernel: PM: Marking nosave pages: [mem 0x0009f000-0x000fffff]
May 28 01:50:06 main kernel: PM: Marking nosave pages: [mem 0xbd49e000-0xbd49efff]
May 28 01:50:06 main kernel: PM: Marking nosave pages: [mem 0xbd4ad000-0xbd4aefff]
May 28 01:50:06 main kernel: PM: Marking nosave pages: [mem 0xbd4cf000-0xbd4cffff]
May 28 01:50:06 main kernel: PM: Marking nosave pages: [mem 0xbe565000-0xbe56bfff]
May 28 01:50:06 main kernel: PM: Marking nosave pages: [mem 0xbf01f000-0xbf516fff]
May 28 01:50:06 main kernel: PM: Marking nosave pages: [mem 0xdcc0c000-0xdcc74fff]
May 28 01:50:06 main kernel: PM: Marking nosave pages: [mem 0xdccd8000-0xdeffefff]
May 28 01:50:06 main kernel: PM: Marking nosave pages: [mem 0xdf000000-0xffffffff]
May 28 01:50:06 main kernel: PM: Basic memory bitmaps created
May 28 01:50:06 main kernel: PM: Preallocating image memory... done (allocated 804480 pages)
May 28 01:50:06 main kernel: PM: Allocated 3217920 kbytes in 0.54 seconds (5959.11 MB/s)
May 28 01:50:06 main kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
May 28 01:50:06 main kernel: Suspending console(s) (use no_console_suspend to debug)
May 28 01:50:06 main kernel: serial 00:05: disabled
May 28 01:50:06 main kernel: PM: freeze of devices complete after 74.328 msecs
May 28 01:50:06 main kernel: PM: late freeze of devices complete after 0.325 msecs
May 28 01:50:06 main kernel: PM: noirq freeze of devices complete after 0.447 msecs
May 28 01:50:06 main kernel: ACPI: Preparing to enter system sleep state S4
May 28 01:50:06 main kernel: PM: Saving platform NVS memory
May 28 01:50:06 main kernel: Disabling non-boot CPUs ...
May 28 01:50:06 main kernel: smpboot: CPU 1 is now offline
May 28 01:50:06 main kernel: smpboot: CPU 2 is now offline
May 28 01:50:06 main kernel: smpboot: CPU 3 is now offline
May 28 01:50:06 main kernel: PM: Creating hibernation image:
May 28 01:50:06 main kernel: PM: Need to copy 799838 pages
May 28 01:50:06 main kernel: PM: Normal pages needed: 799838 + 1024, available pages: 1278493
May 28 01:50:06 main kernel: PM: Restoring platform NVS memory
May 28 01:50:06 main kernel: Suspended for 59.365 seconds
May 28 01:50:06 main kernel: Enabling non-boot CPUs ...
May 28 01:50:06 main kernel: x86: Booting SMP configuration:
May 28 01:50:06 main kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
May 28 01:50:06 main kernel:  cache: parent cpu1 should not be sleeping
May 28 01:50:06 main kernel: CPU1 is up
May 28 01:50:06 main kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
May 28 01:50:06 main kernel:  cache: parent cpu2 should not be sleeping
May 28 01:50:06 main kernel: CPU2 is up
May 28 01:50:06 main kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
May 28 01:50:06 main kernel:  cache: parent cpu3 should not be sleeping
May 28 01:50:06 main kernel: CPU3 is up
May 28 01:50:06 main kernel: ACPI: Waking up from system sleep state S4
May 28 01:50:06 main kernel: pcieport 0000:00:1c.0: Enabling MPC IRBNCE
May 28 01:50:06 main kernel: pcieport 0000:00:1c.0: Intel PCH root port ACS workaround enabled
May 28 01:50:06 main kernel: pcieport 0000:00:1c.2: Enabling MPC IRBNCE
May 28 01:50:06 main kernel: pcieport 0000:00:1c.2: Intel PCH root port ACS workaround enabled
May 28 01:50:06 main kernel: pcieport 0000:00:1c.3: Enabling MPC IRBNCE
May 28 01:50:06 main kernel: pcieport 0000:00:1c.3: Intel PCH root port ACS workaround enabled
May 28 01:50:06 main kernel: PM: noirq restore of devices complete after 1.140 msecs
May 28 01:50:06 main kernel: PM: early restore of devices complete after 0.740 msecs
May 28 01:50:06 main kernel: usb usb1: root hub lost power or was reset
May 28 01:50:06 main kernel: usb usb2: root hub lost power or was reset
May 28 01:50:06 main kernel: rtc_cmos 00:02: System wakeup disabled by ACPI
May 28 01:50:06 main kernel: serial 00:05: activated
May 28 01:50:06 main kernel: RTNL: assertion failed at net/core/dev.c (2325)
May 28 01:50:06 main kernel: CPU: 1 PID: 2213 Comm: kworker/u8:6 Tainted: P           O    4.11.2-1-ARCH #1
May 28 01:50:06 main kernel: Hardware name: Gigabyte Technology Co., Ltd. Z97X-Gaming 5/Z97X-Gaming 5, BIOS F5 05/30/2014
May 28 01:50:06 main kernel: Workqueue: events_unbound async_run_entry_fn
May 28 01:50:06 main kernel: Call Trace:
May 28 01:50:06 main kernel:  dump_stack+0x63/0x81
May 28 01:50:06 main kernel:  netif_set_real_num_tx_queues+0x111/0x1b0
May 28 01:50:06 main kernel:  __alx_open+0x1b4/0x4b0 [alx]
May 28 01:50:06 main kernel:  alx_resume+0x3d/0x40 [alx]
May 28 01:50:06 main kernel:  pci_pm_restore+0x7a/0xb0
May 28 01:50:06 main kernel:  ? pci_pm_suspend_noirq+0x190/0x190
May 28 01:50:06 main kernel:  dpm_run_callback+0x53/0x180
May 28 01:50:06 main kernel:  device_resume+0xe1/0x200
May 28 01:50:06 main kernel:  async_resume+0x1d/0x50
May 28 01:50:06 main kernel:  async_run_entry_fn+0x37/0x150
May 28 01:50:06 main kernel:  process_one_work+0x1e0/0x490
May 28 01:50:06 main kernel:  worker_thread+0x48/0x4e0
May 28 01:50:06 main kernel:  kthread+0x125/0x140
May 28 01:50:06 main kernel:  ? process_one_work+0x490/0x490
May 28 01:50:06 main kernel:  ? kthread_create_on_node+0x70/0x70
May 28 01:50:06 main kernel:  ret_from_fork+0x2c/0x40
May 28 01:50:06 main kernel: RTNL: assertion failed at net/core/dev.c (2367)
May 28 01:50:06 main kernel: CPU: 1 PID: 2213 Comm: kworker/u8:6 Tainted: P           O    4.11.2-1-ARCH #1
May 28 01:50:06 main kernel: Hardware name: Gigabyte Technology Co., Ltd. Z97X-Gaming 5/Z97X-Gaming 5, BIOS F5 05/30/2014
May 28 01:50:06 main kernel: Workqueue: events_unbound async_run_entry_fn
May 28 01:50:06 main kernel: Call Trace:
May 28 01:50:06 main kernel:  dump_stack+0x63/0x81
May 28 01:50:06 main kernel:  netif_set_real_num_rx_queues+0x78/0x80
May 28 01:50:06 main kernel:  __alx_open+0x1c2/0x4b0 [alx]
May 28 01:50:06 main kernel:  alx_resume+0x3d/0x40 [alx]
May 28 01:50:06 main kernel:  pci_pm_restore+0x7a/0xb0
May 28 01:50:06 main kernel:  ? pci_pm_suspend_noirq+0x190/0x190
May 28 01:50:06 main kernel:  dpm_run_callback+0x53/0x180
May 28 01:50:06 main kernel:  device_resume+0xe1/0x200
May 28 01:50:06 main kernel:  async_resume+0x1d/0x50
May 28 01:50:06 main kernel:  async_run_entry_fn+0x37/0x150
May 28 01:50:06 main kernel:  process_one_work+0x1e0/0x490
May 28 01:50:06 main kernel:  worker_thread+0x48/0x4e0
May 28 01:50:06 main kernel:  kthread+0x125/0x140
May 28 01:50:06 main kernel:  ? process_one_work+0x490/0x490
May 28 01:50:06 main kernel:  ? kthread_create_on_node+0x70/0x70
May 28 01:50:06 main kernel:  ret_from_fork+0x2c/0x40
May 28 01:50:06 main kernel: sd 0:0:0:0: [sda] Starting disk
May 28 01:50:06 main kernel: sd 1:0:0:0: [sdb] Starting disk
May 28 01:50:06 main kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 28 01:50:06 main kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 28 01:50:06 main kernel: ata1.00: supports DRM functions and may not be fully accessible
May 28 01:50:06 main kernel: ata2.00: configured for UDMA/133
May 28 01:50:06 main kernel: ata1.00: disabling queued TRIM support
May 28 01:50:06 main kernel: ata1.00: supports DRM functions and may not be fully accessible
May 28 01:50:06 main kernel: ata1.00: disabling queued TRIM support
May 28 01:50:06 main kernel: ata1.00: configured for UDMA/133
May 28 01:50:06 main kernel: ata1.00: Enabling discard_zeroes_data
May 28 01:50:06 main kernel: usb 1-9: reset low-speed USB device number 2 using xhci_hcd
May 28 01:50:06 main kernel: usb 1-10: reset full-speed USB device number 3 using xhci_hcd
May 28 01:50:06 main kernel: PM: restore of devices complete after 1051.786 msecs
May 28 01:50:06 main kernel: PM: Image restored successfully.
May 28 01:50:06 main kernel: PM: Basic memory bitmaps freed
May 28 01:50:06 main kernel: Restarting tasks ... 
May 28 01:50:06 main kernel: pci_bus 0000:05: Allocating resources
May 28 01:50:06 main kernel: pci 0000:04:00.0: bridge window [io  0x1000-0x0fff] to [bus 05] add_size 1000
May 28 01:50:06 main kernel: pci 0000:04:00.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 05] add_size 200000 add_align 100000
May 28 01:50:06 main kernel: pci 0000:04:00.0: bridge window [mem 0x00100000-0x000fffff] to [bus 05] add_size 200000 add_align 100000
May 28 01:50:06 main kernel: pci 0000:04:00.0: BAR 14: no space for [mem size 0x00200000]
May 28 01:50:06 main kernel: pci 0000:04:00.0: BAR 14: failed to assign [mem size 0x00200000]
May 28 01:50:06 main kernel: pci 0000:04:00.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
May 28 01:50:06 main kernel: pci 0000:04:00.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
May 28 01:50:06 main kernel: pci 0000:04:00.0: BAR 13: no space for [io  size 0x1000]
May 28 01:50:06 main kernel: pci 0000:04:00.0: BAR 13: failed to assign [io  size 0x1000]
May 28 01:50:06 main kernel: pci 0000:04:00.0: BAR 14: no space for [mem size 0x00200000]
May 28 01:50:06 main kernel: pci 0000:04:00.0: BAR 14: failed to assign [mem size 0x00200000]
May 28 01:50:06 main kernel: pci 0000:04:00.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
May 28 01:50:06 main kernel: pci 0000:04:00.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
May 28 01:50:06 main kernel: pci 0000:04:00.0: BAR 13: no space for [io  size 0x1000]
May 28 01:50:06 main kernel: pci 0000:04:00.0: BAR 13: failed to assign [io  size 0x1000]
May 28 01:50:06 main kernel: pci 0000:04:00.0: PCI bridge to [bus 05]
May 28 01:50:06 main kernel: done.
May 28 01:50:06 main systemd-sleep[2206]: System resumed.
May 28 01:50:06 main systemd[510]: Time has been changed
May 28 01:50:06 main systemd[1]: Time has been changed
May 28 01:50:06 main org_kde_powerdevil[627]: powerdevil: ACTIVE SESSION PATH CHANGED: "/org/freedesktop/login1/session/c2"
May 28 01:50:06 main org_kde_powerdevil[627]: powerdevil: Current session is now active
May 28 01:50:06 main systemd[1]: Started Hibernate.
May 28 01:50:06 main systemd[1]: sleep.target: Unit not needed anymore. Stopping.
May 28 01:50:06 main systemd[1]: Stopped target Sleep.
May 28 01:50:06 main systemd[1]: Reached target Hibernate.
May 28 01:50:06 main systemd[1]: hibernate.target: Unit is bound to inactive unit systemd-hibernate.service. Stopping, too.
May 28 01:50:06 main systemd[1]: Stopped target Hibernate.
May 28 01:50:06 main systemd-logind[389]: Operation 'sleep' finished.
May 28 01:50:06 main kernel: alx 0000:03:00.0 enp3s0: NIC Up: 100 Mbps Full
May 28 01:50:07 main ksmserver[584]: CreateNotify: 130023427
May 28 01:50:07 main ksmserver[584]: CreateNotify: 127926275
May 28 01:50:07 main ksmserver[584]: CreateNotify: 132120579
May 28 01:50:07 main kdeinit5[564]: bluedevil: About to resume
May 28 01:50:07 main kcminit[2284]: Initializing  "kcm_input" :  "kcminit_mouse"
May 28 01:50:07 main kcminit[2278]: Initializing  "kcm_input" :  "kcminit_mouse"
May 28 01:50:07 main kcminit[2277]: Initializing  "kcm_input" :  "kcminit_mouse"
May 28 01:50:07 main ksmserver[584]: CreateNotify: 132120584
May 28 01:50:07 main kwin_x11[611]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 16421, resource id: 132120584, major code: 18 (ChangeProperty), minor code: 0
May 28 01:50:07 main kwin_x11[611]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 16627, resource id: 127926280, major code: 18 (ChangeProperty), minor code: 0
May 28 01:50:07 main kwin_x11[611]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 16631, resource id: 130023432, major code: 18 (ChangeProperty), minor code: 0
May 28 01:50:07 main ksmserver[584]: CreateNotify: 127926280
May 28 01:50:07 main ksmserver[584]: CreateNotify: 130023432
May 28 01:50:07 main kscreenlocker_greet[2199]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml:98:103: Unable to assign int to QEasingCurve
May 28 01:50:12 main kcheckpass[2308]: pam_tally(kde:auth): Error opening /var/log/faillog for update
May 28 01:50:12 main kcheckpass[2308]: pam_tally(kde:auth): Error opening /var/log/faillog for read
May 28 01:50:12 main kcheckpass[2308]: pam_tally(kde:setcred): Error opening /var/log/faillog for update
May 28 01:50:12 main kcheckpass[2308]: pam_tally(kde:setcred): Error opening /var/log/faillog for update
May 28 01:50:12 main ksmserver[584]: UnmapNotify: 125829130
May 28 01:50:12 main ksmserver[584]: UnmapNotify: 125829130
May 28 01:50:12 main ksmserver[584]: CreateNotify: 125829136
May 28 01:50:12 main kwin_x11[611]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 18236, resource id: 125829136, major code: 18 (ChangeProperty), minor code: 0
May 28 01:50:12 main ksmserver[584]: Grab Released
May 28 01:50:12 main kdeinit5[564]: ktp-kded-module:

Offline

#10 2017-05-28 22:37:30

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: RTNL: assertion failed

I would start but not loading whatever module is tainting the kernel and check if the problem is still there (blacklist or remove the package that provides the module and make sure to reboot). That should give you a better idea of which upstream you may want to contact to ask for more help.


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#11 2017-07-30 07:28:48

vollekannehoschi
Member
Registered: 2015-03-08
Posts: 29

Re: RTNL: assertion failed

DevilDust did you solved the problem?

I have the same warnings, but my PC wakes up without hangs:

Jul 29 20:00:52 maxxgubbl systemd-sleep[393]: Suspending system...
Jul 30 07:48:36 maxxgubbl kernel: PM: Syncing filesystems ... done.
Jul 30 07:48:36 maxxgubbl kernel: PM: Preparing system for sleep (mem)
Jul 30 07:48:36 maxxgubbl kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Jul 30 07:48:36 maxxgubbl kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Jul 30 07:48:36 maxxgubbl kernel: PM: Suspending system (mem)
Jul 30 07:48:36 maxxgubbl kernel: Suspending console(s) (use no_console_suspend to debug)
Jul 30 07:48:36 maxxgubbl kernel: sd 5:0:0:0: [sdb] Synchronizing SCSI cache
Jul 30 07:48:36 maxxgubbl kernel: sd 4:0:0:0: [sda] Synchronizing SCSI cache
Jul 30 07:48:36 maxxgubbl kernel: serial 00:05: disabled
Jul 30 07:48:36 maxxgubbl kernel: sd 4:0:0:0: [sda] Stopping disk
Jul 30 07:48:36 maxxgubbl kernel: sd 5:0:0:0: [sdb] Stopping disk
Jul 30 07:48:36 maxxgubbl kernel: PM: suspend of devices complete after 617.130 msecs
Jul 30 07:48:36 maxxgubbl kernel: PM: late suspend of devices complete after 6.472 msecs
Jul 30 07:48:36 maxxgubbl kernel: ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
Jul 30 07:48:36 maxxgubbl kernel: ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI
Jul 30 07:48:36 maxxgubbl kernel: xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
Jul 30 07:48:36 maxxgubbl kernel: PM: noirq suspend of devices complete after 33.274 msecs
Jul 30 07:48:36 maxxgubbl kernel: ACPI: Preparing to enter system sleep state S3
Jul 30 07:48:36 maxxgubbl kernel: PM: Saving platform NVS memory
Jul 30 07:48:36 maxxgubbl kernel: Disabling non-boot CPUs ...
Jul 30 07:48:36 maxxgubbl kernel: smpboot: CPU 1 is now offline
Jul 30 07:48:36 maxxgubbl kernel: smpboot: CPU 2 is now offline
Jul 30 07:48:36 maxxgubbl kernel: smpboot: CPU 3 is now offline
Jul 30 07:48:36 maxxgubbl kernel: smpboot: CPU 4 is now offline
Jul 30 07:48:36 maxxgubbl kernel: smpboot: CPU 5 is now offline
Jul 30 07:48:36 maxxgubbl kernel: smpboot: CPU 6 is now offline
Jul 30 07:48:36 maxxgubbl kernel: smpboot: CPU 7 is now offline
Jul 30 07:48:36 maxxgubbl kernel: ACPI: Low-level resume complete
Jul 30 07:48:36 maxxgubbl kernel: PM: Restoring platform NVS memory
Jul 30 07:48:36 maxxgubbl kernel: Suspended for 42459.519 seconds
Jul 30 07:48:36 maxxgubbl kernel: Enabling non-boot CPUs ...
Jul 30 07:48:36 maxxgubbl kernel: x86: Booting SMP configuration:
Jul 30 07:48:36 maxxgubbl kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Jul 30 07:48:36 maxxgubbl kernel:  cache: parent cpu1 should not be sleeping
Jul 30 07:48:36 maxxgubbl kernel: microcode: sig=0x306c3, pf=0x2, revision=0x1c
Jul 30 07:48:36 maxxgubbl kernel: CPU1 is up
Jul 30 07:48:36 maxxgubbl kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Jul 30 07:48:36 maxxgubbl kernel:  cache: parent cpu2 should not be sleeping
Jul 30 07:48:36 maxxgubbl kernel: CPU2 is up
Jul 30 07:48:36 maxxgubbl kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Jul 30 07:48:36 maxxgubbl kernel:  cache: parent cpu3 should not be sleeping
Jul 30 07:48:36 maxxgubbl kernel: CPU3 is up
Jul 30 07:48:36 maxxgubbl kernel: smpboot: Booting Node 0 Processor 4 APIC 0x1
Jul 30 07:48:36 maxxgubbl kernel:  cache: parent cpu4 should not be sleeping
Jul 30 07:48:36 maxxgubbl kernel: microcode: sig=0x306c3, pf=0x2, revision=0x22
Jul 30 07:48:36 maxxgubbl kernel: CPU4 is up
Jul 30 07:48:36 maxxgubbl kernel: smpboot: Booting Node 0 Processor 5 APIC 0x3
Jul 30 07:48:36 maxxgubbl kernel:  cache: parent cpu5 should not be sleeping
Jul 30 07:48:36 maxxgubbl kernel: CPU5 is up
Jul 30 07:48:36 maxxgubbl kernel: smpboot: Booting Node 0 Processor 6 APIC 0x5
Jul 30 07:48:36 maxxgubbl kernel:  cache: parent cpu6 should not be sleeping
Jul 30 07:48:36 maxxgubbl kernel: CPU6 is up
Jul 30 07:48:36 maxxgubbl kernel: smpboot: Booting Node 0 Processor 7 APIC 0x7
Jul 30 07:48:36 maxxgubbl kernel:  cache: parent cpu7 should not be sleeping
Jul 30 07:48:36 maxxgubbl kernel: CPU7 is up
Jul 30 07:48:36 maxxgubbl kernel: ACPI: Waking up from system sleep state S3
Jul 30 07:48:36 maxxgubbl kernel: xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI
Jul 30 07:48:36 maxxgubbl kernel: ehci-pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 30 07:48:36 maxxgubbl kernel: ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 30 07:48:36 maxxgubbl kernel: PM: noirq resume of devices complete after 35.590 msecs
Jul 30 07:48:36 maxxgubbl kernel: PM: early resume of devices complete after 0.258 msecs
Jul 30 07:48:36 maxxgubbl kernel: rtc_cmos 00:02: System wakeup disabled by ACPI
Jul 30 07:48:36 maxxgubbl kernel: serial 00:05: activated
Jul 30 07:48:36 maxxgubbl kernel: sd 4:0:0:0: [sda] Starting disk
Jul 30 07:48:36 maxxgubbl kernel: sd 5:0:0:0: [sdb] Starting disk
Jul 30 07:48:36 maxxgubbl kernel: RTNL: assertion failed at net/core/dev.c (2326)
Jul 30 07:48:36 maxxgubbl kernel: CPU: 0 PID: 433 Comm: kworker/u16:43 Tainted: G           O    4.11.9-1-ARCH #1
Jul 30 07:48:36 maxxgubbl kernel: Hardware name: Gigabyte Technology Co., Ltd. Z97X-SOC Force/Z97X-SOC Force, BIOS F8 09/19/2015
Jul 30 07:48:36 maxxgubbl kernel: Workqueue: events_unbound async_run_entry_fn
Jul 30 07:48:36 maxxgubbl kernel: Call Trace:
Jul 30 07:48:36 maxxgubbl kernel:  dump_stack+0x63/0x81
Jul 30 07:48:36 maxxgubbl kernel:  netif_set_real_num_tx_queues+0x111/0x1b0
Jul 30 07:48:36 maxxgubbl kernel:  __alx_open+0x1b4/0x4b0 [alx]
Jul 30 07:48:36 maxxgubbl kernel:  alx_resume+0x3d/0x40 [alx]
Jul 30 07:48:36 maxxgubbl kernel:  pci_pm_resume+0x65/0xa0
Jul 30 07:48:36 maxxgubbl kernel:  ? pci_pm_thaw+0x90/0x90
Jul 30 07:48:36 maxxgubbl kernel:  dpm_run_callback+0x53/0x180
Jul 30 07:48:36 maxxgubbl kernel:  device_resume+0xe1/0x200
Jul 30 07:48:36 maxxgubbl kernel:  async_resume+0x1d/0x50
Jul 30 07:48:36 maxxgubbl kernel:  async_run_entry_fn+0x37/0x150
Jul 30 07:48:36 maxxgubbl kernel:  process_one_work+0x1e0/0x490
Jul 30 07:48:36 maxxgubbl kernel:  worker_thread+0x48/0x4e0
Jul 30 07:48:36 maxxgubbl kernel:  kthread+0x125/0x140
Jul 30 07:48:36 maxxgubbl kernel:  ? process_one_work+0x490/0x490
Jul 30 07:48:36 maxxgubbl kernel:  ? kthread_create_on_node+0x70/0x70
Jul 30 07:48:36 maxxgubbl kernel:  ? SyS_exit+0x17/0x20
Jul 30 07:48:36 maxxgubbl kernel:  ret_from_fork+0x25/0x30
Jul 30 07:48:36 maxxgubbl kernel: RTNL: assertion failed at net/core/dev.c (2368)
Jul 30 07:48:36 maxxgubbl kernel: CPU: 0 PID: 433 Comm: kworker/u16:43 Tainted: G           O    4.11.9-1-ARCH #1
Jul 30 07:48:36 maxxgubbl kernel: Hardware name: Gigabyte Technology Co., Ltd. Z97X-SOC Force/Z97X-SOC Force, BIOS F8 09/19/2015
Jul 30 07:48:36 maxxgubbl kernel: Workqueue: events_unbound async_run_entry_fn
Jul 30 07:48:36 maxxgubbl kernel: Call Trace:
Jul 30 07:48:36 maxxgubbl kernel:  dump_stack+0x63/0x81
Jul 30 07:48:36 maxxgubbl kernel:  netif_set_real_num_rx_queues+0x78/0x80
Jul 30 07:48:36 maxxgubbl kernel:  __alx_open+0x1c2/0x4b0 [alx]
Jul 30 07:48:36 maxxgubbl kernel:  alx_resume+0x3d/0x40 [alx]
Jul 30 07:48:36 maxxgubbl kernel:  pci_pm_resume+0x65/0xa0
Jul 30 07:48:36 maxxgubbl kernel:  ? pci_pm_thaw+0x90/0x90
Jul 30 07:48:36 maxxgubbl kernel:  dpm_run_callback+0x53/0x180
Jul 30 07:48:36 maxxgubbl kernel:  device_resume+0xe1/0x200
Jul 30 07:48:36 maxxgubbl kernel:  async_resume+0x1d/0x50
Jul 30 07:48:36 maxxgubbl kernel:  async_run_entry_fn+0x37/0x150
Jul 30 07:48:36 maxxgubbl kernel:  process_one_work+0x1e0/0x490
Jul 30 07:48:36 maxxgubbl kernel:  worker_thread+0x48/0x4e0
Jul 30 07:48:36 maxxgubbl kernel:  kthread+0x125/0x140
Jul 30 07:48:36 maxxgubbl kernel:  ? process_one_work+0x490/0x490
Jul 30 07:48:36 maxxgubbl kernel:  ? kthread_create_on_node+0x70/0x70
Jul 30 07:48:36 maxxgubbl kernel:  ? SyS_exit+0x17/0x20
Jul 30 07:48:36 maxxgubbl kernel:  ret_from_fork+0x25/0x30
Jul 30 07:48:36 maxxgubbl kernel: usb 3-8: reset high-speed USB device number 3 using xhci_hcd
Jul 30 07:48:36 maxxgubbl kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jul 30 07:48:36 maxxgubbl kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Jul 30 07:48:36 maxxgubbl kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Jul 30 07:48:36 maxxgubbl kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Jul 30 07:48:36 maxxgubbl kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Jul 30 07:48:36 maxxgubbl kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Jul 30 07:48:36 maxxgubbl kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Jul 30 07:48:36 maxxgubbl kernel: ata5.00: configured for UDMA/133
Jul 30 07:48:36 maxxgubbl kernel: usb 3-8.1: reset high-speed USB device number 4 using xhci_hcd
Jul 30 07:48:36 maxxgubbl kernel: usb 3-8.2: reset full-speed USB device number 5 using xhci_hcd
Jul 30 07:48:36 maxxgubbl kernel: usb 3-8.3: reset full-speed USB device number 6 using xhci_hcd
Jul 30 07:48:36 maxxgubbl kernel: [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training
Jul 30 07:48:36 maxxgubbl kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jul 30 07:48:36 maxxgubbl kernel: [drm:intel_dp_start_link_train [i915]] *ERROR* failed to start channel equalization
Jul 30 07:48:36 maxxgubbl kernel: ata6.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Jul 30 07:48:36 maxxgubbl kernel: ata6.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Jul 30 07:48:36 maxxgubbl kernel: ata6.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Jul 30 07:48:36 maxxgubbl kernel: ata6.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Jul 30 07:48:36 maxxgubbl kernel: ata6.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Jul 30 07:48:36 maxxgubbl kernel: ata6.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Jul 30 07:48:36 maxxgubbl kernel: ata6.00: configured for UDMA/133
Jul 30 07:48:36 maxxgubbl kernel: PM: resume of devices complete after 1450.541 msecs
Jul 30 07:48:36 maxxgubbl kernel: PM: Finishing wakeup.
Jul 30 07:48:36 maxxgubbl kernel: Restarting tasks ... 
Jul 30 07:48:36 maxxgubbl kernel: pci_bus 0000:03: Allocating resources
Jul 30 07:48:36 maxxgubbl kernel: pci 0000:02:00.0: bridge window [io  0x1000-0x0fff] to [bus 03] add_size 1000
Jul 30 07:48:36 maxxgubbl kernel: pci 0000:02:00.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 03] add_size 200000 add_align 100000
Jul 30 07:48:36 maxxgubbl kernel: pci 0000:02:00.0: bridge window [mem 0x00100000-0x000fffff] to [bus 03] add_size 200000 add_align 100000
Jul 30 07:48:36 maxxgubbl kernel: pci 0000:02:00.0: BAR 14: no space for [mem size 0x00200000]
Jul 30 07:48:36 maxxgubbl kernel: pci 0000:02:00.0: BAR 14: failed to assign [mem size 0x00200000]
Jul 30 07:48:36 maxxgubbl kernel: pci 0000:02:00.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
Jul 30 07:48:36 maxxgubbl kernel: pci 0000:02:00.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
Jul 30 07:48:36 maxxgubbl kernel: pci 0000:02:00.0: BAR 13: no space for [io  size 0x1000]
Jul 30 07:48:36 maxxgubbl kernel: pci 0000:02:00.0: BAR 13: failed to assign [io  size 0x1000]
Jul 30 07:48:36 maxxgubbl kernel: pci 0000:02:00.0: BAR 14: no space for [mem size 0x00200000]
Jul 30 07:48:36 maxxgubbl kernel: pci 0000:02:00.0: BAR 14: failed to assign [mem size 0x00200000]
Jul 30 07:48:36 maxxgubbl kernel: pci 0000:02:00.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
Jul 30 07:48:36 maxxgubbl kernel: pci 0000:02:00.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
Jul 30 07:48:36 maxxgubbl kernel: pci 0000:02:00.0: BAR 13: no space for [io  size 0x1000]
Jul 30 07:48:36 maxxgubbl kernel: pci 0000:02:00.0: BAR 13: failed to assign [io  size 0x1000]
Jul 30 07:48:36 maxxgubbl kernel: pci 0000:02:00.0: PCI bridge to [bus 03]
Jul 30 07:48:36 maxxgubbl connmand[451]: enp4s0 {RX} 10411999 packets 2619206180 bytes
Jul 30 07:48:36 maxxgubbl systemd[1]: Starting Rotate log files...
Jul 30 07:48:36 maxxgubbl connmand[451]: enp4s0 {TX} 1137373 packets 88594236 bytes
Jul 30 07:48:36 maxxgubbl systemd[1]: Starting Update man-db cache...
Jul 30 07:48:36 maxxgubbl connmand[451]: enp4s0 {update} flags 36867 <UP>
Jul 30 07:48:36 maxxgubbl systemd[1]: Started Verify integrity of password and group files.
Jul 30 07:48:36 maxxgubbl connman-vpnd[485]: enp4s0 {update} flags 36867 <UP>
Jul 30 07:48:36 maxxgubbl connman-vpnd[485]: enp4s0 {newlink} index 2 address FC:AA:14:21:F2:FA mtu 1500
Jul 30 07:48:36 maxxgubbl connman-vpnd[485]: enp4s0 {newlink} index 2 operstate 2 <DOWN>
Jul 30 07:48:36 maxxgubbl systemd-sleep[393]: System resumed.
Jul 30 07:48:36 maxxgubbl kernel: done.
Jul 30 07:48:36 maxxgubbl kernel: video LNXVIDEO:00: Restoring backlight state
Jul 30 07:48:36 maxxgubbl systemd[1]: Started Suspend.
Jul 30 07:48:36 maxxgubbl systemd[1]: sleep.target: Unit not needed anymore. Stopping.
Jul 30 07:48:36 maxxgubbl systemd[1]: Stopped target Sleep.
Jul 30 07:48:36 maxxgubbl systemd[1]: suspend.target: Bound to unit systemd-suspend.service, but unit isn't active.
Jul 30 07:48:36 maxxgubbl systemd[1]: Dependency failed for Suspend.
Jul 30 07:48:36 maxxgubbl systemd-logind[437]: Operation 'sleep' finished.
Jul 30 07:48:36 maxxgubbl systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.
Jul 30 07:48:36 maxxgubbl root[547]: ACPI group/action undefined: jack/lineout / LINEOUT
Jul 30 07:48:36 maxxgubbl root[549]: ACPI group/action undefined: jack/videoout / VIDEOOUT
Jul 30 07:48:36 maxxgubbl dunst[655]: (RandR) Could not get screen info, falling back to single monitor mode
Jul 30 07:48:37 maxxgubbl kernel: IPv6: ADDRCONF(NETDEV_UP): enp4s0: link is not ready
Jul 30 07:48:37 maxxgubbl sh[534]: Doppelter Passworteintrag
Jul 30 07:48:37 maxxgubbl sh[534]: Zeile »systemd-journal-gateway:x:191:191:systemd-journal-gateway:/:/usr/bin/nologin« löschen?Nein
Jul 30 07:48:37 maxxgubbl sh[534]: Doppelter Passworteintrag
Jul 30 07:48:37 maxxgubbl sh[534]: Zeile »systemd-timesync:x:192:192:systemd-timesync:/:/usr/bin/nologin« löschen?Nein
Jul 30 07:48:37 maxxgubbl sh[534]: Doppelter Passworteintrag
Jul 30 07:48:37 maxxgubbl sh[534]: Zeile »systemd-network:x:193:193:systemd-network:/:/usr/bin/nologin« löschen?Nein
Jul 30 07:48:37 maxxgubbl sh[534]: Doppelter Passworteintrag
Jul 30 07:48:37 maxxgubbl sh[534]: Zeile »systemd-bus-proxy:x:194:194:systemd-bus-proxy:/:/usr/bin/nologin« löschen?Nein
Jul 30 07:48:37 maxxgubbl sh[534]: Doppelter Passworteintrag
Jul 30 07:48:37 maxxgubbl sh[534]: Zeile »systemd-resolve:x:195:195:systemd-resolve:/:/usr/bin/nologin« löschen?Nein
Jul 30 07:48:37 maxxgubbl sh[534]: Doppelter Passworteintrag
Jul 30 07:48:37 maxxgubbl sh[534]: Zeile »systemd-journal-gateway:x:191:191::/:/usr/bin/nologin« löschen?Nein
Jul 30 07:48:37 maxxgubbl sh[534]: Doppelter Passworteintrag
Jul 30 07:48:37 maxxgubbl sh[534]: Zeile »systemd-timesync:x:192:192::/:/usr/bin/nologin« löschen?Nein
Jul 30 07:48:37 maxxgubbl sh[534]: Doppelter Passworteintrag
Jul 30 07:48:37 maxxgubbl sh[534]: Zeile »systemd-network:x:193:193::/:/usr/bin/nologin« löschen?Nein
Jul 30 07:48:37 maxxgubbl sh[534]: Doppelter Passworteintrag
Jul 30 07:48:37 maxxgubbl sh[534]: Zeile »systemd-bus-proxy:x:194:194::/:/usr/bin/nologin« löschen?Nein
Jul 30 07:48:37 maxxgubbl sh[534]: Doppelter Passworteintrag
Jul 30 07:48:37 maxxgubbl sh[534]: Zeile »systemd-resolve:x:195:195::/:/usr/bin/nologin« löschen?Nein
Jul 30 07:48:37 maxxgubbl connmand[451]: enp4s0 {newlink} index 2 address FC:AA:14:21:F2:FA mtu 1500
Jul 30 07:48:37 maxxgubbl sh[534]: pwck: Keine Änderungen
Jul 30 07:48:37 maxxgubbl connmand[451]: enp4s0 {newlink} index 2 operstate 2 <DOWN>
Jul 30 07:48:37 maxxgubbl avahi-daemon[438]: Withdrawing address record for 192.168.0.60 on enp4s0.
Jul 30 07:48:37 maxxgubbl avahi-daemon[438]: Leaving mDNS multicast group on interface enp4s0.IPv4 with address 192.168.0.60.
Jul 30 07:48:37 maxxgubbl avahi-daemon[438]: Interface enp4s0.IPv4 no longer relevant for mDNS.
Jul 30 07:48:37 maxxgubbl avahi-daemon[438]: Withdrawing address record for fe80::feaa:14ff:fe21:f2fa on enp4s0.
Jul 30 07:48:37 maxxgubbl avahi-daemon[438]: Leaving mDNS multicast group on interface enp4s0.IPv6 with address fe80::feaa:14ff:fe21:f2fa.
Jul 30 07:48:37 maxxgubbl avahi-daemon[438]: Interface enp4s0.IPv6 no longer relevant for mDNS.
Jul 30 07:48:37 maxxgubbl connmand[451]: enp4s0 {del} address 192.168.0.60/24 label enp4s0
Jul 30 07:48:37 maxxgubbl connmand[451]: enp4s0 {del} route 192.168.0.0 gw 0.0.0.0 scope 253 <LINK>
Jul 30 07:48:37 maxxgubbl connmand[451]: enp4s0 {del} route fe80:: gw :: scope 0 <UNIVERSE>
Jul 30 07:48:37 maxxgubbl sh[534]: Doppelter Gruppeneintrag
Jul 30 07:48:37 maxxgubbl sh[534]: Zeile »proc:x:26:« löschen?Nein
Jul 30 07:48:37 maxxgubbl sh[534]: Doppelter Gruppeneintrag
Jul 30 07:48:37 maxxgubbl sh[534]: Zeile »input:x:97:« löschen?Nein
Jul 30 07:48:37 maxxgubbl sh[534]: Doppelter Gruppeneintrag
Jul 30 07:48:37 maxxgubbl sh[534]: Zeile »input:x:97:« löschen?Nein
Jul 30 07:48:37 maxxgubbl sh[534]: Doppelter Gruppeneintrag
Jul 30 07:48:37 maxxgubbl sh[534]: Zeile »proc:x:26:polkitd« löschen?Nein
Jul 30 07:48:37 maxxgubbl sh[534]: 'polkitd' is a member of the 'proc' group in /etc/group but not in /etc/gshadow
Jul 30 07:48:37 maxxgubbl sh[534]: Doppelter Eintrag für shadow-Gruppe
Jul 30 07:48:37 maxxgubbl sh[534]: Zeile »proc:::« löschen?Nein
Jul 30 07:48:37 maxxgubbl sh[534]: Doppelter Eintrag für shadow-Gruppe
Jul 30 07:48:37 maxxgubbl sh[534]: Zeile »input:x::« löschen?Nein
Jul 30 07:48:37 maxxgubbl sh[534]: Doppelter Eintrag für shadow-Gruppe
Jul 30 07:48:37 maxxgubbl sh[534]: Zeile »input:!::« löschen?Nein
Jul 30 07:48:37 maxxgubbl sh[534]: Doppelter Eintrag für shadow-Gruppe
Jul 30 07:48:37 maxxgubbl sh[534]: Zeile »proc:!::polkitd« löschen?Nein
Jul 30 07:48:37 maxxgubbl sh[534]: 'polkitd' is a member of the 'proc' group in /etc/gshadow but not in /etc/group
Jul 30 07:48:37 maxxgubbl sh[534]: grpck: Keine Änderungen
Jul 30 07:48:37 maxxgubbl systemd[1]: shadow.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Jul 30 07:48:37 maxxgubbl systemd[1]: shadow.service: Unit entered failed state.
Jul 30 07:48:37 maxxgubbl systemd[1]: shadow.service: Failed with result 'exit-code'.
Jul 30 07:48:37 maxxgubbl systemd[1]: Reloading Apache Web Server.
Jul 30 07:48:37 maxxgubbl systemd[1]: Reloaded Apache Web Server.
Jul 30 07:48:37 maxxgubbl systemd[1]: Started Rotate log files.
Jul 30 07:48:38 maxxgubbl ntpd[466]: Deleting interface #11 enp4s0, fe80::feaa:14ff:fe21:f2fa%2#123, interface stats: received=0, sent=0, dropped=0, active_time=1236 secs
Jul 30 07:48:38 maxxgubbl ntpd[466]: Deleting interface #12 enp4s0, 192.168.0.60#123, interface stats: received=49, sent=49, dropped=0, active_time=1232 secs
Jul 30 07:48:38 maxxgubbl ntpd[466]: 195.78.244.50 local addr 192.168.0.60 -> <null>
Jul 30 07:48:38 maxxgubbl ntpd[466]: 129.70.132.35 local addr 192.168.0.60 -> <null>
Jul 30 07:48:38 maxxgubbl ntpd[466]: 5.135.182.135 local addr 192.168.0.60 -> <null>
Jul 30 07:48:38 maxxgubbl ntpd[466]: 213.136.86.203 local addr 192.168.0.60 -> <null>
Jul 30 07:48:38 maxxgubbl connmand[451]: enp4s0 {add} route fe80:: gw :: scope 0 <UNIVERSE>
Jul 30 07:48:38 maxxgubbl connmand[451]: enp4s0 {RX} 10411999 packets 2619206180 bytes
Jul 30 07:48:38 maxxgubbl kernel: alx 0000:04:00.0 enp4s0: NIC Up: 1 Gbps Full
Jul 30 07:48:38 maxxgubbl kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp4s0: link becomes ready
Jul 30 07:48:38 maxxgubbl connmand[451]: enp4s0 {TX} 1137373 packets 88594236 bytes
Jul 30 07:48:38 maxxgubbl connmand[451]: enp4s0 {update} flags 102467 <UP,RUNNING,LOWER_UP>
Jul 30 07:48:38 maxxgubbl connman-vpnd[485]: enp4s0 {update} flags 102467 <UP,RUNNING,LOWER_UP>
Jul 30 07:48:38 maxxgubbl connmand[451]: enp4s0 {newlink} index 2 address FC:AA:14:21:F2:FA mtu 1500
Jul 30 07:48:38 maxxgubbl connman-vpnd[485]: enp4s0 {newlink} index 2 address FC:AA:14:21:F2:FA mtu 1500
Jul 30 07:48:38 maxxgubbl connmand[451]: enp4s0 {newlink} index 2 operstate 6 <UP>
Jul 30 07:48:38 maxxgubbl connman-vpnd[485]: enp4s0 {newlink} index 2 operstate 6 <UP>
Jul 30 07:48:38 maxxgubbl connmand[451]: Skipping disconnect of carrier, network is connecting.

Offline

Board footer

Powered by FluxBB