date:20170920

Default Comment by Bridge

** Attachment added: "test-case: io_setup.c"
   https://bugs.launchpad.net/bugs/1718397/+attachment/4954139/+files/io_setup.c

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

Title:
  multipath -ll is not showing the disks which are actually multipath

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Zesty:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  [Impact]

   * The number of available AIO contexts is severely limited
 on systems with a large number of possible CPUs 
 (e.g., IBM POWER8 processors w/ 20ish cores * 8 threads/core,
 and other multithreaded server-class processors).

   * This prevents application such as multipath/directio checker
 to provide all of the available devices to the system.

   * Other applications which depend on AIO can be affected/limited.

   * The patch fixes how aio increments the number of active contexts
 (seen in /proc/sys/fs/aio-nr) and checks that against the global
 limit (seen in /proc/sys/fs/aio-max-nr).

  [Test Case]

   * A synthetic test-case is attached (io_setup_v2.c) and demonstrated
 (original/patched kernels) in comment #4.

   * Trying to perform multipath discovery in debug/verbose mode
 (i.e., "multipath -v3" command) with sufficient number of 
 individual paths using the "directio" path checker should
 demonstrate the problem/solution as well (i.e., presence or
 not of "io_setup failed" messages).

  [Regression Potential]

   * Note the fix is trivial and has been tested by several users,
 even caused the introduction of a new test-case in "libaio";
 (but that can never be a strong enough reason for no more errors).

   * Applications which use aio with small "nr_events" value as argument
 to "io_setup()" now have access to a much larger number of aio contexts;
 but hopefully those apps are already only requesting what they need,
 not trying to get more and more.

   * Applications which relied in the _incorrect_ behavior of 
'/proc/sys/fs/aio-nr'
 being possibly greater than '/proc/sys/fs/aio-max-nr' might have problems,
 but those apps should be fixed.


  Problem Description
  =
  I am facing this issue for Texan Flash storage 840 disks which are coming 
from coho and salfish adapter

  coho adapter with 840 storage  is 3G disks and salfish adapter with
  840 is 12G disks

  I am able to see those disks in lsblk o/p but not in multipath -ll
  comamnd

  0004:01:00.0 Coho: Saturn-X  U78C9.001.WZS0060-P1-C6 
0x1090fa2a51f8  host10  Online
  0004:01:00.1 Coho: Saturn-X  U78C9.001.WZS0060-P1-C6 
0x1090fa2a51f9  host11  Online

  0005:09:00.0 Sailfish: QLogic 8GBU78C9.001.WZS0060-P1-C9 
0x2124ff787778  host2   Online
  0005:09:00.1 Sailfish: QLogic 8GBU78C9.001.WZS0060-P1-C9 
0x2124ff787779  host4   Online

  root@luckyv1:/dev/disk# multipath -ll | grep "size=3.0G" -B 1
  root@luckyv1:/dev/disk# multipath -ll | grep "size=12G" -B 1
  root@luckyv1:/dev/disk#

  == Comment: #3 - Luciano Chavez  - 2016-09-20 20:22:20 ==
  I edited /etc/multipath.conf and added
  verbosity 6

  to crank up the output and ran multipath -ll and saved it off to a
  text file (attached). All the using the directio checker failed and
  those using the tur checker seem to work.

  Sep 20 20:07:36 | loading //lib/multipath/libcheckdirectio.so checker
  Sep 20 20:07:36 | loading //lib/multipath/libprioconst.so prioritizer
  Sep 20 20:07:36 | Discover device 
/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/block/sdai
  Sep 20 20:07:36 | sdai: udev property ID_WWN whitelisted
  Sep 20 20:07:36 | sdai: not found in pathvec
  Sep 20 20:07:36 | sdai: mask = 0x25
  Sep 20 20:07:36 | sdai: dev_t = 66:32
  Sep 20 20:07:36 | open 
'/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/block/sdai/size'
  Sep 20 20:07:36 | sdai: size = 20971520
  Sep 20 20:07:36 | sdai: vendor = IBM
  Sep 20 20:07:36 | sdai: product = FlashSystem-9840
  Sep 20 20:07:36 | sdai: rev = 1442
  Sep 20 20:07:36 | sdai: h:b:t:l = 3:0:0:0
  Sep 20 20:07:36 | SCSI target 3:0:0 -> FC rport 3:0-2
  Sep 20 20:07:36 | sdai: tgt_node_name = 0x500507605e839800
  Sep 20 20:07:36 | open 
'/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/state'
  Sep 20 20:07:36 | sdai: path state = running
  Sep 20 20:07:36 | sdai: get_state
  Sep 20 20:07:36 | sdai: path_checker = directio (internal default)
  Sep 20 20:07:36 | sdai: checker

[Kernel-packages] [Bug 1718397] test-case: io_setup_v2.c

Default Comment by Bridge

** Attachment added: "test-case: io_setup_v2.c"
   
https://bugs.launchpad.net/bugs/1718397/+attachment/4954140/+files/file_146489.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/1718397

Title:
  multipath -ll is not showing the disks which are actually multipath

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Zesty:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  [Impact]

   * The number of available AIO contexts is severely limited
 on systems with a large number of possible CPUs 
 (e.g., IBM POWER8 processors w/ 20ish cores * 8 threads/core,
 and other multithreaded server-class processors).

   * This prevents application such as multipath/directio checker
 to provide all of the available devices to the system.

   * Other applications which depend on AIO can be affected/limited.

   * The patch fixes how aio increments the number of active contexts
 (seen in /proc/sys/fs/aio-nr) and checks that against the global
 limit (seen in /proc/sys/fs/aio-max-nr).

  [Test Case]

   * A synthetic test-case is attached (io_setup_v2.c) and demonstrated
 (original/patched kernels) in comment #4.

   * Trying to perform multipath discovery in debug/verbose mode
 (i.e., "multipath -v3" command) with sufficient number of 
 individual paths using the "directio" path checker should
 demonstrate the problem/solution as well (i.e., presence or
 not of "io_setup failed" messages).

  [Regression Potential]

   * Note the fix is trivial and has been tested by several users,
 even caused the introduction of a new test-case in "libaio";
 (but that can never be a strong enough reason for no more errors).

   * Applications which use aio with small "nr_events" value as argument
 to "io_setup()" now have access to a much larger number of aio contexts;
 but hopefully those apps are already only requesting what they need,
 not trying to get more and more.

   * Applications which relied in the _incorrect_ behavior of 
'/proc/sys/fs/aio-nr'
 being possibly greater than '/proc/sys/fs/aio-max-nr' might have problems,
 but those apps should be fixed.


  Problem Description
  =
  I am facing this issue for Texan Flash storage 840 disks which are coming 
from coho and salfish adapter

  coho adapter with 840 storage  is 3G disks and salfish adapter with
  840 is 12G disks

  I am able to see those disks in lsblk o/p but not in multipath -ll
  comamnd

  0004:01:00.0 Coho: Saturn-X  U78C9.001.WZS0060-P1-C6 
0x1090fa2a51f8  host10  Online
  0004:01:00.1 Coho: Saturn-X  U78C9.001.WZS0060-P1-C6 
0x1090fa2a51f9  host11  Online

  0005:09:00.0 Sailfish: QLogic 8GBU78C9.001.WZS0060-P1-C9 
0x2124ff787778  host2   Online
  0005:09:00.1 Sailfish: QLogic 8GBU78C9.001.WZS0060-P1-C9 
0x2124ff787779  host4   Online

  root@luckyv1:/dev/disk# multipath -ll | grep "size=3.0G" -B 1
  root@luckyv1:/dev/disk# multipath -ll | grep "size=12G" -B 1
  root@luckyv1:/dev/disk#

  == Comment: #3 - Luciano Chavez  - 2016-09-20 20:22:20 ==
  I edited /etc/multipath.conf and added
  verbosity 6

  to crank up the output and ran multipath -ll and saved it off to a
  text file (attached). All the using the directio checker failed and
  those using the tur checker seem to work.

  Sep 20 20:07:36 | loading //lib/multipath/libcheckdirectio.so checker
  Sep 20 20:07:36 | loading //lib/multipath/libprioconst.so prioritizer
  Sep 20 20:07:36 | Discover device 
/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/block/sdai
  Sep 20 20:07:36 | sdai: udev property ID_WWN whitelisted
  Sep 20 20:07:36 | sdai: not found in pathvec
  Sep 20 20:07:36 | sdai: mask = 0x25
  Sep 20 20:07:36 | sdai: dev_t = 66:32
  Sep 20 20:07:36 | open 
'/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/block/sdai/size'
  Sep 20 20:07:36 | sdai: size = 20971520
  Sep 20 20:07:36 | sdai: vendor = IBM
  Sep 20 20:07:36 | sdai: product = FlashSystem-9840
  Sep 20 20:07:36 | sdai: rev = 1442
  Sep 20 20:07:36 | sdai: h:b:t:l = 3:0:0:0
  Sep 20 20:07:36 | SCSI target 3:0:0 -> FC rport 3:0-2
  Sep 20 20:07:36 | sdai: tgt_node_name = 0x500507605e839800
  Sep 20 20:07:36 | open 
'/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/state'
  Sep 20 20:07:36 | sdai: path state = running
  Sep 20 20:07:36 | sdai: get_state
  Sep 20 20:07:36 | sdai: path_checker = directio (internal default)
  Sep 20 20:07:36 | sdai:

[Kernel-packages] [Bug 1718578] Re: Support setting I2C_TIMEOUT via ioctl for i2c-designware

2017-09-20 Thread Kai-Heng Feng

This one is for tracking SRU process, no need to do apport-collect.

** Tags added: originate-from-1703800 somerville

** Changed in: hwe-next
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

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

Title:
  Support setting I2C_TIMEOUT via ioctl for i2c-designware

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SRU Justification

  [Impact]
  The timeout value in i2c-designware is hardcoded. Userspace tool may want to 
change the timeout value via ioctl I2C_TIMEOUT, but it doesn't work for 
i2c-designware.

  [Test Case]
  Change the timeout value via ioctl I2C_TIMEOUT. Nothing happened.
  With the patch, timeout value for i2c-designware will be updated correctly.

  [Regression Potential]
  Minimal. The change only applies to a specific driver, i2c-designware. Also, 
it has minimal code change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718578/+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 1718397] output of multipath -ll with verbosity increased to 6

Default Comment by Bridge

** Attachment added: "output of multipath -ll with verbosity increased to 6"
   
https://bugs.launchpad.net/bugs/1718397/+attachment/4954138/+files/multipath-trace.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/1718397

Title:
  multipath -ll is not showing the disks which are actually multipath

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Zesty:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  [Impact]

   * The number of available AIO contexts is severely limited
 on systems with a large number of possible CPUs 
 (e.g., IBM POWER8 processors w/ 20ish cores * 8 threads/core,
 and other multithreaded server-class processors).

   * This prevents application such as multipath/directio checker
 to provide all of the available devices to the system.

   * Other applications which depend on AIO can be affected/limited.

   * The patch fixes how aio increments the number of active contexts
 (seen in /proc/sys/fs/aio-nr) and checks that against the global
 limit (seen in /proc/sys/fs/aio-max-nr).

  [Test Case]

   * A synthetic test-case is attached (io_setup_v2.c) and demonstrated
 (original/patched kernels) in comment #4.

   * Trying to perform multipath discovery in debug/verbose mode
 (i.e., "multipath -v3" command) with sufficient number of 
 individual paths using the "directio" path checker should
 demonstrate the problem/solution as well (i.e., presence or
 not of "io_setup failed" messages).

  [Regression Potential]

   * Note the fix is trivial and has been tested by several users,
 even caused the introduction of a new test-case in "libaio";
 (but that can never be a strong enough reason for no more errors).

   * Applications which use aio with small "nr_events" value as argument
 to "io_setup()" now have access to a much larger number of aio contexts;
 but hopefully those apps are already only requesting what they need,
 not trying to get more and more.

   * Applications which relied in the _incorrect_ behavior of 
'/proc/sys/fs/aio-nr'
 being possibly greater than '/proc/sys/fs/aio-max-nr' might have problems,
 but those apps should be fixed.


  Problem Description
  =
  I am facing this issue for Texan Flash storage 840 disks which are coming 
from coho and salfish adapter

  coho adapter with 840 storage  is 3G disks and salfish adapter with
  840 is 12G disks

  I am able to see those disks in lsblk o/p but not in multipath -ll
  comamnd

  0004:01:00.0 Coho: Saturn-X  U78C9.001.WZS0060-P1-C6 
0x1090fa2a51f8  host10  Online
  0004:01:00.1 Coho: Saturn-X  U78C9.001.WZS0060-P1-C6 
0x1090fa2a51f9  host11  Online

  0005:09:00.0 Sailfish: QLogic 8GBU78C9.001.WZS0060-P1-C9 
0x2124ff787778  host2   Online
  0005:09:00.1 Sailfish: QLogic 8GBU78C9.001.WZS0060-P1-C9 
0x2124ff787779  host4   Online

  root@luckyv1:/dev/disk# multipath -ll | grep "size=3.0G" -B 1
  root@luckyv1:/dev/disk# multipath -ll | grep "size=12G" -B 1
  root@luckyv1:/dev/disk#

  == Comment: #3 - Luciano Chavez  - 2016-09-20 20:22:20 ==
  I edited /etc/multipath.conf and added
  verbosity 6

  to crank up the output and ran multipath -ll and saved it off to a
  text file (attached). All the using the directio checker failed and
  those using the tur checker seem to work.

  Sep 20 20:07:36 | loading //lib/multipath/libcheckdirectio.so checker
  Sep 20 20:07:36 | loading //lib/multipath/libprioconst.so prioritizer
  Sep 20 20:07:36 | Discover device 
/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/block/sdai
  Sep 20 20:07:36 | sdai: udev property ID_WWN whitelisted
  Sep 20 20:07:36 | sdai: not found in pathvec
  Sep 20 20:07:36 | sdai: mask = 0x25
  Sep 20 20:07:36 | sdai: dev_t = 66:32
  Sep 20 20:07:36 | open 
'/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/block/sdai/size'
  Sep 20 20:07:36 | sdai: size = 20971520
  Sep 20 20:07:36 | sdai: vendor = IBM
  Sep 20 20:07:36 | sdai: product = FlashSystem-9840
  Sep 20 20:07:36 | sdai: rev = 1442
  Sep 20 20:07:36 | sdai: h:b:t:l = 3:0:0:0
  Sep 20 20:07:36 | SCSI target 3:0:0 -> FC rport 3:0-2
  Sep 20 20:07:36 | sdai: tgt_node_name = 0x500507605e839800
  Sep 20 20:07:36 | open 
'/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/state'
  Sep 20 20:07:36 | sdai: path state = running
  Sep 20 20:07:36 | sdai: get_state
  Sep 20 20:07:36 | sdai: path_checker = directio (internal

[Kernel-packages] [Bug 1718397] Re: multipath -ll is not showing the disks which are actually multipath

2017-09-20 Thread Frank Heimes

** Changed in: ubuntu-power-systems
   Status: New => Triaged

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

Title:
  multipath -ll is not showing the disks which are actually multipath

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Zesty:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  [Impact]

   * The number of available AIO contexts is severely limited
 on systems with a large number of possible CPUs 
 (e.g., IBM POWER8 processors w/ 20ish cores * 8 threads/core,
 and other multithreaded server-class processors).

   * This prevents application such as multipath/directio checker
 to provide all of the available devices to the system.

   * Other applications which depend on AIO can be affected/limited.

   * The patch fixes how aio increments the number of active contexts
 (seen in /proc/sys/fs/aio-nr) and checks that against the global
 limit (seen in /proc/sys/fs/aio-max-nr).

  [Test Case]

   * A synthetic test-case is attached (io_setup_v2.c) and demonstrated
 (original/patched kernels) in comment #4.

   * Trying to perform multipath discovery in debug/verbose mode
 (i.e., "multipath -v3" command) with sufficient number of 
 individual paths using the "directio" path checker should
 demonstrate the problem/solution as well (i.e., presence or
 not of "io_setup failed" messages).

  [Regression Potential]

   * Note the fix is trivial and has been tested by several users,
 even caused the introduction of a new test-case in "libaio";
 (but that can never be a strong enough reason for no more errors).

   * Applications which use aio with small "nr_events" value as argument
 to "io_setup()" now have access to a much larger number of aio contexts;
 but hopefully those apps are already only requesting what they need,
 not trying to get more and more.

   * Applications which relied in the _incorrect_ behavior of 
'/proc/sys/fs/aio-nr'
 being possibly greater than '/proc/sys/fs/aio-max-nr' might have problems,
 but those apps should be fixed.


  Problem Description
  =
  I am facing this issue for Texan Flash storage 840 disks which are coming 
from coho and salfish adapter

  coho adapter with 840 storage  is 3G disks and salfish adapter with
  840 is 12G disks

  I am able to see those disks in lsblk o/p but not in multipath -ll
  comamnd

  0004:01:00.0 Coho: Saturn-X  U78C9.001.WZS0060-P1-C6 
0x1090fa2a51f8  host10  Online
  0004:01:00.1 Coho: Saturn-X  U78C9.001.WZS0060-P1-C6 
0x1090fa2a51f9  host11  Online

  0005:09:00.0 Sailfish: QLogic 8GBU78C9.001.WZS0060-P1-C9 
0x2124ff787778  host2   Online
  0005:09:00.1 Sailfish: QLogic 8GBU78C9.001.WZS0060-P1-C9 
0x2124ff787779  host4   Online

  root@luckyv1:/dev/disk# multipath -ll | grep "size=3.0G" -B 1
  root@luckyv1:/dev/disk# multipath -ll | grep "size=12G" -B 1
  root@luckyv1:/dev/disk#

  == Comment: #3 - Luciano Chavez  - 2016-09-20 20:22:20 ==
  I edited /etc/multipath.conf and added
  verbosity 6

  to crank up the output and ran multipath -ll and saved it off to a
  text file (attached). All the using the directio checker failed and
  those using the tur checker seem to work.

  Sep 20 20:07:36 | loading //lib/multipath/libcheckdirectio.so checker
  Sep 20 20:07:36 | loading //lib/multipath/libprioconst.so prioritizer
  Sep 20 20:07:36 | Discover device 
/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/block/sdai
  Sep 20 20:07:36 | sdai: udev property ID_WWN whitelisted
  Sep 20 20:07:36 | sdai: not found in pathvec
  Sep 20 20:07:36 | sdai: mask = 0x25
  Sep 20 20:07:36 | sdai: dev_t = 66:32
  Sep 20 20:07:36 | open 
'/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/block/sdai/size'
  Sep 20 20:07:36 | sdai: size = 20971520
  Sep 20 20:07:36 | sdai: vendor = IBM
  Sep 20 20:07:36 | sdai: product = FlashSystem-9840
  Sep 20 20:07:36 | sdai: rev = 1442
  Sep 20 20:07:36 | sdai: h:b:t:l = 3:0:0:0
  Sep 20 20:07:36 | SCSI target 3:0:0 -> FC rport 3:0-2
  Sep 20 20:07:36 | sdai: tgt_node_name = 0x500507605e839800
  Sep 20 20:07:36 | open 
'/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/state'
  Sep 20 20:07:36 | sdai: path state = running
  Sep 20 20:07:36 | sdai: get_state
  Sep 20 20:07:36 | sdai: path_checker = directio (internal default)
  Sep 20 20:07:36 | sdai: checker timeout = 30 ms (internal default)
  Sep 20 20:07:36 | io_setup failed
  Sep 20 20:07:36 |

[Kernel-packages] [Bug 1718292] Re: POWER9: NX842 module changes

2017-09-20 Thread Frank Heimes

** Changed in: ubuntu-power-systems
   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/1718292

Title:
  POWER9: NX842 module changes

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

Bug description:
  This feature request will be used to submit NX842 changes needed to
  support on p9 - Using VAS interfaces instead of icswx to communicate
  with VAS (on PowerNV), modification of HCALL interface (on PowerVM, if
  needed) and other format changes.

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

2017-09-20 Thread Ubuntu Kernel Bot

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 1718578

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

Title:
  Support setting I2C_TIMEOUT via ioctl for i2c-designware

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SRU Justification

  [Impact]
  The timeout value in i2c-designware is hardcoded. Userspace tool may want to 
change the timeout value via ioctl I2C_TIMEOUT, but it doesn't work for 
i2c-designware.

  [Test Case]
  Change the timeout value via ioctl I2C_TIMEOUT. Nothing happened.
  With the patch, timeout value for i2c-designware will be updated correctly.

  [Regression Potential]
  Minimal. The change only applies to a specific driver, i2c-designware. Also, 
it has minimal code change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718578/+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 1718578] [NEW] Support setting I2C_TIMEOUT via ioctl for i2c-designware

2017-09-20 Thread Kai-Heng Feng

Public bug reported:

SRU Justification

[Impact]
The timeout value in i2c-designware is hardcoded. Userspace tool may want to 
change the timeout value via ioctl I2C_TIMEOUT, but it doesn't work for 
i2c-designware.

[Test Case]
Change the timeout value via ioctl I2C_TIMEOUT. Nothing happened.
With the patch, timeout value for i2c-designware will be updated correctly.

[Regression Potential]
Minimal. The change only applies to a specific driver, i2c-designware. Also, it 
has minimal code change.

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

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

** No longer affects: subiquity (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/1718578

Title:
  Support setting I2C_TIMEOUT via ioctl for i2c-designware

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  SRU Justification

  [Impact]
  The timeout value in i2c-designware is hardcoded. Userspace tool may want to 
change the timeout value via ioctl I2C_TIMEOUT, but it doesn't work for 
i2c-designware.

  [Test Case]
  Change the timeout value via ioctl I2C_TIMEOUT. Nothing happened.
  With the patch, timeout value for i2c-designware will be updated correctly.

  [Regression Potential]
  Minimal. The change only applies to a specific driver, i2c-designware. Also, 
it has minimal code change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718578/+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 1694167] Re: unity does not start when booting with 4.11.3 kernel

