date:20180212

--- Comment From hbath...@in.ibm.com 2018-02-13 02:12 EDT---
(In reply to comment #8)
> This bug was fixed in the package makedumpfile - 1:1.6.3-1
>
> ---
> makedumpfile (1:1.6.3-1) unstable; urgency=medium
>
> * New upstream release. Main new feature:
> o Support new kernels
> - The supported kernel is updated to 4.14.8 in this version. (LP: #1746299)
> 4.14.9 and later can't be filtered correctly due to inappropriate VMCOREINFO,
> it will be resolved in kernel 4.15.
>
> * Changelog:
> o New feature
> - [PATCH v2] x86_64: Take care of init_level4_pgt rename in kernel (by
> Pratyush Anand) 64bd5db
> - [PATCH v2] Fix SECTION_MAP_MASK for kernel >= v.13 (by Pratyush Anand)
> 4bf4f2b
> - [PATCH v2] book3s/ppc64: Lower the max real address to 53 bits for kernels
> >= v4.11
> (by Bhupesh Sharma) 6c83e74
> - [PATCH v3 1/4] Support symbol __cpu_online_mask (by Takao Indoh) 3b11c00
> - [PATCH] ppc64: update hash page table geometry (by Hari Bathini) 3c39f13
> - [PATCH] handle renamed init_level4_pgt -> init_top_pgt (by Jeff Mahoney)
> 5e54d53
>
> o Bugfix
> - [PATCH v2] arm64: Fix page table walk of 1GB section (by Bradley Bolen)
> 27508f1
> - [PATCH v2 1/2] ppc64: set page_offset in get_versiondep_info_ppc64() (by
> Pingfan Liu) 52319d2
> - [PATCH v2 2/2] ppc64: get the info of mem reserved for crashkernel (by
> Pingfan Liu) c7fcbbc
> - [PATCH v3 3/4] sadump: Fix a KASLR problem of sadump (by Takao Indoh)
> b4f7d95
> - [PATCH v3 4/4] sadump: Fix a KASLR problem of sadump while kdump is
> working (by Takao Indoh) 13d3059
> - [PATCH 2/2] Fix 'kernel_version' variable being uninitialized & introduce
> minor reorganization
> (by Bhupesh Sharma) d1ffe82
> - [PATCH 1/2] Fix off-by-one errors in exclude_segment() (by Petr Tesarik)
> 590f35e
> - [PATCH 2/2] Fix physical-to-virtual conversion in exclude_segment() (by
> Petr Tesarik) 6c1bf2a
>
> o Cleanup
> - [PATCH] Fix formatting problems in header file (by Eric DeVolder) cefea9e
> - [PATCH v3 2/4] Introduce vtop4_x86_64_pagetable (by Takao Indoh) 6de5d37
> - [PATCH 1/2] Fix compilation warnings on ppc64/ppc64le platforms (by
> Bhupesh Sharma) 0df157a
> - [PATCH] Make good use of is_cyclic_region() (by Atsushi Kumagai) 6bfd7a3
> - [PATCH] Fix the regression about getting kernel version (by Atsushi
> Kumagai) 254c116
> - [PATCH] Update maintainers (by Atsushi Kumagai) 9d3147e
>
> * Use multi-user.target. (LP: #1708409)
> * kdump-tools Recommends initramfs-tools-core.
> * Add myself as uploader.
> * Move Vcs control fields to salsa.
>
> -- Thadeu Lima de Souza Cascardo   Tue, 06 Feb 2018
> 12:53:14 -0200

Hello Cascardo, we don't see the fix package in -proposed yet.
When could we expect it there..?

Thanks
Hari

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

Title:
  update makedumpfile tool version to v1.6.3

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  New upstream kernel versions, as those in linux-hwe package, require a newer 
makedumpfile to be supported. Otherwise, all copies fallback to copying the 
entire memory.

  [Test case]
  kdump-tools has been installed, system rebooted, then crash trigerred and 
verified that a small dump file was present on /var/crash/. Tested on amd64 and 
ppc64le.

  [Regression potential]
  Many other bug fixes have been included in the latest version of the package. 
The changes are supposed to fix these bugs, and have been tested as well. 
However, as the total of changes is not trivial, there is impact of regression 
that has been minimized by the tests done. Regression potential of not 
supporting older kernels has been tested with the kernels shipped on xenial and 
artful as well.


  
  

  == Comment: #0 - Hari Krishna Bathini  - 2018-01-30 
10:46:53 ==
  ---Problem Description---
  update makedumpfile to latest version v1.6.3 that officially supports
  up to kernel version 4.14.8. Since makedumpfile is inherently backward 
compatible,
  this would not break existing functionality..

  Contact Information = hbath...@in.ibm.com

  ---uname output---
  na

  Machine Type = na

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

  ---Steps to Reproduce---
   makedumpfile reports ""The kernel version is not supported" while generating 
vmcore
  Also, there is a possibility of bogus address translations in makedumpfile 
tool with
  missing upstream patches. Can't be so sure without an exhaustive testing. 
Instead,
  it would be a good idea to go with the version which officially supports the 
kernel
  version in question.

  Userspace tool common name: makedumpfile

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: makedumpfile

  Userspace tool obtained from project website:  na

  *Additional Instructi

[Kernel-packages] [Bug 1749058] Re: incorrect source address in IGMP Membership Report messages

I think I should also have mentioned that I had tried a couple of things
all in vain, they all resulted in the same unchanged value at source
address field in the IGMP packets:


1) A route-map in quagga:
ip prefix-list p4-multicast seq 5 permit 224.0.0.0/4
!
route-map filter-multicast-4 permit 10
 match ip address prefix-list p4-multicast
 set src 10.0.0.48
!
route-map set-src permit 10
 set src 10.0.0.48
!
ip protocol any route-map filter-multicast-4


2) A route directly in the linux routing table:

ip route replace 224.0.0.0/4 src 10.0.0.48 dev fabric1


3) A SNAT line in iptables:

iptables -t nat -A POSTROUTING --dst 224.0.0.0/4 -j SNAT --to-source
10.0.0.48


Thank you,
Gunwoo

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

