[Bug 1912162] Re: NetworkManager managed wifi can't connect
Thanks for the reply, I opened the following upstream issue: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/635 Though I'm not sure how effective that is going to be as ubuntu is not using the latest upstream NM so they just tell me "please update to latest version and report back"... ** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #635 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/635 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912162 Title: NetworkManager managed wifi can't connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1912162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912162] Re: NetworkManager managed wifi can't connect
Just to make it explicitly clear - I think there are 2 bugs involved - 1 is related to driver/firmware on older 5.4 kernel since on that version I couldn't get the adapter to connect even with the /etc/network/interfaces based configuration, but on kernel 5.10 it works. This bug deals only with not being able to connect via NetworkManager to my wifi even on 5.10. Once this is resolved I can go back and try to do bisection of the kernel which patch enables the /etc/networking/interfaces configuration to work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912162 Title: NetworkManager managed wifi can't connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1912162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912162] Re: NetworkManager managed wifi can't connect
Here's the output wpa_supplicant as used from NetworkManager and under which my intel ax200 based interface cannot connect. ** Attachment added: "wpa-supllicant-broken" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1912162/+attachment/5454051/+files/wpa-supllicant-broken -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912162 Title: NetworkManager managed wifi can't connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1912162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912162] [NEW] NetworkManager managed wifi can't connect
Public bug reported: My computer has an built-in intel ax200 adapter (the motherboard is asock taichi x570). With the latest stable 5.4 kernel on Ubuntu Focal 20.04 I cannot get the card to connect to my home wifi (2.4ghz). The errors I get are : iwlwifi :05:00.0: No beacon heard and the time event is over already... wlp5s0: Connection to AP 30:b5:c2:75:a4:ce lost wlp5s0: send auth to 30:b5:c2:75:a4:ce (try 2/3) Initially I thought this could be due to a problem with the iwlwifi driver and the firmware used. I upgraded to a custom-build (using ubuntu's configuration) 5.10 kernel And now the errors I was getting were: [нд яну 17 22:01:33 2021] iwlwifi :05:00.0: No beacon heard and the session protection is over already... [нд яну 17 22:01:33 2021] wlp5s0: Connection to AP 30:b5:c2:75:a4:ce lost [нд яну 17 22:01:33 2021] wlp5s0: send auth to 30:b5:c2:75:a4:ce (try 3/3) [нд яну 17 22:01:34 2021] wlp5s0: authentication with 30:b5:c2:75:a4:ce timed out [нд яну 17 22:01:35 2021] wlp5s0: authenticate with 30:b5:c2:75:a4:ce [нд яну 17 22:01:35 2021] wlp5s0: send auth to 30:b5:c2:75:a4:ce (try 1/3) [нд яну 17 22:01:36 2021] iwlwifi :05:00.0: No beacon heard and the session protection is over already... [нд яну 17 22:01:36 2021] wlp5s0: Connection to AP 30:b5:c2:75:a4:ce lost [нд яну 17 22:01:36 2021] wlp5s0: send auth to 30:b5:c2:75:a4:ce (try 2/3) [нд яну 17 22:01:37 2021] iwlwifi :05:00.0: No beacon heard and the session protection is over already... [нд яну 17 22:01:37 2021] wlp5s0: Connection to AP 30:b5:c2:75:a4:ce lost [нд яну 17 22:01:37 2021] wlp5s0: send auth to 30:b5:c2:75:a4:ce (try 3/3) The change of message is because newer versions of the driver/firmware have moved part of the processing in firmware. At this point I was willing to accept this is an issue with the kernel. However, I added the following configuration to /etc/network/interfaces: allow-hotplug wlp5s0 iface wlp5s0 inet dhcp wpa-ssid HOME wpa-psk wpa-debug-level 2 And what do you know - I was able to connect to my home wifi with no problems. I'm attaching the output of wpa_supplicant run with -dd from both the /etc/network/interfaces-based configuration (wpa_supplicant_working) and from the NetworkManager managed one ( I have edited /lib/systemd/system/wpa_supplicant.service to include -f /var/log/wpa_supplicant -dd) options. I wasn't able to figure any glaring differences between the flows of the two. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: "output of working wpa supplicant from ifupdown scripts" https://bugs.launchpad.net/bugs/1912162/+attachment/5454050/+files/wpa-supllicant-working -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912162 Title: NetworkManager managed wifi can't connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1912162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787801] Re: openvpn does not work with ecryptfs setup
Ok, thanks for the tip I didn't know that. If this is then coming from upstream I guess a bug report is warranted there as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787801 Title: openvpn does not work with ecryptfs setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1787801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787801] [NEW] openvpn does not work with ecryptfs setup
Public bug reported: I have an ecryptfs in which my decrypted mount point is /home/$user/Private . Additionally my openvpn setup is such that under /etc/openvpn I have symlinks to the actual files which are located in /home/$user/Private/openvpn. When I try to start openvpn (bear in mind that this setup worked on 16.04, I upgraded the machine) I get an error : fisk-mobile ovpn-CONF-FILE[25710]: Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/CONF-FILE.conf Needless to say that manually running openvpn --config /etc/openvpn /CONF-FILE.conf (which is a symlink ) worked flawlessly. After a bit of headbanging it turned out the issue is caused by the ProtectHome directive of the openvpn service file under: /lib/systemd/system/openvpn@.service - the same directive also applies to openvpn-client@.service service as well. Changing the value from 'true' to 'read-only' resolved the issue. In my opinion having the config files on an encrypted partition under /home/$USER is not that uncommon and so the unit file should be changed to at least allow RO permissions. Additionally, this setup worked on ubuntu 16.04 and I just performed an upgrade which broke the existing setup so I consider this a regression as well. ** Affects: openvpn (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787801 Title: openvpn does not work with ecryptfs setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1787801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724977] Re: two mouse cursors visible at the same time on rotated screen
Is the fix for this bug going to make it to 18.04 release? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724977 Title: two mouse cursors visible at the same time on rotated screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1724977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605843] Re: Kernel crashes from time to time when using ftrace
This is still not fixed in the latest ubuntu kernel - 4.4.0-38-generic #57-Ubuntu. Considering the low-impact of the fix is this going to go in future 4.4 releases? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605843 Title: Kernel crashes from time to time when using ftrace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605843] Re: Kernel crashes from time to time when using ftrace
Ping on the issue. I now also managed to trigger it while setting a very simple systemtap probe: probe kernel.function("generic_fillattr") { printf("Uid in inode: %u gid: %u\n", $inode->i_uid->val, $inode->i_gid->val); } Running this resulted in: [854807.910390] invalid opcode: [#1] SMP [854807.911398] CPU: 6 PID: 1 Comm: systemd Tainted: G OE 4.4.0-31-generic #50-Ubuntu [854807.911436] Hardware name: Dell Inc. Precision T1650/0X9M3X, BIOS A20 12/21/2015 [854807.911469] task: 88040be58000 ti: 88040be6 task.ti: 88040be6 [854807.911503] RIP: 0010:[] [] ftrace_stub+0x0/0x8 [854807.911544] RSP: 0018:88040be63e50 EFLAGS: 00010246 [854807.911569] RAX: RBX: 880405bcf410 RCX: 88040378c6c0 [854807.911611] RDX: 88040d891b60 RSI: 88040be63ec0 RDI: 88014b51dd78 [854807.911632] RBP: 88040be63e60 R08: 88014b51dd78 R09: 88040be63e20 [854807.911672] R10: 7fc4541498c0 R11: R12: 88040be63ec0 [854807.911703] R13: 88040be63ec0 R14: R15: 55de063aff00 [854807.911736] FS: 7fc4541498c0() GS:88041e38() knlGS: [854807.911771] CS: 0010 DS: ES: CR0: 80050033 [854807.911797] CR2: 7f891558de00 CR3: 000405a4e000 CR4: 001406e0 [854807.911828] Stack: [854807.911839] 81211cd5 81211da6 88040be63e80 81211fb6 [854807.911878] 880405bcf400 880405bcf400 88040be63eb0 81211ff3 [854807.911917] 00088000 7ffc05f286b0 000a 07ff [854807.911956] Call Trace: [854807.911972] [] ? generic_fillattr+0x5/0xa0 [854807.911999] [] ? vfs_getattr_nosec+0x36/0x40 [854807.912027] [] vfs_getattr+0x26/0x30 [854807.912052] [] vfs_fstat+0x33/0x60 [854807.912076] [] SYSC_newfstat+0x24/0x60 [854807.912102] [] ? do_sys_open+0x1bf/0x2a0 [854807.912129] [] SyS_newfstat+0xe/0x10 [854807.912154] [] entry_SYSCALL_64_fastpath+0x16/0x71 [854807.912183] Code: 8b 44 24 48 48 8b 7c 24 70 48 8b 74 24 68 48 8b 54 24 60 48 8b 4c 24 58 48 8b 44 24 50 48 8b 6c 24 20 48 81 c4 d0 00 00 00 e9 fd ff ff 80 00 00 00 00 9c 55 ff 74 24 18 55 48 89 e5 ff 74 24 [854807.912392] RIP [] ftrace_stub+0x0/0x8 [854807.912420] RSP -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605843 Title: Kernel crashes from time to time when using ftrace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605843] Re: Kernel crashes from time to time when using ftrace
Original report of the exact same issue: https://lkml.org/lkml/2016/5/13/327 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605843 Title: Kernel crashes from time to time when using ftrace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605843] Re: Kernel crashes from time to time when using ftrace
I think the fix for this crash is this upstream commit: 8329e818f14926a6040df86b2668568bde342ebf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605843 Title: Kernel crashes from time to time when using ftrace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605843] Re: Kernel crashes from time to time when using ftrace
Is there a way to obtain a vmlinux image for the upstream kernel as built by ubuntu (without having to compile locally) so that I can compare the disassemblies of the ftrace_stub ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605843 Title: Kernel crashes from time to time when using ftrace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605843] Re: Kernel crashes from time to time when using ftrace
I tried with the upstream kernel : nborisov@fisk:~$ uname -a Linux fisk 4.7.0-040700-generic #201607241632 SMP Sun Jul 24 20:34:30 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux In the meantime I managed to find a sequence which can trigger this 100% of the time on the ubuntu kernel. The following commands have to be one after the other: sudo trace-cmd record -p function_graph -l vfs_read -F ls sudo trace-cmd record -p function -l vfs_read -F ls ** Tags added: kernel-fixed-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605843 Title: Kernel crashes from time to time when using ftrace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605843] Re: Kernel crashes from time to time when using ftrace
So here is a disassembly of the ftrace functions: 0x8183026b:mov$0x0,%rcx 0x81830272 : callq 0x81156d80 0x81830277 : mov0x40(%rsp),%r9 0x8183027c :mov0x48(%rsp),%r8 0x81830281 :mov0x70(%rsp),%rdi 0x81830286 :mov0x68(%rsp),%rsi 0x8183028b :mov0x60(%rsp),%rdx 0x81830290 :mov0x58(%rsp),%rcx 0x81830295 :mov0x50(%rsp),%rax 0x8183029a :mov0x20(%rsp),%rbp 0x8183029f :add$0xd0,%rsp 0x818302a6 : jmpq 0x818302a8 And here is disassembly of ftrace_stub, which clearly looks broken: crash> dis ftrace_stub 10 0x818302a8 : (bad) 0x818302a9 : (bad) 0x818302aa : incl 0x0(%rax) 0x818302b0 :pushfq 0x818302b1 : push %rbp 0x818302b2 : pushq 0x18(%rsp) 0x818302b6 : push %rbp 0x818302b7 : mov%rsp,%rbp 0x818302ba : pushq 0x20(%rsp) 0x818302be : push %rbp crash> rd 0x818302a8 818302a8: 80ff So I guess the reason is that ftrace_stub somehow gets corrupted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605843 Title: Kernel crashes from time to time when using ftrace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605843] Re: Kernel crashes from time to time when using ftrace
** Attachment added: "uname-a.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605843/+attachment/4705813/+files/uname-a.log ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605843 Title: Kernel crashes from time to time when using ftrace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605843] Re: Kernel crashes from time to time when using ftrace
Dmesg as seen from the crash dump image. ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605843/+attachment/4705811/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605843 Title: Kernel crashes from time to time when using ftrace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605843] Re: Kernel crashes from time to time when using ftrace
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605843/+attachment/4705812/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605843 Title: Kernel crashes from time to time when using ftrace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605843] [NEW] Kernel crashes from time to time when using ftrace
Public bug reported: While performing some tracing suing ftrace-cmd I came across the following OOPS: [ 333.051723] invalid opcode: [#1] SMP [ 333.051742] Modules linked in: drbg ansi_cprng ctr ccm xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 arc4 bridge stp llc ebtable_filter ebtables ath9k_htc ath9k_common ath9k_hw ath mac80211 cfg80211 binfmt_misc snd_hda_codec_hdmi dcdbas dell_smm_hwmon snd_hda_codec_realtek snd_hda_codec_generic intel_rapl uvcvideo snd_hda_intel x86_pkg_temp_thermal intel_powerclamp coretemp videobuf2_vmalloc snd_hda_codec videobuf2_memops input_leds videobuf2_v4l2 snd_usb_audio crct10dif_pclmul videobuf2_core snd_hda_core v4l2_common crc32_pclmul snd_usbmidi_lib videodev snd_hwdep aesni_intel media snd_pcm aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_seq_midi snd_seq_midi_event snd_rawmidi serio_raw snd_seq snd_seq_device snd_timer lpc_ich snd ie31200_edac [ 333.051972] edac_core soundcore mei_me mei 8250_fintek mac_hid kvm_intel ip6t_REJECT nf_reject_ipv6 kvm nf_log_ipv6 irqbypass xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack iptable_filter ip_tables parport_pc x_tables ppdev lp parport autofs4 hid_apple raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic usbhid hid raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log i915 i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt fb_sys_fops e1000e ahci libahci drm ptp [ 333.052206] pps_core fjes video [ 333.052216] CPU: 1 PID: 5616 Comm: trace-cmd Not tainted 4.4.0-31-generic #50-Ubuntu [ 333.052235] Hardware name: Dell Inc. Precision T1650/0X9M3X, BIOS A15 09/09/2013 [ 333.052254] task: 8804066b1b80 ti: 88040b474000 task.ti: 88040b474000 [ 333.052272] RIP: 0010:[] [] ftrace_stub+0x0/0x8 [ 333.052296] RSP: 0018:88040b477f00 EFLAGS: 00010286 [ 333.052309] RAX: RBX: 8800d9a4ec00 RCX: 88040b477f18 [ 333.052326] RDX: 2000 RSI: 0237d690 RDI: 8800d9a4ec00 [ 333.052343] RBP: 88040b477f48 R08: 7f89df102cf8 R09: 0021 [ 333.052360] R10: 000d R11: 0246 R12: 8800d9a4ec00 [ 333.052377] R13: 0237d690 R14: 2000 R15: 0237d690 [ 333.052395] FS: 7f89df50f700() GS:88041e24() knlGS: [ 333.052414] CS: 0010 DS: ES: CR0: 80050033 [ 333.052428] CR2: 00a78d88 CR3: 0003c3542000 CR4: 001406e0 [ 333.052445] Stack: [ 333.052451] 8120d165 8120df35 7fff364487e5 [ 333.052473] eee5d05c 0006 [ 333.052494] 0008 2000 8182db32 0004 [ 333.052515] Call Trace: [ 333.052525] [] ? vfs_read+0x5/0x130 [ 333.052538] [] ? SyS_read+0x55/0xc0 [ 333.052553] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 333.052568] Code: 8b 44 24 48 48 8b 7c 24 70 48 8b 74 24 68 48 8b 54 24 60 48 8b 4c 24 58 48 8b 44 24 50 48 8b 6c 24 20 48 81 c4 d0 00 00 00 e9 fd ff ff 80 00 00 00 00 9c 55 ff 74 24 18 55 48 89 e5 ff 74 24 [ 333.052685] RIP [] ftrace_stub+0x0/0x8 [ 333.052700] RSP All code 0: 8b 44 24 48 mov0x48(%rsp),%eax 4: 48 8b 7c 24 70 mov0x70(%rsp),%rdi 9: 48 8b 74 24 68 mov0x68(%rsp),%rsi e: 48 8b 54 24 60 mov0x60(%rsp),%rdx 13: 48 8b 4c 24 58 mov0x58(%rsp),%rcx 18: 48 8b 44 24 50 mov0x50(%rsp),%rax 1d: 48 8b 6c 24 20 mov0x20(%rsp),%rbp 22: 48 81 c4 d0 00 00 00add$0xd0,%rsp 29:* e9 fd ff ff ff jmpq 0x2b <-- trapping instruction 2e: 80 00 00addb $0x0,(%rax) 31: 00 00 add%al,(%rax) 33: 9c pushfq 34: 55 push %rbp 35: ff 74 24 18 pushq 0x18(%rsp) 39: 55 push %rbp 3a: 48 89 e5mov%rsp,%rbp 3d: ff .byte 0xff 3e: 74 24 je 0x64 Code starting with the faulting instruction === 0: ff (bad) 1: ff (bad) 2: ff 80 00 00 00 00 incl 0x0(%rax) 8: 9c pushfq 9: 55 push %rbp a: ff 74 24 18 pushq 0x18(%rsp) e: 55 push %rbp f: 48 89 e5mov%rsp,%rbp 12: ff .byte