from:"Leonardo"

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1788098/+attachment/5241805/+files/WifiSyslog.txt

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+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

[Kernel-packages] [Bug 1788098] ProcPpc64.tar.gz

apport information

** Attachment added: "ProcPpc64.tar.gz"
   
https://bugs.launchpad.net/bugs/1788098/+attachment/5241803/+files/ProcPpc64.tar.gz

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+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

[Kernel-packages] [Bug 1788098] nvram.gz

apport information

** Attachment added: "nvram.gz"
   https://bugs.launchpad.net/bugs/1788098/+attachment/5241806/+files/nvram.gz

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+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

[Kernel-packages] [Bug 1788098] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1788098/+attachment/5241804/+files/UdevDb.txt

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+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

[Kernel-packages] [Bug 1788098] DeviceTree.tar.gz

apport information

** Attachment added: "DeviceTree.tar.gz"
   
https://bugs.launchpad.net/bugs/1788098/+attachment/5241796/+files/DeviceTree.tar.gz

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+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

[Kernel-packages] [Bug 1788098] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1788098/+attachment/5241799/+files/ProcCpuinfoMinimal.txt

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+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

[Kernel-packages] [Bug 1788098] ProcMisc.txt

apport information

** Attachment added: "ProcMisc.txt"
   
https://bugs.launchpad.net/bugs/1788098/+attachment/5241801/+files/ProcMisc.txt

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+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

[Kernel-packages] [Bug 1788098] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1788098/+attachment/5241802/+files/ProcModules.txt

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+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

[Kernel-packages] [Bug 1788098] OpalElog.tar.gz

apport information

** Attachment added: "OpalElog.tar.gz"
   
https://bugs.launchpad.net/bugs/1788098/+attachment/5241798/+files/OpalElog.tar.gz

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+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

[Kernel-packages] [Bug 1788098] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1788098/+attachment/5241797/+files/Lspci.txt

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+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

[Kernel-packages] [Bug 1788098] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1788098/+attachment/5241795/+files/CurrentDmesg.txt

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+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

[Kernel-packages] [Bug 1788098] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1788098/+attachment/5241800/+files/ProcInterrupts.txt

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+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

[Kernel-packages] [Bug 1788098] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1788098/+attachment/5241794/+files/CRDA.txt

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+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

[Kernel-packages] [Bug 1788098] .sys.firmware.opal.msglog.txt

apport information

** Attachment added: ".sys.firmware.opal.msglog.txt"
   
https://bugs.launchpad.net/bugs/1788098/+attachment/5241793/+files/.sys.firmware.opal.msglog.txt

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+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

[Kernel-packages] [Bug 1788098] Re: Avoid migration issues with aligned 2MB THB

ProblemType: Bug
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Feb 26 08:00 seq
 crw-rw 1 root audio 116, 33 Feb 26 08:00 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=/dev/mapper/rhel_zzfp368h-swap
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Package: linux (not installed)
PciMultimedia:
 
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:
 
ProcKernelCmdLine: root=/dev/mapper/rhel_zzfp368h-root ro quiet splash
ProcLoadAvg: 10.92 2.60 0.86 1/1347 9348
ProcLocks:
 1: POSIX  ADVISORY  WRITE 3540 00:17:577 0 EOF
 2: FLOCK  ADVISORY  WRITE 3320 00:17:555 0 EOF
 3: POSIX  ADVISORY  WRITE 3628 00:17:610 0 EOF
 4: POSIX  ADVISORY  WRITE 1743 00:17:351 0 EOF
 5: FLOCK  ADVISORY  WRITE 3621 00:17:605 0 EOF
ProcSwaps:
 Filename   TypeSizeUsedPriority
 /dev/dm-1   partition  166460800   
-2
ProcVersion: Linux version 4.15.0-45-generic (buildd@bos02-ppc64el-005) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #48-Ubuntu SMP Tue Jan 29 16:27:02 UTC 
2019
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-45-generic N/A
 linux-backports-modules-4.15.0-45-generic  N/A
 linux-firmware 1.173.3
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags:  bionic
Uname: Linux 4.15.0-45-generic ppc64le
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
VarLogDump_list:
 total 36888
 -r--r- 1 root root 9520107 Feb 25 15:11 
FSPDUMP.13C63FW.0A0F.20190225210916
 -r--r- 1 root root 9556523 Feb 25 15:11 
FSPDUMP.13C63FW.1A0F.20190225211018
 -r--r- 1 root root 9642286 Feb 26 08:00 
FSPDUMP.13C63FW.2A0F.20190226135913
 -r--r- 1 root root 9041963 Feb 25 15:11 
FSPDUMP.13C63FW.7A0E.20190225203903
_MarkForUpload: False
cpu_cores: Number of cores present = 40
cpu_coreson: Number of cores online = 40
cpu_dscr: DSCR is 16
cpu_freq:
 min:   3.499 GHz (cpu 159)
 max:   3.500 GHz (cpu 2)
 avg:   3.499 GHz
cpu_runmode:
 Could not retrieve current diagnostics mode,
 No kernel interface to firmware
cpu_smt: SMT=4


** Tags added: apport-collected bionic

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+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

[Kernel-packages] [Bug 1810108] Re: Failure to boot as QEMU guest when using -device virtio-vga, virgl=true

2019-01-13 Thread Leonardo Müller

I can no longer reproduce this with newer Xubuntu Bionic Daily images,
the guest is booting normally with 4.15.0-43.

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

Title:
  Failure to boot as QEMU guest when using -device virtio-vga,virgl=true

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installed Xubuntu 18.04 in a QEMU virtual machine using -device
  virtio-vga,virgl=true fails to boot. Even setting to output boot
  messages to a serial console no messages appear as if it never tried
  to boot at all.

  What makes this strange is that the live media works correctly using
  -device virtio-vga,virgl=true, but then, on reboot, the installed
  system fails to boot.

  To make the guest work it's required to remove the option ,virgl=true
  from the command line.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  Date: Sun Dec 30 17:33:21 2018
  InstallationDate: Installed on 2018-12-30 (0 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20181230)
  IwConfig:
   ens2  no wireless extensions.
   
   lono wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcFB: 0 virtiodrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=15c2a9cf-1159-4e4a-a06c-68ad2ad82d12 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-4.0
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-4.0
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810108/+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

[Kernel-packages] [Bug 1810108] [NEW] Failure to boot as QEMU guest when using -device virtio-vga, virgl=true

2018-12-30 Thread Leonardo Müller

Public bug reported:

Installed Xubuntu 18.04 in a QEMU virtual machine using -device virtio-
vga,virgl=true fails to boot. Even setting to output boot messages to a
serial console no messages appear as if it never tried to boot at all.

What makes this strange is that the live media works correctly using
-device virtio-vga,virgl=true, but then, on reboot, the installed system
fails to boot.

To make the guest work it's required to remove the option ,virgl=true
from the command line.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-43-generic 4.15.0-43.46
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: XFCE
Date: Sun Dec 30 17:33:21 2018
InstallationDate: Installed on 2018-12-30 (0 days ago)
InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20181230)
IwConfig:
 ens2  no wireless extensions.
 
 lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcFB: 0 virtiodrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=15c2a9cf-1159-4e4a-a06c-68ad2ad82d12 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-43-generic N/A
 linux-backports-modules-4.15.0-43-generic  N/A
 linux-firmware 1.173.3
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/06/2015
dmi.bios.vendor: EFI Development Kit II / OVMF
dmi.bios.version: 0.0.0
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-4.0
dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-4.0
dmi.sys.vendor: QEMU

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  Failure to boot as QEMU guest when using -device virtio-vga,virgl=true

Status in linux package in Ubuntu:
  New

Bug description:
  Installed Xubuntu 18.04 in a QEMU virtual machine using -device
  virtio-vga,virgl=true fails to boot. Even setting to output boot
  messages to a serial console no messages appear as if it never tried
  to boot at all.

  What makes this strange is that the live media works correctly using
  -device virtio-vga,virgl=true, but then, on reboot, the installed
  system fails to boot.

  To make the guest work it's required to remove the option ,virgl=true
  from the command line.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  Date: Sun Dec 30 17:33:21 2018
  InstallationDate: Installed on 2018-12-30 (0 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20181230)
  IwConfig:
   ens2  no wireless extensions.
   
   lono wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcFB: 0 virtiodrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=15c2a9cf-1159-4e4a-a06c-68ad2ad82d12 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-4.0
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-4.0
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1799102] Re: WARNING on boot in Intel GVT-g guest

2018-12-08 Thread Leonardo Müller

What causes this WARNING is the host kernel.

Using latest drm-tip (d63c50f2b014037b43c1c0f108c61e0a31ede3c1) in the
host, there is no WARNING in the guest, while the WARNING happens when
the host uses 4.18.0-12 (HWE 18.04 Edge). 4.15.0-42 does not support
iGVT-g with dma-buf, so it's not useful to test.

It seems the results weren't dependent of the Linux kernel version on
the guest: they were the same with 4.18.0-11, 4.18.0-12 and 4.19.5.

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