Title:
  incorrect source address in IGMP Membership Report messages

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I found that linux kernel had had a bug in the implementation of IGMP
  membership report packet generation. the RFC documents for IGMP version 2
  and 3 says that you must ignore the reports with a source ip address that
  you can't identify as belonging to a network assigned to the interface on
  which the packet was received. and the networking OS in the ToR switch,
  Force10 OS 9 does ignore it.

  I've also figured out a patch has been made for this bug in Linus's Github.
  and there was a mark on Github that reads "v4.16-rc1". (
  
https://github.com/torvalds/linux/commit/a46182b00290839fa3fa159d54fd3237bd8669f0
   )

  I honestly have no idea how Ubuntu LTS team works with regard to this kind
  of patches from the fresh new upstream version of linux kernel. hope you
  guys will easily fix it for people like me who has no experience at
  building and distributing custom built kernels over a few servers.

  Test environment:
  I used two ToR switches and one linux machine for this test.
  I only used 2 ethernet ports on the linux machine.
  There was a recent version of Ubuntu with HWE kernel. I'm not sure if
  no-HWE one would be the same case - the version of linux-generic-hwe-16.04
  was 4.13.0.32.52 -
  To test networking router stuff, I used the quagga from Cumulus Routing on
  the Host 3.3.2 (
  
https://cumulusnetworks.com/products/cumulus-routing-on-the-host/#roh-download-section
   )

  What I did and saw in my case:
  1. set a network interface (A) so it gets an IPv4 address, but also in vain
  issue "ip link set ${if_name} multicast off"
  2. assign an IPv4 address to another network interface (B), but in this
  case with a 31-bit-long subnet mask length.
  3. install quagga from cumulus, launch zebra and pimd, issue "ip pim sm" in
  the interface configuration mode for the interface (B) with a 31-bit-long
  subnet mask length
  4. I checked that the source IP address part of the IGMP membership report
  packets from the linux machine is the address I assigned to the network
  interface (A) with 27-bit-long subnet mask -using dumpcap and tshark-, and
  that the PIM service on the switch ignored the Reports printing debugging
  messages including : "Invalid sender address"

   affects ubuntu

  Regards,
  Gunwoo
  -- 
  You can find my PGP public key here: https://google.com/+DewrKim/about

  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 12 15:36 seq
   crw-rw 1 root audio 116, 33 Feb 12 15:36 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/peta--0001--01--vg-swap_1
  InstallationDate: Installed on 2017-07-05 (223 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL360 G6
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=/dev/mapper/peta--0001--01--vg-root ro 
isolcpus=4,8,12,16,20,24,28,6,10,14,18,22,26,30 hugepagesz=1G hugepages=0 
hugepagesz=2M hugepages=2048
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.13.0-32-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh ins

[Kernel-packages] [Bug 1749058] WifiSyslog.txt

apport information

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

** 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/1749058

Title:
  incorrect source address in IGMP Membership Report messages

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I found that linux kernel had had a bug in the implementation of IGMP
  membership report packet generation. the RFC documents for IGMP version 2
  and 3 says that you must ignore the reports with a source ip address that
  you can't identify as belonging to a network assigned to the interface on
  which the packet was received. and the networking OS in the ToR switch,
  Force10 OS 9 does ignore it.

  I've also figured out a patch has been made for this bug in Linus's Github.
  and there was a mark on Github that reads "v4.16-rc1". (
  
https://github.com/torvalds/linux/commit/a46182b00290839fa3fa159d54fd3237bd8669f0
   )

  I honestly have no idea how Ubuntu LTS team works with regard to this kind
  of patches from the fresh new upstream version of linux kernel. hope you
  guys will easily fix it for people like me who has no experience at
  building and distributing custom built kernels over a few servers.

  Test environment:
  I used two ToR switches and one linux machine for this test.
  I only used 2 ethernet ports on the linux machine.
  There was a recent version of Ubuntu with HWE kernel. I'm not sure if
  no-HWE one would be the same case - the version of linux-generic-hwe-16.04
  was 4.13.0.32.52 -
  To test networking router stuff, I used the quagga from Cumulus Routing on
  the Host 3.3.2 (
  
https://cumulusnetworks.com/products/cumulus-routing-on-the-host/#roh-download-section
   )

  What I did and saw in my case:
  1. set a network interface (A) so it gets an IPv4 address, but also in vain
  issue "ip link set ${if_name} multicast off"
  2. assign an IPv4 address to another network interface (B), but in this
  case with a 31-bit-long subnet mask length.
  3. install quagga from cumulus, launch zebra and pimd, issue "ip pim sm" in
  the interface configuration mode for the interface (B) with a 31-bit-long
  subnet mask length
  4. I checked that the source IP address part of the IGMP membership report
  packets from the linux machine is the address I assigned to the network
  interface (A) with 27-bit-long subnet mask -using dumpcap and tshark-, and
  that the PIM service on the switch ignored the Reports printing debugging
  messages including : "Invalid sender address"

   affects ubuntu

  Regards,
  Gunwoo
  -- 
  You can find my PGP public key here: https://google.com/+DewrKim/about

  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 12 15:36 seq
   crw-rw 1 root audio 116, 33 Feb 12 15:36 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/peta--0001--01--vg-swap_1
  InstallationDate: Installed on 2017-07-05 (223 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL360 G6
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=/dev/mapper/peta--0001--01--vg-root ro 
isolcpus=4,8,12,16,20,24,28,6,10,14,18,22,26,30 hugepagesz=1G hugepages=0 
hugepagesz=2M hugepages=2048
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.13.0-32-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 08/16/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P64
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP64:bd08/16/2015:svnHP:pnProLiantDL360G6:pvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 G6
  dmi.sys.vendor: HP

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

--

[Kernel-packages] [Bug 1749058] JournalErrors.txt

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1749058/+attachment/5053990/+files/JournalErrors.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/1749058

Title:
  incorrect source address in IGMP Membership Report messages

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I found that linux kernel had had a bug in the implementation of IGMP
  membership report packet generation. the RFC documents for IGMP version 2
  and 3 says that you must ignore the reports with a source ip address that
  you can't identify as belonging to a network assigned to the interface on
  which the packet was received. and the networking OS in the ToR switch,
  Force10 OS 9 does ignore it.

  I've also figured out a patch has been made for this bug in Linus's Github.
  and there was a mark on Github that reads "v4.16-rc1". (
  
https://github.com/torvalds/linux/commit/a46182b00290839fa3fa159d54fd3237bd8669f0
   )

  I honestly have no idea how Ubuntu LTS team works with regard to this kind
  of patches from the fresh new upstream version of linux kernel. hope you
  guys will easily fix it for people like me who has no experience at
  building and distributing custom built kernels over a few servers.

  Test environment:
  I used two ToR switches and one linux machine for this test.
  I only used 2 ethernet ports on the linux machine.
  There was a recent version of Ubuntu with HWE kernel. I'm not sure if
  no-HWE one would be the same case - the version of linux-generic-hwe-16.04
  was 4.13.0.32.52 -
  To test networking router stuff, I used the quagga from Cumulus Routing on
  the Host 3.3.2 (
  
https://cumulusnetworks.com/products/cumulus-routing-on-the-host/#roh-download-section
   )

  What I did and saw in my case:
  1. set a network interface (A) so it gets an IPv4 address, but also in vain
  issue "ip link set ${if_name} multicast off"
  2. assign an IPv4 address to another network interface (B), but in this
  case with a 31-bit-long subnet mask length.
  3. install quagga from cumulus, launch zebra and pimd, issue "ip pim sm" in
  the interface configuration mode for the interface (B) with a 31-bit-long
  subnet mask length
  4. I checked that the source IP address part of the IGMP membership report
  packets from the linux machine is the address I assigned to the network
  interface (A) with 27-bit-long subnet mask -using dumpcap and tshark-, and
  that the PIM service on the switch ignored the Reports printing debugging
  messages including : "Invalid sender address"

   affects ubuntu

  Regards,
  Gunwoo
  -- 
  You can find my PGP public key here: https://google.com/+DewrKim/about

  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 12 15:36 seq
   crw-rw 1 root audio 116, 33 Feb 12 15:36 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/peta--0001--01--vg-swap_1
  InstallationDate: Installed on 2017-07-05 (223 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL360 G6
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=/dev/mapper/peta--0001--01--vg-root ro 
isolcpus=4,8,12,16,20,24,28,6,10,14,18,22,26,30 hugepagesz=1G hugepages=0 
hugepagesz=2M hugepages=2048
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.13.0-32-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 08/16/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P64
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP64:bd08/16/2015:svnHP:pnProLiantDL360G6:pvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 G6
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to

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

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1749058/+attachment/5053996/+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/1749058

Title:
  incorrect source address in IGMP Membership Report messages

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I found that linux kernel had had a bug in the implementation of IGMP
  membership report packet generation. the RFC documents for IGMP version 2
  and 3 says that you must ignore the reports with a source ip address that
  you can't identify as belonging to a network assigned to the interface on
  which the packet was received. and the networking OS in the ToR switch,
  Force10 OS 9 does ignore it.

  I've also figured out a patch has been made for this bug in Linus's Github.
  and there was a mark on Github that reads "v4.16-rc1". (
  
https://github.com/torvalds/linux/commit/a46182b00290839fa3fa159d54fd3237bd8669f0
   )

  I honestly have no idea how Ubuntu LTS team works with regard to this kind
  of patches from the fresh new upstream version of linux kernel. hope you
  guys will easily fix it for people like me who has no experience at
  building and distributing custom built kernels over a few servers.

  Test environment:
  I used two ToR switches and one linux machine for this test.
  I only used 2 ethernet ports on the linux machine.
  There was a recent version of Ubuntu with HWE kernel. I'm not sure if
  no-HWE one would be the same case - the version of linux-generic-hwe-16.04
  was 4.13.0.32.52 -
  To test networking router stuff, I used the quagga from Cumulus Routing on
  the Host 3.3.2 (
  
https://cumulusnetworks.com/products/cumulus-routing-on-the-host/#roh-download-section
   )

  What I did and saw in my case:
  1. set a network interface (A) so it gets an IPv4 address, but also in vain
  issue "ip link set ${if_name} multicast off"
  2. assign an IPv4 address to another network interface (B), but in this
  case with a 31-bit-long subnet mask length.
  3. install quagga from cumulus, launch zebra and pimd, issue "ip pim sm" in
  the interface configuration mode for the interface (B) with a 31-bit-long
  subnet mask length
  4. I checked that the source IP address part of the IGMP membership report
  packets from the linux machine is the address I assigned to the network
  interface (A) with 27-bit-long subnet mask -using dumpcap and tshark-, and
  that the PIM service on the switch ignored the Reports printing debugging
  messages including : "Invalid sender address"

   affects ubuntu

  Regards,
  Gunwoo
  -- 
  You can find my PGP public key here: https://google.com/+DewrKim/about

  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 12 15:36 seq
   crw-rw 1 root audio 116, 33 Feb 12 15:36 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/peta--0001--01--vg-swap_1
  InstallationDate: Installed on 2017-07-05 (223 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL360 G6
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=/dev/mapper/peta--0001--01--vg-root ro 
isolcpus=4,8,12,16,20,24,28,6,10,14,18,22,26,30 hugepagesz=1G hugepages=0 
hugepagesz=2M hugepages=2048
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.13.0-32-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 08/16/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P64
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP64:bd08/16/2015:svnHP:pnProLiantDL360G6:pvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 G6
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packa

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

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1749058/+attachment/5053991/+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/1749058

Title:
  incorrect source address in IGMP Membership Report messages

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I found that linux kernel had had a bug in the implementation of IGMP
  membership report packet generation. the RFC documents for IGMP version 2
  and 3 says that you must ignore the reports with a source ip address that
  you can't identify as belonging to a network assigned to the interface on
  which the packet was received. and the networking OS in the ToR switch,
  Force10 OS 9 does ignore it.

  I've also figured out a patch has been made for this bug in Linus's Github.
  and there was a mark on Github that reads "v4.16-rc1". (
  
https://github.com/torvalds/linux/commit/a46182b00290839fa3fa159d54fd3237bd8669f0
   )

  I honestly have no idea how Ubuntu LTS team works with regard to this kind
  of patches from the fresh new upstream version of linux kernel. hope you
  guys will easily fix it for people like me who has no experience at
  building and distributing custom built kernels over a few servers.

  Test environment:
  I used two ToR switches and one linux machine for this test.
  I only used 2 ethernet ports on the linux machine.
  There was a recent version of Ubuntu with HWE kernel. I'm not sure if
  no-HWE one would be the same case - the version of linux-generic-hwe-16.04
  was 4.13.0.32.52 -
  To test networking router stuff, I used the quagga from Cumulus Routing on
  the Host 3.3.2 (
  
https://cumulusnetworks.com/products/cumulus-routing-on-the-host/#roh-download-section
   )

  What I did and saw in my case:
  1. set a network interface (A) so it gets an IPv4 address, but also in vain
  issue "ip link set ${if_name} multicast off"
  2. assign an IPv4 address to another network interface (B), but in this
  case with a 31-bit-long subnet mask length.
  3. install quagga from cumulus, launch zebra and pimd, issue "ip pim sm" in
  the interface configuration mode for the interface (B) with a 31-bit-long
  subnet mask length
  4. I checked that the source IP address part of the IGMP membership report
  packets from the linux machine is the address I assigned to the network
  interface (A) with 27-bit-long subnet mask -using dumpcap and tshark-, and
  that the PIM service on the switch ignored the Reports printing debugging
  messages including : "Invalid sender address"

   affects ubuntu

  Regards,
  Gunwoo
  -- 
  You can find my PGP public key here: https://google.com/+DewrKim/about

  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 12 15:36 seq
   crw-rw 1 root audio 116, 33 Feb 12 15:36 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/peta--0001--01--vg-swap_1
  InstallationDate: Installed on 2017-07-05 (223 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL360 G6
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=/dev/mapper/peta--0001--01--vg-root ro 
isolcpus=4,8,12,16,20,24,28,6,10,14,18,22,26,30 hugepagesz=1G hugepages=0 
hugepagesz=2M hugepages=2048
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.13.0-32-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 08/16/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P64
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP64:bd08/16/2015:svnHP:pnProLiantDL360G6:pvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 G6
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-package

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

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1749058/+attachment/5053995/+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/1749058

Title:
  incorrect source address in IGMP Membership Report messages

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I found that linux kernel had had a bug in the implementation of IGMP
  membership report packet generation. the RFC documents for IGMP version 2
  and 3 says that you must ignore the reports with a source ip address that
  you can't identify as belonging to a network assigned to the interface on
  which the packet was received. and the networking OS in the ToR switch,
  Force10 OS 9 does ignore it.

  I've also figured out a patch has been made for this bug in Linus's Github.
  and there was a mark on Github that reads "v4.16-rc1". (
  
https://github.com/torvalds/linux/commit/a46182b00290839fa3fa159d54fd3237bd8669f0
   )

  I honestly have no idea how Ubuntu LTS team works with regard to this kind
  of patches from the fresh new upstream version of linux kernel. hope you
  guys will easily fix it for people like me who has no experience at
  building and distributing custom built kernels over a few servers.

  Test environment:
  I used two ToR switches and one linux machine for this test.
  I only used 2 ethernet ports on the linux machine.
  There was a recent version of Ubuntu with HWE kernel. I'm not sure if
  no-HWE one would be the same case - the version of linux-generic-hwe-16.04
  was 4.13.0.32.52 -
  To test networking router stuff, I used the quagga from Cumulus Routing on
  the Host 3.3.2 (
  
https://cumulusnetworks.com/products/cumulus-routing-on-the-host/#roh-download-section
   )

  What I did and saw in my case:
  1. set a network interface (A) so it gets an IPv4 address, but also in vain
  issue "ip link set ${if_name} multicast off"
  2. assign an IPv4 address to another network interface (B), but in this
  case with a 31-bit-long subnet mask length.
  3. install quagga from cumulus, launch zebra and pimd, issue "ip pim sm" in
  the interface configuration mode for the interface (B) with a 31-bit-long
  subnet mask length
  4. I checked that the source IP address part of the IGMP membership report
  packets from the linux machine is the address I assigned to the network
  interface (A) with 27-bit-long subnet mask -using dumpcap and tshark-, and
  that the PIM service on the switch ignored the Reports printing debugging
  messages including : "Invalid sender address"

   affects ubuntu

  Regards,
  Gunwoo
  -- 
  You can find my PGP public key here: https://google.com/+DewrKim/about

  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 12 15:36 seq
   crw-rw 1 root audio 116, 33 Feb 12 15:36 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/peta--0001--01--vg-swap_1
  InstallationDate: Installed on 2017-07-05 (223 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL360 G6
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=/dev/mapper/peta--0001--01--vg-root ro 
isolcpus=4,8,12,16,20,24,28,6,10,14,18,22,26,30 hugepagesz=1G hugepages=0 
hugepagesz=2M hugepages=2048
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.13.0-32-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 08/16/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P64
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP64:bd08/16/2015:svnHP:pnProLiantDL360G6:pvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 G6
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : k

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

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1749058/+attachment/5053994/+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/1749058

Title:
  incorrect source address in IGMP Membership Report messages

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I found that linux kernel had had a bug in the implementation of IGMP
  membership report packet generation. the RFC documents for IGMP version 2
  and 3 says that you must ignore the reports with a source ip address that
  you can't identify as belonging to a network assigned to the interface on
  which the packet was received. and the networking OS in the ToR switch,
  Force10 OS 9 does ignore it.

  I've also figured out a patch has been made for this bug in Linus's Github.
  and there was a mark on Github that reads "v4.16-rc1". (
  
https://github.com/torvalds/linux/commit/a46182b00290839fa3fa159d54fd3237bd8669f0
   )

  I honestly have no idea how Ubuntu LTS team works with regard to this kind
  of patches from the fresh new upstream version of linux kernel. hope you
  guys will easily fix it for people like me who has no experience at
  building and distributing custom built kernels over a few servers.

  Test environment:
  I used two ToR switches and one linux machine for this test.
  I only used 2 ethernet ports on the linux machine.
  There was a recent version of Ubuntu with HWE kernel. I'm not sure if
  no-HWE one would be the same case - the version of linux-generic-hwe-16.04
  was 4.13.0.32.52 -
  To test networking router stuff, I used the quagga from Cumulus Routing on
  the Host 3.3.2 (
  
https://cumulusnetworks.com/products/cumulus-routing-on-the-host/#roh-download-section
   )

  What I did and saw in my case:
  1. set a network interface (A) so it gets an IPv4 address, but also in vain
  issue "ip link set ${if_name} multicast off"
  2. assign an IPv4 address to another network interface (B), but in this
  case with a 31-bit-long subnet mask length.
  3. install quagga from cumulus, launch zebra and pimd, issue "ip pim sm" in
  the interface configuration mode for the interface (B) with a 31-bit-long
  subnet mask length
  4. I checked that the source IP address part of the IGMP membership report
  packets from the linux machine is the address I assigned to the network
  interface (A) with 27-bit-long subnet mask -using dumpcap and tshark-, and
  that the PIM service on the switch ignored the Reports printing debugging
  messages including : "Invalid sender address"

   affects ubuntu

  Regards,
  Gunwoo
  -- 
  You can find my PGP public key here: https://google.com/+DewrKim/about

  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 12 15:36 seq
   crw-rw 1 root audio 116, 33 Feb 12 15:36 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/peta--0001--01--vg-swap_1
  InstallationDate: Installed on 2017-07-05 (223 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL360 G6
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=/dev/mapper/peta--0001--01--vg-root ro 
isolcpus=4,8,12,16,20,24,28,6,10,14,18,22,26,30 hugepagesz=1G hugepages=0 
hugepagesz=2M hugepages=2048
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.13.0-32-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 08/16/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P64
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP64:bd08/16/2015:svnHP:pnProLiantDL360G6:pvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 G6
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to

[Kernel-packages] [Bug 1749058] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1749058/+attachment/5053992/+files/Lsusb.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/1749058

Title:
  incorrect source address in IGMP Membership Report messages

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I found that linux kernel had had a bug in the implementation of IGMP
  membership report packet generation. the RFC documents for IGMP version 2
  and 3 says that you must ignore the reports with a source ip address that
  you can't identify as belonging to a network assigned to the interface on
  which the packet was received. and the networking OS in the ToR switch,
  Force10 OS 9 does ignore it.

  I've also figured out a patch has been made for this bug in Linus's Github.
  and there was a mark on Github that reads "v4.16-rc1". (
  
https://github.com/torvalds/linux/commit/a46182b00290839fa3fa159d54fd3237bd8669f0
   )

  I honestly have no idea how Ubuntu LTS team works with regard to this kind
  of patches from the fresh new upstream version of linux kernel. hope you
  guys will easily fix it for people like me who has no experience at
  building and distributing custom built kernels over a few servers.

  Test environment:
  I used two ToR switches and one linux machine for this test.
  I only used 2 ethernet ports on the linux machine.
  There was a recent version of Ubuntu with HWE kernel. I'm not sure if
  no-HWE one would be the same case - the version of linux-generic-hwe-16.04
  was 4.13.0.32.52 -
  To test networking router stuff, I used the quagga from Cumulus Routing on
  the Host 3.3.2 (
  
https://cumulusnetworks.com/products/cumulus-routing-on-the-host/#roh-download-section
   )

  What I did and saw in my case:
  1. set a network interface (A) so it gets an IPv4 address, but also in vain
  issue "ip link set ${if_name} multicast off"
  2. assign an IPv4 address to another network interface (B), but in this
  case with a 31-bit-long subnet mask length.
  3. install quagga from cumulus, launch zebra and pimd, issue "ip pim sm" in
  the interface configuration mode for the interface (B) with a 31-bit-long
  subnet mask length
  4. I checked that the source IP address part of the IGMP membership report
  packets from the linux machine is the address I assigned to the network
  interface (A) with 27-bit-long subnet mask -using dumpcap and tshark-, and
  that the PIM service on the switch ignored the Reports printing debugging
  messages including : "Invalid sender address"

   affects ubuntu

  Regards,
  Gunwoo
  -- 
  You can find my PGP public key here: https://google.com/+DewrKim/about

  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 12 15:36 seq
   crw-rw 1 root audio 116, 33 Feb 12 15:36 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/peta--0001--01--vg-swap_1
  InstallationDate: Installed on 2017-07-05 (223 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL360 G6
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=/dev/mapper/peta--0001--01--vg-root ro 
isolcpus=4,8,12,16,20,24,28,6,10,14,18,22,26,30 hugepagesz=1G hugepages=0 
hugepagesz=2M hugepages=2048
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.13.0-32-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 08/16/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P64
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP64:bd08/16/2015:svnHP:pnProLiantDL360G6:pvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 G6
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-package

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

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1749058/+attachment/5053993/+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/1749058

Title:
  incorrect source address in IGMP Membership Report messages

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I found that linux kernel had had a bug in the implementation of IGMP
  membership report packet generation. the RFC documents for IGMP version 2
  and 3 says that you must ignore the reports with a source ip address that
  you can't identify as belonging to a network assigned to the interface on
  which the packet was received. and the networking OS in the ToR switch,
  Force10 OS 9 does ignore it.

  I've also figured out a patch has been made for this bug in Linus's Github.
  and there was a mark on Github that reads "v4.16-rc1". (
  
https://github.com/torvalds/linux/commit/a46182b00290839fa3fa159d54fd3237bd8669f0
   )

  I honestly have no idea how Ubuntu LTS team works with regard to this kind
  of patches from the fresh new upstream version of linux kernel. hope you
  guys will easily fix it for people like me who has no experience at
  building and distributing custom built kernels over a few servers.

  Test environment:
  I used two ToR switches and one linux machine for this test.
  I only used 2 ethernet ports on the linux machine.
  There was a recent version of Ubuntu with HWE kernel. I'm not sure if
  no-HWE one would be the same case - the version of linux-generic-hwe-16.04
  was 4.13.0.32.52 -
  To test networking router stuff, I used the quagga from Cumulus Routing on
  the Host 3.3.2 (
  
https://cumulusnetworks.com/products/cumulus-routing-on-the-host/#roh-download-section
   )

  What I did and saw in my case:
  1. set a network interface (A) so it gets an IPv4 address, but also in vain
  issue "ip link set ${if_name} multicast off"
  2. assign an IPv4 address to another network interface (B), but in this
  case with a 31-bit-long subnet mask length.
  3. install quagga from cumulus, launch zebra and pimd, issue "ip pim sm" in
  the interface configuration mode for the interface (B) with a 31-bit-long
  subnet mask length
  4. I checked that the source IP address part of the IGMP membership report
  packets from the linux machine is the address I assigned to the network
  interface (A) with 27-bit-long subnet mask -using dumpcap and tshark-, and
  that the PIM service on the switch ignored the Reports printing debugging
  messages including : "Invalid sender address"

   affects ubuntu

  Regards,
  Gunwoo
  -- 
  You can find my PGP public key here: https://google.com/+DewrKim/about

  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 12 15:36 seq
   crw-rw 1 root audio 116, 33 Feb 12 15:36 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/peta--0001--01--vg-swap_1
  InstallationDate: Installed on 2017-07-05 (223 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL360 G6
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=/dev/mapper/peta--0001--01--vg-root ro 
isolcpus=4,8,12,16,20,24,28,6,10,14,18,22,26,30 hugepagesz=1G hugepages=0 
hugepagesz=2M hugepages=2048
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.13.0-32-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 08/16/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P64
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP64:bd08/16/2015:svnHP:pnProLiantDL360G6:pvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 G6
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
P

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

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1749058/+attachment/5053989/+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/1749058

Title:
  incorrect source address in IGMP Membership Report messages

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I found that linux kernel had had a bug in the implementation of IGMP
  membership report packet generation. the RFC documents for IGMP version 2
  and 3 says that you must ignore the reports with a source ip address that
  you can't identify as belonging to a network assigned to the interface on
  which the packet was received. and the networking OS in the ToR switch,
  Force10 OS 9 does ignore it.

  I've also figured out a patch has been made for this bug in Linus's Github.
  and there was a mark on Github that reads "v4.16-rc1". (
  
https://github.com/torvalds/linux/commit/a46182b00290839fa3fa159d54fd3237bd8669f0
   )

  I honestly have no idea how Ubuntu LTS team works with regard to this kind
  of patches from the fresh new upstream version of linux kernel. hope you
  guys will easily fix it for people like me who has no experience at
  building and distributing custom built kernels over a few servers.

  Test environment:
  I used two ToR switches and one linux machine for this test.
  I only used 2 ethernet ports on the linux machine.
  There was a recent version of Ubuntu with HWE kernel. I'm not sure if
  no-HWE one would be the same case - the version of linux-generic-hwe-16.04
  was 4.13.0.32.52 -
  To test networking router stuff, I used the quagga from Cumulus Routing on
  the Host 3.3.2 (
  
https://cumulusnetworks.com/products/cumulus-routing-on-the-host/#roh-download-section
   )

  What I did and saw in my case:
  1. set a network interface (A) so it gets an IPv4 address, but also in vain
  issue "ip link set ${if_name} multicast off"
  2. assign an IPv4 address to another network interface (B), but in this
  case with a 31-bit-long subnet mask length.
  3. install quagga from cumulus, launch zebra and pimd, issue "ip pim sm" in
  the interface configuration mode for the interface (B) with a 31-bit-long
  subnet mask length
  4. I checked that the source IP address part of the IGMP membership report
  packets from the linux machine is the address I assigned to the network
  interface (A) with 27-bit-long subnet mask -using dumpcap and tshark-, and
  that the PIM service on the switch ignored the Reports printing debugging
  messages including : "Invalid sender address"

   affects ubuntu

  Regards,
  Gunwoo
  -- 
  You can find my PGP public key here: https://google.com/+DewrKim/about

  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 12 15:36 seq
   crw-rw 1 root audio 116, 33 Feb 12 15:36 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/peta--0001--01--vg-swap_1
  InstallationDate: Installed on 2017-07-05 (223 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL360 G6
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=/dev/mapper/peta--0001--01--vg-root ro 
isolcpus=4,8,12,16,20,24,28,6,10,14,18,22,26,30 hugepagesz=1G hugepages=0 
hugepagesz=2M hugepages=2048
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.13.0-32-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 08/16/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P64
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP64:bd08/16/2015:svnHP:pnProLiantDL360G6:pvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 G6
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to :

[Kernel-packages] [Bug 1746088] Comment bridged from LTC Bugzilla

--- Comment From mputt...@in.ibm.com 2018-02-13 01:26 EDT---
Reminder 2: Please advice if the fix have been picked up?

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

Title:
  [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on
  4.13.0-26-generic kernel

Status in The Ubuntu-power-systems project:
  Triaged
Status in crash package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel 
(Ubuntu 16.04.4)
   
  ---uname output---
  Linux ltc-briggs1 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 21:40:36 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8001-22C 

  ---Steps to Reproduce---
   This bug follow up bug of 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=163565
  The steps to create dump is as follows 

  Once you generate the kdump 
  use crash to analyze the vmcore and we get this error 

  console logs ==

  root@ltc-briggs1:/var/crash/201801150227# ls
  dmesg.201801150227  vmcore.201801150227
  .0-26-generic vmcore.2018011502271150227# crash 
/usr/lib/debug/boot/vmlinux-4.13.

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
   
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)   
  WARNING: cannot access vmalloc'd module memory

  
  crash: invalid structure member offset: thread_info_task
 FILE: task.c  LINE: 598  FUNCTION: irqstacks_init()

  [/usr/bin/crash] error trace: 1008ade0 => 1011552c => 1017d220 =>
  100833e0

100833e0: (undetermined)
1017d220: OFFSET_verify+80
1011552c: task_init+5084
1008ade0: main_loop+336

  == Comment from Hari Krishna Bathini ==

  There are quite a few commits (all available upstream) that are needed for
  crash tool to work fine. I think the right thing to do here would be to use
  the latest crash tool version 7.2.0 to go with the kernel update. Also, the
  below commit would be needed on top of 7.2.0 crash utility:

commit c8178eca9c74f81a7f803a58d339635cc152e8d9
Author: Dave Anderson 
Date:   Thu Nov 9 11:39:05 2017 -0500

  Update for support of Linux 4.14 and later PPC64 kernels where the
  hash page table geometry accomodates a larger virtual address range.
  Without the patch, the virtual-to-physical translation of user space
  virtual addresses by "vm -p", "vtop", and "rd -u" may generate an
  invalid translation or otherwise fail.
  (hbath...@linux.vnet.ibm.com)

  Similar thing holds true for makedumpfile tool..

  Thanks
  Hari

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1746088/+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 1749058] Re: incorrect source address in IGMP Membership Report messages

apport information

** Tags added: apport-collected xenial

** Description changed:

  I found that linux kernel had had a bug in the implementation of IGMP
  membership report packet generation. the RFC documents for IGMP version 2
  and 3 says that you must ignore the reports with a source ip address that
  you can't identify as belonging to a network assigned to the interface on
  which the packet was received. and the networking OS in the ToR switch,
  Force10 OS 9 does ignore it.
  
  I've also figured out a patch has been made for this bug in Linus's Github.
  and there was a mark on Github that reads "v4.16-rc1". (
  
https://github.com/torvalds/linux/commit/a46182b00290839fa3fa159d54fd3237bd8669f0
   )
  
  I honestly have no idea how Ubuntu LTS team works with regard to this kind
  of patches from the fresh new upstream version of linux kernel. hope you
  guys will easily fix it for people like me who has no experience at
  building and distributing custom built kernels over a few servers.
  
  Test environment:
  I used two ToR switches and one linux machine for this test.
  I only used 2 ethernet ports on the linux machine.
  There was a recent version of Ubuntu with HWE kernel. I'm not sure if
  no-HWE one would be the same case - the version of linux-generic-hwe-16.04
  was 4.13.0.32.52 -
  To test networking router stuff, I used the quagga from Cumulus Routing on
  the Host 3.3.2 (
  
https://cumulusnetworks.com/products/cumulus-routing-on-the-host/#roh-download-section
   )
  
  What I did and saw in my case:
  1. set a network interface (A) so it gets an IPv4 address, but also in vain
  issue "ip link set ${if_name} multicast off"
  2. assign an IPv4 address to another network interface (B), but in this
  case with a 31-bit-long subnet mask length.
  3. install quagga from cumulus, launch zebra and pimd, issue "ip pim sm" in
  the interface configuration mode for the interface (B) with a 31-bit-long
  subnet mask length
  4. I checked that the source IP address part of the IGMP membership report
  packets from the linux machine is the address I assigned to the network
  interface (A) with 27-bit-long subnet mask -using dumpcap and tshark-, and
  that the PIM service on the switch ignored the Reports printing debugging
  messages including : "Invalid sender address"
  
   affects ubuntu
  
  Regards,
  Gunwoo
  -- 
  You can find my PGP public key here: https://google.com/+DewrKim/about
+ 
+ --- 
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 Feb 12 15:36 seq
+  crw-rw 1 root audio 116, 33 Feb 12 15:36 timer
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.20.1-0ubuntu2.15
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=/dev/mapper/peta--0001--01--vg-swap_1
+ InstallationDate: Installed on 2017-07-05 (223 days ago)
+ InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
+ IwConfig: Error: [Errno 2] No such file or directory
+ MachineType: HP ProLiant DL360 G6
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 radeondrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=/dev/mapper/peta--0001--01--vg-root ro 
isolcpus=4,8,12,16,20,24,28,6,10,14,18,22,26,30 hugepagesz=1G hugepages=0 
hugepagesz=2M hugepages=2048
+ ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
+ RelatedPackageVersions:
+  linux-restricted-modules-4.13.0-32-generic N/A
+  linux-backports-modules-4.13.0-32-generic  N/A
+  linux-firmware 1.157.14
+ RfKill: Error: [Errno 2] No such file or directory
+ Tags:  xenial xenial
+ Uname: Linux 4.13.0-32-generic x86_64
+ UnreportableReason: The report belongs to a package that is not installed.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: False
+ dmi.bios.date: 08/16/2015
+ dmi.bios.vendor: HP
+ dmi.bios.version: P64
+ dmi.chassis.type: 23
+ dmi.chassis.vendor: HP
+ dmi.modalias: 
dmi:bvnHP:bvrP64:bd08/16/2015:svnHP:pnProLiantDL360G6:pvr:cvnHP:ct23:cvr:
+ dmi.product.family: ProLiant
+ dmi.product.name: ProLiant DL360 G6
+ dmi.sys.vendor: HP

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1749058/+attachment/5053988/+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/1749058

Title:
  incorrect source address in IGMP Membership Report messages

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I found that linux kernel had had a bug in the implementation of IGMP
  membership report packet generation. the RFC documents fo

[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)

2018-02-12 Thread Lucas Zanella

Ok, just installed it. Gonna monitor it to see if any errors come up

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lz 1088 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-01-30 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Razer Blade Stealth
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=0ca062

[Kernel-packages] [Bug 1749058] Re: incorrect source address in IGMP Membership Report messages

I'm sorry that I confused with the IGMP service with the PIM service on
Dell FTOS 9, which printed the debugging message "Invalid sender
address"

and I think you can just test the igmp connection by issuing "ping
224.0.0.1" instead of installing quagga and launching pimd.

Best regards,
Gunwoo

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

Title:
  incorrect source address in IGMP Membership Report messages

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I found that linux kernel had had a bug in the implementation of IGMP
  membership report packet generation. the RFC documents for IGMP version 2
  and 3 says that you must ignore the reports with a source ip address that
  you can't identify as belonging to a network assigned to the interface on
  which the packet was received. and the networking OS in the ToR switch,
  Force10 OS 9 does ignore it.

  I've also figured out a patch has been made for this bug in Linus's Github.
  and there was a mark on Github that reads "v4.16-rc1". (
  
https://github.com/torvalds/linux/commit/a46182b00290839fa3fa159d54fd3237bd8669f0
   )

  I honestly have no idea how Ubuntu LTS team works with regard to this kind
  of patches from the fresh new upstream version of linux kernel. hope you
  guys will easily fix it for people like me who has no experience at
  building and distributing custom built kernels over a few servers.

  Test environment:
  I used two ToR switches and one linux machine for this test.
  I only used 2 ethernet ports on the linux machine.
  There was a recent version of Ubuntu with HWE kernel. I'm not sure if
  no-HWE one would be the same case - the version of linux-generic-hwe-16.04
  was 4.13.0.32.52 -
  To test networking router stuff, I used the quagga from Cumulus Routing on
  the Host 3.3.2 (
  
https://cumulusnetworks.com/products/cumulus-routing-on-the-host/#roh-download-section
   )

  What I did and saw in my case:
  1. set a network interface (A) so it gets an IPv4 address, but also in vain
  issue "ip link set ${if_name} multicast off"
  2. assign an IPv4 address to another network interface (B), but in this
  case with a 31-bit-long subnet mask length.
  3. install quagga from cumulus, launch zebra and pimd, issue "ip pim sm" in
  the interface configuration mode for the interface (B) with a 31-bit-long
  subnet mask length
  4. I checked that the source IP address part of the IGMP membership report
  packets from the linux machine is the address I assigned to the network
  interface (A) with 27-bit-long subnet mask -using dumpcap and tshark-, and
  that the PIM service on the switch ignored the Reports printing debugging
  messages including : "Invalid sender address"

   affects ubuntu

  Regards,
  Gunwoo
  -- 
  You can find my PGP public key here: https://google.com/+DewrKim/about

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

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1749058

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

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

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

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

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

Title:
  incorrect source address in IGMP Membership Report messages

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I found that linux kernel had had a bug in the implementation of IGMP
  membership report packet generation. the RFC documents for IGMP version 2
  and 3 says that you must ignore the reports with a source ip address that
  you can't identify as belonging to a network assigned to the interface on
  which the packet was received. and the networking OS in the ToR switch,
  Force10 OS 9 does ignore it.

  I've also figured out a patch has been made for this bug in Linus's Github.
  and there was a mark on Github that reads "v4.16-rc1". (
  
https://github.com/torvalds/linux/commit/a46182b00290839fa3fa159d54fd3237bd8669f0
   )

  I honestly have no idea how Ubuntu LTS team works with regard to this kind
  of patches from the fresh new upstream version of linux kernel. hope you
  guys will easily fix it for people like me who has no experience at
  building and distributing custom built kernels over a few servers.

  Test environment:
  I used two ToR switches and one linux machine for this test.
  I only used 2 ethernet ports on the linux machine.
  There was a recent version of Ubuntu with HWE kernel. I'm not sure if
  no-HWE one would be the same case - the version of linux-generic-hwe-16.04
  was 4.13.0.32.52 -
  To test networking router stuff, I used the quagga from Cumulus Routing on
  the Host 3.3.2 (
  
https://cumulusnetworks.com/products/cumulus-routing-on-the-host/#roh-download-section
   )

  What I did and saw in my case:
  1. set a network interface (A) so it gets an IPv4 address, but also in vain
  issue "ip link set ${if_name} multicast off"
  2. assign an IPv4 address to another network interface (B), but in this
  case with a 31-bit-long subnet mask length.
  3. install quagga from cumulus, launch zebra and pimd, issue "ip pim sm" in
  the interface configuration mode for the interface (B) with a 31-bit-long
  subnet mask length
  4. I checked that the source IP address part of the IGMP membership report
  packets from the linux machine is the address I assigned to the network
  interface (A) with 27-bit-long subnet mask -using dumpcap and tshark-, and
  that the PIM service on the switch ignored the Reports printing debugging
  messages including : "Invalid sender address"

   affects ubuntu

  Regards,
  Gunwoo
  -- 
  You can find my PGP public key here: https://google.com/+DewrKim/about

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749058/+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 1510570] Re: Bluetooth LE pairing fail

2018-02-12 Thread Daniel van Vugt

Being a HWE problem, and not completely patchable, it sounds like we may
have to consider a major upgrade of bluez to xenial. Assuming we can
avoid ABI/API breaks...

I don't think we want to do it, but if it comes to that then we may have
to.

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

Title:
Bluetooth LE pairing fail

Status in OEM Priority Project:
Confirmed
Status in bluez package in Ubuntu:
Fix Released
Status in bluez source package in Xenial:
Fix Committed

Bug description:
[Impact]

When the Bluetooth adapter is not powered on it is not possible to use
it in normal way. We used to have a hack to force powering on by using
an udev rule but this doe snot work anymore. Luckily the BlueZ has
introduced "AutoEnable" option that makes the stack power on adapters by
itself.

Backporting this to xenial will improve life of the desktop users and
will not require them to hack the solution on their own. The fix itself
uses the well known solution to this problem that is floating around
there for a while.

The upload fixes the bug by enabling the 'AutoEnable' option in the
bluetoothd config file.

[Original Report]

. 15.10 we now have bluez 5 so we can pair BLE devices like the
Microsoft Arc Touch Bluetooth Mouse.

But this pairing doesn't work very well. Mouse is seen but pairing fail.
More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

This is due to udev rule that use "hcitool" to power on device.
Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used
instead of udev rules.

here is a commit with this parameter:
http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138

[Test Case]

On xenial install from ppa:
https://launchpad.net/~bluetooth/+archive/ubuntu/bluez

Now reboot the machine. The BT adapter shall be
powered on.

[Regression Potential]

If things go wrong the adapter will not be powered on after the system
boots up. Therefore while testing please focus on the adapter state,
i.e. powered on or off.

[Other Info]

This fix is included in the development release, see:
http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22

[What to upload]

For xenial as in:

) https://launchpad.net/~bluetooth/+archive/ubuntu/bluez
)
https://launchpadlibrarian.net/347480725/bluez_5.37-0ubuntu5_5.37-0ubuntu5.2~build1.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+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 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state

Please try [1].

The previous one was built on Bionic, it had higher libssl requirement
as a result. I build the new one on Xenial, so it should have the
correct version number.

[1] people.canonical.com/~khfeng/lp1746340-pcireset/

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

Title:
  Samsung SSD 960 EVO 500GB refused to change power state

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  === SRU Justification ===
  [Impact]
  A user reported his NVMe went out to lunch after S3.

  [Fix]
  Disable APST for this particular NVMe + Motherboard setup.

  [Test]
  User confirmed this quirk works for his system.

  [Regression Potential]
  Very Low. This applies to a specific device setup, also user can
  override this quirk by "nvme_core.force_apst=1".

  === Original Bug Report ===
  Originally thought my issue was same as this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  but requested to report as separate bug

  System becomes unusable at seemingly random times but especially after
  resume from suspend due to disk 'disappearing' becoming inaccessible,
  with hundreds of I/O errors logged.

  After viewing the above bug report yesterday as a quick temporary fix I added 
kernel param, updated grub, etc with:
  GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0"

  System appears to have been stable for the last day, but is presumably
  using more power than it should.

  System, drive details below:

  M2 nvme drive: Samsung SSD 960 EVO 500GB

  Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17

  M/B Asus Prime B350m-A
  Ryzen 1600 cpu

  Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST 
device=00:00.0 address=0xfffdf800 flags=0x0a00]
  Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is 
down; will reset: CSTS=0x, PCI_STATUS=0x
  Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 
callbacks suppressed
  Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to 
change power state, currently in D3
  Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe 
failure status: -19
  Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change 
from 500107862016 to 0
  Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, 
dev nvme0n1, sector 0

  nvme list

  /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB
  / 500.11 GB 512 B + 0 B 2B7QCXE7

  sudo nvme id-ctrl /dev/nvme0

  NVME Identify Controller:
  vid : 0x144d
  ssvid : 0x144d
  sn : S3EUNX0J305518L
  mn : Samsung SSD 960 EVO 500GB
  fr : 2B7QCXE7
  rab : 2
  ieee : 002538
  cmic : 0
  mdts : 9
  cntlid : 2
  ver : 10200
  rtd3r : 7a120
  rtd3e : 4c4b40
  oaes : 0
  oacs : 0x7
  acl : 7
  aerl : 3
  frmw : 0x16
  lpa : 0x3
  elpe : 63
  npss : 4
  avscc : 0x1
  apsta : 0x1
  wctemp : 350
  cctemp : 352
  mtfa : 0
  hmpre : 0
  hmmin : 0
  tnvmcap : 500107862016
  unvmcap : 0
  rpmbs : 0
  sqes : 0x66
  cqes : 0x44
  nn : 1
  oncs : 0x1f
  fuses : 0
  fna : 0x5
  vwc : 0x1
  awun : 255
  awupf : 0
  nvscc : 1
  acwu : 0
  sgls : 0
  ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0
    rwt:0 rwl:0 idle_power:- active_power:-
  ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1
    rwt:1 rwl:1 idle_power:- active_power:-
  ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2
    rwt:2 rwl:2 idle_power:- active_power:-
  ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3
    rwt:3 rwl:3 idle_power:- active_power:-
  ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4
    rwt:4 rwl:4 idle_power:- active_power:-
  ---
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  drgrumpy   2192 F pulseaudio
   /dev/snd/pcmC1D0p:   drgrumpy   2192 F...m pulseaudio
   /dev/snd/controlC1:  drgrumpy   2192 F pulseaudio
  DistroRelease: Linux 18.2
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=a6896cdd-6bac-4e7f-9e13-55460859c3ec
  InstallationDate: Installed on 2017-07-06 (15 days ago)
  InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628
  IwConfig:
   lono wireless extensions.

   enp37s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic 
root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro 
nvme_core.default_ps_max_latency_us=0
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  PulseList:
   Er

[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)

Can you try again with [1]?

The one you used is with quirk NVME_QUIRK_NO_DEEPEST_PS, let's see if
that quirk is unnecessary.

[1] people.canonical.com/~khfeng/lp1746340-pcireset/

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lz 1088 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-01-30 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Razer Blade Stealth
  Package: linux (not installed)
  Pr

[Kernel-packages] [Bug 1748489] Re: linux-aws: 4.4.0-1052.61 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-xenial

** Tags added: block-proposed

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

Title:
  linux-aws: 4.4.0-1052.61 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1748990
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1748489/+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 1749058] Re: incorrect source address in IGMP Membership Report messages

I think I add a command "affects ubuntu/linux"

** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  incorrect source address in IGMP Membership Report messages

Status in linux package in Ubuntu:
  New

Bug description:
  I found that linux kernel had had a bug in the implementation of IGMP
  membership report packet generation. the RFC documents for IGMP version 2
  and 3 says that you must ignore the reports with a source ip address that
  you can't identify as belonging to a network assigned to the interface on
  which the packet was received. and the networking OS in the ToR switch,
  Force10 OS 9 does ignore it.

  I've also figured out a patch has been made for this bug in Linus's Github.
  and there was a mark on Github that reads "v4.16-rc1". (
  
https://github.com/torvalds/linux/commit/a46182b00290839fa3fa159d54fd3237bd8669f0
   )

  I honestly have no idea how Ubuntu LTS team works with regard to this kind
  of patches from the fresh new upstream version of linux kernel. hope you
  guys will easily fix it for people like me who has no experience at
  building and distributing custom built kernels over a few servers.

  Test environment:
  I used two ToR switches and one linux machine for this test.
  I only used 2 ethernet ports on the linux machine.
  There was a recent version of Ubuntu with HWE kernel. I'm not sure if
  no-HWE one would be the same case - the version of linux-generic-hwe-16.04
  was 4.13.0.32.52 -
  To test networking router stuff, I used the quagga from Cumulus Routing on
  the Host 3.3.2 (
  
https://cumulusnetworks.com/products/cumulus-routing-on-the-host/#roh-download-section
   )

  What I did and saw in my case:
  1. set a network interface (A) so it gets an IPv4 address, but also in vain
  issue "ip link set ${if_name} multicast off"
  2. assign an IPv4 address to another network interface (B), but in this
  case with a 31-bit-long subnet mask length.
  3. install quagga from cumulus, launch zebra and pimd, issue "ip pim sm" in
  the interface configuration mode for the interface (B) with a 31-bit-long
  subnet mask length
  4. I checked that the source IP address part of the IGMP membership report
  packets from the linux machine is the address I assigned to the network
  interface (A) with 27-bit-long subnet mask -using dumpcap and tshark-, and
  that the PIM service on the switch ignored the Reports printing debugging
  messages including : "Invalid sender address"

   affects ubuntu

  Regards,
  Gunwoo
  -- 
  You can find my PGP public key here: https://google.com/+DewrKim/about

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749058/+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 1749058] [NEW] incorrect source address in IGMP Membership Report messages

You have been subscribed to a public bug:

I found that linux kernel had had a bug in the implementation of IGMP
membership report packet generation. the RFC documents for IGMP version 2
and 3 says that you must ignore the reports with a source ip address that
you can't identify as belonging to a network assigned to the interface on
which the packet was received. and the networking OS in the ToR switch,
Force10 OS 9 does ignore it.

I've also figured out a patch has been made for this bug in Linus's Github.
and there was a mark on Github that reads "v4.16-rc1". (
https://github.com/torvalds/linux/commit/a46182b00290839fa3fa159d54fd3237bd8669f0
 )

I honestly have no idea how Ubuntu LTS team works with regard to this kind
of patches from the fresh new upstream version of linux kernel. hope you
guys will easily fix it for people like me who has no experience at
building and distributing custom built kernels over a few servers.

Test environment:
I used two ToR switches and one linux machine for this test.
I only used 2 ethernet ports on the linux machine.
There was a recent version of Ubuntu with HWE kernel. I'm not sure if
no-HWE one would be the same case - the version of linux-generic-hwe-16.04
was 4.13.0.32.52 -
To test networking router stuff, I used the quagga from Cumulus Routing on
the Host 3.3.2 (
https://cumulusnetworks.com/products/cumulus-routing-on-the-host/#roh-download-section
 )

What I did and saw in my case:
1. set a network interface (A) so it gets an IPv4 address, but also in vain
issue "ip link set ${if_name} multicast off"
2. assign an IPv4 address to another network interface (B), but in this
case with a 31-bit-long subnet mask length.
3. install quagga from cumulus, launch zebra and pimd, issue "ip pim sm" in
the interface configuration mode for the interface (B) with a 31-bit-long
subnet mask length
4. I checked that the source IP address part of the IGMP membership report
packets from the linux machine is the address I assigned to the network
interface (A) with 27-bit-long subnet mask -using dumpcap and tshark-, and
that the PIM service on the switch ignored the Reports printing debugging
messages including : "Invalid sender address"

 affects ubuntu

Regards,
Gunwoo
-- 
You can find my PGP public key here: https://google.com/+DewrKim/about

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


** Tags: bot-comment
-- 
incorrect source address in IGMP Membership Report messages
https://bugs.launchpad.net/bugs/1749058
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
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 1655100] Re: NVME devices and Network devices disappears upon suspend

The patch has "Cc: sta...@vger.kernel.org" hence Xenial's v4.4 based
kernel will automatically pick this patch.

We only need to backport it to Artful's v4.13 based kernel.

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

Title:
  NVME devices and Network devices disappears upon suspend

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Yakkety:
  Won't Fix

Bug description:
  Ubuntu 16.10 on a Alienware 15 R2 when resuming from suspend the NVME
  devices and network devices are gone.

  I can force the devices to re-appear issuing echo 1 >
  /sys/bus/pci/rescan, that was what I did to be able to submit this bug
  report from a live USB stick.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-22-generic 4.8.0-22.24
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CasperVersion: 1.379
  CurrentDesktop: Unity
  Date: Mon Jan  9 17:55:50 2017
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Alienware Alienware 15 R2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper quiet splash ---
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.3.9
  dmi.board.name: 0X70NC
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.3.9:bd09/30/2016:svnAlienware:pnAlienware15R2:pvr1.3.9:rvnAlienware:rn0X70NC:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
  dmi.product.name: Alienware 15 R2
  dmi.product.version: 1.3.9
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655100/+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 1748990] Re: linux: 4.4.0-116.140 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the 4.4.0-116.140 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  phase: Uploaded

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

Title:
  linux: 4.4.0-116.140 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-beta series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-edge series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-116.140 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1748990/+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 1510570] Re: Bluetooth LE pairing fail

