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

apport-collect 1612560

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/1612560

Title:
  4.8 rc1 segfault

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Tested the 4.8 rc1 kernel from the unstable ppa on yakkety 64 bits,
  and get some issues (not fatal)

  Linux version 4.8.0-0-generic (buildd@lgw01-12) (gcc version 6.1.1
  20160805 (Ubuntu 6.1.1-11ubuntu12) ) #1-Ubuntu SMP Thu Aug 11 17:03:49
  UTC 2016 (Ubuntu 4.8.0-0.1-generic 4.8.0 rc1 )

   NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
  kernel: unchecked MSR access error: WRMSR to 0xdf (tried to write 
0x000000ff80000001) at rIP: 0xffffffff96262124 (native_write_msr+0x4/0x20)
  kernel:  ffffffff96206a7d ffff9a083a40d000 ffff9a083fc0a380 000000000000001e
  kernel:  0000000000000000 ffffffff96206b53 ffff9a083a40d000 0000000000000000
  kernel:  ffff9a083fc0a380 ffffffff96206e71 ffffd61bffc01de0 0000000000000000
  kernel: Call Trace:
  kernel:  [<ffffffff96206a7d>] ? x86_perf_event_set_period+0xcd/0x160
  kernel:  [<ffffffff96206b53>] ? x86_pmu_start+0x43/0xf0
  kernel:  [<ffffffff96206e71>] ? x86_pmu_enable+0x271/0x2e0
  kernel:  [<ffffffff96370dad>] ? event_function+0x9d/0x160
  kernel:  [<ffffffff96371f30>] ? perf_cgroup_attach+0x70/0x70
  kernel:  [<ffffffff96371f6b>] ? remote_function+0x3b/0x40
  kernel:  [<ffffffff963038b8>] ? generic_exec_single+0x98/0x100
  kernel:  [<ffffffff963039fc>] ? smp_call_function_single+0xdc/0x180
  kernel:  [<ffffffff962d5f6a>] ? vprintk_emit+0x35a/0x520
  kernel:  [<ffffffff96377cb5>] ? event_function_call+0x115/0x120
  kernel:  [<ffffffff96377170>] ? perf_mux_hrtimer_handler+0x260/0x260
  kernel:  [<ffffffff96370d10>] ? cpu_clock_event_read+0x30/0x30
  kernel:  [<ffffffff96377dd5>] ? perf_event_enable+0x15/0x30
  kernel:  [<ffffffff9632dee5>] ? watchdog_enable+0x155/0x1f0
  kernel:  [<ffffffff962a1e9c>] ? smpboot_thread_fn+0x9c/0x180
  kernel:  [<ffffffff962a1e00>] ? __smpboot_create_thread.part.1+0xe0/0xe0
  kernel:  [<ffffffff9629ecbd>] ? kthread+0xcd/0xf0
  kernel:  [<ffffffff9681eb1f>] ? ret_from_fork+0x1f/0x40
  kernel:  [<ffffffff9629ebf0>] ? kthread_create_on_node+0x1e0/0x1e0

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to