[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/1694167

Title:
  unity does not start when booting with 4.11.3 kernel

Status in linux package in Ubuntu:
  Expired

Bug description:
  I installed the recent 4.11.3 kernel from the packages downloaded from
  kernel.ubuntu.org

  After rebooting unity did not start properly. I had no dash, no
  decorations and no dock. After starting unity manually from the
  command line I got window decorations for a program that is run after
  login but nothing else.

  After switching back to 4.11.2 the system is working fine again.

  > lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  
  If you need further information please let me know!
  --- 
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-01 (347 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: linux (not installed)
  Tags:  zesty
  Uname: Linux 4.11.8-041108-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-04-26 (79 days ago)
  UserGroups: adm cdrom dip docker kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694167/+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 1685190] Re: Intermittent wireless network problem with RTL8821AE and 802.11n/EWC

[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/1685190

Title:
  Intermittent wireless network problem with RTL8821AE and 802.11n/EWC

Status in linux package in Ubuntu:
  Expired

Bug description:
  An intermittent but very repeatable problem has started occurring upon
  upgrading from Ubuntu 16.10 (kernel 4.8) to Kubuntu 17.04 (kernel
  4.10). After about 10 to 30 minutes the wireless network will stop
  working. The network manager will still report that the network is
  "connected" but all network requests will timeout. This problem occurs
  only with the wireless network and not the wired ethernet connection.
  After walking through the kernel bug reporting instructions
  (https://wiki.ubuntu.com/Kernel/LinuxWireless) I found that turning
  off "802.11n/EWC" in my router solves the problem. I have logged this
  as a problem with the kernel since it appears to be specific to my
  hardware. Please correct me if this was an incorrect assumption.

  Attached is two samples of the system log (obtained using KSystemLog) after 
running through the following method twice:
  1. Restart computer.
  2. Browse the web until problem occurs (about 10 to 30 minutes)
  3. Save system log.

  Here is the hardware info from `lshw -c network`:
*-network
 description: Wireless interface
 product: RTL8821AE 802.11ac PCIe Wireless Network Adapter
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:03:00.0
 logical name: wlp3s0
 version: 00
 serial: 6e:77:8e:04:bf:fb
 width: 64 bits
 clock: 33MHz
 capabilities: bus_master cap_list ethernet physical wireless
 configuration: broadcast=yes driver=rtl8821ae 
driverversion=4.10.0-19-generic firmware=N/A ip=192.168.0.4 latency=0 link=yes 
multicast=yes wireless=IEEE 802.11
 resources: irq:50 ioport:3000(size=256) memory:b200-b2003fff

  Here is my full answers to the questions asked in
  https://wiki.ubuntu.com/Kernel/LinuxWireless:

  Q: What is the full computer model number (ex. HP G32-301TX Notebook PC)?
  A: ASUSPRO P2520LA 
https://www.asus.com/au/Commercial-Notebooks/ASUSPRO-P2520LA/overview/

  Q: If you update your BIOS to the newest version following the guide here, 
does this change anything?
  A: No

  Regarding your wireless Access Point (AP):

  Q: 3a. What is the current AP manufacturer, full model, revision, and 
firmware version?
  A: Board ID:  F@ST3864V2
 Symmetric CPU Threads: 2
 HardWare Version:  253561846
 Serial Number: N7161262J001520
 Mac Address:   88:a6:c6:8b:b5:72
 Build Timestamp:   160325_1801
 Software Version:  8.353.1_F@ST5350_Optus
 Bootloader (CFE) Version:  8.337
 DSL PHY and Driver Version:A2pv6F039p.d26b
 Wireless Driver Version:   6.37.14.4803.cpe4.14L04.0-kdb
 Voice Service Version: Voice
 Manufacturer: Sagecom

  Q: 3b. If you update the AP to the latest firmware does it change 
anything?
  A: No

  Q: 3c. What wireless connection type are you using (802.11ac, 802.11n 
150/300, 802.11g, etc.)?
  A: I think 802.11n given that "802.11n/EWC" option in router is set to 
"Auto".

  3d. If you switch to a different wireless type (802.11g or 802.11n if you 
are using 802.11g) does this change anything?
  A: Yes. The problem is solved when "802.11n/EWC" is set to "Disabled".

  Q: 3e. What channel specifically are you using when this problem is 
reproducible?
  A: It doesn't seem to depend on the channel but the router commonly 
chooses channel 6 and 11.

  Q: 3f. In order to understand the wireless environment your AP is
  working in, please provide the output of the following terminal
  command:

  sudo iw dev wlan0 scan | grep -i "ds parameter set"
  A:
  DS Parameter set: channel 11
  DS Parameter set: channel 11
  DS Parameter set: channel 1
  DS Parameter set: channel 1
  DS Parameter set: channel 11
  DS Parameter set: channel 1

  Q: 3g. What encryption type are you using (ex. WEP, WPA2-PSK, etc.)?
  A: WPA2-PSK

  Q: 3h. If you change and remove encryption entirely does this change 
anything?
  A: I don't think so. I can repeat my testing if certainty is required on 
this one.

  Q: 3i. Do you have QoS (Quality of Service)/WMM (Wi-Fi Multimedia) 
enabled?
  A: Yes (It is set to "Auto").

  Q: 3j. If you disable/enable QoS/WMM does it change anything?
  A: No.

  Q: 3k. What is the current beacon interval (usually default is 100)?
  A: 100

  Q: 3l. If you adjust this to 50

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

--- Comment From hasri...@in.ibm.com 2017-09-20 23:29 EDT---
(In reply to comment #12)
> Also, it might be worth testing v4.14-rc1:
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc1/

Looks like build failed for ppc, can you check?

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

Title:
  xfstest fails with corrupt file /mnt/scratch/1 - non-zero size but no
  extents ( ext4 )

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

Bug description:
  xfstests fails non-zero size but no extents on ext4 filesystem

  Environment
  --
  Kernel Build:  4.12.1-041201-generic

  Model  : 8247-22L
  Platform:  PowerNV ( P8 )

  Uname output
  ---
  # uname -a
  Linux ltc-test-ci2 4.12.1-041201-generic #201707121132 SMP Wed Jul 12 
17:03:25 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Create a loop device with ext4 filesystem
  2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd 
xfstests-dev
  3. make
  4. Create a local.config for running with created loop device
  5. Run xfstests-dev test  : ./check tests/generic/044

  The test 044 fails with following
  generic/044 - output mismatch (see 
/root/harish/xfstests-dev/results//generic/044.out.bad)
  --- tests/generic/044.out 2017-07-13 06:04:36.208323135 -0400
  +++ /root/harish/xfstests-dev/results//generic/044.out.bad
2017-07-14 06:24:08.153731112 -0400
  @@ -1 +1,1000 @@
   QA output created by 044
  +corrupt file /mnt/scratch/1 - non-zero size but no extents
  +corrupt file /mnt/scratch/2 - non-zero size but no extents
  +corrupt file /mnt/scratch/3 - non-zero size but no extents
  +corrupt file /mnt/scratch/4 - non-zero size but no extents
  +corrupt file /mnt/scratch/5 - non-zero size but no extents
  +corrupt file /mnt/scratch/6 - non-zero size but no extents
  ...
  (Run 'diff -u tests/generic/044.out 
/root/harish/xfstests-dev/results//generic/044.out.bad'  to see the entire diff)
  Ran: generic/044
  Failures: generic/044
  Failed 1 of 1 tests

  
  Dmesg:
  --
  [17244.878673] EXT4-fs (loop0): mounted filesystem with ordered data mode. 
Opts: (null)
  [17245.517227] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17245.697100] EXT4-fs (loop0): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17245.710634] run fstests generic/044 at 2017-07-14 06:23:49
  [17246.534410] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17246.535534] EXT4-fs (loop2): shut down requested (1)
  [17246.535625] Aborting journal on device loop2-8.
  [17247.278467] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17259.888304] EXT4-fs (loop2): shut down requested (2)
  [17259.995751] Aborting journal on device loop2-8.
  [17260.113582] EXT4-fs (loop2): recovery complete
  [17260.113902] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17260.190076] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17264.821978] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr


  == Comment: #2 - SEETEENA THOUFEEK  - 2017-07-17 
02:10:52 ==
  Issue does not happen when running the same test with xfs file system. (ie, 
creating loop device with xfs file system).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1704730/+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 1696049] Comment bridged from LTC Bugzilla

--- Comment From hasri...@in.ibm.com 2017-09-20 23:24 EDT---
(In reply to comment #42)
> The test kernel can be downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1696049
>
> Can you test that kernel and report back if it has the bug or not?  I will
> build the next test kernel based on your test results.

Issue exists in this commit kernel.

Thanks,
Harish S

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

Title:
  xfstest sanity checks on seek operations fails

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  Fix Released

Bug description:
  == Comment: #0 - Harish Sriram 
  Issue:
  --
  xfstest fails with sanity checks on seek operations

  # uname -a
  Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 
12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Create a loop device with xfs filesystem
  2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd 
xfstests-dev
  3. make
  4. Create a local.config for running with created loop device
  5. Run xfstests-dev test  : ./check tests/generic/285 or ./check 
tests/generic/436

  The test 285 fails with following
  ...
  ...
  07. Test file with unwritten extents, only have dirty pages
  07.01 SEEK_HOLE expected 0 or 45056, got 0.   succ
  07.02 SEEK_HOLE expected 1 or 45056, got 1.   succ
  07.03 SEEK_DATA expected 40960 or 40960, got -1.  FAIL
  07.04 SEEK_DATA expected 40960 or 40960, got -1.  FAIL

  08. Test file with unwritten extents, only have unwritten pages
  08.01 SEEK_HOLE expected 0 or 45056, got 0.   succ
  08.02 SEEK_HOLE expected 1 or 45056, got 1.   succ
  08.03 SEEK_DATA expected 40960 or 40960, got -1.  FAIL
  08.04 SEEK_DATA expected 40960 or 40960, got -1.  FAIL

  The test 436 fails with 
  ...
  ...
  14. Test file with unwritten extents, small hole after pagevec dirty pages
  14.01 SEEK_HOLE expected 917504 or 4194304, got 3670016.  FAIL
  14.02 SEEK_HOLE expected 917504 or 4194304, got 3670016.  FAIL
  14.03 SEEK_HOLE expected 3670016 or 4194304, got 3670016. succ
  14.04 SEEK_DATA expected 0 or 0, got 0.   succ
  14.05 SEEK_DATA expected 1 or 1, got 1.   succ
  14.06 SEEK_DATA expected 2752512 or 2752512, got 2752512. succ

  seek sanity check failed!

  Full log is attached.

  == Comment: #6 - Harish Sriram

  commit 5375023ae1266553a7baa0845e82917d8803f48c
  Author: Jan Kara 
  Date:   Thu May 18 16:36:22 2017 -0700

  xfs: Fix missed holes in SEEK_HOLE implementation
  XFS SEEK_HOLE implementation could miss a hole in an unwritten extent as
  can be seen by the following command:
  
  xfs_io -c "falloc 0 256k" -c "pwrite 0 56k" -c "pwrite 128k 8k"
 -c "seek -h 0" file
  wrote 57344/57344 bytes at offset 0
  56 KiB, 14 ops; 0. sec (49.312 MiB/sec and 12623.9856 ops/sec)
  wrote 8192/8192 bytes at offset 131072
  8 KiB, 2 ops; 0. sec (70.383 MiB/sec and 18018.0180 ops/sec)
  Whence  Result
  HOLE139264
  
  Where we can see that hole at offset 56k was just ignored by SEEK_HOLE
  implementation. The bug is in xfs_find_get_desired_pgoff() which does
  not properly detect the case when pages are not contiguous.
  
  Fix the problem by properly detecting when found page has larger offset
  than expected.
  
  CC: sta...@vger.kernel.org
  Fixes: d126d43f631f996daeee5006714fed914be32368
  Signed-off-by: Jan Kara 
  Reviewed-by: Brian Foster 
  Reviewed-by: Darrick J. Wong 
  Signed-off-by: Darrick J. Wong 

  
  The above commit fixes the generic/436 test, but generic/285 still FAILS.

  The generic/285 failure is reproducible on most P8/P9 systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696049/+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 1707695] Re: radeon 0000:03:00.0: ring 0 stalled for more than 10000msec

2017-09-20 Thread Kai-Heng Feng

** Also affects: linux via
   https://bugs.freedesktop.org/show_bug.cgi?id=102909
   Importance: Unknown
   Status: Unknown

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

Title:
  radeon :03:00.0: ring 0 stalled for more than 1msec

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

Bug description:
  My system intermittently locks up every few days. It does not seem to
  correspond to a particular program or action.  When that happens, the
  screen goes to black, then returns after a few seconds. At that point,
  the time on the clock is static and indicates that the screen is
  frozen, but audio continues to play for 30 seconds to a minute. The
  keyboard and mouse do not affect what's being displayed, but I can Alt
  - SysRq - REISUB to restart.

  Every time (7 crashes and counting), /var/log/kern.log indicates that

  kernel: [353692.378886] radeon :03:00.0: ring 0 stalled for more than 
10280msec
  kernel: [353692.378896] radeon :03:00.0: GPU lockup (current fence id 
0x006e96e5 last fence id 0x006e96e9 on ring 0)

  just before the system locks. Different ring numbers are reported as
  stalling at different times.

  As per the instructions, I posted a question about this issue at:

  https://askubuntu.com/questions/937792/system-lockup-radeon-ring-
  stalled-for-more-than-10280msec?noredirect=1#comment1486875_937792

  but I have not received many responses.

  I'm running 16.04 LTS. 
  :~$ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  According to the Software Center, I am running Ubuntu Software 3.20.1.

  I have a Radeon HD graphics card.

  :~$ lspci | grep VGA
  03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cedar [Radeon HD 5000/6000/7350/8350 Series]

  :~$ lspci -v -s 03:00.0
  03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cedar [Radeon HD 5000/6000/7350/8350 Series] (prog-if 00 [VGA controller])
  Subsystem: Gigabyte Technology Co., Ltd Cedar [Radeon HD 5000/6000/7350/8350 
Series]
  Flags: bus master, fast devsel, latency 0, IRQ 53
  Memory at c000 (64-bit, prefetchable) [size=256M]
  Memory at d3d2 (64-bit, non-prefetchable) [size=128K]
  I/O ports at 7000 [size=256]
  Expansion ROM at d3d0 [disabled] [size=128K]
  Capabilities: 
  Kernel driver in use: radeon
  Kernel modules: radeon

  Please let me know if additional information would be useful, and I
  will be glad to provide it.  Thanks in advance.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-87-generic 4.4.0-87.110
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  clapp  3889 F pulseaudio
   /dev/snd/controlC2:  clapp  3889 F pulseaudio
   /dev/snd/controlC1:  clapp  3889 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 31 14:02:27 2017
  HibernationDevice: RESUME=UUID=1b30dad6-8c48-42cf-ae26-66ab8b0eb446
  InstallationDate: Installed on 2013-09-04 (1425 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: Dell Inc. Precision T7600
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic 
root=UUID=33722f76-37fd-4289-b071-d7f48b65dd32 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-87-generic N/A
   linux-backports-modules-4.4.0-87-generic  N/A
   linux-firmware1.157.11
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/03/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 082WXT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd05/03/2013:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn082WXT:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T7600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

Re: [Kernel-packages] [Bug 1589814] Re: zfs-dkms 0.6.5.6-0ubuntu9: zfs kernel module failed to build

2017-09-20 Thread Abram Daniel

Dear Mr. Laager,

Very sorry for this late reply, I just noticed while I am doing In-box
cleanup.

And you are very much correct, it is no longer an issue, but I wonder if
you have an answer for this line, it is no longer showing version
number, it just give a new line return.

$sudo dmesg | grep ZFS

$

Many thanks in advance

Regards,

Dani

On 10/03/2016 09:30 AM, Richard Laager wrote:
> This is clearly a bug, but 15.10 is EOL now. In 16.04+, the module is
> pre-built, so there is no more DKMS building.
>
> ** Changed in: zfs-linux (Ubuntu)
>Status: Confirmed => Invalid
>

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

Title:
  zfs-dkms 0.6.5.6-0ubuntu9: zfs kernel module failed to build

Status in zfs-linux package in Ubuntu:
  Invalid

Bug description:
  this summary was reported towards the end of upgrading ver. 15.10 to
  16.04lts.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zfs-dkms 0.6.5.6-0ubuntu9
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-22-generic (x86_64)
   Tue Jun  7 02:13:31 EDT 2016
   make: *** No targets specified and no makefile found.  Stop.
  DKMSKernelVersion: 4.4.0-22-generic
  Date: Tue Jun  7 02:14:10 2016
  InstallationDate: Installed on 2015-12-20 (169 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageVersion: 0.6.5.6-0ubuntu9
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.6.5.6-0ubuntu9: zfs kernel module failed to build
  UpgradeStatus: Upgraded to xenial on 2016-06-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1589814/+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 1670137] Re: cache on NVMe inhibits proper suspend/hibernate - zfs l2arc

2017-09-20 Thread Joseph Yasi

I've attached my workaround script. To use:

change the ZFSPOOLNAME variable in the script to the name of the zfspool with 
an NVMe L2ARC.
change the NVMEL2ARCPART to the name of the cache partition.

sudo cp zpool-offline-cache.sh /lib/systemd/system-sleep/
sudo chmod +x /lib/systemd/system-sleep/zpool-offline-cache.sh

** Attachment added: "L2ARC workaround sleep script"
   
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1670137/+attachment/4954099/+files/zpool-offline-cache.sh

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

Title:
  cache on NVMe inhibits proper suspend/hibernate - zfs l2arc

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  Please see: 2017-03-05 09:03  2017-03-05 14:03 UTCKernelOops  
linux-image-4.4.0-31-generic
https://errors.ubuntu.com/oops/7bb2122e-01b1-11e7-ba2a-fa163e839e11

  Running zfs [root] with l2arc cache enabled fails to suspend properly,
  screen goes blank but power stays on, when I disable the cache it
  works fine.  Unsure if this happens with non-root install of zfs, slog
  does not cause this problem.

  Linux mp 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016
  x86_64 x86_64 x86_64 GNU/Linux

  ii  zfs-initramfs  0.6.5.6-0ubuntu15  
 all  Native OpenZFS root filesystem 
capabilities for Linux
  ii  zfs-zed0.6.5.6-0ubuntu15  
 amd64OpenZFS Event Daemon (zed)
  ii  zfsutils-linux 0.6.5.6-0ubuntu15  
 amd64Native OpenZFS management utilities 
for Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1670137/+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 1646277] Re: Xenial server 16.04.x will have a black screen after PXE installation

2017-09-20 Thread NancyHsu

The bug existed in 4.2.0-16.
Reproduce step:
1. PXE install Ubuntu 16.04.3.
2. Downgrade kernel to 4.2.0-16.
3. The screen goes black after a reboot.

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

Title:
  Xenial server 16.04.x will have a black screen after PXE installation

Status in debian-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in debian-installer source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  The display will keep black screen after install 16.04.x via PXE(need
  use "Ctrl+Alt+F1" to change to terminal 1, then can see text mode
  screen)

  Quanta team is installing Xenial server using PXE boot.   After the
  installation, the console will show a black screen.   Hitting ctl-
  alt-f1 displays the text mode screen OK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1646277/+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 1717992] Re: Sound silently plays to "Dummy Output"

2017-09-20 Thread Carlos Eduardo Moreira dos Santos

Reboot in 4.10-0-33 and youtube is muted on Dummy Output. Tried VLC with
same results. The weird thing is that I could hear audio in 4.10.0-35 in
some occasions, with my device being correctly displayed in pavucontrol.
Suddenly, it had a Dummy Output again...

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

Title:
  Sound silently plays to "Dummy Output"

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Since upgrade to 4.10.0-35-generic in Ubuntu 17.04, the sound card is
  detected, but pavucontrol has only "Dummy Output". Bar animation shows
  audio is playing, but no sound is heard. alsamixer is working fine,
  but audio still can't be heard. Configuration tab says "No cards
  available for configuration".

  $ lspci -v
  0:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
Subsystem: Dell Device 0781
Flags: bus master, fast devsel, latency 32, IRQ 283
Memory at d5328000 (64-bit, non-prefetchable) [size=16K]
Memory at d530 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

  # aplay -L
  default
  Playback/recording through the PulseAudio sound server
  null
  Discard all samples (playback) or generate zero samples (capture)
  pulse
  PulseAudio Sound Server
  sysdefault:CARD=PCH
  HDA Intel PCH, ALC3246 Analog
  Default Audio Device
  front:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Front speakers
  surround21:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  2.1 Surround output to Front and Subwoofer speakers
  surround40:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  4.0 Surround output to Front and Rear speakers
  surround41:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  4.1 Surround output to Front, Rear and Subwoofer speakers
  surround50:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  5.0 Surround output to Front, Center and Rear speakers
  surround51:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  5.1 Surround output to Front, Center, Rear and Subwoofer speakers
  surround71:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
  hdmi:CARD=PCH,DEV=0
  HDA Intel PCH, HDMI 0
  HDMI Audio Output
  hdmi:CARD=PCH,DEV=1
  HDA Intel PCH, HDMI 1
  HDMI Audio Output
  hdmi:CARD=PCH,DEV=2
  HDA Intel PCH, HDMI 2
  HDMI Audio Output
  dmix:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct sample mixing device
  dmix:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct sample mixing device
  dmix:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct sample mixing device
  dmix:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct sample mixing device
  dsnoop:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct sample snooping device
  hw:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct hardware device without any conversions
  plughw:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Hardware device with all software conversions
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=0bcd17dc-d971-4048-8c1f-d2bb48e8a157
  InstallationDate: Installed on 2017-08-18 (31 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Inspiron 7460
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:

[Kernel-packages] [Bug 1716699] Re: linux: 4.13.0-11.12 -proposed tracker

The package has been published and the bug is being set to Fix Released


** Changed in: kernel-development-workflow/promote-to-release
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow
   Status: In Progress => Fix Released

** Description changed:

  This bug is for tracking the 4.13.0-11.12 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
+ kernel-phase:Released
+ kernel-phase-changed:Thursday, 21. September 2017 01:02 UTC

** Description changed:

  This bug is for tracking the 4.13.0-11.12 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
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-phase:Released
- kernel-phase-changed:Thursday, 21. September 2017 01:02 UTC

** Tags removed: 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/1716699

Title:
  linux: 4.13.0-11.12 -proposed tracker

Status in Kernel Development Workflow:
  Fix Released
Status in Kernel Development Workflow automated-testing series:
  Fix Released
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  Fix Released
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  This bug is for tracking the 4.13.0-11.12 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: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1716699/+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 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)

2017-09-20 Thread Caleb McKay

I'm running 17.10 with the latest patches and still have this bug. What
exactly was released that fixes 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/1653456

Title:
  ASUS G752VS: Touchpad and Fn keys not working (Ubuntu
  16.04.1/16.10/17.04)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Non-Optimus laptop ASUS G752VS-GC063D-CST256.
  17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 
NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 
802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 
x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS.

  Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and
  17.04, among other problems I found that touchpad and Fn keys (all
  except volume control) doesn't work on my brand new ASUS G752VS.

  It is very hard even to try Ubuntu 16.10 and 17.04 because of the
  missing mouse pointer. This problem must be related to a video driver
  because if after installing one is capable to install Nvidia drivers -
  problem is solved. This problem doesn't exist both while trying and
  installing Ubuntu 16.04.1!

  I'm currently on Windows 10, and this bug report is made from Ubuntu
  16.04.1 LiveCD.

  
  dmesg | grep -i elan
  [  101.082929] input: ELAN1203:00 04F3:3043 Touchpad as 
