Bug #1667416 “PowerNV: No rate limit for kernel error “KVM can't...” : Yakkety (16.10) : Bugs : linux package : Ubuntu

Revision history for this message

bugproxy (bugproxy) wrote on 2017-02-23: kern.log

#1

kern.log Edit (476.9 KiB, application/gzip)

Default Comment by Bridge

tags:

added: architecture-ppc64le bugnameltc-151239 severity-medium targetmilestone-inin1704

Revision history for this message

bugproxy (bugproxy) wrote on 2017-02-23: output of dmesg

#2

output of dmesg Edit (68.0 KiB, application/gzip)

Default Comment by Bridge

Revision history for this message

bugproxy (bugproxy) wrote on 2017-02-23: Patch - KVM data copy error

#3

Default Comment by Bridge

Revision history for this message

bugproxy (bugproxy) wrote on 2017-02-23: Kernel debian package with fix

#4

Default Comment by Bridge

Changed in ubuntu:
assignee:	nobody → Taco Screen team (taco-screen-team)
affects:	ubuntu → linux (Ubuntu)

Revision history for this message

bugproxy (bugproxy) wrote on 2017-02-23: Patch - KVM data copy error

#5

Patch - KVM data copy error Edit (1.2 KiB, text/plain)

Default Comment by Bridge

Revision history for this message

bugproxy (bugproxy) wrote on 2017-02-23: Kernel debian package with fix

#6

Kernel debian package with fix Edit (21.9 MiB, application/vnd.debian.binary-package)

Default Comment by Bridge

Revision history for this message

Michael Hohnbaum (hohnbaum) wrote on 2017-02-23: Re: [Bug 1667416] [NEW] PowerNV: No rate limit for kernel error "KVM can't copy data from"

#7

Download full text (3.3 KiB)

Patch for the Kernel Team to evaluate.

Michael

On 02/23/2017 10:11 AM, Launchpad Bug Tracker wrote:
> bugproxy (bugproxy) has assigned this bug to you for Ubuntu:
>
> == Comment: #0 - MIKHAIL S. MEDVEDEV <email address hidden> - 2017-02-03 14:40:58 ==
> ---Problem Description---
> I am experiencing a problem with KVM on Power with a symptom of "KVM can't copy data" message being spammed to kern.log at about 100000 messages a second. Apart from original problem that triggers the error, the printk is a problem on its own. System might run out of space for logs, and would have high CPU load caused by journald.
>
> This bug is to address an absence of rate limiter on printk at
> https://github.com/torvalds/linux/blob/f64e8084c94bb0449177364856d8117e2f14c4c0/arch/powerpc/kvm/book3s_64_mmu.c#L268
>
> Maybe wrapping the printk in printk_ratelimit() is all that is required?
>
> if(printk_ratelimit()){
> printk("KVM can't copy");
> }
>
> Contact Information = Mikhail Medvedev / <email address hidden>, Rafael Folco / <email address hidden>
>
> ---uname output---
> 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
>
> Machine Type = KVM guest on P8 8247 21L
>
> ---Debugger---
> A debugger is not configured
>
> ---Steps to Reproduce---
> 1. Deploy OpenStack with devstack
> 2. Run simultaneously between 4 and 6 instances of a script that
> - boots a VM (openstack server create)
> - immediately creates the backup of the VM (openstack server backup create)
>
> This is not a very good way to reproduce it. I am still unable to
> reproduce the problem just by using libvirt and qemu.
>
>
> == Comment: #5 - VIPIN K. PARASHAR <email address hidden> - 2017-02-07 09:42:31 ==
>
> >From kernel logs
> ===========
>
> [852719.001593] KVM can't copy data from 0x3fff86683c80!
> [852719.001614] KVM can't copy data from 0x3fff86683c80!
> [852719.001617] KVM can't copy data from 0x3fff66a83c80!
> [852719.001624] KVM can't copy data from 0x3fff86683c80!
> [852719.001634] KVM can't copy data from 0x3fff86683c80!
> [852719.001637] KVM can't copy data from 0x3fff66a83c80!
> [852719.001645] KVM can't copy data from 0x3fff86683c80!
> [852719.001655] KVM can't copy data from 0x3fff86683c80!
> [852719.001658] KVM can't copy data from 0x3fff66a83c80!
> [852719.001665] KVM can't copy data from 0x3fff86683c80!
> [852719.001668] KVM can't copy data from 0x3fff66a83c80!
> [852719.001678] KVM can't copy data from 0x3fff66a83c80!
> [852719.001686] KVM can't copy data from 0x3fff86683c80!
>
>
> "KVM can't copy data from" error is being logged at very high rate
> by kernel. rate limiting this error should fix this issue.
>
>
> == Comment: #20 - VIPIN K. PARASHAR <email address hidden> - 2017-02-23 12:01:26 ==
> Fix for this is submitted to PowerPC mailing list
> and is available at below location:
>
> https://patchwork.ozlabs.org/patch/728831/
>
> It reads:
>
> "KVM: PPC: Book3S: Ratelimit copy data failure error messages"
>
> ** Affects: ubuntu
> Importance: Undecided
> Assignee: Taco Screen team (taco-screen-team)
> Status: New
>
>
> ** Tags: architecture-ppc64le bug...

Patch for the Kernel Team to evaluate.

Michael

On 02/23/2017 10:11 AM, Launchpad Bug Tracker wrote:
> bugproxy (bugproxy) has assigned this bug to you for Ubuntu:
>
> == Comment: #0 - MIKHAIL S. MEDVEDEV <mmedvede@us.ibm.com> - 2017-02-03 14:40:58 ==
> ---Problem Description---
> I am experiencing a problem with KVM on Power with a symptom of "KVM can't copy data" message being spammed to kern.log at about 100000 messages a second. Apart from original problem that triggers the error, the printk is a problem on its own. System might run out of space for logs, and would have high CPU load caused by journald.
>
> This bug is to address an absence of rate limiter on printk at
> https://github.com/torvalds/linux/blob/f64e8084c94bb0449177364856d8117e2f14c4c0/arch/powerpc/kvm/book3s_64_mmu.c#L268
>
> Maybe wrapping the printk in printk_ratelimit() is all that is required?
>
>     if(printk_ratelimit()){
>        printk("KVM can't copy");
>     }
>  
> Contact Information = Mikhail Medvedev / mmedvede@us.ibm.com, Rafael Folco / rfolco@br.ibm.com 
>  
> ---uname output---
> 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
>  
> Machine Type = KVM guest on P8 8247 21L  
>  
> ---Debugger---
> A debugger is not configured
>  
> ---Steps to Reproduce---
>  1. Deploy OpenStack with devstack
> 2. Run simultaneously between 4 and 6 instances of a script that
>     - boots a VM (openstack server create)
>     - immediately creates the backup of the VM (openstack server backup create)
>
> This is not a very good way to reproduce it. I am still unable to
> reproduce the problem just by using libvirt and qemu.
>
>
> == Comment: #5 - VIPIN K. PARASHAR <viparash@in.ibm.com> - 2017-02-07 09:42:31 ==
>
> >From kernel logs
> ===========
>
> [852719.001593] KVM can't copy data from 0x3fff86683c80!
> [852719.001614] KVM can't copy data from 0x3fff86683c80!
> [852719.001617] KVM can't copy data from 0x3fff66a83c80!
> [852719.001624] KVM can't copy data from 0x3fff86683c80!
> [852719.001634] KVM can't copy data from 0x3fff86683c80!
> [852719.001637] KVM can't copy data from 0x3fff66a83c80!
> [852719.001645] KVM can't copy data from 0x3fff86683c80!
> [852719.001655] KVM can't copy data from 0x3fff86683c80!
> [852719.001658] KVM can't copy data from 0x3fff66a83c80!
> [852719.001665] KVM can't copy data from 0x3fff86683c80!
> [852719.001668] KVM can't copy data from 0x3fff66a83c80!
> [852719.001678] KVM can't copy data from 0x3fff66a83c80!
> [852719.001686] KVM can't copy data from 0x3fff86683c80!
>
>
> "KVM can't copy data from" error is being logged at very high rate
> by kernel. rate limiting this error should fix this issue.
>
>
> == Comment: #20 - VIPIN K. PARASHAR <viparash@in.ibm.com> - 2017-02-23 12:01:26 ==
> Fix for this is submitted to PowerPC mailing list 
> and is available at below location:
>
> https://patchwork.ozlabs.org/patch/728831/
>
> It reads:
>
> "KVM: PPC: Book3S: Ratelimit copy data failure error messages"
>
> ** Affects: ubuntu
>      Importance: Undecided
>      Assignee: Taco Screen team (taco-screen-team)
>          Status: New
>
>
> ** Tags: architecture-ppc64le bugnameltc-151239 severity-medium targetmilestone-inin1704

-- 
Michael Hohnbaum
OIL Program Manager
Power (ppc64el) Development Project Manager
Canonical, Ltd.

Revision history for this message

bugproxy (bugproxy) wrote on 2017-02-23: Comment bridged from LTC Bugzilla

#8

------- Comment From <email address hidden> 2017-02-23 13:39 EDT-------
Please include this for Ubuntu 16.10, 16.04.02 along with Ubuntu 17.04 release.

Leann Ogasawara (leannogasawara) on 2017-02-23

Changed in linux (Ubuntu):
assignee:	Taco Screen team (taco-screen-team) → Canonical Kernel Team (canonical-kernel-team)
importance:	Undecided → Medium
status:	New → Triaged

