Am Donnerstag, den 26.03.2020, 13:06 +0100 schrieb Jiri Slaby:
> On 26. 03. 20, 12:56, josef Reidinger wrote:  
> > 
> > OK, reproduced. Now I have vmcore, which I can upload somewhere and also more detailed info in crash dmesg:
> > 
> > [   94.326703] show_signal_msg: 34 callbacks suppressed
> > [   94.326706] chrome[4992]: segfault at 39 ip 000055b2354eca04 sp 00007ffd8aab1af0 error 6 in chrome[55b2351f1000+7287000]
> > [   94.326712] Code: cc cc cc cc cc cc 55 48 89 e5 bf 08 00 00 00 e8 62 ed 73 02 48 8d 0d 3b bb 03 07 48 89 08 5d c3 cc cc cc cc cc cc 55 48 89 e5 <c6> 04 25 39 00 00 00 21 5d c3 cc cc 55 48 89 e5 b8 01 00 00 00 48
> > [   94.453075] BUG: unable to handle page fault for address: ffff8ca8947d8000
> > [   94.453081] #PF: supervisor write access in kernel mode
> > [   94.453084] #PF: error_code(0x0002) - not-present page
> > [   94.453086] PGD 59e01067 P4D 59e01067 PUD 3b438c063 PMD 3947d3063 PTE 0
> > [   94.453095] Oops: 0002 [#1] SMP NOPTI
> > [   94.453101] CPU: 6 PID: 0 Comm: swapper/6 Kdump: loaded Tainted: P         C OE     5.5.9-1-default #1 openSUSE Tumbleweed (unreleased)
> > [   94.453103] Hardware name: ASUSTeK COMPUTER INC. TUF Gaming FX705DT_FX705DT/FX705DT, BIOS FX705DT.308 09/19/2019
> > [   94.453111] RIP: 0010:__memset+0x24/0x30
> > [   94.453115] Code: cc cc cc cc cc cc 0f 1f 44 00 00 49 89 f9 48 89 d1 83 e2 07 48 c1 e9 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48 0f af c6 <f3> 48 ab 89 d1 f3 aa 4c 89 c8 c3 90 49 89 f9 40 88 f0 48 89 d1 f3
> > [   94.453117] RSP: 0018:ffffa208802f0898 EFLAGS: 00010216
> > [   94.453120] RAX: 0000000000000000 RBX: 00000000ffffffff RCX: 000000001ff1a800
> > [   94.453122] RDX: 0000000000000007 RSI: 0000000000000000 RDI: ffff8ca8947d7ffa
> > [   94.453124] RBP: ffff8ca916f36800 R08: ffff8ca8d612e800 R09: ffff8ca8940ac002
> > [   94.453126] R10: ffff8ca8940a8000 R11: 0000000000000568 R12: ffff8ca917039ec0
> > [   94.453128] R13: 000000000000000c R14: 00000000304d434e R15: ffff8ca90835a800
> > [   94.453131] FS:  0000000000000000(0000) GS:ffff8ca936d80000(0000) knlGS:0000000000000000
> > [   94.453133] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > [   94.453135] CR2: ffff8ca8947d8000 CR3: 00000003aca6a000 CR4: 00000000003406e0
> > [   94.453137] Call Trace:
> > [   94.453140]  <IRQ>
> > [   94.453150]  cdc_ncm_fill_tx_frame+0x597/0x700 [cdc_ncm]  
> 
> It is a long standing issue. There is a guy reporting this on 5.2:
> https://lists.zx2c4.com/pipermail/wireguard/2019-August/004386.html
> 
> I would try reporting it upstream. And upstream is ... Oliver Neukum. CCed.
> 
> You should perhaps create a bug too.  

Please make a bugzilla entry, enable dynamic debugging for module
cdc_ncm, reload it and please reproduce.

    Regards
        Oliver