/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11
  [  101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID 
v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00

  
  xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ G-SPY USB Gaming Mouse  id=10   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=13   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=14   [slave  pointer 
 (2)]
  ⎜   ↳ ELAN1203:00 04F3:3043 Touchpad  id=15   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ G-SPY USB Gaming Mouse  id=9[slave  
keyboard (3)]
  ↳ USB2.0 HD UVC WebCamid=11   [slave  
keyboard (3)]
  ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=12   [slave  
keyboard (3)]
  ↳ Asus WMI hotkeysid=16   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=17   [slave  
keyboard (3)]

  cat /proc/bus/input/devices
  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: 
Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input4
  U: Uniq=
  H: Handlers=kbd event4 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0003 Vendor=04d9 Product=a070 Version=0110
  N: Name="G-SPY USB Gaming Mouse"
  P: Phys=usb-:00:14.0-2/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:04D9:A070.0001/input/input5
  U: Uniq=
  H: Handlers=sysrq kbd event5 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=e080ffdf01cf fffe
  B: MSC=10
  B: LED=1f

  I: Bus=0003 Vendor=04d9 Product=a070 Version=0110
  N: Name="G-SPY USB

[Kernel-packages] [Bug 1701137] Re: enable ARCH_SUNXI (and friends) in arm64 kernel .config

This bug was fixed in the package linux - 4.13.0-11.12

---
linux (4.13.0-11.12) artful; urgency=low

  * linux: 4.13.0-11.12 -proposed tracker (LP: #1716699)

  * kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: fix local TLB flushing vs. detach of an mm address space
- s390/mm: fix race on mm->context.flush_mm

  * CVE-2017-1000251
- Bluetooth: Properly check L2CAP config option output buffer length

 -- Seth Forshee   Tue, 12 Sep 2017 10:18:38
-0500

** Changed in: linux (Ubuntu Artful)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-1000251

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

Title:
  enable ARCH_SUNXI (and friends) in arm64 kernel .config

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

Bug description:
  The mainline support for the ARM64 Allwinner SoCs (featured on the Pine64 
boards and the Pinebook notebook, for instance, as well as other development 
boards like the BananaPi-M64) has come a long way by now, since 4.11 we have 
MMC and USB support working.
  Now can we just enable the proper .config bits to make the official Ubuntu 
kernel support those boards? The latest mainline U-Boot can load an EFI grub 
from some UEFI ESP partition, so any standard EFI installer should work.
  Apart from some minor hiccup (a missing MBR bootable flag/MBR at all) this 
works already with the Debian-testing netinst installer.
  The config symbols needed for decent support are (all enabled by the latest 
Debian kernel and the official mainline defconfig):
  ARCH_SUNXI=y
  CONFIG_USB_MUSB_SUNXI=m
  CONFIG_MMC_SUNXI=m
  CONFIG_RTC_DRV_SUN6I=y
  CONFIG_PHY_SUN4I_USB=y

  Those enable MMC and USB (the mandatory clocks, pinctrl and UART are enabled 
by default) and make those boards quite usable already. The on-SoC Ethernet 
driver will probably be merged into 4.13-rc1.
  Optionally:
  CONFIG_I2C_MV64XXX=m
  CONFIG_SPI_SUN6I=m
  give us I2C and SPI support as well.

  So can we add those symbols to the Ubuntu kernel .config to give users
  an out-of-the-box experience?

  Cheers,
  Andre.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701137/+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 1713103] Re: snapd 2.27.3+17.10 ADT test failure with linux 4.13.0-6.7

This bug was fixed in the package linux - 4.13.0-11.12

---
linux (4.13.0-11.12) artful; urgency=low

  * linux: 4.13.0-11.12 -proposed tracker (LP: #1716699)

  * kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: fix local TLB flushing vs. detach of an mm address space
- s390/mm: fix race on mm->context.flush_mm

  * CVE-2017-1000251
- Bluetooth: Properly check L2CAP config option output buffer length

 -- Seth Forshee   Tue, 12 Sep 2017 10:18:38
-0500

** Changed in: linux (Ubuntu)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-1000251

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

Title:
  snapd 2.27.3+17.10 ADT test failure with linux 4.13.0-6.7

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/s/snapd/20170825_154928_33cfc@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/i386/s/snapd/20170825_150258_33cfc@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/s/snapd/20170825_141201_33cfc@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713103/+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 1703339] Re: Unable to install Ubuntu on the NVMe disk under VMD PCI domain

This bug was fixed in the package linux - 4.13.0-11.12

---
linux (4.13.0-11.12) artful; urgency=low

  * linux: 4.13.0-11.12 -proposed tracker (LP: #1716699)

  * kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: fix local TLB flushing vs. detach of an mm address space
- s390/mm: fix race on mm->context.flush_mm

  * CVE-2017-1000251
- Bluetooth: Properly check L2CAP config option output buffer length

 -- Seth Forshee   Tue, 12 Sep 2017 10:18:38
-0500

** Changed in: linux (Ubuntu Artful)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-1000251

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

Title:
  Unable to install Ubuntu on the NVMe disk under VMD PCI domain

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

Bug description:
  It is not possible to install Ubuntu on the NVMe disk under VMD
  (Volume Management Device) PCI domain. The disk is not visible in the
  installer because VMD module is not available at this stage.

  I'm raising it against kernel package as I have impression VMD module
  must be included in linux-image dpkg package, not linux-image-extra.

  Please also assure VMD module gets included in initramfs by installer
  (if necessary).

  For more information about VMD please see bug 1591806.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-generic 4.10.0.26.28
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   tomasz 1659 F...m pulseaudio
   /dev/snd/controlC0:  tomasz 1659 F pulseaudio
   /dev/snd/timer:  tomasz 1659 f pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jul 10 10:40:20 2017
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2017-07-06 (3 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170702)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=/dev/mapper/hostname--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.167
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703339/+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 1714571] Re: [P9, POwer NV] Perf PMU event : pm_br_2path and pm_ld_miss_l1 is counted twice when perf stat is done (perf:)

This bug was fixed in the package linux - 4.13.0-11.12

---
linux (4.13.0-11.12) artful; urgency=low

  * linux: 4.13.0-11.12 -proposed tracker (LP: #1716699)

  * kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: fix local TLB flushing vs. detach of an mm address space
- s390/mm: fix race on mm->context.flush_mm

  * CVE-2017-1000251
- Bluetooth: Properly check L2CAP config option output buffer length

 -- Seth Forshee   Tue, 12 Sep 2017 10:18:38
-0500

** Changed in: linux (Ubuntu)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-1000251

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

Title:
  [P9,POwer NV] Perf PMU event : pm_br_2path and pm_ld_miss_l1 is
  counted twice when perf stat is done (perf:)

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Sukadev Bhattiprolu  - 2017-09-01 12:56:47 ==

  ---Problem Description---
  Problem description :
  =
  Perf PMU event : pm_br_2path and pm_ld_miss_l1 is counted twice , it is 
because two raw point to the same name.

  [ 
  
{,  
  
  "EventCode": "0x20036",   
  
  "EventName": "PM_BR_2PATH",   
  
  "BriefDescription": "Branches that are not strongly biased",  
  
  "PublicDescription": ""   
  
},  
  
{,  
  
  "EventCode": "0x40036",   
  
  "EventName": "PM_BR_2PATH",   
  
  "BriefDescription": "Branches that are not strongly biased",  
  
  "PublicDescription": ""   
  
},

  
  Ex :
  ===

  [root@zzfp189p1 ~]#  perf stat -e pm_br_2path sleep 1

   Performance counter stats for 'sleep 1':

  30,163  pm_br_2path   
  
 pm_br_2path   
(0.00%)

 1.002046416 seconds time elapsed

  [root@zzfp189p1 ~]# perf stat -e pm_ld_miss_l1 sleep 1

   Performance counter stats for 'sleep 1':

   9,217  pm_ld_miss_l1 
  
 pm_ld_miss_l1 
(0.00%)

 1.001956110 seconds time elapsed

  
  ---Steps to Reproduce---
   Steps to reproduce :
  
  1. Install perf (linux-tools)
  2. Run
  perf stat -e pm_ld_miss_l1 sleep 1
  perf stat -e pm_br_2path sleep 1

  
  == Comment: #1 - Sukadev Bhattiprolu  - 2017-09-01 12:58:16 ==
  The fix for this bug was pulled into Arnaldo's tree:

  
https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git/commit/?h=perf/core=828e291e2982a7c10a62aa32195d0cb501cedaae

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

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

This bug was fixed in the package linux - 4.13.0-11.12

---
linux (4.13.0-11.12) artful; urgency=low

  * linux: 4.13.0-11.12 -proposed tracker (LP: #1716699)

  * kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: fix local TLB flushing vs. detach of an mm address space
- s390/mm: fix race on mm->context.flush_mm

  * CVE-2017-1000251
- Bluetooth: Properly check L2CAP config option output buffer length

 -- Seth Forshee   Tue, 12 Sep 2017 10:18:38
-0500

** Changed in: linux (Ubuntu Artful)
   Status: Confirmed => Fix Released

** CVE added: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-1000251

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

Title:
  linux: 4.13.0-10.11 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Confirmed
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  This bug is for tracking the 4.13.0-10.11 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-development-workflow/+bug/1716287/+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 1716093] Re: please add aufs-dkms to the Provides: for the kernel packages

This bug was fixed in the package linux - 4.13.0-11.12

---
linux (4.13.0-11.12) artful; urgency=low

  * linux: 4.13.0-11.12 -proposed tracker (LP: #1716699)

  * kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: fix local TLB flushing vs. detach of an mm address space
- s390/mm: fix race on mm->context.flush_mm

  * CVE-2017-1000251
- Bluetooth: Properly check L2CAP config option output buffer length

 -- Seth Forshee   Tue, 12 Sep 2017 10:18:38
-0500

** Changed in: linux (Ubuntu)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-1000251

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

Title:
  please add aufs-dkms to the Provides: for the kernel packages

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  The fsprotect package is currently stuck in artful-proposed because it
  depends on aufs-dkms.  This does not exist in Ubuntu, because aufs is
  included in the main kernel package.  Please add aufs-dkms to the
  Provides: of the linux-image packages so that this package will be
  installable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716093/+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 1715073] Re: SRIOV: warning if unload VFs

This bug was fixed in the package linux - 4.13.0-11.12

---
linux (4.13.0-11.12) artful; urgency=low

  * linux: 4.13.0-11.12 -proposed tracker (LP: #1716699)

  * kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: fix local TLB flushing vs. detach of an mm address space
- s390/mm: fix race on mm->context.flush_mm

  * CVE-2017-1000251
- Bluetooth: Properly check L2CAP config option output buffer length

 -- Seth Forshee   Tue, 12 Sep 2017 10:18:38
-0500

** Changed in: linux (Ubuntu Artful)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-1000251

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

Title:
  SRIOV: warning if unload VFs

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Released

Bug description:
  == Comment: #0 - Carol L. Soto  - 2017-02-23 16:11:47 ==
  ---Problem Description---
  When doing SRIOV if I unload VFs will see a warning:

  Feb 23 16:05:56 powerio-le11 kernel: [  201.343397] 
mlx5_3:wait_for_async_commands:674:(pid 6272): done with all pending requests
  Feb 23 16:05:56 powerio-le11 kernel: [  201.603999] iommu: Removing device 
0004:01:00.2 from group 7
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604078] pci 0004:01: 0.2: [PE# 
00] Removing DMA window #0
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604084] pci 0004:01: 0.2: [PE# 
00] Disabling 64-bit DMA bypass
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604350] mlx5_core 0004:01:00.0: 
VF BAR0: [mem 0x2400-0x2401 64bit pref] shifted to [mem 
0x2400-0x2401 64bit pref] (Disabling 1 VFs shifted by 0)
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604363] mlx5_core 0004:01:00.0: 
can't update enabled VF BAR0 [mem 0x2400-0x2401 64bit pref]
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604379] [ cut here 
]
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604386] WARNING: CPU: 14 PID: 
6272 at /build/linux-twbIHf/linux-4.10.0/drivers/pci/iov.c:584 
pci_iov_update_resource+0x178/0x1d0
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604388] Modules linked in: 
mlx5_ib 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 kvm_hv kvm_pr kvm 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bridge stp 
llc binfmt_misc ipmi_powernv ipmi_devintf uio_pdrv_genirq ipmi_msghandler uio 
vmx_crypto powernv_rng powernv_op_panel leds_powernv ibmpowernv ib_iser rdma_cm 
iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi knem(OE) ip_tables x_tables autofs4 btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear mlx4_en ses enclosure scsi_transport_sas 
crc32c_vpmsum mlx5_core mlx4_core
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604451]  tg3 ipr devlink
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604456] CPU: 14 PID: 6272 Comm: 
bash Tainted: G   OE   4.10.0-8-generic #10-Ubuntu
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604457] task: c00f40a6d600 
task.stack: c00f40ac8000
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604459] NIP: c06721b8 LR: 
c06721b4 CTR: 
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604461] REGS: c00f40acb590 
TRAP: 0700   Tainted: G   OE(4.10.0-8-generic)
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604462] MSR: 9282b033 

  Feb 23 16:05:56 powerio-le11 kernel: [  201.604470]   CR: 42424422  XER: 
2000
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] CFAR: c0b49db4 
SOFTE: 1
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR00: c06721b4 
c00f40acb810 c143c900 0063
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR04: 0001 
0539 c01fff70 00021a50
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR08: 0007 
0007 0001 656d5b2030524142
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR12: 4400 
cfb87e00 10180df8 10189e60
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR16: 10189ed8 
c00fdd0a2400 c01fff97d180 c0d46268
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR20: c0d4e410 
c0d41df8 c01fff97d190 c0d4d8d8
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR24: c0d4d8e0

[Kernel-packages] [Bug 1715145] Re: linux: 4.13.0-9.10 -proposed tracker

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

This bug was fixed in the package linux - 4.13.0-11.12

---
linux (4.13.0-11.12) artful; urgency=low

  * linux: 4.13.0-11.12 -proposed tracker (LP: #1716699)

  * kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: fix local TLB flushing vs. detach of an mm address space
- s390/mm: fix race on mm->context.flush_mm

  * CVE-2017-1000251
- Bluetooth: Properly check L2CAP config option output buffer length

 -- Seth Forshee   Tue, 12 Sep 2017 10:18:38
-0500

** Changed in: linux (Ubuntu Artful)
   Status: Confirmed => Fix Released

** CVE added: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-1000251

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

Title:
  linux: 4.13.0-9.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  This bug is for tracking the 4.13.0-9.10 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-phase:Packaging
  kernel-phase-changed:Tuesday, 05. September 2017 13:00 UTC

  -- swm properties --
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1715145/+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 1715064] Re: 17.10 fails to boot on POWER9 DD2.0 with Deep stop states

This bug was fixed in the package linux - 4.13.0-11.12

---
linux (4.13.0-11.12) artful; urgency=low

  * linux: 4.13.0-11.12 -proposed tracker (LP: #1716699)

  * kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: fix local TLB flushing vs. detach of an mm address space
- s390/mm: fix race on mm->context.flush_mm

  * CVE-2017-1000251
- Bluetooth: Properly check L2CAP config option output buffer length

 -- Seth Forshee   Tue, 12 Sep 2017 10:18:38
-0500

** Changed in: linux (Ubuntu Artful)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-1000251

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

Title:
  17.10 fails to boot on POWER9 DD2.0 with Deep stop states

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  == Comment: #0 - Ranjal G. Shenoy
  On Boston DD2.0 system, where deep stop states such as stop4 are enabled, the 
17.10 kernel Ubuntu-4.12.0-12.13 fails to boot.

  It requires the following upstream fixes to be backported.

  1) commit 5f221c3ca13d ("powerpc/powernv/idle: Correctly initialize 
core_idle_state_ptr")
  2) commit ec4867355244 ("powerpc/powernv/idle: Decouple Timebase restore & 
Per-core SPRs restore")
  3) commit cb0be7ec0307 ("powerpc/powernv/idle: Restore LPCR on wakeup from 
deep-stop")
  4) commit 1e1601b38e6e ("powerpc/powernv/idle: Restore SPRs for deep idle 
states via stop API.")
  5) commit 22c6663dc69a ("powerpc/powernv/idle: Use Requested Level for 
restoring state on P9 DD1")
  6) commit f9122ee4f558 ("cpuidle-powernv: Allow Deep stop states that don't 
stop time")
  7) commit 785a12afdb4a ("powerpc/powernv/idle: Disable LOSE_FULL_CONTEXT 
states when stop-api fails")
  8) commit e1c1cfed5432 ("powerpc/powernv: Save/Restore additional SPRs for 
stop4 cpuidle")
  9) commit 24be85a23d1f ("powerpc/powernv: Clear PECE1 in LPCR via stop-api 
only on Hotplug")
  10) https://patchwork.ozlabs.org/patch/808233/ ("powerpc/powernv: Clear 
LPCR[PECE1] via stop-api only for deep state offline")

  Of these 1-7 are in Linux Kernel 4.13. 8 and 9 are in
  powerpc/linux.git -next branch. and 10) is posted upstream which fixes
  9).

  These patches have been backported on top of  Ubuntu-4.12.0-12.13 and
  tested on Boston where they are working as expected.

  == Comment: #1 - Ranjal G. Shenoy 
 
  The lower 8 bits of core_idle_state_ptr tracks the number of non-idle
  threads in the core. This is supposed to be initialized to bit-map
  corresponding to the threads_per_core. However, currently it is
  initialized to PNV_CORE_IDLE_THREAD_BITS (0xFF). This is correct for
  POWER8 which has 8 threads per core, but not for POWER9 which has 4
  threads per core.
  
  As a result, on POWER9, core_idle_state_ptr gets initialized to
  0xFF. In case when all the threads of the core are idle, the bits
  corresponding tracking the idle-threads are non-zero. As a result, the
  idle entry/exit code fails to save/restore per-core hypervisor state
  since it assumes that there are threads in the cores which are still
  active.
  
  Fix this by correctly initializing the lower bits of the
  core_idle_state_ptr on the basis of threads_per_core.
  
  Cherry-picked from commit 5f221c3ca13d ("powerpc/powernv/idle:
  Correctly initialize core_idle_state_ptr")

  == Comment: #2 - Ranjal G. Shenoy 
 On POWER8, in case of
 -  nap: both timebase and hypervisor state is retained.
 -  fast-sleep: timebase is lost. But the hypervisor state is retained.
 -  winkle: timebase and hypervisor state is lost.
  
  Hence, the current code for handling exit from a idle state assumes
  that if the timebase value is retained, then so is the hypervisor
  state. Thus, the current code doesn't restore per-core hypervisor
  state in such cases.
  
  But that is no longer the case on POWER9 where we do have stop states
  in which timebase value is retained, but the hypervisor state is
  lost. So we have to ensure that the per-core hypervisor state gets
  restored in such cases.
  
  Fix this by ensuring that even in the case when timebase is retained,
  we explicitly check if we are waking up from a deep stop that loses
  per-core hypervisor state (indicated by cr4 being eq or gt), and if
  this is the case, we restore the per-core hypervisor state.
  
  Cherry-picked from commit ec4867355244 ("powerpc/powernv/idle:
  Decouple Timebase restore & Per-core SPRs restore")

  == Comment: #3 - Ranjal G. Shenoy 
 On wakeup from a deep stop state which is

[Kernel-packages] [Bug 1715578] Re: [Patch] network-i40e:NVM bug fixes (cherrypick from 4.14)

This bug was fixed in the package linux - 4.13.0-11.12

---
linux (4.13.0-11.12) artful; urgency=low

  * linux: 4.13.0-11.12 -proposed tracker (LP: #1716699)

  * kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: fix local TLB flushing vs. detach of an mm address space
- s390/mm: fix race on mm->context.flush_mm

  * CVE-2017-1000251
- Bluetooth: Properly check L2CAP config option output buffer length

 -- Seth Forshee   Tue, 12 Sep 2017 10:18:38
-0500

** Changed in: linux (Ubuntu)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-1000251

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

Title:
  [Patch] network-i40e:NVM bug fixes (cherrypick from 4.14)

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:
  Theses two commits need to be cherrypicked from upstream to 4.12/4.13 and 
integrated into 17.10

  Target Kernel: 4.14
  Target Release: 17.10

  Action: Cherrypick

  Here are the two commit id's:
  
  commit 3c8f3e96af3a6799841761923d000566645f0942
  Author: Jacob Keller 
  Date:   Fri Sep 1 13:43:08 2017 -0700
  
  i40e: point wb_desc at the nvm_wb_desc during i40e_read_nvm_aq
  
  When introducing the functions to read the NVM through the AdminQ,
  we
  did not correctly mark the wb_desc.
  
  Fixes: 7073f46e443e ("i40e: Add AQ commands for NVM Update for
  X722", 2015-06-05)
  Signed-off-by: Jacob Keller 
  Tested-by: Andrew Bowers 
  Signed-off-by: Jeff Kirsher 
  
  commit 09f79fd49d94cda5837e9bfd0cb32b3b6d9f
  Author: Anjali Singhai Jain 
  Date:   Fri Sep 1 13:42:49 2017 -0700
  
  i40e: avoid NVM acquire deadlock during NVM update
  
  X722 devices use the AdminQ to access the NVM, and this requires
  taking
  the AdminQ lock. Because of this, we lock the AdminQ during
  i40e_read_nvm(), which is also called in places where the lock is
  already held, such as the firmware update path which wants to lock
  once
  and then unlock when finished after performing several tasks.
  
  Although this should have only affected X722 devices, commit
  96a39aed25e6 ("i40e: Acquire NVM lock before reads on all devices",
  2016-12-02) added locking for all NVM reads, regardless of device
  family.
  
  This resulted in us accidentally causing NVM acquire timeouts on
  all
  devices, causing failed firmware updates which left the eeprom in
  a corrupt state.
  
  Create unsafe non-locked variants of i40e_read_nvm_word and
  i40e_read_nvm_buffer, __i40e_read_nvm_word and
  __i40e_read_nvm_buffer
  respectively. These variants will not take the NVM lock and are
  expected
  to only be called in places where the NVM lock is already held if
  needed.
  
  Since the only caller of i40e_read_nvm_buffer() was in such a path,
  remove it entirely in favor of the unsafe version. If necessary we
  can
  always add it back in the future.
  
  Additionally, we now need to hold the NVM lock in
  i40e_validate_checksum
  because the call to i40e_calc_nvm_checksum now assumes that the NVM
  lock
  is held. We can further move the call to read
  I40E_SR_SW_CHECKSUM_WORD
  up a bit so that we do not need to acquire the NVM lock twice.
  
  This should resolve firmware updates and also fix potential raise
  that
  could have caused the driver to report an invalid NVM checksum upon
  driver load.
  
  Reported-by: Stefan Assmann 
  Fixes: 96a39aed25e6 ("i40e: Acquire NVM lock before reads on all
  devices", 2016-12-02)
  Signed-off-by: Anjali Singhai Jain 
  Signed-off-by: Jacob Keller 
  Tested-by: Andrew Bowers 
  Signed-off-by: Jeff Kirsher 

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1715578/+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 1716284] Re: Artful update to v4.13.1 stable release

This bug was fixed in the package linux - 4.13.0-11.12

---
linux (4.13.0-11.12) artful; urgency=low

  * linux: 4.13.0-11.12 -proposed tracker (LP: #1716699)

  * kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: fix local TLB flushing vs. detach of an mm address space
- s390/mm: fix race on mm->context.flush_mm

  * CVE-2017-1000251
- Bluetooth: Properly check L2CAP config option output buffer length

 -- Seth Forshee   Tue, 12 Sep 2017 10:18:38
-0500

** Changed in: linux (Ubuntu Artful)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-1000251

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

Title:
  Artful update to v4.13.1 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The v4.13.1 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the v4.13.1 stable release shall be
  applied:

  usb: quirks: add delay init quirk for Corsair Strafe RGB keyboard
  USB: serial: option: add support for D-Link DWM-157 C1
  usb: Add device quirk for Logitech HD Pro Webcam C920-C
  usb:xhci:Fix regression when ATI chipsets detected
  USB: musb: fix external abort on suspend
  ANDROID: binder: add padding to binder_fd_array_object.
  ANDROID: binder: add hwbinder,vndbinder to BINDER_DEVICES.
  USB: core: Avoid race of async_completed() w/ usbdev_release()
  staging/rts5208: fix incorrect shift to extract upper nybble
  staging: ccree: save ciphertext for CTS IV
  staging: fsl-dpaa2/eth: fix off-by-one FD ctrl bitmaks
  iio: adc: ti-ads1015: fix incorrect data rate setting update
  iio: adc: ti-ads1015: fix scale information for ADS1115
  iio: adc: ti-ads1015: enable conversion when CONFIG_PM is not set
  iio: adc: ti-ads1015: avoid getting stale result after runtime resume
  iio: adc: ti-ads1015: don't return invalid value from buffer setup callbacks
  iio: adc: ti-ads1015: add adequate wait time to get correct conversion
  driver core: bus: Fix a potential double free
  HID: wacom: Do not completely map WACOM_HID_WD_TOUCHRINGSTATUS usage
  binder: free memory on error
  crypto: caam/qi - fix compilation with CONFIG_DEBUG_FORCE_WEAK_PER_CPU=y
  crypto: caam/qi - fix compilation with DEBUG enabled
  thunderbolt: Fix reset response_type
  fpga: altera-hps2fpga: fix multiple init of l3_remap_lock
  intel_th: pci: Add Cannon Lake PCH-H support
  intel_th: pci: Add Cannon Lake PCH-LP support
  ath10k: fix memory leak in rx ring buffer allocation
  drm/vgem: Pin our pages for dmabuf exports
  drm/ttm: Fix accounting error when fail to get pages for pool
  drm/dp/mst: Handle errors from drm_atomic_get_private_obj_state() correctly
  rtlwifi: rtl_pci_probe: Fix fail path of _rtl_pci_find_adapter
  Bluetooth: Add support of 13d3:3494 RTL8723BE device
  iwlwifi: pci: add new PCI ID for 7265D
  dlm: avoid double-free on error path in dlm_device_{register,unregister}
  mwifiex: correct channel stat buffer overflows
  MCB: add support for SC31 to mcb-lpc
  s390/mm: avoid empty zero pages for KVM guests to avoid postcopy hangs
  drm/nouveau/pci/msi: disable MSI on big-endian platforms by default
  drm/nouveau: Fix error handling in nv50_disp_atomic_commit
  workqueue: Fix flag collision
  ahci: don't use MSI for devices with the silly Intel NVMe remapping scheme
  cs5536: add support for IDE controller variant
  scsi: sg: protect against races between mmap() and SG_SET_RESERVED_SIZE
  scsi: sg: recheck MMAP_IO request length with lock held
  of/device: Prevent buffer overflow in of_device_modalias()
  rtlwifi: Fix memory leak when firmware request fails
  rtlwifi: Fix fallback firmware loading
  Linux 4.13.1

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

This bug was fixed in the package linux - 4.13.0-11.12

---
linux (4.13.0-11.12) artful; urgency=low

  * linux: 4.13.0-11.12 -proposed tracker (LP: #1716699)

  * kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: fix local TLB flushing vs. detach of an mm address space
- s390/mm: fix race on mm->context.flush_mm

  * CVE-2017-1000251
- Bluetooth: Properly check L2CAP config option output buffer length

 -- Seth Forshee   Tue, 12 Sep 2017 10:18:38
-0500

** Changed in: linux (Ubuntu Artful)
   Status: Confirmed => Fix Released

** CVE added: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-1000251

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

Title:
  linux: 4.13.0-11.12 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  Confirmed
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  This bug is for tracking the 4.13.0-11.12 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-development-workflow/+bug/1716699/+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 1716843] Re: [bug] 17.10: CDP test fail on platform of Purley-2S/4S/Neoncity, BDW-de/ep/ex,

2017-09-20 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  [bug] 17.10: CDP test fail on platform of Purley-2S/4S/Neoncity,BDW-
  de/ep/ex,

Status in intel:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  Description:

  CQM2(CMT/MBM rework) upstream patchset has been merged into upstream in 
4.14-rc1.
  And the patch 5dc1d5c6bac2 (“x86/intel_rdt: Simplify info and base file 
lists”) fixed this issue by the way in another way with rework.
  This issue will not happen on 4.14-rc kernel.

  
  Target Release: 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1716843/+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 1718149] Re: linux: 4.4.0-97.120 -proposed tracker

** Changed in: kernel-sru-workflow/security-signoff
   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/1718149

Title:
  linux: 4.4.0-97.120 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
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 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: 1718150,1718151
  derivatives: 1718153,1718154,1718155,1718156,1718157
  -- 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/1718149/+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 1718143] Re: linux: 4.10.0-36.40 -proposed tracker

** Changed in: kernel-sru-workflow/security-signoff
   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/1718143

Title:
  linux: 4.10.0-36.40 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
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 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 Zesty:
  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: 1718145,1718146
  derivatives: 1718147
  -- 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/1718143/+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 1591609] Re: [Feature]Memory Bandwidth Monitoring(MBM) port to new Cache Quality Monitoring (CQM)

** Information type changed from Proprietary to Public

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

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

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

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

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

Title:
  [Feature]Memory Bandwidth Monitoring(MBM) port to new Cache Quality
  Monitoring (CQM)

Status in intel:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  Google has sent a new cqm patch with a lot of fixes to the existing
  cqm which is upstream. The MBM was based on the old cqm and now needs
  to be ported on top of the new version of cqm. The google patch is
  enormous and hence mbm requires a lot of changes to work on top of it.
  However This wont impact the openstack usage of cqm/mbm as the name of
  the events would still be the same and they can just be used like
  before - only that there may be some features which wernt working will
  work now.

  Platform:  BDW-EP or BDW-EX

  upstream schedule: 4.13 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1591609/+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 1712031] Re: [Feature] PXE boot with Intel Omni-Path

** Changed in: linux-firmware (Ubuntu)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  [Feature] PXE boot with Intel Omni-Path

Status in intel:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Triaged

Bug description:
  Description:

  This is about ability to PXE boot over Intel Fabric.
  Netboot initrd is missing infiniband kernel stack along with hfi1.ko (for 1st 
generation of Intel Omni-Path cards). In addition some firmware files required 
to load modules are also missing in initrd. This firmware came from existing 
linux-firmware package, but is not included in netboot initrd image.

  Add Intel Omni-Path Architecture (OPA) Firmware to initrd.gz

  The initrd.gz supplied on Ubuntu 17.04 is missing
  the following firmware listed below in the /lib/firmware directory.
  As a result, PXE boot over fabric fails.

  hfi1_dc8051.fw
  hfi1_fabric.fw
  hfi1_pcie.fw
  hfi1_sbus.fw

  Target Release: 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1712031/+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 1718548] Re: ubuntu-fan autopkgtests are broken against systemd-resolved