2018-02-12 Thread Cyrus Lien

With bluez 5.37-0ubuntu5.2 Designer keyboard still can not connect on
4.13.0-32-generic.

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

Title:
Bluetooth LE pairing fail

Status in OEM Priority Project:
Confirmed
Status in bluez package in Ubuntu:
Fix Released
Status in bluez source package in Xenial:
Fix Committed

Bug description:
[Impact]

The upload fixes the bug by enabling the 'AutoEnable' option in the
bluetoothd config file.

[Original Report]

. 15.10 we now have bluez 5 so we can pair BLE devices like the
Microsoft Arc Touch Bluetooth Mouse.

But this pairing doesn't work very well. Mouse is seen but pairing fail.
More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

This is due to udev rule that use "hcitool" to power on device.
Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used
instead of udev rules.

here is a commit with this parameter:
http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138

[Test Case]

On xenial install from ppa:
https://launchpad.net/~bluetooth/+archive/ubuntu/bluez

Now reboot the machine. The BT adapter shall be
powered on.

[Regression Potential]

If things go wrong the adapter will not be powered on after the system
boots up. Therefore while testing please focus on the adapter state,
i.e. powered on or off.

[Other Info]

This fix is included in the development release, see:
http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22

[What to upload]

For xenial as in:

) https://launchpad.net/~bluetooth/+archive/ubuntu/bluez
)
https://launchpadlibrarian.net/347480725/bluez_5.37-0ubuntu5_5.37-0ubuntu5.2~build1.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

