This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1605843

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1605843

Title:
  Kernel crashes from time to time when using ftrace

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While performing some tracing suing ftrace-cmd I came across the
  following OOPS:

  [  333.051723] invalid opcode: 0000 [#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: ffff8804066b1b80 ti: ffff88040b474000 task.ti: 
ffff88040b474000
  [  333.052272] RIP: 0010:[<ffffffff818302a8>]  [<ffffffff818302a8>] 
ftrace_stub+0x0/0x8
  [  333.052296] RSP: 0018:ffff88040b477f00  EFLAGS: 00010286
  [  333.052309] RAX: 0000000000000000 RBX: ffff8800d9a4ec00 RCX: 
ffff88040b477f18
  [  333.052326] RDX: 0000000000002000 RSI: 000000000237d690 RDI: 
ffff8800d9a4ec00
  [  333.052343] RBP: ffff88040b477f48 R08: 00007f89df102cf8 R09: 
0000000000000021
  [  333.052360] R10: 000000000000000d R11: 0000000000000246 R12: 
ffff8800d9a4ec00
  [  333.052377] R13: 000000000237d690 R14: 0000000000002000 R15: 
000000000237d690
  [  333.052395] FS:  00007f89df50f700(0000) GS:ffff88041e240000(0000) 
knlGS:0000000000000000
  [  333.052414] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
  [  333.052428] CR2: 0000000000a78d88 CR3: 00000003c3542000 CR4: 
00000000001406e0
  [  333.052445] Stack:
  [  333.052451]  ffffffff8120d165 ffffffff8120df35 00007fff364487e5 
0000000000000000
  [  333.052473]  00000000eee5d05c 0000000000000000 0000000000000000 
0000000000000006
  [  333.052494]  0000000000000008 0000000000002000 ffffffff8182db32 
0000000000000004
  [  333.052515] Call Trace:
  [  333.052525]  [<ffffffff8120d165>] ? vfs_read+0x5/0x130
  [  333.052538]  [<ffffffff8120df35>] ? SyS_read+0x55/0xc0
  [  333.052553]  [<ffffffff8182db32>] 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 
ff 80 00 00 00 00 9c 55 ff 74 24 18 55 48 89 e5 ff 74 24 
  [  333.052685] RIP  [<ffffffff818302a8>] ftrace_stub+0x0/0x8
  [  333.052700]  RSP <ffff88040b477f00>

  
  All code
  ========
     0: 8b 44 24 48             mov    0x48(%rsp),%eax
     4: 48 8b 7c 24 70          mov    0x70(%rsp),%rdi
     9: 48 8b 74 24 68          mov    0x68(%rsp),%rsi
     e: 48 8b 54 24 60          mov    0x60(%rsp),%rdx
    13: 48 8b 4c 24 58          mov    0x58(%rsp),%rcx
    18: 48 8b 44 24 50          mov    0x50(%rsp),%rax
    1d: 48 8b 6c 24 20          mov    0x20(%rsp),%rbp
    22: 48 81 c4 d0 00 00 00    add    $0xd0,%rsp
    29:*        e9 fd ff ff ff          jmpq   0x2b             <-- trapping 
instruction
    2e: 80 00 00                addb   $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 e5                mov    %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 e5                mov    %rsp,%rbp
    12: ff                      .byte 0xff
    13: 74 24                   je     0x39


  The way I was running trace-cmd was:

  trace-cmd stream -p function -l vfs_read -F ls

  But the same crash occured if I ran 'trace-cmd record -p function -l
  vfs_read -F ls'

  What's interesting is this doesn't happen always but will usually occur one 
out of 10 times or so. Apparently it goes bogus in the mcount handler: 
  addr2line -e /vmlinux ffffffff818302a8
  /build/linux-dcxD3m/linux-4.4.0/arch/x86/kernel/mcount_64.S:184

  I managed to also capture a complete kernel crashdump so if you need
  any other relevant information (diassembly of relvant function) I'm
  happy to provide it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605843/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to