Title:
  WARNING on boot in Intel GVT-g guest

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When booting Ubuntu Cosmic Cuttlefish 18.10 in an Intel GVT-g Virtual
  Machine, a kernel WARNING appears in dmesg, with the following:

  [3.563734] WARNING: CPU: 3 PID: 346 at
  drivers/gpu/drm/i915/i915_irq.c:161 gen3_assert_iir_is_zero+0x38/0xa0
  [i915]

  I have not noticed negative effects in the VM, but a kernel WARNING
  probably has relevance.

  While I added a custom EDID to fix resolution, the WARNING happens
  without custom EDID set too. I will add information about the host in
  the next message.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: User Name 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1896 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 19:44:44 2018
  InstallationDate: Installed on 2018-10-18 (3 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   ens8  no wireless extensions.
  Lsusb:
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 003: ID 46f4:0002  
   Bus 002 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=6cb7fc66-eb2c-4203-9d7d-2aa2665911ac ro quiet splash 
drm.edid_firmware=EDID_E1941.bin log_buf_len=16M vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-3.0
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.0:cvnQEMU:ct1:cvrpc-i440fx-3.0:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-3.0
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799102/+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

[Kernel-packages] [Bug 1798165] Re: Vulkan applications cause permanent memory leak with Intel GPU

2018-11-15 Thread Leonardo Müller

How should I test the Cosmic Cuttlefish proposed kernel? I don't want to
upgrade my install, currently 18.04 LTS, to 18.10, which has only 9
months support.

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

Title:
  Vulkan applications cause permanent memory leak with Intel GPU

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  
  == SRU Justification ==
  Vulkan applications, as Dota 2 and DXVK games cause a memory leak where
  memory is never freed and can cause a system crash if the applications are
  used for long enough. Certain applications can make the leak be as high as
  10 MB/minute.

  This commit has been cc'd to upstream stable, but it has not landed in
  Bionic or Cosmic as of yet.

  Details about the upstream bug can be seen at:
  https://github.com/doitsujin/dxvk/issues/632
  https://bugs.freedesktop.org/show_bug.cgi?id=107899

  == Fix ==
  337fe9f5c1e7 ("drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set")

  == Regression Potential ==
  Low.  This commit has been cc'd to stable, so it has had additional
  upstream review.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  Vulkan applications, as Dota 2 and DXVK games cause a memory leak
  where memory is never freed and can cause a system crash if the
  applications are used for long enough. Certain applications can make
  the leak be as high as 10 MB/minute.

  Details about this bug can be seen at
  https://github.com/doitsujin/dxvk/issues/632 and
  https://bugs.freedesktop.org/show_bug.cgi?id=107899

  This bug was fixed in 4.19-rc6 and was backported to 4.14 and 4.18.
  The particular commit is:

  commit a2cef7d049f07995406b403605119a54881daf15
  Author: Jason Ekstrand 
  Date:   Wed Sep 26 02:17:03 2018 -0500

  drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set

  commit 337fe9f5c1e7de1f391c6a692531379d2aa2ee11 upstream.

  We attempt to get fences earlier in the hopes that everything will
  already have fences and no callbacks will be needed.  If we do succeed
  in getting a fence, getting one a second time will result in a duplicate
  ref with no unref.  This is causing memory leaks in Vulkan applications
  that create a lot of fences; playing for a few hours can, apparently,
  bring down the system.

  Cc: sta...@vger.kernel.org
  Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107899
  Reviewed-by: Chris Wilson 
  Signed-off-by: Jason Ekstrand 
  Signed-off-by: Sean Paul 
  Link: 
https://patchwork.freedesktop.org/patch/msgid/20180926071703.15257-1-jason.ekstr...@intel.com
  Signed-off-by: Greg Kroah-Hartman 

  On Ubuntu 18.04 with 4.15.0-36 it appears in slabtop as:
  https://i.imgur.com/qMAvuwl.png

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario4655 F pulseaudio
   /dev/snd/seq:usuario4640 F timidity
  CurrentDesktop: XFCE
  Date: Tue Oct 16 14:16:54 2018
  HibernationDevice: RESUME=UUID=0946602f-3ca2-4379-9012-7a5171928de7
  InstallationDate: Installed on 2017-06-13 (489 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 
kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 intel_iommu=on iommu=pt 
i915.enable_gvt=1 i915.fastboot=1 
resume=UUID=0946602f-3ca2-4379-9012-7a5171928de7 mtrr_gran_size=2M 
mtrr_chunk_size=64M cgroup_enable=memory swapaccount=1 zswap.enabled=1 
log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (361 days ago)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias:

[Kernel-packages] [Bug 1798165] Re: Vulkan applications cause permanent memory leak with Intel GPU

2018-11-15 Thread Leonardo Müller

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  Vulkan applications cause permanent memory leak with Intel GPU

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  
  == SRU Justification ==
  Vulkan applications, as Dota 2 and DXVK games cause a memory leak where
  memory is never freed and can cause a system crash if the applications are
  used for long enough. Certain applications can make the leak be as high as
  10 MB/minute.

  This commit has been cc'd to upstream stable, but it has not landed in
  Bionic or Cosmic as of yet.

  Details about the upstream bug can be seen at:
  https://github.com/doitsujin/dxvk/issues/632
  https://bugs.freedesktop.org/show_bug.cgi?id=107899

  == Fix ==
  337fe9f5c1e7 ("drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set")

  == Regression Potential ==
  Low.  This commit has been cc'd to stable, so it has had additional
  upstream review.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  Vulkan applications, as Dota 2 and DXVK games cause a memory leak
  where memory is never freed and can cause a system crash if the
  applications are used for long enough. Certain applications can make
  the leak be as high as 10 MB/minute.

  Details about this bug can be seen at
  https://github.com/doitsujin/dxvk/issues/632 and
  https://bugs.freedesktop.org/show_bug.cgi?id=107899

  This bug was fixed in 4.19-rc6 and was backported to 4.14 and 4.18.
  The particular commit is:

  commit a2cef7d049f07995406b403605119a54881daf15
  Author: Jason Ekstrand 
  Date:   Wed Sep 26 02:17:03 2018 -0500

  drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set

  commit 337fe9f5c1e7de1f391c6a692531379d2aa2ee11 upstream.

  We attempt to get fences earlier in the hopes that everything will
  already have fences and no callbacks will be needed.  If we do succeed
  in getting a fence, getting one a second time will result in a duplicate
  ref with no unref.  This is causing memory leaks in Vulkan applications
  that create a lot of fences; playing for a few hours can, apparently,
  bring down the system.

  Cc: sta...@vger.kernel.org
  Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107899
  Reviewed-by: Chris Wilson 
  Signed-off-by: Jason Ekstrand 
  Signed-off-by: Sean Paul 
  Link: 
https://patchwork.freedesktop.org/patch/msgid/20180926071703.15257-1-jason.ekstr...@intel.com
  Signed-off-by: Greg Kroah-Hartman 

  On Ubuntu 18.04 with 4.15.0-36 it appears in slabtop as:
  https://i.imgur.com/qMAvuwl.png

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario4655 F pulseaudio
   /dev/snd/seq:usuario4640 F timidity
  CurrentDesktop: XFCE
  Date: Tue Oct 16 14:16:54 2018
  HibernationDevice: RESUME=UUID=0946602f-3ca2-4379-9012-7a5171928de7
  InstallationDate: Installed on 2017-06-13 (489 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 
kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 intel_iommu=on iommu=pt 
i915.enable_gvt=1 i915.fastboot=1 
resume=UUID=0946602f-3ca2-4379-9012-7a5171928de7 mtrr_gran_size=2M 
mtrr_chunk_size=64M cgroup_enable=memory swapaccount=1 zswap.enabled=1 
log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (361 days ago)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias:

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

2018-11-03 Thread Leonardo Müller

I shutdown and turned on the computer using this kernel four times and
in none the problem happened. With the default Bionic kernel the failure
on boot would have happened twice.

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

Title:
  QCA9377 isn't being recognized sometimes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, the Wireless Network Card QCA9377 is not recognized on
  boot. This caused, on prior versions, a kernel panic at boot. With
  Bionic, the system boots but is unable to use wireless network. On
  dmesg there are messages like:

  [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd
  [2.808640] usb 1-7: device descriptor read/64, error -71
  [3.044337] usb 1-7: device descriptor read/64, error -71
  [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd
  [3.408245] usb 1-7: device descriptor read/64, error -71
  [3.644244] usb 1-7: device descriptor read/64, error -71
  [3.752193] usb usb1-port7: attempt power cycle
  [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd
  [4.404904] usb 1-7: Device not responding to setup address.
  [4.612478] usb 1-7: Device not responding to setup address.
  [4.820588] usb 1-7: device not accepting address 9, error -71
  [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd
  [4.949109] usb 1-7: Device not responding to setup address.
  [5.156893] usb 1-7: Device not responding to setup address.
  [5.364589] usb 1-7: device not accepting address 10, error -71
  [5.364655] usb usb1-port7: unable to enumerate USB device

  And lspci and lsusb don't show the wireless network card. The
  alternative is to turn the system off. Reboot don't work and reboot to
  Windows 10 also don't. The system must be powered off to restore
  functionality. Then, on the next boot, it works properly.

  However, after the system is turned off, it may cause the issue again.
  This is not 100% consistent, but mostly it cycles between powering off
  and powering on the notebook as:

  Work -> Don't work -> Work -> Don't work

  On Windows 10 this doesn't happen but when happens on Ubuntu, it's
  possible to reboot and see the status on Windows 10 too: on Device
  Manager it's shown a unidentified USB device at 1-7. Sometimes, on
  Windows 10's Network Devices it's shown, instead of the QCA9377, from
  four to six different devices with generic names and Bluetooth and/or
  Wireless don't work.

  When turning Ubuntu off, there are messages that appears a few
  instants before the system is turned off:

  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] 
ath10k_pci :02:00.0: failed to install key for vdev 0 peer 
xx:xx:xx:xx:xx:xx: -110
  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] 
wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110)

  Generally, only the second message appears (but both are recorded on
  kern.log). The MAC adress is the one from the router, not from the
  wireless card.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1364 F pulseaudio
   /dev/snd/seq:usuario1258 F timidity
  CurrentDesktop: XFCE
  Date: Tue Mar 20 14:43:42 2018
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2017-06-13 (279 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago)
  dmi.bios.date: 07/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN43WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN43WW:bd07/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK

[Kernel-packages] [Bug 1799102] Re: WARNING on boot in Intel GVT-g guest

2018-10-23 Thread Leonardo Müller

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

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

Title:
  WARNING on boot in Intel GVT-g guest

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When booting Ubuntu Cosmic Cuttlefish 18.10 in an Intel GVT-g Virtual
  Machine, a kernel WARNING appears in dmesg, with the following:

  [3.563734] WARNING: CPU: 3 PID: 346 at
  drivers/gpu/drm/i915/i915_irq.c:161 gen3_assert_iir_is_zero+0x38/0xa0
  [i915]

  I have not noticed negative effects in the VM, but a kernel WARNING
  probably has relevance.

  While I added a custom EDID to fix resolution, the WARNING happens
  without custom EDID set too. I will add information about the host in
  the next message.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: User Name 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1896 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 19:44:44 2018
  InstallationDate: Installed on 2018-10-18 (3 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   ens8  no wireless extensions.
  Lsusb:
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 003: ID 46f4:0002  
   Bus 002 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=6cb7fc66-eb2c-4203-9d7d-2aa2665911ac ro quiet splash 
drm.edid_firmware=EDID_E1941.bin log_buf_len=16M vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-3.0
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.0:cvnQEMU:ct1:cvrpc-i440fx-3.0:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-3.0
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799102/+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

[Kernel-packages] [Bug 1799102] Re: WARNING on boot in Intel GVT-g guest

2018-10-23 Thread Leonardo Müller

dmesg with 4.19.0-041900-generic is attached. 4.19-rc8 has the same
WARNING on boot.

** Attachment added: "dmesg with 4.19.0-041900-generic"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799102/+attachment/5204537/+files/dmesg

** Tags added: kernel-bug-exists-upstream

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

Title:
  WARNING on boot in Intel GVT-g guest

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When booting Ubuntu Cosmic Cuttlefish 18.10 in an Intel GVT-g Virtual
  Machine, a kernel WARNING appears in dmesg, with the following:

  [3.563734] WARNING: CPU: 3 PID: 346 at
  drivers/gpu/drm/i915/i915_irq.c:161 gen3_assert_iir_is_zero+0x38/0xa0
  [i915]

  I have not noticed negative effects in the VM, but a kernel WARNING
  probably has relevance.

  While I added a custom EDID to fix resolution, the WARNING happens
  without custom EDID set too. I will add information about the host in
  the next message.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: User Name 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1896 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 19:44:44 2018
  InstallationDate: Installed on 2018-10-18 (3 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   ens8  no wireless extensions.
  Lsusb:
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 003: ID 46f4:0002  
   Bus 002 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=6cb7fc66-eb2c-4203-9d7d-2aa2665911ac ro quiet splash 
drm.edid_firmware=EDID_E1941.bin log_buf_len=16M vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-3.0
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.0:cvnQEMU:ct1:cvrpc-i440fx-3.0:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-3.0
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799102/+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

[Kernel-packages] [Bug 1799102] Re: WARNING on boot in Intel GVT-g guest

2018-10-21 Thread Leonardo Müller

Host information:

OS: Xubuntu 18.04.1 (amd64);
Kernel: 4.17.19 with 337fe9f5c1e7de1f391c6a692531379d2aa2ee11 applied to fix 
https://bugs.freedesktop.org/show_bug.cgi?id=107899;
QEMU: 3.0.0;

QEMU command line:

env PULSE_LATENCY_MSEC=5 QEMU_AUDIO_ADC_VOICES=0 QEMU_AUDIO_DRV=pa 
qemu-system-x86_64 \
-name "Ubuntu Cosmic" -k pt-br -nodefaults -enable-kvm -cpu host -smp 
cores=2,threads=2 -m 2G \
-device 
vfio-pci,sysfsdev=/sys/bus/pci/devices/:00:02.0/ef5f4cb6-734b-11e8-aaff-9fff2622012e,rombar=0,display=on,x-intx-mmap-timeout-ms=0x200,addr=0x3,id=iHD520
 \
-device qemu-xhci,id=xhcihub -device usb-tablet,id=usbtablet -device 
usb-audio,id=usbaudio,buffer=6144 -bios /usr/share/ovmf/OVMF.fd  \
-display gtk,gl=on -hda ubuntucosmic.qcow2 -monitor vc -serial mon:stdio \
-machine kernel_irqchip=on -global PIIX4_PM.disable_s3=1 -global 
PIIX4_PM.disable_s4=1 -M pc,usb=true \
-netdev user,id=net0,hostfwd=::5454-:22 -device e1000,netdev=net0,addr=8

** Bug watch added: freedesktop.org Bugzilla #107899
   https://bugs.freedesktop.org/show_bug.cgi?id=107899

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

Title:
  WARNING on boot in Intel GVT-g guest

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When booting Ubuntu Cosmic Cuttlefish 18.10 in an Intel GVT-g Virtual
  Machine, a kernel WARNING appears in dmesg, with the following:

  [3.563734] WARNING: CPU: 3 PID: 346 at
  drivers/gpu/drm/i915/i915_irq.c:161 gen3_assert_iir_is_zero+0x38/0xa0
  [i915]

  I have not noticed negative effects in the VM, but a kernel WARNING
  probably has relevance.

  While I added a custom EDID to fix resolution, the WARNING happens
  without custom EDID set too. I will add information about the host in
  the next message.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: User Name 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1896 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 19:44:44 2018
  InstallationDate: Installed on 2018-10-18 (3 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   ens8  no wireless extensions.
  Lsusb:
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 003: ID 46f4:0002  
   Bus 002 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=6cb7fc66-eb2c-4203-9d7d-2aa2665911ac ro quiet splash 
drm.edid_firmware=EDID_E1941.bin log_buf_len=16M vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-3.0
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.0:cvnQEMU:ct1:cvrpc-i440fx-3.0:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-3.0
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799102/+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

[Kernel-packages] [Bug 1799102] [NEW] WARNING on boot in Intel GVT-g guest

2018-10-21 Thread Leonardo Müller

Public bug reported:

When booting Ubuntu Cosmic Cuttlefish 18.10 in an Intel GVT-g Virtual
Machine, a kernel WARNING appears in dmesg, with the following:

[3.563734] WARNING: CPU: 3 PID: 346 at
drivers/gpu/drm/i915/i915_irq.c:161 gen3_assert_iir_is_zero+0x38/0xa0
[i915]

I have not noticed negative effects in the VM, but a kernel WARNING
probably has relevance.

While I added a custom EDID to fix resolution, the WARNING happens
without custom EDID set too. I will add information about the host in
the next message.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-10-generic 4.18.0-10.11
ProcVersionSignature: User Name 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  ubuntu 1896 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 21 19:44:44 2018
InstallationDate: Installed on 2018-10-18 (3 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
IwConfig:
 lono wireless extensions.
 
 ens8  no wireless extensions.
Lsusb:
 Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 002 Device 003: ID 46f4:0002  
 Bus 002 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=6cb7fc66-eb2c-4203-9d7d-2aa2665911ac ro quiet splash 
drm.edid_firmware=EDID_E1941.bin log_buf_len=16M vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-10-generic N/A
 linux-backports-modules-4.18.0-10-generic  N/A
 linux-firmware 1.175
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/06/2015
dmi.bios.vendor: EFI Development Kit II / OVMF
dmi.bios.version: 0.0.0
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-3.0
dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.0:cvnQEMU:ct1:cvrpc-i440fx-3.0:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-3.0
dmi.sys.vendor: QEMU

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug cosmic

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

Title:
  WARNING on boot in Intel GVT-g guest

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When booting Ubuntu Cosmic Cuttlefish 18.10 in an Intel GVT-g Virtual
  Machine, a kernel WARNING appears in dmesg, with the following:

  [3.563734] WARNING: CPU: 3 PID: 346 at
  drivers/gpu/drm/i915/i915_irq.c:161 gen3_assert_iir_is_zero+0x38/0xa0
  [i915]

  I have not noticed negative effects in the VM, but a kernel WARNING
  probably has relevance.

  While I added a custom EDID to fix resolution, the WARNING happens
  without custom EDID set too. I will add information about the host in
  the next message.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: User Name 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1896 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 19:44:44 2018
  InstallationDate: Installed on 2018-10-18 (3 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   ens8  no wireless extensions.
  Lsusb:
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 003: ID 46f4:0002  
   Bus 002 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=6cb7fc66-eb2c-4203-9d7d-2aa2665911ac ro quiet splash 
drm.edid_firmware=EDID_E1941.bin log_buf_len=16M vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1

[Kernel-packages] [Bug 1798165] Re: Vulkan applications cause permanent memory leak with Intel GPU

2018-10-16 Thread Leonardo Müller

This kernel has the bug fixed. After one hour open, a game using DXVK
did not allocate any memory it couldn't free when closed. It would leak
around 600 MB in the same time previously.

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

Title:
  Vulkan applications cause permanent memory leak with Intel GPU

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  Vulkan applications, as Dota 2 and DXVK games cause a memory leak
  where memory is never freed and can cause a system crash if the
  applications are used for long enough. Certain applications can make
  the leak be as high as 10 MB/minute.

  Details about this bug can be seen at
  https://github.com/doitsujin/dxvk/issues/632 and
  https://bugs.freedesktop.org/show_bug.cgi?id=107899

  This bug was fixed in 4.19-rc6 and was backported to 4.14 and 4.18.
  The particular commit is:

  commit a2cef7d049f07995406b403605119a54881daf15
  Author: Jason Ekstrand 
  Date:   Wed Sep 26 02:17:03 2018 -0500

  drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set
  
  commit 337fe9f5c1e7de1f391c6a692531379d2aa2ee11 upstream.
  
  We attempt to get fences earlier in the hopes that everything will
  already have fences and no callbacks will be needed.  If we do succeed
  in getting a fence, getting one a second time will result in a duplicate
  ref with no unref.  This is causing memory leaks in Vulkan applications
  that create a lot of fences; playing for a few hours can, apparently,
  bring down the system.
  
  Cc: sta...@vger.kernel.org
  Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107899
  Reviewed-by: Chris Wilson 
  Signed-off-by: Jason Ekstrand 
  Signed-off-by: Sean Paul 
  Link: 
https://patchwork.freedesktop.org/patch/msgid/20180926071703.15257-1-jason.ekstr...@intel.com
  Signed-off-by: Greg Kroah-Hartman 

  
  On Ubuntu 18.04 with 4.15.0-36 it appears in slabtop as: 
https://i.imgur.com/qMAvuwl.png

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario4655 F pulseaudio
   /dev/snd/seq:usuario4640 F timidity
  CurrentDesktop: XFCE
  Date: Tue Oct 16 14:16:54 2018
  HibernationDevice: RESUME=UUID=0946602f-3ca2-4379-9012-7a5171928de7
  InstallationDate: Installed on 2017-06-13 (489 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 
kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 intel_iommu=on iommu=pt 
i915.enable_gvt=1 i915.fastboot=1 
resume=UUID=0946602f-3ca2-4379-9012-7a5171928de7 mtrr_gran_size=2M 
mtrr_chunk_size=64M cgroup_enable=memory swapaccount=1 zswap.enabled=1 
log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (361 days ago)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1798165/+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

[Kernel-packages] [Bug 1798165] Re: Vulkan applications cause permanent memory leak with Intel GPU

2018-10-16 Thread Leonardo Müller

** Tags added: kernel-fixed-upstream

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

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

Title:
  Vulkan applications cause permanent memory leak with Intel GPU

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Vulkan applications, as Dota 2 and DXVK games cause a memory leak
  where memory is never freed and can cause a system crash if the
  applications are used for long enough. Certain applications can make
  the leak be as high as 10 MB/minute.

  Details about this bug can be seen at
  https://github.com/doitsujin/dxvk/issues/632 and
  https://bugs.freedesktop.org/show_bug.cgi?id=107899

  This bug was fixed in 4.19-rc6 and was backported to 4.14 and 4.18.
  The particular commit is:

  commit a2cef7d049f07995406b403605119a54881daf15
  Author: Jason Ekstrand 
  Date:   Wed Sep 26 02:17:03 2018 -0500

  drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set
  
  commit 337fe9f5c1e7de1f391c6a692531379d2aa2ee11 upstream.
  
  We attempt to get fences earlier in the hopes that everything will
  already have fences and no callbacks will be needed.  If we do succeed
  in getting a fence, getting one a second time will result in a duplicate
  ref with no unref.  This is causing memory leaks in Vulkan applications
  that create a lot of fences; playing for a few hours can, apparently,
  bring down the system.
  
  Cc: sta...@vger.kernel.org
  Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107899
  Reviewed-by: Chris Wilson 
  Signed-off-by: Jason Ekstrand 
  Signed-off-by: Sean Paul 
  Link: 
https://patchwork.freedesktop.org/patch/msgid/20180926071703.15257-1-jason.ekstr...@intel.com
  Signed-off-by: Greg Kroah-Hartman 

  
  On Ubuntu 18.04 with 4.15.0-36 it appears in slabtop as: 
https://i.imgur.com/qMAvuwl.png

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario4655 F pulseaudio
   /dev/snd/seq:usuario4640 F timidity
  CurrentDesktop: XFCE
  Date: Tue Oct 16 14:16:54 2018
  HibernationDevice: RESUME=UUID=0946602f-3ca2-4379-9012-7a5171928de7
  InstallationDate: Installed on 2017-06-13 (489 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 
kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 intel_iommu=on iommu=pt 
i915.enable_gvt=1 i915.fastboot=1 
resume=UUID=0946602f-3ca2-4379-9012-7a5171928de7 mtrr_gran_size=2M 
mtrr_chunk_size=64M cgroup_enable=memory swapaccount=1 zswap.enabled=1 
log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (361 days ago)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1798165/+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

[Kernel-packages] [Bug 1798165] [NEW] Vulkan applications cause permanent memory leak with Intel GPU

2018-10-16 Thread Leonardo Müller

Public bug reported:

Vulkan applications, as Dota 2 and DXVK games cause a memory leak where
memory is never freed and can cause a system crash if the applications
are used for long enough. Certain applications can make the leak be as
high as 10 MB/minute.

Details about this bug can be seen at
https://github.com/doitsujin/dxvk/issues/632 and
https://bugs.freedesktop.org/show_bug.cgi?id=107899

This bug was fixed in 4.19-rc6 and was backported to 4.14 and 4.18. The
particular commit is:

commit a2cef7d049f07995406b403605119a54881daf15
Author: Jason Ekstrand 
Date:   Wed Sep 26 02:17:03 2018 -0500

drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set

commit 337fe9f5c1e7de1f391c6a692531379d2aa2ee11 upstream.

We attempt to get fences earlier in the hopes that everything will
already have fences and no callbacks will be needed.  If we do succeed
in getting a fence, getting one a second time will result in a duplicate
ref with no unref.  This is causing memory leaks in Vulkan applications
that create a lot of fences; playing for a few hours can, apparently,
bring down the system.

Cc: sta...@vger.kernel.org
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107899
Reviewed-by: Chris Wilson 
Signed-off-by: Jason Ekstrand 
Signed-off-by: Sean Paul 
Link: 
https://patchwork.freedesktop.org/patch/msgid/20180926071703.15257-1-jason.ekstr...@intel.com
Signed-off-by: Greg Kroah-Hartman 


On Ubuntu 18.04 with 4.15.0-36 it appears in slabtop as: 
https://i.imgur.com/qMAvuwl.png

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-36-generic 4.15.0-36.39
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  usuario4655 F pulseaudio
 /dev/snd/seq:usuario4640 F timidity
CurrentDesktop: XFCE
Date: Tue Oct 16 14:16:54 2018
HibernationDevice: RESUME=UUID=0946602f-3ca2-4379-9012-7a5171928de7
InstallationDate: Installed on 2017-06-13 (489 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: LENOVO 80UG
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 
kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 intel_iommu=on iommu=pt 
i915.enable_gvt=1 i915.fastboot=1 
resume=UUID=0946602f-3ca2-4379-9012-7a5171928de7 mtrr_gran_size=2M 
mtrr_chunk_size=64M cgroup_enable=memory swapaccount=1 zswap.enabled=1 
log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-36-generic N/A
 linux-backports-modules-4.15.0-36-generic  N/A
 linux-firmware 1.173.1
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2017-10-20 (361 days ago)
dmi.bios.date: 08/09/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 0XCN45WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Toronto 4A2
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 310-14ISK
dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
dmi.product.family: IDEAPAD
dmi.product.name: 80UG
dmi.product.version: Lenovo ideapad 310-14ISK
dmi.sys.vendor: LENOVO

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  Vulkan applications cause permanent memory leak with Intel GPU

Status in linux package in Ubuntu:
  New

Bug description:
  Vulkan applications, as Dota 2 and DXVK games cause a memory leak
  where memory is never freed and can cause a system crash if the
  applications are used for long enough. Certain applications can make
  the leak be as high as 10 MB/minute.

  Details about this bug can be seen at
  https://github.com/doitsujin/dxvk/issues/632 and
  https://bugs.freedesktop.org/show_bug.cgi?id=107899

  This bug was fixed in 4.19-rc6 and was backported to 4.14 and 4.18.
  The particular commit is:

  commit a2cef7d049f07995406b403605119a54881daf15
  Author: Jason Ekstrand 
  Date:   Wed Sep 26 02:17:03 2018 -0500

  drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set
  
  commit 337fe9f5c1e7de1f391c6a692531379d2aa2ee11 upstream.
  
  We attempt to get fences earlier in the hopes that everything will
  already have fences and no callbacks will be needed.  If we do succeed
  in getting a fence, getting one a second time will result in a duplicate
  ref

[Kernel-packages] [Bug 1793846] Re: Regression: gamepad Redragon Seymur 2 no longer works properly

2018-10-03 Thread Leonardo Müller

Thank you for this option. Using it the controller is working properly
again.

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

Title:
  Regression: gamepad Redragon Seymur 2 no longer works properly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The gamepad Redragon Seymur 2 right analog stick no longer works
  properly with kernel versions at least 4.18 and newer. On 4.17.19 they
  work properly.

  I already reported this regression on kernel bugzilla but it did not
  receive attention there and Ubuntu Cosmic release is going to be soon,
  so I think it's relevant it's reported here too.

  This is the link of the bugzilla report I wrote:
  https://bugzilla.kernel.org/show_bug.cgi?id=200995

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperVersion: 1.396
  CurrentDesktop: XFCE
  Date: Sat Sep 22 04:14:39 2018
  IwConfig:
   lono wireless extensions.
   
   ens2  no wireless extensions.
  LiveMediaBuild: Xubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180921)
  Lsusb:
   Bus 002 Device 002: ID 0480:0200 Toshiba America Inc External Disk
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0079:0006 DragonRise Inc. PC TWIN SHOCK Gamepad
   Bus 001 Device 002: ID 0781:5567 SanDisk Corp. Cruzer Blade
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtiodrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-7-generic N/A
   linux-backports-modules-4.18.0-7-generic  N/A
   linux-firmware1.175
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.11.2-0-gf9626ccb91-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-3.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.11.2-0-gf9626ccb91-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.0:cvnQEMU:ct1:cvrpc-i440fx-3.0:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-3.0
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793846/+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

[Kernel-packages] [Bug 1793846] Re: Regression: gamepad Redragon Seymur 2 no longer works properly

2018-09-26 Thread Leonardo Müller

No, because I don't know where I should apply
HID_QUIRK_INCREMENT_USAGE_ON_DUPLICATE, as all search results are the
commit message.

Where do I apply this quirk?

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

Title:
  Regression: gamepad Redragon Seymur 2 no longer works properly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The gamepad Redragon Seymur 2 right analog stick no longer works
  properly with kernel versions at least 4.18 and newer. On 4.17.19 they
  work properly.

  I already reported this regression on kernel bugzilla but it did not
  receive attention there and Ubuntu Cosmic release is going to be soon,
  so I think it's relevant it's reported here too.

  This is the link of the bugzilla report I wrote:
  https://bugzilla.kernel.org/show_bug.cgi?id=200995

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperVersion: 1.396
  CurrentDesktop: XFCE
  Date: Sat Sep 22 04:14:39 2018
  IwConfig:
   lono wireless extensions.
   
   ens2  no wireless extensions.
  LiveMediaBuild: Xubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180921)
  Lsusb:
   Bus 002 Device 002: ID 0480:0200 Toshiba America Inc External Disk
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0079:0006 DragonRise Inc. PC TWIN SHOCK Gamepad
   Bus 001 Device 002: ID 0781:5567 SanDisk Corp. Cruzer Blade
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtiodrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-7-generic N/A
   linux-backports-modules-4.18.0-7-generic  N/A
   linux-firmware1.175
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.11.2-0-gf9626ccb91-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-3.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.11.2-0-gf9626ccb91-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.0:cvnQEMU:ct1:cvrpc-i440fx-3.0:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-3.0
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793846/+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

[Kernel-packages] [Bug 1793846] Re: Regression: gamepad Redragon Seymur 2 no longer works properly

2018-09-26 Thread Leonardo Müller

Unfortunately the gamepad is still with the problem. The right stick
does not work properly, its up/down movement does the left/right action
and left/right movement do nothing.

** Tags added: kernel-bug-exists-upstream

** Changed in: linux (Ubuntu)
   Status: Triaged => Confirmed

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

Title:
  Regression: gamepad Redragon Seymur 2 no longer works properly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The gamepad Redragon Seymur 2 right analog stick no longer works
  properly with kernel versions at least 4.18 and newer. On 4.17.19 they
  work properly.

  I already reported this regression on kernel bugzilla but it did not
  receive attention there and Ubuntu Cosmic release is going to be soon,
  so I think it's relevant it's reported here too.

  This is the link of the bugzilla report I wrote:
  https://bugzilla.kernel.org/show_bug.cgi?id=200995

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperVersion: 1.396
  CurrentDesktop: XFCE
  Date: Sat Sep 22 04:14:39 2018
  IwConfig:
   lono wireless extensions.
   
   ens2  no wireless extensions.
  LiveMediaBuild: Xubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180921)
  Lsusb:
   Bus 002 Device 002: ID 0480:0200 Toshiba America Inc External Disk
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0079:0006 DragonRise Inc. PC TWIN SHOCK Gamepad
   Bus 001 Device 002: ID 0781:5567 SanDisk Corp. Cruzer Blade
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtiodrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-7-generic N/A
   linux-backports-modules-4.18.0-7-generic  N/A
   linux-firmware1.175
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.11.2-0-gf9626ccb91-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-3.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.11.2-0-gf9626ccb91-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.0:cvnQEMU:ct1:cvrpc-i440fx-3.0:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-3.0
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793846/+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

[Kernel-packages] [Bug 1793846] [NEW] Regression: gamepad Redragon Seymur 2 no longer works properly

2018-09-21 Thread Leonardo Müller

Public bug reported:

The gamepad Redragon Seymur 2 right analog stick no longer works
properly with kernel versions at least 4.18 and newer. On 4.17.19 they
work properly.

I already reported this regression on kernel bugzilla but it did not
receive attention there and Ubuntu Cosmic release is going to be soon,
so I think it's relevant it's reported here too.

This is the link of the bugzilla report I wrote:
https://bugzilla.kernel.org/show_bug.cgi?id=200995

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-7-generic 4.18.0-7.8
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperVersion: 1.396
CurrentDesktop: XFCE
Date: Sat Sep 22 04:14:39 2018
IwConfig:
 lono wireless extensions.
 
 ens2  no wireless extensions.
LiveMediaBuild: Xubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180921)
Lsusb:
 Bus 002 Device 002: ID 0480:0200 Toshiba America Inc External Disk
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0079:0006 DragonRise Inc. PC TWIN SHOCK Gamepad
 Bus 001 Device 002: ID 0781:5567 SanDisk Corp. Cruzer Blade
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 virtiodrmfb
ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-7-generic N/A
 linux-backports-modules-4.18.0-7-generic  N/A
 linux-firmware1.175
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.11.2-0-gf9626ccb91-prebuilt.qemu-project.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-3.0
dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.11.2-0-gf9626ccb91-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.0:cvnQEMU:ct1:cvrpc-i440fx-3.0:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-3.0
dmi.sys.vendor: QEMU

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug cosmic

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

Title:
  Regression: gamepad Redragon Seymur 2 no longer works properly

Status in linux package in Ubuntu:
  New

Bug description:
  The gamepad Redragon Seymur 2 right analog stick no longer works
  properly with kernel versions at least 4.18 and newer. On 4.17.19 they
  work properly.

  I already reported this regression on kernel bugzilla but it did not
  receive attention there and Ubuntu Cosmic release is going to be soon,
  so I think it's relevant it's reported here too.

  This is the link of the bugzilla report I wrote:
  https://bugzilla.kernel.org/show_bug.cgi?id=200995

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperVersion: 1.396
  CurrentDesktop: XFCE
  Date: Sat Sep 22 04:14:39 2018
  IwConfig:
   lono wireless extensions.
   
   ens2  no wireless extensions.
  LiveMediaBuild: Xubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180921)
  Lsusb:
   Bus 002 Device 002: ID 0480:0200 Toshiba America Inc External Disk
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0079:0006 DragonRise Inc. PC TWIN SHOCK Gamepad
   Bus 001 Device 002: ID 0781:5567 SanDisk Corp. Cruzer Blade
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtiodrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-7-generic N/A
   linux-backports-modules-4.18.0-7-generic  N/A
   linux-firmware1.175
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.11.2-0-gf9626ccb91-prebuilt.qemu-project.org

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

2018-06-12 Thread Leonardo Müller

This kernel did not work. On boot, the same messages that appeared with
the other problematic kernels appear and the boot freezes.

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

Title:
  QCA9377 isn't being recognized sometimes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, the Wireless Network Card QCA9377 is not recognized on
  boot. This caused, on prior versions, a kernel panic at boot. With
  Bionic, the system boots but is unable to use wireless network. On
  dmesg there are messages like:

  [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd
  [2.808640] usb 1-7: device descriptor read/64, error -71
  [3.044337] usb 1-7: device descriptor read/64, error -71
  [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd
  [3.408245] usb 1-7: device descriptor read/64, error -71
  [3.644244] usb 1-7: device descriptor read/64, error -71
  [3.752193] usb usb1-port7: attempt power cycle
  [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd
  [4.404904] usb 1-7: Device not responding to setup address.
  [4.612478] usb 1-7: Device not responding to setup address.
  [4.820588] usb 1-7: device not accepting address 9, error -71
  [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd
  [4.949109] usb 1-7: Device not responding to setup address.
  [5.156893] usb 1-7: Device not responding to setup address.
  [5.364589] usb 1-7: device not accepting address 10, error -71
  [5.364655] usb usb1-port7: unable to enumerate USB device

  And lspci and lsusb don't show the wireless network card. The
  alternative is to turn the system off. Reboot don't work and reboot to
  Windows 10 also don't. The system must be powered off to restore
  functionality. Then, on the next boot, it works properly.

  However, after the system is turned off, it may cause the issue again.
  This is not 100% consistent, but mostly it cycles between powering off
  and powering on the notebook as:

  Work -> Don't work -> Work -> Don't work

  On Windows 10 this doesn't happen but when happens on Ubuntu, it's
  possible to reboot and see the status on Windows 10 too: on Device
  Manager it's shown a unidentified USB device at 1-7. Sometimes, on
  Windows 10's Network Devices it's shown, instead of the QCA9377, from
  four to six different devices with generic names and Bluetooth and/or
  Wireless don't work.

  When turning Ubuntu off, there are messages that appears a few
  instants before the system is turned off:

  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] 
ath10k_pci :02:00.0: failed to install key for vdev 0 peer 
xx:xx:xx:xx:xx:xx: -110
  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] 
wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110)

  Generally, only the second message appears (but both are recorded on
  kern.log). The MAC adress is the one from the router, not from the
  wireless card.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1364 F pulseaudio
   /dev/snd/seq:usuario1258 F timidity
  CurrentDesktop: XFCE
  Date: Tue Mar 20 14:43:42 2018
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2017-06-13 (279 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago)
  dmi.bios.date: 07/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN43WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN43WW:bd07/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

To manage notifications about

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

2018-06-11 Thread Leonardo Müller

Ok, using btusb.autosuspend=0 with this kernel version worked. I tested
to turn the notebook off and on 5 times and all times both Bluetooth and
Wireless worked.

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

Title:
  QCA9377 isn't being recognized sometimes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, the Wireless Network Card QCA9377 is not recognized on
  boot. This caused, on prior versions, a kernel panic at boot. With
  Bionic, the system boots but is unable to use wireless network. On
  dmesg there are messages like:

  [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd
  [2.808640] usb 1-7: device descriptor read/64, error -71
  [3.044337] usb 1-7: device descriptor read/64, error -71
  [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd
  [3.408245] usb 1-7: device descriptor read/64, error -71
  [3.644244] usb 1-7: device descriptor read/64, error -71
  [3.752193] usb usb1-port7: attempt power cycle
  [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd
  [4.404904] usb 1-7: Device not responding to setup address.
  [4.612478] usb 1-7: Device not responding to setup address.
  [4.820588] usb 1-7: device not accepting address 9, error -71
  [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd
  [4.949109] usb 1-7: Device not responding to setup address.
  [5.156893] usb 1-7: Device not responding to setup address.
  [5.364589] usb 1-7: device not accepting address 10, error -71
  [5.364655] usb usb1-port7: unable to enumerate USB device

  And lspci and lsusb don't show the wireless network card. The
  alternative is to turn the system off. Reboot don't work and reboot to
  Windows 10 also don't. The system must be powered off to restore
  functionality. Then, on the next boot, it works properly.

  However, after the system is turned off, it may cause the issue again.
  This is not 100% consistent, but mostly it cycles between powering off
  and powering on the notebook as:

  Work -> Don't work -> Work -> Don't work

  On Windows 10 this doesn't happen but when happens on Ubuntu, it's
  possible to reboot and see the status on Windows 10 too: on Device
  Manager it's shown a unidentified USB device at 1-7. Sometimes, on
  Windows 10's Network Devices it's shown, instead of the QCA9377, from
  four to six different devices with generic names and Bluetooth and/or
  Wireless don't work.

  When turning Ubuntu off, there are messages that appears a few
  instants before the system is turned off:

  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] 
ath10k_pci :02:00.0: failed to install key for vdev 0 peer 
xx:xx:xx:xx:xx:xx: -110
  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] 
wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110)

  Generally, only the second message appears (but both are recorded on
  kern.log). The MAC adress is the one from the router, not from the
  wireless card.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1364 F pulseaudio
   /dev/snd/seq:usuario1258 F timidity
  CurrentDesktop: XFCE
  Date: Tue Mar 20 14:43:42 2018
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2017-06-13 (279 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago)
  dmi.bios.date: 07/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN43WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN43WW:bd07/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

2018-06-11 Thread Leonardo Müller

This kernel version works, but I don't understand why testing a 4.17
version would be relevant on this case, as the first kernel fixed is
4.16-rc5 and, according to the checkout we've done before, the first
good commit should be:

commit 1fdb926974695d3dbc05a429bafa266fdd16510e
Author: Hans de Goede 
Date: Tue Feb 20 09:06:18 2018 +0100

Bluetooth: btusb: Use DMI matching for QCA reset_resume quirking

However, this commit alone have not solved the issue. Maybe because
there were many Bluetooth related commits together with this one and the
checkout was unable to detect this detail.

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

Title:
  QCA9377 isn't being recognized sometimes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, the Wireless Network Card QCA9377 is not recognized on
  boot. This caused, on prior versions, a kernel panic at boot. With
  Bionic, the system boots but is unable to use wireless network. On
  dmesg there are messages like:

  [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd
  [2.808640] usb 1-7: device descriptor read/64, error -71
  [3.044337] usb 1-7: device descriptor read/64, error -71
  [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd
  [3.408245] usb 1-7: device descriptor read/64, error -71
  [3.644244] usb 1-7: device descriptor read/64, error -71
  [3.752193] usb usb1-port7: attempt power cycle
  [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd
  [4.404904] usb 1-7: Device not responding to setup address.
  [4.612478] usb 1-7: Device not responding to setup address.
  [4.820588] usb 1-7: device not accepting address 9, error -71
  [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd
  [4.949109] usb 1-7: Device not responding to setup address.
  [5.156893] usb 1-7: Device not responding to setup address.
  [5.364589] usb 1-7: device not accepting address 10, error -71
  [5.364655] usb usb1-port7: unable to enumerate USB device

  And lspci and lsusb don't show the wireless network card. The
  alternative is to turn the system off. Reboot don't work and reboot to
  Windows 10 also don't. The system must be powered off to restore
  functionality. Then, on the next boot, it works properly.

  However, after the system is turned off, it may cause the issue again.
  This is not 100% consistent, but mostly it cycles between powering off
  and powering on the notebook as:

  Work -> Don't work -> Work -> Don't work

  On Windows 10 this doesn't happen but when happens on Ubuntu, it's
  possible to reboot and see the status on Windows 10 too: on Device
  Manager it's shown a unidentified USB device at 1-7. Sometimes, on
  Windows 10's Network Devices it's shown, instead of the QCA9377, from
  four to six different devices with generic names and Bluetooth and/or
  Wireless don't work.

  When turning Ubuntu off, there are messages that appears a few
  instants before the system is turned off:

  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] 
ath10k_pci :02:00.0: failed to install key for vdev 0 peer 
xx:xx:xx:xx:xx:xx: -110
  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] 
wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110)

  Generally, only the second message appears (but both are recorded on
  kern.log). The MAC adress is the one from the router, not from the
  wireless card.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1364 F pulseaudio
   /dev/snd/seq:usuario1258 F timidity
  CurrentDesktop: XFCE
  Date: Tue Mar 20 14:43:42 2018
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2017-06-13 (279 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago)
  dmi.bios.date: 07/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN43WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN

[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension

2018-06-11 Thread Leonardo Müller

This kernel update released today have not corrected the problem, but
the kernel from
https://people.canonical.com/~khfeng/lp1752772-r8169-intx/ works.

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

Title:
  r8169 ethernet card don't work after returning from suspension

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  Ethernet r8169 stops working after system resumed from suspend.

  [Test]
  User confirmed these patches fix the issue. r8169 continues to work
  after resume from suspend.

  [Regression Potential]
  Medium. The fix is limited to one device, all patches are in mainline.
  The WOL default change might cause regression for users that depend on
  BIOS settings. We can advice them to use userspace tool (systemd,
  ethtool, etc.) instead.

  ===Original Bug Report===
  I have noticed that the network stopped working on my desktop after I've 
suspended the system and woke it up. On dmesg there are messages like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity:
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:

  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
     Mixer name : 'VIA VT1818S'
     Components : 'HDA:11060440,18492818,0010'
     Controls  : 40
     Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
     Mixer name : 'ATI R6xx HDMI'
     Components : 'HDA:1002aa01,00aa0100,00100200'
     Controls  : 7
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined
     Playback channels: Mono
     Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:

  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias:

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

2018-06-09 Thread Leonardo Müller

The issues happens only on cold boot. In a pattern of:

Work -> Don't work -> Work

If the cold boot is successful, all reboots work. If the cold boot
failed, all reboots fail.

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

Title:
  QCA9377 isn't being recognized sometimes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, the Wireless Network Card QCA9377 is not recognized on
  boot. This caused, on prior versions, a kernel panic at boot. With
  Bionic, the system boots but is unable to use wireless network. On
  dmesg there are messages like:

  [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd
  [2.808640] usb 1-7: device descriptor read/64, error -71
  [3.044337] usb 1-7: device descriptor read/64, error -71
  [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd
  [3.408245] usb 1-7: device descriptor read/64, error -71
  [3.644244] usb 1-7: device descriptor read/64, error -71
  [3.752193] usb usb1-port7: attempt power cycle
  [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd
  [4.404904] usb 1-7: Device not responding to setup address.
  [4.612478] usb 1-7: Device not responding to setup address.
  [4.820588] usb 1-7: device not accepting address 9, error -71
  [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd
  [4.949109] usb 1-7: Device not responding to setup address.
  [5.156893] usb 1-7: Device not responding to setup address.
  [5.364589] usb 1-7: device not accepting address 10, error -71
  [5.364655] usb usb1-port7: unable to enumerate USB device

  And lspci and lsusb don't show the wireless network card. The
  alternative is to turn the system off. Reboot don't work and reboot to
  Windows 10 also don't. The system must be powered off to restore
  functionality. Then, on the next boot, it works properly.

  However, after the system is turned off, it may cause the issue again.
  This is not 100% consistent, but mostly it cycles between powering off
  and powering on the notebook as:

  Work -> Don't work -> Work -> Don't work

  On Windows 10 this doesn't happen but when happens on Ubuntu, it's
  possible to reboot and see the status on Windows 10 too: on Device
  Manager it's shown a unidentified USB device at 1-7. Sometimes, on
  Windows 10's Network Devices it's shown, instead of the QCA9377, from
  four to six different devices with generic names and Bluetooth and/or
  Wireless don't work.

  When turning Ubuntu off, there are messages that appears a few
  instants before the system is turned off:

  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] 
ath10k_pci :02:00.0: failed to install key for vdev 0 peer 
xx:xx:xx:xx:xx:xx: -110
  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] 
wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110)

  Generally, only the second message appears (but both are recorded on
  kern.log). The MAC adress is the one from the router, not from the
  wireless card.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1364 F pulseaudio
   /dev/snd/seq:usuario1258 F timidity
  CurrentDesktop: XFCE
  Date: Tue Mar 20 14:43:42 2018
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2017-06-13 (279 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago)
  dmi.bios.date: 07/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN43WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN43WW:bd07/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK

[Kernel-packages] [Bug 1774824] [NEW] la nueva versión de mi ubuntu budgi x64 bits no reconoce tarjeta wiffi

2018-06-02 Thread leonardo

Public bug reported:

ubuntu budgi x64 bits no me reconoce mi tarjeta wifi Qualcomm Atheros
AR9287 Wireless Network Adapter

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-22-generic 4.15.0-22.24
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Sat Jun  2 17:29:50 2018
InstallationDate: Installed on 2018-06-02 (0 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
SourcePackage: linux-signed
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  la nueva versión de mi ubuntu budgi x64 bits no reconoce tarjeta wiffi

Status in linux-signed package in Ubuntu:
  New

Bug description:
  ubuntu budgi x64 bits no me reconoce mi tarjeta wifi Qualcomm Atheros
  AR9287 Wireless Network Adapter

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sat Jun  2 17:29:50 2018
  InstallationDate: Installed on 2018-06-02 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1774824/+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

[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension

2018-05-26 Thread Leonardo Müller

It is working for me too.

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

Title:
  r8169 ethernet card don't work after returning from suspension

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ===SRU Justification===
  [Impact]
  Ethernet r8169 stops working after system resumed from suspend.

  [Test]
  User confirmed these patches fix the issue. r8169 continues to work
  after resume from suspend.

  [Regression Potential]
  Medium. The fix is limited to one device, all patches are in mainline.
  The WOL default change might cause regression for users that depend on
  BIOS settings. We can advice them to use userspace tool (systemd,
  ethtool, etc.) instead.

  ===Original Bug Report===
  I have noticed that the network stopped working on my desktop after I've 
suspended the system and woke it up. On dmesg there are messages like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity:
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:

  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
     Mixer name : 'VIA VT1818S'
     Components : 'HDA:11060440,18492818,0010'
     Controls  : 40
     Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
     Mixer name : 'ATI R6xx HDMI'
     Components : 'HDA:1002aa01,00aa0100,00100200'
     Controls  : 7
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined
     Playback channels: Mono
     Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:

  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled

[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension

2018-05-14 Thread Leonardo Müller

This kernel did not work, when waking from suspension it shows the same
dmesg messages and only reloading the r8169 module the Ethernet works
again.

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

Title:
  r8169 ethernet card don't work after returning from suspension

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have noticed that the network stopped working on my desktop after
  I've suspended the system and woke it up. On dmesg there are messages
  like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity: 
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:
   
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
 Mixer name : 'VIA VT1818S'
 Components : 'HDA:11060440,18492818,0010'
 Controls  : 40
 Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 7
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined
 Playback channels: Mono
 Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:
   
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/+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

[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension

2018-05-11 Thread Leonardo Müller

The kernel version 4.17-rc4 is working for me.

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

Title:
  r8169 ethernet card don't work after returning from suspension

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have noticed that the network stopped working on my desktop after
  I've suspended the system and woke it up. On dmesg there are messages
  like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity: 
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:
   
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
 Mixer name : 'VIA VT1818S'
 Components : 'HDA:11060440,18492818,0010'
 Controls  : 40
 Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 7
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined
 Playback channels: Mono
 Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:
   
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/+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

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

2018-05-10 Thread Leonardo Müller

Unfortunately, this kernel still has the same issue.

The parameter btusb.enable_autosuspend is decisive to define if the
fixed kernels will work. Disabling it ("btusb.enable_autosuspend=0")
makes the fixed kernels act like the broken ones. However, setting it in
broken kernels ("btusb.enable_autosuspend=1") has no effect.

** Attachment added: "Netconsole"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757218/+attachment/5137254/+files/netconsole002.log

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

Title:
  QCA9377 isn't being recognized sometimes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, the Wireless Network Card QCA9377 is not recognized on
  boot. This caused, on prior versions, a kernel panic at boot. With
  Bionic, the system boots but is unable to use wireless network. On
  dmesg there are messages like:

  [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd
  [2.808640] usb 1-7: device descriptor read/64, error -71
  [3.044337] usb 1-7: device descriptor read/64, error -71
  [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd
  [3.408245] usb 1-7: device descriptor read/64, error -71
  [3.644244] usb 1-7: device descriptor read/64, error -71
  [3.752193] usb usb1-port7: attempt power cycle
  [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd
  [4.404904] usb 1-7: Device not responding to setup address.
  [4.612478] usb 1-7: Device not responding to setup address.
  [4.820588] usb 1-7: device not accepting address 9, error -71
  [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd
  [4.949109] usb 1-7: Device not responding to setup address.
  [5.156893] usb 1-7: Device not responding to setup address.
  [5.364589] usb 1-7: device not accepting address 10, error -71
  [5.364655] usb usb1-port7: unable to enumerate USB device

  And lspci and lsusb don't show the wireless network card. The
  alternative is to turn the system off. Reboot don't work and reboot to
  Windows 10 also don't. The system must be powered off to restore
  functionality. Then, on the next boot, it works properly.

  However, after the system is turned off, it may cause the issue again.
  This is not 100% consistent, but mostly it cycles between powering off
  and powering on the notebook as:

  Work -> Don't work -> Work -> Don't work

  On Windows 10 this doesn't happen but when happens on Ubuntu, it's
  possible to reboot and see the status on Windows 10 too: on Device
  Manager it's shown a unidentified USB device at 1-7. Sometimes, on
  Windows 10's Network Devices it's shown, instead of the QCA9377, from
  four to six different devices with generic names and Bluetooth and/or
  Wireless don't work.

  When turning Ubuntu off, there are messages that appears a few
  instants before the system is turned off:

  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] 
ath10k_pci :02:00.0: failed to install key for vdev 0 peer 
xx:xx:xx:xx:xx:xx: -110
  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] 
wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110)

  Generally, only the second message appears (but both are recorded on
  kern.log). The MAC adress is the one from the router, not from the
  wireless card.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1364 F pulseaudio
   /dev/snd/seq:usuario1258 F timidity
  CurrentDesktop: XFCE
  Date: Tue Mar 20 14:43:42 2018
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2017-06-13 (279 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago)
  dmi.bios.date: 07/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN43WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK

[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension

2018-04-27 Thread Leonardo Müller

With a different install of Bionic in my notebook, the problem is
happening too. This appears on dmesg:

[   95.285073] [ cut here ]
[   95.285109] NETDEV WATCHDOG: enp1s0 (r8169): transmit queue 0 timed out
[   95.285165] WARNING: CPU: 3 PID: 0 at 
/build/linux-5s7Xkn/linux-4.15.0/net/sched/sch_generic.c:323 
dev_watchdog+0x221/0x230
[   95.285170] Modules linked in: rfcomm ccm xt_CHECKSUM iptable_mangle 
ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 bridge stp llc 
devlink ebtable_filter ebtables bnep binfmt_misc nls_iso8859_1 arc4 uvcvideo 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev 
snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc 
snd_soc_acpi snd_soc_core media snd_compress rtsx_usb_ms memstick btusb btrtl 
btbcm btintel bluetooth ecdh_generic snd_hda_codec_hdmi snd_hda_codec_conexant 
snd_hda_codec_generic ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec 
snd_hda_core snd_hwdep snd_pcm ip6t_REJECT snd_seq_midi nf_reject_ipv6 
snd_seq_midi_event xt_hl ip6t_rt ath10k_pci ath10k_core ath mac80211 cfg80211 
snd_rawmidi snd_seq snd_seq_device snd_timer nf_conntrack_ipv6
[   95.285324]  nf_defrag_ipv6 intel_rapl x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc input_leds aesni_intel aes_x86_64 crypto_simd 
glue_helper cryptd intel_cstate intel_rapl_perf joydev serio_raw 
intel_wmi_thunderbolt snd mei_me mei shpchp soundcore intel_pch_thermal 
ipt_REJECT nf_reject_ipv4 ideapad_laptop sparse_keymap xt_limit tpm_crb mac_hid 
acpi_pad 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 sch_fq_codel libcrc32c 
iptable_filter parport_pc ppdev lp parport ip_tables x_tables autofs4 
hid_generic usbhid rtsx_usb_sdmmc hid rtsx_usb uas usb_storage i915 
i2c_algo_bit drm_kms_helper
[   95.285473]  syscopyarea sysfillrect sysimgblt fb_sys_fops ahci r8169 
psmouse drm libahci mii wmi video
[   95.285511] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 4.15.0-20-generic 
#21-Ubuntu
[   95.285515] Hardware name: LENOVO 80UG/Toronto 4A2, BIOS 0XCN43WW 07/10/2017
[   95.285531] RIP: 0010:dev_watchdog+0x221/0x230
[   95.285542] RSP: 0018:9158f3583e58 EFLAGS: 00010286
[   95.285549] RAX:  RBX:  RCX: 
[   95.285554] RDX: 00040400 RSI: 00f6 RDI: 0300
[   95.285558] RBP: 9158f3583e88 R08: 0001 R09: 042a
[   95.285562] R10: 9158f3583ee0 R11:  R12: 0001
[   95.285567] R13: 9158e971e000 R14: 9158e971e478 R15: 9158de262480
[   95.285574] FS:  () GS:9158f358() 
knlGS:
[   95.285579] CS:  0010 DS:  ES:  CR0: 80050033
[   95.285584] CR2: 7f4ee6b2a000 CR3: 0001ff80a001 CR4: 003606e0
[   95.285590] DR0:  DR1:  DR2: 
[   95.285594] DR3:  DR6: fffe0ff0 DR7: 0400
[   95.285596] Call Trace:
[   95.285602]  
[   95.285619]  ? dev_deactivate_queue.constprop.33+0x60/0x60
[   95.285632]  call_timer_fn+0x30/0x130
[   95.285645]  run_timer_softirq+0x3fb/0x450
[   95.285658]  ? ktime_get+0x43/0xa0
[   95.285669]  ? lapic_next_deadline+0x26/0x30
[   95.285682]  __do_softirq+0xdf/0x2b2
[   95.285693]  irq_exit+0xb6/0xc0
[   95.285703]  smp_apic_timer_interrupt+0x71/0x130
[   95.285712]  apic_timer_interrupt+0x84/0x90
[   95.285716]  
[   95.285727] RIP: 0010:cpuidle_enter_state+0xa7/0x2f0
[   95.285732] RSP: 0018:a98200d13e68 EFLAGS: 0246 ORIG_RAX: 
ff11
[   95.285739] RAX: 9158f35a2880 RBX: 00162f6decee RCX: 001f
[   95.285751] RDX: 00162f6decee RSI: fffd0406ee17 RDI: 
[   95.285756] RBP: a98200d13ea8 R08: 0682 R09: 0f7b
[   95.285760] R10: a98200d13e38 R11: 00b5 R12: 9158f35ac900
[   95.285763] R13: 0006 R14: bab71e78 R15: 
[   95.285776]  ? cpuidle_enter_state+0x97/0x2f0
[   95.285785]  cpuidle_enter+0x17/0x20
[   95.285799]  call_cpuidle+0x23/0x40
[   95.285807]  do_idle+0x18c/0x1f0
[   95.285817]  cpu_startup_entry+0x73/0x80
[   95.285826]  start_secondary+0x1a6/0x200
[   95.285836]  secondary_startup_64+0xa5/0xb0
[   95.285842] Code: 38 00 49 63 4e e8 eb 92 4c 89 ef c6 05 e7 55 d9 00 01 e8 
23 38 fd ff 89 d9 48 89 c2 4c 89 ee 48 c7 c7 40 6d 79 ba e8 ef 03 81 ff <0f> 0b 
eb c0 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 
[   95.286003] ---[ end trace cd56da1f7e4ebcb2 ]---

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

Title:
  r8169 ethernet card

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

2018-04-17 Thread Leonardo Müller

This file is one with the failed boot, unfortunately the kernel panic
message don't appear. Unlike the other file with the failure I uploaded
before, on this one the boot failed. I was helped on #ubuntu+1 on how to
add netconsole to initramfs, so I was able to obtain the first 7 seconds
of the log.

** Attachment added: "netconsole15.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757218/+attachment/5119900/+files/netconsole15.log

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

Title:
  QCA9377 isn't being recognized sometimes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, the Wireless Network Card QCA9377 is not recognized on
  boot. This caused, on prior versions, a kernel panic at boot. With
  Bionic, the system boots but is unable to use wireless network. On
  dmesg there are messages like:

  [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd
  [2.808640] usb 1-7: device descriptor read/64, error -71
  [3.044337] usb 1-7: device descriptor read/64, error -71
  [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd
  [3.408245] usb 1-7: device descriptor read/64, error -71
  [3.644244] usb 1-7: device descriptor read/64, error -71
  [3.752193] usb usb1-port7: attempt power cycle
  [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd
  [4.404904] usb 1-7: Device not responding to setup address.
  [4.612478] usb 1-7: Device not responding to setup address.
  [4.820588] usb 1-7: device not accepting address 9, error -71
  [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd
  [4.949109] usb 1-7: Device not responding to setup address.
  [5.156893] usb 1-7: Device not responding to setup address.
  [5.364589] usb 1-7: device not accepting address 10, error -71
  [5.364655] usb usb1-port7: unable to enumerate USB device

  And lspci and lsusb don't show the wireless network card. The
  alternative is to turn the system off. Reboot don't work and reboot to
  Windows 10 also don't. The system must be powered off to restore
  functionality. Then, on the next boot, it works properly.

  However, after the system is turned off, it may cause the issue again.
  This is not 100% consistent, but mostly it cycles between powering off
  and powering on the notebook as:

  Work -> Don't work -> Work -> Don't work

  On Windows 10 this doesn't happen but when happens on Ubuntu, it's
  possible to reboot and see the status on Windows 10 too: on Device
  Manager it's shown a unidentified USB device at 1-7. Sometimes, on
  Windows 10's Network Devices it's shown, instead of the QCA9377, from
  four to six different devices with generic names and Bluetooth and/or
  Wireless don't work.

  When turning Ubuntu off, there are messages that appears a few
  instants before the system is turned off:

  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] 
ath10k_pci :02:00.0: failed to install key for vdev 0 peer 
xx:xx:xx:xx:xx:xx: -110
  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] 
wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110)

  Generally, only the second message appears (but both are recorded on
  kern.log). The MAC adress is the one from the router, not from the
  wireless card.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1364 F pulseaudio
   /dev/snd/seq:usuario1258 F timidity
  CurrentDesktop: XFCE
  Date: Tue Mar 20 14:43:42 2018
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2017-06-13 (279 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago)
  dmi.bios.date: 07/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN43WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias:

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

2018-04-17 Thread Leonardo Müller

** Attachment added: "dmesg_ok.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757218/+attachment/5119845/+files/dmesg_ok.txt

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

Title:
  QCA9377 isn't being recognized sometimes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, the Wireless Network Card QCA9377 is not recognized on
  boot. This caused, on prior versions, a kernel panic at boot. With
  Bionic, the system boots but is unable to use wireless network. On
  dmesg there are messages like:

  [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd
  [2.808640] usb 1-7: device descriptor read/64, error -71
  [3.044337] usb 1-7: device descriptor read/64, error -71
  [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd
  [3.408245] usb 1-7: device descriptor read/64, error -71
  [3.644244] usb 1-7: device descriptor read/64, error -71
  [3.752193] usb usb1-port7: attempt power cycle
  [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd
  [4.404904] usb 1-7: Device not responding to setup address.
  [4.612478] usb 1-7: Device not responding to setup address.
  [4.820588] usb 1-7: device not accepting address 9, error -71
  [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd
  [4.949109] usb 1-7: Device not responding to setup address.
  [5.156893] usb 1-7: Device not responding to setup address.
  [5.364589] usb 1-7: device not accepting address 10, error -71
  [5.364655] usb usb1-port7: unable to enumerate USB device

  And lspci and lsusb don't show the wireless network card. The
  alternative is to turn the system off. Reboot don't work and reboot to
  Windows 10 also don't. The system must be powered off to restore
  functionality. Then, on the next boot, it works properly.

  However, after the system is turned off, it may cause the issue again.
  This is not 100% consistent, but mostly it cycles between powering off
  and powering on the notebook as:

  Work -> Don't work -> Work -> Don't work

  On Windows 10 this doesn't happen but when happens on Ubuntu, it's
  possible to reboot and see the status on Windows 10 too: on Device
  Manager it's shown a unidentified USB device at 1-7. Sometimes, on
  Windows 10's Network Devices it's shown, instead of the QCA9377, from
  four to six different devices with generic names and Bluetooth and/or
  Wireless don't work.

  When turning Ubuntu off, there are messages that appears a few
  instants before the system is turned off:

  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] 
ath10k_pci :02:00.0: failed to install key for vdev 0 peer 
xx:xx:xx:xx:xx:xx: -110
  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] 
wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110)

  Generally, only the second message appears (but both are recorded on
  kern.log). The MAC adress is the one from the router, not from the
  wireless card.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1364 F pulseaudio
   /dev/snd/seq:usuario1258 F timidity
  CurrentDesktop: XFCE
  Date: Tue Mar 20 14:43:42 2018
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2017-06-13 (279 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago)
  dmi.bios.date: 07/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN43WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN43WW:bd07/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

To manage

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

2018-04-17 Thread Leonardo Müller

Many tries were required until I could obtain a useful log. As it can be
seen in the kernel command line, I had to add many debug options to
obtain this.

** Attachment added: "dmesg_falha.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757218/+attachment/5119844/+files/dmesg_falha.txt

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

Title:
  QCA9377 isn't being recognized sometimes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, the Wireless Network Card QCA9377 is not recognized on
  boot. This caused, on prior versions, a kernel panic at boot. With
  Bionic, the system boots but is unable to use wireless network. On
  dmesg there are messages like:

  [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd
  [2.808640] usb 1-7: device descriptor read/64, error -71
  [3.044337] usb 1-7: device descriptor read/64, error -71
  [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd
  [3.408245] usb 1-7: device descriptor read/64, error -71
  [3.644244] usb 1-7: device descriptor read/64, error -71
  [3.752193] usb usb1-port7: attempt power cycle
  [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd
  [4.404904] usb 1-7: Device not responding to setup address.
  [4.612478] usb 1-7: Device not responding to setup address.
  [4.820588] usb 1-7: device not accepting address 9, error -71
  [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd
  [4.949109] usb 1-7: Device not responding to setup address.
  [5.156893] usb 1-7: Device not responding to setup address.
  [5.364589] usb 1-7: device not accepting address 10, error -71
  [5.364655] usb usb1-port7: unable to enumerate USB device

  And lspci and lsusb don't show the wireless network card. The
  alternative is to turn the system off. Reboot don't work and reboot to
  Windows 10 also don't. The system must be powered off to restore
  functionality. Then, on the next boot, it works properly.

  However, after the system is turned off, it may cause the issue again.
  This is not 100% consistent, but mostly it cycles between powering off
  and powering on the notebook as:

  Work -> Don't work -> Work -> Don't work

  On Windows 10 this doesn't happen but when happens on Ubuntu, it's
  possible to reboot and see the status on Windows 10 too: on Device
  Manager it's shown a unidentified USB device at 1-7. Sometimes, on
  Windows 10's Network Devices it's shown, instead of the QCA9377, from
  four to six different devices with generic names and Bluetooth and/or
  Wireless don't work.

  When turning Ubuntu off, there are messages that appears a few
  instants before the system is turned off:

  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] 
ath10k_pci :02:00.0: failed to install key for vdev 0 peer 
xx:xx:xx:xx:xx:xx: -110
  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] 
wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110)

  Generally, only the second message appears (but both are recorded on
  kern.log). The MAC adress is the one from the router, not from the
  wireless card.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1364 F pulseaudio
   /dev/snd/seq:usuario1258 F timidity
  CurrentDesktop: XFCE
  Date: Tue Mar 20 14:43:42 2018
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2017-06-13 (279 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago)
  dmi.bios.date: 07/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN43WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias:

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

2018-03-30 Thread Leonardo Müller

This is funny, but the option btusb.enable_autosuspend=0 make the bug
happen on v4.16-rc7. I'm seeing a pattern that, when I change the kernel
version or a grub option, I can't just turn on and off the notebook
twice (as it triggers normally), but thrice.

So, every time I change a configuration I have to turn the notebook on
and off thrice to test.

The good new is that btusb.enable_autosuspend=0 triggers the bug.

And no v4.15 kernel from mainline is free from this bug.

This bug is biting me for a long time and was being very hard to find,
but finally it is cornered.

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

Title:
  QCA9377 isn't being recognized sometimes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, the Wireless Network Card QCA9377 is not recognized on
  boot. This caused, on prior versions, a kernel panic at boot. With
  Bionic, the system boots but is unable to use wireless network. On
  dmesg there are messages like:

  [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd
  [2.808640] usb 1-7: device descriptor read/64, error -71
  [3.044337] usb 1-7: device descriptor read/64, error -71
  [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd
  [3.408245] usb 1-7: device descriptor read/64, error -71
  [3.644244] usb 1-7: device descriptor read/64, error -71
  [3.752193] usb usb1-port7: attempt power cycle
  [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd
  [4.404904] usb 1-7: Device not responding to setup address.
  [4.612478] usb 1-7: Device not responding to setup address.
  [4.820588] usb 1-7: device not accepting address 9, error -71
  [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd
  [4.949109] usb 1-7: Device not responding to setup address.
  [5.156893] usb 1-7: Device not responding to setup address.
  [5.364589] usb 1-7: device not accepting address 10, error -71
  [5.364655] usb usb1-port7: unable to enumerate USB device

  And lspci and lsusb don't show the wireless network card. The
  alternative is to turn the system off. Reboot don't work and reboot to
  Windows 10 also don't. The system must be powered off to restore
  functionality. Then, on the next boot, it works properly.

  However, after the system is turned off, it may cause the issue again.
  This is not 100% consistent, but mostly it cycles between powering off
  and powering on the notebook as:

  Work -> Don't work -> Work -> Don't work

  On Windows 10 this doesn't happen but when happens on Ubuntu, it's
  possible to reboot and see the status on Windows 10 too: on Device
  Manager it's shown a unidentified USB device at 1-7. Sometimes, on
  Windows 10's Network Devices it's shown, instead of the QCA9377, from
  four to six different devices with generic names and Bluetooth and/or
  Wireless don't work.

  When turning Ubuntu off, there are messages that appears a few
  instants before the system is turned off:

  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] 
ath10k_pci :02:00.0: failed to install key for vdev 0 peer 
xx:xx:xx:xx:xx:xx: -110
  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] 
wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110)

  Generally, only the second message appears (but both are recorded on
  kern.log). The MAC adress is the one from the router, not from the
  wireless card.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1364 F pulseaudio
   /dev/snd/seq:usuario1258 F timidity
  CurrentDesktop: XFCE
  Date: Tue Mar 20 14:43:42 2018
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2017-06-13 (279 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago)
  dmi.bios.date: 07/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN43WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

2018-03-30 Thread Leonardo Müller

The bug is still the same. What happened was that the system froze at a
different message in that particular try. Journalctl from a successful
initialization showing the most common point of failure:

systemd[1]: Starting Load/Save Screen Backlight Brightness of 
backlight:intel_backlight...
systemd[1]: Started Load/Save Screen Backlight Brightness of 
backlight:intel_backlight.
systemd[1]: Started Uncomplicated firewall.
systemd-udevd[400]: link_config: autonegotiation is unset or enabled, the speed 
and duplex are not writable.
systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
systemd[1]: Starting Load/Save RF Kill Switch Status...

The messages after the one of intel backlight are the ones related with
/dev/rfkill. This is why it freezes showing:

[ OK ]: Started Load/Save Screen Backlight Brightness of
backlight:intel_backlight.

Probably the RF Kill has a serious enough failure when this bug happens
that the entire system freezes.

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

Title:
  QCA9377 isn't being recognized sometimes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, the Wireless Network Card QCA9377 is not recognized on
  boot. This caused, on prior versions, a kernel panic at boot. With
  Bionic, the system boots but is unable to use wireless network. On
  dmesg there are messages like:

  [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd
  [2.808640] usb 1-7: device descriptor read/64, error -71
  [3.044337] usb 1-7: device descriptor read/64, error -71
  [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd
  [3.408245] usb 1-7: device descriptor read/64, error -71
  [3.644244] usb 1-7: device descriptor read/64, error -71
  [3.752193] usb usb1-port7: attempt power cycle
  [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd
  [4.404904] usb 1-7: Device not responding to setup address.
  [4.612478] usb 1-7: Device not responding to setup address.
  [4.820588] usb 1-7: device not accepting address 9, error -71
  [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd
  [4.949109] usb 1-7: Device not responding to setup address.
  [5.156893] usb 1-7: Device not responding to setup address.
  [5.364589] usb 1-7: device not accepting address 10, error -71
  [5.364655] usb usb1-port7: unable to enumerate USB device

  And lspci and lsusb don't show the wireless network card. The
  alternative is to turn the system off. Reboot don't work and reboot to
  Windows 10 also don't. The system must be powered off to restore
  functionality. Then, on the next boot, it works properly.

  However, after the system is turned off, it may cause the issue again.
  This is not 100% consistent, but mostly it cycles between powering off
  and powering on the notebook as:

  Work -> Don't work -> Work -> Don't work

  On Windows 10 this doesn't happen but when happens on Ubuntu, it's
  possible to reboot and see the status on Windows 10 too: on Device
  Manager it's shown a unidentified USB device at 1-7. Sometimes, on
  Windows 10's Network Devices it's shown, instead of the QCA9377, from
  four to six different devices with generic names and Bluetooth and/or
  Wireless don't work.

  When turning Ubuntu off, there are messages that appears a few
  instants before the system is turned off:

  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] 
ath10k_pci :02:00.0: failed to install key for vdev 0 peer 
xx:xx:xx:xx:xx:xx: -110
  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] 
wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110)

  Generally, only the second message appears (but both are recorded on
  kern.log). The MAC adress is the one from the router, not from the
  wireless card.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1364 F pulseaudio
   /dev/snd/seq:usuario1258 F timidity
  CurrentDesktop: XFCE
  Date: Tue Mar 20 14:43:42 2018
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2017-06-13 (279 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

2018-03-29 Thread Leonardo Müller

No, using this parameter when using the kernel v4.16-rc7 do not cause
the issue.

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

Title:
  QCA9377 isn't being recognized sometimes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, the Wireless Network Card QCA9377 is not recognized on
  boot. This caused, on prior versions, a kernel panic at boot. With
  Bionic, the system boots but is unable to use wireless network. On
  dmesg there are messages like:

  [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd
  [2.808640] usb 1-7: device descriptor read/64, error -71
  [3.044337] usb 1-7: device descriptor read/64, error -71
  [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd
  [3.408245] usb 1-7: device descriptor read/64, error -71
  [3.644244] usb 1-7: device descriptor read/64, error -71
  [3.752193] usb usb1-port7: attempt power cycle
  [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd
  [4.404904] usb 1-7: Device not responding to setup address.
  [4.612478] usb 1-7: Device not responding to setup address.
  [4.820588] usb 1-7: device not accepting address 9, error -71
  [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd
  [4.949109] usb 1-7: Device not responding to setup address.
  [5.156893] usb 1-7: Device not responding to setup address.
  [5.364589] usb 1-7: device not accepting address 10, error -71
  [5.364655] usb usb1-port7: unable to enumerate USB device

  And lspci and lsusb don't show the wireless network card. The
  alternative is to turn the system off. Reboot don't work and reboot to
  Windows 10 also don't. The system must be powered off to restore
  functionality. Then, on the next boot, it works properly.

  However, after the system is turned off, it may cause the issue again.
  This is not 100% consistent, but mostly it cycles between powering off
  and powering on the notebook as:

  Work -> Don't work -> Work -> Don't work

  On Windows 10 this doesn't happen but when happens on Ubuntu, it's
  possible to reboot and see the status on Windows 10 too: on Device
  Manager it's shown a unidentified USB device at 1-7. Sometimes, on
  Windows 10's Network Devices it's shown, instead of the QCA9377, from
  four to six different devices with generic names and Bluetooth and/or
  Wireless don't work.

  When turning Ubuntu off, there are messages that appears a few
  instants before the system is turned off:

  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] 
ath10k_pci :02:00.0: failed to install key for vdev 0 peer 
xx:xx:xx:xx:xx:xx: -110
  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] 
wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110)

  Generally, only the second message appears (but both are recorded on
  kern.log). The MAC adress is the one from the router, not from the
  wireless card.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1364 F pulseaudio
   /dev/snd/seq:usuario1258 F timidity
  CurrentDesktop: XFCE
  Date: Tue Mar 20 14:43:42 2018
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2017-06-13 (279 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago)
  dmi.bios.date: 07/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN43WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN43WW:bd07/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

This is comparing the 4.15.0-13 kernel with the mainline kernel.

** Attachment added: "diff_415_416rc7.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757218/+attachment/5092728/+files/diff_415_416rc7.txt

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

Title:
  QCA9377 isn't being recognized sometimes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, the Wireless Network Card QCA9377 is not recognized on
  boot. This caused, on prior versions, a kernel panic at boot. With
  Bionic, the system boots but is unable to use wireless network. On
  dmesg there are messages like:

  [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd
  [2.808640] usb 1-7: device descriptor read/64, error -71
  [3.044337] usb 1-7: device descriptor read/64, error -71
  [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd
  [3.408245] usb 1-7: device descriptor read/64, error -71
  [3.644244] usb 1-7: device descriptor read/64, error -71
  [3.752193] usb usb1-port7: attempt power cycle
  [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd
  [4.404904] usb 1-7: Device not responding to setup address.
  [4.612478] usb 1-7: Device not responding to setup address.
  [4.820588] usb 1-7: device not accepting address 9, error -71
  [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd
  [4.949109] usb 1-7: Device not responding to setup address.
  [5.156893] usb 1-7: Device not responding to setup address.
  [5.364589] usb 1-7: device not accepting address 10, error -71
  [5.364655] usb usb1-port7: unable to enumerate USB device

  And lspci and lsusb don't show the wireless network card. The
  alternative is to turn the system off. Reboot don't work and reboot to
  Windows 10 also don't. The system must be powered off to restore
  functionality. Then, on the next boot, it works properly.

  However, after the system is turned off, it may cause the issue again.
  This is not 100% consistent, but mostly it cycles between powering off
  and powering on the notebook as:

  Work -> Don't work -> Work -> Don't work

  On Windows 10 this doesn't happen but when happens on Ubuntu, it's
  possible to reboot and see the status on Windows 10 too: on Device
  Manager it's shown a unidentified USB device at 1-7. Sometimes, on
  Windows 10's Network Devices it's shown, instead of the QCA9377, from
  four to six different devices with generic names and Bluetooth and/or
  Wireless don't work.

  When turning Ubuntu off, there are messages that appears a few
  instants before the system is turned off:

  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] 
ath10k_pci :02:00.0: failed to install key for vdev 0 peer 
xx:xx:xx:xx:xx:xx: -110
  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] 
wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110)

  Generally, only the second message appears (but both are recorded on
  kern.log). The MAC adress is the one from the router, not from the
  wireless card.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1364 F pulseaudio
   /dev/snd/seq:usuario1258 F timidity
  CurrentDesktop: XFCE
  Date: Tue Mar 20 14:43:42 2018
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2017-06-13 (279 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago)
  dmi.bios.date: 07/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN43WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN43WW:bd07/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

The only thing I can think that is wrong is the configuration file of
the kernels. They have some significant differences regarding Bluetooth.

** Attachment added: "diff_415_416rc2+.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757218/+attachment/5092727/+files/diff_415_416rc2+.txt

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

Title:
  QCA9377 isn't being recognized sometimes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, the Wireless Network Card QCA9377 is not recognized on
  boot. This caused, on prior versions, a kernel panic at boot. With
  Bionic, the system boots but is unable to use wireless network. On
  dmesg there are messages like:

  [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd
  [2.808640] usb 1-7: device descriptor read/64, error -71
  [3.044337] usb 1-7: device descriptor read/64, error -71
  [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd
  [3.408245] usb 1-7: device descriptor read/64, error -71
  [3.644244] usb 1-7: device descriptor read/64, error -71
  [3.752193] usb usb1-port7: attempt power cycle
  [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd
  [4.404904] usb 1-7: Device not responding to setup address.
  [4.612478] usb 1-7: Device not responding to setup address.
  [4.820588] usb 1-7: device not accepting address 9, error -71
  [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd
  [4.949109] usb 1-7: Device not responding to setup address.
  [5.156893] usb 1-7: Device not responding to setup address.
  [5.364589] usb 1-7: device not accepting address 10, error -71
  [5.364655] usb usb1-port7: unable to enumerate USB device

  And lspci and lsusb don't show the wireless network card. The
  alternative is to turn the system off. Reboot don't work and reboot to
  Windows 10 also don't. The system must be powered off to restore
  functionality. Then, on the next boot, it works properly.

  However, after the system is turned off, it may cause the issue again.
  This is not 100% consistent, but mostly it cycles between powering off
  and powering on the notebook as:

  Work -> Don't work -> Work -> Don't work

  On Windows 10 this doesn't happen but when happens on Ubuntu, it's
  possible to reboot and see the status on Windows 10 too: on Device
  Manager it's shown a unidentified USB device at 1-7. Sometimes, on
  Windows 10's Network Devices it's shown, instead of the QCA9377, from
  four to six different devices with generic names and Bluetooth and/or
  Wireless don't work.

  When turning Ubuntu off, there are messages that appears a few
  instants before the system is turned off:

  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] 
ath10k_pci :02:00.0: failed to install key for vdev 0 peer 
xx:xx:xx:xx:xx:xx: -110
  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] 
wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110)

  Generally, only the second message appears (but both are recorded on
  kern.log). The MAC adress is the one from the router, not from the
  wireless card.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1364 F pulseaudio
   /dev/snd/seq:usuario1258 F timidity
  CurrentDesktop: XFCE
  Date: Tue Mar 20 14:43:42 2018
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2017-06-13 (279 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago)
  dmi.bios.date: 07/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN43WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias:

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

This is insane. I have reset that bisect and tried again using "fixed"
and "broken" instead of "new" and "old" and, again, the bisect had the
following:

1fdb926974695d3dbc05a429bafa266fdd16510e is the first fixed commit
commit 1fdb926974695d3dbc05a429bafa266fdd16510e
Author: Hans de Goede 
Date:   Tue Feb 20 09:06:18 2018 +0100

Bluetooth: btusb: Use DMI matching for QCA reset_resume quirking

Commit 61f5acea8737 ("Bluetooth: btusb: Restore QCA Rome suspend/resume fix
with a "rewritten" version") applied the USB_QUIRK_RESET_RESUME to all QCA
USB Bluetooth modules. But it turns out that the resume problems are not
caused by the QCA Rome chipset, on most platforms it resumes fine. The
resume problems are actually a platform problem (likely the platform
cutting all power when suspended).

The USB_QUIRK_RESET_RESUME quirk also disables runtime suspend, so by
matching on usb-ids, we're causing all boards with these chips to use extra
power, to fix resume problems which only happen on some boards.

This commit fixes this by applying the quirk based on DMI matching instead
of on usb-ids, so that we match the platform and not the chipset.

Here is the /sys/kernel/debug/usb/devices for the Bluetooth module:

T:  Bus=01 Lev=01 Prnt=01 Port=07 Cnt=04 Dev#=  5 Spd=12   MxCh= 0
D:  Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=0cf3 ProdID=e300 Rev= 0.01
C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=1ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
I:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=83(I) Atr=01(Isoc) MxPS=   9 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=   9 Ivl=1ms
I:  If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  17 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=  17 Ivl=1ms
I:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  25 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=  25 Ivl=1ms
I:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  33 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=  33 Ivl=1ms
I:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  49 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=  49 Ivl=1ms

BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1514836
Fixes: 61f5acea8737 ("Bluetooth: btusb: Restore QCA Rome suspend/resume..")
Cc: sta...@vger.kernel.org
Cc: Brian Norris 
Cc: Kai-Heng Feng 
Reported-and-tested-by: Kevin Fenzi 
Signed-off-by: Hans de Goede 
Signed-off-by: Marcel Holtmann 

:04 04 2930a43c59c0e767763843528fa8526d4e17b764
626944fe592accb35e33c69be141dbcee910910c M  drivers

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

Title:
  QCA9377 isn't being recognized sometimes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, the Wireless Network Card QCA9377 is not recognized on
  boot. This caused, on prior versions, a kernel panic at boot. With
  Bionic, the system boots but is unable to use wireless network. On
  dmesg there are messages like:

  [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd
  [2.808640] usb 1-7: device descriptor read/64, error -71
  [3.044337] usb 1-7: device descriptor read/64, error -71
  [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd
  [3.408245] usb 1-7: device descriptor read/64, error -71
  [3.644244] usb 1-7: device descriptor read/64, error -71
  [3.752193] usb usb1-port7: attempt power cycle
  [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd
  [4.404904] usb 1-7: Device not responding to setup address.
  [4.612478] usb 1-7: Device not responding to setup address.
  [4.820588] usb 1-7: device not accepting address 9, error -71
  [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd
  [4.949109] usb 1-7: Device not responding to setup address.
  [5.156893] usb 1-7: Device not responding to setup address.
  [5.364589] usb 1-7: device not accepting address 10, error -71
  [5.364655] usb usb1-port7: unable to enumerate USB device

  And lspci and lsusb don't show the wireless network card. The
  alternative

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

Don't mark this as fixed yet, it has just happened in a different way:
it progressed further on boot until it froze at the a message like
waiting for /dev/disk.

I, sincerely, don't know what to do now. This has never happened the
kernels starting from 4.16.0-rc5. I have uploaded the bisect log.

And the Ethernet problem was not fixed. It's important to say that I
have both a desktop and a notebook with this same Ethernet device (but
different revision) and only the desktop has this problem:

Desktop:
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411
PCI Express Gigabit Ethernet Controller (rev 03)

Notebook:
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411
PCI Express Gigabit Ethernet Controller (rev 10)

** Attachment added: "bisect_wireless_bt_panic_log.txt"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757218/+attachment/5092474/+files/bisect_wireless_bt_panic_log.txt

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

Title:
QCA9377 isn't being recognized sometimes

Status in linux package in Ubuntu:
Confirmed

Bug description:
Sometimes, the Wireless Network Card QCA9377 is not recognized on
boot. This caused, on prior versions, a kernel panic at boot. With
Bionic, the system boots but is unable to use wireless network. On
dmesg there are messages like:

[2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd
[2.808640] usb 1-7: device descriptor read/64, error -71
[3.044337] usb 1-7: device descriptor read/64, error -71
[3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd
[3.408245] usb 1-7: device descriptor read/64, error -71
[3.644244] usb 1-7: device descriptor read/64, error -71
[3.752193] usb usb1-port7: attempt power cycle
[4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd
[4.404904] usb 1-7: Device not responding to setup address.
[4.612478] usb 1-7: Device not responding to setup address.
[4.820588] usb 1-7: device not accepting address 9, error -71
[4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd
[4.949109] usb 1-7: Device not responding to setup address.
[5.156893] usb 1-7: Device not responding to setup address.
[5.364589] usb 1-7: device not accepting address 10, error -71
[5.364655] usb usb1-port7: unable to enumerate USB device

And lspci and lsusb don't show the wireless network card. The
alternative is to turn the system off. Reboot don't work and reboot to
Windows 10 also don't. The system must be powered off to restore
functionality. Then, on the next boot, it works properly.

However, after the system is turned off, it may cause the issue again.
This is not 100% consistent, but mostly it cycles between powering off
and powering on the notebook as:

Work -> Don't work -> Work -> Don't work

On Windows 10 this doesn't happen but when happens on Ubuntu, it's
possible to reboot and see the status on Windows 10 too: on Device
Manager it's shown a unidentified USB device at 1-7. Sometimes, on
Windows 10's Network Devices it's shown, instead of the QCA9377, from
four to six different devices with generic names and Bluetooth and/or
Wireless don't work.

When turning Ubuntu off, there are messages that appears a few
instants before the system is turned off:

Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388]
ath10k_pci :02:00.0: failed to install key for vdev 0 peer
xx:xx:xx:xx:xx:xx: -110
Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399]
wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110)

Generally, only the second message appears (but both are recorded on
kern.log). The MAC adress is the one from the router, not from the
wireless card.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-12-generic 4.15.0-12.13
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: usuario1364 F pulseaudio
/dev/snd/seq:usuario1258 F timidity
CurrentDesktop: XFCE
Date: Tue Mar 20 14:43:42 2018
HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
InstallationDate: Installed on 2017-06-13 (279 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: LENOVO 80UG
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
RelatedPackageVersions:
linux-restricted-modules-4.15.0-12-generic N/A
linux-backports-modules-4.15.0-12-generic N/A

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

The kernel was updated today to version 4.15.0-13 and the commit
"Bluetooth: btusb: Use DMI matching for QCA reset_resume quirking" was
added. I have tested the notebook and now it is no longer failing to
boot or booting without wireless and bluetooth.

The problem is fixed to me.

Thank you.

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

Title:
  QCA9377 isn't being recognized sometimes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, the Wireless Network Card QCA9377 is not recognized on
  boot. This caused, on prior versions, a kernel panic at boot. With
  Bionic, the system boots but is unable to use wireless network. On
  dmesg there are messages like:

  [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd
  [2.808640] usb 1-7: device descriptor read/64, error -71
  [3.044337] usb 1-7: device descriptor read/64, error -71
  [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd
  [3.408245] usb 1-7: device descriptor read/64, error -71
  [3.644244] usb 1-7: device descriptor read/64, error -71
  [3.752193] usb usb1-port7: attempt power cycle
  [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd
  [4.404904] usb 1-7: Device not responding to setup address.
  [4.612478] usb 1-7: Device not responding to setup address.
  [4.820588] usb 1-7: device not accepting address 9, error -71
  [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd
  [4.949109] usb 1-7: Device not responding to setup address.
  [5.156893] usb 1-7: Device not responding to setup address.
  [5.364589] usb 1-7: device not accepting address 10, error -71
  [5.364655] usb usb1-port7: unable to enumerate USB device

  And lspci and lsusb don't show the wireless network card. The
  alternative is to turn the system off. Reboot don't work and reboot to
  Windows 10 also don't. The system must be powered off to restore
  functionality. Then, on the next boot, it works properly.

  However, after the system is turned off, it may cause the issue again.
  This is not 100% consistent, but mostly it cycles between powering off
  and powering on the notebook as:

  Work -> Don't work -> Work -> Don't work

  On Windows 10 this doesn't happen but when happens on Ubuntu, it's
  possible to reboot and see the status on Windows 10 too: on Device
  Manager it's shown a unidentified USB device at 1-7. Sometimes, on
  Windows 10's Network Devices it's shown, instead of the QCA9377, from
  four to six different devices with generic names and Bluetooth and/or
  Wireless don't work.

  When turning Ubuntu off, there are messages that appears a few
  instants before the system is turned off:

  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] 
ath10k_pci :02:00.0: failed to install key for vdev 0 peer 
xx:xx:xx:xx:xx:xx: -110
  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] 
wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110)

  Generally, only the second message appears (but both are recorded on
  kern.log). The MAC adress is the one from the router, not from the
  wireless card.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1364 F pulseaudio
   /dev/snd/seq:usuario1258 F timidity
  CurrentDesktop: XFCE
  Date: Tue Mar 20 14:43:42 2018
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2017-06-13 (279 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago)
  dmi.bios.date: 07/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN43WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias:

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

Finally, after 10 kernels built, I've obtained the result. Here is the
output:

1fdb926974695d3dbc05a429bafa266fdd16510e is the first new commit
commit 1fdb926974695d3dbc05a429bafa266fdd16510e
Author: Hans de Goede 
Date:   Tue Feb 20 09:06:18 2018 +0100

Bluetooth: btusb: Use DMI matching for QCA reset_resume quirking

Commit 61f5acea8737 ("Bluetooth: btusb: Restore QCA Rome suspend/resume fix
with a "rewritten" version") applied the USB_QUIRK_RESET_RESUME to all QCA
USB Bluetooth modules. But it turns out that the resume problems are not
caused by the QCA Rome chipset, on most platforms it resumes fine. The
resume problems are actually a platform problem (likely the platform
cutting all power when suspended).

The USB_QUIRK_RESET_RESUME quirk also disables runtime suspend, so by
matching on usb-ids, we're causing all boards with these chips to use extra
power, to fix resume problems which only happen on some boards.

This commit fixes this by applying the quirk based on DMI matching instead
of on usb-ids, so that we match the platform and not the chipset.

Here is the /sys/kernel/debug/usb/devices for the Bluetooth module:

T:  Bus=01 Lev=01 Prnt=01 Port=07 Cnt=04 Dev#=  5 Spd=12   MxCh= 0
D:  Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=0cf3 ProdID=e300 Rev= 0.01
C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=1ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
I:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=83(I) Atr=01(Isoc) MxPS=   9 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=   9 Ivl=1ms
I:  If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  17 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=  17 Ivl=1ms
I:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  25 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=  25 Ivl=1ms
I:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  33 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=  33 Ivl=1ms
I:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  49 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=  49 Ivl=1ms

BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1514836
Fixes: 61f5acea8737 ("Bluetooth: btusb: Restore QCA Rome suspend/resume..")
Cc: sta...@vger.kernel.org
Cc: Brian Norris 
Cc: Kai-Heng Feng 
Reported-and-tested-by: Kevin Fenzi 
Signed-off-by: Hans de Goede 
Signed-off-by: Marcel Holtmann 

:04 04 2930a43c59c0e767763843528fa8526d4e17b764
626944fe592accb35e33c69be141dbcee910910c M  drivers

** Bug watch added: Red Hat Bugzilla #1514836
   https://bugzilla.redhat.com/show_bug.cgi?id=1514836

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

Title:
  QCA9377 isn't being recognized sometimes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, the Wireless Network Card QCA9377 is not recognized on
  boot. This caused, on prior versions, a kernel panic at boot. With
  Bionic, the system boots but is unable to use wireless network. On
  dmesg there are messages like:

  [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd
  [2.808640] usb 1-7: device descriptor read/64, error -71
  [3.044337] usb 1-7: device descriptor read/64, error -71
  [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd
  [3.408245] usb 1-7: device descriptor read/64, error -71
  [3.644244] usb 1-7: device descriptor read/64, error -71
  [3.752193] usb usb1-port7: attempt power cycle
  [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd
  [4.404904] usb 1-7: Device not responding to setup address.
  [4.612478] usb 1-7: Device not responding to setup address.
  [4.820588] usb 1-7: device not accepting address 9, error -71
  [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd
  [4.949109] usb 1-7: Device not responding to setup address.
  [5.156893] usb 1-7: Device not responding to setup address.
  [5.364589] usb 1-7: device not accepting address 10, error -71
  [5.364655] usb usb1-port7: unable to enumerate USB device

  And lspci and lsusb don't show the wireless

[Kernel-packages] [Bug 1686448] Re: Unable to reach higher than package C2 state with Skylake processor

I remember I read that article two days after the notebook had arrived.
Its Linux support was really poor, even with it having Satux Linux (a
really bad distribution). It had much more problems which quickly were
corrected, but this one is one of the most persistent issues (tied with
the wireless problem we're nearly solving).

>From what I researched back then ( 
>https://access.redhat.com/documentation/pt-br/red_hat_enterprise_linux/6/html/power_management_guide/alpm
> ), these SATA LPM options are changed by the following commands on this 
>notebook:
echo 'min_power' > '/sys/class/scsi_host/host0/link_power_management_policy'
echo 'min_power' > '/sys/class/scsi_host/host1/link_power_management_policy'

And they work. As the powertop proposed changes were effective back then
to enable Package C3 and now Package C8, I've done a systemd service to
enable them on boot.

Only USB ports and the PCI Audio device aren't with its powersave modes,
as setting them to save more power make problems start to appear.

** Attachment added: "econoenerg.service"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686448/+attachment/5091424/+files/econoenerg.service

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

Title:
  Unable to reach higher than package C2 state with Skylake processor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello

  I have a Lenovo Ideapad 310 with a Intel Core i3-6100U. I have noticed
  its battery last less time on Xubuntu 16.04 than on Windows 10. I have
  searched on internet what could cause it, and found with powertop it
  can't reach states higher than package C state 2, while it could reach
  package C state 10.

  On this particular notebook model, I would expect the battery would
  last a bit more than 5 hours using only browser, as it happens with
  Windows 10 and CentOS 7. On Xubuntu, battery lasts slightly more than
  4 hours. The best was 4h30min, so I am having at least 30 minutes less
  battery time, but generally it is one hour.

  I have tried to get support on Ubuntu Forums, here is the link of the thread:
  https://ubuntuforums.org/showthread.php?t=2357271

  As everything we tried had no success, I am making this report.

  As a reference, CentOS 7 functioned correctly and the battery lasted
  the same time than Windows 10, while Fedora 25 has this problem too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-generic 4.4.0.75.81
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario4786 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Apr 26 12:39:30 2017
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2016-12-31 (116 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-75-generic.efi.signed 
root=UUID=0fbb0f28-6764-4447-a890-dc966d1f8adf ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-75-generic N/A
   linux-backports-modules-4.4.0-75-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN39WW:bd01/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686448/+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

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

The first kernel fixed is 4.16-rc5.

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

Title:
  QCA9377 isn't being recognized sometimes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, the Wireless Network Card QCA9377 is not recognized on
  boot. This caused, on prior versions, a kernel panic at boot. With
  Bionic, the system boots but is unable to use wireless network. On
  dmesg there are messages like:

  [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd
  [2.808640] usb 1-7: device descriptor read/64, error -71
  [3.044337] usb 1-7: device descriptor read/64, error -71
  [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd
  [3.408245] usb 1-7: device descriptor read/64, error -71
  [3.644244] usb 1-7: device descriptor read/64, error -71
  [3.752193] usb usb1-port7: attempt power cycle
  [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd
  [4.404904] usb 1-7: Device not responding to setup address.
  [4.612478] usb 1-7: Device not responding to setup address.
  [4.820588] usb 1-7: device not accepting address 9, error -71
  [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd
  [4.949109] usb 1-7: Device not responding to setup address.
  [5.156893] usb 1-7: Device not responding to setup address.
  [5.364589] usb 1-7: device not accepting address 10, error -71
  [5.364655] usb usb1-port7: unable to enumerate USB device

  And lspci and lsusb don't show the wireless network card. The
  alternative is to turn the system off. Reboot don't work and reboot to
  Windows 10 also don't. The system must be powered off to restore
  functionality. Then, on the next boot, it works properly.

  However, after the system is turned off, it may cause the issue again.
  This is not 100% consistent, but mostly it cycles between powering off
  and powering on the notebook as:

  Work -> Don't work -> Work -> Don't work

  On Windows 10 this doesn't happen but when happens on Ubuntu, it's
  possible to reboot and see the status on Windows 10 too: on Device
  Manager it's shown a unidentified USB device at 1-7. Sometimes, on
  Windows 10's Network Devices it's shown, instead of the QCA9377, from
  four to six different devices with generic names and Bluetooth and/or
  Wireless don't work.

  When turning Ubuntu off, there are messages that appears a few
  instants before the system is turned off:

  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] 
ath10k_pci :02:00.0: failed to install key for vdev 0 peer 
xx:xx:xx:xx:xx:xx: -110
  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] 
wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110)

  Generally, only the second message appears (but both are recorded on
  kern.log). The MAC adress is the one from the router, not from the
  wireless card.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1364 F pulseaudio
   /dev/snd/seq:usuario1258 F timidity
  CurrentDesktop: XFCE
  Date: Tue Mar 20 14:43:42 2018
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2017-06-13 (279 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago)
  dmi.bios.date: 07/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN43WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN43WW:bd07/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

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

[Kernel-packages] [Bug 1686448] Re: Unable to reach higher than package C2 state with Skylake processor