2017-09-20 Thread Steve Langasek

Attached is the partial patch, which should also provide insight into
how to fix the docker test.

** Patch added: "ubuntu-fan-resolved.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1718548/+attachment/4954044/+files/ubuntu-fan-resolved.debdiff

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

Title:
  ubuntu-fan autopkgtests are broken against systemd-resolved

Status in ubuntu-fan package in Ubuntu:
  New

Bug description:
  Now that 17.10 has migrated to netplan+systemd-networkd+systemd-
  resolved by default, ubuntu-fan autopkgtests are failing; at least one
  reason for this failure is wrong detection of the default network
  interface because autopkgtest environments appear for some reason to
  be getting multiple default routes:

  autopkgtest [20:14:59]: test lxd: [---
  Error: either "dev" is duplicate, or "ens2" is a garbage.
  II: Auto-init LXD...
  LXD has been successfully configured.
  II: Creating Fan Bridge...
  /usr/sbin/fanatic: .0.0/16: unknown underlay network format
  FAIL: Error on enable-fan
  autopkgtest [20:15:10]: test lxd: ---]

  
(https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/amd64/u/ubuntu-
  fan/20170916_203221_4f037@/log.gz)

  The other part failure appears to be a race with systemd-resolved in
  setting up the network inside of docker containers:

  autopkgtest [17:25:39]: test docker: [---
  Running in the Canonical CI environment
  II: Auto-create Fan Bridge...
  configuring fan underlay:10.220.0.0/16 overlay:250.0.0.0/8
  II: Create docker Fan Network...
  configuring docker for underlay:10.220.0.0/16 overlay:250.0.0.0/8 (fan-250 
250.4
  6.84.0/24)
  1c8a03aa50ab88b997c3b3aee88bfa6933b14368f1594db4a800c2ae8d62074f
  II: Test docker...
  local docker test: pulling container images ...
  Using default tag: latest
  latest: Pulling from library/ubuntu
  d5c6f90da05d: Pulling fs layer
  [...]
  2b8db33536d4: Pull complete
  Digest: 
sha256:2b9285d3e340ae9d4297f83fed6a9563493945935fc787e98cc32a69f5687641
  Status: Downloaded newer image for ubuntu:latest
  local docker test: creating test container ...
  5cbdd232b71bc0738f27f1fa3eae4360716bfe3f8cea976874bf6309b1843169
   slave: installing ping ...
  W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease  
Temporary failure resolving 'archive.ubuntu.com'
  [...]
  E: Unable to locate package iputils-ping
   slave: installing nc ...
  E: Unable to locate package netcat-openbsd
  test master: ping test (250.46.84.2) ...
  test slave: ping test (250.46.84.1) ...
  test slave: ping test ... FAIL
  --- transcript start ---
  /bin/sh: 108: ping: not found
  --- transcript end ---
  test slave: short data test (250.46.84.2 -> 250.46.84.1) ...
  test master: ping test ... PASS
  test master: short data test (250.46.84.1 -> 250.46.84.2) ...
  autopkgtest [20:12:19]: ERROR: timed out on command [...]

  I've reproduced this problem locally and prepared a partial patch
  based on a similar fix to the docker.io package's autopkgtests - but
  so far this only fixes races in the lxd test, not in the docker test,
  so it needs further investigation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1718548/+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 1716843] Re: [bug] 17.10: CDP test fail on platform of Purley-2S/4S/Neoncity, BDW-de/ep/ex,

** Information type changed from Proprietary to Public

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

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

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

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

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  [bug] 17.10: CDP test fail on platform of Purley-2S/4S/Neoncity,BDW-
  de/ep/ex,

Status in intel:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  Description:

  CQM2(CMT/MBM rework) upstream patchset has been merged into upstream in 
4.14-rc1.
  And the patch 5dc1d5c6bac2 (“x86/intel_rdt: Simplify info and base file 
lists”) fixed this issue by the way in another way with rework.
  This issue will not happen on 4.14-rc kernel.

  
  Target Release: 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1716843/+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 1718548] [NEW] ubuntu-fan autopkgtests are broken against systemd-resolved

2017-09-20 Thread Steve Langasek

Public bug reported:

Now that 17.10 has migrated to netplan+systemd-networkd+systemd-resolved
by default, ubuntu-fan autopkgtests are failing; at least one reason for
this failure is wrong detection of the default network interface because
autopkgtest environments appear for some reason to be getting multiple
default routes:

autopkgtest [20:14:59]: test lxd: [---
Error: either "dev" is duplicate, or "ens2" is a garbage.
II: Auto-init LXD...
LXD has been successfully configured.
II: Creating Fan Bridge...
/usr/sbin/fanatic: .0.0/16: unknown underlay network format
FAIL: Error on enable-fan
autopkgtest [20:15:10]: test lxd: ---]

(https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-artful/artful/amd64/u/ubuntu-
fan/20170916_203221_4f037@/log.gz)

The other part failure appears to be a race with systemd-resolved in
setting up the network inside of docker containers:

autopkgtest [17:25:39]: test docker: [---
Running in the Canonical CI environment
II: Auto-create Fan Bridge...
configuring fan underlay:10.220.0.0/16 overlay:250.0.0.0/8
II: Create docker Fan Network...
configuring docker for underlay:10.220.0.0/16 overlay:250.0.0.0/8 (fan-250 250.4
6.84.0/24)
1c8a03aa50ab88b997c3b3aee88bfa6933b14368f1594db4a800c2ae8d62074f
II: Test docker...
local docker test: pulling container images ...
Using default tag: latest
latest: Pulling from library/ubuntu
d5c6f90da05d: Pulling fs layer
[...]
2b8db33536d4: Pull complete
Digest: sha256:2b9285d3e340ae9d4297f83fed6a9563493945935fc787e98cc32a69f5687641
Status: Downloaded newer image for ubuntu:latest
local docker test: creating test container ...
5cbdd232b71bc0738f27f1fa3eae4360716bfe3f8cea976874bf6309b1843169
 slave: installing ping ...
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease  
Temporary failure resolving 'archive.ubuntu.com'
[...]
E: Unable to locate package iputils-ping
 slave: installing nc ...
E: Unable to locate package netcat-openbsd
test master: ping test (250.46.84.2) ...
test slave: ping test (250.46.84.1) ...
test slave: ping test ... FAIL
--- transcript start ---
/bin/sh: 108: ping: not found
--- transcript end ---
test slave: short data test (250.46.84.2 -> 250.46.84.1) ...
test master: ping test ... PASS
test master: short data test (250.46.84.1 -> 250.46.84.2) ...
autopkgtest [20:12:19]: ERROR: timed out on command [...]

I've reproduced this problem locally and prepared a partial patch based
on a similar fix to the docker.io package's autopkgtests - but so far
this only fixes races in the lxd test, not in the docker test, so it
needs further investigation.

** Affects: ubuntu-fan (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  ubuntu-fan autopkgtests are broken against systemd-resolved

Status in ubuntu-fan package in Ubuntu:
  New

Bug description:
  Now that 17.10 has migrated to netplan+systemd-networkd+systemd-
  resolved by default, ubuntu-fan autopkgtests are failing; at least one
  reason for this failure is wrong detection of the default network
  interface because autopkgtest environments appear for some reason to
  be getting multiple default routes:

  autopkgtest [20:14:59]: test lxd: [---
  Error: either "dev" is duplicate, or "ens2" is a garbage.
  II: Auto-init LXD...
  LXD has been successfully configured.
  II: Creating Fan Bridge...
  /usr/sbin/fanatic: .0.0/16: unknown underlay network format
  FAIL: Error on enable-fan
  autopkgtest [20:15:10]: test lxd: ---]

  
(https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/amd64/u/ubuntu-
  fan/20170916_203221_4f037@/log.gz)

  The other part failure appears to be a race with systemd-resolved in
  setting up the network inside of docker containers:

  autopkgtest [17:25:39]: test docker: [---
  Running in the Canonical CI environment
  II: Auto-create Fan Bridge...
  configuring fan underlay:10.220.0.0/16 overlay:250.0.0.0/8
  II: Create docker Fan Network...
  configuring docker for underlay:10.220.0.0/16 overlay:250.0.0.0/8 (fan-250 
250.4
  6.84.0/24)
  1c8a03aa50ab88b997c3b3aee88bfa6933b14368f1594db4a800c2ae8d62074f
  II: Test docker...
  local docker test: pulling container images ...
  Using default tag: latest
  latest: Pulling from library/ubuntu
  d5c6f90da05d: Pulling fs layer
  [...]
  2b8db33536d4: Pull complete
  Digest: 
sha256:2b9285d3e340ae9d4297f83fed6a9563493945935fc787e98cc32a69f5687641
  Status: Downloaded newer image for ubuntu:latest
  local docker test: creating test container ...
  5cbdd232b71bc0738f27f1fa3eae4360716bfe3f8cea976874bf6309b1843169
   slave: installing ping ...
  W: Failed to fetch

[Kernel-packages] [Bug 1713619] Re: [Feature] RDT: Disable most RDT features on Skylake server

** Information type changed from Proprietary to Public

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

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

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

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

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

Title:
  [Feature] RDT: Disable most RDT features on Skylake server

Status in intel:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  Description:

  There are serious errata in CMT, MBM and CAT sub-features of resource
  director technology. Disable these features by default on Skylake but
  provide a boot time argument to re-enable them for users who
  understand the errata and can use them for specific workloads.

  
  Commit IDs:(4.14)
  0576113a387e0c8a5d9e24b4cd62605d1c9c0db8
  1d9807fc64c131a83a96917f2b2da1c9b00cf127
  d56593eb5eda8f593db92927059697bbf89bc4b3

  Target Release : 17.10
  Target Kernel: 4.14

  (Need backporting into 17.10 from 4.14 to 4.13)

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1713619/+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 1673344] Re: Ubuntu 16.04 doesn't recongnize wifi card after loosing signal completely (intel 7260) even when I try to restart network manager

2017-09-20 Thread Paul Mann

Apport-collect won't work as this is a network related bug. By the time
the bug has manifested, networking is no longer available

** 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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1673344

Title:
  Ubuntu 16.04 doesn't recongnize wifi card after loosing signal
  completely (intel 7260) even when I try to restart network manager

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  My wireless connection completely disappears and isn't recognized
  along with my NIC card and doesn't come back until I reboot even if I
  restart network manager.

  
  I've attached the required files showing what my wifi information looks like 
connected and what it looks like when the problem occurs hopefully a fix or 
workaround can be found this happens several times a day.

  Steps:

  1) I boot up type in sudo iwconfig wlp3s0 power off (turn off power 
management)
   
  2) 
  $ iwconfig
  enp4s0f2  no wireless extensions.
  
  lono wireless extensions.
  
  wlp3s0IEEE 802.11  ESSID:"2.4ghz"  
Mode:Managed  Frequency:2.437 GHz  Access Point: 
E0:3F:29:93:3F:20   
Bit Rate=144.4 Mb/s   Tx-Power=22 dBm   
Retry short limit:7   RTS thr:off   Fragment thr:off
Power Management:off
Link Quality=60/70  Signal level=-50 dBm  
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:55   Missed beacon:0
  
  3) I loose wifi using 5ghz or 2.4ghz after a certain amount of time
  
  4) sudo rmmod iwlmvm iwlwifi && sudo modprobe iwlmvm iwlwifi
  5) sudo systemctl restart network-manager.service

  I do a **iwconfig** and **I'm missing wlp3s0IEEE 802.11
  ESSID:"2.4ghz"**

  $ iwconfig
  enp4s0f2  no wireless extensions.
  
  lono wireless extensions.

  I have to reboot to get my wifi back and for ubunutu to recognize my
  wifi card back how can I prevent this.

  $ uname -a
  Linux sys76 4.8.0-41-generic #44~16.04.1-Ubuntu SMP Fri Mar 3 17:11:16 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  $ dmesg | grep iwlwifi
  876.891600] iwlwifi :03:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  876.891602] iwlwifi :03:00.0: Scan failed! ret -5
  [  877.909370] iwlwifi :03:00.0: Failed to wake NIC for hcmd
  [  877.909397] iwlwifi :03:00.0: Error sending 
SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5
  [  877.909409] iwlwifi :03:00.0: Scan failed! ret -5
  [  878.928277] iwlwifi :03:00.0: Failed to wake NIC for hcmd
  [  878.928364] iwlwifi :03:00.0: Error sending 
SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5
  [  878.928366] iwlwifi :03:00.0: Scan failed! ret -5
  [  879.947120] iwlwifi :03:00.0: Failed to wake NIC for hcmd
  [  879.947170] iwlwifi :03:00.0: Error sending 
SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5
  [  879.947172] iwlwifi :03:00.0: Scan failed! ret -5

  
  $ sudo lshw -C network
  [sudo] password for rt: 
*-network   
 description: Wireless interface
 product: Wireless 7260
 vendor: Intel Corporation
 physical id: 0
 bus info: pci@:03:00.0
 logical name: wlp3s0
 version: 73
 serial: 0c:8b:fd:2e:64:8e
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet 
physical wireless
 configuration: broadcast=yes driver=iwlwifi 
driverversion=4.8.0-41-generic firmware=17.352738.0 ip=192.168.1.8 latency=0 
link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:31 memory:f7d0-f7d01fff
*-network
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0.2
 bus info: pci@:04:00.2
 logical name: enp4s0f2
 version: 0a
 serial: 00:90:f5:f9:d4:f8
 size: 10Mbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd bus_master cap_list 
ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8411-1_0.0.3 06/18/12 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
 resources: irq:27 ioport:e000(size=256)

[Kernel-packages] [Bug 1716564] Re: BT 4.0 not working

2017-09-20 Thread Alejandro Arcos

Hi, I just coming out of pneumonia,

But I have other problem.


:~/Downloads/temp$ sudo dpkg -i *.deb
 
Selecting previously unselected package linux-headers-3.14.4-031404-generic.
(Reading database ... 237646 files and directories currently installed.)
Preparing to unpack 
linux-headers-3.14.4-031404-generic_3.14.4-031404.201405130853_amd64.deb ...
Unpacking linux-headers-3.14.4-031404-generic (3.14.4-031404.201405130853) ...
Selecting previously unselected package linux-image-3.14.4-031404-generic.
Preparing to unpack 
linux-image-3.14.4-031404-generic_3.14.4-031404.201405130853_amd64.deb ...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode 
3.14.4-031404-generic /boot/vmlinuz-3.14.4-031404-generic
Done.
Unpacking linux-image-3.14.4-031404-generic (3.14.4-031404.201405130853) ...
dpkg: dependency problems prevent configuration of 
linux-headers-3.14.4-031404-generic:
 linux-headers-3.14.4-031404-generic depends on linux-headers-3.14.4-031404; 
however:
  Package linux-headers-3.14.4-031404 is not installed.

dpkg: error processing package linux-headers-3.14.4-031404-generic (--install):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of 
linux-image-3.14.4-031404-generic:
 linux-image-3.14.4-031404-generic depends on module-init-tools (>= 
3.3-pre11-4ubuntu3); however:
  Package module-init-tools is not installed.

dpkg: error processing package linux-image-3.14.4-031404-generic (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-headers-3.14.4-031404-generic
 linux-image-3.14.4-031404-generic

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

Title:
  BT 4.0 not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My xubuntu not find any BT device.

  I know propietary driver but not find if setup available for working.

  Thanks a lot

  Alejandro

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-93-generic 4.4.0-93.116
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aarcos 1895 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Sep 12 00:35:26 2017
  HibernationDevice: RESUME=UUID=cb562a6f-2f15-48cd-a992-b8b8c1c11b6a
  InstallationDate: Installed on 2016-11-16 (300 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Vostro 3460
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=eb6173e0-2af2-4b58-b5d2-d70b037ec784 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-93-generic N/A
   linux-backports-modules-4.4.0-93-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/22/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0J1V31
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd08/22/2013:svnDellInc.:pnVostro3460:pvr:rvnDellInc.:rn0J1V31:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Vostro 3460
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716564/+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 1702910] Re: System freeze after in6_dev_finish_destroy errors

Can folks affected by this bug test the kernel located at:
http://kernel.ubuntu.com/~jsalisbury/lp1702910/

To test the kernel, please install both the linux-image and linux-image-
extra .deb 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/1702910

Title:
  System freeze after in6_dev_finish_destroy errors

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  After the upgrade to the `4.4.0-83-generic #106~14.04.1-Ubuntu` kernel
  we are seeing system hangs with the following logs.  Prior to this
  upgrade there were no crashes or kernel traces of this sort.  We have
  ruled out physical hardware issues by moving the VM to another
  physical host.

  In the logs there's reference to docker instances on the host.  This
  results in veth devices being brought up and torn down frequently,
  which is likely related.

  As a possible workaround we have disabled IPv6 for now.

  ```
  kernel: [337352.274907] vethf317e0d: renamed from eth0
  kernel: [337352.386446] docker0: port 1(veth160ed4a) entered disabled state
  kernel: [337352.393444] docker0: port 1(veth160ed4a) entered disabled state
  kernel: [337352.395408] device veth160ed4a left promiscuous mode
  kernel: [337352.395417] docker0: port 1(veth160ed4a) entered disabled state
  kernel: [337359.301576] vethee2599d: renamed from eth0
  kernel: [337359.339582] docker0: port 2(veth3100aab) entered disabled state
  kernel: [337359.343059] docker0: port 2(veth3100aab) entered disabled state
  kernel: [337359.344987] device veth3100aab left promiscuous mode
  kernel: [337359.344997] docker0: port 2(veth3100aab) entered disabled state
  kernel: [337475.398358] [ cut here ]
  kernel: [337475.398370] WARNING: CPU: 3 PID: 23671 at 
/build/linux-lts-xenial-ep3zLI/linux-lts-xenial-4.4.0/net/ipv6/addrconf_core.c:159
 in6_dev_f

  kernel: [337475.398372] Modules linked in: btrfs xor raid6_pq ufs qnx4 
hfsplus hfs minix ntfs msdos jfs xfs libcrc32c veth ip6table_filter ip6_tab
  comment ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_fil
  filter bridge stp llc aufs tcp_diag inet_diag coretemp crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel ppdev aes_x86_64 lrw gf128mul
  input_leds serio_raw drm_kms_helper parport_pc drm lp fb_sys_fops syscopyarea 
sysfillrect sysimgblt vmw_vmci parport shpchp 8250_fintek i2c_piix4

  kernel: [337475.398416] CPU: 3 PID: 23671 Comm: kworker/u8:0 Not tainted 
4.4.0-83-generic #106~14.04.1-Ubuntu
  kernel: [337475.398418] Hardware name: VMware, Inc. VMware Virtual 
Platform/440BX Desktop Reference Platform, BIOS 6.00 09/17/2015
  kernel: [337475.398423] Workqueue: netns cleanup_net
  kernel: [337475.398424]   8801b197fbb8 813ddefc 

  kernel: [337475.398427]  81d7aa10 8801b197fbf0 8107ea36 
88016f97d400
  kernel: [337475.398428]  88016f97e800 0006 8801b197fcc0 

  kernel: [337475.398430] Call Trace:
  kernel: [337475.398435]  [] dump_stack+0x63/0x87
  kernel: [337475.398440]  [] warn_slowpath_common+0x86/0xc0
  kernel: [337475.398442]  [] warn_slowpath_null+0x1a/0x20
  kernel: [337475.398444]  [] in6_dev_finish_destroy+0x6b/0xb0
  kernel: [337475.398447]  [] ip6_route_dev_notify+0x110/0x130
  kernel: [337475.398450]  [] notifier_call_chain+0x49/0x70
  kernel: [337475.398452]  [] 
raw_notifier_call_chain+0x16/0x20
  kernel: [337475.398455]  [] 
call_netdevice_notifiers_info+0x35/0x60
  kernel: [337475.398458]  [] netdev_run_todo+0x157/0x300
  kernel: [337475.398461]  [] ? 
rollback_registered_many+0x22e/0x2e0
  kernel: [337475.398463]  [] rtnl_unlock+0xe/0x10
  kernel: [337475.398464]  [] 
default_device_exit_batch+0x138/0x150
  kernel: [337475.398468]  [] ? __wake_up_sync+0x20/0x20
  kernel: [337475.398470]  [] ops_exit_list.isra.4+0x52/0x60
  kernel: [337475.398472]  [] cleanup_net+0x1b3/0x280
  kernel: [337475.398476]  [] process_one_work+0x150/0x3f0
  kernel: [337475.398478]  [] worker_thread+0x11a/0x470
  kernel: [337475.398481]  [] ? __schedule+0x359/0x980
  kernel: [337475.398483]  [] ? rescuer_thread+0x310/0x310
  kernel: [337475.398484]  [] kthread+0xd6/0xf0
  kernel: [337475.398486]  [] ? kthread_park+0x60/0x60
  kernel: [337475.398488]  [] ret_from_fork+0x3f/0x70
  kernel: [337475.398490]  [] ? kthread_park+0x60/0x60
  kernel: [337475.398491] ---[ end trace 6d63274dc9a3dbec ]---
  kernel: [337475.398492] [ cut here ]

  ```

  ProblemType: Bug
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: amd64
  Date: Fri Jul  7 13:59:36 2017
  Dependencies:
   adduser 3.113+nmu3ubuntu3
   apt-utils 1.0.1ubuntu2.17
   base-passwd 3.5.33
   busybox-initramfs 1:1.21.0-1ubuntu1
   coreutils 8.21-1ubuntu5.4

[Kernel-packages] [Bug 1715552] Re: VMWare does not start

** Tags removed: needs-bisect

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

Title:
  VMWare does not start

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Under Ubuntu 17.10 beta VMWare 12.5.7 cannot be started:

  /usr/lib/vmware/bin/vmware-modconfig: Relink `/lib/x86_64-linux-
  gnu/libbsd.so.0' with `/lib/x86_64-linux-gnu/librt.so.1' for IFUNC
  symbol `clock_gettime'

  Works under Ubuntu 17.04

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-13-generic 4.12.0-13.14
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wolf   9336 F pulseaudio
   /dev/snd/controlC0:  wolf   9336 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 07:53:43 2017
  HibernationDevice: RESUME=UUID=88d69bc7-ac96-42c6-bf6d-5c912964a63b
  InstallationDate: Installed on 2017-09-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.12.0-13-generic N/A
   linux-backports-modules-4.12.0-13-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B33.1706181928
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715552/+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 1702910] Re: System freeze after in6_dev_finish_destroy errors

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

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

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

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

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

Title:
  System freeze after in6_dev_finish_destroy errors

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  After the upgrade to the `4.4.0-83-generic #106~14.04.1-Ubuntu` kernel
  we are seeing system hangs with the following logs.  Prior to this
  upgrade there were no crashes or kernel traces of this sort.  We have
  ruled out physical hardware issues by moving the VM to another
  physical host.

  In the logs there's reference to docker instances on the host.  This
  results in veth devices being brought up and torn down frequently,
  which is likely related.

  As a possible workaround we have disabled IPv6 for now.

  ```
  kernel: [337352.274907] vethf317e0d: renamed from eth0
  kernel: [337352.386446] docker0: port 1(veth160ed4a) entered disabled state
  kernel: [337352.393444] docker0: port 1(veth160ed4a) entered disabled state
  kernel: [337352.395408] device veth160ed4a left promiscuous mode
  kernel: [337352.395417] docker0: port 1(veth160ed4a) entered disabled state
  kernel: [337359.301576] vethee2599d: renamed from eth0
  kernel: [337359.339582] docker0: port 2(veth3100aab) entered disabled state
  kernel: [337359.343059] docker0: port 2(veth3100aab) entered disabled state
  kernel: [337359.344987] device veth3100aab left promiscuous mode
  kernel: [337359.344997] docker0: port 2(veth3100aab) entered disabled state
  kernel: [337475.398358] [ cut here ]
  kernel: [337475.398370] WARNING: CPU: 3 PID: 23671 at 
/build/linux-lts-xenial-ep3zLI/linux-lts-xenial-4.4.0/net/ipv6/addrconf_core.c:159
 in6_dev_f

  kernel: [337475.398372] Modules linked in: btrfs xor raid6_pq ufs qnx4 
hfsplus hfs minix ntfs msdos jfs xfs libcrc32c veth ip6table_filter ip6_tab
  comment ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_fil
  filter bridge stp llc aufs tcp_diag inet_diag coretemp crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel ppdev aes_x86_64 lrw gf128mul
  input_leds serio_raw drm_kms_helper parport_pc drm lp fb_sys_fops syscopyarea 
sysfillrect sysimgblt vmw_vmci parport shpchp 8250_fintek i2c_piix4

  kernel: [337475.398416] CPU: 3 PID: 23671 Comm: kworker/u8:0 Not tainted 
4.4.0-83-generic #106~14.04.1-Ubuntu
  kernel: [337475.398418] Hardware name: VMware, Inc. VMware Virtual 
Platform/440BX Desktop Reference Platform, BIOS 6.00 09/17/2015
  kernel: [337475.398423] Workqueue: netns cleanup_net
  kernel: [337475.398424]   8801b197fbb8 813ddefc 

  kernel: [337475.398427]  81d7aa10 8801b197fbf0 8107ea36 
88016f97d400
  kernel: [337475.398428]  88016f97e800 0006 8801b197fcc0 

  kernel: [337475.398430] Call Trace:
  kernel: [337475.398435]  [] dump_stack+0x63/0x87
  kernel: [337475.398440]  [] warn_slowpath_common+0x86/0xc0
  kernel: [337475.398442]  [] warn_slowpath_null+0x1a/0x20
  kernel: [337475.398444]  [] in6_dev_finish_destroy+0x6b/0xb0
  kernel: [337475.398447]  [] ip6_route_dev_notify+0x110/0x130
  kernel: [337475.398450]  [] notifier_call_chain+0x49/0x70
  kernel: [337475.398452]  [] 
raw_notifier_call_chain+0x16/0x20
  kernel: [337475.398455]  [] 
call_netdevice_notifiers_info+0x35/0x60
  kernel: [337475.398458]  [] netdev_run_todo+0x157/0x300
  kernel: [337475.398461]  [] ? 
rollback_registered_many+0x22e/0x2e0
  kernel: [337475.398463]  [] rtnl_unlock+0xe/0x10
  kernel: [337475.398464]  [] 
default_device_exit_batch+0x138/0x150
  kernel: [337475.398468]  [] ? __wake_up_sync+0x20/0x20
  kernel: [337475.398470]  [] ops_exit_list.isra.4+0x52/0x60
  kernel: [337475.398472]  [] cleanup_net+0x1b3/0x280
  kernel: [337475.398476]  [] process_one_work+0x150/0x3f0
  kernel: [337475.398478]  [] worker_thread+0x11a/0x470
  kernel: [337475.398481]  [] ? __schedule+0x359/0x980
  kernel: [337475.398483]  [] ? rescuer_thread+0x310/0x310
  kernel: [337475.398484]  [] kthread+0xd6/0xf0
  kernel: [337475.398486]  [] ? kthread_park+0x60/0x60
  kernel: [337475.398488]  [] ret_from_fork+0x3f/0x70
  kernel: [337475.398490]  [] ? kthread_park+0x60/0x60
  kernel: [337475.398491] ---[ end trace 6d63274dc9a3dbec ]---
  kernel: [337475.398492] [ cut here ]

  ```

  ProblemType: Bug
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: amd64
  Date: Fri Jul  7 13:59:36 2017
  Dependencies:
   adduser 3.113+nmu3ubuntu3
   apt-utils 1.0.1ubuntu2.17

[Kernel-packages] [Bug 1704730] Re: xfstest fails with corrupt file /mnt/scratch/1 - non-zero size but no extents ( ext4 )

Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of a
regression, and when this regression was introduced.   If this is a
regression, we can perform a kernel bisect to identify the commit that
introduced the problem.

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

Title:
  xfstest fails with corrupt file /mnt/scratch/1 - non-zero size but no
  extents ( ext4 )

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

Bug description:
  xfstests fails non-zero size but no extents on ext4 filesystem

  Environment
  --
  Kernel Build:  4.12.1-041201-generic

  Model  : 8247-22L
  Platform:  PowerNV ( P8 )

  Uname output
  ---
  # uname -a
  Linux ltc-test-ci2 4.12.1-041201-generic #201707121132 SMP Wed Jul 12 
17:03:25 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Create a loop device with ext4 filesystem
  2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd 
xfstests-dev
  3. make
  4. Create a local.config for running with created loop device
  5. Run xfstests-dev test  : ./check tests/generic/044

  The test 044 fails with following
  generic/044 - output mismatch (see 
/root/harish/xfstests-dev/results//generic/044.out.bad)
  --- tests/generic/044.out 2017-07-13 06:04:36.208323135 -0400
  +++ /root/harish/xfstests-dev/results//generic/044.out.bad
2017-07-14 06:24:08.153731112 -0400
  @@ -1 +1,1000 @@
   QA output created by 044
  +corrupt file /mnt/scratch/1 - non-zero size but no extents
  +corrupt file /mnt/scratch/2 - non-zero size but no extents
  +corrupt file /mnt/scratch/3 - non-zero size but no extents
  +corrupt file /mnt/scratch/4 - non-zero size but no extents
  +corrupt file /mnt/scratch/5 - non-zero size but no extents
  +corrupt file /mnt/scratch/6 - non-zero size but no extents
  ...
  (Run 'diff -u tests/generic/044.out 
/root/harish/xfstests-dev/results//generic/044.out.bad'  to see the entire diff)
  Ran: generic/044
  Failures: generic/044
  Failed 1 of 1 tests

  
  Dmesg:
  --
  [17244.878673] EXT4-fs (loop0): mounted filesystem with ordered data mode. 
Opts: (null)
  [17245.517227] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17245.697100] EXT4-fs (loop0): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17245.710634] run fstests generic/044 at 2017-07-14 06:23:49
  [17246.534410] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17246.535534] EXT4-fs (loop2): shut down requested (1)
  [17246.535625] Aborting journal on device loop2-8.
  [17247.278467] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17259.888304] EXT4-fs (loop2): shut down requested (2)
  [17259.995751] Aborting journal on device loop2-8.
  [17260.113582] EXT4-fs (loop2): recovery complete
  [17260.113902] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17260.190076] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17264.821978] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr


  == Comment: #2 - SEETEENA THOUFEEK  - 2017-07-17 