[Kernel-packages] [Bug 1510570] Re: Bluetooth LE pairing fail

2018-02-12 Thread Cyrus Lien

Designer keyboard still can not connect on 4.13.0-32-generic.

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

Title:
Bluetooth LE pairing fail

Status in OEM Priority Project:
Confirmed
Status in bluez package in Ubuntu:
Fix Released
Status in bluez source package in Xenial:
Fix Committed

Bug description:
[Impact]

The upload fixes the bug by enabling the 'AutoEnable' option in the
bluetoothd config file.

[Original Report]

. 15.10 we now have bluez 5 so we can pair BLE devices like the
Microsoft Arc Touch Bluetooth Mouse.

But this pairing doesn't work very well. Mouse is seen but pairing fail.
More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

This is due to udev rule that use "hcitool" to power on device.
Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used
instead of udev rules.

here is a commit with this parameter:
http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138

[Test Case]

On xenial install from ppa:
https://launchpad.net/~bluetooth/+archive/ubuntu/bluez

Now reboot the machine. The BT adapter shall be
powered on.

[Regression Potential]

If things go wrong the adapter will not be powered on after the system
boots up. Therefore while testing please focus on the adapter state,
i.e. powered on or off.

[Other Info]

This fix is included in the development release, see:
http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22

[What to upload]

For xenial as in:

) https://launchpad.net/~bluetooth/+archive/ubuntu/bluez
)
https://launchpadlibrarian.net/347480725/bluez_5.37-0ubuntu5_5.37-0ubuntu5.2~build1.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

[Kernel-packages] [Bug 1742316] Re: DVB Card with SAA7146 chipset not working

No not really.

I'll backport the patch once it's in Linus' tree.

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

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

Title:
  DVB Card with SAA7146 chipset not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 17.10 (from 16.04 with 4.4 kernel) my PCI DVB card
  Terratec Cinergy DVB-1200 with SAA7146 chipset is not working anymore.
  There is a kernel bug message while booting and no /dev/dvb device is
  created. Tried also with newest mainline 4.14 kernel - same error.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-25-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Date: Wed Jan 10 00:42:24 2018
  HibernationDevice: RESUME=UUID=342e30a6-d71f-47c0-b65a-5ba657a80456
  InstallationDate: Installed on 2016-02-13 (696 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release i386 
(20151021)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 psbdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=UUID=97ea5186-d18d-4c06-a8b2-2dd1417477be ro splash quiet acpi=force 
video=LVDS-1:d vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2016-07-07 (551 days ago)
  dmi.bios.date: 04/19/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: AD2700-ITX
  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.60:bd04/19/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAD2700-ITX: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/1742316/+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 1744852] Re: Broken screen at kernel 4.13.0-32 (16.04 HWE)

2018-02-12 Thread la Nube

Mainline Kernel 4.15.3 works WELL.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.3/

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

Title:
  Broken screen at kernel 4.13.0-32 (16.04 HWE)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've upgraded linux kernel from 4.10.0-42.46~16.04.1 to 4.13.0-31.34~16.04.1.
  After rebooting, my linux screen has been broken.

  See Imgur images.

  https://i.imgur.com/9cXTyIG.jpg
  https://i.imgur.com/0skgISl.jpg

  Restroing kernel 4.10, then works well.
  Also, 4.4.0-112.135 works well.

  --

  Distributor ID: Ubuntu
  Description: Ubuntu 16.04.3 LTS
  Release: 16.04
  Codename: xenial
  Linux asus-1000HE 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 
UTC 2017 i686 i686 i686 GNU/Linux

  CPU: Single core Intel Atom N270 (-HT-) cache: 512 KB
     flags: (nx pae sse sse2 sse3 ssse3) bmips: 3192
     clock speeds: max: 1600 MHz 1: 1333 MHz 2: 800 MHz

  Graphics: Card: Intel Mobile 945GSE Express Integrated Graphics Controller
     bus-ID: 00:02.0
     Display Server: N/A drivers: intel (unloaded: fbdev,vesa)
     tty size: 80x24 Advanced Data: N/A out of X

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744852/+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 1738147] Re: Cherry Trail & USB 3.0

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Cherry Trail & USB 3.0

Status in linux package in Ubuntu:
  Expired

Bug description:
  Disk I/O error

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-19-generic 4.13.0-19.22
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-19-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/comprC1D2', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Date: Thu Dec 14 02:56:10 2017
  InstallationDate: Installed on 2017-12-10 (3 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Default string Default string
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed 
root=UUID=980de5c4-1458-48a8-b8ab-f9a69c7b4e69 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  StagingDrivers: r8723bs
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Default string
  dmi.board.name: Cherry Trail CR
  dmi.board.vendor: AMI Corporation
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd07/18/2017:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Default string

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738147/+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 1744852] Re: Broken screen at kernel 4.13.0-32 (16.04 HWE)

2018-02-12 Thread la Nube

Mainline Kernel 4.15.2 works WELL.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.2/

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

Title:
  Broken screen at kernel 4.13.0-32 (16.04 HWE)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've upgraded linux kernel from 4.10.0-42.46~16.04.1 to 4.13.0-31.34~16.04.1.
  After rebooting, my linux screen has been broken.

  See Imgur images.

  https://i.imgur.com/9cXTyIG.jpg
  https://i.imgur.com/0skgISl.jpg

  Restroing kernel 4.10, then works well.
  Also, 4.4.0-112.135 works well.

  --

  Distributor ID: Ubuntu
  Description: Ubuntu 16.04.3 LTS
  Release: 16.04
  Codename: xenial
  Linux asus-1000HE 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 
UTC 2017 i686 i686 i686 GNU/Linux

  CPU: Single core Intel Atom N270 (-HT-) cache: 512 KB
     flags: (nx pae sse sse2 sse3 ssse3) bmips: 3192
     clock speeds: max: 1600 MHz 1: 1333 MHz 2: 800 MHz

  Graphics: Card: Intel Mobile 945GSE Express Integrated Graphics Controller
     bus-ID: 00:02.0
     Display Server: N/A drivers: intel (unloaded: fbdev,vesa)
     tty size: 80x24 Advanced Data: N/A out of X

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744852/+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 1722677] Re: Touch Screen NOT working

*** This bug is a duplicate of bug 1745342 ***
https://bugs.launchpad.net/bugs/1745342

** This bug has been marked a duplicate of bug 1745342
   touchscreen that worked in artful with 4.12 no longer works with 4.13

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

Title:
  Touch Screen NOT working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 Beta 2. Dell Venue 11 pro 7139. 
  Touchscreen does not work after installing OS from live USB. It did not work 
on USB either. There is zero touchscreen functionality.

  Workaroud: Must put computer to sleep, and then wake from sleep for
  touchscreen to work.

  Please Note: In this edition of 17.10, tilt sensors work perfectly
  without having to put the computer to sleep (an old bug). Also note,
  wifi works perfectly after resuming from sleep (another old bug fixed
  :)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-15-generic 4.13.0-15.16
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  troll  1255 F pulseaudio
   /dev/snd/controlC0:  troll  1255 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 18:54:29 2017
  InstallationDate: Installed on 2017-09-30 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic.efi.signed 
root=UUID=cdb5516d-c1f9-4c0b-8869-35a9db498fa1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-15-generic N/A
   linux-backports-modules-4.13.0-15-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0RFDKW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0RFDKW:rvrA01:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722677/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake

Hans,
Based on the test result, the commit is not the culprit.

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

Title:
  Touchpad stops working after reboot on Apollo Lake

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

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1728244/+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 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

Yea, but is its ACPI device alive? Please attach `dmesg` and `udevadm
info -e`.

According to comment #65, the SYNA7500's _STA says it's not alive:

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C3:00/SYNA7500:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C3:00/SYNA7500:00
E: MODALIAS=
E: SUBSYSTEM=acpi

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745342/+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 1711283] Comment bridged from LTC Bugzilla

