each write on a socketcan (cc770) produces kernel warning/error

Bug #1915035 reported by Patric Hopfgarten
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-signed-hwe (Ubuntu)
New
Undecided
Unassigned

Bug Description

Since the kernel 4.15.0-133 (Ubuntu 16.04.7 LTS) each write on a socketcan interface, with the cc770 chipset, produces a warning/error in the /var/log/kern.log. However the data is send on the bus. Previous kernel (4.15.0-132) worked fine.
This results in a very big kern.log after a few hours, if a can control loop is running, and crashes the system.
Can be reproduced with cansend.

Following warning is found in the kern.log:
Feb 8 14:40:28 sick01 kernel: [ 307.543907] ------------[ cut here ]------------
Feb 8 14:40:28 sick01 kernel: [ 307.543925] WARNING: CPU: 1 PID: 255 at /build/linux-hwe-EhsNBW/linux-hwe-4.15.0/net/core/skbuff.c:615 skb_release_head_state+0xba/0xd0
Feb 8 14:40:28 sick01 kernel: [ 307.543943] Modules linked in: btrfs zstd_compress xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c can_raw can intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel uvcvideo(OE) pcbc videobuf2_vmalloc aesni_intel videobuf2_memops aes_x86_64 videobuf2_v4l2 crypto_simd glue_helper cryptd videobuf2_core intel_cstate videodev(OE) intel_rapl_perf media input_leds shpchp intel_wmi_thunderbolt serio_raw mei_me mei intel_pch_thermal mac_hid acpi_pad binfmt_misc cc770_isa cc770 can_dev parport_pc ppdev lp parport autofs4 i915 igb drm_kms_helper syscopyarea sysfillrect dca e1000e sysimgblt i2c_algo_bit fb_sys_fops ahci ptp drm pps_core libahci wmi video
Feb 8 14:40:28 sick01 kernel: [ 307.543970] CPU: 1 PID: 255 Comm: systemd-journal Tainted: G W OE 4.15.0-133-generic #137~16.04.1-Ubuntu
Feb 8 14:40:28 sick01 kernel: [ 307.543971] Hardware name: Bernecker + Rainer Industrie-Elektronik APC3100/APC3100, BIOS a1.13 09/25/2018
Feb 8 14:40:28 sick01 kernel: [ 307.543973] RIP: 0010:skb_release_head_state+0xba/0xd0
Feb 8 14:40:28 sick01 kernel: [ 307.543974] RSP: 0000:ffff9a81eec83e18 EFLAGS: 00010086
Feb 8 14:40:28 sick01 kernel: [ 307.543976] RAX: 0000000000000024 RBX: ffff9a81e148e000 RCX: 0000000000000006
Feb 8 14:40:28 sick01 kernel: [ 307.543977] RDX: 0000000000000000 RSI: ffff9a81eec96498 RDI: ffff9a81eec96490
Feb 8 14:40:28 sick01 kernel: [ 307.543978] RBP: ffff9a81eec83e20 R08: 0000000000027e14 R09: ffffffff887624c4
Feb 8 14:40:28 sick01 kernel: [ 307.543979] R10: 0000000000000000 R11: 00000000003e7f80 R12: ffff9a81e148e000
Feb 8 14:40:28 sick01 kernel: [ 307.543980] R13: ffff9a81dc272000 R14: ffff9a81dbf02400 R15: 0000000000000055
Feb 8 14:40:28 sick01 kernel: [ 307.543981] FS: 00007f16e4321840(0000) GS:ffff9a81eec80000(0000) knlGS:0000000000000000
Feb 8 14:40:28 sick01 kernel: [ 307.543982] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 8 14:40:28 sick01 kernel: [ 307.543983] CR2: 00007f16e22df028 CR3: 000000026394e003 CR4: 00000000003606e0
Feb 8 14:40:28 sick01 kernel: [ 307.543984] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Feb 8 14:40:28 sick01 kernel: [ 307.543985] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Feb 8 14:40:28 sick01 kernel: [ 307.543986] Call Trace:
Feb 8 14:40:28 sick01 kernel: [ 307.543987] <IRQ>
Feb 8 14:40:28 sick01 kernel: [ 307.543990] skb_release_all+0x12/0x30
Feb 8 14:40:28 sick01 kernel: [ 307.543992] consume_skb+0x2c/0xa0
Feb 8 14:40:28 sick01 kernel: [ 307.543995] can_put_echo_skb+0xbd/0xf0 [can_dev]
Feb 8 14:40:28 sick01 kernel: [ 307.543998] cc770_interrupt+0x336/0x680 [cc770]
Feb 8 14:40:28 sick01 kernel: [ 307.544002] ? kmem_cache_free+0x1d1/0x1e0
Feb 8 14:40:28 sick01 kernel: [ 307.544005] ? kmem_cache_free+0x1d1/0x1e0
Feb 8 14:40:28 sick01 kernel: [ 307.544008] __handle_irq_event_percpu+0x84/0x1a0
Feb 8 14:40:28 sick01 kernel: [ 307.544012] handle_irq_event_percpu+0x32/0x80
Feb 8 14:40:28 sick01 kernel: [ 307.544015] handle_irq_event+0x3b/0x60
Feb 8 14:40:28 sick01 kernel: [ 307.544017] handle_edge_irq+0x7f/0x1a0
Feb 8 14:40:28 sick01 kernel: [ 307.544020] handle_irq+0x20/0x30
Feb 8 14:40:28 sick01 kernel: [ 307.544022] do_IRQ+0x4e/0xe0
Feb 8 14:40:28 sick01 kernel: [ 307.544025] common_interrupt+0x90/0x90
Feb 8 14:40:28 sick01 kernel: [ 307.544026] </IRQ>
Feb 8 14:40:28 sick01 kernel: [ 307.544028] RIP: 0033:0x7f16e30b2b0a
Feb 8 14:40:28 sick01 kernel: [ 307.544029] RSP: 002b:00007ffdb94f97a8 EFLAGS: 00000207 ORIG_RAX: ffffffffffffffdc
Feb 8 14:40:28 sick01 kernel: [ 307.544031] RAX: 0000000000000000 RBX: 00007ffdb94fd110 RCX: 0000000000000030
Feb 8 14:40:28 sick01 kernel: [ 307.544032] RDX: 000000000000000f RSI: 000000000000000a RDI: 00007ffdb94fb0c0
Feb 8 14:40:28 sick01 kernel: [ 307.544034] RBP: 00000000000000ca R08: 1999999999999999 R09: 0000000000000000
Feb 8 14:40:28 sick01 kernel: [ 307.544035] R10: 00007f16e319b6a0 R11: 00007f16e319ada0 R12: 00000000000000c9
Feb 8 14:40:28 sick01 kernel: [ 307.544036] R13: 00007ffdb94fb026 R14: 00007ffdb94fb019 R15: 0000000000000000
Feb 8 14:40:28 sick01 kernel: [ 307.544037] Code: 5b 5d c3 e8 49 b5 05 00 eb da e8 02 05 0d 00 eb 9c 48 83 e7 fe e8 77 18 02 00 e9 72 ff ff ff 48 c7 c7 a0 5e ea 87 e8 56 3d 89 ff <0f> 0b 48 8b 43 60 eb 9a 0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00
Feb 8 14:40:28 sick01 kernel: [ 307.544059] ---[ end trace 2897b005757ca737 ]---

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.15.0-133-generic 4.15.0-133.137~16.04.1
ProcVersionSignature: Ubuntu 4.15.0-133.137~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-133-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.30
Architecture: amd64
Date: Mon Feb 8 17:05:16 2021
InstallationDate: Installed on 2021-01-13 (26 days ago)
InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806)
SourcePackage: linux-signed-hwe
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Patric Hopfgarten (patrickit) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.