02:10:52 ==
  Issue does not happen when running the same test with xfs file system. (ie, 
creating loop device with xfs file system).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1704730/+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 1704730] Re: xfstest fails with corrupt file /mnt/scratch/1 - non-zero size but no extents ( ext4 )

Also, it might be worth testing v4.14-rc1:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc1/

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

Title:
  xfstest fails with corrupt file /mnt/scratch/1 - non-zero size but no
  extents ( ext4 )

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

Bug description:
  xfstests fails non-zero size but no extents on ext4 filesystem

  Environment
  --
  Kernel Build:  4.12.1-041201-generic

  Model  : 8247-22L
  Platform:  PowerNV ( P8 )

  Uname output
  ---
  # uname -a
  Linux ltc-test-ci2 4.12.1-041201-generic #201707121132 SMP Wed Jul 12 
17:03:25 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Create a loop device with ext4 filesystem
  2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd 
xfstests-dev
  3. make
  4. Create a local.config for running with created loop device
  5. Run xfstests-dev test  : ./check tests/generic/044

  The test 044 fails with following
  generic/044 - output mismatch (see 
/root/harish/xfstests-dev/results//generic/044.out.bad)
  --- tests/generic/044.out 2017-07-13 06:04:36.208323135 -0400
  +++ /root/harish/xfstests-dev/results//generic/044.out.bad
2017-07-14 06:24:08.153731112 -0400
  @@ -1 +1,1000 @@
   QA output created by 044
  +corrupt file /mnt/scratch/1 - non-zero size but no extents
  +corrupt file /mnt/scratch/2 - non-zero size but no extents
  +corrupt file /mnt/scratch/3 - non-zero size but no extents
  +corrupt file /mnt/scratch/4 - non-zero size but no extents
  +corrupt file /mnt/scratch/5 - non-zero size but no extents
  +corrupt file /mnt/scratch/6 - non-zero size but no extents
  ...
  (Run 'diff -u tests/generic/044.out 
/root/harish/xfstests-dev/results//generic/044.out.bad'  to see the entire diff)
  Ran: generic/044
  Failures: generic/044
  Failed 1 of 1 tests

  
  Dmesg:
  --
  [17244.878673] EXT4-fs (loop0): mounted filesystem with ordered data mode. 
Opts: (null)
  [17245.517227] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17245.697100] EXT4-fs (loop0): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17245.710634] run fstests generic/044 at 2017-07-14 06:23:49
  [17246.534410] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17246.535534] EXT4-fs (loop2): shut down requested (1)
  [17246.535625] Aborting journal on device loop2-8.
  [17247.278467] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17259.888304] EXT4-fs (loop2): shut down requested (2)
  [17259.995751] Aborting journal on device loop2-8.
  [17260.113582] EXT4-fs (loop2): recovery complete
  [17260.113902] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17260.190076] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17264.821978] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr


  == Comment: #2 - SEETEENA THOUFEEK  - 2017-07-17 
02:10:52 ==
  Issue does not happen when running the same test with xfs file system. (ie, 
creating loop device with xfs file system).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1704730/+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 1718284] Re: package linux-image-4.10.0-35-generic 4.10.0-35.39 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"

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

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

Title:
  package linux-image-4.10.0-35-generic 4.10.0-35.39 failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  recurring failure to install. likely to be local issue

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-35-generic 4.10.0-35.39
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alex   3521 F pulseaudio
   /dev/snd/controlC0:  alex   3521 F pulseaudio
  Date: Mon Sep 18 17:29:36 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=53248f42-e64e-45c2-a19c-ea82c55b9eb5
  InstallationDate: Installed on 2016-11-16 (307 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic.efi.signed 
root=UUID=520bf0a3-9021-4268-b355-10efda7b0177 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.10.0-35-generic 4.10.0-35.39 failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.23
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2163
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 29.24
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.23:bd09/26/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr08961030410620100:rvnHewlett-Packard:rn2163:rvr29.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 08961030410620100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718284/+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 1718292] Re: POWER9: NX842 module changes

** Tags added: kernel-da-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/1718292

Title:
  POWER9: NX842 module changes

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  This feature request will be used to submit NX842 changes needed to
  support on p9 - Using VAS interfaces instead of icswx to communicate
  with VAS (on PowerNV), modification of HCALL interface (on PowerVM, if
  needed) and other format changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1718292/+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 1707695] Re: radeon 0000:03:00.0: ring 0 stalled for more than 10000msec

2017-09-20 Thread Christopher Clapp

kaihengfeng, I posted at fredesktop.org as you suggested.  Thanks!

See:  https://bugs.freedesktop.org/show_bug.cgi?id=102909

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

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

Title:
  radeon :03:00.0: ring 0 stalled for more than 1msec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My system intermittently locks up every few days. It does not seem to
  correspond to a particular program or action.  When that happens, the
  screen goes to black, then returns after a few seconds. At that point,
  the time on the clock is static and indicates that the screen is
  frozen, but audio continues to play for 30 seconds to a minute. The
  keyboard and mouse do not affect what's being displayed, but I can Alt
  - SysRq - REISUB to restart.

  Every time (7 crashes and counting), /var/log/kern.log indicates that

  kernel: [353692.378886] radeon :03:00.0: ring 0 stalled for more than 
10280msec
  kernel: [353692.378896] radeon :03:00.0: GPU lockup (current fence id 
0x006e96e5 last fence id 0x006e96e9 on ring 0)

  just before the system locks. Different ring numbers are reported as
  stalling at different times.

  As per the instructions, I posted a question about this issue at:

  https://askubuntu.com/questions/937792/system-lockup-radeon-ring-
  stalled-for-more-than-10280msec?noredirect=1#comment1486875_937792

  but I have not received many responses.

  I'm running 16.04 LTS. 
  :~$ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  According to the Software Center, I am running Ubuntu Software 3.20.1.

  I have a Radeon HD graphics card.

  :~$ lspci | grep VGA
  03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cedar [Radeon HD 5000/6000/7350/8350 Series]

  :~$ lspci -v -s 03:00.0
  03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cedar [Radeon HD 5000/6000/7350/8350 Series] (prog-if 00 [VGA controller])
  Subsystem: Gigabyte Technology Co., Ltd Cedar [Radeon HD 5000/6000/7350/8350 
Series]
  Flags: bus master, fast devsel, latency 0, IRQ 53
  Memory at c000 (64-bit, prefetchable) [size=256M]
  Memory at d3d2 (64-bit, non-prefetchable) [size=128K]
  I/O ports at 7000 [size=256]
  Expansion ROM at d3d0 [disabled] [size=128K]
  Capabilities: 
  Kernel driver in use: radeon
  Kernel modules: radeon

  Please let me know if additional information would be useful, and I
  will be glad to provide it.  Thanks in advance.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-87-generic 4.4.0-87.110
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  clapp  3889 F pulseaudio
   /dev/snd/controlC2:  clapp  3889 F pulseaudio
   /dev/snd/controlC1:  clapp  3889 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 31 14:02:27 2017
  HibernationDevice: RESUME=UUID=1b30dad6-8c48-42cf-ae26-66ab8b0eb446
  InstallationDate: Installed on 2013-09-04 (1425 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: Dell Inc. Precision T7600
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic 
root=UUID=33722f76-37fd-4289-b071-d7f48b65dd32 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-87-generic N/A
   linux-backports-modules-4.4.0-87-generic  N/A
   linux-firmware1.157.11
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/03/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 082WXT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd05/03/2013:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn082WXT:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T7600
  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/1707695/+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 1718397] Re: multipath -ll is not showing the disks which are actually multipath

** Changed in: kernel-package (Ubuntu)
   Importance: Undecided => Critical

** Tags added: kernel-da-key

** Package changed: kernel-package (Ubuntu) => linux (Ubuntu)

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

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

** Also affects: linux (Ubuntu Artful)
   Importance: Critical
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
   Status: Triaged

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

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

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

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

** Changed in: linux (Ubuntu Xenial)
   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/1718397

Title:
  multipath -ll is not showing the disks which are actually multipath

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Zesty:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  [Impact]

   * The number of available AIO contexts is severely limited
 on systems with a large number of possible CPUs 
 (e.g., IBM POWER8 processors w/ 20ish cores * 8 threads/core,
 and other multithreaded server-class processors).

   * This prevents application such as multipath/directio checker
 to provide all of the available devices to the system.

   * Other applications which depend on AIO can be affected/limited.

   * The patch fixes how aio increments the number of active contexts
 (seen in /proc/sys/fs/aio-nr) and checks that against the global
 limit (seen in /proc/sys/fs/aio-max-nr).

  [Test Case]

   * A synthetic test-case is attached (io_setup_v2.c) and demonstrated
 (original/patched kernels) in comment #4.

   * Trying to perform multipath discovery in debug/verbose mode
 (i.e., "multipath -v3" command) with sufficient number of 
 individual paths using the "directio" path checker should
 demonstrate the problem/solution as well (i.e., presence or
 not of "io_setup failed" messages).

  [Regression Potential]

   * Note the fix is trivial and has been tested by several users,
 even caused the introduction of a new test-case in "libaio";
 (but that can never be a strong enough reason for no more errors).

   * Applications which use aio with small "nr_events" value as argument
 to "io_setup()" now have access to a much larger number of aio contexts;
 but hopefully those apps are already only requesting what they need,
 not trying to get more and more.

   * Applications which relied in the _incorrect_ behavior of 
'/proc/sys/fs/aio-nr'
 being possibly greater than '/proc/sys/fs/aio-max-nr' might have problems,
 but those apps should be fixed.


  Problem Description
  =
  I am facing this issue for Texan Flash storage 840 disks which are coming 
from coho and salfish adapter

  coho adapter with 840 storage  is 3G disks and salfish adapter with
  840 is 12G disks

  I am able to see those disks in lsblk o/p but not in multipath -ll
  comamnd

  0004:01:00.0 Coho: Saturn-X  U78C9.001.WZS0060-P1-C6 
0x1090fa2a51f8  host10  Online
  0004:01:00.1 Coho: Saturn-X  U78C9.001.WZS0060-P1-C6 
0x1090fa2a51f9  host11  Online

  0005:09:00.0 Sailfish: QLogic 8GBU78C9.001.WZS0060-P1-C9 
0x2124ff787778  host2   Online
  0005:09:00.1 Sailfish: QLogic 8GBU78C9.001.WZS0060-P1-C9 
0x2124ff787779  host4   Online

  root@luckyv1:/dev/disk# multipath -ll | grep "size=3.0G" -B 1
  root@luckyv1:/dev/disk# multipath -ll | grep "size=12G" -B 1
  root@luckyv1:/dev/disk#

  == Comment: #3 - Luciano Chavez  - 2016-09-20 20:22:20 ==
  I edited /etc/multipath.conf and added
  verbosity 6

  to crank up the output and ran multipath -ll and saved it off to a
  text file (attached). All the using the directio checker failed and
  those using the tur checker seem to work.

  Sep 20 20:07:36 | loading //lib/multipath/libcheckdirectio.so checker
  Sep 20 20:07:36 | loading //lib/multipath/libprioconst.so prioritizer
  Sep 20 20:07:36 | Discover device 
/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/block/sdai
  Sep 20 20:07:36 | sdai: udev property ID_WWN whitelisted
  Sep 20 20:07:36 | sdai: not found in pathvec
  Sep 20 20:07:36 | sdai: mask = 0x25
  Sep 20 20:07:36 | sdai: dev_t = 66:32
  Sep 20 20:07:36 | open

[Kernel-packages] [Bug 1718397] [NEW] multipath -ll is not showing the disks which are actually multipath

You have been subscribed to a public bug:

[Impact]

 * The number of available AIO contexts is severely limited
   on systems with a large number of possible CPUs 
   (e.g., IBM POWER8 processors w/ 20ish cores * 8 threads/core,
   and other multithreaded server-class processors).

 * This prevents application such as multipath/directio checker
   to provide all of the available devices to the system.

 * Other applications which depend on AIO can be affected/limited.

 * The patch fixes how aio increments the number of active contexts
   (seen in /proc/sys/fs/aio-nr) and checks that against the global
   limit (seen in /proc/sys/fs/aio-max-nr).

[Test Case]

 * A synthetic test-case is attached (io_setup_v2.c) and demonstrated
   (original/patched kernels) in comment #4.

 * Trying to perform multipath discovery in debug/verbose mode
   (i.e., "multipath -v3" command) with sufficient number of 
   individual paths using the "directio" path checker should
   demonstrate the problem/solution as well (i.e., presence or
   not of "io_setup failed" messages).

[Regression Potential]

 * Note the fix is trivial and has been tested by several users,
   even caused the introduction of a new test-case in "libaio";
   (but that can never be a strong enough reason for no more errors).

 * Applications which use aio with small "nr_events" value as argument
   to "io_setup()" now have access to a much larger number of aio contexts;
   but hopefully those apps are already only requesting what they need,
   not trying to get more and more.

 * Applications which relied in the _incorrect_ behavior of 
'/proc/sys/fs/aio-nr'
   being possibly greater than '/proc/sys/fs/aio-max-nr' might have problems,
   but those apps should be fixed.


Problem Description
=
I am facing this issue for Texan Flash storage 840 disks which are coming from 
coho and salfish adapter

coho adapter with 840 storage  is 3G disks and salfish adapter with 840
is 12G disks

I am able to see those disks in lsblk o/p but not in multipath -ll
comamnd

0004:01:00.0 Coho: Saturn-X  U78C9.001.WZS0060-P1-C6 
0x1090fa2a51f8  host10  Online
0004:01:00.1 Coho: Saturn-X  U78C9.001.WZS0060-P1-C6 
0x1090fa2a51f9  host11  Online

0005:09:00.0 Sailfish: QLogic 8GBU78C9.001.WZS0060-P1-C9 
0x2124ff787778  host2   Online
0005:09:00.1 Sailfish: QLogic 8GBU78C9.001.WZS0060-P1-C9 
0x2124ff787779  host4   Online

root@luckyv1:/dev/disk# multipath -ll | grep "size=3.0G" -B 1
root@luckyv1:/dev/disk# multipath -ll | grep "size=12G" -B 1
root@luckyv1:/dev/disk#

== Comment: #3 - Luciano Chavez  - 2016-09-20 20:22:20 ==
I edited /etc/multipath.conf and added
verbosity 6

to crank up the output and ran multipath -ll and saved it off to a text
file (attached). All the using the directio checker failed and those
using the tur checker seem to work.

Sep 20 20:07:36 | loading //lib/multipath/libcheckdirectio.so checker
Sep 20 20:07:36 | loading //lib/multipath/libprioconst.so prioritizer
Sep 20 20:07:36 | Discover device 
/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/block/sdai
Sep 20 20:07:36 | sdai: udev property ID_WWN whitelisted
Sep 20 20:07:36 | sdai: not found in pathvec
Sep 20 20:07:36 | sdai: mask = 0x25
Sep 20 20:07:36 | sdai: dev_t = 66:32
Sep 20 20:07:36 | open 
'/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/block/sdai/size'
Sep 20 20:07:36 | sdai: size = 20971520
Sep 20 20:07:36 | sdai: vendor = IBM
Sep 20 20:07:36 | sdai: product = FlashSystem-9840
Sep 20 20:07:36 | sdai: rev = 1442
Sep 20 20:07:36 | sdai: h:b:t:l = 3:0:0:0
Sep 20 20:07:36 | SCSI target 3:0:0 -> FC rport 3:0-2
Sep 20 20:07:36 | sdai: tgt_node_name = 0x500507605e839800
Sep 20 20:07:36 | open 
'/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/state'
Sep 20 20:07:36 | sdai: path state = running
Sep 20 20:07:36 | sdai: get_state
Sep 20 20:07:36 | sdai: path_checker = directio (internal default)
Sep 20 20:07:36 | sdai: checker timeout = 30 ms (internal default)
Sep 20 20:07:36 | io_setup failed
Sep 20 20:07:36 | sdai: checker init failed

== Comment: #7 - Mauricio Faria De Oliveira  - 2016-09-27 
18:32:57 ==
The function is failing at the io_setup() system call.

 @ checkers/directio.c

 int libcheck_init (struct checker * c)
 {
  unsigned long pgsize = getpagesize();
  struct directio_context * ct;
  long flags;

  ct = malloc(sizeof(struct directio_context));
  if (!ct)
  return 1;
  memset(ct, 0, sizeof(struct directio_context));

  if (io_setup(1, >ioctx) != 0) {
  condlog(1, "io_setup failed");
  free(ct);
  return 1;
  }
 <...>

The syscall is failing w/ EAGAIN

 # grep ^io_setup multipath_-v2_-d.strace
 io_setup(1,

[Kernel-packages] [Bug 1715741] Re: Wi-Fi broken in 16.04.3 and later on Dell Edge 3003

I installed the daily of artful server.  I confirmed that it was kernel
4.12.0-13 and that the wi-fi doesn't work.  I installed kernel 4.14rc1
debs on it.  I don't know where to get linux-kernel-extra 4.14rc1 deb,
so it was not installed.  And, it panics.



How do I get kernel 4.14rc1 running on anything?

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

Title:
  Wi-Fi broken in 16.04.3 and later on Dell Edge 3003

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The built-in Wi-Fi on the Dell Edge 3003 is not working.  It works in
  16.04.1 but not in 16.04.3 or 17.04.  Both server and desktop versions
  were tested.  The Wi-Fi device is an RSI 915 connected on the SDIO
  bus.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715741/+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 1712580] Re: [SRU][Zesty]PCI: Add pci_mmap_resource_range() and use it for ARM64

= Testing AMD64 =

== Before patch ==
ubuntu@betelnut:~$ lspci | grep Mellanox
01:00.0 Ethernet controller: Mellanox Technologies MT27520 Family [ConnectX-3 
Pro]

ubuntu@betelnut:~$ ls /sys/bus/pci/devices/\:01\:00.0/resource*
/sys/bus/pci/devices/:01:00.0/resource
/sys/bus/pci/devices/:01:00.0/resource0
/sys/bus/pci/devices/:01:00.0/resource2
/sys/bus/pci/devices/:01:00.0/resource2_wc

== After patch ==
ubuntu@betelnut:~$ uname -a 
Linux betelnut 4.10.0-33-generic #37~lp1712580+build.3-Ubuntu SMP Thu Aug 24 
18:57:45 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

ubuntu@betelnut:~$ lspci | grep Mellanox01:00.0 Ethernet controller:
Mellanox Technologies MT27520 Family [ConnectX-3 Pro]

ubuntu@betelnut:~$ ls /sys/bus/pci/devices/\:01\:00.0/resource*
/sys/bus/pci/devices/:01:00.0/resource
/sys/bus/pci/devices/:01:00.0/resource0
/sys/bus/pci/devices/:01:00.0/resource2
/sys/bus/pci/devices/:01:00.0/resource2_wc

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

Title:
  [SRU][Zesty]PCI: Add pci_mmap_resource_range() and use it for ARM64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  uio device binding inside VM would fail with errors
  EAL: Detected 3 lcore(s)
  EAL: Probing VFIO support...
  EAL: PCI device :00:01.0 on NUMA socket -1
  EAL: probe driver: 1af4:1000 net_virtio
  EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource1: No such file or 
directory
  EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource0: No such file or 
directory
  EAL: Error - exiting with code: 1
    Cause: Requested device :00:01.0 cannot be used

  [Fix]
  Fixed in linus kernel 4.13 by patch David Woodhouse (4):
  PCI: Move multiple declarations of pci_mmap_page_range() to 
  PCI: Use BAR index in sysfs attr->private instead of resource pointer
  PCI: Add BAR index argument to pci_mmap_page_range()
  PCI: Add pci_mmap_resource_range() and use it for ARM64

  [Test]
  Please see comment #3 and comment #4 for ARM64 testing on QDF2400 system, and 
subsequent comments for testing on other arches.

  [Regression Potential]
  Patch touches PCI subsystem on all architectures, and PCI drivers. Regression 
tested on ARM64, ppc64el and AMD64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1712580/+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 1715368] Re: Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03 'kernel-fixed-upstream'

The purpose of going through a "Reverse" bisect is to identify the
commit that fixes this bug and adds the proper CuW B1 device IDs.  To do
that, we would want to figure out the last kernel that did not have the
ids and the first kernel that did.

However, it sounds like all the upstream kernels you tested so far do
not exhibit this bug (4.4 -> 4.13), but the 16.04.3 kernel does have the
bug?