Seth Forshee (sforshee) on 2017-02-24

Changed in linux (Ubuntu):
assignee:	Canonical Kernel Team (canonical-kernel-team) → Seth Forshee (sforshee)
status:	Triaged → In Progress
Changed in linux (Ubuntu Yakkety):
assignee:	nobody → Seth Forshee (sforshee)
importance:	Undecided → Medium
status:	New → In Progress

Revision history for this message

Seth Forshee (sforshee) wrote on 2017-02-24:

#9

https://lists.ubuntu.com/archives/kernel-team/2017-February/082695.html

Changed in linux (Ubuntu):
status:	In Progress → Fix Committed

Revision history for this message

bugproxy (bugproxy) wrote on 2017-02-24:

#10

Download full text (12.2 KiB)

== Comment: #0 - MIKHAIL S. MEDVEDEV <email address hidden> - 2017-02-03 14:40:58 ==
---Problem Description---
I am experiencing a problem with KVM on Power with a symptom of "KVM can't copy data" message being spammed to kern.log at about 100000 messages a second. Apart from original problem that triggers the error, the printk is a problem on its own. System might run out of space for logs, and would have high CPU load caused by journald.

This bug is to address an absence of rate limiter on printk at https://github.com/torvalds/linux/blob/f64e8084c94bb0449177364856d8117e2f14c4c0/arch/powerpc/kvm/book3s_64_mmu.c#L268

Maybe wrapping the printk in printk_ratelimit() is all that is required?

if(printk_ratelimit()){
printk("KVM can't copy");
}

Contact Information = Mikhail Medvedev / <email address hidden>, Rafael Folco / <email address hidden>

---uname output---
4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux

Machine Type = KVM guest on P8 8247 21L

---Debugger---
A debugger is not configured

---Steps to Reproduce---
1. Deploy OpenStack with devstack
2. Run simultaneously between 4 and 6 instances of a script that
- boots a VM (openstack server create)
- immediately creates the backup of the VM (openstack server backup create)

This is not a very good way to reproduce it. I am still unable to reproduce the problem just by using libvirt and qemu.

== Comment: #5 - VIPIN K. PARASHAR <email address hidden> - 2017-02-07 09:42:31 ==

From kernel logs
===========

[852719.001593] KVM can't copy data from 0x3fff86683c80!
[852719.001614] KVM can't copy data from 0x3fff86683c80!
[852719.001617] KVM can't copy data from 0x3fff66a83c80!
[852719.001624] KVM can't copy data from 0x3fff86683c80!
[852719.001634] KVM can't copy data from 0x3fff86683c80!
[852719.001637] KVM can't copy data from 0x3fff66a83c80!
[852719.001645] KVM can't copy data from 0x3fff86683c80!
[852719.001655] KVM can't copy data from 0x3fff86683c80!
[852719.001658] KVM can't copy data from 0x3fff66a83c80!
[852719.001665] KVM can't copy data from 0x3fff86683c80!
[852719.001668] KVM can't copy data from 0x3fff66a83c80!
[852719.001678] KVM can't copy data from 0x3fff66a83c80!
[852719.001686] KVM can't copy data from 0x3fff86683c80!

"KVM can't copy data from" error is being logged at very high rate
by kernel. rate limiting this error should fix this issue.

== Comment: #20 - VIPIN K. PARASHAR <email address hidden> - 2017-02-23 12:01:26 ==
Fix for this is submitted to PowerPC mailing list
and is available at below location:

https://patchwork.ozlabs.org/patch/728831/

It reads:

"KVM: PPC: Book3S: Ratelimit copy data failure error messages"

Default Comment by Bridge

Patch for the Kernel Team to evaluate.

Michael

On 02/23/2017 10:11 AM, Launchpad Bug Tracker wrote:
> bugproxy (bugproxy) has assigned this bug to you for Ubuntu:
>
> == Comment: #0 - MIKHAIL S. MEDVEDEV <email address hidden> - 2017-02-03 14:40:58 ==
> ---Problem Description---
> I am experiencing a problem with KVM on Power with a symptom of "...

== Comment: #0 - MIKHAIL S. MEDVEDEV <mmedvede@us.ibm.com> - 2017-02-03 14:40:58 ==
---Problem Description---
I am experiencing a problem with KVM on Power with a symptom of "KVM can't copy data" message being spammed to kern.log at about 100000 messages a second. Apart from original problem that triggers the error, the printk is a problem on its own. System might run out of space for logs, and would have high CPU load caused by journald.

This bug is to address an absence of rate limiter on printk at https://github.com/torvalds/linux/blob/f64e8084c94bb0449177364856d8117e2f14c4c0/arch/powerpc/kvm/book3s_64_mmu.c#L268

Maybe wrapping the printk in printk_ratelimit() is all that is required?

if(printk_ratelimit()){
printk("KVM can't copy");
}

Contact Information = Mikhail Medvedev / mmedvede@us.ibm.com, Rafael Folco / rfolco@br.ibm.com

---uname output---
4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux

Machine Type = KVM guest on P8 8247 21L

---Debugger---
A debugger is not configured

---Steps to Reproduce---
1. Deploy OpenStack with devstack
2. Run simultaneously between 4 and 6 instances of a script that
- boots a VM (openstack server create)
- immediately creates the backup of the VM (openstack server backup create)

This is not a very good way to reproduce it. I am still unable to reproduce the problem just by using libvirt and qemu.

== Comment: #5 - VIPIN K. PARASHAR <viparash@in.ibm.com> - 2017-02-07 09:42:31 ==

From kernel logs
===========

[852719.001593] KVM can't copy data from 0x3fff86683c80!
[852719.001614] KVM can't copy data from 0x3fff86683c80!
[852719.001617] KVM can't copy data from 0x3fff66a83c80!
[852719.001624] KVM can't copy data from 0x3fff86683c80!
[852719.001634] KVM can't copy data from 0x3fff86683c80!
[852719.001637] KVM can't copy data from 0x3fff66a83c80!
[852719.001645] KVM can't copy data from 0x3fff86683c80!
[852719.001655] KVM can't copy data from 0x3fff86683c80!
[852719.001658] KVM can't copy data from 0x3fff66a83c80!
[852719.001665] KVM can't copy data from 0x3fff86683c80!
[852719.001668] KVM can't copy data from 0x3fff66a83c80!
[852719.001678] KVM can't copy data from 0x3fff66a83c80!
[852719.001686] KVM can't copy data from 0x3fff86683c80!

"KVM can't copy data from" error is being logged at very high rate
by kernel. rate limiting this error should fix this issue.

== Comment: #20 - VIPIN K. PARASHAR <viparash@in.ibm.com> - 2017-02-23 12:01:26 ==
Fix for this is submitted to PowerPC mailing list
and is available at below location:

https://patchwork.ozlabs.org/patch/728831/

It reads:

"KVM: PPC: Book3S: Ratelimit copy data failure error messages"

Default Comment by Bridge

Patch for the Kernel Team to evaluate.

Michael

On 02/23/2017 10:11 AM, Launchpad Bug Tracker wrote:
> bugproxy (bugproxy) has assigned this bug to you for Ubuntu:
>
> == Comment: #0 - MIKHAIL S. MEDVEDEV <mmedvede@us.ibm.com> - 2017-02-03 14:40:58 ==
> ---Problem Description---
> I am experiencing a problem with KVM on Power with a symptom of "KVM can't copy data" message being spammed to kern.log at about 100000 messages a second. Apart from original problem that triggers the error, the printk is a problem on its own. System might run out of space for logs, and would have high CPU load caused by journald.
>
> This bug is to address an absence of rate limiter on printk at
> https://github.com/torvalds/linux/blob/f64e8084c94bb0449177364856d8117e2f14c4c0/arch/powerpc/kvm/book3s_64_mmu.c#L268
>
> Maybe wrapping the printk in printk_ratelimit() is all that is required?
>
>     if(printk_ratelimit()){
>        printk("KVM can't copy");
>     }
>
> Contact Information = Mikhail Medvedev / mmedvede@us.ibm.com, Rafael Folco / rfolco@br.ibm.com
>
> ---uname output---
> 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
>
> Machine Type = KVM guest on P8 8247 21L
>
> ---Debugger---
> A debugger is not configured
>
> ---Steps to Reproduce---
>  1. Deploy OpenStack with devstack
> 2. Run simultaneously between 4 and 6 instances of a script that
>     - boots a VM (openstack server create)
>     - immediately creates the backup of the VM (openstack server backup create)
>
> This is not a very good way to reproduce it. I am still unable to
> reproduce the problem just by using libvirt and qemu.
>
>
> == Comment: #5 - VIPIN K. PARASHAR <viparash@in.ibm.com> - 2017-02-07 09:42:31 ==
>
> >From kernel logs
> ===========
>
> [852719.001593] KVM can't copy data from 0x3fff86683c80!
> [852719.001614] KVM can't copy data from 0x3fff86683c80!
> [852719.001617] KVM can't copy data from 0x3fff66a83c80!
> [852719.001624] KVM can't copy data from 0x3fff86683c80!
> [852719.001634] KVM can't copy data from 0x3fff86683c80!
> [852719.001637] KVM can't copy data from 0x3fff66a83c80!
> [852719.001645] KVM can't copy data from 0x3fff86683c80!
> [852719.001655] KVM can't copy data from 0x3fff86683c80!
> [852719.001658] KVM can't copy data from 0x3fff66a83c80!
> [852719.001665] KVM can't copy data from 0x3fff86683c80!
> [852719.001668] KVM can't copy data from 0x3fff66a83c80!
> [852719.001678] KVM can't copy data from 0x3fff66a83c80!
> [852719.001686] KVM can't copy data from 0x3fff86683c80!
>
>
> "KVM can't copy data from" error is being logged at very high rate
> by kernel. rate limiting this error should fix this issue.
>
>
> == Comment: #20 - VIPIN K. PARASHAR <viparash@in.ibm.com> - 2017-02-23 12:01:26 ==
> Fix for this is submitted to PowerPC mailing list
> and is available at below location:
>
> https://patchwork.ozlabs.org/patch/728831/
>
> It reads:
>
> "KVM: PPC: Book3S: Ratelimit copy data failure error messages"
>
> ** Affects: ubuntu
>      Importance: Undecided
>      Assignee: Taco Screen team (taco-screen-team)
>          Status: New
>
>
> ** Tags: architecture-ppc64le bugnameltc-151239 severity-medium targetmilestone-inin1704

