RTNL: assertion failed at /build/linux-XO_uEE/linux-4.13.0/net/core/dev.c (2398)

[Mathieu SERVIERE]

none

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: wl
Annotation: Your system might become unstable now and might need to be restarted.
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Sun Oct 22 04:28:11 2017
Failure: oops
HibernationDevice: RESUME=UUID=86c7a013-98c6-4e61-a699-bc7115a72d6c
InstallationDate: Installed on 2017-10-20 (2 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Dell Inc. Vostro 3360
OopsText:
 RTNL: assertion failed at /build/linux-XO_uEE/linux-4.13.0/net/core/dev.c (2398)
 CPU: 1 PID: 11321 Comm: kworker/u16:10 Tainted: P OE 4.13.0-16-generic #19-Ubuntu
 Hardware name: Dell Inc. Vostro 3360/0RGR2N, BIOS A18 09/25/2013
 Workqueue: events_unbound async_run_entry_fn
 Call Trace:
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
SourcePackage: linux
Title: RTNL: assertion failed at /build/linux-XO_uEE/linux-4.13.0/net/core/dev.c (2398)
UpgradeStatus: Upgraded to artful on 2017-10-20 (1 days ago)
dmi.bios.date: 09/25/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A18
dmi.board.name: 0RGR2N
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnDellInc.:bvrA18:bd09/25/2013:svnDellInc.:pnVostro3360:pvr:rvnDellInc.:rn0RGR2N:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.family: ChiefRiver System
dmi.product.name: Vostro 3360
dmi.sys.vendor: Dell Inc.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc6

[Tristan (supersluether)]

I have a crontab entry on my desktop to suspend the system to memory at 11pm and resume at 7am every day. Because the desktop has graphical artifacts on resume, I log out before it suspends. When I log back in, this same error is shown.

I do not get this error when resuming if I use the suspend option on the lock screen. (the graphical artifacts do not happen either with this method)

I do not get this error on my laptop, whether suspending via the lock screen or using rtcwake.

Both my desktop and laptop are running Ubuntu 17.10 with kernel 4.13.0-16-generic. The laptop has an Intel i3 CPU and is using the default drivers. The desktop has an Intel i7 CPU and an Nvidia GTX 760 with the Nvidia drivers installed.

I attempted booting the latest v4.14 kernel on my desktop as suggested, but it would not load the GUI. I was only able to access the terminal (TTY2-6). I'm guessing this is because of the proprietary graphics drivers or a misconfiguration on my end when installing the new kernel.

The system appears to be stable, and everything seems to work just fine after dismissing the error message. I haven't run into any problems other than the error message simply appearing.

I cannot tell when the issue started happening, as I have not used rtcwake in some time (this error did not happen before, but I remember the graphical artifacts being an issue with Nvidia graphics).

Is there any debug info I can grab from the laptop that would help determine why it does not have this issue?

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]