--- Comment From hasri...@in.ibm.com 2018-02-12 22:09 EDT---
(In reply to comment #14)
> Could you please re-test with a kernel from the Ubuntu archives and report
> back here if you are able to reproduce the failures.

With the mailine kernel 4.16-rc1 on Ubuntu 18.04, the following issues are 
observed.
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/

not ok 1..1 selftests:  copy_unaligned [FAIL]
not ok 1..3 selftests:  paste_unaligned [FAIL]
not ok 1..4 selftests:  paste_last_unaligned [FAIL]
not ok 1..1 selftests:  cp_abort [FAIL]
not ok 1..2 selftests:  subpage_prot [FAIL]
not ok 1..1 selftests:  reg_access_test [FAIL]
not ok 1..2 selftests:  event_attributes_test [FAIL]
not ok 1..3 selftests:  cycles_test [FAIL]
not ok 1..4 selftests:  cycles_with_freeze_test [FAIL]
not ok 1..5 selftests:  pmc56_overflow_test [FAIL]
not ok 1..6 selftests:  ebb_vs_cpu_event_test [FAIL]
not ok 1..7 selftests:  cpu_event_vs_ebb_test [FAIL]
not ok 1..8 selftests:  cpu_event_pinned_vs_ebb_test [FAIL]
not ok 1..9 selftests:  task_event_vs_ebb_test [FAIL]
not ok 1..10 selftests:  task_event_pinned_vs_ebb_test [FAIL]
not ok 1..11 selftests:  multi_ebb_procs_test [FAIL]
not ok 1..12 selftests:  multi_counter_test [FAIL]
not ok 1..13 selftests:  pmae_handling_test [FAIL]
not ok 1..14 selftests:  close_clears_pmcc_test [FAIL]
not ok 1..15 selftests:  instruction_count_test [FAIL]
not ok 1..16 selftests:  fork_cleanup_test [FAIL]
not ok 1..17 selftests:  ebb_on_child_test [FAIL]
not ok 1..18 selftests:  ebb_on_willing_child_test [FAIL]
not ok 1..19 selftests:  back_to_back_ebbs_test [FAIL]
not ok 1..20 selftests:  lost_exception_test [FAIL]
not ok 1..21 selftests:  no_handler_test [FAIL]
not ok 1..22 selftests:  cycles_with_mmcr2_test [FAIL]
not ok 1..10 selftests:  tm-unavailable [FAIL]
not ok 1..11 selftests:  tm-trap [FAIL]

Thanks,
Harish

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

Title:
  few kernel selftest failed on Ubuntu 17.10

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Invalid

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-01 05:11:09 ==
  Problem Description
  
  Few kernel selftest failed on Ubuntu 17.10

  Environment
  --
  Kernel Build:  4.11.0-10-generic
  System Name : ltc-test-ci2
  Model  : 8247-22L
  Platform:  PowerNV ( P8 )

  Uname output
  ---
  # uname -a
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Get kernel source using apt source
  2. Start powerpc specific tests

  The following FAILS are observed.
  selftests:  cycles_test [FAIL]
  selftests:  cycles_with_freeze_test [FAIL]
  selftests:  pmc56_overflow_test [FAIL]
  selftests:  ebb_vs_cpu_event_test [FAIL]
  selftests:  cpu_event_vs_ebb_test [FAIL]
  selftests:  task_event_vs_ebb_test [FAIL]
  selftests:  multi_ebb_procs_test [FAIL]
  selftests:  multi_counter_test [FAIL]
  selftests:  pmae_handling_test [FAIL]
  selftests:  close_clears_pmcc_test [FAIL]
  selftests:  instruction_count_test [FAIL]
  selftests:  ebb_on_willing_child_test [FAIL]
  selftests:  back_to_back_ebbs_test [FAIL]
  selftests:  lost_exception_test [FAIL]
  selftests:  cycles_with_mmcr2_test [FAIL]
  selftests:  tm-vmxcopy [FAIL]

  Full run log is attached.

  == Comment: #5 - Harish Sriram  - 2017-08-08 03:33:36 ==
  With the latest ubuntu mainline kernel 4.13-rc4 from 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc4/, I see following 
additional failures

  selftests:  ptrace-gpr [FAIL]
  selftests:  ptrace-tm-gpr [FAIL]
  selftests:  ptrace-tm-spd-gpr [FAIL]

  # uname -a
  Linux ltc-test-ci2 4.13.0-041300rc4-generic #201708062231 SMP Mon Aug 7 
03:29:19 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Thanks,
  Harish

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1711283/+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 1749040] Re: fails to boot on Cavium ThunderX CRB

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

** Changed in: linux (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  fails to boot on Cavium ThunderX CRB

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+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 1748828] Re: Bluetooth states off in systray while on

2018-02-12 Thread Daniel van Vugt

This sounds like bug 1738838. Please have a look at the video there and
tell us if you agree.

** Package changed: bluez (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

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

Title:
  Bluetooth states off in systray while on

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The bluetooth indicator suggest that bluetooth is disabled (turned
  off) while this is not the case. See screenshot 1. Only after opening
  the bluetooth toggle, you can see the actual correct action: turn off.
  See screenshot 2.

  As far as I can remember, this behaviour has been introduced on 17.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748828/+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 1748489] Re: linux-aws: 4.4.0-1052.61 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1748990
  phase: Uploaded

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

Title:
  linux-aws: 4.4.0-1052.61 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1748990
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1748489/+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 1746806] Re: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

2018-02-12 Thread Sam

@kamalmostafa: Is the latest kernel released? Your assistance is
appreciated

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

Title:
  sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

Status in cloud-images:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  In Progress
Status in linux-aws source package in Xenial:
  In Progress

Bug description:
  After upgrading to the Ubuntu EC2 AMI from 20180126 (specifically
  ami-79873901 in us-west-2) we have seen sssd hard locking c5 and m5
  EC2 instances after starting the service and CPU goes to 100%.

  We do not experience this issue with t2 or c4 instance types and we do
  not see this issue on any instance types using Ubuntu Cloud images
  from 20180109 or before. I have verified that this is kernel related
  as I booted an image that we created using the Ubuntu cloud image from
  20180109 which works fine on a c5. I then did a "apt update && apt
  install --only-upgrade linux-aws && systemctl disable sssd", rebooted
  the server, verified I was on the new kernel and started sssd with
  "systemctl start sssd" and the EC2 instance froze and Cloudwatch CPU
  usage for that instance went to 100%.

  I haven't been able to find much in the syslog, kern.log, journalctl
  logs, etc. The only thing I have been able to find is that when this
  happens I tend to see "^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@" in
  the syslog and sssd log files.  I have attached several log files and
  the output of a "apport-bug /usr/sbin/sssd". Let me know if you need
  anything else to help track this down.

  Thanks,
  Paul

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1746806/+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 1749040] Re: fails to boot on Cavium ThunderX CRB

4.13.0-33.36 from artful boots fine while 4.13.0-33.36~16.04.1 from
xenial does not - so possibly a toolchain-related 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/1749040

Title:
  fails to boot on Cavium ThunderX CRB

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+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 1747492] Re: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable monitor flickering

2018-02-12 Thread naisanza

It would be best in the Ubuntu installer image. Is there a way get an
ISO build with 4.15?

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

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable monitor flickering

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After installing 17.10.1, plugging in the 15m DisplayPort cable, it works, 
however, there is an unusable amount of screen tearing and flickering, and 
pixelated lines across the screen
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  eric   2029 F pulseaudio
   /dev/snd/controlC1:  eric   2029 F pulseaudio
   /dev/snd/pcmC0D0p:   eric   2029 F...m pulseaudio
   /dev/snd/controlC0:  eric   2029 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=efed4438-d8f7-494f-bc1f-c5097c43bfff
  InstallationDate: Installed on 2018-02-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e6bd0705-72b8-4f01-ba2f-15282ceafa55 ro text
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  artful
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: X299 Taichi
  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.60:bd08/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX299Taichi: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/1747492/+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 1749040] Re: fails to boot on Cavium ThunderX CRB

I did test w/ the latest artful upload (35.39), and the problem is not
reproducing. I don't see anything obvious in the git log that explains
it. I'll try rebuilding it in a xenial environment on the off-chance it
is a toolchain 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/1749040

Title:
  fails to boot on Cavium ThunderX CRB

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+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 1746801] List of patches to include

Default Comment by Bridge

** Attachment added: "List of patches to include"
   
https://bugs.launchpad.net/bugs/1746801/+attachment/5053968/+files/IBM_sas_consolidation_patches.csv

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

Title:
  Request to update 18.04 kernel aacraid to upstream 4.16 version

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  We are asking for the aacraid driver to be updated for 18.04 release
  to match the latest patches upstream, that targeting 4.16. The desired
  patches were merged upstream this week and are present in Linus's
  origin/master branch now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1746801/+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 1746801] Re: Request to update 18.04 kernel aacraid to upstream 4.16 version

2018-02-12 Thread raghava aditya renukunta

Hi Manoj, Joseph,
I have attached the list of patches to be included.

Regards,
Raghava Aditya

** Attachment added: "List of patches to include"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746801/+attachment/5053967/+files/IBM_sas_consolidation_patches.csv

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

Title:
  Request to update 18.04 kernel aacraid to upstream 4.16 version

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  We are asking for the aacraid driver to be updated for 18.04 release
  to match the latest patches upstream, that targeting 4.16. The desired
  patches were merged upstream this week and are present in Linus's
  origin/master branch now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1746801/+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 1749040] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1749040

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

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

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

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

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

Title:
  fails to boot on Cavium ThunderX CRB

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+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 1749040] Re: fails to boot on Cavium ThunderX CRB

** Attachment added: "console.log.2"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5053954/+files/console.log.2

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

Title:
  fails to boot on Cavium ThunderX CRB

Status in linux package in Ubuntu:
  New

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+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 1749040] [NEW] fails to boot on Cavium ThunderX CRB

Public bug reported:

While regression testing the current linux-hwe proposed kernel
(4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
ThunderX CRB. I've rebooted twice since upgrading from the current
-updates kernel, and it's failed to boot both times, with different
failure modes.

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

** Attachment added: "console.log"
   
https://bugs.launchpad.net/bugs/1749040/+attachment/5053953/+files/console.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/1749040

Title:
  fails to boot on Cavium ThunderX CRB

Status in linux package in Ubuntu:
  New

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+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 1748743] Re: linux: 4.13.0-35.39 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.13.0-35.39 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase-changed:Tuesday, 13. February 2018 00:31 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the 4.13.0-35.39 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-stable-phase-changed:Tuesday, 13. February 2018 00:31 UTC
- kernel-stable-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 4.13.0-35.39 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  Confirmed

Bug description:
  This bug is for tracking the 4.13.0-35.39 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1748743/+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 1748489] Re: linux-aws: 4.4.0-1052.61 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

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

Title:
  linux-aws: 4.4.0-1052.61 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1748990
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1748489/+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 1748486] Re: linux-aws: 4.4.0-1014.14 -proposed tracker

** Summary changed:

- linux-aws:  -proposed tracker
+ linux-aws: 4.4.0-1014.14 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa 
(kamalmostafa)

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
- kernel-stable-master-bug: 1748745
+ kernel-stable-master-bug: 1748990
  phase: Packaging

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

Title:
  linux-aws: 4.4.0-1014.14 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1748990
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1748486/+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 1743111] Re: crash after update linux-image-4.13.0-26-generic

2018-02-12 Thread john walter

** 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/1743111

Title:
  crash after update linux-image-4.13.0-26-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The lubuntu does not startup correctly screen is a mess but no crash.
  More complaints seen in the ubuntu forem blog

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743111/+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 1743111] Re: crash after update linux-image-4.13.0-26-generic

2018-02-12 Thread john walter

I am running Lubuntu 16.04.3 on a Acer Aspire One AOA150/ZG5.

I had the same problem described by Henk Leusink, after an update to
4.13.0-26 generic.

Now I deleted 4.13.0-26 and my system is working fine with the previous
kernel 4.10.0-42 generic.

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

Title:
  crash after update linux-image-4.13.0-26-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The lubuntu does not startup correctly screen is a mess but no crash.
  More complaints seen in the ubuntu forem blog

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743111/+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 1748489] Re: linux-aws: 4.4.0-1052.61 -proposed tracker

** Summary changed:

- linux-aws:  -proposed tracker
+ linux-aws: 4.4.0-1052.61 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa 
(kamalmostafa)

** Tags removed: kernel-sru-cycle-2018.02.01-2 kernel-sru-derivative-of-1748745
** Tags added: kernel-sru-cycle-2018.02.01-3 kernel-sru-derivative-of-1748990

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
- kernel-stable-master-bug: 1748745
+ kernel-stable-master-bug: 1748990
  phase: Packaging

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

Title:
  linux-aws: 4.4.0-1052.61 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1748990
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1748489/+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 1722677] Re: Touch Screen NOT working

2018-02-12 Thread redx

no sorry the fix dosen't work. 
The attachment is the udevadm before supend,


** Attachment added: "udevadm"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722677/+attachment/5053926/+files/udevadm

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

Title:
  Touch Screen NOT working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 Beta 2. Dell Venue 11 pro 7139. 
  Touchscreen does not work after installing OS from live USB. It did not work 
on USB either. There is zero touchscreen functionality.

  Workaroud: Must put computer to sleep, and then wake from sleep for
  touchscreen to work.

  Please Note: In this edition of 17.10, tilt sensors work perfectly
  without having to put the computer to sleep (an old bug). Also note,
  wifi works perfectly after resuming from sleep (another old bug fixed
  :)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-15-generic 4.13.0-15.16
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  troll  1255 F pulseaudio
   /dev/snd/controlC0:  troll  1255 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 18:54:29 2017
  InstallationDate: Installed on 2017-09-30 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic.efi.signed 
root=UUID=cdb5516d-c1f9-4c0b-8869-35a9db498fa1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-15-generic N/A
   linux-backports-modules-4.13.0-15-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0RFDKW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0RFDKW:rvrA01:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722677/+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 1748489] Re: linux-aws: 4.4.0-1052.61 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/snap-release-to-stable
   Status: New => Invalid

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1748990
  phase: Packaging
+ kernel-stable-phase-changed:Monday, 12. February 2018 23:01 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1748990
- phase: Packaging
- kernel-stable-phase-changed:Monday, 12. February 2018 23:01 UTC
- kernel-stable-phase:Uploaded
+ phase: Uploaded

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

Title:
  linux-aws: 4.4.0-1052.61 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1748990
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1748489/+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 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29

2018-02-12 Thread varacanero

I can also confirm that with the 4.15 mainline kernel
(4.15.0-041500-generic for amd64) resume from hibernate 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/1743094

Title:
  [regression] hibernation (freezes on resume) since 4.13.0-25.29

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After hibernating the system and than resuming it the system reboots
  notifying that it is resuming and than stops/freezes. The system does
  not respond to anything (no tty's other notifying textg are
  available).

  
  After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep 
functions as proposed.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jb 1717 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478
  InstallationDate: Installed on 2017-12-10 (34 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: Acer Aspire S3-391
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic 
root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-26-generic N/A
   linux-backports-modules-4.13.0-26-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Hummingbird2
  dmi.board.vendor: Acer
  dmi.board.version: V2.10
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.10
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S3-391
  dmi.product.version: V2.10
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/+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 1748486] Re: linux-aws: -proposed tracker

** Tags removed: kernel-sru-backport-of-1748745 kernel-sru-cycle-2018.02.01-2
** Tags added: kernel-sru-backport-of-1748990 kernel-sru-cycle-2018.02.01-3

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

Title:
  linux-aws:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1748745
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1748486/+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 1748669] Re: New kernel update cause seriouse video problems.

2018-02-12 Thread Várkuli Miklós Gábor

error makes any data collection impossible

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Várkuli Miklós Gábor (e3c15)

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

Title:
  New kernel update cause seriouse video problems.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Test machine:

  Asus   Eee PC 1000H
  CPU:   Intel Atom N270 1,6 GHz
  Video: Intel GMA950

  no proprietary drivers in use

  Last stable kernel without the error: 4.4.0-112  
  System: current Xubuntu 16.04 LTSpreviously Lubuntu 16.4 LTS 

  After this kernel was updated 4/5 of the desktop disappear or filled
  with random pixels and only a small portion is rendered normally. This
  problem is not occuring when switching back to the older kerrnel
  mentioned above. I tried this with fresh install and with old install
  upgraded. Results were the same. I can't provide data from the faulty
  state since I can't see enough from the desktop to send or even start
  a report. The current bug report is from the properly working, stable
  system .

  Lubuntu, debian and xubuntu is making the same error after kernel
  update. We have 2 stronger notebook an asus and a fujitsu siemens
  business class. They both using proprietary drivers: Nvidia and Intel
  microcode and the error doesn't occured there. I didn't tried to
  switch back to free drivers. They both use lubuntu 16.04 LTS with
  newest kernel and drivers.

  Thanks for your help and the great operating system you all created.
  Sincerely. Miklós Várkuli.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Sat Feb 10 21:03:44 2018
  ProcEnviron:
   LANGUAGE=hu
   TERM=xterm
   PATH=(custom, no user)
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748669/+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 1736390] Re: openvswitch: kernel oops destroying interfaces on i386

I'm still in the process of bisecting this.  Some of the testing that
did not exhibit the bug, does sometimes.  I need to run through the
prior testing I did to confirm whether the kernels were really good or
bad.

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

Title:
  openvswitch: kernel oops destroying interfaces on i386

Status in linux package in Ubuntu:
  In Progress
Status in openvswitch package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  In Progress
Status in openvswitch source package in Artful:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in openvswitch source package in Bionic:
  Invalid