Also, the 16.04.3 kernel should be 4.10 based, but you see version
4.4.0-87?  Is that correct?

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

Title:
  Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03
  'kernel-fixed-upstream'

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Zesty:
  Triaged

Bug description:
  Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03.
  CuW B1 device IDs are missing with Ubuntu 16.04.03 inbox bnxt_en 
driver(0.1.24) 

  Below is the modinfo output of Ubuntu 16.04.03 inbox bnxt_en driver.

  root@ubuntu160403:~# modinfo bnxt_en 
  filename: 
/lib/modules/4.4.0-87-generic/kernel/drivers/net/ethernet/broadcom/bnxt/bnxt_en.ko
 
  version: 0.1.24 
  description: Broadcom BCM573xx network driver 
  license: GPL 
  srcversion: 0110469E9118262B301CA46 
  alias: pci:v14E4d16D3sv*sd*bc*sc*i* 
  alias: pci:v14E4d16CBsv*sd*bc*sc*i* 
  alias: pci:v14E4d16D2sv*sd*bc*sc*i* 
  alias: pci:v14E4d16D1sv*sd*bc*sc*i* 
  alias: pci:v14E4d16CAsv*sd*bc*sc*i* 
  alias: pci:v14E4d16C9sv*sd*bc*sc*i* 
  depends: vxlan 
  intree: Y 
  vermagic: 4.4.0-87-generic SMP mod_unload modversions 

  OS Details: 
  root@ubuntu160403:~# cat /etc/issue 
  Ubuntu 16.04.3 LTS \n \l 

  root@ubuntu160403:~# uname -a 
  Linux ubuntu160403 4.4.0-87-generic #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715368/+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 1567597] Re: [FFe] implement 'complain mode' in seccomp for developer mode with snaps

2017-09-20 Thread Tyler Hicks

I had previously attached a slightly old version of the lp1567597-test.c
program that contained a mistake. I'm now attaching the corrected
version after fetching it from my testing VM.

** Attachment removed: "lp1567597-test.c"
   
https://bugs.launchpad.net/snappy/+bug/1567597/+attachment/4953120/+files/lp1567597-test.c

** Attachment added: "lp1567597-test.c"
   
https://bugs.launchpad.net/snappy/+bug/1567597/+attachment/4954002/+files/lp1567597-test.c

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

Title:
  [FFe] implement 'complain mode' in seccomp for developer mode with
  snaps

Status in Snappy:
  Confirmed
Status in libseccomp package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  A requirement for snappy is that a snap may be placed in developer
  mode which will put the security sandbox in complain mode such that
  violations against policy are logged, but permitted. In this manner
  learning tools can be written to parse the logs, etc and make
  developing on snappy easier.

  Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while
  we can set complain mode to permit all calls, they are not logged at
  this time. I've discussed this with upstream and we are working
  together on the approach. This may require a kernel patch and an
  update to libseccomp, to filing this bug for now as a placeholder and
  we'll add other tasks as necessary.

  UPDATE: ubuntu-core-launcher now supports the '@complain' directive
  that is a synonym for '@unrestricted' so people can at least turn on
  developer mode and not be blocked by seccomp. Proper complain mode for
  seccomp needs to still be implemented (this bug).

  [Impact]

  Snapd needs a way to log seccomp actions without blocking any syscalls
  in order to have a more useful complain mode. Such functionality has
  been acked upstream and patches are on their way into the Linux 4.14
  kernel (backported to 4.12.0-13.14 in artful).

  The corresponding libseccomp changes are still undergoing review
  (https://github.com/seccomp/libseccomp/pull/92). The pull request adds
  a number of new symbols and probably isn't appropriate to backport
  until upstream has acked the pull request. However, only a small part
  of that larger pull request is needed by snapd and that change can be
  safely backported since the only added symbol, the SCMP_ACT_LOG macro,
  must match the SECCOMP_RET_LOG macro that has already been approved
  and merged in the upstream Linux kernel.

  [Test Case]

  A large number of tests are ran as part of the libseccomp build.
  However, the "live" tests which test libseccomp with actual kernel
  enforcement are not ran at that time. They can be manually exercised
  to help catch any regressions. Note that on Artful, there's an
  existing test failure (20-live-basic_die%%002-1):

  $ sudo apt build-dep -y libseccomp
  $ sudo apt install -y cython
  $ apt source libseccomp
  $ autoreconf -ivf && ./configure --enable-python && make check-build
  $ (cd tests && ./regression -T live)
  ...
  Test 20-live-basic_die%%002-1 result:   FAILURE 20-live-basic_die TRAP 
rc=159
  ...
  Regression Test Summary
   tests run: 12
   tests skipped: 0
   tests passed: 11
   tests failed: 1
   tests errored: 0
  

  Now we can build and run a small test program to test the SCMP_ACT_LOG
  action in the way that snapd wants to use it for developer mode:

  $ sudo apt install -y libseccomp-dev
  $ gcc -o lp1567597-test lp1567597-test.c -lseccomp
  $ ./lp1567597-test

  The exit code should be 0 and you should have an entry in the system
  log that looks like this:

  audit: type=1326 audit(1505859630.994:69): auid=1000 uid=1000 gid=1000
  ses=2 pid=18451 comm="lp1567597-test"
  exe="/home/tyhicks/lp1567597-test" sig=0 arch=c03e syscall=2
  compat=0 ip=0x7f547352c5c0 code=0x7ffc

  [Regression Potential]

  Relatively small since the core logic is in the kernel and we're only
  exposing the new action through libseccomp. The changes include smarts
  to query the kernel to see if the action is available in the kernel.
  Calling applications will not be able to use the action on older
  kernels that don't support it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1567597/+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 1693369] Re: 5U84 - ses driver isn't binding right - cannot blink lights on 1 of the 2 5u84

** Description changed:

- This is a request to add the following upstream commit to both Ubuntu
- 16.04.1 and 16.04.2:
+
+ == SRU Justification ==
+ This bug is resolved by commit 62e62ffd95539b9220894a7900a619e0f3ef4756.
+
+ Without this patch, the symlink in sysfs which binds a SAS device to an
enclosure
+ slot does not get created. This makes disk hotplug near impossible on large
+ JBOD disk drawers.
+
+ Commit 62e62ffd95 is also needed in Xenial. However, Xenial also needed some
+ prereq commits, so it's SRU will be sent separately.
+
+ Commit 62e62ffd95 is in mainline as of 4.13-rc1.
+
+
+ == Fix ==
+ commit 62e62ffd95539b9220894a7900a619e0f3ef4756
+ Author: Maurizio Lombardi
+ Date: Tue Jun 27 11:53:27 2017 +0200
+
+ scsi: ses: do not add a device to an enclosure if
+ enclosure_add_links() fails.
+
+ == Regression Potential ==
+ This patch was also cc'd and applied to upstream stable, so there is
+ upstream confidence in it.
+
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug
reporter.
+ The bug reporter states the test kernel resolved the bug.
+
+
+
+ This is a request to add the following upstream commit to both Ubuntu 16.04.1
and 16.04.2:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/scsi/ses.c?id=9373eba6cfae48911b977d14323032cd5d161aae

Without this patch, the symlink in sysfs which binds a SAS device to an
enclosure slot does not get created. This makes disk hotplug near
impossible on large JBOD disk drawers.

You should be able to do:

ls /sys/block/sdb/device/ | grep enclosure

and see something like:

enclosure_device:1

If you cd to this directory, you can then access the SES controls for
that slot to flash the LED to assist in locating the disk to replace a
failed disk.

Currently with 16.04.1 and 16.04.2, these symlinks are not getting
created.

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

Title:
5U84 - ses driver isn't binding right - cannot blink lights on 1 of
the 2 5u84

Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
In Progress
Status in linux source package in Zesty:
In Progress
Status in linux source package in Artful:
Fix Released

Bug description:

== SRU Justification ==
This bug is resolved by commit 62e62ffd95539b9220894a7900a619e0f3ef4756.

Without this patch, the symlink in sysfs which binds a SAS device to an
enclosure
slot does not get created. This makes disk hotplug near impossible on large
JBOD disk drawers.

Commit 62e62ffd95 is also needed in Xenial. However, Xenial also needed some
prereq commits, so it's SRU will be sent separately.

Commit 62e62ffd95 is in mainline as of 4.13-rc1.

== Fix ==
commit 62e62ffd95539b9220894a7900a619e0f3ef4756
Author: Maurizio Lombardi
Date: Tue Jun 27 11:53:27 2017 +0200

scsi: ses: do not add a device to an enclosure if
enclosure_add_links() fails.

== Regression Potential ==
This patch was also cc'd and applied to upstream stable, so there is
upstream confidence in it.

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

This is a request to add the following upstream commit to both Ubuntu 16.04.1
and 16.04.2:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/scsi/ses.c?id=9373eba6cfae48911b977d14323032cd5d161aae

Without this patch, the symlink in sysfs which binds a SAS device to
an enclosure slot does not get created. This makes disk hotplug near
impossible on large JBOD disk drawers.

You should be able to do:

ls /sys/block/sdb/device/ | grep enclosure

and see something like:

enclosure_device:1

If you cd to this directory, you can then access the SES controls for
that slot to flash the LED to assist in locating the disk to replace a
failed disk.

Currently with 16.04.1 and 16.04.2, these symlinks are not getting
created.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1693369/+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 1712580] Re: [SRU][Zesty]PCI: Add pci_mmap_resource_range() and use it for ARM64

** Description changed:

  [Impact]
  uio device binding inside VM would fail with errors
  EAL: Detected 3 lcore(s)
  EAL: Probing VFIO support...
  EAL: PCI device :00:01.0 on NUMA socket -1
  EAL: probe driver: 1af4:1000 net_virtio
  EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource1: No such file or 
directory
  EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource0: No such file or 
directory
  EAL: Error - exiting with code: 1
    Cause: Requested device :00:01.0 cannot be used
  
  [Fix]
  Fixed in linus kernel 4.13 by patch David Woodhouse (4):
  PCI: Move multiple declarations of pci_mmap_page_range() to 
  PCI: Use BAR index in sysfs attr->private instead of resource pointer
  PCI: Add BAR index argument to pci_mmap_page_range()
  PCI: Add pci_mmap_resource_range() and use it for ARM64
  
  [Test]
  Please see comment #3 and comment #4 for ARM64 testing, and subsequent 
comments for testing on other arches.
  
  [Regression Potential]
- Patch touches PCI subsystem on all architectures, and PCI drivers. Regression 
tested on ARM64.
+ Patch touches PCI subsystem on all architectures, and PCI drivers. Regression 
tested on ARM64, ppc64el and AMD64.

** Description changed:

  [Impact]
  uio device binding inside VM would fail with errors
  EAL: Detected 3 lcore(s)
  EAL: Probing VFIO support...
  EAL: PCI device :00:01.0 on NUMA socket -1
  EAL: probe driver: 1af4:1000 net_virtio
  EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource1: No such file or 
directory
  EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource0: No such file or 
directory
  EAL: Error - exiting with code: 1
    Cause: Requested device :00:01.0 cannot be used
  
  [Fix]
  Fixed in linus kernel 4.13 by patch David Woodhouse (4):
  PCI: Move multiple declarations of pci_mmap_page_range() to 
  PCI: Use BAR index in sysfs attr->private instead of resource pointer
  PCI: Add BAR index argument to pci_mmap_page_range()
  PCI: Add pci_mmap_resource_range() and use it for ARM64
  
  [Test]
- Please see comment #3 and comment #4 for ARM64 testing, and subsequent 
comments for testing on other arches.
+ Please see comment #3 and comment #4 for ARM64 testing on QDF2400 system, and 
subsequent comments for testing on other arches.
  
  [Regression Potential]
  Patch touches PCI subsystem on all architectures, and PCI drivers. Regression 
tested on ARM64, ppc64el and AMD64.

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

Title:
  [SRU][Zesty]PCI: Add pci_mmap_resource_range() and use it for ARM64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  uio device binding inside VM would fail with errors
  EAL: Detected 3 lcore(s)
  EAL: Probing VFIO support...
  EAL: PCI device :00:01.0 on NUMA socket -1
  EAL: probe driver: 1af4:1000 net_virtio
  EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource1: No such file or 
directory
  EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource0: No such file or 
directory
  EAL: Error - exiting with code: 1
    Cause: Requested device :00:01.0 cannot be used

  [Fix]
  Fixed in linus kernel 4.13 by patch David Woodhouse (4):
  PCI: Move multiple declarations of pci_mmap_page_range() to 
  PCI: Use BAR index in sysfs attr->private instead of resource pointer
  PCI: Add BAR index argument to pci_mmap_page_range()
  PCI: Add pci_mmap_resource_range() and use it for ARM64

  [Test]
  Please see comment #3 and comment #4 for ARM64 testing on QDF2400 system, and 
subsequent comments for testing on other arches.

  [Regression Potential]
  Patch touches PCI subsystem on all architectures, and PCI drivers. Regression 
tested on ARM64, ppc64el and AMD64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1712580/+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 1712580] Re: [SRU][Zesty]PCI: Add pci_mmap_resource_range() and use it for ARM64

= Testing ppc64el =

== Before the patch ==
ubuntu@cameron:~$ lspci | grep PCIe
0005:05:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0005:05:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0005:05:00.2 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0005:05:00.3 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)

ubuntu@cameron:~$ ls /sys/bus/pci/devices/0005\:05\:00.0/resource*
/sys/bus/pci/devices/0005:05:00.0/resource
/sys/bus/pci/devices/0005:05:00.0/resource0
/sys/bus/pci/devices/0005:05:00.0/resource0_wc
/sys/bus/pci/devices/0005:05:00.0/resource2
/sys/bus/pci/devices/0005:05:00.0/resource2_wc
/sys/bus/pci/devices/0005:05:00.0/resource4
/sys/bus/pci/devices/0005:05:00.0/resource4_wc

== After the patch ==
ubuntu@cameron:~$ uname -a 
Linux cameron 4.10.0-33-generic #37~lp1712580+build.3-Ubuntu SMP Thu Aug 24 
18:56:29 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

ubuntu@cameron:~$ lspci | grep PCIe
0005:05:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0005:05:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0005:05:00.2 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0005:05:00.3 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)

ubuntu@cameron:~$ ls /sys/bus/pci/devices/0005\:05\:00.0/resource*
/sys/bus/pci/devices/0005:05:00.0/resource
/sys/bus/pci/devices/0005:05:00.0/resource0
/sys/bus/pci/devices/0005:05:00.0/resource0_wc
/sys/bus/pci/devices/0005:05:00.0/resource2
/sys/bus/pci/devices/0005:05:00.0/resource2_wc
/sys/bus/pci/devices/0005:05:00.0/resource4
/sys/bus/pci/devices/0005:05:00.0/resource4_wc


** Description changed:

  [Impact]
  uio device binding inside VM would fail with errors
  EAL: Detected 3 lcore(s)
  EAL: Probing VFIO support...
  EAL: PCI device :00:01.0 on NUMA socket -1
  EAL: probe driver: 1af4:1000 net_virtio
  EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource1: No such file or 
directory
  EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource0: No such file or 
directory
  EAL: Error - exiting with code: 1
    Cause: Requested device :00:01.0 cannot be used
  
  [Fix]
  Fixed in linus kernel 4.13 by patch David Woodhouse (4):
  PCI: Move multiple declarations of pci_mmap_page_range() to 
  PCI: Use BAR index in sysfs attr->private instead of resource pointer
  PCI: Add BAR index argument to pci_mmap_page_range()
  PCI: Add pci_mmap_resource_range() and use it for ARM64
  
  [Test]
- Please see comment #3 and comment #4
+ Please see comment #3 and comment #4 for ARM64 testing, and subsequent 
comments for testing on other arches.
  
  [Regression Potential]
  Patch touches PCI subsystem on all architectures, and PCI drivers. Regression 
tested on ARM64.

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

Title:
  [SRU][Zesty]PCI: Add pci_mmap_resource_range() and use it for ARM64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  uio device binding inside VM would fail with errors
  EAL: Detected 3 lcore(s)
  EAL: Probing VFIO support...
  EAL: PCI device :00:01.0 on NUMA socket -1
  EAL: probe driver: 1af4:1000 net_virtio
  EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource1: No such file or 
directory
  EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource0: No such file or 
directory
  EAL: Error - exiting with code: 1
    Cause: Requested device :00:01.0 cannot be used

  [Fix]
  Fixed in linus kernel 4.13 by patch David Woodhouse (4):
  PCI: Move multiple declarations of pci_mmap_page_range() to 
  PCI: Use BAR index in sysfs attr->private instead of resource pointer
  PCI: Add BAR index argument to pci_mmap_page_range()
  PCI: Add pci_mmap_resource_range() and use it for ARM64

  [Test]
  Please see comment #3 and comment #4 for ARM64 testing, and subsequent 
comments for testing on other arches.

  [Regression Potential]
  Patch touches PCI subsystem on all architectures, and PCI drivers. Regression 
tested on ARM64, ppc64el and AMD64.

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

** Changed in: kernel-development-workflow/automated-testing
   Status: Incomplete => Fix Released

** Changed in: kernel-development-workflow/promote-to-release
   Status: New => Confirmed

** Tags removed: block-proposed-artful

** Tags removed: block-proposed

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

Title:
  linux: 4.13.0-11.12 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  Confirmed
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  This bug is for tracking the 4.13.0-11.12 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-development-workflow/+bug/1716699/+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

Re: [Kernel-packages] [Bug 1710716] Re: kernel-oops Bad page state in process sh

2017-09-20 Thread Benjamin Werthmann

I have not seen this issue since upgrading to 3.13.0-129-generic.

On Wed, Aug 16, 2017 at 10:18 AM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:

> Did this issue start happening after an update/upgrade?  Was there a
> prior kernel version where you were not having this particular problem?
>
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.13 kernel[0].
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".
>
>
> Thanks in advance.
>
> [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc4
>
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Medium
>
> ** Tags added: kernel-da-key trusty
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1710716
>
> Title:
>   kernel-oops Bad page state in process sh
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Seeing this on an AWS c4.8xlarge. Running linux-
>   image-3.13.0-108.155-generic
>
>   [201186.215054] BUG: Bad page state in process sh  pfn:7dc276
>   [201186.215055] page:ea001f709d80 count:1 mapcount:0
> mapping:880764b72ee9 index:0x2
>   [201186.215056] page flags: 0x6089b080078(uptodate|
> dirty|lru|active|swapbacked)
>   [201186.215067] Modules linked in: nfsv4 xt_conntrack cls_fw xt_nat
> iptable_nat nf_nat_ipv4 nf_nat xt_mark iptable_mangle veth aufs xt_tcpudp
> xt_LOG xt_limit iptable_filter ip_tables x_tables sch_sfq sch_htb
> openvswitch gre vxlan ip_tunnel libcrc32c dm_crypt nfsd auth_rpcgss nfs_acl
> nfs lockd sunrpc fscache i2c_piix4 serio_raw mac_hid nf_conntrack_ipv4
> nf_defrag_ipv4 nf_conntrack isofs crct10dif_pclmul crc32_pclmul
> ghash_clmulni_intel cirrus aesni_intel syscopyarea sysfillrect aes_x86_64
> sysimgblt lrw gf128mul ttm glue_helper drm_kms_helper ablk_helper cryptd
> drm psmouse ixgbevf floppy pata_acpi
>   [201186.215068] CPU: 25 PID: 14770 Comm: sh Tainted: GB
>  3.13.0-108.155-generic #apcera1
>   [201186.215069] Hardware name: Xen HVM domU, BIOS 4.2.amazon 02/16/2017
>   [201186.215071]   8807c8bffaf0 8172d229
> ea001f709d80
>   [201186.215073]  880ef0f365b8 8807c8bffb08 81727a27
> 0032
>   [201186.215075]  8807c8bffbe8 8115ccea 880f0ffc3e08
> 0002
>   [201186.215075] Call Trace:
>   [201186.215077]  [] dump_stack+0x64/0x82
>   [201186.215078]  [] bad_page.part.61+0xcf/0xe8
>   [201186.215080]  [] get_page_from_freelist+0x84a/0x920
>   [201186.215081]  [] __alloc_pages_nodemask+0x1a3/0xb90
>   [201186.215084]  [] ? si_read_lock+0x6d/0x110 [aufs]
>   [201186.215088]  [] ? aufs_permission+0x190/0x310
> [aufs]
>   [201186.215089]  [] ? down_write+0x12/0x30
>   [201186.215092]  [] ? di_write_lock+0x1f/0x40 [aufs]
>   [201186.215093]  [] ? radix_tree_lookup_slot+0xe/0x10
>   [201186.215095]  [] ? unlock_page+0x23/0x30
>   [201186.215096]  [] alloc_pages_vma+0x9a/0x140
>   [201186.215098]  [] handle_mm_fault+0xbb1/0xf10
>   [201186.215100]  [] ? vma_link+0xb7/0xc0
>   [201186.215101]  [] __do_page_fault+0x184/0x560
>   [201186.215103]  [] ? do_mmap_pgoff+0x34e/0x3d0
>   [201186.215105]  [] ? vm_mmap_pgoff+0x99/0xc0
>   [201186.215106]  [] do_page_fault+0x1a/0x70
>   [201186.215108]  [] page_fault+0x28/0x30
>
>   $ cat /proc/version_signature
>   Ubuntu 3.13.0-108.155.apcera1-generic 3.13.11-ckt39
>
>   $ lspci -vnvn
>   00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC
> [Natoma] [8086:1237] (rev 02)
>   Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100]
>   Physical Slot: 0
>   Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B- DisINTx-
>   Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> SERR-Latency: 0
>
>   00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA
> [Natoma/Triton II] [8086:7000]
>   Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100]
>   Physical Slot: 1
>   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B- DisINTx-
>   Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> SERR-Latency: 0
>
>   00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE
> [Natoma/Triton II] [8086:7010] (prog-if 80 [Master])
>   Subsystem: XenSource, Inc. Device [5853:0001]
>   Physical Slot: 1
>   Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B- DisINTx-
>   Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> SERR-

[Kernel-packages] [Bug 1718149] Re: linux: 4.4.0-97.120 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => 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/1718149

Title:
  linux: 4.4.0-97.120 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
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:
  In Progress
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: 1718150,1718151
  derivatives: 1718153,1718154,1718155,1718156,1718157
  -- 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/1718149/+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 1712580] Re: [SRU][Zesty]PCI: Add pci_mmap_resource_range() and use it for ARM64

** Description changed:

  [Impact]
  uio device binding inside VM would fail with errors
  EAL: Detected 3 lcore(s)
  EAL: Probing VFIO support...
  EAL: PCI device :00:01.0 on NUMA socket -1
  EAL: probe driver: 1af4:1000 net_virtio
  EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource1: No such file or 
directory
  EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource0: No such file or 
directory
  EAL: Error - exiting with code: 1
-   Cause: Requested device :00:01.0 cannot be used
+   Cause: Requested device :00:01.0 cannot be used
  
  [Fix]
- Fixed in linus kernel by patch 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm64/include/asm/pci.h?h=v4.13-rc4=f719582435afe9c7985206e42d804ea6aa315d33
+ Fixed in linus kernel 4.13 by patch David Woodhouse (4):
+ PCI: Move multiple declarations of pci_mmap_page_range() to 
+ PCI: Use BAR index in sysfs attr->private instead of resource pointer
+ PCI: Add BAR index argument to pci_mmap_page_range()
+ PCI: Add pci_mmap_resource_range() and use it for ARM64
  
  [Test]
+ Please see comment #3 and comment #4
  
  [Regression Potential]
+ Patch touches PCI subsystem on all architectures, and PCI drivers. Regression 
tested on ARM64.

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

Title:
  [SRU][Zesty]PCI: Add pci_mmap_resource_range() and use it for ARM64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  uio device binding inside VM would fail with errors
  EAL: Detected 3 lcore(s)
  EAL: Probing VFIO support...
  EAL: PCI device :00:01.0 on NUMA socket -1
  EAL: probe driver: 1af4:1000 net_virtio
  EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource1: No such file or 
directory
  EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource0: No such file or 
directory
  EAL: Error - exiting with code: 1
    Cause: Requested device :00:01.0 cannot be used

  [Fix]
  Fixed in linus kernel 4.13 by patch David Woodhouse (4):
  PCI: Move multiple declarations of pci_mmap_page_range() to 
  PCI: Use BAR index in sysfs attr->private instead of resource pointer
  PCI: Add BAR index argument to pci_mmap_page_range()
  PCI: Add pci_mmap_resource_range() and use it for ARM64

  [Test]
  Please see comment #3 and comment #4

  [Regression Potential]
  Patch touches PCI subsystem on all architectures, and PCI drivers. Regression 
tested on ARM64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1712580/+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 1712580] Re: [SRU][Zesty]PCI: Add pci_mmap_resource_range() and use it for ARM64

= Testing =

== Before applying the patch ==
$ lspci 
:00:00.0 PCI bridge: Airgo Networks, Inc. Device 0401
:01:00.0 Ethernet controller: Mellanox Technologies MT27700 Family 
[ConnectX-4]
0004:00:00.0 PCI bridge: Airgo Networks, Inc. Device 0401
0005:00:00.0 PCI bridge: Airgo Networks, Inc. Device 0401

$ ls /sys/bus/pci/devices/\:01\:00.0/resource*
/sys/bus/pci/devices/:01:00.0/resource

