All of lore.kernel.org
 help / color / mirror / Atom feed
From: Per Oberg <pero@wolfram.com>
To: xenomai@lists.linux.dev
Subject: RTNet unable to handle kernel NULL pointer dereference at 0000000000000068
Date: Wed, 4 Oct 2023 03:45:26 -0500 (CDT)	[thread overview]
Message-ID: <1516654157.3383261.1696409126391.JavaMail.zimbra@wolfram.com> (raw)

Hi list
I experienced a crash  with Xenomai-3.1 on Linux 4.19.114-cip24

It does not seem to be the end of the world though because things were not immediately broken for me and I can't reproduce it.

Any thoughts ?

[  129.326872] RTnet: registered rteth1
[  129.326874] rt_igb 0000:02:00.0: Intel(R) Gigabit Ethernet Network Connection
[  129.326875] rt_igb 0000:02:00.0: rteth1: (PCIe:2.5Gb/s:Width x1) 00:1b:21:e0:b6:31
[  129.327002] rt_igb 0000:02:00.0: rteth1: PBA No: G69016-005
[  129.327003] rt_igb 0000:02:00.0: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)
[  321.182356] rt_igb: rteth1: igb: rteth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[  361.783381] [Xenomai] switching rtnet-rtpc to secondary mode after exception #14 in kernel-space at 0xffffffffc03855a0 (pid 1445)
[  361.783386] BUG: unable to handle kernel NULL pointer dereference at 0000000000000068
[  361.783415] PGD 0 P4D 0 
[  361.783428] Oops: 0000 [#1] PREEMPT SMP PTI
[  361.784109] CPU: 2 PID: 1445 Comm: rtnet-rtpc Tainted: G        W  O      4.19.114-cip24-xeno-cobolt #1
[  361.784809] Hardware name: Default string Default string/SKYBAY, BIOS 5.11 09/22/2016
[  361.785504] I-pipe domain: Linux
[  361.786214] RIP: 0010:rtdev_reference+0x0/0x70 [rtnet]
[  361.786911] Code: 00 eb e0 48 89 ef e8 ff 25 00 00 89 de 48 c7 c7 19 cf 38 c0 e8 da fb 91 c1 eb c8 0f 1f 44 00 00 66 2e 0f 1f 84 00 00 00 00 00 <48> 8b 57 68 48 85 d2 74 52 53 8b 47 5c 85 c0 74 19 8d 50 01 48 8d
[  361.787708] RSP: 0018:ffff947dc01a7df0 EFLAGS: 00010206
[  361.788516] RAX: 000000000000587e RBX: 0000000000000000 RCX: 0000000000000000
[  361.789333] RDX: 0000000083ca0000 RSI: 0000000000001a00 RDI: 0000000000000000
[  361.790153] RBP: ffff891e64a4c058 R08: ffff891e617e8138 R09: 0000000000000002
[  361.790980] R10: 0000000000000000 R11: 00000000000005dc R12: ffff891e617e8110
[  361.791812] R13: 0000000000025540 R14: ffff891e64a4c278 R15: ffff891e617e8000
[  361.792646] FS:  0000000000000000(0000) GS:ffff891e65b00000(0000) knlGS:0000000000000000
[  361.793490] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  361.794334] CR2: 0000000000000068 CR3: 0000000051c0a005 CR4: 00000000003606e0
[  361.795182] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  361.796026] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[  361.796869] Call Trace:
[  361.797721]  rt_tcp_segment.constprop.21+0x1ca/0x510 [rttcp]
[  361.798557]  rt_tcp_send+0x3e/0xd0 [rttcp]
[  361.799411]  ? rtdm_event_timedwait+0x181/0x320
[  361.800271]  rtpc_dispatch_handler+0xd4/0x1f0 [rtnet]
[  361.801137]  ? xnthread_map+0x370/0x370
[  361.802002]  kthread_trampoline+0x77/0x133
[  361.802868]  kthread+0x10e/0x130
[  361.803716]  ? kthread_create_worker_on_cpu+0x70/0x70
[  361.804591]  ret_from_fork+0x36/0x50
[  361.805464] Modules linked in: rttcp rtpacket rtudp rtipv4 igb rt_igb rtnet x86_pkg_temp_thermal e1000e pcan(O)
[  361.806378] CR2: 0000000000000068
[  361.807284] ---[ end trace a94628c3ed940012 ]---
[  361.808201] RIP: 0010:rtdev_reference+0x0/0x70 [rtnet]
[  361.809144] Code: 00 eb e0 48 89 ef e8 ff 25 00 00 89 de 48 c7 c7 19 cf 38 c0 e8 da fb 91 c1 eb c8 0f 1f 44 00 00 66 2e 0f 1f 84 00 00 00 00 00 <48> 8b 57 68 48 85 d2 74 52 53 8b 47 5c 85 c0 74 19 8d 50 01 48 8d
[  361.810147] RSP: 0018:ffff947dc01a7df0 EFLAGS: 00010206
[  361.811161] RAX: 000000000000587e RBX: 0000000000000000 RCX: 0000000000000000
[  361.812184] RDX: 0000000083ca0000 RSI: 0000000000001a00 RDI: 0000000000000000
[  361.813207] RBP: ffff891e64a4c058 R08: ffff891e617e8138 R09: 0000000000000002
[  361.814222] R10: 0000000000000000 R11: 00000000000005dc R12: ffff891e617e8110
[  361.815248] R13: 0000000000025540 R14: ffff891e64a4c278 R15: ffff891e617e8000
[  361.816246] FS:  0000000000000000(0000) GS:ffff891e65b00000(0000) knlGS:0000000000000000
[  361.817247] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  361.818213] CR2: 0000000000000068 CR3: 0000000051c0a005 CR4: 00000000003606e0
[  361.819152] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  361.820047] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


Regards
Per Öberg 

             reply	other threads:[~2023-10-04  8:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-04  8:45 Per Oberg [this message]
2023-10-04  9:42 ` RTNet unable to handle kernel NULL pointer dereference at 0000000000000068 Jan Kiszka
2023-10-04 13:01   ` Per Oberg
2023-10-04 13:57     ` Jan Kiszka
2023-10-04 14:15       ` Per Oberg
2023-10-05 14:19         ` Per Oberg
2023-10-05 14:21           ` Jan Kiszka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1516654157.3383261.1696409126391.JavaMail.zimbra@wolfram.com \
    --to=pero@wolfram.com \
    --cc=xenomai@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.