Bug description:
  Reproducable on bionic using the autopkgtest's from openvswitch on
  i386:

  [   41.420568] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   41.421000] IP: igmp_group_dropped+0x21/0x220
  [   41.421246] *pdpt = 1d62c001 *pde =  

  [   41.421659] Oops:  [#1] SMP
  [   41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass 
input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg 
mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse 
virtio_blk virtio_net pata_acpi floppy
  [   41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW   
4.13.0-18-generic #21-Ubuntu
  [   41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [   41.424849] Workqueue: netns cleanup_net
  [   41.425071] task: db8fba80 task.stack: dba1
  [   41.425346] EIP: igmp_group_dropped+0x21/0x220
  [   41.425656] EFLAGS: 00010202 CPU: 0
  [   41.425864] EAX:  EBX: dd726360 ECX: dba11e6c EDX: 0002
  [   41.426335] ESI:  EDI: dd4db500 EBP: dba11dcc ESP: dba11d94
  [   41.426687]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   41.426990] CR0: 80050033 CR2:  CR3: 1e6d6d60 CR4: 06f0
  [   41.427340] Call Trace:
  [   41.427485]  ? __wake_up+0x36/0x40
  [   41.427680]  ip_mc_down+0x27/0x90
  [   41.427869]  inetdev_event+0x398/0x4e0
  [   41.428082]  ? skb_dequeue+0x5b/0x70
  [   41.428286]  ? wireless_nlevent_flush+0x4c/0x90
  [   41.428541]  notifier_call_chain+0x4e/0x70
  [   41.428772]  raw_notifier_call_chain+0x11/0x20
  [   41.429023]  call_netdevice_notifiers_info+0x2a/0x60
  [   41.429301]  dev_close_many+0x9d/0xe0
  [   41.429509]  rollback_registered_many+0xd7/0x380
  [   41.429768]  unregister_netdevice_many.part.102+0x10/0x80
  [   41.430075]  default_device_exit_batch+0x134/0x160
  [   41.430344]  ? do_wait_intr_irq+0x80/0x80
  [   41.430650]  ops_exit_list.isra.8+0x4d/0x60
  [   41.430886]  cleanup_net+0x18e/0x260
  [   41.431090]  process_one_work+0x1a0/0x390
  [   41.431317]  worker_thread+0x37/0x450
  [   41.431525]  kthread+0xf3/0x110
  [   41.431714]  ? process_one_work+0x390/0x390
  [   41.431941]  ? kthread_create_on_node+0x20/0x20
  [   41.432187]  ret_from_fork+0x19/0x24
  [   41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 
56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 
8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00
  [   41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94
  [   41.433750] CR2: 
  [   41.433961] ---[ end trace 595db54cab84070c ]---

  
  system then becomes unresponsive; no further interfaces can be created.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+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 1748990] Re: linux: 4.4.0-116.140 -proposed tracker

** Tags added: kernel-sru-cycle-2018.02.01-3

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

Title:
  linux: 4.4.0-116.140 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-beta series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-edge series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-116.140 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1748990/+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 1748484] Re: linux: 4.4.0-114.137 -proposed tracker

*** This bug is a duplicate of bug 1748990 ***
https://bugs.launchpad.net/bugs/1748990

** This bug is no longer a duplicate of bug 1748745
   linux: 4.4.0-115.139 -proposed tracker
** This bug has been marked a duplicate of bug 1748990
   linux: 4.4.0-116.140 -proposed tracker

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

Title:
  linux: 4.4.0-114.137 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1748486 (linux-aws), bug 1748488 (linux-lts-xenial)
  derivatives: bug 1748489 (linux-aws), bug 1748490 (linux-euclid), bug 1748491 
(linux-gke), bug 1748492 (linux-kvm), bug 1748493 (linux-raspi2), bug 1748494 
(linux-snapdragon)
  kernel-stable-phase-changed:Saturday, 10. February 2018 03:01 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1748484/+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 1746936] Re: linux: 4.4.0-113.136 -proposed tracker

*** This bug is a duplicate of bug 1748990 ***
https://bugs.launchpad.net/bugs/1748990

** This bug is no longer a duplicate of bug 1748745
   linux: 4.4.0-115.139 -proposed tracker
** This bug has been marked a duplicate of bug 1748990
   linux: 4.4.0-116.140 -proposed tracker

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

Title:
  linux: 4.4.0-113.136 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1746937,1746938
  derivatives: 1746939,1746941,1746942,1746944,1746945,1746946
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1746936/+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 1748745] Re: linux: 4.4.0-115.139 -proposed tracker

*** This bug is a duplicate of bug 1748990 ***
https://bugs.launchpad.net/bugs/1748990

** This bug has been marked a duplicate of bug 1748990
   linux: 4.4.0-116.140 -proposed tracker

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

Title:
  linux: 4.4.0-115.139 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-115.138 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1748745/+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 1735713] Re: Ubuntu16.04.03: Kernel Oops on targetcli

2018-02-12 Thread Manoj Iyer

Does this bug still reproduce with latest linux-hwe? Please post the
system logs if you are able to repro this 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/1735713

Title:
  Ubuntu16.04.03: Kernel Oops on targetcli

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - RAHUL CHANDRAKAR  - 2017-12-01 03:26:31 
==
  ---Problem Description---
  Error while running targetcli command on Ubuntu 16.04
   
  ---uname output---
  Linux alpvm2nova 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:23:01 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8408-44E 
   
  ---System Hang---
   gpfs is stuck because of this
   
  ---Debugger---
  A debugger is not configured
   
  Contact Information = rahch...@in.ibm.com 
   
  Stack trace output:
   [Fri Dec  1 03:05:12 2017] Unable to handle kernel paging request for data 
at address 0x010d0688
  [Fri Dec  1 03:05:12 2017] Faulting instruction address: 0xd7570a30
  [Fri Dec  1 03:05:12 2017] Oops: Kernel access of bad area, sig: 11 [#2]
  [Fri Dec  1 03:05:12 2017] SMP NR_CPUS=2048 NUMA pSeries
  [Fri Dec  1 03:05:12 2017] Modules linked in: hvcs(OE) hvcserver rpadlpar_io 
rpaphp xt_tcpudp xt_nat target_core_pscsi(OE) target_core_file(OE) 
target_core_iblock(OE) target_core_user(OE) uio iscsi_target_mod(OE) mmfs26(OE) 
mmfslinux(OE) tracedev(OE) dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag 
af_packet_diag netlink_diag openvswitch binfmt_misc pseries_rng ibmvmc(OE) 
vmx_crypto rtc_generic xt_conntrack nf_nat_ftp nf_conntrack_ftp 
nf_conntrack_netlink nfnetlink nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_conntrack_ipv6 nf_defrag_ipv6 nbd br_netfilter bridge ib_iser rdma_cm iw_cm 
ib_cm ib_sa ib_mad ib_core ib_addr vhost_net vhost macvtap macvlan iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi ip_vs libcrc32c iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_mangle iptable_filter
  [Fri Dec  1 03:05:12 2017]  ipt_REJECT nf_reject_ipv4 ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_nat nf_conntrack ip_tables ip6table_filter ip6_tables 
ebtables x_tables dm_snapshot dm_bufio 8021q garp mrp stp llc autofs4 
dm_round_robin ses enclosure scsi_transport_sas be2net ibmvscsis(OE) 
target_core_mod(OE) configfs(OE) ibmveth(OE) lpfc vxlan ip6_udp_tunnel 
udp_tunnel scsi_transport_fc ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua 
dm_multipath
  [Fri Dec  1 03:05:12 2017] CPU: 13 PID: 178523 Comm: targetcli Tainted: G 
 D W  OE   4.4.0-98-generic #121-Ubuntu
  [Fri Dec  1 03:05:12 2017] task: c007d399cf60 ti: c007e4a84000 
task.ti: c007e4a84000
  [Fri Dec  1 03:05:12 2017] NIP: d7570a30 LR: d75709c4 CTR: 
c016e220
  [Fri Dec  1 03:05:12 2017] REGS: c007e4a87820 TRAP: 0300   Tainted: G 
 D W  OE(4.4.0-98-generic)
  [Fri Dec  1 03:05:12 2017] MSR: 80009033   CR: 
4248  XER: 
  [Fri Dec  1 03:05:12 2017] CFAR: c0008468 DAR: 010d0688 
DSISR: 4000 SOFTE: 1 
 GPR00: d75709c4 c007e4a87aa0 
d757fdf8 0001 
 GPR04: 0240 c007e8739b10 
0001  
 GPR08: 010d0680 d7f61d50 
d757fdf8 d75765f0 
 GPR12: c016e220 cfb47b80 
3fffc86beb50  
 GPR16:  103b7d00 
  
 GPR20: c007d5379aa0 c004d39b5280 
 0024 
 GPR24: c007e8739b00 c004d39b5280 
d7570910 c00516f61d00 
 GPR28: c00518b7e488 c007a6367810 
c007e8739b00 d7f6db50 
  [Fri Dec  1 03:05:12 2017] NIP [d7570a30] 
configfs_open_file+0x120/0x260 [configfs]
  [Fri Dec  1 03:05:12 2017] LR [d75709c4] 
configfs_open_file+0xb4/0x260 [configfs]
  [Fri Dec  1 03:05:12 2017] Call Trace:
  [Fri Dec  1 03:05:12 2017] [c007e4a87aa0] [d75709c4] 
configfs_open_file+0xb4/0x260 [configfs] (unreliable)
  [Fri Dec  1 03:05:12 2017] [c007e4a87af0] [c02e2d40] 
do_dentry_open+0x2c0/0x460
  [Fri Dec  1 03:05:12 2017] [c007e4a87b50] [c02fb388] 
do_last+0x178/0xff0
  [Fri Dec  1 03:05:12 2017] [c007e4a87c10] [c02fc41c] 
path_openat+0xcc/0x3c0
  [Fri Dec  1 03:05:12 2017] [c007e4a87c90] [c02fe33c] 
do_filp_open+0xfc/0x170
  [Fri Dec  1 03:05:12 2017] [c007e4a87db0] [c02e4b30] 
do_sys_open+0x1c0/0x3b0
  [Fri Dec  1 03:05:12 2017] [c007e4a87e30] [c0009204] 
system_call+0x38/0xb4
  [Fri Dec  1 03:05:12 2017] Instruction dump:
  [Fri Dec  1 03:05:12 2017] 419e00e0

[Kernel-packages] [Bug 1749015] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1749015

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

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

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

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

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

Title:
  4.16 - VBOXGUEST not built

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Reporting by recommendation by apw on #ubuntu-kernel

  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/ refers to
  0006-configs-based-on-Ubuntu-4.15.0-9.10.patch which, at line 1771 has

  +# CONFIG_VBOXGUEST is not set

  I am not in any position to demand a rebuild ahead of next upstream
  RC, but I *was* looking forward to the support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749015/+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 1746340] Re: Samsung SSD corruption (fsck needed)

2018-02-12 Thread Lucas Zanella

I've been running for days without any problem (it'd happen before like
30 minutes after installation). So can you release the source? Will it
be on mainline?

Also, how to use this kernel with the live image? Because it's painful
to install ubuntu with this problems, I get I/O error in 90% of my
tries. I have to try for hours until it installs good.

Thank you so much!

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lz 1088 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDat

[Kernel-packages] [Bug 1749015] [NEW] 4.16 - VBOXGUEST not built

2018-02-12 Thread Fjodor

Public bug reported:

Reporting by recommendation by apw on #ubuntu-kernel

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/ refers to 0006
-configs-based-on-Ubuntu-4.15.0-9.10.patch which, at line 1771 has

+# CONFIG_VBOXGUEST is not set

I am not in any position to demand a rebuild ahead of next upstream RC,
but I *was* looking forward to the support.

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

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

Title:
  4.16 - VBOXGUEST not built

Status in linux package in Ubuntu:
  New

Bug description:
  Reporting by recommendation by apw on #ubuntu-kernel

  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/ refers to
  0006-configs-based-on-Ubuntu-4.15.0-9.10.patch which, at line 1771 has

  +# CONFIG_VBOXGUEST is not set

  I am not in any position to demand a rebuild ahead of next upstream
  RC, but I *was* looking forward to the support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749015/+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 1748990] Re: linux: 4.4.0-116.140 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

** Description changed:

  This bug is for tracking the 4.4.0-116.140 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
- kernel-stable-phase-changed:Monday, 12. February 2018 20:42 UTC
- kernel-stable-phase:Packaging
- 
  -- swm properties --
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Monday, 12. February 2018 21:33 UTC

** Description changed:

  This bug is for tracking the 4.4.0-116.140 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Monday, 12. February 2018 21:33 UTC
+ phase: Uploaded

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

Title:
  linux: 4.4.0-116.140 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-beta series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-edge series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-116.140 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1748990/+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 1744791] Re: [Ubuntu18.04] linux-image-4.13.0-25-generic-dbgsym is not available in repo which is required for crash analysis of vmcore

Specifically, the 4.13.0-25 dbgsym package is available from here:
https://launchpad.net/~canonical-kernel-security-team/+archive/ubuntu/ppa/+build/14223090

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

Title:
  [Ubuntu18.04] linux-image-4.13.0-25-generic-dbgsym is not available in
  repo which is required for crash analysis of vmcore

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  In Progress

Bug description:
  ---Problem Description---
  No debug kernel deb packages available for 4.13.0-25-generic kernel [Ubuntu 
18.04 ]
  Unable to analyze vmcore generated via crash. 

  ---uname output---
  Linux spoon2 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:15:55 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8335-GTC 
   
  ---Steps to Reproduce---
  Install 18.04 ppc64el
  upgrade kernel to 4.13.0-25-generic or 4.13.0-17-generic
  try configuring debug repo
  https://wiki.ubuntu.com/Kernel/CrashdumpRecipe
  http://ddebs.ubuntu.com/pool/main/l/linux/
  sudo tee /etc/apt/sources.list.d/ddebs.list << EOF
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)  main restricted 
universe multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-security main restricted 
universe multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-updates  main restricted 
universe multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-proposed main restricted 
universe multiverse
  EOF

  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys ECDCAD72428D7C01
  sudo apt-get update
  sudo apt-get install linux-image-$(uname -r)-dbgsym

  Warning /!\ Be aware that those packages are huge! (~600 MB)

  When installed, the debug kernel can be found under
  /usr/lib/debug/boot/ and crash is started by:

  crash  

  Crash command to analyze vmcore will not work as kernel debuginfo deb package 
is not found in repo . 
  root@spoon2:~# sudo apt-get install linux-image-$(uname -r)-dbgsym
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package linux-image-4.13.0-25-generic-dbgsym
  E: Couldn't find any package by glob 'linux-image-4.13.0-25-generic-dbgsym'
  E: Couldn't find any package by regex 'linux-image-4.13.0-25-generic-dbgsym'
  root@spoon2:~# 
   
  I was also not able to find this debug symbol for 18.04 kernel. I understand 
that the current 18.04 kernel is old and was removed from the archive. Is it 
correct?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1744791/+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 1748903] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1748903

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

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

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

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

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

Title:
  linux 4.13.0-32 version freezes screen before end of boot for X60
  lenovo laptop

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 16.04.3 on x60 lenovo laptop

  previous version of linux 4.10.0-42 works without problems.
  as well older versions linux 4.10.0-38 works without problems.
  even the 4.4.0-96 works without problems.

  at linux 4.13.0-32 the display freezes with 2 top lines fixed.
  however the login greeter still works, you can even login. but you 
  cannot see anything you typed. alt-ctrl-f1 will work. and you can
  see the display working again, however the top 2 lines remain fixed.
  you can do ls and clear, etc. however no gui display. 
  i only installed the linux-*4.13.0-32 packages and it freezes the
  display when you reboot. 7 packages in all. 

  hope you guys fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.23
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Feb 12 22:05:17 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748903/+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 1748669] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1748669

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

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

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

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

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

Title:
  New kernel update cause seriouse video problems.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Test machine:

  Asus   Eee PC 1000H
  CPU:   Intel Atom N270 1,6 GHz
  Video: Intel GMA950

  no proprietary drivers in use

  Last stable kernel without the error: 4.4.0-112  
  System: current Xubuntu 16.04 LTSpreviously Lubuntu 16.4 LTS 

  After this kernel was updated 4/5 of the desktop disappear or filled
  with random pixels and only a small portion is rendered normally. This
  problem is not occuring when switching back to the older kerrnel
  mentioned above. I tried this with fresh install and with old install
  upgraded. Results were the same. I can't provide data from the faulty
  state since I can't see enough from the desktop to send or even start
  a report. The current bug report is from the properly working, stable
  system .

  Lubuntu, debian and xubuntu is making the same error after kernel
  update. We have 2 stronger notebook an asus and a fujitsu siemens
  business class. They both using proprietary drivers: Nvidia and Intel
  microcode and the error doesn't occured there. I didn't tried to
  switch back to free drivers. They both use lubuntu 16.04 LTS with
  newest kernel and drivers.

  Thanks for your help and the great operating system you all created.
  Sincerely. Miklós Várkuli.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Sat Feb 10 21:03:44 2018
  ProcEnviron:
   LANGUAGE=hu
   TERM=xterm
   PATH=(custom, no user)
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748669/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake

2018-02-12 Thread Vi+

Touchpad is working and both 2 buttons are clickable after applying
v4.16-rc1 (4.16.0-041600rc1-generic and 4.16.0-041600rc1-lowlatency),
and only after returning back from "suspend" mode (before v4.16-rc1 both
2 buttons were not clickable even touchpad was working after "suspend")
on my YEPO 737A laptop.

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

Title:
  Touchpad stops working after reboot on Apollo Lake

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

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1728244/+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 1748988] Status changed to Confirmed

This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => 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/1748988