== After applying the patch ==
$ ls /sys/bus/pci/devices/\:01\:00.0/resource*
/sys/bus/pci/devices/:01:00.0/resource
/sys/bus/pci/devices/:01:00.0/resource0
/sys/bus/pci/devices/:01:00.0/resource0_wc

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

Title:
  [SRU][Zesty]PCI: Add pci_mmap_resource_range() and use it for ARM64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  uio device binding inside VM would fail with errors
  EAL: Detected 3 lcore(s)
  EAL: Probing VFIO support...
  EAL: PCI device :00:01.0 on NUMA socket -1
  EAL: probe driver: 1af4:1000 net_virtio
  EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource1: No such file or 
directory
  EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource0: No such file or 
directory
  EAL: Error - exiting with code: 1
Cause: Requested device :00:01.0 cannot be used

  [Fix]
  Fixed in linus kernel by patch 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm64/include/asm/pci.h?h=v4.13-rc4=f719582435afe9c7985206e42d804ea6aa315d33

  [Test]

  [Regression Potential]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1712580/+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 1712580] Re: [SRU][Zesty]PCI: Add pci_mmap_resource_range() and use it for ARM64

>From WuFan:

HI Manoj,

Sorry for the delay. I haven't got chance to test your patch but I do
find a (much) simple way to verify it. In a working system you have:

/home/ubuntu>ls /sys/bus/pci/devices/0002\:01\:00.0/resource*
/sys/bus/pci/devices/0002:01:00.0/resource
/sys/bus/pci/devices/0002:01:00.0/resource0
/sys/bus/pci/devices/0002:01:00.0/resource1
/sys/bus/pci/devices/0002:01:00.0/resource2

While a failing system has this:

ubuntu@controller:~$ ls /sys/bus/pci/devices/0002\:01\:00.0/resource*
/sys/bus/pci/devices/0002:01:00.0/resource

Here the PCI device could be any PCIe NIC.

Thanks,
Fan

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

Title:
  [SRU][Zesty]PCI: Add pci_mmap_resource_range() and use it for ARM64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  uio device binding inside VM would fail with errors
  EAL: Detected 3 lcore(s)
  EAL: Probing VFIO support...
  EAL: PCI device :00:01.0 on NUMA socket -1
  EAL: probe driver: 1af4:1000 net_virtio
  EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource1: No such file or 
directory
  EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource0: No such file or 
directory
  EAL: Error - exiting with code: 1
Cause: Requested device :00:01.0 cannot be used

  [Fix]
  Fixed in linus kernel by patch 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm64/include/asm/pci.h?h=v4.13-rc4=f719582435afe9c7985206e42d804ea6aa315d33

  [Test]

  [Regression Potential]

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

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => 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/1718143

Title:
  linux: 4.10.0-36.40 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
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:
  In Progress
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 Zesty:
  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: 1718145,1718146
  derivatives: 1718147
  -- 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/1718143/+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 1715609] Re: kernel warning: skb_warn_bad_offload

It might also be good to test the latest mainline kernel.  This will
tell us if this commit needs to be reverted, or if there are other
commits in mainline that might be needed in combination with
b2504a5dbef.

The latest mainline kernel can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc1/

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

Title:
  kernel warning: skb_warn_bad_offload

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  Since upgrading to kernel version 4.10.0-33.37, we're seeing a lot of
  call traces triggered by skb_warn_bad_offload in the syslog.

  Regression introduced when fixing this bug?
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705447


  kernel: [570943.49] [ cut here ]
  kernel: [570943.494448] WARNING: CPU: 3 PID: 21982 at 
/build/linux-hwe-YA6IuF/linux-hwe-4.10.0/net/core/dev.c:2576 
skb_warn_bad_offload+0xd1/0x120
  kernel: [570943.494450] e1000e: caps=(0x0030002149a9, 0x) 
len=1701 data_len=1659 gso_size=1480 gso_type=2 ip_summed=0
  kernel: [570943.494451] Modules linked in: udp_diag tcp_diag inet_diag 
echainiv authenc xfrm4_mode_tunnel xt_state binfmt_misc veth xfrm_user 
xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfrm_algo bridge stp 
llc iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_nat_ipv4 nf_nat ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter ip_tables x_tables 
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm ppdev 
irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel 
aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf hci_uart 
ie31200_edac btbcm edac_core intel_pch_thermal btqca serio_raw btintel 
bluetooth parport_pc parport mac_hid intel_lpss_acpi acpi_pad intel_lpss autofs4
  kernel: [570943.494500]  btrfs raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 
e1000e psmouse ptp ahci pps_core libahci wmi pinctrl_sunrisepoint i2c_hid video 
pinctrl_intel hid fjes
  kernel: [570943.494524] CPU: 3 PID: 21982 Comm: charon Tainted: GW
   4.10.0-33-generic #37~16.04.1-Ubuntu
  kernel: [570943.494524] Hardware name: ...
  kernel: [570943.494525] Call Trace:
  kernel: [570943.494541]  
  kernel: [570943.494544]  dump_stack+0x63/0x90
  kernel: [570943.494545]  __warn+0xcb/0xf0
  kernel: [570943.494546]  warn_slowpath_fmt+0x5f/0x80
  kernel: [570943.494547]  ? ___ratelimit+0xa2/0xf0
  kernel: [570943.494549]  skb_warn_bad_offload+0xd1/0x120
  kernel: [570943.494550]  __skb_gso_segment+0x17d/0x190
  kernel: [570943.494564]  validate_xmit_skb+0x14f/0x2a0
  kernel: [570943.494565]  validate_xmit_skb_list+0x43/0x70
  kernel: [570943.494567]  sch_direct_xmit+0x16b/0x1c0
  kernel: [570943.494568]  __dev_queue_xmit+0x47e/0x690
  kernel: [570943.494569]  dev_queue_xmit+0x10/0x20
  kernel: [570943.494570]  ip_finish_output2+0x27a/0x370
  kernel: [570943.494571]  ip_finish_output+0x176/0x270
  kernel: [570943.494571]  ip_output+0x76/0xe0
  kernel: [570943.494572]  ? ip_fragment.constprop.49+0x80/0x80
  kernel: [570943.494573]  ip_forward_finish+0x43/0x70
  kernel: [570943.494574]  ip_forward+0x385/0x460
  kernel: [570943.494575]  ? ip_frag_mem+0x50/0x50
  kernel: [570943.494575]  ip_rcv_finish+0x11b/0x400
  kernel: [570943.494576]  ip_rcv+0x28b/0x3a0
  ...
  kernel: [570943.494632] ---[ end trace f01d0adcc1256afe ]---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715609/+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 1708130] Re: ISST-LTE: Ubuntu16.04.03: PowerNV: 'ppc64_cpu' commands hangs while changing SMT value with Leaf IO and BASE tests

@Mauricio,  I was just wondering if there was results from the testing
mentioned in comment #18?

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

Title:
  ISST-LTE: Ubuntu16.04.03: PowerNV: 'ppc64_cpu' commands hangs while
  changing SMT value with Leaf IO and BASE tests

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

Bug description:
  == Comment: #0 - INDIRA P. JOGA  - 2017-07-07 
03:56:54 ==
  Description:
  --
  Started Leaf IO and BASE(without smt tests)and then tried to change the SMT 
value manually where it hangs

UBUNTU BUILD: 4.10.0-26-generic

  Steps to re-create:
  --
  > Installed latest Ubuntu160403 kernel on system lotkvm
  4.10.0-26-generic

  > Leaf microcode: KMIPP113

  > Started Leaf IO and BASE tests(without smt tests).

  root@lotkvm:/home# show.report.py
  HOSTNAMEKERNEL VERSION   DISTRO INFO
  ----
  lotkvm  4.10.0-26-genericUbuntu 16.04.2 LTS \n \l

   Current Time: Tue Jul  4 00:55:37 2017 
  Job-IDFOCUS   Start-Time  DurationFunction
  ---   --  
  1 IO  20170704-00:44:45   0.0 hr(s) 10.0 min(s)   IO_Focus
  2 BASE20170704-00:44:52   0.0 hr(s) 10.0 min(s)   Test

  FOCUS IO  BASESUM
  TOTAL 76  25  101
  FAIL  0   4   4
  PASS  76  21  97
  (%)   (100%)  (84%)   (96%)

  >Now manually changed the smt value

  root@lotkvm:/home# ppc64_cpu --smt
  SMT=8
  root@lotkvm:/home# date
  Tue Jul  4 00:46:01 CDT 2017
  root@lotkvm:/home# ppc64_cpu --smt=2
  root@lotkvm:/home# ppc64_cpu --smt
  SMT=2
  root@lotkvm:/home# date
  Tue Jul  4 00:50:01 CDT 2017
  root@lotkvm:/home# ppc64_cpu --smt=4
  root@lotkvm:/home# ppc64_cpu --smt
  SMT=4
  root@lotkvm:/home# date
  Tue Jul  4 00:54:38 CDT 2017
  root@lotkvm:/home# ppc64_cpu --smt=8

  
  [ 2055.142781] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 
seconds.
  [ 2055.142915]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.142978] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.143150] INFO: task kworker/48:0H:21755 blocked for more than 120 
seconds.
  [ 2055.143226]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.143289] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.143570] INFO: task kworker/u259:3:22436 blocked for more than 120 
seconds.
  [ 2055.143647]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.143709] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.143953] INFO: task kworker/8:188:118516 blocked for more than 120 
seconds.
  [ 2055.144029]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144091] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.144289] INFO: task mkfs.ntfs:95505 blocked for more than 120 seconds.
  [ 2055.144353]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.144600] INFO: task ppc64_cpu:80305 blocked for more than 120 seconds.
  [ 2055.144665]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144727] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.144872] INFO: task rm:80950 blocked for more than 120 seconds.
  [ 2055.144936]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144998] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.145133] INFO: task rm:80951 blocked for more than 120 seconds.
  [ 2055.145195]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.145257] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2175.974718] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 
seconds.
  [ 2175.974848]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2175.974912] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2175.975068] INFO: task kworker/48:0H:21755 blocked for more than 120 
seconds.
  [ 2175.975144]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2175.975206] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  
  >  root@lotkvm:# ps -eaf | grep ppc*
  root  48054  12068  0 01:24 pts/000:00:00 grep --color=auto ppc*
  root  80305   5719  0 00:54 hvc0 00:00:00 ppc64_cpu --smt 8

  > ppc64_cpu --smt command hangs here . Not able to change the SMT
  value from 4 to 8.

  > Attached dmesg logs

  == Comment:

[Kernel-packages] [Bug 1718149] Re: linux: 4.4.0-97.120 -proposed tracker

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

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 4.4.0-97.120 -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:
  In Progress
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: 1718150,1718151
  derivatives: 1718153,1718154,1718155,1718156,1718157
  -- 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/1718149/+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 1718143] Re: linux: 4.10.0-36.40 -proposed tracker

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

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 4.10.0-36.40 -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:
  In Progress
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 Zesty:
  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: 1718145,1718146
  derivatives: 1718147
  -- 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/1718143/+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 1715741] Re: Wi-Fi broken in 16.04.3 and later on Dell Edge 3003

I removed linux-image-extras-4.4.0-87, which made it update to kernel
4.4.0-96.  The update seemed to do something to the 4.14 intramfs, it
made no difference.  4.14 panics.

What am I missing?

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

Title:
  Wi-Fi broken in 16.04.3 and later on Dell Edge 3003

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The built-in Wi-Fi on the Dell Edge 3003 is not working.  It works in
  16.04.1 but not in 16.04.3 or 17.04.  Both server and desktop versions
  were tested.  The Wi-Fi device is an RSI 915 connected on the SDIO
  bus.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715741/+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 1713576] Re: More migrations with constant load

** Description changed:

+ == SRU Justification ==
+ There is a significantly higher number of task migrations when the load is 
+ fixed and not balanced across cores.
+ 
+ Benchmark results are posted in the bug description and in the commits
+ git log.
+ 
+ This bug is resolved by mainline commit 
05b40e057734811ce452344fb3690d09965a7b6a, which is 
+ in mailine as of 4.12-rc1.
+ 
+ 
+ == Fix ==
+ commit 05b40e057734811ce452344fb3690d09965a7b6a
+ Author: Srikar Dronamraju 
+ Date:   Wed Mar 22 23:27:50 2017 +0530
+ 
+ sched/fair: Prefer sibiling only if local group is under-utilized
+ 
+ == Regression Potential ==
+ Medium, since this commit does touch the scheduler.  However, the commit only 
makes a change to 
+ allow a local group to pull a task, if the source group has more number of 
+ tasks than the local group.
+ 
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug 
reporter.
+ The bug reporter states the test kernel resolved the bug.
+ 
+ 
+ 
  == Comment: #0 - PUVICHAKRAVARTHY RAMACHANDRAN  - 2017-08-06 13:44:45 ==
  ---Problem Description---
  Significantly higher number of task migrations when the load is fixed but not 
balanced across cores.
-  
+ 
  ---uname output---
  Linux isvbos3 4.10.0-29-generic #33~16.04.1-Ubuntu SMP Tue Jul 25 18:17:06 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
-  
+ 
  ---Additional Hardware Info---
- Power9 dd2.0 
+ Power9 dd2.0
  
- Machine Type = Power9 
-  
+ Machine Type = Power9
+ 
  ---Steps to Reproduce---
-  Benchmark : Multithreaded - cpu intensive. The system had 2 socket/ 32 
cores/ SMT4 mode.
+  Benchmark : Multithreaded - cpu intensive. The system had 2 socket/ 32 
cores/ SMT4 mode.
  
  When 64 threads was run - the migrations were less over 10s interval.
  when 80 threads were run - the migrations were very high.
  
- Ideally, it should have been very minimal, as the over all load was constant
-  
+ Ideally, it should have been very minimal, as the over all load was
+ constant
+ 
  == Comment: #3 - SRIKAR DRONAMRAJU - 2017-08-11 06:56:47 ==
  As suspected (commit :  05b40e0577 : "sched/fair: Prefer sibiling only if 
local group is under-utilized")
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=05b40e0577
  should fix the problem
  
  Ran ' perf stat -a -r 5 -e sched:sched_migrate_task 
/home/srikar/work/ebizzy-0.3/ebizzy -t 35 -S 100'
  to detect the problem and verify the fix
  
  Here is perf stat without fix.
  
  Performance counter stats for 'system wide' (5 runs):
  
-  7,758  sched:sched_migrate_task
+  7,758  sched:sched_migrate_task
  ( +-  1.28% )
  
-  100.015658079 seconds time elapsed
+  100.015658079 seconds time elapsed
  ( +-  0.00% )
  
  perf stat with fix.
  
  Performance counter stats for 'system wide' (5 runs):
  
-415  sched:sched_migrate_task
+    415  sched:sched_migrate_task
  ( +- 11.74% )
  
-  100.016021787 seconds time elapsed
+  100.016021787 seconds time elapsed
  ( +-  0.00% )
- 
  
  git describe on upstream kernel says v4.11-rc2
  # git describe 05b40e0577
  v4.11-rc2-227-g05b40e0
  
  == Comment: #4 - SRIKAR DRONAMRAJU - 2017-08-11 07:05:37 ==
  Attaching the patch that needs to be applied to fix this bug.
  Verified that patch fixes the problem.

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

Title:
  More migrations with constant load

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

Bug description:
  == SRU Justification ==
  There is a significantly higher number of task migrations when the load is 
  fixed and not balanced across cores.

  Benchmark results are posted in the bug description and in the commits
  git log.

  This bug is resolved by mainline commit 
05b40e057734811ce452344fb3690d09965a7b6a, which is 
  in mailine as of 4.12-rc1.

  
  == Fix ==
  commit 05b40e057734811ce452344fb3690d09965a7b6a
  Author: Srikar Dronamraju 
  Date:   Wed Mar 22 23:27:50 2017 +0530

  sched/fair: Prefer sibiling only if local group is under-utilized

  == Regression Potential ==
  Medium, since this commit does touch the scheduler.  However, the commit only 
makes a change to 
  allow a local group to pull a task, if the source group has more number of 
  tasks than the local group.

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


  
  == Comment: #0 - PUVICHAKRAVARTHY RAMACHANDRAN  - 2017-08-06 13:44:45 ==
  ---Problem Description---
  Significantly higher number of task migrations when the load is fixed but not 
balanced across cores.

  ---uname output---

[Kernel-packages] [Bug 1715741] Re: Wi-Fi broken in 16.04.3 and later on Dell Edge 3003

The instructions for installing kernels says I might need to remove
'extras' packages.

How do I do this correctly?
Do I need a new linux-image-extras for 4.14?

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

Title:
  Wi-Fi broken in 16.04.3 and later on Dell Edge 3003

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The built-in Wi-Fi on the Dell Edge 3003 is not working.  It works in
  16.04.1 but not in 16.04.3 or 17.04.  Both server and desktop versions
  were tested.  The Wi-Fi device is an RSI 915 connected on the SDIO
  bus.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715741/+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 1716491] Re: New PMU fixes for marked events.

** Description changed:

+ == SRU Justification ==
+ The current Zesty kernel does not enable marked events on Power9. The 
+ following fixes are required:
+ 
+ 101dd590a7fa ("powerpc/perf: Avoid spurious PMU interrupts after idle")
+ 09539f9b1236 ("powerpc/perf: POWER9 PMU stops after idle workaround")
+ 
+ Commit 101dd590a7fa was added to mainline in v4.13-rc3 and commit 
09539f9b1236 
+ was added in v4.13-rc4.
+ 
+ 
+ == Fixes ==
+ commit 101dd590a7fa37954540cf3149a1c502c0acc524
+ Author: Nicholas Piggin 
+ Date:   Mon Jul 10 16:19:38 2017 +1000
+ 
+ powerpc/perf: Avoid spurious PMU interrupts after idle
+ 
+ commit 09539f9b123652e969894d6299ae0df2fe12cb5d
+ Author: Nicholas Piggin 
+ Date:   Thu Jul 20 11:53:22 2017 +1000
+ 
+ powerpc/perf: POWER9 PMU stops after idle workaround
+ 
+ 
+ == Regression Potential ==
+ Low, since these commits are specific to powerpc.
+ 
+ 
+ 
  Dear Canonical,
  
  Please include the following fixes into Ubuntu Zesty (4.10) kernel. The
  current kernel does not enable marked events on Power9. And the
  following fixes are required:
  
  09539f9b1236 ("powerpc/perf: POWER9 PMU stops after idle workaround")
  101dd590a7fa ("powerpc/perf: Avoid spurious PMU interrupts after idle")

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

Title:
  New PMU fixes for marked events.

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

Bug description:
  == SRU Justification ==
  The current Zesty kernel does not enable marked events on Power9. The 
  following fixes are required:

  101dd590a7fa ("powerpc/perf: Avoid spurious PMU interrupts after idle")
  09539f9b1236 ("powerpc/perf: POWER9 PMU stops after idle workaround")

  Commit 101dd590a7fa was added to mainline in v4.13-rc3 and commit 
09539f9b1236 
  was added in v4.13-rc4.

  
  == Fixes ==
  commit 101dd590a7fa37954540cf3149a1c502c0acc524
  Author: Nicholas Piggin 
  Date:   Mon Jul 10 16:19:38 2017 +1000

  powerpc/perf: Avoid spurious PMU interrupts after idle

  commit 09539f9b123652e969894d6299ae0df2fe12cb5d
  Author: Nicholas Piggin 
  Date:   Thu Jul 20 11:53:22 2017 +1000

  powerpc/perf: POWER9 PMU stops after idle workaround

  
  == Regression Potential ==
  Low, since these commits are specific to powerpc.


  
  Dear Canonical,

  Please include the following fixes into Ubuntu Zesty (4.10) kernel.
  The current kernel does not enable marked events on Power9. And the
  following fixes are required:

  09539f9b1236 ("powerpc/perf: POWER9 PMU stops after idle workaround")
  101dd590a7fa ("powerpc/perf: Avoid spurious PMU interrupts after idle")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1716491/+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 1715741] Re: Wi-Fi broken in 16.04.3 and later on Dell Edge 3003

I reloaded Server 16.04.3 LTS, then installed kernel v4.14-rc1 (the
headers, generic headers and generic image debians).  The installation
complained that there possible missing firmware versions for the i915
module.  The kernel panics.

I have not had any luck installing new kernels.  They always panic.
This panic looks the same as the others I reported earlier in this
thread.  And, yes, the backtrace seems to show this is in the RSI SDIO
module.

Help?

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

Title:
  Wi-Fi broken in 16.04.3 and later on Dell Edge 3003

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The built-in Wi-Fi on the Dell Edge 3003 is not working.  It works in
  16.04.1 but not in 16.04.3 or 17.04.  Both server and desktop versions
  were tested.  The Wi-Fi device is an RSI 915 connected on the SDIO
  bus.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715741/+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 1696049] Re: xfstest sanity checks on seek operations fails

I started a "Reverse" kernel bisect between v4.12.rc2 final and
v4.12-rc3. The kernel bisect will require testing of about 7-10 test
kernels.

I built the first test kernel, up to the following commit:
6ce47829113772b1d6b9046f5eaf00e154f0f9de

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1696049

Can you test that kernel and report back if it has the bug or not?  I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  xfstest sanity checks on seek operations fails

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  Fix Released

Bug description:
  == Comment: #0 - Harish Sriram 
  Issue:
  --
  xfstest fails with sanity checks on seek operations

  # uname -a
  Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 
12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Create a loop device with xfs filesystem
  2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd 
xfstests-dev
  3. make
  4. Create a local.config for running with created loop device
  5. Run xfstests-dev test  : ./check tests/generic/285 or ./check 
tests/generic/436

  The test 285 fails with following
  ...
  ...
  07. Test file with unwritten extents, only have dirty pages
  07.01 SEEK_HOLE expected 0 or 45056, got 0.   succ
  07.02 SEEK_HOLE expected 1 or 45056, got 1.   succ
  07.03 SEEK_DATA expected 40960 or 40960, got -1.  FAIL
  07.04 SEEK_DATA expected 40960 or 40960, got -1.  FAIL

  08. Test file with unwritten extents, only have unwritten pages
  08.01 SEEK_HOLE expected 0 or 45056, got 0.   succ
  08.02 SEEK_HOLE expected 1 or 45056, got 1.   succ
  08.03 SEEK_DATA expected 40960 or 40960, got -1.  FAIL
  08.04 SEEK_DATA expected 40960 or 40960, got -1.  FAIL

  The test 436 fails with 
  ...
  ...
  14. Test file with unwritten extents, small hole after pagevec dirty pages
  14.01 SEEK_HOLE expected 917504 or 4194304, got 3670016.  FAIL
  14.02 SEEK_HOLE expected 917504 or 4194304, got 3670016.  FAIL
  14.03 SEEK_HOLE expected 3670016 or 4194304, got 3670016. succ
  14.04 SEEK_DATA expected 0 or 0, got 0.   succ
  14.05 SEEK_DATA expected 1 or 1, got 1.   succ
  14.06 SEEK_DATA expected 2752512 or 2752512, got 2752512. succ

  seek sanity check failed!

  Full log is attached.

  == Comment: #6 - Harish Sriram

  commit 5375023ae1266553a7baa0845e82917d8803f48c
  Author: Jan Kara 
  Date:   Thu May 18 16:36:22 2017 -0700

  xfs: Fix missed holes in SEEK_HOLE implementation
  XFS SEEK_HOLE implementation could miss a hole in an unwritten extent as
  can be seen by the following command:
  
  xfs_io -c "falloc 0 256k" -c "pwrite 0 56k" -c "pwrite 128k 8k"
 -c "seek -h 0" file
  wrote 57344/57344 bytes at offset 0
  56 KiB, 14 ops; 0. sec (49.312 MiB/sec and 12623.9856 ops/sec)
  wrote 8192/8192 bytes at offset 131072
  8 KiB, 2 ops; 0. sec (70.383 MiB/sec and 18018.0180 ops/sec)
  Whence  Result
  HOLE139264
  
  Where we can see that hole at offset 56k was just ignored by SEEK_HOLE
  implementation. The bug is in xfs_find_get_desired_pgoff() which does
  not properly detect the case when pages are not contiguous.
  
  Fix the problem by properly detecting when found page has larger offset
  than expected.
  
  CC: sta...@vger.kernel.org
  Fixes: d126d43f631f996daeee5006714fed914be32368
  Signed-off-by: Jan Kara 
  Reviewed-by: Brian Foster 
  Reviewed-by: Darrick J. Wong 
  Signed-off-by: Darrick J. Wong 

  
  The above commit fixes the generic/436 test, but generic/285 still FAILS.

  The generic/285 failure is reproducible on most P8/P9 systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696049/+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 1718143] Re: linux: 4.10.0-36.40 -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  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: 1718145,1718146
  derivatives: 1718147
- kernel-stable-phase-changed:Tuesday, 19. September 2017 12:32 UTC
- kernel-stable-phase:Uploaded
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Wednesday, 20. September 2017 15:04 UTC

** 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
  
  backports: 1718145,1718146
  derivatives: 1718147
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Wednesday, 20. September 2017 15:04 UTC
+ 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/1718143

Title:
  linux: 4.10.0-36.40 -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 Zesty:
  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: 1718145,1718146
  derivatives: 1718147
  -- 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/1718143/+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 1718149] Re: linux: 4.4.0-97.120 -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  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: 1718150,1718151
  derivatives: 1718153,1718154,1718155,1718156,1718157
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Tuesday, 19. September 2017 18:01 UTC
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Wednesday, 20. September 2017 15:01 UTC