--
Michael Hohnbaum
OIL Program Manager
Power (ppc64el) Development Project Manager
Canonical, Ltd.

Please include this for Ubuntu 16.10, 16.04.02 along with Ubuntu 17.04 release.
== Comment: #0 - MIKHAIL S. MEDVEDEV <mmedvede@us.ibm.com> - 2017-02-03 14:40:58 ==
---Problem Description---
I am experiencing a problem with KVM on Power with a symptom of "KVM can't copy data" message being spammed to kern.log at about 100000 messages a second. Apart from original problem that triggers the error, the printk is a problem on its own. System might run out of space for logs, and would have high CPU load caused by journald.

This bug is to address an absence of rate limiter on printk at https://github.com/torvalds/linux/blob/f64e8084c94bb0449177364856d8117e2f14c4c0/arch/powerpc/kvm/book3s_64_mmu.c#L268

Maybe wrapping the printk in printk_ratelimit() is all that is required?

if(printk_ratelimit()){
printk("KVM can't copy");
}

Contact Information = Mikhail Medvedev / mmedvede@us.ibm.com, Rafael Folco / rfolco@br.ibm.com

---uname output---
4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux

Machine Type = KVM guest on P8 8247 21L

---Debugger---
A debugger is not configured

---Steps to Reproduce---
1. Deploy OpenStack with devstack
2. Run simultaneously between 4 and 6 instances of a script that
- boots a VM (openstack server create)
- immediately creates the backup of the VM (openstack server backup create)

This is not a very good way to reproduce it. I am still unable to reproduce the problem just by using libvirt and qemu.

== Comment: #5 - VIPIN K. PARASHAR <viparash@in.ibm.com> - 2017-02-07 09:42:31 ==

From kernel logs
===========

[852719.001593] KVM can't copy data from 0x3fff86683c80!
[852719.001614] KVM can't copy data from 0x3fff86683c80!
[852719.001617] KVM can't copy data from 0x3fff66a83c80!
[852719.001624] KVM can't copy data from 0x3fff86683c80!
[852719.001634] KVM can't copy data from 0x3fff86683c80!
[852719.001637] KVM can't copy data from 0x3fff66a83c80!
[852719.001645] KVM can't copy data from 0x3fff86683c80!
[852719.001655] KVM can't copy data from 0x3fff86683c80!
[852719.001658] KVM can't copy data from 0x3fff66a83c80!
[852719.001665] KVM can't copy data from 0x3fff86683c80!
[852719.001668] KVM can't copy data from 0x3fff66a83c80!
[852719.001678] KVM can't copy data from 0x3fff66a83c80!
[852719.001686] KVM can't copy data from 0x3fff86683c80!

"KVM can't copy data from" error is being logged at very high rate
by kernel. rate limiting this error should fix this issue.

== Comment: #20 - VIPIN K. PARASHAR <viparash@in.ibm.com> - 2017-02-23 12:01:26 ==
Fix for this is submitted to PowerPC mailing list
and is available at below location:

https://patchwork.ozlabs.org/patch/728831/

It reads:

"KVM: PPC: Book3S: Ratelimit copy data failure error messages"

Default Comment by Bridge

Patch for the Kernel Team to evaluate.

Michael

On 02/23/2017 10:11 AM, Launchpad Bug Tracker wrote:
> bugproxy (bugproxy) has assigned this bug to you for Ubuntu:
>
> == Comment: #0 - MIKHAIL S. MEDVEDEV <mmedvede@us.ibm.com> - 2017-02-03 14:40:58 ==
> ---Problem Description---
> I am experiencing a problem with KVM on Power with a symptom of "KVM can't copy data" message being spammed to kern.log at about 100000 messages a second. Apart from original problem that triggers the error, the printk is a problem on its own. System might run out of space for logs, and would have high CPU load caused by journald.
>
> This bug is to address an absence of rate limiter on printk at
> https://github.com/torvalds/linux/blob/f64e8084c94bb0449177364856d8117e2f14c4c0/arch/powerpc/kvm/book3s_64_mmu.c#L268
>
> Maybe wrapping the printk in printk_ratelimit() is all that is required?
>
>     if(printk_ratelimit()){
>        printk("KVM can't copy");
>     }
>
> Contact Information = Mikhail Medvedev / mmedvede@us.ibm.com, Rafael Folco / rfolco@br.ibm.com
>
> ---uname output---
> 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
>
> Machine Type = KVM guest on P8 8247 21L
>
> ---Debugger---
> A debugger is not configured
>
> ---Steps to Reproduce---
>  1. Deploy OpenStack with devstack
> 2. Run simultaneously between 4 and 6 instances of a script that
>     - boots a VM (openstack server create)
>     - immediately creates the backup of the VM (openstack server backup create)
>
> This is not a very good way to reproduce it. I am still unable to
> reproduce the problem just by using libvirt and qemu.
>
>
> == Comment: #5 - VIPIN K. PARASHAR <viparash@in.ibm.com> - 2017-02-07 09:42:31 ==
>
> >From kernel logs
> ===========
>
> [852719.001593] KVM can't copy data from 0x3fff86683c80!
> [852719.001614] KVM can't copy data from 0x3fff86683c80!
> [852719.001617] KVM can't copy data from 0x3fff66a83c80!
> [852719.001624] KVM can't copy data from 0x3fff86683c80!
> [852719.001634] KVM can't copy data from 0x3fff86683c80!
> [852719.001637] KVM can't copy data from 0x3fff66a83c80!
> [852719.001645] KVM can't copy data from 0x3fff86683c80!
> [852719.001655] KVM can't copy data from 0x3fff86683c80!
> [852719.001658] KVM can't copy data from 0x3fff66a83c80!
> [852719.001665] KVM can't copy data from 0x3fff86683c80!
> [852719.001668] KVM can't copy data from 0x3fff66a83c80!
> [852719.001678] KVM can't copy data from 0x3fff66a83c80!
> [852719.001686] KVM can't copy data from 0x3fff86683c80!
>
>
> "KVM can't copy data from" error is being logged at very high rate
> by kernel. rate limiting this error should fix this issue.
>
>
> == Comment: #20 - VIPIN K. PARASHAR <viparash@in.ibm.com> - 2017-02-23 12:01:26 ==
> Fix for this is submitted to PowerPC mailing list
> and is available at below location:
>
> https://patchwork.ozlabs.org/patch/728831/
>
> It reads:
>
> "KVM: PPC: Book3S: Ratelimit copy data failure error messages"
>
> ** Affects: ubuntu
>      Importance: Undecided
>      Assignee: Taco Screen team (taco-screen-team)
>          Status: New
>
>
> ** Tags: architecture-ppc64le bugnameltc-151239 severity-medium targetmilestone-inin1704

--
Michael Hohnbaum
OIL Program Manager
Power (ppc64el) Development Project Manager
Canonical, Ltd.

Please include this for Ubuntu 16.10, 16.04.02 along with Ubuntu 17.04 release.

Brad Figg (brad-figg) on 2017-03-01

Changed in linux (Ubuntu Yakkety):
status:	In Progress → Fix Committed

Revision history for this message

bugproxy (bugproxy) wrote on 2017-03-01:

#11