Title:
  Random total system freezes (resolved)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Intel 7260 WiFi card in my desktop (lspci output: 09:00.0
  Network controller: Intel Corporation Wireless 7260 (rev bb)), running
  18.04. All the way since 17.04 I have experienced random freezes,
  where the entire system would be unresponsive, I was unable to
  Ctrl+Alt+F1 to a different console, and I couldn't connect to it via
  ssh. After upgrading to 17.10 (and a fresh install of 17.10), and
  subsequently upgrading to 18.04, the issue intensified, appearing at
  least hourly, often quicker than that, and only a hard reset would let
  me access my system again. The issue is also present in Linux Mint
  18.3. Freezes could happen at any time, regardless of usage (or just
  idling).

  After getting a tip that this might be caused by the WiFi card, I
  looked at the provided firmware from Intel's site, and compared the
  files to the files present in /lib/firmware/. The file provided by
  Intel for my specific card is iwlwifi-7260-14.ucode, but the files
  present in the folder were the numbers 7, 8, 9, 10, 12, 13, 16, and
  17. Downloading the firmware from Intel, and adding the -14 file to
  the folder solved the issue of the screen freezing, and the issue has
  not appeared for the ten hours I've been running since applying the
  fix.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sten   2687 F pulseaudio
   /dev/snd/controlC1:  sten   2687 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Feb 12 21:18:57 2018
  HibernationDevice: RESUME=UUID=96fd0755-bbbc-43ce-9174-b4de65ea2e26
  InstallationDate: Installed on 2017-10-27 (107 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=b3449b90-a2aa-4c46-8837-574f25841071 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-02-05 (7 days ago)
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3803
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B350-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3803:bd01/22/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748988/+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 1744791] Re: [Ubuntu18.04] linux-image-4.13.0-25-generic-dbgsym is not available in repo which is required for crash analysis of vmcore

When trying to debug a bug, it's probably best to use the latest Ubuntu
kernel version, in case it's already fixed.

Are you specifically looking for older versions of kernels and their
dbgsym package?


All prior kernel versions can be found here:
https://launchpad.net/ubuntu/artful/+source/linux

>From that page, select the version.  On the next page, select ppc64el
under the "Builds" section.  The linux-image-VERSION-generic-dbgsym
kernel can be downloaded from that last page.

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

** Changed in: linux (Ubuntu)
   Importance: Undecided => Critical

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

** Changed in: linux (Ubuntu)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph 
Salisbury (jsalisbury)

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

Title:
  [Ubuntu18.04] linux-image-4.13.0-25-generic-dbgsym is not available in
  repo which is required for crash analysis of vmcore

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  In Progress

Bug description:
  ---Problem Description---
  No debug kernel deb packages available for 4.13.0-25-generic kernel [Ubuntu 
18.04 ]
  Unable to analyze vmcore generated via crash. 

  ---uname output---
  Linux spoon2 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:15:55 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8335-GTC 
   
  ---Steps to Reproduce---
  Install 18.04 ppc64el
  upgrade kernel to 4.13.0-25-generic or 4.13.0-17-generic
  try configuring debug repo
  https://wiki.ubuntu.com/Kernel/CrashdumpRecipe
  http://ddebs.ubuntu.com/pool/main/l/linux/
  sudo tee /etc/apt/sources.list.d/ddebs.list << EOF
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)  main restricted 
universe multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-security main restricted 
universe multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-updates  main restricted 
universe multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-proposed main restricted 
universe multiverse
  EOF

  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys ECDCAD72428D7C01
  sudo apt-get update
  sudo apt-get install linux-image-$(uname -r)-dbgsym

  Warning /!\ Be aware that those packages are huge! (~600 MB)

  When installed, the debug kernel can be found under
  /usr/lib/debug/boot/ and crash is started by:

  crash  

  Crash command to analyze vmcore will not work as kernel debuginfo deb package 
is not found in repo . 
  root@spoon2:~# sudo apt-get install linux-image-$(uname -r)-dbgsym
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package linux-image-4.13.0-25-generic-dbgsym
  E: Couldn't find any package by glob 'linux-image-4.13.0-25-generic-dbgsym'
  E: Couldn't find any package by regex 'linux-image-4.13.0-25-generic-dbgsym'
  root@spoon2:~# 
   
  I was also not able to find this debug symbol for 18.04 kernel. I understand 
that the current 18.04 kernel is old and was removed from the archive. Is it 
correct?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1744791/+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 1748990] Re: linux: 4.4.0-116.140 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => 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/1748990

Title:
  linux: 4.4.0-116.140 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-beta series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-edge series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-116.140 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-phase-changed:Monday, 12. February 2018 20:42 UTC
  kernel-stable-phase:Packaging

  -- swm properties --
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1748990/+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 1748669] Re: New kernel update cause seriouse video problems.

2018-02-12 Thread Brian Murray

** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

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

Title:
  New kernel update cause seriouse video problems.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Test machine:

  Asus   Eee PC 1000H
  CPU:   Intel Atom N270 1,6 GHz
  Video: Intel GMA950

  no proprietary drivers in use

  Last stable kernel without the error: 4.4.0-112  
  System: current Xubuntu 16.04 LTSpreviously Lubuntu 16.4 LTS 

  After this kernel was updated 4/5 of the desktop disappear or filled
  with random pixels and only a small portion is rendered normally. This
  problem is not occuring when switching back to the older kerrnel
  mentioned above. I tried this with fresh install and with old install
  upgraded. Results were the same. I can't provide data from the faulty
  state since I can't see enough from the desktop to send or even start
  a report. The current bug report is from the properly working, stable
  system .

  Lubuntu, debian and xubuntu is making the same error after kernel
  update. We have 2 stronger notebook an asus and a fujitsu siemens
  business class. They both using proprietary drivers: Nvidia and Intel
  microcode and the error doesn't occured there. I didn't tried to
  switch back to free drivers. They both use lubuntu 16.04 LTS with
  newest kernel and drivers.

  Thanks for your help and the great operating system you all created.
  Sincerely. Miklós Várkuli.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Sat Feb 10 21:03:44 2018
  ProcEnviron:
   LANGUAGE=hu
   TERM=xterm
   PATH=(custom, no user)
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748669/+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 1748903] Re: linux 4.13.0-32 version freezes screen before end of boot for X60 lenovo laptop

2018-02-12 Thread Brian Murray

** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

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

Title:
  linux 4.13.0-32 version freezes screen before end of boot for X60
  lenovo laptop

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 16.04.3 on x60 lenovo laptop

  previous version of linux 4.10.0-42 works without problems.
  as well older versions linux 4.10.0-38 works without problems.
  even the 4.4.0-96 works without problems.

  at linux 4.13.0-32 the display freezes with 2 top lines fixed.
  however the login greeter still works, you can even login. but you 
  cannot see anything you typed. alt-ctrl-f1 will work. and you can
  see the display working again, however the top 2 lines remain fixed.
  you can do ls and clear, etc. however no gui display. 
  i only installed the linux-*4.13.0-32 packages and it freezes the
  display when you reboot. 7 packages in all. 

  hope you guys fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.23
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Feb 12 22:05:17 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748903/+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 1724317] Re: Shutdown hangs / no standby - possible Wifi-bug in the kernel

2018-02-12 Thread Massimo Bacilieri

SOLVED.
Starting from your suggestion, having I a rtl8723be based wifi card, I made a 
simple test:

$ sudo su
# service network-manager stop
# modprobe -r rtl8723be
# modprobe -r rtl8723_common rtl_pci
# modprobe -r rtlwifi
# killall -9 wpa_supplicant

then shutdown: the system halted perfectly. I retryed several time, and
always worked.

So, simply, I made a script in /usr/local/sbin/wireless-stop.sh:

#!/bin/bash
service network-manager stop
modprobe -r rtl8723be
modprobe -r rtl8723_common rtl_pci
modprobe -r rtlwifi
killall -9 wpa_supplicant

then an entry in /etc/init.d/wireless:

#!/bin/sh
### BEGIN INIT INFO
# Provides:  wireless
# Required-Start:
# Required-Stop:
# Default-Start:
# Default-Stop:  0 6
# Short-Description: unload wifi modules
### END INIT INFO
PATH=/sbin:/bin:/usr/sbin:/usr/bin
case "$1" in
start)
# do nothing at start
;;
stop)
log_daemon_msg "Removing wifi modules from kernel"
/usr/local/sbin/wireless-stop.sh
;;
restart|force-reload)
# do nothing at restart and reload
;;
status)
# no mean to ask for a status.
;;
*)
echo "Usage: /etc/init.d/wireless stop"
exit 1
;;
esac

then, just symlink in /etc/rc0.d (shutdown) and /etc/rc6.d (restart):

# cd /etc/rc0.d && ln -s /etc/init.d/wireless K00wireless
# cd /etc/rc6.d && ln -s /etc/init.d/wireless K00wireless

et voilà. Shutdown and restart now 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/1724317

Title:
  Shutdown hangs / no standby - possible Wifi-bug in the kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Shutdown-process hangs. After about two minutes the following
  message is displayed:

  Oct 17 18:47:06 Kahlan kernel: [  363.170588] INFO: task kworker/u8:2:186 
blocked for more than 120 seconds.
  Oct 17 18:47:06 Kahlan kernel: [  363.170592]   Tainted: P   OE   
4.13.0-12-generic #13-Ubuntu
  Oct 17 18:47:06 Kahlan kernel: [  363.170593] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.

  Two Minutes later this message is displayed:
  Oct 17 18:49:07 Kahlan kernel: [  484.008650] INFO: task kworker/u8:2:186 
blocked for more than 120 seconds.
  Oct 17 18:49:07 Kahlan kernel: [  484.008659]   Tainted: P   OE   
4.13.0-12-generic #13-Ubuntu
  Oct 17 18:49:07 Kahlan kernel: [  484.008662] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.

  This message repeates itself. If I am lucky, my laptop shuts down
  after some time.

  Also standby does not work. I think my wifi-adapter causes this
  problem.

  With Ubuntu 17.04 or Suse 42.3 I cannot reproduce this problem. I
  found a bug report in the Arch Bug System
  (https://bugs.archlinux.org/task/55872

  In my laptop I have also a Qualcomm Atheros Adapter. Perhaps the
  linuxkernel has a bug?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Tue Oct 17 19:08:32 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: kubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-12-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-384, 384.90, 4.13.0-12-generic, x86_64: installed
   nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 5500 [1025:0962]
  InstallationDate: Installed on 2017-10-07 (10 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Acer Aspire VN7-571G
  ProcEnviron:
   LANGUAGE=de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=d5a4b134-b39a-4764-99bd-208c9e504fa8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-571G
  dmi.board.vendor: Acer
  dmi.board.version: V1.14
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.14
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.14:bd01/08/2015:svnAcer:pnAspireVN7-571G:pvrV1.14:rvnAcer:rnAspireVN7-571G:rvrV1.14:cvnAcer:ct10:cvrV1.14:
  d

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

2018-02-12 Thread John Lenton

With

Linux flimsy 4.15.0-9-generic #10~lp1745342+2 SMP Tue Feb 13 01:54:54
CST 2018 x86_64 x86_64 x86_64 GNU/Linux


the touchscreen didn't work.

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745342/+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 1748985] Re: linux: 4.4.0-116.140 -proposed tracker

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

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

Title:
  linux: 4.4.0-116.140 -proposed tracker

Status in linux package in Ubuntu:
  Invalid

Bug description:
  This bug is for tracking the 4.4.0-116.140 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748985/+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 1748988] [NEW] Random total system freezes (resolved)

2018-02-12 Thread Sten Jørgen Pettersen

Public bug reported:

I have an Intel 7260 WiFi card in my desktop (lspci output: 09:00.0
Network controller: Intel Corporation Wireless 7260 (rev bb)), running
18.04. All the way since 17.04 I have experienced random freezes, where
the entire system would be unresponsive, I was unable to Ctrl+Alt+F1 to
a different console, and I couldn't connect to it via ssh. After
upgrading to 17.10 (and a fresh install of 17.10), and subsequently
upgrading to 18.04, the issue intensified, appearing at least hourly,
often quicker than that, and only a hard reset would let me access my
system again. The issue is also present in Linux Mint 18.3. Freezes
could happen at any time, regardless of usage (or just idling).

After getting a tip that this might be caused by the WiFi card, I looked
at the provided firmware from Intel's site, and compared the files to
the files present in /lib/firmware/. The file provided by Intel for my
specific card is iwlwifi-7260-14.ucode, but the files present in the
folder were the numbers 7, 8, 9, 10, 12, 13, 16, and 17. Downloading the
firmware from Intel, and adding the -14 file to the folder solved the
issue of the screen freezing, and the issue has not appeared for the ten
hours I've been running since applying the fix.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.13.0-32-generic 4.13.0-32.35
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.8-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  sten   2687 F pulseaudio
 /dev/snd/controlC1:  sten   2687 F pulseaudio
CurrentDesktop: KDE
Date: Mon Feb 12 21:18:57 2018
HibernationDevice: RESUME=UUID=96fd0755-bbbc-43ce-9174-b4de65ea2e26
InstallationDate: Installed on 2017-10-27 (107 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: System manufacturer System Product Name
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=b3449b90-a2aa-4c46-8837-574f25841071 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-32-generic N/A
 linux-backports-modules-4.13.0-32-generic  N/A
 linux-firmware 1.170
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-02-05 (7 days ago)
dmi.bios.date: 01/22/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3803
dmi.board.asset.tag: Default string
dmi.board.name: PRIME B350-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3803:bd01/22/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug bionic third-party-packages

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

Title:
  Random total system freezes (resolved)

Status in linux package in Ubuntu:
  New

Bug description:
  I have an Intel 7260 WiFi card in my desktop (lspci output: 09:00.0
  Network controller: Intel Corporation Wireless 7260 (rev bb)), running
  18.04. All the way since 17.04 I have experienced random freezes,
  where the entire system would be unresponsive, I was unable to
  Ctrl+Alt+F1 to a different console, and I couldn't connect to it via
  ssh. After upgrading to 17.10 (and a fresh install of 17.10), and
  subsequently upgrading to 18.04, the issue intensified, appearing at
  least hourly, often quicker than that, and only a hard reset would let
  me access my system again. The issue is also present in Linux Mint
  18.3. Freezes could happen at any time, regardless of usage (or just
  idling).

  After getting a tip that this might be caused by the WiFi card, I
  looked at the provided firmware from Intel's site, and compared the
  files to the files present in /lib/firmware/. The file provided by
  Intel for my specific card is iwlwifi-7260-14.ucode, but the files
  present in the folder were the numbers 7, 8, 9, 10, 12, 13, 16, and
  17. Downloading the firmware from Intel, and adding the -14 file to
  the folder solved the issue of the screen freezing, and the issue has
  not appeared for the ten hours I've been running since applying the
  fix.

  ProblemType: Bug
  DistroRel

[Kernel-packages] [Bug 1748990] [NEW] linux: 4.4.0-116.140 -proposed tracker

Public bug reported:

This bug is for tracking the 4.4.0-116.140 upload package. This bug will
contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-stable-phase-changed:Monday, 12. February 2018 20:42 UTC
kernel-stable-phase:Packaging

-- swm properties --
phase: Packaging

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/snap-certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: Invalid

** Affects: kernel-sru-workflow/snap-release-to-beta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Invalid

** Affects: kernel-sru-workflow/snap-release-to-candidate
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Invalid

** Affects: kernel-sru-workflow/snap-release-to-edge
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Invalid

** Affects: kernel-sru-workflow/snap-release-to-stable
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Invalid

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Xenial)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live xenial

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Tags added: xenial

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-beta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-candidate
   Import

[Kernel-packages] [Bug 1748903] [NEW] linux 4.13.0-32 version freezes screen before end of boot for X60 lenovo laptop

You have been subscribed to a public bug:

ubuntu 16.04.3 on x60 lenovo laptop

previous version of linux 4.10.0-42 works without problems.
as well older versions linux 4.10.0-38 works without problems.
even the 4.4.0-96 works without problems.

at linux 4.13.0-32 the display freezes with 2 top lines fixed.
however the login greeter still works, you can even login. but you 
cannot see anything you typed. alt-ctrl-f1 will work. and you can
see the display working again, however the top 2 lines remain fixed.
you can do ls and clear, etc. however no gui display. 
i only installed the linux-*4.13.0-32 packages and it freezes the
display when you reboot. 7 packages in all. 

hope you guys fix it.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.23
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic i686
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Mon Feb 12 22:05:17 2018
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug dist-upgrade i386 xenial
-- 
linux 4.13.0-32 version freezes screen before end of boot for X60 lenovo laptop
https://bugs.launchpad.net/bugs/1748903
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
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 1748669] [NEW] New kernel update cause seriouse video problems.

You have been subscribed to a public bug:

Test machine:

Asus   Eee PC 1000H
CPU:   Intel Atom N270 1,6 GHz
Video: Intel GMA950

no proprietary drivers in use

Last stable kernel without the error: 4.4.0-112  
System: current Xubuntu 16.04 LTSpreviously Lubuntu 16.4 LTS 

After this kernel was updated 4/5 of the desktop disappear or filled
with random pixels and only a small portion is rendered normally. This
problem is not occuring when switching back to the older kerrnel
mentioned above. I tried this with fresh install and with old install
upgraded. Results were the same. I can't provide data from the faulty
state since I can't see enough from the desktop to send or even start a
report. The current bug report is from the properly working, stable
system .