** 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
  
  backports: 1718150,1718151
  derivatives: 1718153,1718154,1718155,1718156,1718157
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Wednesday, 20. September 2017 15:01 UTC
+ 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/1718149

Title:
  linux: 4.4.0-97.120 -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 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: 1718150,1718151
  derivatives: 1718153,1718154,1718155,1718156,1718157
  -- 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/1718149/+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 1718155] Re: linux-aws: 4.4.0-1036.45 -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/1718155

Title:
  linux-aws: 4.4.0-1036.45 -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 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: 1718149
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1718155/+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 1718193] UdevDb.txt

apport information

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

Title:
  NEW RYZEN 7 SYSTEM WAKEUP

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  after waking up - the kernel throws 22 stack traces ...
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   1699 F pulseaudio
   /dev/snd/pcmC2D0p:   dave   1699 F...m pulseaudio
   /dev/snd/controlC2:  dave   1699 F pulseaudio
   /dev/snd/controlC1:  dave   1699 F pulseaudio
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=442028c2-80ef-4fa9-94f9-8d4e3b6284b3
  InstallationDate: Installed on 2017-09-18 (1 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp6s0no wireless extensions.
  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)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=8fce0715-8dd7-462d-9452-0f8a749fba60 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-35-generic N/A
   linux-backports-modules-4.10.0-35-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.10.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.20
  dmi.board.name: X370 Killer SLI
  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.:bvrP3.20:bd08/25/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370KillerSLI:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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/1718193/+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 1718193] ProcModules.txt

apport information

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

Title:
  NEW RYZEN 7 SYSTEM WAKEUP

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  after waking up - the kernel throws 22 stack traces ...
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   1699 F pulseaudio
   /dev/snd/pcmC2D0p:   dave   1699 F...m pulseaudio
   /dev/snd/controlC2:  dave   1699 F pulseaudio
   /dev/snd/controlC1:  dave   1699 F pulseaudio
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=442028c2-80ef-4fa9-94f9-8d4e3b6284b3
  InstallationDate: Installed on 2017-09-18 (1 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp6s0no wireless extensions.
  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)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=8fce0715-8dd7-462d-9452-0f8a749fba60 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-35-generic N/A
   linux-backports-modules-4.10.0-35-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.10.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.20
  dmi.board.name: X370 Killer SLI
  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.:bvrP3.20:bd08/25/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370KillerSLI:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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/1718193/+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 1718193] ProcInterrupts.txt

apport information

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

Title:
  NEW RYZEN 7 SYSTEM WAKEUP

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  after waking up - the kernel throws 22 stack traces ...
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   1699 F pulseaudio
   /dev/snd/pcmC2D0p:   dave   1699 F...m pulseaudio
   /dev/snd/controlC2:  dave   1699 F pulseaudio
   /dev/snd/controlC1:  dave   1699 F pulseaudio
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=442028c2-80ef-4fa9-94f9-8d4e3b6284b3
  InstallationDate: Installed on 2017-09-18 (1 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp6s0no wireless extensions.
  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)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=8fce0715-8dd7-462d-9452-0f8a749fba60 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-35-generic N/A
   linux-backports-modules-4.10.0-35-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.10.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.20
  dmi.board.name: X370 Killer SLI
  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.:bvrP3.20:bd08/25/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370KillerSLI:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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/1718193/+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 1718193] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1718193/+attachment/4953712/+files/ProcEnviron.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/1718193

Title:
  NEW RYZEN 7 SYSTEM WAKEUP

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  after waking up - the kernel throws 22 stack traces ...
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   1699 F pulseaudio
   /dev/snd/pcmC2D0p:   dave   1699 F...m pulseaudio
   /dev/snd/controlC2:  dave   1699 F pulseaudio
   /dev/snd/controlC1:  dave   1699 F pulseaudio
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=442028c2-80ef-4fa9-94f9-8d4e3b6284b3
  InstallationDate: Installed on 2017-09-18 (1 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp6s0no wireless extensions.
  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)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=8fce0715-8dd7-462d-9452-0f8a749fba60 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-35-generic N/A
   linux-backports-modules-4.10.0-35-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.10.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.20
  dmi.board.name: X370 Killer SLI
  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.:bvrP3.20:bd08/25/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370KillerSLI:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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/1718193/+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 1718193] ProcCpuinfoMinimal.txt

apport information

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

Title:
  NEW RYZEN 7 SYSTEM WAKEUP

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  after waking up - the kernel throws 22 stack traces ...
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   1699 F pulseaudio
   /dev/snd/pcmC2D0p:   dave   1699 F...m pulseaudio
   /dev/snd/controlC2:  dave   1699 F pulseaudio
   /dev/snd/controlC1:  dave   1699 F pulseaudio
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=442028c2-80ef-4fa9-94f9-8d4e3b6284b3
  InstallationDate: Installed on 2017-09-18 (1 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp6s0no wireless extensions.
  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)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=8fce0715-8dd7-462d-9452-0f8a749fba60 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-35-generic N/A
   linux-backports-modules-4.10.0-35-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.10.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.20
  dmi.board.name: X370 Killer SLI
  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.:bvrP3.20:bd08/25/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370KillerSLI:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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/1718193/+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 1718193] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1718193/+attachment/4953710/+files/ProcCpuinfo.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/1718193

Title:
  NEW RYZEN 7 SYSTEM WAKEUP

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  after waking up - the kernel throws 22 stack traces ...
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   1699 F pulseaudio
   /dev/snd/pcmC2D0p:   dave   1699 F...m pulseaudio
   /dev/snd/controlC2:  dave   1699 F pulseaudio
   /dev/snd/controlC1:  dave   1699 F pulseaudio
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=442028c2-80ef-4fa9-94f9-8d4e3b6284b3
  InstallationDate: Installed on 2017-09-18 (1 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp6s0no wireless extensions.
  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)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=8fce0715-8dd7-462d-9452-0f8a749fba60 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-35-generic N/A
   linux-backports-modules-4.10.0-35-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.10.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.20
  dmi.board.name: X370 Killer SLI
  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.:bvrP3.20:bd08/25/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370KillerSLI:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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/1718193/+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 1718193] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1718193/+attachment/4953716/+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/1718193

Title:
  NEW RYZEN 7 SYSTEM WAKEUP

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  after waking up - the kernel throws 22 stack traces ...
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   1699 F pulseaudio
   /dev/snd/pcmC2D0p:   dave   1699 F...m pulseaudio
   /dev/snd/controlC2:  dave   1699 F pulseaudio
   /dev/snd/controlC1:  dave   1699 F pulseaudio
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=442028c2-80ef-4fa9-94f9-8d4e3b6284b3
  InstallationDate: Installed on 2017-09-18 (1 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp6s0no wireless extensions.
  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)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=8fce0715-8dd7-462d-9452-0f8a749fba60 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-35-generic N/A
   linux-backports-modules-4.10.0-35-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.10.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.20
  dmi.board.name: X370 Killer SLI
  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.:bvrP3.20:bd08/25/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370KillerSLI:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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/1718193/+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 1718193] Lspci.txt

apport information

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

Title:
  NEW RYZEN 7 SYSTEM WAKEUP

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  after waking up - the kernel throws 22 stack traces ...
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   1699 F pulseaudio
   /dev/snd/pcmC2D0p:   dave   1699 F...m pulseaudio
   /dev/snd/controlC2:  dave   1699 F pulseaudio
   /dev/snd/controlC1:  dave   1699 F pulseaudio
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=442028c2-80ef-4fa9-94f9-8d4e3b6284b3
  InstallationDate: Installed on 2017-09-18 (1 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp6s0no wireless extensions.
  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)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=8fce0715-8dd7-462d-9452-0f8a749fba60 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-35-generic N/A
   linux-backports-modules-4.10.0-35-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.10.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.20
  dmi.board.name: X370 Killer SLI
  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.:bvrP3.20:bd08/25/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370KillerSLI:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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/1718193/+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 1718193] JournalErrors.txt

apport information

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

Title:
  NEW RYZEN 7 SYSTEM WAKEUP

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  after waking up - the kernel throws 22 stack traces ...
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   1699 F pulseaudio
   /dev/snd/pcmC2D0p:   dave   1699 F...m pulseaudio
   /dev/snd/controlC2:  dave   1699 F pulseaudio
   /dev/snd/controlC1:  dave   1699 F pulseaudio
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=442028c2-80ef-4fa9-94f9-8d4e3b6284b3
  InstallationDate: Installed on 2017-09-18 (1 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp6s0no wireless extensions.
  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)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=8fce0715-8dd7-462d-9452-0f8a749fba60 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-35-generic N/A
   linux-backports-modules-4.10.0-35-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.10.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.20
  dmi.board.name: X370 Killer SLI
  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.:bvrP3.20:bd08/25/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370KillerSLI:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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/1718193/+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 1718193] Re: NEW RYZEN 7 SYSTEM WAKEUP

apport information

** Tags added: apport-collected zesty

** Description changed:

  after waking up - the kernel throws 22 stack traces ...
+ --- 
+ ApportVersion: 2.20.4-0ubuntu4.5
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  dave   1699 F pulseaudio
+  /dev/snd/pcmC2D0p:   dave   1699 F...m pulseaudio
+  /dev/snd/controlC2:  dave   1699 F pulseaudio
+  /dev/snd/controlC1:  dave   1699 F pulseaudio
+ DistroRelease: Ubuntu 17.04
+ HibernationDevice: RESUME=UUID=442028c2-80ef-4fa9-94f9-8d4e3b6284b3
+ InstallationDate: Installed on 2017-09-18 (1 days ago)
+ InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
+ IwConfig:
+  lono wireless extensions.
+  
+  enp6s0no wireless extensions.
+ 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)
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=8fce0715-8dd7-462d-9452-0f8a749fba60 ro quiet splash
+ ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
+ PulseList:
+  Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
+  No PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-4.10.0-35-generic N/A
+  linux-backports-modules-4.10.0-35-generic  N/A
+  linux-firmware 1.164.1
+ RfKill:
+  
+ Tags:  zesty
+ Uname: Linux 4.10.0-35-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 08/25/2017
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: P3.20
+ dmi.board.name: X370 Killer SLI
+ 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.:bvrP3.20:bd08/25/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370KillerSLI:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1718193/+attachment/4953704/+files/AlsaInfo.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/1718193

Title:
  NEW RYZEN 7 SYSTEM WAKEUP

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  after waking up - the kernel throws 22 stack traces ...
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   1699 F pulseaudio
   /dev/snd/pcmC2D0p:   dave   1699 F...m pulseaudio
   /dev/snd/controlC2:  dave   1699 F pulseaudio
   /dev/snd/controlC1:  dave   1699 F pulseaudio
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=442028c2-80ef-4fa9-94f9-8d4e3b6284b3
  InstallationDate: Installed on 2017-09-18 (1 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp6s0no wireless extensions.
  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)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=8fce0715-8dd7-462d-9452-0f8a749fba60 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-35-generic N/A
   linux-backports-modules-4.10.0-35-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.10.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.20
  dmi.board.name: X370 Killer SLI
  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.:bvrP3.20:bd08/25/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370KillerSLI:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.

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

apport information

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

Title:
  NEW RYZEN 7 SYSTEM WAKEUP

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  after waking up - the kernel throws 22 stack traces ...
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   1699 F pulseaudio
   /dev/snd/pcmC2D0p:   dave   1699 F...m pulseaudio
   /dev/snd/controlC2:  dave   1699 F pulseaudio
   /dev/snd/controlC1:  dave   1699 F pulseaudio
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=442028c2-80ef-4fa9-94f9-8d4e3b6284b3
  InstallationDate: Installed on 2017-09-18 (1 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp6s0no wireless extensions.
  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)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=8fce0715-8dd7-462d-9452-0f8a749fba60 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-35-generic N/A
   linux-backports-modules-4.10.0-35-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.10.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.20
  dmi.board.name: X370 Killer SLI
  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.:bvrP3.20:bd08/25/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370KillerSLI:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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/1718193/+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 1718193] CurrentDmesg.txt

apport information

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

Title:
  NEW RYZEN 7 SYSTEM WAKEUP

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  after waking up - the kernel throws 22 stack traces ...
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   1699 F pulseaudio
   /dev/snd/pcmC2D0p:   dave   1699 F...m pulseaudio
   /dev/snd/controlC2:  dave   1699 F pulseaudio
   /dev/snd/controlC1:  dave   1699 F pulseaudio
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=442028c2-80ef-4fa9-94f9-8d4e3b6284b3
  InstallationDate: Installed on 2017-09-18 (1 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp6s0no wireless extensions.
  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)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=8fce0715-8dd7-462d-9452-0f8a749fba60 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-35-generic N/A
   linux-backports-modules-4.10.0-35-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.10.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.20
  dmi.board.name: X370 Killer SLI
  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.:bvrP3.20:bd08/25/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370KillerSLI:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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/1718193/+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 1718193] CRDA.txt

apport information

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

Title:
  NEW RYZEN 7 SYSTEM WAKEUP

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  after waking up - the kernel throws 22 stack traces ...
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   1699 F pulseaudio
   /dev/snd/pcmC2D0p:   dave   1699 F...m pulseaudio
   /dev/snd/controlC2:  dave   1699 F pulseaudio
   /dev/snd/controlC1:  dave   1699 F pulseaudio
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=442028c2-80ef-4fa9-94f9-8d4e3b6284b3
  InstallationDate: Installed on 2017-09-18 (1 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp6s0no wireless extensions.
  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)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=8fce0715-8dd7-462d-9452-0f8a749fba60 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-35-generic N/A
   linux-backports-modules-4.10.0-35-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.10.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.20
  dmi.board.name: X370 Killer SLI
  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.:bvrP3.20:bd08/25/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370KillerSLI:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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/1718193/+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 1693369] Re: 5U84 - ses driver isn't binding right - cannot blink lights on 1 of the 2 5u84

** No longer affects: linux (Ubuntu Yakkety)

** Also affects: linux (Ubuntu Artful)
   Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
   Status: In Progress

** Changed in: linux (Ubuntu Artful)
   Status: In Progress => Fix Released

** Changed in: linux (Ubuntu Artful)
 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/1693369

Title:
  5U84 - ses driver isn't binding right - cannot blink lights on 1 of
  the 2 5u84

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  Fix Released

Bug description:
  This is a request to add the following upstream commit to both Ubuntu
  16.04.1 and 16.04.2:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/scsi/ses.c?id=9373eba6cfae48911b977d14323032cd5d161aae

  Without this patch, the symlink in sysfs which binds a SAS device to
  an enclosure slot does not get created. This makes disk hotplug near
  impossible on large JBOD disk drawers.

  You should be able to do:

  ls /sys/block/sdb/device/ | grep enclosure

  and see something like:

  enclosure_device:1

  If you cd to this directory, you can then access the SES controls for
  that slot to flash the LED to assist in locating the disk to replace a
  failed disk.

  Currently with 16.04.1 and 16.04.2, these symlinks are not getting
  created.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1693369/+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 1717259] Re: adaptec starfire fails to initializewith recent kernels

2017-09-20 Thread Steve Holton

Driver correctly initializes under v3.4-rc6-precise (3.4.0-030400)
Driver fails to initialize under v3.4-rc6-precise-pae   (3.4.0-030400)
Driver fails to initialize under v3.4.1-quantal (3.4.1-030401)

v3.4-rc6-precise/
 From: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc6-precise/
 linux-headers-3.4.0-030400rc6-generic_3.4.0-030400rc6.201205061835_i386.deb
 linux-headers-3.4.0-030400rc6_3.4.0-030400rc6.201205061835_all.deb
 linux-image-3.4.0-030400rc6-generic_3.4.0-030400rc6.201205061835_i386.deb

v3.4-rc6-precise-pae/
 From: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc6-precise/
 linux-headers-3.4.0-030400rc6-generic-pae_3.4.0-030400rc6.201205061835_i386.deb
 linux-headers-3.4.0-030400rc6_3.4.0-030400rc6.201205061835_all.deb
 linux-image-3.4.0-030400rc6-generic-pae_3.4.0-030400rc6.201205061835_i386.deb
 linux-image-3.4.0-030400rc6-generic_3.4.0-030400rc6.201205061835_i386.deb

v3.4.1-quantal/
 From: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4.1-quantal/
 linux-headers-3.4.1-030401-generic_3.4.1-030401.201206041411_i386.deb
 linux-headers-3.4.1-030401_3.4.1-030401.201206041411_all.deb
 linux-image-3.4.1-030401-generic_3.4.1-030401.201206041411_i386.deb
 linux-image-extra-3.4.1-030401-generic_3.4.1-030401.201206041411_i386.deb

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

Title:
  adaptec starfire fails to initializewith recent kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Re-opening
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1473200 (expired)

  Adaptec ethernet adapter using starfire driver fails to initialize
  when recent kernels are used.

  This hardware/driver can be successfully initialized under a
  3.2.0-126-generic kernel (from precise) but initialization is known to
  fail under 3.13.0-129-generic kernel and under -pae kernel builds of
  many vintages.  initialization also fails under current 4.x series
  kernel.  Full kernel bisect is not yet complete.

  Specific indication from dmesg:

  [3.536508] starfire.c:v1.03 7/26/2000  Written by Donald Becker 

  (unofficial 2.2/2.4 kernel port, version 2.1, July  6, 2008)
  [3.536509] starfire: polling (NAPI) enabled
  [3.536771] ioremap: invalid physical address fe48
  [3.536773] [ cut here ]
  [3.536784] WARNING: CPU: 1 PID: 115 at 
/build/linux-CK3pdl/linux-4.4.0/arch/x86/mm/ioremap.c:104 
__ioremap_caller+0x40f/0x440()
  [3.536790] Modules linked in: starfire(+) mii fjes floppy(+)
  [3.536795] CPU: 1 PID: 115 Comm: systemd-udevd Not tainted 
4.4.0-93-generic #116-Ubuntu
  [3.536797] Hardware name: Intel/SE7501BR2S, BIOS 
SBR20.86B.0082.P23.050407173004/07/2005
  [3.536805]  c1ae9967 73b5a5ce 0286 c01ddb90 c13add2f  
c19d0e40 c01ddbc0
  [3.536811]  c1070387 c19d8dd4 0001 0073 c19d0e40 0068 
c105fe2f c105fe2f
  [3.536818]  0fff fe4f  c01ddbd0 c1070492 0009 
 c01ddc3c
  [3.536819] Call Trace:
  [3.536829]  [] dump_stack+0x58/0x79
  [3.536835]  [] warn_slowpath_common+0x87/0xc0
  [3.536840]  [] ? __ioremap_caller+0x40f/0x440
  [3.536843]  [] ? __ioremap_caller+0x40f/0x440
  [3.536847]  [] warn_slowpath_null+0x22/0x30
  [3.536850]  [] __ioremap_caller+0x40f/0x440
  [3.536855]  [] ? __pci_request_region+0xb4/0x180
  [3.536861]  [] ? starfire_init_one+0xc6/0x680 [starfire]
  [3.536866]  [] ? starfire_init_one+0xc6/0x680 [starfire]
  [3.536869]  [] ioremap_nocache+0x1f/0x30
  [3.536874]  [] ? starfire_init_one+0xc6/0x680 [starfire]
  [3.536879]  [] starfire_init_one+0xc6/0x680 [starfire]
  [3.536885]  [] ? __pm_runtime_resume+0x51/0x80
  [3.536889]  [] pci_device_probe+0x7b/0xf0
  [3.536894]  [] ? devices_kset_move_last+0x2d/0xa0
  [3.536899]  [] driver_probe_device+0x1f9/0x4a0
  [3.536904]  [] ? sysfs_create_dir_ns+0x37/0x90
  [3.536907]  [] ? pci_match_device+0xdc/0x100
  [3.536911]  [] __driver_attach+0x79/0x80
  [3.536915]  [] ? driver_probe_device+0x4a0/0x4a0
  [3.536918]  [] bus_for_each_dev+0x57/0xa0
  [3.536921]  [] driver_attach+0x1e/0x20
  [3.536925]  [] ? driver_probe_device+0x4a0/0x4a0
  [3.536928]  [] bus_add_driver+0x1ef/0x290
  [3.536931]  [] ? 0xf8465000
  [3.536933]  [] ? 0xf8465000
  [3.536936]  [] driver_register+0x5d/0xf0
  [3.536939]  [] __pci_register_driver+0x33/0x40
  [3.536944]  [] starfire_init+0x2b/0x1000 [starfire]
  [3.536948]  [] do_one_initcall+0xaa/0x200
  [3.536951]  [] ? 0xf8465000
  [3.536955]  [] ? kfree+0x120/0x130
  [3.536958]  [] ? kmem_cache_alloc_trace+0x185/0x1e0
  [3.536964]  [] ? do_init_module+0x21/0x1a6
  [3.536967]  [] ? do_init_module+0x21/0x1a6
  [3.536970]  []

[Kernel-packages] [Bug 1646277] Re: Xenial server 16.04.x will have a black screen after PXE installation

Thanks, can you next test 4.2.0-16:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/8099555


Also, this bug might be very related to graphics hw. Some server boards with 
remote management capabilities use something like Matrox or similarly exotic. 
In the past we sometimes saw problems switching framebuffer devices. Things 
that maybe can help are changing grub to console mode or adding nomodeset into 
kernel parameters. (If you change GRUB setting, be sure to run "sudo 
update-grub" before rebooting).

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

Title:
  Xenial server 16.04.x will have a black screen after PXE installation

Status in debian-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in debian-installer source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  The display will keep black screen after install 16.04.x via PXE(need
  use "Ctrl+Alt+F1" to change to terminal 1, then can see text mode
  screen)

  Quanta team is installing Xenial server using PXE boot.   After the
  installation, the console will show a black screen.   Hitting ctl-
  alt-f1 displays the text mode screen OK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1646277/+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 1715609] Re: kernel warning: skb_warn_bad_offload

@jo Vanvoorden,

A Xenial 4.4 based test kernel has been built with a revert of commit
b2504a5dbe.

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1715609/xenial

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

Title:
  kernel warning: skb_warn_bad_offload

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  Since upgrading to kernel version 4.10.0-33.37, we're seeing a lot of
  call traces triggered by skb_warn_bad_offload in the syslog.

  Regression introduced when fixing this bug?
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705447


  kernel: [570943.49] [ cut here ]
  kernel: [570943.494448] WARNING: CPU: 3 PID: 21982 at 
/build/linux-hwe-YA6IuF/linux-hwe-4.10.0/net/core/dev.c:2576 
skb_warn_bad_offload+0xd1/0x120
  kernel: [570943.494450] e1000e: caps=(0x0030002149a9, 0x) 
len=1701 data_len=1659 gso_size=1480 gso_type=2 ip_summed=0
  kernel: [570943.494451] Modules linked in: udp_diag tcp_diag inet_diag 
echainiv authenc xfrm4_mode_tunnel xt_state binfmt_misc veth xfrm_user 
xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfrm_algo bridge stp 
llc iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_nat_ipv4 nf_nat ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter ip_tables x_tables 
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm ppdev 
irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel 
aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf hci_uart 
ie31200_edac btbcm edac_core intel_pch_thermal btqca serio_raw btintel 
bluetooth parport_pc parport mac_hid intel_lpss_acpi acpi_pad intel_lpss autofs4
  kernel: [570943.494500]  btrfs raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 
e1000e psmouse ptp ahci pps_core libahci wmi pinctrl_sunrisepoint i2c_hid video 
pinctrl_intel hid fjes
  kernel: [570943.494524] CPU: 3 PID: 21982 Comm: charon Tainted: GW
   4.10.0-33-generic #37~16.04.1-Ubuntu
  kernel: [570943.494524] Hardware name: ...
  kernel: [570943.494525] Call Trace:
  kernel: [570943.494541]  
  kernel: [570943.494544]  dump_stack+0x63/0x90
  kernel: [570943.494545]  __warn+0xcb/0xf0
  kernel: [570943.494546]  warn_slowpath_fmt+0x5f/0x80
  kernel: [570943.494547]  ? ___ratelimit+0xa2/0xf0
  kernel: [570943.494549]  skb_warn_bad_offload+0xd1/0x120
  kernel: [570943.494550]  __skb_gso_segment+0x17d/0x190
  kernel: [570943.494564]  validate_xmit_skb+0x14f/0x2a0
  kernel: [570943.494565]  validate_xmit_skb_list+0x43/0x70
  kernel: [570943.494567]  sch_direct_xmit+0x16b/0x1c0
  kernel: [570943.494568]  __dev_queue_xmit+0x47e/0x690
  kernel: [570943.494569]  dev_queue_xmit+0x10/0x20
  kernel: [570943.494570]  ip_finish_output2+0x27a/0x370
  kernel: [570943.494571]  ip_finish_output+0x176/0x270
  kernel: [570943.494571]  ip_output+0x76/0xe0
  kernel: [570943.494572]  ? ip_fragment.constprop.49+0x80/0x80
  kernel: [570943.494573]  ip_forward_finish+0x43/0x70
  kernel: [570943.494574]  ip_forward+0x385/0x460
  kernel: [570943.494575]  ? ip_frag_mem+0x50/0x50
  kernel: [570943.494575]  ip_rcv_finish+0x11b/0x400
  kernel: [570943.494576]  ip_rcv+0x28b/0x3a0
  ...
  kernel: [570943.494632] ---[ end trace f01d0adcc1256afe ]---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715609/+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 1696049] Re: xfstest sanity checks on seek operations fails