------- Comment From <email address hidden> 2017-02-28 23:31 EDT-------
(In reply to comment #20)
> Fix for this is submitted to PowerPC mailing list
> and is available at below location:
>
> https://patchwork.ozlabs.org/patch/728831/
>
> It reads:
>
> "KVM: PPC: Book3S: Ratelimit copy data failure error messages"

Fix is accepted upstream as commit 4da934dc6515afa

4da934dc65 - KVM: PPC: Book3S PR: Ratelimit copy data failure error messages

Revision history for this message

Launchpad Janitor (janitor) wrote on 2017-03-08:

#12

Download full text (14.0 KiB)

This bug was fixed in the package linux - 4.10.0-11.13

---------------
linux (4.10.0-11.13) zesty; urgency=low

[ Tim Gardner ]

* Release Tracking Bug
- LP: #1669127

* linux-tools-common should Depends: lsb-release (LP: #1667571)
- [Config] linux-tools-common depends on lsb-release

  * Ubuntu (Zesty): When we miss LSI/INTx interrupts on slot, message is too
    imprecise (LP: #1668382)
    - of/irq: improve error report on irq discovery process failure

  * Zesty update to v4.10.1 stable release (LP: #1668993)
    - ptr_ring: fix race conditions when resizing
    - ip: fix IP_CHECKSUM handling
    - net: socket: fix recvmmsg not returning error from sock_error
    - tty: serial: msm: Fix module autoload
    - USB: serial: mos7840: fix another NULL-deref at open
    - USB: serial: cp210x: add new IDs for GE Bx50v3 boards
    - USB: serial: ftdi_sio: fix modem-status error handling
    - USB: serial: ftdi_sio: fix extreme low-latency setting
    - USB: serial: ftdi_sio: fix line-status over-reporting
    - USB: serial: spcp8x5: fix modem-status handling
    - USB: serial: opticon: fix CTS retrieval at open
    - USB: serial: ark3116: fix register-accessor error handling
    - USB: serial: console: fix uninitialised spinlock
    - x86/platform/goldfish: Prevent unconditional loading
    - goldfish: Sanitize the broken interrupt handler
    - netfilter: nf_ct_helper: warn when not applying default helper assignment
    - ACPICA: Linuxize: Restore and fix Intel compiler build
    - block: fix double-free in the failure path of cgwb_bdi_init()
    - rtlwifi: rtl_usb: Fix for URB leaking when doing ifconfig up/down
    - xfs: clear delalloc and cache on buffered write failure
    - Linux 4.10.1

  * [UBUNTU Zesty] mlx5 - Improve OVS offload driver (LP: #1668019)
    - net/sched: cls_flower: Disallow duplicate internal elements
    - net/sched: cls_flower: Properly handle classifier flags dumping
    - net/sched: cls_matchall: Dump the classifier flags
    - net/sched: Reflect HW offload status
    - net/sched: cls_flower: Reflect HW offload status
    - net/sched: cls_matchall: Reflect HW offloading status
    - net/sched: cls_u32: Reflect HW offload status
    - net/sched: cls_bpf: Reflect HW offload status
    - net/mlx5: Push min-inline mode resolution helper into the core
    - IB/mlx5: Enable Eth VFs to query their min-inline value for user-space
    - net/mlx5: Use exact encap header size for the FW input buffer
    - net/mlx5e: Add TC offloads matching on IPv6 encapsulation headers
    - net/mlx5e: TC ipv4 tunnel encap offload cosmetic changes
    - net/mlx5e: Use the full tunnel key info for encapsulation offload house- keeping
    - net/mlx5e: Maximize ip tunnel key usage on the TC offloading path
    - net/mlx5e: Support SRIOV TC encapsulation offloads for IPv6 tunnels
    - net/mlx5: E-Switch, Enlarge the FDB size for the switchdev mode
    - net/mlx5: Fix static checker warnings

  * [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups
    (LP: #1470250)
    - SAUCE: Tools: hv: vss: Thaw the filesystem and continue after freeze fails

* Ubuntu17.04: Need more patches for aacraid to bring up Bost...

This bug was fixed in the package linux - 4.10.0-11.13

---------------
linux (4.10.0-11.13) zesty; urgency=low

[ Tim Gardner ]

* Release Tracking Bug
    - LP: #1669127

* linux-tools-common should Depends: lsb-release (LP: #1667571)
    - [Config] linux-tools-common depends on lsb-release

* Ubuntu (Zesty): When we miss LSI/INTx interrupts on slot, message is too
    imprecise (LP: #1668382)
    - of/irq: improve error report on irq discovery process failure

* Zesty update to v4.10.1 stable release (LP: #1668993)
    - ptr_ring: fix race conditions when resizing
    - ip: fix IP_CHECKSUM handling
    - net: socket: fix recvmmsg not returning error from sock_error
    - tty: serial: msm: Fix module autoload
    - USB: serial: mos7840: fix another NULL-deref at open
    - USB: serial: cp210x: add new IDs for GE Bx50v3 boards
    - USB: serial: ftdi_sio: fix modem-status error handling
    - USB: serial: ftdi_sio: fix extreme low-latency setting
    - USB: serial: ftdi_sio: fix line-status over-reporting
    - USB: serial: spcp8x5: fix modem-status handling
    - USB: serial: opticon: fix CTS retrieval at open
    - USB: serial: ark3116: fix register-accessor error handling
    - USB: serial: console: fix uninitialised spinlock
    - x86/platform/goldfish: Prevent unconditional loading
    - goldfish: Sanitize the broken interrupt handler
    - netfilter: nf_ct_helper: warn when not applying default helper assignment
    - ACPICA: Linuxize: Restore and fix Intel compiler build
    - block: fix double-free in the failure path of cgwb_bdi_init()
    - rtlwifi: rtl_usb: Fix for URB leaking when doing ifconfig up/down
    - xfs: clear delalloc and cache on buffered write failure
    - Linux 4.10.1

* [UBUNTU Zesty] mlx5 - Improve OVS offload driver  (LP: #1668019)
    - net/sched: cls_flower: Disallow duplicate internal elements
    - net/sched: cls_flower: Properly handle classifier flags dumping
    - net/sched: cls_matchall: Dump the classifier flags
    - net/sched: Reflect HW offload status
    - net/sched: cls_flower: Reflect HW offload status
    - net/sched: cls_matchall: Reflect HW offloading status
    - net/sched: cls_u32: Reflect HW offload status
    - net/sched: cls_bpf: Reflect HW offload status
    - net/mlx5: Push min-inline mode resolution helper into the core
    - IB/mlx5: Enable Eth VFs to query their min-inline value for user-space
    - net/mlx5: Use exact encap header size for the FW input buffer
    - net/mlx5e: Add TC offloads matching on IPv6 encapsulation headers
    - net/mlx5e: TC ipv4 tunnel encap offload cosmetic changes
    - net/mlx5e: Use the full tunnel key info for encapsulation offload house- keeping
    - net/mlx5e: Maximize ip tunnel key usage on the TC offloading path
    - net/mlx5e: Support SRIOV TC encapsulation offloads for IPv6 tunnels
    - net/mlx5: E-Switch, Enlarge the FDB size for the switchdev mode
    - net/mlx5: Fix static checker warnings

* [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups
    (LP: #1470250)
    - SAUCE: Tools: hv: vss: Thaw the filesystem and continue after freeze fails

* Ubuntu17.04: Need more patches for aacraid to bring up Boston System
    (LP: #1668726)
    - scsi: aacraid: Remove duplicate irq management code
    - scsi: aacraid: Added aacraid.h include guard
    - scsi: aacraid: added support for init_struct_8
    - scsi: aacraid: Added sa firmware support
    - scsi: aacraid: Retrieve and update the device types
    - scsi: aacraid: Reworked scsi command submission path
    - scsi: aacraid: Process Error for response I/O
    - scsi: aacraid: Added support for response path
    - scsi: aacraid: Added support for read medium error
    - scsi: aacraid: Reworked aac_command_thread
    - scsi: aacraid: Added support for periodic wellness sync
    - scsi: aacraid: Retrieve Queue Depth from Adapter FW
    - scsi: aacraid: Added support to set QD of attached drives
    - scsi: aacraid: Added support for hotplug
    - scsi: aacraid: Include HBA direct interface
    - scsi: aacraid: Add task management functionality
    - scsi: aacraid: Added support to abort cmd and reset lun
    - scsi: aacraid: VPD 83 type3 support
    - scsi: aacraid: Added new IWBR reset
    - scsi: aacraid: Added ioctl to trigger IOP/IWBR reset
    - scsi: aacraid: Retrieve HBA host information ioctl
    - scsi: aacraid: Update copyrights
    - scsi: aacraid: Change Driver Version Prefix
    - scsi: aacraid: update version
    - scsi: aacraid: rcode is unsigned and should be signed int
    - scsi: aacraid: avoid open-coded upper_32_bits
    - scsi: aacraid: Fix camel case
    - scsi: aacraid: Use correct channel number for raw srb
    - scsi: aacraid: Fix for excessive prints on EEH
    - scsi: aacraid: Prevent E3 lockup when deleting units
    - scsi: aacraid: Fix memory leak in fib init path
    - scsi: aacraid: Added sysfs for driver version
    - scsi: aacraid: Fix sync fibs time out on controller reset
    - scsi: aacraid: Skip wellness sync on controller failure
    - scsi: aacraid: Reload offlined drives after controller reset
    - scsi: aacraid: Decrease adapter health check interval
    - scsi: aacraid: Skip IOP reset on controller panic(SMART Family)
    - scsi: aacraid: Reorder Adapter status check
    - scsi: aacraid: Save adapter fib log before an IOP reset
    - scsi: aacraid: Fix a potential spinlock double unlock bug
    - scsi: aacraid: Update driver version
    - scsi: aacraid: Fixed expander hotplug for SMART family

* Ubuntu 17.04: "Oops: Exception in kernel mode, sig: 5 [#1]" seen during
    fadump over ssh on Alpine machine. (LP: #1655241)
    - Revert "UBUNTU: SAUCE: powerpc/fadump: set an upper limit for boot memory size"
    - SAUCE: powerpc/fadump: set an upper limit for boot memory size (V2)

* CAPI:Ubuntu: Kernel panic while rebooting (LP: #1667599)
    - pci/hotplug/pnv-php: Remove WARN_ON() in pnv_php_put_slot()
    - pci/hotplug/pnv-php: Disable surprise hotplug capability on conflicts
    - pci/hotplug/pnv-php: Disable MSI and PCI device properly

* Nvlink2: Additional patches (LP: #1667081)
    - powerpc/powernv: Initialise nest mmu
    - powerpc/powernv: Use OPAL call for TCE kill on NVLink2
    - powerpc/mm: refactor radix physical page mapping
    - powerpc/mm: add radix__create_section_mapping()
    - powerpc/mm: add radix__remove_section_mapping()
    - powerpc/mm: unstub radix__vmemmap_remove_mapping()
    - [Config] Enforce CONFIG_MOVABLE_NODE=y for ppc64el

* PowerNV: No rate limit for kernel error "KVM can't copy data from"
    (LP: #1667416)
    - SAUCE: KVM: PPC: Book3S: Ratelimit copy data failure error messages

* Please disable unnecessary config options in the Ubuntu 17.04 kernel config
    (LP: #1667490)
    - [Config] Disable experimental IMA options

* POWER9: AST: Improve AST 2500 support (LP: #1667424)
    - SAUCE: drm/ast: Handle configuration without P2A bridge
    - SAUCE: drm/ast: const'ify mode setting tables
    - SAUCE: drm/ast: Remove spurrious include
    - SAUCE: drm/ast: Fix calculation of MCLK
    - SAUCE: drm/ast: Base support for AST2500
    - SAUCE: drm/ast: Fixed vram size incorrect issue on POWER
    - SAUCE: drm/ast: Factor mmc_test code in POST code
    - SAUCE: drm/ast: Rename ast_init_dram_2300 to ast_post_chip_2300
    - SAUCE: drm/ast: POST code for the new AST2500
    - SAUCE: drm/ast: Fix test for VGA enabled
    - SAUCE: drm/ast: Call open_key before enable_mmio in POST code

* POWER9: Additional patches for 17.04 and 16.04.2 (LP: #1667116)
    - powerpc/mm: Update PROTFAULT handling in the page fault path
    - powerpc/mm/radix: Update pte update sequence for pte clear case
    - powerpc/mm/radix: Use ptep_get_and_clear_full when clearing pte for full mm
    - powerpc/mm/radix: Skip ptesync in pte update helpers
    - SAUCE: powerpc/mm/hash: Always clear UPRT and Host Radix bits when setting up CPU

* POWER9: Improve PMU capabilites (LP: #1667413)
    - powerpc/perf: use is_kernel_addr macro in perf_get_misc_flags()
    - powerpc/perf: Avoid FAB_*_MATCH checks for power9
    - powerpc/perf: Add restrictions to PMC5 in power9 DD1
    - powerpc/perf: Use Instruction Counter value
    - powerpc/perf: Use PM_INST_DISP for generic instructions sample
    - powerpc/perf: Add alternative event table and function for power9
    - powerpc/perf: Add PM_INST_DISP event to Power9 event list
    - powerpc/perf: Factor out event_alternative function

* Miscellaneous Ubuntu changes
    - [Config] CONFIG_QCOM_FALKOR_ERRATUM_1009=y
    - [Config] CONFIG_QCOM_L2_PMU=y
    - [Config] CONFIG_QCOM_FALKOR_ERRATUM_1003=y
    - ubuntu: vbox -- Update to 5.1.14-dfsg-2

* Miscellaneous upstream changes
    - arm64: errata: Provide macro for major and minor cpu revisions
    - arm64: Define Falkor v1 CPU
    - arm64: Use __tlbi() macros in KVM code
    - arm64: Work around Falkor erratum 1009
    - perf: add qcom l2 cache perf events driver
    - arm64: arch_timer: document Hisilicon erratum 161010101
    - arm64: Work around Falkor erratum 1003
    - ACPI/IORT: Fix iort_node_get_id() mapping entries indexing
    - net: qcom/emac: add ethtool support
    - Revert "net: qcom/emac: configure the external phy to allow pause frames"
    - net: qcom/emac: rename emac_phy to emac_sgmii and move it
    - net: qcom/emac: claim the irq only when the device is opened
    - net: qcom/emac: display the phy driver info after we connect
    - net: qcom/emac: always use autonegotiation to configure the SGMII link
    - net: qcom/emac: do not call emac_mac_start twice
    - net: qcom/emac: remove extraneous wake-on-lan code
    - net: qcom/emac: add an error interrupt handler for the sgmii
    - net: qcom/emac: add ethool support for setting pause parameters
    - net: qcom/emac: fix semicolon.cocci warnings
    - net: qcom/emac: add ethtool support for reading hardware registers
    - net: qcom/emac: add ethtool support for setting ring parameters
    - net: qcom/emac: fix a sizeof() typo

linux (4.10.0-10.12) zesty; urgency=low

[ Tim Gardner ]

* Release Tracking Bug
    - LP: #1666636

* POWER9 : Enable Stop 0-2 with ESL=EC=0 (LP: #1666197)
    - powernv:idle: Add IDLE_STATE_ENTER_SEQ_NORET macro
    - powernv:stop: Rename pnv_arch300_idle_init to pnv_power9_idle_init
    - cpuidle:powernv: Add helper function to populate powernv idle states.
    - powernv: Pass PSSCR value and mask to power9_idle_stop
    - Documentation:powerpc: Add device-tree bindings for power-mgt

* ecryptfs fails to load block cipher on ppc64el  (LP: #1666483)
    - [Config] CONFIG_CRYPTO_DEV_VMX=n

* [ubuntu 16.10] Enable OPTPROBES for powerpc (LP: #1585741)
    - powerpc/bpf: Introduce __PPC_SH64()
    - powerpc: Add helper to check if offset is within relative branch range
    - powerpc/kprobes: Fixes for kprobe_lookup_name() on BE
    - powerpc/kprobes: Implement Optprobes
    - powerpc/kprobes: Optimize kprobe in kretprobe_trampoline()

* Miscellaneous Ubuntu changes
    - [Config] CONFIG_QCOM_IRQ_COMBINER=y
    - [Config] CONFIG_ARM_ARCH_TIMER_OOL_WORKAROUND=y
    - [Config] CONFIG_HISILICON_ERRATUM_161010101=y

* Miscellaneous upstream changes
    - ACPI: Generic GSI: Do not attempt to map non-GSI IRQs during bus scan
    - ACPI: Add support for ResourceSource/IRQ domain mapping
    - irqchip/qcom: Add IRQ combiner driver
    - clocksource/drivers/arm_arch_timer: Add dt binding for hisilicon-161010101 erratum
    - clocksource/drivers/arm_arch_timer: Remove fsl-a008585 parameter
    - clocksource/drivers/arm_arch_timer: Introduce generic errata handling infrastructure
    - clocksource/drivers/arm_arch_timer: Work around Hisilicon erratum 161010101
    - iommu/dma: Allow MSI-only cookies
    - iommu: Rename iommu_dm_regions into iommu_resv_regions
    - iommu: Add a new type field in iommu_resv_region
    - iommu: iommu_alloc_resv_region
    - iommu: Only map direct mapped regions
    - iommu: iommu_get_group_resv_regions
    - iommu: Implement reserved_regions iommu-group sysfs file
    - iommu/vt-d: Implement reserved region get/put callbacks
    - iommu/amd: Declare MSI and HT regions as reserved IOVA regions
    - iommu/arm-smmu: Implement reserved region get/put callbacks
    - iommu/arm-smmu-v3: Implement reserved region get/put callbacks
    - irqdomain: Add irq domain MSI and MSI_REMAP flags
    - genirq/msi: Set IRQ_DOMAIN_FLAG_MSI on MSI domain creation
    - irqdomain: irq_domain_check_msi_remap
    - irqchip/gicv3-its: Sets IRQ_DOMAIN_FLAG_MSI_REMAP
    - vfio/type1: Allow transparent MSI IOVA allocation
    - vfio/type1: Check MSI remapping at irq domain level
    - iommu/arm-smmu: Do not advertise IOMMU_CAP_INTR_REMAP anymore
    - iommu/arm-smmu-v3: Clear prior settings when updating STEs
    - iommu/arm-smmu-v3: limit use of 2-level stream tables
    - iommu/arm-smmu: Support for Extended Stream ID (16 bit)
    - iommu/arm-smmu: Fix for ThunderX erratum #27704

linux (4.10.0-9.11) zesty; urgency=low

[ Tim Gardner ]

* Release Tracking Bug
    - LP: #1666214

* linux: disable CONFIG_PCIEPORTBUS in the kernel (LP: #1665404)
    - [Config] CONFIG_PCIEPORTBUS=n for ppc64el

* linux-lts-xenial 4.4.0-63.84~14.04.2 ADT test failure with linux-lts-xenial
    4.4.0-63.84~14.04.2 (LP: #1664912)
    - SAUCE: apparmor: fix link auditing failure due to, uninitialized var

* Ubuntu 17.04: "Oops: Exception in kernel mode, sig: 5 [#1]" seen during
    fadump over ssh on Alpine machine. (LP: #1655241)
    - SAUCE: powerpc/fadump: set an upper limit for boot memory size

* In Ubuntu 17.04 : after reboot getting message in console like Unable to
    open file: /etc/keys/x509_ima.der (-2) (LP: #1656908)
    - SAUCE: ima: Downgrade error to warning

* NFS client : permission denied when trying to access subshare, since kernel
    4.4.0-31 (LP: #1649292)
    - fs: Better permission checking for submounts

* Miscellaneous Ubuntu changes
    - SAUCE: (noup) Update spl to 0.6.5.9-1, zfs to 0.6.5.9-2
    - [Config] CONFIG_SCSI_HISI_SAS=m on arm64
    - d-i: Add hisi_sas_v2_hw to scsi-modules
    - d-i: Add hns_enet_drv to nic-modules
    - d-i: Add supporting modules for hns_enet_drv to nic-modules
    - rebase to v4.10

[ Upstream Kernel Changes ]

* rebase to v4.10

-- Seth Forshee <seth.forshee@canonical.com>  Thu, 23 Feb 2017 12:32:41 -0600

Changed in linux (Ubuntu):
status:	Fix Committed → Fix Released

Revision history for this message

Thadeu Lima de Souza Cascardo (cascardo) wrote on 2017-03-21:

#13

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed-yakkety'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: verification-needed-yakkety

Mikhail S Medvedev (msmedved) on 2017-03-23

tags:

added: verification-failed-yakkety
removed: verification-needed-yakkety

Revision history for this message

Mikhail S Medvedev (msmedved) wrote on 2017-03-23:

#14

The latest kernel from yakkety-proposed does not appear to fix the problem. Note that I did test it on Xenial, not Yakkety, because I do not have an easy way to reproduce the bug that excercises rate-limited printk on Yakkety.

I made sure that the proposed kernel was used by comparing what is getting installed on Yakkety vs Xenial:

On Yakkety
==========

$ sudo apt-get install -y linux-image-generic/yakkety-proposed

Selected version '4.8.0.44.56' (Ubuntu:16.10/yakkety-proposed [ppc64el]) for 'linux-image-generic'
The following additional packages will be installed:
  crda iw libnl-3-200 libnl-genl-3-200 linux-firmware linux-image-4.8.0-44-generic
  linux-image-extra-4.8.0-44-generic wireless-regdb
Suggested packages:
  fdutils linux-doc-4.8.0 | linux-source-4.8.0 linux-tools linux-headers-4.8.0-44-generic
The following NEW packages will be installed:
  crda iw libnl-3-200 libnl-genl-3-200 linux-firmware linux-image-4.8.0-44-generic
  linux-image-extra-4.8.0-44-generic linux-image-generic wireless-regdb

# uname -a
Linux mmedvede2-test-ratelimit-pkvmci836 4.8.0-44-generic #47-Ubuntu SMP Wed Mar 22 14:27:02 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

On Xenial
=========

$ sudo apt-get install -y linux-image-generic/yakkety-proposed
Selected version '4.8.0.44.56' (Ubuntu:16.10/yakkety-proposed [ppc64el]) for 'linux-image-generic'
The following additional packages will be installed:
  linux-image-4.8.0-44-generic linux-image-extra-4.8.0-44-generic
Suggested packages:
  fdutils linux-doc-4.8.0 | linux-source-4.8.0 linux-tools linux-headers-4.8.0-44-generic
The following NEW packages will be installed:
  linux-image-4.8.0-44-generic linux-image-extra-4.8.0-44-generic
The following packages will be upgraded:
  linux-image-generic

$ uname -a
Linux mmedvede-test-ratelimit-pkvmci8361 4.8.0-44-generic #47-Ubuntu SMP Wed Mar 22 14:27:02 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

And I was able to reproduce the printk spam on Xenial with the proposed kernel. Did the fix actually get into 4.8.0.44.56?

The latest kernel from yakkety-proposed does not appear to fix the problem. Note that I did test it on Xenial, not Yakkety, because I do not have an easy way to reproduce the bug that excercises rate-limited printk on Yakkety.

I made sure that the proposed kernel was used by comparing what is getting installed on Yakkety vs Xenial:

On Yakkety
==========

$ sudo apt-get install -y linux-image-generic/yakkety-proposed

Selected version '4.8.0.44.56' (Ubuntu:16.10/yakkety-proposed [ppc64el]) for 'linux-image-generic'
The following additional packages will be installed:
  crda iw libnl-3-200 libnl-genl-3-200 linux-firmware linux-image-4.8.0-44-generic
  linux-image-extra-4.8.0-44-generic wireless-regdb
Suggested packages:
  fdutils linux-doc-4.8.0 | linux-source-4.8.0 linux-tools linux-headers-4.8.0-44-generic
The following NEW packages will be installed:
  crda iw libnl-3-200 libnl-genl-3-200 linux-firmware linux-image-4.8.0-44-generic
  linux-image-extra-4.8.0-44-generic linux-image-generic wireless-regdb

# uname -a
Linux mmedvede2-test-ratelimit-pkvmci836 4.8.0-44-generic #47-Ubuntu SMP Wed Mar 22 14:27:02 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

On Xenial
=========

$ sudo apt-get install -y linux-image-generic/yakkety-proposed
Selected version '4.8.0.44.56' (Ubuntu:16.10/yakkety-proposed [ppc64el]) for 'linux-image-generic'
The following additional packages will be installed:
  linux-image-4.8.0-44-generic linux-image-extra-4.8.0-44-generic
Suggested packages:
  fdutils linux-doc-4.8.0 | linux-source-4.8.0 linux-tools linux-headers-4.8.0-44-generic
The following NEW packages will be installed:
  linux-image-4.8.0-44-generic linux-image-extra-4.8.0-44-generic
The following packages will be upgraded:
  linux-image-generic

$ uname -a
Linux mmedvede-test-ratelimit-pkvmci8361 4.8.0-44-generic #47-Ubuntu SMP Wed Mar 22 14:27:02 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

And I was able to reproduce the printk spam on Xenial with the proposed kernel. Did the fix actually get into 4.8.0.44.56?

Revision history for this message

Seth Forshee (sforshee) wrote on 2017-03-23:

#15

No, it didn't. There was a regression in a recent update, and the kernel that was in -proposed got replaced with one that only has the reverts necessary to fix the regression. That's the kernel you tested.

Sorry for the confusion. I'll remove the verification tags, and once a new kernel with the fix is in -proposed there will be another comment asking for testing.

tags:

removed: verification-failed-yakkety

Revision history for this message

Kleber Sacilotto de Souza (kleber-souza) wrote on 2017-04-13:

#16

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed-yakkety'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: verification-needed-yakkety

Revision history for this message

Mikhail S Medvedev (msmedved) wrote on 2017-04-13:

#17

I have triggered the error while using kernel image from proposed repository:

2017-04-13 21:55:41.868 | Selected version '4.8.0.48.60' (Ubuntu:16.10/yakkety-proposed [ppc64el]) for 'linux-image-generic'
$ uname -a
Linux mmedvede-test-ratelimit-pkvmci8401 4.8.0-48-generic #51-Ubuntu SMP Wed Apr 12 12:59:15 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

And confirmed that the printk is now ratelimited. From kernel log:

[ 1725.561053] kvmppc_mmu_book3s_64_xlate: 282675 callbacks suppressed
[ 1725.561057] KVM: Can't copy data from 0x3fff8b7bbc80!
[ 1725.561068] KVM: Can't copy data from 0x3fff8b7bbc80!
[ 1725.561078] KVM: Can't copy data from 0x3fff8b7bbc80!
[ 1725.561088] KVM: Can't copy data from 0x3fff8b7bbc80!
[ 1725.561099] KVM: Can't copy data from 0x3fff8b7bbc80!
[ 1725.561109] KVM: Can't copy data from 0x3fff8b7bbc80!
[ 1725.561119] KVM: Can't copy data from 0x3fff8b7bbc80!
[ 1725.561130] KVM: Can't copy data from 0x3fff8b7bbc80!
[ 1725.561140] KVM: Can't copy data from 0x3fff8b7bbc80!
[ 1725.561150] KVM: Can't copy data from 0x3fff8b7bbc80!

tags:

added: verification-done-yakkety
removed: verification-needed-yakkety

Revision history for this message

Launchpad Janitor (janitor) wrote on 2017-04-24:

#18

Download full text (14.5 KiB)

This bug was fixed in the package linux - 4.8.0-49.52

---------------
linux (4.8.0-49.52) yakkety; urgency=low

* linux: 4.8.0-49.52 -proposed tracker (LP: #1684427)

  * [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
    (LP: #1682561)
    - Drivers: hv: util: move waiting for release to hv_utils_transport itself

linux (4.8.0-48.51) yakkety; urgency=low

* linux: 4.8.0-48.51 -proposed tracker (LP: #1682034)

  * [Hyper-V] hv: vmbus: Raise retry/wait limits in vmbus_post_msg()
    (LP: #1681893)
    - Drivers: hv: vmbus: Raise retry/wait limits in vmbus_post_msg()

linux (4.8.0-47.50) yakkety; urgency=low

* linux: 4.8.0-47.50 -proposed tracker (LP: #1679678)

* CVE-2017-6353
- sctp: deny peeloff operation on asocs with threads sleeping on it

* CVE-2017-5986
- sctp: avoid BUG_ON on sctp_wait_for_sndbuf

* vfat: missing iso8859-1 charset (LP: #1677230)
- [Config] NLS_ISO8859_1=y

* [Hyper-V] pci-hyperv: Use device serial number as PCI domain (LP: #1667527)
- net/mlx4_core: Use cq quota in SRIOV when creating completion EQs

* Regression: KVM modules should be on main kernel package (LP: #1678099)
- [Config] powerpc: Add kvm-hv and kvm-pr to the generic inclusion list

  * linux-lts-xenial 4.4.0-63.84~14.04.2 ADT test failure with linux-lts-xenial
    4.4.0-63.84~14.04.2 (LP: #1664912)
    - SAUCE: apparmor: fix link auditing failure due to, uninitialized var

* regession tests failing after stackprofile test is run (LP: #1661030)
- SAUCE: fix regression with domain change in complain mode

  * Permission denied and inconsistent behavior in complain mode with 'ip netns
    list' command (LP: #1648903)
    - SAUCE: fix regression with domain change in complain mode

  * unexpected errno=13 and disconnected path when trying to open /proc/1/ns/mnt
    from a unshared mount namespace (LP: #1656121)
    - SAUCE: apparmor: null profiles should inherit parent control flags

  * apparmor refcount leak of profile namespace when removing profiles
    (LP: #1660849)
    - SAUCE: apparmor: fix ns ref count link when removing profiles from policy

  * tor in lxd: apparmor="DENIED" operation="change_onexec"
    namespace="root//CONTAINERNAME_<var-lib-lxd>" profile="unconfined"
    name="system_tor" (LP: #1648143)
    - SAUCE: apparmor: Fix no_new_privs blocking change_onexec when using stacked
      namespaces

* apparmor oops in bind_mnt when dev_path lookup fails (LP: #1660840)
- SAUCE: apparmor: fix oops in bind_mnt when dev_path lookup fails

  * apparmor auditing denied access of special apparmor .null fi\ le
    (LP: #1660836)
    - SAUCE: apparmor: Don't audit denied access of special apparmor .null file

* apparmor label leak when new label is unused (LP: #1660834)
- SAUCE: apparmor: fix label leak when new label is unused

* apparmor reference count bug in label_merge_insert() (LP: #1660833)
- SAUCE: apparmor: fix reference count bug in label_merge_insert()

* apparmor's raw_data file in securityfs is sometimes truncated (LP: #1638996)
- SAUCE: apparmor: fix replacement race in reading rawdata

* unix domain socket cross permission check failing with n...

This bug was fixed in the package linux - 4.8.0-49.52

---------------
linux (4.8.0-49.52) yakkety; urgency=low

* linux: 4.8.0-49.52 -proposed tracker (LP: #1684427)

* [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
    (LP: #1682561)
    - Drivers: hv: util: move waiting for release to hv_utils_transport itself

linux (4.8.0-48.51) yakkety; urgency=low

* linux: 4.8.0-48.51 -proposed tracker (LP: #1682034)

* [Hyper-V] hv: vmbus: Raise retry/wait limits in vmbus_post_msg()
    (LP: #1681893)
    - Drivers: hv: vmbus: Raise retry/wait limits in vmbus_post_msg()

linux (4.8.0-47.50) yakkety; urgency=low

* linux: 4.8.0-47.50 -proposed tracker (LP: #1679678)

* CVE-2017-6353
    - sctp: deny peeloff operation on asocs with threads sleeping on it

* CVE-2017-5986
    - sctp: avoid BUG_ON on sctp_wait_for_sndbuf

* vfat: missing iso8859-1 charset (LP: #1677230)
    - [Config] NLS_ISO8859_1=y

* [Hyper-V] pci-hyperv: Use device serial number as PCI domain (LP: #1667527)
    - net/mlx4_core: Use cq quota in SRIOV when creating completion EQs

* Regression: KVM modules should be on main kernel package (LP: #1678099)
    - [Config] powerpc: Add kvm-hv and kvm-pr to the generic inclusion list

* linux-lts-xenial 4.4.0-63.84~14.04.2 ADT test failure with linux-lts-xenial
    4.4.0-63.84~14.04.2 (LP: #1664912)
    - SAUCE: apparmor: fix link auditing failure due to, uninitialized var

* regession tests failing after stackprofile test is run (LP: #1661030)
    - SAUCE: fix regression with domain change in complain mode

* Permission denied and inconsistent behavior in complain mode with 'ip netns
    list' command (LP: #1648903)
    - SAUCE: fix regression with domain change in complain mode

* unexpected errno=13 and disconnected path when trying to open /proc/1/ns/mnt
    from a unshared mount namespace (LP: #1656121)
    - SAUCE: apparmor: null profiles should inherit parent control flags

* apparmor refcount leak of profile namespace when removing profiles
    (LP: #1660849)
    - SAUCE: apparmor: fix ns ref count link when removing profiles from policy

* tor in lxd: apparmor="DENIED" operation="change_onexec"
    namespace="root//CONTAINERNAME_<var-lib-lxd>" profile="unconfined"
    name="system_tor" (LP: #1648143)
    - SAUCE: apparmor: Fix no_new_privs blocking change_onexec when using stacked
      namespaces

* apparmor oops in bind_mnt when dev_path lookup fails (LP: #1660840)
    - SAUCE: apparmor: fix oops in bind_mnt when dev_path lookup fails

* apparmor  auditing denied access of special apparmor .null fi\ le
    (LP: #1660836)
    - SAUCE: apparmor: Don't audit denied access of special apparmor .null file

* apparmor label leak when new label is unused (LP: #1660834)
    - SAUCE: apparmor: fix label leak when new label is unused

* apparmor reference count bug in label_merge_insert() (LP: #1660833)
    - SAUCE: apparmor: fix reference count bug in label_merge_insert()

* apparmor's raw_data file in securityfs is sometimes truncated (LP: #1638996)
    - SAUCE: apparmor: fix replacement race in reading rawdata

* unix domain socket cross permission check failing with nested namespaces
    (LP: #1660832)
    - SAUCE: apparmor: fix cross ns perm of unix domain sockets

* [Hyper-V][Mellanox] net/mlx4_core: Avoid delays during VF driver device
    shutdown (LP: #1672785)
    - Revert "net/mlx4_en: Avoid unregister_netdev at shutdown flow"
    - net/mlx4_core: Avoid delays during VF driver device shutdown

* Update ENA driver to 1.1.2 from net-next (LP: #1664312)
    - net: ena: Remove unnecessary pci_set_drvdata()
    - net: ena: Fix error return code in ena_device_init()
    - net: ena: change the return type of ena_set_push_mode() to be void.
    - net: ena: use setup_timer() and mod_timer()
    - net/ena: remove ntuple filter support from device feature list
    - net/ena: fix queues number calculation
    - net/ena: fix ethtool RSS flow configuration
    - net/ena: fix RSS default hash configuration
    - net/ena: fix NULL dereference when removing the driver after device reset
      failed
    - net/ena: refactor ena_get_stats64 to be atomic context safe
    - net/ena: fix potential access to freed memory during device reset
    - net/ena: use READ_ONCE to access completion descriptors
    - net/ena: reduce the severity of ena printouts
    - net/ena: change driver's default timeouts
    - net/ena: change condition for host attribute configuration
    - net/ena: update driver version to 1.1.2

* ISST-LTE:pVM:roselp4:ubuntu16.04.2: number of numa_miss and numa_foreign
    wrong in numastat (LP: #1672953)
    - mm: fix remote numa hits statistics
    - mm: get rid of __GFP_OTHER_NODE

* Using an NVMe drive causes huge power drain (LP: #1664602)
    - nvme/scsi: Remove power management support
    - nvme: Pass pointers, not dma addresses, to nvme_get/set_features()
    - nvme: introduce struct nvme_request
    - nvme: Add a quirk mechanism that uses identify_ctrl
    - nvme: Enable autonomous power state transitions

* POWER9: Additional patches for TTY and CPU_IDLE (LP: #1674325)
    - tty: Fix ldisc crash on reopened tty
    - SAUCE: powerpc/powernv/cpuidle: Pass correct drv->cpumask for registration

* Ubuntu 16.10: Network checksum fixes needed for IPoIB for Mellanox CX4/CX5
    card (LP: #1670247)
    - Revert "powerpc: port 64 bits pgtable_cache to 32 bits"
    - powerpc/Makefile: Drop CONFIG_WORD_SIZE for BITS
    - powerpc: port 64 bits pgtable_cache to 32 bits
    - [Config] CONFIG_WORD_SIZE disappeared
    - powerpc/64: Fix checksum folding in csum_tcpudp_nofold and
      ip_fast_csum_nofold
    - powerpc/64: Use optimized checksum routines on little-endian
    - CONFIG_GENERIC_CSUM=n for ppc64el
    - powerpc/64: Fix checksum folding in csum_add()

* [Hyper-V] Rebase Hyper-V to the upstream 4.10 kernel (LP: #1670544)
    - PCI: hv: Use device serial number as PCI domain
    - PCI: hv: Fix wslot_to_devfn() to fix warnings on device removal
    - PCI: hv: Use the correct buffer size in new_pcichild_device()
    - scsi: storvsc: Payload buffer incorrectly sized for 32 bit kernels.
    - hv_netvsc: remove excessive logging on MTU change
    - net: centralize net_device min/max MTU checking
    - net: deprecate eth_change_mtu, remove usage
    - net: use core MTU range checking in virt drivers
    - hv_netvsc: fix a race between netvsc_send() and netvsc_init_buf()
    - net: use core MTU range checking in virt drivers
    - tools: hv: fix a compile warning in snprintf
    - tools: hv: remove unnecessary header files and netlink related code
    - vmbus: add support for dynamic device id's
    - Drivers: hv: utils: reduce HV_UTIL_NEGO_TIMEOUT timeout
    - Drivers: hv: utils: Fix the mapping between host version and protocol to use
    - Drivers: hv: vss: Improve log messages.
    - hv: change clockevents unbind tactics
    - Drivers: hv: balloon: Disable hot add when CONFIG_MEMORY_HOTPLUG is not set
    - Drivers: hv: balloon: Fix info request to show max page count
    - Drivers: hv: balloon: Add logging for dynamic memory operations
    - [Config] CONFIG_UIO_HV_GENERIC=m
    - uio-hv-generic: new userspace i/o driver for VMBus
    - hyperv: Fix spelling of HV_UNKOWN
    - Drivers: hv: ring_buffer: count on wrap around mappings in
      get_next_pkt_raw() (v2)
    - ethernet: use net core MTU range checking in more drivers

* Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v
    2012r2 Gen2 VM (LP: #1674635)
    - scsi: storvsc: Workaround for virtual DVD SCSI version

* Enable lspcon on i915 (LP: #1676747)
    - drm: Helper for lspcon in drm_dp_dual_mode
    - drm/i915: Add lspcon support for I915 driver
    - drm/i915: Parse VBT data for lspcon
    - drm/i915: Enable lspcon initialization
    - drm/i915: Add lspcon resume function

* stress_smoke_test passing and exiting rc=9 (linux 4.9.0-12.13 ADT test
    failure with linux 4.9.0-12.13) (LP: #1658633)
    - ext4: lock the xattr block before checksuming it

* ip_rcv_finish() NULL pointer kernel panic (LP: #1672470)
    - (upstream) bridge: drop netfilter fake rtable unconditionally

* dm-queue-length module is not included in installer/initramfs (LP: #1673350)
    - d-i: Also add dm-queue-length to multipath modules

* Broadcom bluetooth modules sometimes fail to initialize (LP: #1483101)
    - Bluetooth: btbcm: Add a delay for module reset

* Need support of Broadcom bluetooth device [413c:8143] (LP: #1166113)
    - Bluetooth: btusb: Add support for 413c:8143

* Unable to Connect Third HDD via USB Hub (LP: #1663991)
    - mm/slub.c: fix random_seq offset destruction

* POWER9 : Enable Stop 0-2 with ESL=EC=0 (LP: #1666197)
    - powernv:idle: Add IDLE_STATE_ENTER_SEQ_NORET macro
    - powernv:stop: Rename pnv_arch300_idle_init to pnv_power9_idle_init
    - cpuidle:powernv: Add helper function to populate powernv idle states.
    - powernv: Pass PSSCR value and mask to power9_idle_stop
    - Documentation:powerpc: Add device-tree bindings for power-mgt
    - powerpc/powernv: Fix bug due to labeling ambiguity in power_enter_stop

* Nvlink2: Additional patches (LP: #1667081)
    - mm: enable CONFIG_MOVABLE_NODE on non-x86 arches
    - of/fdt: mark hotpluggable memory
    - dt: add documentation of "hotpluggable" memory property
    - powerpc/mm: Fix memory hotplug BUG() on radix
    - powerpc/powernv: Initialise nest mmu
    - powerpc/powernv: Use OPAL call for TCE kill on NVLink2
    - powerpc/mm: refactor radix physical page mapping
    - powerpc/mm: add radix__create_section_mapping()
    - powerpc/mm: add radix__remove_section_mapping()
    - powerpc/mm: unstub radix__vmemmap_remove_mapping()
    - [Config] Update CONFIG_MOVABLE_NODE values and annotations
    - [Config] CONFIG_MOVABLE_NODE=n for s390x

* FC Adapter (LPe32000-based) prints "iotag out of range", goes offline, and
    delays boot a lot (Ubuntu17.04/Emulex/lpfc)) (LP: #1670490)
    - scsi: lpfc: Correct WQ creation for pagesize
    - scsi: lpfc: Add missing memory barrier

* CIFS: Call echo service immediately after socket reconnect (LP: #1669941)
    - Call echo service immediately after socket reconnect

* Kernel: Fix Transactional memory config typo (LP: #1669023)
    - powerpc/process: Fix CONFIG_ALIVEC typo in restore_tm_state()

* h-prod does not function across cores (LP: #1670726)
    - KVM: PPC: Book3S HV: Fix H_PROD to actually wake the target vcpu

* [Hyper-V] Missing PCI patches breaking SR-IOV hot remove (LP: #1670518)
    - PCI: hv: Fix hv_pci_remove() for hot-remove
    - PCI: hv: Delete the device earlier from hbus->children for hot-remove
    - PCI: hv: Make unnecessarily global IRQ masking functions static
    - PCI: hv: Allocate physically contiguous hypercall params buffer

* move aufs.ko from -extra to linux-image package (LP: #1673498)
    - [config] aufs.ko moved to linux-image package

* POWER9: Improve CAS negotiation (LP: #1671169)
    - powerpc: Parse the command line before calling CAS
    - powerpc: Add missing error check to prom_find_boot_cpu()
    - powerpc/pseries: Advertise HPT resizing support via CAS
    - powerpc/64: Disable use of radix under a hypervisor
    - powerpc/pseries: Advertise Hot Plug Event support to firmware
    - powerpc: Update to new option-vector-5 format for CAS

* Power9 kernel: add virtualization patches (LP: #1670800)
    - powerpc/fadump: Set core e_flags using kernel's ELF ABI version
    - powerpc/sparse: Add more assembler prototypes
    - powerpc/pasemi: Fix Nemo SB600 i8259 interrupts.
    - powerpc/pasemi: Fix device_type of Nemo SB600 node.
    - powerpc/pseries: Use H_CLEAR_HPT to clear MMU hash table during kexec
    - powerpc/pseries: Move CMO code from plapr_wrappers.h to platforms/pseries
    - powerpc: Fix old style declaration GCC warnings
    - powerpc/pseries: add definitions for new H_SIGNAL_SYS_RESET hcall
    - powerpc/prom: Define structs for client architecture vectors
    - powerpc/prom: Switch to using structs for ibm_architecture_vec
    - tracing: Have the reg function allow to fail
    - powerpc: port 64 bits pgtable_cache to 32 bits
    - powerpc/64: Don't try to use radix MMU under a hypervisor
    - powerpc/pseries: Fixes for the "ibm,architecture-vec-5" options
    - powerpc/64: Enable use of radix MMU under hypervisor on POWER9

* lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
    (LP: #1619918)
    - btrfs: fix btrfs_compat_ioctl failures on non-compat ioctls

* linux-tools-common should Depends: lsb-release (LP: #1667571)
    - [Config] linux-tools-common depends on lsb-release

* CAPI:Ubuntu: Kernel panic while rebooting (LP: #1667599)
    - pci/hotplug/pnv-php: Remove WARN_ON() in pnv_php_put_slot()

* Add Use-After-Free Patch for Ubuntu16.10 - EEH on BELL3 adapter fails to
    recover (serial/tty) (LP: #1669153)
    - 8250_pci: Fix potential use-after-free in error path

* Request to backport cxlflash patches to Xenial SRU stream (LP: #1623750)
    - scsi: cxlflash: Scan host only after the port is ready for I/O
    - scsi: cxlflash: Fix to avoid EEH and host reset collisions
    - scsi: cxlflash: Improve EEH recovery time

* FlashGT Integration and Setup: fsbmc30: After 17th reboot of soft bootme,
    HTX & Linux errors seen with 256 virtual LUNs (LP: #1667239)
    - cxl: Fix coredump generation when cxl_get_fd() is used

* POWER9: Additional patches for 17.04 and 16.04.2 (LP: #1667116)
    - powerpc/mm: Update PROTFAULT handling in the page fault path
    - powerpc/mm/radix: Update pte update sequence for pte clear case
    - powerpc/mm/radix: Use ptep_get_and_clear_full when clearing pte for full mm
    - powerpc/mm/radix: Skip ptesync in pte update helpers
    - SAUCE: powerpc/mm/hash: Always clear UPRT and Host Radix bits when setting
      up CPU

* [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups
    (LP: #1470250)
    - Drivers: hv: vss: Operation timeouts should match host expectation
    - SAUCE: Tools: hv: vss: Thaw the filesystem and continue after freeze fails

* PowerNV: No rate limit for kernel error "KVM can't copy data from"
    (LP: #1667416)
    - SAUCE: KVM: PPC: Book3S: Ratelimit copy data failure error messages

* kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop (LP: #1666421)
    - rtlwifi: rtl_usb: Fix missing entry in USB driver's private data

* Export symbol "dev_pm_qos_update_user_latency_tolerance" (LP: #1666401)
    - PM / QoS: Export dev_pm_qos_update_user_latency_tolerance

* Linux ZFS port doesn't respect RLIMIT_FSIZE (LP: #1656259)
    - SAUCE: (noup) Update zfs to 0.6.5.8-0ubuntu4.2

-- Stefan Bader <stefan.bader@canonical.com>  Thu, 20 Apr 2017 09:38:36 +0200

Changed in linux (Ubuntu Yakkety):
status:	Fix Committed → Fix Released

Ubuntu
linux package

PowerNV: No rate limit for kernel error "KVM can't copy data from"

Bug Description

CVE References

Other bug subscribers

Bug attachments

Remote bug watches

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Fix Released	Medium	Seth Forshee
	Yakkety	Fix Released	Medium	Seth Forshee

Ubuntulinux package

PowerNV: No rate limit for kernel error "KVM can't copy data from"

Bug Description

CVE References

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package