Lubuntu, debian and xubuntu is making the same error after kernel
update. We have 2 stronger notebook an asus and a fujitsu siemens
business class. They both using proprietary drivers: Nvidia and Intel
microcode and the error doesn't occured there. I didn't tried to switch
back to free drivers. They both use lubuntu 16.04 LTS with newest kernel
and drivers.

Thanks for your help and the great operating system you all created.
Sincerely. Miklós Várkuli.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core (not installed)
ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
Uname: Linux 4.4.0-112-generic i686
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
Date: Sat Feb 10 21:03:44 2018
ProcEnviron:
 LANGUAGE=hu
 TERM=xterm
 PATH=(custom, no user)
 LANG=hu_HU.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 xenial
-- 
New kernel update cause seriouse video problems.
https://bugs.launchpad.net/bugs/1748669
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
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 1745927] Re: Driver not found in Ubuntu kernel does not detect interface

** Tags removed: kernel-da-key
** Tags added: kernel-key

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

Title:
  Driver not found in Ubuntu kernel does not detect interface

Status in The Ubuntu-power-systems project:
  Triaged
Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Harish Sriram 
  --Problem Description---
  kernel does not detect interface in Ubuntu, driver missing in kernel

  Contact Information = hasri...@in.ibm.com

  ---Issue observed---
  While installing Ubuntu on a machine with Chelsio card, ubuntu-installer 
fails to show the interface name - probable cause would be due to missing 
driver in Ubuntu kernel. 

  Machine Type = Tuleta/Power 8 BML

  Additional Info-
  Installer Shell
  ---
  BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  ~ # ip a
  1: lo:  mtu 65536 qdisc noop qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: enP5p9s0f0:  mtu 1500 qdisc mq qlen 1000
  link/ether 98:be:94:02:09:7c brd ff:ff:ff:ff:ff:ff
  3: enP5p9s0f1:  mtu 1500 qdisc mq qlen 1000
  link/ether 98:be:94:02:09:7d brd ff:ff:ff:ff:ff:ff
  4: enP5p9s0f2:  mtu 1500 qdisc mq qlen 1000
  link/ether 98:be:94:02:09:7e brd ff:ff:ff:ff:ff:ff
  5: enP5p9s0f3:  mtu 1500 qdisc mq qlen 1000
  link/ether 98:be:94:02:09:7f brd ff:ff:ff:ff:ff:ff

  ~ # lspci -k
  :00:00.0 PCI bridge: IBM Device 03dc
  0001:00:00.0 PCI bridge: IBM Device 03dc
  0001:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:02:08.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:02:09.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:03:00.0 Ethernet controller: Chelsio Communications Inc T422-CR Unified 
Wire Ethernet Controller
Subsystem: IBM Device 03e5
  0001:03:00.1 Ethernet controller: Chelsio Communications Inc T422-CR Unified 
Wire Ethernet Controller
Subsystem: IBM Device 03e5
  0001:03:00.2 Ethernet controller: Chelsio Communications Inc Device 4102
Subsystem: IBM Device 03e5
  0001:03:00.3 Ethernet controller: Chelsio Communications Inc Device 4102
Subsystem: IBM Device 03e5
  0001:03:00.4 Ethernet controller: Chelsio Communications Inc T422-CR Unified 
Wire Ethernet Controller
Subsystem: IBM Device 03e5
  0001:03:00.5 SCSI storage controller: Chelsio Communications Inc T422-CR 
Unified Wire Storage Controller
Subsystem: IBM Device 03e5
  0001:03:00.6 Fibre Channel: Chelsio Communications Inc T422-CR Unified Wire 
Storage Controller
Subsystem: IBM Device 03e5
  0001:03:00.7 Ethernet controller: Chelsio Communications Inc Device 
Subsystem: IBM Device 03e5
  0001:04:00.0 RAID bus controller: IBM PCI-E IPR SAS Adapter (ASIC) (rev 02)
Subsystem: IBM Device 03ff
  0004:00:00.0 PCI bridge: IBM Device 03dc
  0004:01:00.0 PCI bridge: Integrated Device Technology, Inc. [IDT] 
PES16T4A/4T4G2 PCI Express Gen2 Switch (rev 02)
  0004:02:02.0 PCI bridge: Integrated Device Technology, Inc. [IDT] 
PES16T4A/4T4G2 PCI Express Gen2 Switch (rev 02)
  0004:02:03.0 PCI bridge: Integrated Device Technology, Inc. [IDT] 
PES16T4A/4T4G2 PCI Express Gen2 Switch (rev 02)
  0004:03:00.0 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to 
PCI Express HBA (rev 02)
Subsystem: IBM Device 041e
  0004:03:00.1 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to 
PCI Express HBA (rev 02)
Subsystem: IBM Device 041e
  0004:04:00.0 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to 
PCI Express HBA (rev 02)
Subsystem: IBM Device 041e
  0004:04:00.1 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to 
PCI Express HBA (rev 02)
Subsystem: IBM Device 041e
  0005:00:00.0 PCI bridge: IBM Device 03dc
  0005:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI 
Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA (rev ca)
  0005:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI 
Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA (rev ca)
  0005:02:08.0 PCI bridge: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI 
Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA (rev ca)
  0005:02:09.0 PCI bridge: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI 
Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA (rev ca)
  0005:02:10.0 PCI bridge: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI 
Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA (rev ca)
  0005:02:11.0 PCI bridge: PLX

[Kernel-packages] [Bug 1748983] Re: Generate per-machine MOK for dkms signing

https://code.launchpad.net/~ubuntu-core-dev/shim/+git/shim-signed/+ref
/self-signed

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

Title:
  Generate per-machine MOK for dkms signing

Status in dkms package in Ubuntu:
  In Progress
Status in shim-signed package in Ubuntu:
  In Progress

Bug description:
  shim-signed's update-secureboot-policy should allow creating a
  machine-owner key, and using this for signing kernel modules built via
  DKMS. Key generation and enrolling should be made as easy as possible
  for users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1748983/+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 1748565] Re: Bluetooth: hci0: last event is not cmd complete (0x0f)

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux (Ubuntu)
   Status: New => 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/1748565

Title:
  Bluetooth: hci0: last event is not cmd complete (0x0f)

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

Bug description:
  Hello,

  dmesg:
  [ 3363.056494] Bluetooth: hci0: last event is not cmd complete (0x0f)

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1811 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 20:35:29 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1748565/+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 1748979] Status changed to Confirmed

This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => 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/1748979

Title:
  When playing a video, the whole screen will freeze (incl. Ubuntu
  itself) until the video is done playing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With some videos, it freezes VLC (windowed) and the whole computer. I
  can still hear the sound playing, and the computer operates normally
  again after the video is done playing.

  While it's frozen, I can't move the mouse, none of the hotkeys work
  (ctrl alt t, alt tab, etc), and none of the screen updates. Even the
  vol up/down keys on my Thinkpad don't do anything anymore.

  Once the video is done playing in VLC, everything is back to normal.

  It doesn't always happen with the same video, and it's not always at
  the same point in the video.

  Description:  Ubuntu 17.10
  Release:  17.10

  vlc:
Installed: 2.2.6-6
Candidate: 2.2.6-6
Version table:
   *** 2.2.6-6 500
  500 http://ca.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   coaxial6258 F...m pulseaudio
   /dev/snd/controlC0:  coaxial6258 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 12 14:56:28 2018
  HibernationDevice: RESUME=UUID=7d31-ad44-46d0-bfcc-dba92785b74e
  InstallationDate: Installed on 2017-05-15 (273 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 23243YU
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-27 (108 days ago)
  dmi.bios.date: 10/08/2017
  dmi.bios.vendor: coreboot
  dmi.bios.version: CBET4000 4.6-1715-gef1a5ede6c
  dmi.board.name: 23243YU
  dmi.board.vendor: LENOVO
  dmi.board.version: ThinkPad X230
  dmi.chassis.type: 9
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvncoreboot:bvrCBET40004.6-1715-gef1a5ede6c:bd10/08/2017:svnLENOVO:pn23243YU:pvrThinkPadX230:rvnLENOVO:rn23243YU:rvrThinkPadX230:cvnLENOVO:ct9:cvr:
  dmi.product.name: 23243YU
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748979/+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 1748983] Re: Generate per-machine MOK for dkms signing

dkms changes in debdiff format. There didn't seem to be a code branch
for dkms specific to Ubuntu.

** Patch added: "dkms.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1748983/+attachment/5053788/+files/dkms.debdiff

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

Title:
  Generate per-machine MOK for dkms signing

Status in dkms package in Ubuntu:
  In Progress
Status in shim-signed package in Ubuntu:
  In Progress

Bug description:
  shim-signed's update-secureboot-policy should allow creating a
  machine-owner key, and using this for signing kernel modules built via
  DKMS. Key generation and enrolling should be made as easy as possible
  for users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1748983/+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 1748983] [NEW] Generate per-machine MOK for dkms signing

Public bug reported:

shim-signed's update-secureboot-policy should allow creating a machine-
owner key, and using this for signing kernel modules built via DKMS. Key
generation and enrolling should be made as easy as possible for users.

** Affects: dkms (Ubuntu)
 Importance: High
 Assignee: Mathieu Trudel-Lapierre (cyphermox)
 Status: In Progress

** Affects: shim-signed (Ubuntu)
 Importance: High
 Assignee: Mathieu Trudel-Lapierre (cyphermox)
 Status: In Progress

** Also affects: dkms (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: dkms (Ubuntu)
   Status: New => In Progress

** Changed in: shim-signed (Ubuntu)
   Status: New => In Progress

** Changed in: dkms (Ubuntu)
   Importance: Undecided => High

** Changed in: shim-signed (Ubuntu)
   Importance: Undecided => High

** Changed in: dkms (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

** Changed in: shim-signed (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

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

Title:
  Generate per-machine MOK for dkms signing

Status in dkms package in Ubuntu:
  In Progress
Status in shim-signed package in Ubuntu:
  In Progress

Bug description:
  shim-signed's update-secureboot-policy should allow creating a
  machine-owner key, and using this for signing kernel modules built via
  DKMS. Key generation and enrolling should be made as easy as possible
  for users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1748983/+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 1748983] Re: Generate per-machine MOK for dkms signing

There are dkms changes and shim-signed changes for this. I'm linking
both.

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

Title:
  Generate per-machine MOK for dkms signing

Status in dkms package in Ubuntu:
  In Progress
Status in shim-signed package in Ubuntu:
  In Progress

Bug description:
  shim-signed's update-secureboot-policy should allow creating a
  machine-owner key, and using this for signing kernel modules built via
  DKMS. Key generation and enrolling should be made as easy as possible
  for users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1748983/+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 1748985] [NEW] linux: 4.4.0-116.140 -proposed tracker

2018-02-12 Thread Khaled El Mously

Public bug reported:

This bug is for tracking the 4.4.0-116.140 upload package. This bug will
contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

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


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

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

Title:
  linux: 4.4.0-116.140 -proposed tracker

Status in linux package in Ubuntu:
  New

Bug description:
  This bug is for tracking the 4.4.0-116.140 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748985/+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 1694485] Re: Ubuntu17.04: CAPI: call trace seen while error injection to the CAPI card.

** Also affects: linux (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Artful)
   Status: New => In Progress

** Changed in: linux (Ubuntu Artful)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Artful)
   Status: In Progress => Fix Released

** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Ubuntu17.04: CAPI: call trace seen while error injection to  the CAPI
  card.

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  Fix Released

Bug description:
  == Comment: #0 - SUDEESH JOHN  - 2017-03-18 13:55:03 ==
  ---Problem Description---
  call trace while injecting error to the CAPI card.

  " WARNING: CPU: 31 PID: 491 at 
/build/linux-VtwHOM/linux-4.10.0/drivers/misc/cxl/main.c:325 
cxl_adapter_context_unlock+0x68/0x90 [cxl] " 

  ---uname output---
  Linux freak 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:27:28 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = PowerNV 8247-21L 

  ---Steps to Reproduce---
  1. echo 1 > /sys/kernel/debug/powerpc/eeh_max_freezes
  2. echo 1 > /sys/class/cxl/card0/perst_reloads_same_image
  3.  echo 0x8000 > 
/sys/kernel/debug/powerpc/PCI/err_injct_outbound
   
  ---The complete call trace ---

  Mar 18 14:39:09 freak kernel: [  289.675421] [ cut here 
]
  Mar 18 14:39:09 freak kernel: [  289.675431] WARNING: CPU: 5 PID: 491 at 
/build/linux-VtwHOM/linux-4.10.0/drivers/misc/cxl/main.c:325 
cxl_adapter_context_unlock+0x68/0x90 [cxl]
  Mar 18 14:39:09 freak kernel: [  289.675432] Modules linked in: xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT 
nf_reject_ipv4 xt_tcpudp bridge stp llc kvm_hv kvm_pr kvm ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter uio_pdrv_genirq uio 
ipmi_powernv ipmi_devintf ipmi_msghandler powernv_op_panel powernv_rng 
vmx_crypto ibmpowernv leds_powernv ib_iser rdma_cm iw_cm ib_cm ib_core configfs 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 
btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx 
xor raid6_pq raid1 raid0 multipath linear ses enclosure scsi_transport_sas 
bnx2x mlx5_core tg3 cxl mdio ipr libcrc32c devlink crc32c_vpmsum pnv_php
  Mar 18 14:39:09 freak kernel: [  289.675490] CPU: 5 PID: 491 Comm: eehd Not 
tainted 4.10.0-13-generic #15-Ubuntu
  Mar 18 14:39:09 freak kernel: [  289.675492] task: c003bfbfde00 
task.stack: c003bfc5c000
  Mar 18 14:39:09 freak kernel: [  289.675493] NIP: d5cc0ca0 LR: 
d5cc0c9c CTR: c0605aa0
  Mar 18 14:39:09 freak kernel: [  289.675495] REGS: c003bfc5f6a0 TRAP: 
0700   Not tainted  (4.10.0-13-generic)
  Mar 18 14:39:09 freak kernel: [  289.675496] MSR: 9282b033 

  Mar 18 14:39:09 freak kernel: [  289.675504]   CR: 28008282  XER: 2000
  Mar 18 14:39:09 freak kernel: [  289.675504] CFAR: c0b568dc SOFTE: 1
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR00: d5cc0c9c 
c003bfc5f920 d5cf2d88 002f
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR04: 0001 
03fd 63206576 
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR08: c15dc700 
  0001
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR12: 8800 
cfb82d00 c0108c88 c003c51f9f00
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR16:  
  
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR20:  
  c0d53990
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR24: c0d53968 
c14a4330 c003ab8fa800 c003bd2c20c0
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR28: c003c5051098 
 c003ab8fa800 
  Mar 18 14:39:09 freak kernel: [  289.675535] NIP [d5cc0ca0] 
cxl_adapter_context_unlock+0x68/0x90 [cxl]
  Mar 18 14:39:09 freak kernel: [  289.675540] LR [d5cc0c9c] 
cxl_adapter_context_unlock+0x64/0x90 [cxl]
  Mar 18 14:39:09 freak kernel: [  289.675541] Call Trace:
  Mar 18 14:39:09 freak kernel: [  289.675547] [c003bfc5f920] 
[d5cc0c9c] cxl_adapter_context_unlock+0x64/0x90 [cxl] (unreliable)
  Mar 18 14:39:09 freak kernel: [  289.675556] [c003bfc5f980] 
[d5cd022c] cxl_configur

[Kernel-packages] [Bug 1706247] Re: Add support for 16g huge pages on Ubuntu 16.04.2 PowerNV

** Also affects: linux (Ubuntu Bionic)
   Importance: Medium
 Assignee: Joseph Salisbury (jsalisbury)
   Status: In Progress

** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Released

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

Title:
  Add support for 16g huge pages on Ubuntu 16.04.2 PowerNV

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  16G Huge Pages are not supported on PowerNV (bare metal) installations. 
Ubuntu 16.04.2 still allows 16G huge pages to be turned on.
   
  Contact Information = Mike Hollinger (mchol...@us.ibm.com) 
   
  ---uname output---
  Linux aprilmin4 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:53:54 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8335-GTB 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Add the following to the kernel boot args (either via editing the 
petitboot boot option manually, or updating /boot/grub/grub.cfg:

  default_hugepagesz=16G hugepagesz=16G hugepages=4

  2. Boot Linux
  3. Observe that the kernel believes 16G huge pages are available:
  ubuntu@aprilmin7:~$ cat /proc/meminfo | grep -i huge
  AnonHugePages:475136 kB
  HugePages_Total:   0
  HugePages_Free:0
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   16777216 kB
  ubuntu@aprilmin7:~$ ls /sys/devices/system/node/node0/hugepages
  hugepages-1024kB  hugepages-16384kB  hugepages-16777216kB

   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for Mike Hollinger (mchol...@us.ibm.com): 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.

  
  This may be recreated on any bare metal POWER8 server with Ubuntu 16.04.2; I 
haven't checked other versions of Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1706247/+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 1707875] Re: [18.04] include support for Python bindings in "perf"