[Kernel-packages] [Bug 1831846] Re: [raven] fix screen corruption on modprobe

[Timo Aaltonen]

** Changed in: linux-oem-osp1 (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  [raven] fix screen corruption on modprobe

Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Disco:
  Incomplete
Status in linux-oem-osp1 source package in Disco:
  Invalid

Bug description:
  [Impact]
  These patches (or a squashed commit) are needed to fix screen corruption 
during modprobe on raven:

  02122753f1 drm/amdgpu: reserve stollen vram for raven series
  379109351f drm/amdgpu: keep stolen memory on picasso

  [Test case]

  test modprobe on affected hw

  [Regression potential]

  shouldn't be any

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831846/+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 1810416] Re: SD card error mmc0: error -110 whilst initialising SD card

[Kai-Heng Feng]

If it worked on older kernels, please do a kernel bisection to find the
regression commit.

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

Title:
  SD card error mmc0: error -110 whilst initialising SD card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When inserting card to internal card reader:

  laurynas@laurynas-ThinkPad-T450:~$ dmesg
  [342809.333716] mmc0: error -110 whilst initialising SD card

  laurynas@laurynas-ThinkPad-T450:~$ uname -a
  Linux laurynas-ThinkPad-T450 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 
14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  
  SanDisk Extreme 64GB UHS 3. Working fine on windows 10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  laurynas   3963 F pulseaudio
   /dev/snd/controlC0:  laurynas   3963 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  3 16:09:26 2019
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=6d87ff4e-c0ef-4f84-a96e-19a22e4acce4
  InstallationDate: Installed on 2017-02-18 (683 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20BUS3GN07
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=a0b409bc-4664-443b-b5be-7941f78d50a8 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-10-04 (90 days ago)
  dmi.bios.date: 02/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET68WW (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BUS3GN07
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET68WW(1.32):bd02/27/2018:svnLENOVO:pn20BUS3GN07:pvrThinkPadT450:rvnLENOVO:rn20BUS3GN07:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BUS3GN07
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810416/+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 1829378] Re: Kernel 4.15.0-50 wont boot as Xen-DomU with PVH

[David Kowis]

https://lists.xenproject.org/archives/html/xen-
users/2019-05/txtiEUldDuKY9.txt

This is the stacktrace/log that was originally captured by the filer.

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

Title:
  Kernel 4.15.0-50 wont boot as Xen-DomU with PVH

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  New

Bug description:
  After upgrading HWE-16.04-kernel from 4.15.0-48 to 4.15.0-50 the kernel 
crashes while booting as PVH-Guest with Xen 4.12 (booting as PV works).
  Kernel 4.15.0-48 and prior did boot without any problems as PVH.

  We have the same problem for Ubuntu 18.04 with Kernel 4.15.0-50.
  Ubunutu 18.04 with HWE-Kernel 4.18.0-20 boots without problems as PVH-
  DomU.

  See also https://lists.xenproject.org/archives/html/xen-
  users/2019-05/msg00010.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829378/+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 1829378] Re: Kernel 4.15.0-50 wont boot as Xen-DomU with PVH

[David Kowis]

Also does not boot for linux-image-4.15.0-51-generic

>From the xl console output trying to boot that kernel. Previous kernels
have no problem.

libxl: error: libxl_xshelp.c:201:libxl__xs_read_mandatory: xenstore read 
failed: `/libxl/45/type': No such file or directory
libxl: warning: libxl_dom.c:52:libxl__domain_type: unable to get domain type 
for domid=45, assuming HVM
xenconsole: Could not read tty from store: No such file or directory
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console child 
[3420] exited with error status 2
root@nosgoth:/etc/xen/conf#

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

Title:
  Kernel 4.15.0-50 wont boot as Xen-DomU with PVH

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  New

Bug description:
  After upgrading HWE-16.04-kernel from 4.15.0-48 to 4.15.0-50 the kernel 
crashes while booting as PVH-Guest with Xen 4.12 (booting as PV works).
  Kernel 4.15.0-48 and prior did boot without any problems as PVH.

  We have the same problem for Ubuntu 18.04 with Kernel 4.15.0-50.
  Ubunutu 18.04 with HWE-Kernel 4.18.0-20 boots without problems as PVH-
  DomU.

  See also https://lists.xenproject.org/archives/html/xen-
  users/2019-05/msg00010.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829378/+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 1832661] [NEW] Xenial update: 4.4.181 upstream stable release

[Khaled El Mously]

Public bug reported:


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 following upstream
   stable patches should be included in the Ubuntu kernel:

   4.4.181 upstream stable release
   from git://git.kernel.org/

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

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

Title:
  Xenial update: 4.4.181 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  New

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 following upstream
 stable patches should be included in the Ubuntu kernel:

 4.4.181 upstream stable release
 from git://git.kernel.org/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832661/+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 1832634] Re: libhugetlbfs FAIL small_const is not hugepage

[Po-Hsu Lin]

s/enabled/disabled/ in comment #2

https://kernel.ubuntu.com/git/ubuntu/autotest-client-
tests.git/commit/?id=2208088acc770d820fd57a6960ae9b2db8bdb08a

Tests disabled.

** Changed in: ubuntu-kernel-tests
   Status: In Progress => Fix Released

** Changed in: ubuntu-kernel-tests
   Importance: Undecided => Medium

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

Title:
  libhugetlbfs FAIL small_const is not hugepage

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Eoan:
  Invalid

Bug description:
  Series: Eoan
  Kernel: 5.2.0-4.5-generic
  Metal Or Clouds Affected: (Bare Metal Intel) & AWS
  Instance Type: Any

  This bug has been seen in prior series, however not really officially tracked 
 and followed up on. We will do that here. 
   
  libhugetlbfs fails with the following.

  06/12 18:56:14 DEBUG| utils:0153| [stdout] linkhuge_rw (2M: 64):  PASS
  06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=R linkhuge_rw 
(2M: 64): FAILsmall_const is not hugepage
  06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=W linkhuge_rw 
(2M: 64):
  06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=RW linkhuge_rw 
(2M: 64):FAILsmall_data is not hugepage
  06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=no linkhuge_rw 
(2M: 64):PASS
  06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=R 
HUGETLB_MINIMAL_COPY=no linkhuge_rw (2M: 64): FAILsmall_const is not 
hugepage
  06/12 18:56:16 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=W 
HUGETLB_MINIMAL_COPY=no linkhuge_rw (2M: 64): FAILsmall_data is not hugepage
  06/12 18:56:16 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=RW 
HUGETLB_MINIMAL_COPY=no linkhuge_rw (2M: 64):FAILsmall_data is not 
hugepage
  06/12 18:56:16 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=0 
HUGETLB_ELFMAP=R linkhuge_rw (2M: 64): FAILsmall_const is not hugepage
  06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=1 
HUGETLB_ELFMAP=R linkhuge_rw (2M: 64): FAILsmall_const is not hugepage
  06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=0 
HUGETLB_ELFMAP=W linkhuge_rw (2M: 64):
  06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=1 
HUGETLB_ELFMAP=W linkhuge_rw (2M: 64):
  06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=0 
HUGETLB_ELFMAP=RW linkhuge_rw (2M: 64):FAILsmall_data is not 
hugepage
  06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=1 
HUGETLB_ELFMAP=RW linkhuge_rw (2M: 64):FAILsmall_data is not 
hugepage
  06/12 18:56:17 DEBUG| utils:0153| [stdout] chunk-overcommit (2M: 64): 
PASS

  Full logs attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1832634/+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 1830792] Re: [i915] Rotated display is overscaled and overdrawn while i915 crashes repeatedly

[Daniel van Vugt]

Thanks for those logs. They show the problem happening immediately, as
soon as 2.5 seconds after the kernel starts.

This bug is now assigned to the kernel ('linux' component). I believe
this is a kernel bug, if not a hardware fault.

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

Title:
  [i915] Rotated display is overscaled and overdrawn while i915 crashes
  repeatedly

Status in gnome-shell package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  On my system I have two display: one in landscape, and one in
  portrait. The landscape display is fine, but the portrait display is
  corrupted. If I unplug the display from the computer for some time and
  then plug it back in it will occasionally fix the problem.

  Once the problem is fixed, the display works perfectly fine,
  indefinitely. However, as soon as I reboot the computer the display
  will come up corrupted again and never recovers without many rounds of
  plug/unplug turn off/turn on. It's extremely frustrating.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 28 15:57:02 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-22 (36 days ago)
  modified.conffile..etc.logrotate.d.apport: [modified]
  mtime.conffile..etc.logrotate.d.apport: 2019-01-12T15:50:59.090583

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+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 1832634] Re: libhugetlbfs FAIL small_const is not hugepage

[Po-Hsu Lin]

Test should be enabled.

We can copy forward the blacklist file.
$ find ./ -name blacklist.disco
./libhugetlbfs/blacklist.disco
./ubuntu_seccomp/blacklist.disco
./ubuntu_ecryptfs/blacklist.disco


** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: ubuntu-kernel-tests
   Status: Confirmed => In Progress

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

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

Title:
  libhugetlbfs FAIL small_const is not hugepage

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Eoan:
  Invalid

Bug description:
  Series: Eoan
  Kernel: 5.2.0-4.5-generic
  Metal Or Clouds Affected: (Bare Metal Intel) & AWS
  Instance Type: Any

  This bug has been seen in prior series, however not really officially tracked 
 and followed up on. We will do that here. 
   
  libhugetlbfs fails with the following.

  06/12 18:56:14 DEBUG| utils:0153| [stdout] linkhuge_rw (2M: 64):  PASS
  06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=R linkhuge_rw 
(2M: 64): FAILsmall_const is not hugepage
  06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=W linkhuge_rw 
(2M: 64):
  06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=RW linkhuge_rw 
(2M: 64):FAILsmall_data is not hugepage
  06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=no linkhuge_rw 
(2M: 64):PASS
  06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=R 
HUGETLB_MINIMAL_COPY=no linkhuge_rw (2M: 64): FAILsmall_const is not 
hugepage
  06/12 18:56:16 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=W 
HUGETLB_MINIMAL_COPY=no linkhuge_rw (2M: 64): FAILsmall_data is not hugepage
  06/12 18:56:16 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=RW 
HUGETLB_MINIMAL_COPY=no linkhuge_rw (2M: 64):FAILsmall_data is not 
hugepage
  06/12 18:56:16 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=0 
HUGETLB_ELFMAP=R linkhuge_rw (2M: 64): FAILsmall_const is not hugepage
  06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=1 
HUGETLB_ELFMAP=R linkhuge_rw (2M: 64): FAILsmall_const is not hugepage
  06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=0 
HUGETLB_ELFMAP=W linkhuge_rw (2M: 64):
  06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=1 
HUGETLB_ELFMAP=W linkhuge_rw (2M: 64):
  06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=0 
HUGETLB_ELFMAP=RW linkhuge_rw (2M: 64):FAILsmall_data is not 
hugepage
  06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=1 
HUGETLB_ELFMAP=RW linkhuge_rw (2M: 64):FAILsmall_data is not 
hugepage
  06/12 18:56:17 DEBUG| utils:0153| [stdout] chunk-overcommit (2M: 64): 
PASS

  Full logs attached.

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

[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 1813463

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

Title:
  no bluetooth intel ac 9260

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi All

  Using a laptop with the intel AC 9260 wireless card that also has Bluetooth 
5.0.
  Booting either ubuntu 18.04 or 18.10 with kernel 4.18.* through to 4.20.* the 
bluetooth is not detected and can't be switched on.

  hciconfig -a
  Produces no result

  $ bluetoothctl
  Agent registered
  [bluetooth]# show
  No default controller available
  [bluetooth]# devices
  No default controller available
  [bluetooth]#

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813463/+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 1813463] Re: no bluetooth intel ac 9260

[Daniel van Vugt]

Does Ubuntu 19.04 work better with this hardware?

** Tags added: bionic cosmic

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

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

Title:
  no bluetooth intel ac 9260

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi All

  Using a laptop with the intel AC 9260 wireless card that also has Bluetooth 
5.0.
  Booting either ubuntu 18.04 or 18.10 with kernel 4.18.* through to 4.20.* the 
bluetooth is not detected and can't be switched on.

  hciconfig -a
  Produces no result

  $ bluetoothctl
  Agent registered
  [bluetooth]# show
  No default controller available
  [bluetooth]# devices
  No default controller available
  [bluetooth]#

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813463/+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 1731699] Re: Unable to transfer files via bluetooth to paired android phone

[Daniel van Vugt]

** Tags removed: artful
** Tags added: disco

** Changed in: bluez (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  Unable to transfer files via bluetooth to paired android phone

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to transfer files to my phone (Nexus 6P - Android 8.0) from
  Ubuntu 17.10, but when I pair the laptop and phone, I don't think it's
  pairing in a way which permits file transfers. When I pair, my phone
  gives me a checkbox "Allow xx to access your contacts and call
  history", but there is no option to allow file transfers.

  Then, when I attempt to transfer a file via Bluetooth from Ubuntu the
  transfer fails and I get the message "There was an error". My phone
  doesn't seem to recognise there's been any attempt to send a file.

  Discussed at https://ubuntuforums.org/showthread.php?t=2377286

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731699/+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 1832468] Re: linux-oem: 4.15.0-1042.47 -proposed tracker

[Ubuntu Kernel Bot]

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

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

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1829219
- phase: Packaging
- phase-changed: Wednesday, 12. June 2019 09:30 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Thursday, 13. June 2019 01:32 UTC
  reason:
-   prepare-package-meta: Pending -- package tag not yet published
-   promote-to-proposed: Pending -- source package tags missing
+   promote-to-proposed: Pending -- ready for review
  variant: debs

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

Title:
  linux-oem: 4.15.0-1042.47 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1829219
  phase: Ready for Promote to Proposed
  phase-changed: Thursday, 13. June 2019 01:32 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832468/+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 1827725] Re: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386)

[Dima]

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

Yes, nopti helps. Thank you.

** This bug has been marked a duplicate of bug 1827884
   Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

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

Title:
  linux-image-4.15.0-48-lowlatency and newer don't boot after update
  from 4.15.0-47 (16.04)(i386)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Currently I am on 4.15.0-47-lowlatency.
  I will attach kern.log if ubuntu-bug didn't it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.15.0-48-lowlatency 4.15.0-48.51~16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18
  Uname: Linux 4.15.0-47-lowlatency i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sat May  4 16:49:24 2019
  InstallationDate: Installed on 2018-10-01 (214 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160720)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1820 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=a1a12e2a-cc5c-4136-82c0-e30ab9c9febb
  InstallationDate: Installed on 2018-10-01 (234 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160720)
  MachineType: TOSHIBA Satellite L300
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-47-lowlatency 
root=UUID=50c3a930-a3e9--b4ea-1646d276c7c6 ro rootflags=subvol=@ 
ipv6.disable=1 zswap.enabled=0 raid=noautodetect priority=low video=SVIDEO-1:d 
module_blacklist=r8169,mii,msr,jfs,xfs,bluetooth,hfs,hfsplus,ufs,minix,ntfs,joydev,mac_hid
  ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-lowlatency N/A
   linux-backports-modules-4.15.0-47-lowlatency  N/A
   linux-firmware1.157.21
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.15.0-47-lowlatency i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 1.50
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr1.50:bd07/10/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLB0E-014012RU:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: Satellite L300
  dmi.product.version: PSLB0E-014012RU
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+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 1782709] Re: Updating systemd kills network on bionic

[James Gray]

Can confirm the same behaviour on my systems too. Updating systemd
recently caused the entire routing table to be dropped (I had console
access and was able to confirm no routes - not even loopback worked). In
normal operation I see:

>ip route show
default via 10.0.0.1 dev eno1 src 10.0.0.60 metric 202 
10.0.0.0/24 dev eno1 proto dhcp scope link src 10.0.0.60 metric 202 

However, when systemd is updated, the route table is blank although
interfaces maintain their addresses etc. When working remotely, I need
to get remote hands to reboot the system to restore normal functionality
which obviously extends down time. We have implemented procedures to
watch the route table and if it disappears, triggers a reboot but this
is problematic as it could happen before the update process is finished.

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

Title:
  Updating systemd kills network on bionic

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I do have an ubuntu bionic server installation without a graphical interface. 
The server
  has two active network adapters, both connected to the internet. One is used 
for outgoing
  internet traffic, the other for incoming. The incoming adapter lives on a 
public network segment
  (something like 88.236.133.104/29). I do have multiple servers within this 
segment.

  Typically, I update the server regularly, meaning:

  * ssh to the incoming adapter: ssh 88.236.133.108
  * apt-get update
  * apt-get upgrade
  * apt-get dist-upgrade
  * apt-get clean
  * reboot

  It used to work ok.

  BUT: Today, "apt-get upgrade" seem to take really long when updating systemd.
  After a could of minutes, I realized that the ssh session became inactive. I 
couldn't type
  into it, I had to abort it via ~. .

  * ssh from the internet to the incoming adapter was not working anymore - ssh 
88.236.133.108
  * ssh via another server within the public network segment worked
  * ssh 88.236.133.106 -> ssh 88.236.133.108
  * After running "netplan apply" everything was fine again

  Here my netplan configuration (I changed the ip addresses):

  network:
version: 2
renderer: networkd
ethernets:
  eno1:
dhcp4: yes
  eno2:
dhcp4: no
addresses: [88.236.133.108/29]
#gateway4: 88.236.133.105
routes:
 - to: 0.0.0.0/0
   via: 88.236.133.105
   table: 120
routing-policy:
 - from: 88.236.133.108/32
   table: 120
 - to: 88.236.133.108/32
   table: 120

  Unfortunately, I don't have the console output avalable anymore.
  Shall I provide additional info?

  Best regards, Uli
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 20 08:10 seq
   crw-rw 1 root audio 116, 33 Jul 20 08:10 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-14 (5 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: IBM IBM System x -[794582G]-
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic 
root=UUID=a41b3020-8359-4fe2-8fc3-1c97011f71ec ro
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/07/2014
  dmi.bios.vendor: IBM Corp.
  dmi.bios.version: -[D6E162AUS-1.20]-
  dmi.board.asset.tag: (none)
  dmi.board.name: 00D4062
  dmi.board.vendor: IBM
  dmi.board.version: (none)
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: IBM
  dmi.chassis.version: none
  dmi.modalias: 
dmi:bvnIBMCorp.:bvr-[D6E162AUS-1.20]-:bd05/07/2014:svnIBM:pnIBMSystemx-[794582G]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone:
  dmi.product.family: System x
  dmi.product.name: IBM System x -[794582G]-
  dmi.product.version: 00
  dmi.sys.vendor: IBM

To 

[Kernel-packages] [Bug 1791312]

[Paul Dufresne]

The patch is included in:
Linux 4.14.125
Linux 4.19.50
Linux 5.1.9

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

Title:
  ubuntu 18.04 flickering screen with Radeon X1600

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

Bug description:
  my laptop: HP Compaq nx9420
  my grafic card: 
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller])

  attachment:
  the bug-apport-file

  Description:
  I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode;
  -> as soon as the kernel-module radeon.ko is loaded the screen starts 
flickering
  when starting the grafic-mode the flickering continues; so the screen is 
unusable.

  when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the 
screen does not flicker
  but the resolution is limited to 1400x1050 (instead of natural 1680x1050)
  so I can not use this as work-around

  when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157)
  the screen is o.k. NO flickering in textmode, nice grafic, NO flickering 
  xrandr tells: 1680x1050 60.1

  so I must stay on old ubuntu 14.04.05 ???

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1791312/+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 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600

[Bug Watch Updater]

** Changed in: linux
   Status: Confirmed => 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/1791312

Title:
  ubuntu 18.04 flickering screen with Radeon X1600

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

Bug description:
  my laptop: HP Compaq nx9420
  my grafic card: 
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller])

  attachment:
  the bug-apport-file

  Description:
  I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode;
  -> as soon as the kernel-module radeon.ko is loaded the screen starts 
flickering
  when starting the grafic-mode the flickering continues; so the screen is 
unusable.

  when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the 
screen does not flicker
  but the resolution is limited to 1400x1050 (instead of natural 1680x1050)
  so I can not use this as work-around

  when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157)
  the screen is o.k. NO flickering in textmode, nice grafic, NO flickering 
  xrandr tells: 1680x1050 60.1

  so I must stay on old ubuntu 14.04.05 ???

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1791312/+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 1832384] Re: Unable to unmount apparently unused filesystem

[John Gallagher]

Thanks for taking a look. One of the things that is painful about
debugging this issue is how long it takes to manifest. It would probably
require several weeks of testing a particular kernel version without
seeing the issue before we could be reasonably sure that the problem is
fixed. Also, testing in parallel can be quite resource intensive since
we need 10-15 machines to drive the workload for a single machine under
test.

Given this, I think we will spend a couple more days trying to come up
with a better reproducer, one that can produce the issue in less time,
or at least without requiring our application (and therefore our ZFS
bits). If we can do that, we should be in a better position to test with
other kernels.

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

Title:
  Unable to unmount apparently unused filesystem

Status in linux package in Ubuntu:
  In Progress

Bug description:
  We periodically see an issue where unmounting a ZFS filesystem fails
  with EBUSY, even though there appears to be no one using it.

  # cat /proc/self/mounts | grep 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive
  domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive zfs 
rw,nosuid,nodev,noexec,relatime,xattr,noacl 0 0

  'lsof' and 'fuser' show no processes using any of the files in the
  problematic filesystem:

  # ls -l 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive/
  total 221
  -rw-r- 1 500 500  52736 May 22 11:01 1_19_1008904362.dbf
  -rw-r- 1 500 500 541696 May 22 11:03 1_20_1008904362.dbf
  # fuser 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive/1_20_1008904362.dbf
  # fuser 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive/1_19_1008904362.dbf
  # fuser 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive/
  # lsof | grep 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive
  #

  The filesystem was shared over NFS, but has since been unshared:

  # showmount -e | grep 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive
  #

  Since no one appears to be using the filesystem, our expectation is
  that it should be possible to unmount the filesystem. However,
  attempts to unmount the filesystem fail with EBUSY:

  # zfs destroy 
domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive
  umount: 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive: target 
is busy.
  cannot unmount 
'/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive': 
umount failed
  # umount 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive
  umount: 
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive: target 
is busy.

  
  Using bpftrace, we can see that the unmount is failing in 
'propagate_mount_busy()' in the kernel. Using a live kernel debugger, we can 
look at the 'mount' struct for this particular mount and see that the 
'mnt_count' refcount summed across all CPUs is 2. For filesystems that are 
eligible for unmounting, the refcount is 1.

  The only way to work around this issue that we have found is to
  reboot, at which point the filesystem can be unmounted and destroyed.

  
  So far, we have only been able to reproduce this using a workload driven by 
our application. The application mananges ZFS filesystems in groups, and the 
lifecycle of each group looks something like

  - Create and mount a group of filesystems, 1 parent and 4 children:
  /domain0/group-38/oracle_db_container-202/oracle_timeflow-16370
  
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/datafile
  
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/external
  
/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive
  /domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/temp
  - Share all 5 filesystems over NFS
  - A client mounts all 5 shares using NFSv3
  - For a few hours, the client does NFS operations on the filesystems and 
the server occasionally takes ZFS snapshots of them
  - Unshare filesystems
  - Unmount filesystems
  - Delete filesystems

  These groups of filesystems are constantly being created and
  destroyed. At any given time, we have ~30k filesystems on the system,
  about 5k of which are shared. On average, one out of ~200-300k
  unmounts fails with this EBUSY error. To create and destroy this many
  filesystems takes us about a week or so.

  Note that we are using ZFS built from https://github.com/delphix/zfs,
  which is essentially master ZFS on Linux.

  ProblemType: Bug
  

[Kernel-packages] [Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change

[Mike Ranweiler]

I tried some test fw for the boston:

ubuntu@ltc-boston25:~$ sudo /sbin/hwclock --set --date "2019/06/10 12:55:00"; 
sudo /sbin/hwclock --verbose
[sudo] password for ubuntu: 
hwclock from util-linux 2.33.1
System Time: 1560377530.955292
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Last drift adjustment done at 1560189300 seconds after 1969
Last calibration done at 1560189300 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
ioctl(4, RTC_UIE_ON, 0): Invalid argument
Waiting in loop for time from /dev/rtc0 to change
...got clock tick
Time read from Hardware Clock: 2019/06/10 17:55:01
Hw clock time : 2019/06/10 17:55:01 = 1560189301 seconds since 1969
Time since last adjustment is 1 second
Calculated Hardware Clock drift is 0.00 seconds
2019-06-10 12:55:00.022780-05:00
ubuntu@ltc-boston25:~$ 

But I still have:
ubuntu@ltc-boston25:~$ sudo /sbin/hwclock --set --date "2004/11/21 04:10:00"; 
sudo strace -e ioctl "/sbin/hwclock"
ioctl(4, RTC_UIE_ON)= -1 EINVAL (Invalid argument)
ioctl(4, RTC_RD_TIME, {tm_sec=0, tm_min=10, tm_hour=10, tm_mday=21, tm_mon=10, 
tm_year=104, ...}) = 0

ioctl(4, RTC_RD_TIME, {tm_sec=1, tm_min=10, tm_hour=10, tm_mday=21, tm_mon=10, 
tm_year=104, ...}) = 0
ioctl(4, RTC_RD_TIME, {tm_sec=1, tm_min=10, tm_hour=10, tm_mday=21, tm_mon=10, 
tm_year=104, ...}) = 0
2004-11-21 04:10:00.018862-06:00
+++ exited with 0 +++
ubuntu@ltc-boston25:~$ 

But it generally seems to work - if I don't include any args it does set 
correctly still:
ubuntu@ltc-boston25:~$ sudo /sbin/hwclock --set --date "2019/06/10 12:55:00"; 
sudo /sbin/hwclock 
2019-06-10 12:54:59.982163-05:00
ubuntu@ltc-boston25:~$ 

Anything else you suggest?

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

Title:
  hwclock test failed on Power9 due to 0.x sec differences / time out
  waiting for time change

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

Bug description:
  The hwclock test will fail on the Power9 system "baltar" due to a
  <0.02 second difference.

  Traceback (most recent call last):
    File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
  _call_test_function(self.execute, *p_args, **p_dargs)
    File "/home/ubuntu/autotest/client/shared/test.py", line 823, in 
_call_test_function
  return func(*args, **dargs)
    File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
  postprocess_profiled_run, args, dargs)
    File "/home/ubuntu/autotest/client/shared/test.py", line 212, in 
_call_run_once
  self.run_once(*args, **dargs)
    File "/home/ubuntu/autotest/client/tests/hwclock/hwclock.py", line 50, in 
run_once
  raise error.TestFail("Failed to set hwclock back to Warthog's birthday. 
Output of hwclock is '%s'" % date)
  TestFail: Failed to set hwclock back to Warthog's birthday. Output of hwclock 
is '2004-10-20 04:09:59.582146+'

  Didn't see this on Power8 boxes

  Sometimes it will fail because "time out waiting for time change" on the same 
node:
  $ sudo /sbin/hwclock --set --date "2004/10/20 04:10:00"; sudo /sbin/hwclock
  hwclock: Timed out waiting for time change.

  Workaround for these is to add "sleep 1".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-38-generic 4.15.0-38.41
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  8 03:45 seq
   crw-rw 1 root audio 116, 33 Nov  8 03:45 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:

  Date: Thu Nov  8 06:03:54 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc.
   Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd
   Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro 
console=hvc0
  ProcLoadAvg: 0.31 0.11 0.03 1/1392 5654
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3544 00:17:582 0 EOF
   2: POSIX  ADVISORY  WRITE 1798 00:17:338 0 EOF
   3: POSIX  ADVISORY  WRITE 3603 00:17:576 0 EOF
   4: FLOCK  ADVISORY  WRITE 3535 00:17:564 0 EOF
   5: FLOCK  ADVISORY  WRITE 4081 00:17:481 0 

[Kernel-packages] [Bug 1831232] Re: Ubuntu 18.04 won't boot - failed to connect to lvmetad

[Raphael Mankin]

Further experimentation:

root@X1:~# ls /dev/mapper
control  sda3_crypt
root@X1:~# cryptsetup -v open --type plain /dev/sda2 sda2_crypt
Enter passphrase for /dev/sda2: 
Command successful.
root@X1:~# ls /dev/mapper
control  sda2_crypt  sda3_crypt
root@X1:~# swapon -a
swapon: /dev/mapper/sda2_crypt: read swap header failed

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

Title:
  Ubuntu 18.04 won't boot - failed to connect to lvmetad

Status in linux package in Ubuntu:
  Incomplete
Status in lvm2 package in Ubuntu:
  Incomplete

Bug description:
  This bug report relates to a machine running 18.04, not the one I am
  submitting the report from.

  On 30 May The Software Updater prompted me to update. Included in the
  update were initramfs components. I now cannot boot the machine.

  After decrypting the root file system, instead of being prompted for
  the pass-phrase to decrypt the swap, I get the message "cannot connect
  to lvmetad: falling back to device scanning". This repeats for a while
  until I am dropped into a recovery shell of some sort from which I
  cannot access the root disk.

  Blocker. My machine is unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-generic 4.15.0.48.50
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm2433 F pulseaudio
raph   8920 F pulseaudio
   /dev/snd/controlC0:  gdm2433 F pulseaudio
  Date: Fri May 31 12:08:33 2019
  HibernationDevice: RESUME=UUID=2538baa4-d43e-4876-8d94-dd3221894bac
  InstallationDate: Installed on 2018-02-09 (475 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20CJS0UU00
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-48-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-09-12 (260 days ago)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET42W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS0UU00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: R90G3N7R
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET42W(1.18):bd09/13/2017:svnLENOVO:pn20CJS0UU00:pvrThinkPadT550:rvnLENOVO:rn20CJS0UU00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS0UU00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831232/+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 1810416] Re: SD card error mmc0: error -110 whilst initialising SD card

[Diachuck Dmytro]

I have same problem. 
Laptop HP Omen Pro 15, SanDisk 64Gb 
I tested it on Ubuntu 18.04, Ubuntu 18.10, Ubuntu 19.04.  It did not work. In 
all environments, I  always get in logs(system) message: "mmc0: error -110 
whilst initialising SD card"

This card "SanDisk 64Gb" works on Ubuntu 14* and works on any my
cameras.

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

Title:
  SD card error mmc0: error -110 whilst initialising SD card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When inserting card to internal card reader:

  laurynas@laurynas-ThinkPad-T450:~$ dmesg
  [342809.333716] mmc0: error -110 whilst initialising SD card

  laurynas@laurynas-ThinkPad-T450:~$ uname -a
  Linux laurynas-ThinkPad-T450 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 
14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  
  SanDisk Extreme 64GB UHS 3. Working fine on windows 10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  laurynas   3963 F pulseaudio
   /dev/snd/controlC0:  laurynas   3963 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  3 16:09:26 2019
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=6d87ff4e-c0ef-4f84-a96e-19a22e4acce4
  InstallationDate: Installed on 2017-02-18 (683 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20BUS3GN07
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=a0b409bc-4664-443b-b5be-7941f78d50a8 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-10-04 (90 days ago)
  dmi.bios.date: 02/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET68WW (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BUS3GN07
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET68WW(1.32):bd02/27/2018:svnLENOVO:pn20BUS3GN07:pvrThinkPadT450:rvnLENOVO:rn20BUS3GN07:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BUS3GN07
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

[Yangzheng Bai]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1832641/+attachment/5270438/+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/1832641

Title:
  4.15.0-46-generic doesn't support ethtool adaptive-tx for mlx5 card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Bionic 18.04 LTS:
  We found that default bionic kernel 4.15.0-46-generic doesn't support ethtool 
-C adaptive-tx
  Our ethernet card is Mellanox Connect4-Lx and Connect5, and this will affect 
performance of latency sensitive workloads like memcached.
  Maybe we should backport adaptive-tx support to kernel 4.15 LTS?

  
  Xeon Skylake 8168 x86_64:
  ubuntu kernel 4.15.0-46-generic
  eth: mlx5 connect-5
  ethtool doesn't support adaptive-tx (ethernet TX interrupt coalesce)

  X-Gene3 aarch64:
  ubuntu kernel 4.18.0-16-generic, eth: mlx5 connect-4lx
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)

  Same Xeon Skylake 8168 x86_64
  latest kernel 5.2.0-rc2
  eth: mlx5 connect-5
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 14:42 seq
   crw-rw 1 root audio 116, 33 Jun 12 14:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: AmpereComputing(R) OSPREY EV-883832-X3-0001
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=698f489c-124b-4ebb-b6c3-14c8b82c978d ro console=ttyAMA0,115200 
iommu.passthrough=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-16-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/25/2018
  dmi.bios.vendor: Ampere(TM)
  dmi.bios.version: 4.8.19
  dmi.board.asset.tag: APCX3A1-A526-16050501200016
  dmi.board.name: OSPREY
  dmi.board.vendor: AmpereComputing(R)
  dmi.board.version: EV-883832-X3-OD1-2
  dmi.chassis.asset.tag: APCX3A1-A526-16050501200016
  dmi.chassis.type: 23
  dmi.chassis.vendor: AmpereComputing(R)
  dmi.chassis.version: APCA1A1-
  dmi.modalias: 
dmi:bvnAmpere(TM):bvr4.8.19:bd09/25/2018:svnAmpereComputing(R):pnOSPREYEV-883832-X3-0001:pvrPR010:rvnAmpereComputing(R):rnOSPREY:rvrEV-883832-X3-OD1-2:cvnAmpereComputing(R):ct23:cvrAPCA1A1-:
  dmi.product.family: eMAG
  dmi.product.name: OSPREY EV-883832-X3-0001
  dmi.product.sku: EV-883832-X3-OBX-1
  dmi.product.version: PR010
  dmi.sys.vendor: AmpereComputing(R)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 15:22 seq
   crw-rw 1 root audio 116, 33 Jun 12 15:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R640
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=cc79d3b3-63ee-450d-84ff-ddd80ab73c80 ro intel_pstate=disable 
console=ttyS0,115200n8
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  

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

[Yangzheng Bai]

apport information

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

Title:
  4.15.0-46-generic doesn't support ethtool adaptive-tx for mlx5 card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Bionic 18.04 LTS:
  We found that default bionic kernel 4.15.0-46-generic doesn't support ethtool 
-C adaptive-tx
  Our ethernet card is Mellanox Connect4-Lx and Connect5, and this will affect 
performance of latency sensitive workloads like memcached.
  Maybe we should backport adaptive-tx support to kernel 4.15 LTS?

  
  Xeon Skylake 8168 x86_64:
  ubuntu kernel 4.15.0-46-generic
  eth: mlx5 connect-5
  ethtool doesn't support adaptive-tx (ethernet TX interrupt coalesce)

  X-Gene3 aarch64:
  ubuntu kernel 4.18.0-16-generic, eth: mlx5 connect-4lx
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)

  Same Xeon Skylake 8168 x86_64
  latest kernel 5.2.0-rc2
  eth: mlx5 connect-5
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 14:42 seq
   crw-rw 1 root audio 116, 33 Jun 12 14:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: AmpereComputing(R) OSPREY EV-883832-X3-0001
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=698f489c-124b-4ebb-b6c3-14c8b82c978d ro console=ttyAMA0,115200 
iommu.passthrough=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-16-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/25/2018
  dmi.bios.vendor: Ampere(TM)
  dmi.bios.version: 4.8.19
  dmi.board.asset.tag: APCX3A1-A526-16050501200016
  dmi.board.name: OSPREY
  dmi.board.vendor: AmpereComputing(R)
  dmi.board.version: EV-883832-X3-OD1-2
  dmi.chassis.asset.tag: APCX3A1-A526-16050501200016
  dmi.chassis.type: 23
  dmi.chassis.vendor: AmpereComputing(R)
  dmi.chassis.version: APCA1A1-
  dmi.modalias: 
dmi:bvnAmpere(TM):bvr4.8.19:bd09/25/2018:svnAmpereComputing(R):pnOSPREYEV-883832-X3-0001:pvrPR010:rvnAmpereComputing(R):rnOSPREY:rvrEV-883832-X3-OD1-2:cvnAmpereComputing(R):ct23:cvrAPCA1A1-:
  dmi.product.family: eMAG
  dmi.product.name: OSPREY EV-883832-X3-0001
  dmi.product.sku: EV-883832-X3-OBX-1
  dmi.product.version: PR010
  dmi.sys.vendor: AmpereComputing(R)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 15:22 seq
   crw-rw 1 root audio 116, 33 Jun 12 15:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R640
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=cc79d3b3-63ee-450d-84ff-ddd80ab73c80 ro intel_pstate=disable 
console=ttyS0,115200n8
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 

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

[Yangzheng Bai]

apport information

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

Title:
  4.15.0-46-generic doesn't support ethtool adaptive-tx for mlx5 card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Bionic 18.04 LTS:
  We found that default bionic kernel 4.15.0-46-generic doesn't support ethtool 
-C adaptive-tx
  Our ethernet card is Mellanox Connect4-Lx and Connect5, and this will affect 
performance of latency sensitive workloads like memcached.
  Maybe we should backport adaptive-tx support to kernel 4.15 LTS?

  
  Xeon Skylake 8168 x86_64:
  ubuntu kernel 4.15.0-46-generic
  eth: mlx5 connect-5
  ethtool doesn't support adaptive-tx (ethernet TX interrupt coalesce)

  X-Gene3 aarch64:
  ubuntu kernel 4.18.0-16-generic, eth: mlx5 connect-4lx
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)

  Same Xeon Skylake 8168 x86_64
  latest kernel 5.2.0-rc2
  eth: mlx5 connect-5
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 14:42 seq
   crw-rw 1 root audio 116, 33 Jun 12 14:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: AmpereComputing(R) OSPREY EV-883832-X3-0001
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=698f489c-124b-4ebb-b6c3-14c8b82c978d ro console=ttyAMA0,115200 
iommu.passthrough=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-16-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/25/2018
  dmi.bios.vendor: Ampere(TM)
  dmi.bios.version: 4.8.19
  dmi.board.asset.tag: APCX3A1-A526-16050501200016
  dmi.board.name: OSPREY
  dmi.board.vendor: AmpereComputing(R)
  dmi.board.version: EV-883832-X3-OD1-2
  dmi.chassis.asset.tag: APCX3A1-A526-16050501200016
  dmi.chassis.type: 23
  dmi.chassis.vendor: AmpereComputing(R)
  dmi.chassis.version: APCA1A1-
  dmi.modalias: 
dmi:bvnAmpere(TM):bvr4.8.19:bd09/25/2018:svnAmpereComputing(R):pnOSPREYEV-883832-X3-0001:pvrPR010:rvnAmpereComputing(R):rnOSPREY:rvrEV-883832-X3-OD1-2:cvnAmpereComputing(R):ct23:cvrAPCA1A1-:
  dmi.product.family: eMAG
  dmi.product.name: OSPREY EV-883832-X3-0001
  dmi.product.sku: EV-883832-X3-OBX-1
  dmi.product.version: PR010
  dmi.sys.vendor: AmpereComputing(R)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 15:22 seq
   crw-rw 1 root audio 116, 33 Jun 12 15:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R640
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=cc79d3b3-63ee-450d-84ff-ddd80ab73c80 ro intel_pstate=disable 
console=ttyS0,115200n8
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 

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

[Yangzheng Bai]

apport information

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

Title:
  4.15.0-46-generic doesn't support ethtool adaptive-tx for mlx5 card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Bionic 18.04 LTS:
  We found that default bionic kernel 4.15.0-46-generic doesn't support ethtool 
-C adaptive-tx
  Our ethernet card is Mellanox Connect4-Lx and Connect5, and this will affect 
performance of latency sensitive workloads like memcached.
  Maybe we should backport adaptive-tx support to kernel 4.15 LTS?

  
  Xeon Skylake 8168 x86_64:
  ubuntu kernel 4.15.0-46-generic
  eth: mlx5 connect-5
  ethtool doesn't support adaptive-tx (ethernet TX interrupt coalesce)

  X-Gene3 aarch64:
  ubuntu kernel 4.18.0-16-generic, eth: mlx5 connect-4lx
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)

  Same Xeon Skylake 8168 x86_64
  latest kernel 5.2.0-rc2
  eth: mlx5 connect-5
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 14:42 seq
   crw-rw 1 root audio 116, 33 Jun 12 14:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: AmpereComputing(R) OSPREY EV-883832-X3-0001
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=698f489c-124b-4ebb-b6c3-14c8b82c978d ro console=ttyAMA0,115200 
iommu.passthrough=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-16-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/25/2018
  dmi.bios.vendor: Ampere(TM)
  dmi.bios.version: 4.8.19
  dmi.board.asset.tag: APCX3A1-A526-16050501200016
  dmi.board.name: OSPREY
  dmi.board.vendor: AmpereComputing(R)
  dmi.board.version: EV-883832-X3-OD1-2
  dmi.chassis.asset.tag: APCX3A1-A526-16050501200016
  dmi.chassis.type: 23
  dmi.chassis.vendor: AmpereComputing(R)
  dmi.chassis.version: APCA1A1-
  dmi.modalias: 
dmi:bvnAmpere(TM):bvr4.8.19:bd09/25/2018:svnAmpereComputing(R):pnOSPREYEV-883832-X3-0001:pvrPR010:rvnAmpereComputing(R):rnOSPREY:rvrEV-883832-X3-OD1-2:cvnAmpereComputing(R):ct23:cvrAPCA1A1-:
  dmi.product.family: eMAG
  dmi.product.name: OSPREY EV-883832-X3-0001
  dmi.product.sku: EV-883832-X3-OBX-1
  dmi.product.version: PR010
  dmi.sys.vendor: AmpereComputing(R)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 15:22 seq
   crw-rw 1 root audio 116, 33 Jun 12 15:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R640
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=cc79d3b3-63ee-450d-84ff-ddd80ab73c80 ro intel_pstate=disable 
console=ttyS0,115200n8
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  RfKill: 

[Kernel-packages] [Bug 1832641] ProcCpuinfo.txt

[Yangzheng Bai]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1832641/+attachment/5270424/+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/1832641

Title:
  4.15.0-46-generic doesn't support ethtool adaptive-tx for mlx5 card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Bionic 18.04 LTS:
  We found that default bionic kernel 4.15.0-46-generic doesn't support ethtool 
-C adaptive-tx
  Our ethernet card is Mellanox Connect4-Lx and Connect5, and this will affect 
performance of latency sensitive workloads like memcached.
  Maybe we should backport adaptive-tx support to kernel 4.15 LTS?

  
  Xeon Skylake 8168 x86_64:
  ubuntu kernel 4.15.0-46-generic
  eth: mlx5 connect-5
  ethtool doesn't support adaptive-tx (ethernet TX interrupt coalesce)

  X-Gene3 aarch64:
  ubuntu kernel 4.18.0-16-generic, eth: mlx5 connect-4lx
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)

  Same Xeon Skylake 8168 x86_64
  latest kernel 5.2.0-rc2
  eth: mlx5 connect-5
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 14:42 seq
   crw-rw 1 root audio 116, 33 Jun 12 14:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: AmpereComputing(R) OSPREY EV-883832-X3-0001
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=698f489c-124b-4ebb-b6c3-14c8b82c978d ro console=ttyAMA0,115200 
iommu.passthrough=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-16-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/25/2018
  dmi.bios.vendor: Ampere(TM)
  dmi.bios.version: 4.8.19
  dmi.board.asset.tag: APCX3A1-A526-16050501200016
  dmi.board.name: OSPREY
  dmi.board.vendor: AmpereComputing(R)
  dmi.board.version: EV-883832-X3-OD1-2
  dmi.chassis.asset.tag: APCX3A1-A526-16050501200016
  dmi.chassis.type: 23
  dmi.chassis.vendor: AmpereComputing(R)
  dmi.chassis.version: APCA1A1-
  dmi.modalias: 
dmi:bvnAmpere(TM):bvr4.8.19:bd09/25/2018:svnAmpereComputing(R):pnOSPREYEV-883832-X3-0001:pvrPR010:rvnAmpereComputing(R):rnOSPREY:rvrEV-883832-X3-OD1-2:cvnAmpereComputing(R):ct23:cvrAPCA1A1-:
  dmi.product.family: eMAG
  dmi.product.name: OSPREY EV-883832-X3-0001
  dmi.product.sku: EV-883832-X3-OBX-1
  dmi.product.version: PR010
  dmi.sys.vendor: AmpereComputing(R)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 15:22 seq
   crw-rw 1 root audio 116, 33 Jun 12 15:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R640
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=cc79d3b3-63ee-450d-84ff-ddd80ab73c80 ro intel_pstate=disable 
console=ttyS0,115200n8
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  RfKill: 

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

[Yangzheng Bai]

apport information

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

Title:
  4.15.0-46-generic doesn't support ethtool adaptive-tx for mlx5 card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Bionic 18.04 LTS:
  We found that default bionic kernel 4.15.0-46-generic doesn't support ethtool 
-C adaptive-tx
  Our ethernet card is Mellanox Connect4-Lx and Connect5, and this will affect 
performance of latency sensitive workloads like memcached.
  Maybe we should backport adaptive-tx support to kernel 4.15 LTS?

  
  Xeon Skylake 8168 x86_64:
  ubuntu kernel 4.15.0-46-generic
  eth: mlx5 connect-5
  ethtool doesn't support adaptive-tx (ethernet TX interrupt coalesce)

  X-Gene3 aarch64:
  ubuntu kernel 4.18.0-16-generic, eth: mlx5 connect-4lx
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)

  Same Xeon Skylake 8168 x86_64
  latest kernel 5.2.0-rc2
  eth: mlx5 connect-5
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 14:42 seq
   crw-rw 1 root audio 116, 33 Jun 12 14:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: AmpereComputing(R) OSPREY EV-883832-X3-0001
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=698f489c-124b-4ebb-b6c3-14c8b82c978d ro console=ttyAMA0,115200 
iommu.passthrough=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-16-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/25/2018
  dmi.bios.vendor: Ampere(TM)
  dmi.bios.version: 4.8.19
  dmi.board.asset.tag: APCX3A1-A526-16050501200016
  dmi.board.name: OSPREY
  dmi.board.vendor: AmpereComputing(R)
  dmi.board.version: EV-883832-X3-OD1-2
  dmi.chassis.asset.tag: APCX3A1-A526-16050501200016
  dmi.chassis.type: 23
  dmi.chassis.vendor: AmpereComputing(R)
  dmi.chassis.version: APCA1A1-
  dmi.modalias: 
dmi:bvnAmpere(TM):bvr4.8.19:bd09/25/2018:svnAmpereComputing(R):pnOSPREYEV-883832-X3-0001:pvrPR010:rvnAmpereComputing(R):rnOSPREY:rvrEV-883832-X3-OD1-2:cvnAmpereComputing(R):ct23:cvrAPCA1A1-:
  dmi.product.family: eMAG
  dmi.product.name: OSPREY EV-883832-X3-0001
  dmi.product.sku: EV-883832-X3-OBX-1
  dmi.product.version: PR010
  dmi.sys.vendor: AmpereComputing(R)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 15:22 seq
   crw-rw 1 root audio 116, 33 Jun 12 15:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R640
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=cc79d3b3-63ee-450d-84ff-ddd80ab73c80 ro intel_pstate=disable 
console=ttyS0,115200n8
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] 

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

[Yangzheng Bai]

apport information

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

Title:
  4.15.0-46-generic doesn't support ethtool adaptive-tx for mlx5 card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Bionic 18.04 LTS:
  We found that default bionic kernel 4.15.0-46-generic doesn't support ethtool 
-C adaptive-tx
  Our ethernet card is Mellanox Connect4-Lx and Connect5, and this will affect 
performance of latency sensitive workloads like memcached.
  Maybe we should backport adaptive-tx support to kernel 4.15 LTS?

  
  Xeon Skylake 8168 x86_64:
  ubuntu kernel 4.15.0-46-generic
  eth: mlx5 connect-5
  ethtool doesn't support adaptive-tx (ethernet TX interrupt coalesce)

  X-Gene3 aarch64:
  ubuntu kernel 4.18.0-16-generic, eth: mlx5 connect-4lx
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)

  Same Xeon Skylake 8168 x86_64
  latest kernel 5.2.0-rc2
  eth: mlx5 connect-5
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 14:42 seq
   crw-rw 1 root audio 116, 33 Jun 12 14:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: AmpereComputing(R) OSPREY EV-883832-X3-0001
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=698f489c-124b-4ebb-b6c3-14c8b82c978d ro console=ttyAMA0,115200 
iommu.passthrough=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-16-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/25/2018
  dmi.bios.vendor: Ampere(TM)
  dmi.bios.version: 4.8.19
  dmi.board.asset.tag: APCX3A1-A526-16050501200016
  dmi.board.name: OSPREY
  dmi.board.vendor: AmpereComputing(R)
  dmi.board.version: EV-883832-X3-OD1-2
  dmi.chassis.asset.tag: APCX3A1-A526-16050501200016
  dmi.chassis.type: 23
  dmi.chassis.vendor: AmpereComputing(R)
  dmi.chassis.version: APCA1A1-
  dmi.modalias: 
dmi:bvnAmpere(TM):bvr4.8.19:bd09/25/2018:svnAmpereComputing(R):pnOSPREYEV-883832-X3-0001:pvrPR010:rvnAmpereComputing(R):rnOSPREY:rvrEV-883832-X3-OD1-2:cvnAmpereComputing(R):ct23:cvrAPCA1A1-:
  dmi.product.family: eMAG
  dmi.product.name: OSPREY EV-883832-X3-0001
  dmi.product.sku: EV-883832-X3-OBX-1
  dmi.product.version: PR010
  dmi.sys.vendor: AmpereComputing(R)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 15:22 seq
   crw-rw 1 root audio 116, 33 Jun 12 15:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R640
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=cc79d3b3-63ee-450d-84ff-ddd80ab73c80 ro intel_pstate=disable 
console=ttyS0,115200n8
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  RfKill: 

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

[Yangzheng Bai]

apport information

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

Title:
  4.15.0-46-generic doesn't support ethtool adaptive-tx for mlx5 card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Bionic 18.04 LTS:
  We found that default bionic kernel 4.15.0-46-generic doesn't support ethtool 
-C adaptive-tx
  Our ethernet card is Mellanox Connect4-Lx and Connect5, and this will affect 
performance of latency sensitive workloads like memcached.
  Maybe we should backport adaptive-tx support to kernel 4.15 LTS?

  
  Xeon Skylake 8168 x86_64:
  ubuntu kernel 4.15.0-46-generic
  eth: mlx5 connect-5
  ethtool doesn't support adaptive-tx (ethernet TX interrupt coalesce)

  X-Gene3 aarch64:
  ubuntu kernel 4.18.0-16-generic, eth: mlx5 connect-4lx
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)

  Same Xeon Skylake 8168 x86_64
  latest kernel 5.2.0-rc2
  eth: mlx5 connect-5
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 14:42 seq
   crw-rw 1 root audio 116, 33 Jun 12 14:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: AmpereComputing(R) OSPREY EV-883832-X3-0001
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=698f489c-124b-4ebb-b6c3-14c8b82c978d ro console=ttyAMA0,115200 
iommu.passthrough=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-16-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/25/2018
  dmi.bios.vendor: Ampere(TM)
  dmi.bios.version: 4.8.19
  dmi.board.asset.tag: APCX3A1-A526-16050501200016
  dmi.board.name: OSPREY
  dmi.board.vendor: AmpereComputing(R)
  dmi.board.version: EV-883832-X3-OD1-2
  dmi.chassis.asset.tag: APCX3A1-A526-16050501200016
  dmi.chassis.type: 23
  dmi.chassis.vendor: AmpereComputing(R)
  dmi.chassis.version: APCA1A1-
  dmi.modalias: 
dmi:bvnAmpere(TM):bvr4.8.19:bd09/25/2018:svnAmpereComputing(R):pnOSPREYEV-883832-X3-0001:pvrPR010:rvnAmpereComputing(R):rnOSPREY:rvrEV-883832-X3-OD1-2:cvnAmpereComputing(R):ct23:cvrAPCA1A1-:
  dmi.product.family: eMAG
  dmi.product.name: OSPREY EV-883832-X3-0001
  dmi.product.sku: EV-883832-X3-OBX-1
  dmi.product.version: PR010
  dmi.sys.vendor: AmpereComputing(R)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 15:22 seq
   crw-rw 1 root audio 116, 33 Jun 12 15:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R640
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=cc79d3b3-63ee-450d-84ff-ddd80ab73c80 ro intel_pstate=disable 
console=ttyS0,115200n8
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 

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

[Yangzheng Bai]

apport information

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

Title:
  4.15.0-46-generic doesn't support ethtool adaptive-tx for mlx5 card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Bionic 18.04 LTS:
  We found that default bionic kernel 4.15.0-46-generic doesn't support ethtool 
-C adaptive-tx
  Our ethernet card is Mellanox Connect4-Lx and Connect5, and this will affect 
performance of latency sensitive workloads like memcached.
  Maybe we should backport adaptive-tx support to kernel 4.15 LTS?

  
  Xeon Skylake 8168 x86_64:
  ubuntu kernel 4.15.0-46-generic
  eth: mlx5 connect-5
  ethtool doesn't support adaptive-tx (ethernet TX interrupt coalesce)

  X-Gene3 aarch64:
  ubuntu kernel 4.18.0-16-generic, eth: mlx5 connect-4lx
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)

  Same Xeon Skylake 8168 x86_64
  latest kernel 5.2.0-rc2
  eth: mlx5 connect-5
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 14:42 seq
   crw-rw 1 root audio 116, 33 Jun 12 14:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: AmpereComputing(R) OSPREY EV-883832-X3-0001
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=698f489c-124b-4ebb-b6c3-14c8b82c978d ro console=ttyAMA0,115200 
iommu.passthrough=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-16-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/25/2018
  dmi.bios.vendor: Ampere(TM)
  dmi.bios.version: 4.8.19
  dmi.board.asset.tag: APCX3A1-A526-16050501200016
  dmi.board.name: OSPREY
  dmi.board.vendor: AmpereComputing(R)
  dmi.board.version: EV-883832-X3-OD1-2
  dmi.chassis.asset.tag: APCX3A1-A526-16050501200016
  dmi.chassis.type: 23
  dmi.chassis.vendor: AmpereComputing(R)
  dmi.chassis.version: APCA1A1-
  dmi.modalias: 
dmi:bvnAmpere(TM):bvr4.8.19:bd09/25/2018:svnAmpereComputing(R):pnOSPREYEV-883832-X3-0001:pvrPR010:rvnAmpereComputing(R):rnOSPREY:rvrEV-883832-X3-OD1-2:cvnAmpereComputing(R):ct23:cvrAPCA1A1-:
  dmi.product.family: eMAG
  dmi.product.name: OSPREY EV-883832-X3-0001
  dmi.product.sku: EV-883832-X3-OBX-1
  dmi.product.version: PR010
  dmi.sys.vendor: AmpereComputing(R)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 15:22 seq
   crw-rw 1 root audio 116, 33 Jun 12 15:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R640
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=cc79d3b3-63ee-450d-84ff-ddd80ab73c80 ro intel_pstate=disable 
console=ttyS0,115200n8
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  

[Kernel-packages] [Bug 1832641] ProcCpuinfo.txt

[Yangzheng Bai]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1832641/+attachment/5270433/+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/1832641

Title:
  4.15.0-46-generic doesn't support ethtool adaptive-tx for mlx5 card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Bionic 18.04 LTS:
  We found that default bionic kernel 4.15.0-46-generic doesn't support ethtool 
-C adaptive-tx
  Our ethernet card is Mellanox Connect4-Lx and Connect5, and this will affect 
performance of latency sensitive workloads like memcached.
  Maybe we should backport adaptive-tx support to kernel 4.15 LTS?

  
  Xeon Skylake 8168 x86_64:
  ubuntu kernel 4.15.0-46-generic
  eth: mlx5 connect-5
  ethtool doesn't support adaptive-tx (ethernet TX interrupt coalesce)

  X-Gene3 aarch64:
  ubuntu kernel 4.18.0-16-generic, eth: mlx5 connect-4lx
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)

  Same Xeon Skylake 8168 x86_64
  latest kernel 5.2.0-rc2
  eth: mlx5 connect-5
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 14:42 seq
   crw-rw 1 root audio 116, 33 Jun 12 14:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: AmpereComputing(R) OSPREY EV-883832-X3-0001
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=698f489c-124b-4ebb-b6c3-14c8b82c978d ro console=ttyAMA0,115200 
iommu.passthrough=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-16-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/25/2018
  dmi.bios.vendor: Ampere(TM)
  dmi.bios.version: 4.8.19
  dmi.board.asset.tag: APCX3A1-A526-16050501200016
  dmi.board.name: OSPREY
  dmi.board.vendor: AmpereComputing(R)
  dmi.board.version: EV-883832-X3-OD1-2
  dmi.chassis.asset.tag: APCX3A1-A526-16050501200016
  dmi.chassis.type: 23
  dmi.chassis.vendor: AmpereComputing(R)
  dmi.chassis.version: APCA1A1-
  dmi.modalias: 
dmi:bvnAmpere(TM):bvr4.8.19:bd09/25/2018:svnAmpereComputing(R):pnOSPREYEV-883832-X3-0001:pvrPR010:rvnAmpereComputing(R):rnOSPREY:rvrEV-883832-X3-OD1-2:cvnAmpereComputing(R):ct23:cvrAPCA1A1-:
  dmi.product.family: eMAG
  dmi.product.name: OSPREY EV-883832-X3-0001
  dmi.product.sku: EV-883832-X3-OBX-1
  dmi.product.version: PR010
  dmi.sys.vendor: AmpereComputing(R)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 15:22 seq
   crw-rw 1 root audio 116, 33 Jun 12 15:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R640
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=cc79d3b3-63ee-450d-84ff-ddd80ab73c80 ro intel_pstate=disable 
console=ttyS0,115200n8
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  RfKill: 

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

[Yangzheng Bai]

apport information

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

Title:
  4.15.0-46-generic doesn't support ethtool adaptive-tx for mlx5 card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Bionic 18.04 LTS:
  We found that default bionic kernel 4.15.0-46-generic doesn't support ethtool 
-C adaptive-tx
  Our ethernet card is Mellanox Connect4-Lx and Connect5, and this will affect 
performance of latency sensitive workloads like memcached.
  Maybe we should backport adaptive-tx support to kernel 4.15 LTS?

  
  Xeon Skylake 8168 x86_64:
  ubuntu kernel 4.15.0-46-generic
  eth: mlx5 connect-5
  ethtool doesn't support adaptive-tx (ethernet TX interrupt coalesce)

  X-Gene3 aarch64:
  ubuntu kernel 4.18.0-16-generic, eth: mlx5 connect-4lx
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)

  Same Xeon Skylake 8168 x86_64
  latest kernel 5.2.0-rc2
  eth: mlx5 connect-5
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 14:42 seq
   crw-rw 1 root audio 116, 33 Jun 12 14:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: AmpereComputing(R) OSPREY EV-883832-X3-0001
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=698f489c-124b-4ebb-b6c3-14c8b82c978d ro console=ttyAMA0,115200 
iommu.passthrough=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-16-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/25/2018
  dmi.bios.vendor: Ampere(TM)
  dmi.bios.version: 4.8.19
  dmi.board.asset.tag: APCX3A1-A526-16050501200016
  dmi.board.name: OSPREY
  dmi.board.vendor: AmpereComputing(R)
  dmi.board.version: EV-883832-X3-OD1-2
  dmi.chassis.asset.tag: APCX3A1-A526-16050501200016
  dmi.chassis.type: 23
  dmi.chassis.vendor: AmpereComputing(R)
  dmi.chassis.version: APCA1A1-
  dmi.modalias: 
dmi:bvnAmpere(TM):bvr4.8.19:bd09/25/2018:svnAmpereComputing(R):pnOSPREYEV-883832-X3-0001:pvrPR010:rvnAmpereComputing(R):rnOSPREY:rvrEV-883832-X3-OD1-2:cvnAmpereComputing(R):ct23:cvrAPCA1A1-:
  dmi.product.family: eMAG
  dmi.product.name: OSPREY EV-883832-X3-0001
  dmi.product.sku: EV-883832-X3-OBX-1
  dmi.product.version: PR010
  dmi.sys.vendor: AmpereComputing(R)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 15:22 seq
   crw-rw 1 root audio 116, 33 Jun 12 15:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R640
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=cc79d3b3-63ee-450d-84ff-ddd80ab73c80 ro intel_pstate=disable 
console=ttyS0,115200n8
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 

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

[Yangzheng Bai]

apport information

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

** Description changed:

  Ubuntu Bionic 18.04 LTS:
  We found that default bionic kernel 4.15.0-46-generic doesn't support ethtool 
-C adaptive-tx
  Our ethernet card is Mellanox Connect4-Lx and Connect5, and this will affect 
performance of latency sensitive workloads like memcached.
  Maybe we should backport adaptive-tx support to kernel 4.15 LTS?
  
  
  Xeon Skylake 8168 x86_64:
  ubuntu kernel 4.15.0-46-generic
  eth: mlx5 connect-5
  ethtool doesn't support adaptive-tx (ethernet TX interrupt coalesce)
  
  X-Gene3 aarch64:
  ubuntu kernel 4.18.0-16-generic, eth: mlx5 connect-4lx
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)
  
  Same Xeon Skylake 8168 x86_64
  latest kernel 5.2.0-rc2
  eth: mlx5 connect-5
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 14:42 seq
   crw-rw 1 root audio 116, 33 Jun 12 14:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: AmpereComputing(R) OSPREY EV-883832-X3-0001
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=698f489c-124b-4ebb-b6c3-14c8b82c978d ro console=ttyAMA0,115200 
iommu.passthrough=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-16-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/25/2018
  dmi.bios.vendor: Ampere(TM)
  dmi.bios.version: 4.8.19
  dmi.board.asset.tag: APCX3A1-A526-16050501200016
  dmi.board.name: OSPREY
  dmi.board.vendor: AmpereComputing(R)
  dmi.board.version: EV-883832-X3-OD1-2
  dmi.chassis.asset.tag: APCX3A1-A526-16050501200016
  dmi.chassis.type: 23
  dmi.chassis.vendor: AmpereComputing(R)
  dmi.chassis.version: APCA1A1-
  dmi.modalias: 
dmi:bvnAmpere(TM):bvr4.8.19:bd09/25/2018:svnAmpereComputing(R):pnOSPREYEV-883832-X3-0001:pvrPR010:rvnAmpereComputing(R):rnOSPREY:rvrEV-883832-X3-OD1-2:cvnAmpereComputing(R):ct23:cvrAPCA1A1-:
  dmi.product.family: eMAG
  dmi.product.name: OSPREY EV-883832-X3-0001
  dmi.product.sku: EV-883832-X3-OBX-1
  dmi.product.version: PR010
  dmi.sys.vendor: AmpereComputing(R)
+ --- 
+ ProblemType: Bug
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 Jun 12 15:22 seq
+  crw-rw 1 root audio 116, 33 Jun 12 15:22 timer
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
+ ApportVersion: 2.20.9-0ubuntu7.6
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ DistroRelease: Ubuntu 18.04
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 1604:10c0 Tascam 
+  Bus 001 Device 003: ID 1604:10c0 Tascam 
+  Bus 001 Device 002: ID 1604:10c0 Tascam 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: Dell Inc. PowerEdge R640
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=C.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 mgadrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=cc79d3b3-63ee-450d-84ff-ddd80ab73c80 ro intel_pstate=disable 
console=ttyS0,115200n8
+ ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-46-generic N/A
+  linux-backports-modules-4.15.0-46-generic  N/A
+  linux-firmware 1.173.3
+ RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
+ Tags:  bionic uec-images
+ Uname: Linux 4.15.0-46-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 05/21/2018
+ 

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

[Yangzheng Bai]

apport information

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

Title:
  4.15.0-46-generic doesn't support ethtool adaptive-tx for mlx5 card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Bionic 18.04 LTS:
  We found that default bionic kernel 4.15.0-46-generic doesn't support ethtool 
-C adaptive-tx
  Our ethernet card is Mellanox Connect4-Lx and Connect5, and this will affect 
performance of latency sensitive workloads like memcached.
  Maybe we should backport adaptive-tx support to kernel 4.15 LTS?

  
  Xeon Skylake 8168 x86_64:
  ubuntu kernel 4.15.0-46-generic
  eth: mlx5 connect-5
  ethtool doesn't support adaptive-tx (ethernet TX interrupt coalesce)

  X-Gene3 aarch64:
  ubuntu kernel 4.18.0-16-generic, eth: mlx5 connect-4lx
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)

  Same Xeon Skylake 8168 x86_64
  latest kernel 5.2.0-rc2
  eth: mlx5 connect-5
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 14:42 seq
   crw-rw 1 root audio 116, 33 Jun 12 14:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: AmpereComputing(R) OSPREY EV-883832-X3-0001
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=698f489c-124b-4ebb-b6c3-14c8b82c978d ro console=ttyAMA0,115200 
iommu.passthrough=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-16-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/25/2018
  dmi.bios.vendor: Ampere(TM)
  dmi.bios.version: 4.8.19
  dmi.board.asset.tag: APCX3A1-A526-16050501200016
  dmi.board.name: OSPREY
  dmi.board.vendor: AmpereComputing(R)
  dmi.board.version: EV-883832-X3-OD1-2
  dmi.chassis.asset.tag: APCX3A1-A526-16050501200016
  dmi.chassis.type: 23
  dmi.chassis.vendor: AmpereComputing(R)
  dmi.chassis.version: APCA1A1-
  dmi.modalias: 
dmi:bvnAmpere(TM):bvr4.8.19:bd09/25/2018:svnAmpereComputing(R):pnOSPREYEV-883832-X3-0001:pvrPR010:rvnAmpereComputing(R):rnOSPREY:rvrEV-883832-X3-OD1-2:cvnAmpereComputing(R):ct23:cvrAPCA1A1-:
  dmi.product.family: eMAG
  dmi.product.name: OSPREY EV-883832-X3-0001
  dmi.product.sku: EV-883832-X3-OBX-1
  dmi.product.version: PR010
  dmi.sys.vendor: AmpereComputing(R)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 15:22 seq
   crw-rw 1 root audio 116, 33 Jun 12 15:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R640
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=cc79d3b3-63ee-450d-84ff-ddd80ab73c80 ro intel_pstate=disable 
console=ttyS0,115200n8
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  RfKill: 

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

[Yangzheng Bai]

apport information

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

Title:
  4.15.0-46-generic doesn't support ethtool adaptive-tx for mlx5 card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Bionic 18.04 LTS:
  We found that default bionic kernel 4.15.0-46-generic doesn't support ethtool 
-C adaptive-tx
  Our ethernet card is Mellanox Connect4-Lx and Connect5, and this will affect 
performance of latency sensitive workloads like memcached.
  Maybe we should backport adaptive-tx support to kernel 4.15 LTS?

  
  Xeon Skylake 8168 x86_64:
  ubuntu kernel 4.15.0-46-generic
  eth: mlx5 connect-5
  ethtool doesn't support adaptive-tx (ethernet TX interrupt coalesce)

  X-Gene3 aarch64:
  ubuntu kernel 4.18.0-16-generic, eth: mlx5 connect-4lx
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)

  Same Xeon Skylake 8168 x86_64
  latest kernel 5.2.0-rc2
  eth: mlx5 connect-5
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 14:42 seq
   crw-rw 1 root audio 116, 33 Jun 12 14:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: AmpereComputing(R) OSPREY EV-883832-X3-0001
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=698f489c-124b-4ebb-b6c3-14c8b82c978d ro console=ttyAMA0,115200 
iommu.passthrough=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-16-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/25/2018
  dmi.bios.vendor: Ampere(TM)
  dmi.bios.version: 4.8.19
  dmi.board.asset.tag: APCX3A1-A526-16050501200016
  dmi.board.name: OSPREY
  dmi.board.vendor: AmpereComputing(R)
  dmi.board.version: EV-883832-X3-OD1-2
  dmi.chassis.asset.tag: APCX3A1-A526-16050501200016
  dmi.chassis.type: 23
  dmi.chassis.vendor: AmpereComputing(R)
  dmi.chassis.version: APCA1A1-
  dmi.modalias: 
dmi:bvnAmpere(TM):bvr4.8.19:bd09/25/2018:svnAmpereComputing(R):pnOSPREYEV-883832-X3-0001:pvrPR010:rvnAmpereComputing(R):rnOSPREY:rvrEV-883832-X3-OD1-2:cvnAmpereComputing(R):ct23:cvrAPCA1A1-:
  dmi.product.family: eMAG
  dmi.product.name: OSPREY EV-883832-X3-0001
  dmi.product.sku: EV-883832-X3-OBX-1
  dmi.product.version: PR010
  dmi.sys.vendor: AmpereComputing(R)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 15:22 seq
   crw-rw 1 root audio 116, 33 Jun 12 15:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R640
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=cc79d3b3-63ee-450d-84ff-ddd80ab73c80 ro intel_pstate=disable 
console=ttyS0,115200n8
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 

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

[Yangzheng Bai]

apport information

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

Title:
  4.15.0-46-generic doesn't support ethtool adaptive-tx for mlx5 card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Bionic 18.04 LTS:
  We found that default bionic kernel 4.15.0-46-generic doesn't support ethtool 
-C adaptive-tx
  Our ethernet card is Mellanox Connect4-Lx and Connect5, and this will affect 
performance of latency sensitive workloads like memcached.
  Maybe we should backport adaptive-tx support to kernel 4.15 LTS?

  
  Xeon Skylake 8168 x86_64:
  ubuntu kernel 4.15.0-46-generic
  eth: mlx5 connect-5
  ethtool doesn't support adaptive-tx (ethernet TX interrupt coalesce)

  X-Gene3 aarch64:
  ubuntu kernel 4.18.0-16-generic, eth: mlx5 connect-4lx
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)

  Same Xeon Skylake 8168 x86_64
  latest kernel 5.2.0-rc2
  eth: mlx5 connect-5
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 14:42 seq
   crw-rw 1 root audio 116, 33 Jun 12 14:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: AmpereComputing(R) OSPREY EV-883832-X3-0001
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=698f489c-124b-4ebb-b6c3-14c8b82c978d ro console=ttyAMA0,115200 
iommu.passthrough=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-16-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/25/2018
  dmi.bios.vendor: Ampere(TM)
  dmi.bios.version: 4.8.19
  dmi.board.asset.tag: APCX3A1-A526-16050501200016
  dmi.board.name: OSPREY
  dmi.board.vendor: AmpereComputing(R)
  dmi.board.version: EV-883832-X3-OD1-2
  dmi.chassis.asset.tag: APCX3A1-A526-16050501200016
  dmi.chassis.type: 23
  dmi.chassis.vendor: AmpereComputing(R)
  dmi.chassis.version: APCA1A1-
  dmi.modalias: 
dmi:bvnAmpere(TM):bvr4.8.19:bd09/25/2018:svnAmpereComputing(R):pnOSPREYEV-883832-X3-0001:pvrPR010:rvnAmpereComputing(R):rnOSPREY:rvrEV-883832-X3-OD1-2:cvnAmpereComputing(R):ct23:cvrAPCA1A1-:
  dmi.product.family: eMAG
  dmi.product.name: OSPREY EV-883832-X3-0001
  dmi.product.sku: EV-883832-X3-OBX-1
  dmi.product.version: PR010
  dmi.sys.vendor: AmpereComputing(R)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 15:22 seq
   crw-rw 1 root audio 116, 33 Jun 12 15:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R640
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=cc79d3b3-63ee-450d-84ff-ddd80ab73c80 ro intel_pstate=disable 
console=ttyS0,115200n8
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  

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

[Yangzheng Bai]

apport information

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

Title:
  4.15.0-46-generic doesn't support ethtool adaptive-tx for mlx5 card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Bionic 18.04 LTS:
  We found that default bionic kernel 4.15.0-46-generic doesn't support ethtool 
-C adaptive-tx
  Our ethernet card is Mellanox Connect4-Lx and Connect5, and this will affect 
performance of latency sensitive workloads like memcached.
  Maybe we should backport adaptive-tx support to kernel 4.15 LTS?

  
  Xeon Skylake 8168 x86_64:
  ubuntu kernel 4.15.0-46-generic
  eth: mlx5 connect-5
  ethtool doesn't support adaptive-tx (ethernet TX interrupt coalesce)

  X-Gene3 aarch64:
  ubuntu kernel 4.18.0-16-generic, eth: mlx5 connect-4lx
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)

  Same Xeon Skylake 8168 x86_64
  latest kernel 5.2.0-rc2
  eth: mlx5 connect-5
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 14:42 seq
   crw-rw 1 root audio 116, 33 Jun 12 14:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: AmpereComputing(R) OSPREY EV-883832-X3-0001
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=698f489c-124b-4ebb-b6c3-14c8b82c978d ro console=ttyAMA0,115200 
iommu.passthrough=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-16-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/25/2018
  dmi.bios.vendor: Ampere(TM)
  dmi.bios.version: 4.8.19
  dmi.board.asset.tag: APCX3A1-A526-16050501200016
  dmi.board.name: OSPREY
  dmi.board.vendor: AmpereComputing(R)
  dmi.board.version: EV-883832-X3-OD1-2
  dmi.chassis.asset.tag: APCX3A1-A526-16050501200016
  dmi.chassis.type: 23
  dmi.chassis.vendor: AmpereComputing(R)
  dmi.chassis.version: APCA1A1-
  dmi.modalias: 
dmi:bvnAmpere(TM):bvr4.8.19:bd09/25/2018:svnAmpereComputing(R):pnOSPREYEV-883832-X3-0001:pvrPR010:rvnAmpereComputing(R):rnOSPREY:rvrEV-883832-X3-OD1-2:cvnAmpereComputing(R):ct23:cvrAPCA1A1-:
  dmi.product.family: eMAG
  dmi.product.name: OSPREY EV-883832-X3-0001
  dmi.product.sku: EV-883832-X3-OBX-1
  dmi.product.version: PR010
  dmi.sys.vendor: AmpereComputing(R)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 15:22 seq
   crw-rw 1 root audio 116, 33 Jun 12 15:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R640
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=cc79d3b3-63ee-450d-84ff-ddd80ab73c80 ro intel_pstate=disable 
console=ttyS0,115200n8
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 

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

[Yangzheng Bai]

apport information

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

Title:
  4.15.0-46-generic doesn't support ethtool adaptive-tx for mlx5 card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Bionic 18.04 LTS:
  We found that default bionic kernel 4.15.0-46-generic doesn't support ethtool 
-C adaptive-tx
  Our ethernet card is Mellanox Connect4-Lx and Connect5, and this will affect 
performance of latency sensitive workloads like memcached.
  Maybe we should backport adaptive-tx support to kernel 4.15 LTS?

  
  Xeon Skylake 8168 x86_64:
  ubuntu kernel 4.15.0-46-generic
  eth: mlx5 connect-5
  ethtool doesn't support adaptive-tx (ethernet TX interrupt coalesce)

  X-Gene3 aarch64:
  ubuntu kernel 4.18.0-16-generic, eth: mlx5 connect-4lx
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)

  Same Xeon Skylake 8168 x86_64
  latest kernel 5.2.0-rc2
  eth: mlx5 connect-5
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 14:42 seq
   crw-rw 1 root audio 116, 33 Jun 12 14:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: AmpereComputing(R) OSPREY EV-883832-X3-0001
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=698f489c-124b-4ebb-b6c3-14c8b82c978d ro console=ttyAMA0,115200 
iommu.passthrough=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-16-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/25/2018
  dmi.bios.vendor: Ampere(TM)
  dmi.bios.version: 4.8.19
  dmi.board.asset.tag: APCX3A1-A526-16050501200016
  dmi.board.name: OSPREY
  dmi.board.vendor: AmpereComputing(R)
  dmi.board.version: EV-883832-X3-OD1-2
  dmi.chassis.asset.tag: APCX3A1-A526-16050501200016
  dmi.chassis.type: 23
  dmi.chassis.vendor: AmpereComputing(R)
  dmi.chassis.version: APCA1A1-
  dmi.modalias: 
dmi:bvnAmpere(TM):bvr4.8.19:bd09/25/2018:svnAmpereComputing(R):pnOSPREYEV-883832-X3-0001:pvrPR010:rvnAmpereComputing(R):rnOSPREY:rvrEV-883832-X3-OD1-2:cvnAmpereComputing(R):ct23:cvrAPCA1A1-:
  dmi.product.family: eMAG
  dmi.product.name: OSPREY EV-883832-X3-0001
  dmi.product.sku: EV-883832-X3-OBX-1
  dmi.product.version: PR010
  dmi.sys.vendor: AmpereComputing(R)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 15:22 seq
   crw-rw 1 root audio 116, 33 Jun 12 15:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R640
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=cc79d3b3-63ee-450d-84ff-ddd80ab73c80 ro intel_pstate=disable 
console=ttyS0,115200n8
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 

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

[Yangzheng Bai]

apport information

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

Title:
  4.15.0-46-generic doesn't support ethtool adaptive-tx for mlx5 card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Bionic 18.04 LTS:
  We found that default bionic kernel 4.15.0-46-generic doesn't support ethtool 
-C adaptive-tx
  Our ethernet card is Mellanox Connect4-Lx and Connect5, and this will affect 
performance of latency sensitive workloads like memcached.
  Maybe we should backport adaptive-tx support to kernel 4.15 LTS?

  
  Xeon Skylake 8168 x86_64:
  ubuntu kernel 4.15.0-46-generic
  eth: mlx5 connect-5
  ethtool doesn't support adaptive-tx (ethernet TX interrupt coalesce)

  X-Gene3 aarch64:
  ubuntu kernel 4.18.0-16-generic, eth: mlx5 connect-4lx
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)

  Same Xeon Skylake 8168 x86_64
  latest kernel 5.2.0-rc2
  eth: mlx5 connect-5
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 14:42 seq
   crw-rw 1 root audio 116, 33 Jun 12 14:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: AmpereComputing(R) OSPREY EV-883832-X3-0001
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=698f489c-124b-4ebb-b6c3-14c8b82c978d ro console=ttyAMA0,115200 
iommu.passthrough=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-16-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/25/2018
  dmi.bios.vendor: Ampere(TM)
  dmi.bios.version: 4.8.19
  dmi.board.asset.tag: APCX3A1-A526-16050501200016
  dmi.board.name: OSPREY
  dmi.board.vendor: AmpereComputing(R)
  dmi.board.version: EV-883832-X3-OD1-2
  dmi.chassis.asset.tag: APCX3A1-A526-16050501200016
  dmi.chassis.type: 23
  dmi.chassis.vendor: AmpereComputing(R)
  dmi.chassis.version: APCA1A1-
  dmi.modalias: 
dmi:bvnAmpere(TM):bvr4.8.19:bd09/25/2018:svnAmpereComputing(R):pnOSPREYEV-883832-X3-0001:pvrPR010:rvnAmpereComputing(R):rnOSPREY:rvrEV-883832-X3-OD1-2:cvnAmpereComputing(R):ct23:cvrAPCA1A1-:
  dmi.product.family: eMAG
  dmi.product.name: OSPREY EV-883832-X3-0001
  dmi.product.sku: EV-883832-X3-OBX-1
  dmi.product.version: PR010
  dmi.sys.vendor: AmpereComputing(R)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 15:22 seq
   crw-rw 1 root audio 116, 33 Jun 12 15:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R640
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=cc79d3b3-63ee-450d-84ff-ddd80ab73c80 ro intel_pstate=disable 
console=ttyS0,115200n8
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  RfKill: 

[Kernel-packages] [Bug 1832641] Re: 4.15.0-46-generic doesn't support ethtool adaptive-tx for mlx5 card

[Yangzheng Bai]

apport information

** Tags added: apport-collected uec-images

** Description changed:

  Ubuntu Bionic 18.04 LTS:
  We found that default bionic kernel 4.15.0-46-generic doesn't support ethtool 
-C adaptive-tx
  Our ethernet card is Mellanox Connect4-Lx and Connect5, and this will affect 
performance of latency sensitive workloads like memcached.
  Maybe we should backport adaptive-tx support to kernel 4.15 LTS?
  
  
  Xeon Skylake 8168 x86_64:
  ubuntu kernel 4.15.0-46-generic
  eth: mlx5 connect-5
  ethtool doesn't support adaptive-tx (ethernet TX interrupt coalesce)
  
  X-Gene3 aarch64:
  ubuntu kernel 4.18.0-16-generic, eth: mlx5 connect-4lx
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)
  
  Same Xeon Skylake 8168 x86_64
  latest kernel 5.2.0-rc2
  eth: mlx5 connect-5
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)
+ --- 
+ ProblemType: Bug
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 Jun 12 14:42 seq
+  crw-rw 1 root audio 116, 33 Jun 12 14:42 timer
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
+ ApportVersion: 2.20.9-0ubuntu7.6
+ Architecture: arm64
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ DistroRelease: Ubuntu 18.04
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
+ MachineType: AmpereComputing(R) OSPREY EV-883832-X3-0001
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=C.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 astdrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=698f489c-124b-4ebb-b6c3-14c8b82c978d ro console=ttyAMA0,115200 
iommu.passthrough=1
+ ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
+ RelatedPackageVersions:
+  linux-restricted-modules-4.18.0-16-generic N/A
+  linux-backports-modules-4.18.0-16-generic  N/A
+  linux-firmware 1.173.3
+ RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
+ Tags:  bionic uec-images
+ Uname: Linux 4.18.0-16-generic aarch64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 09/25/2018
+ dmi.bios.vendor: Ampere(TM)
+ dmi.bios.version: 4.8.19
+ dmi.board.asset.tag: APCX3A1-A526-16050501200016
+ dmi.board.name: OSPREY
+ dmi.board.vendor: AmpereComputing(R)
+ dmi.board.version: EV-883832-X3-OD1-2
+ dmi.chassis.asset.tag: APCX3A1-A526-16050501200016
+ dmi.chassis.type: 23
+ dmi.chassis.vendor: AmpereComputing(R)
+ dmi.chassis.version: APCA1A1-
+ dmi.modalias: 
dmi:bvnAmpere(TM):bvr4.8.19:bd09/25/2018:svnAmpereComputing(R):pnOSPREYEV-883832-X3-0001:pvrPR010:rvnAmpereComputing(R):rnOSPREY:rvrEV-883832-X3-OD1-2:cvnAmpereComputing(R):ct23:cvrAPCA1A1-:
+ dmi.product.family: eMAG
+ dmi.product.name: OSPREY EV-883832-X3-0001
+ dmi.product.sku: EV-883832-X3-OBX-1
+ dmi.product.version: PR010
+ dmi.sys.vendor: AmpereComputing(R)

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

Title:
  4.15.0-46-generic doesn't support ethtool adaptive-tx for mlx5 card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Bionic 18.04 LTS:
  We found that default bionic kernel 4.15.0-46-generic doesn't support ethtool 
-C adaptive-tx
  Our ethernet card is Mellanox Connect4-Lx and Connect5, and this will affect 
performance of latency sensitive workloads like memcached.
  Maybe we should backport adaptive-tx support to kernel 4.15 LTS?

  
  Xeon Skylake 8168 x86_64:
  ubuntu kernel 4.15.0-46-generic
  eth: mlx5 connect-5
  ethtool doesn't support adaptive-tx (ethernet TX interrupt coalesce)

  X-Gene3 aarch64:
  ubuntu kernel 4.18.0-16-generic, eth: mlx5 connect-4lx
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)

  Same Xeon Skylake 8168 x86_64
  latest kernel 5.2.0-rc2
  eth: mlx5 connect-5
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 14:42 seq
   crw-rw 1 root audio 116, 33 Jun 12 14:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: AmpereComputing(R) OSPREY EV-883832-X3-0001
  

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

[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 1832641

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

** Tags added: bionic

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

Title:
  4.15.0-46-generic doesn't support ethtool adaptive-tx for mlx5 card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Bionic 18.04 LTS:
  We found that default bionic kernel 4.15.0-46-generic doesn't support ethtool 
-C adaptive-tx
  Our ethernet card is Mellanox Connect4-Lx and Connect5, and this will affect 
performance of latency sensitive workloads like memcached.
  Maybe we should backport adaptive-tx support to kernel 4.15 LTS?

  
  Xeon Skylake 8168 x86_64:
  ubuntu kernel 4.15.0-46-generic
  eth: mlx5 connect-5
  ethtool doesn't support adaptive-tx (ethernet TX interrupt coalesce)

  X-Gene3 aarch64:
  ubuntu kernel 4.18.0-16-generic, eth: mlx5 connect-4lx
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)

  Same Xeon Skylake 8168 x86_64
  latest kernel 5.2.0-rc2
  eth: mlx5 connect-5
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832641/+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 1832641] Re: 4.15.0-46-generic doesn't support ethtool adaptive-tx for mlx5 card

[Yangzheng Bai]

kernel 4.18 supports Coalesce adaptive TX

uname -a
Linux xgene3 4.18.0-16-generic #17~18.04.1-Ubuntu SMP Tue Feb 12 13:35:39 UTC 
2019 aarch64 aarch64 aarch64 GNU/Linux

lspci -vvv
:01:00.0 Ethernet controller: Mellanox Technologies MT27710 Family 
[ConnectX-4 Lx]
Subsystem: Mellanox Technologies MT27710 Family [ConnectX-4 Lx]

ethtool -i enp1s0
driver: mlx5_core
version: 5.0-0
firmware-version: 14.24.1000 (MT_2430110032)
expansion-rom-version:
bus-info: :01:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: yes

ethtool -c enp1s0
Coalesce parameters for enp1s0:
Adaptive RX: on  TX: on
stats-block-usecs: 0
sample-interval: 0
pkt-rate-low: 0
pkt-rate-high: 0

rx-usecs: 8
rx-frames: 128
rx-usecs-irq: 0
rx-frames-irq: 0

tx-usecs: 8
tx-frames: 128
tx-usecs-irq: 0
tx-frames-irq: 0

rx-usecs-low: 0
rx-frame-low: 0
tx-usecs-low: 0
tx-frame-low: 0

rx-usecs-high: 0
rx-frame-high: 0
tx-usecs-high: 0
tx-frame-high: 0

lsmod
Module  Size  Used by
nls_iso8859_1  16384  1
rndis_wlan 57344  0
rndis_host 16384  1 rndis_wlan
cdc_ether  16384  1 rndis_host
usbnet 49152  3 rndis_wlan,rndis_host,cdc_ether
cfg80211  733184  1 rndis_wlan
joydev 28672  0
input_leds 16384  0
ipmi_ssif  28672  0
ipmi_devintf   20480  0
ipmi_msghandler57344  2 ipmi_devintf,ipmi_ssif
xgene_hwmon20480  0
cppc_cpufreq   16384  0
sch_fq_codel   20480  33
ib_iser49152  0
rdma_cm65536  1 ib_iser
iw_cm  40960  1 rdma_cm
ib_cm  61440  1 rdma_cm
iscsi_tcp  20480  0
libiscsi_tcp   28672  1 iscsi_tcp
libiscsi   53248  3 libiscsi_tcp,iscsi_tcp,ib_iser
scsi_transport_iscsi   110592  3 iscsi_tcp,ib_iser,libiscsi
ip_tables  28672  0
x_tables   45056  1 ip_tables
autofs453248  2
hid_generic16384  0
usbhid 61440  0
hid   131072  2 usbhid,hid_generic
btrfs1273856  0
zstd_compress 159744  1 btrfs
raid10 57344  0
raid456   167936  0
async_raid6_recov  20480  1 raid456
async_memcpy   16384  2 raid456,async_raid6_recov
async_pq   16384  2 raid456,async_raid6_recov
async_xor  16384  3 async_pq,raid456,async_raid6_recov
async_tx   16384  5 
async_pq,async_memcpy,async_xor,raid456,async_raid6_recov
xor20480  2 async_xor,btrfs
uas24576  0
usb_storage69632  1 uas
raid6_pq  106496  4 async_pq,btrfs,raid456,async_raid6_recov
libcrc32c  16384  2 btrfs,raid456
raid1  40960  0
raid0  20480  0
multipath  20480  0
linear 16384  0
mlx5_ib   237568  0
ib_uverbs 106496  1 mlx5_ib
ib_core   266240  6 rdma_cm,iw_cm,ib_iser,ib_uverbs,mlx5_ib,ib_cm
dwc3  151552  0
ulpi   16384  1 dwc3
udc_core   57344  1 dwc3
ast61440  1
mlx5_core 671744  1 mlx5_ib
ttm   118784  1 ast
aes_ce_blk 28672  0
aes_ce_cipher  16384  1 aes_ce_blk
drm_kms_helper196608  1 ast
crc32_ce   16384  3
crct10dif_ce   16384  0
syscopyarea16384  1 drm_kms_helper
ghash_ce   20480  0
sysfillrect16384  1 drm_kms_helper
sha2_ce16384  0
sysimgblt  16384  1 drm_kms_helper
tls57344  1 mlx5_core
sha256_arm64   24576  1 sha2_ce
fb_sys_fops16384  1 drm_kms_helper
igb   229376  0
sha1_ce16384  0
mlxfw  20480  1 mlx5_core
drm   471040  4 drm_kms_helper,ast,ttm
i2c_algo_bit   16384  2 igb,ast
devlink53248  1 mlx5_core
ahci_platform  16384  2
libahci_platform   20480  1 ahci_platform
libahci40960  2 libahci_platform,ahci_platform
i2c_xgene_slimpro  16384  0
gpio_dwapb 20480  0
xhci_plat_hcd  20480  0
aes_neon_bs24576  1
aes_neon_blk   28672  1 aes_neon_bs
crypto_simd16384  3 aes_neon_bs,aes_ce_blk,aes_neon_blk
cryptd 28672  1 crypto_simd
aes_arm64  16384  5 
aes_neon_bs,aes_ce_cipher,ghash_ce,aes_ce_blk,aes_neon_blk




kernel 4.15 does NOT support Coalesce adaptive TX

uname -a
Linux x8168 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

lspci -vvv

[Kernel-packages] [Bug 1832641] [NEW] 4.15.0-46-generic doesn't support ethtool adaptive-tx for mlx5 card

[Yangzheng Bai]

Public bug reported:

Ubuntu Bionic 18.04 LTS:
We found that default bionic kernel 4.15.0-46-generic doesn't support ethtool 
-C adaptive-tx
Our ethernet card is Mellanox Connect4-Lx and Connect5, and this will affect 
performance of latency sensitive workloads like memcached.
Maybe we should backport adaptive-tx support to kernel 4.15 LTS?


Xeon Skylake 8168 x86_64:
ubuntu kernel 4.15.0-46-generic
eth: mlx5 connect-5
ethtool doesn't support adaptive-tx (ethernet TX interrupt coalesce)

X-Gene3 aarch64:
ubuntu kernel 4.18.0-16-generic, eth: mlx5 connect-4lx
ethtool supports adaptive-tx (ethernet TX interrupt coalesce)

Same Xeon Skylake 8168 x86_64
latest kernel 5.2.0-rc2
eth: mlx5 connect-5
ethtool supports adaptive-tx (ethernet TX interrupt coalesce)

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

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

Title:
  4.15.0-46-generic doesn't support ethtool adaptive-tx for mlx5 card

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu Bionic 18.04 LTS:
  We found that default bionic kernel 4.15.0-46-generic doesn't support ethtool 
-C adaptive-tx
  Our ethernet card is Mellanox Connect4-Lx and Connect5, and this will affect 
performance of latency sensitive workloads like memcached.
  Maybe we should backport adaptive-tx support to kernel 4.15 LTS?

  
  Xeon Skylake 8168 x86_64:
  ubuntu kernel 4.15.0-46-generic
  eth: mlx5 connect-5
  ethtool doesn't support adaptive-tx (ethernet TX interrupt coalesce)

  X-Gene3 aarch64:
  ubuntu kernel 4.18.0-16-generic, eth: mlx5 connect-4lx
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)

  Same Xeon Skylake 8168 x86_64
  latest kernel 5.2.0-rc2
  eth: mlx5 connect-5
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)

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

[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 1832435

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

Title:
  Lenovo miix 510 wifi adapter cannot be turned on

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This problem appears when you first install ubuntu 18.04, 18.10, and
  19.10 on a Lenovo Miix 501 laptop. I have not tried previous versions
  of ubuntu.  After installation or update to a newer versio of ubuntu
  the network adaptor is set to off and cannot be turned on. I believe
  this is because of a non-existent or faulty driver for the intel 8260
  wifi adapter. It also could be that the driver is waiting for physical
  or keyboard switch to turn on the adapter. However, no such switch
  exists in this laptop model.

  The problem can be resolved by adding "blacklist ideapad_laptop" to
  the configuration file

  /etc/modprobe.d/blacklist.conf

  (this is for ubuntu 19.04. The filename and location are different for
  18.04 and 18.10)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832435/+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 1813463] Re: no bluetooth intel ac 9260

[Brian Murray]

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

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

Title:
  no bluetooth intel ac 9260

Status in bluez package in Ubuntu:
  New

Bug description:
  Hi All

  Using a laptop with the intel AC 9260 wireless card that also has Bluetooth 
5.0.
  Booting either ubuntu 18.04 or 18.10 with kernel 4.18.* through to 4.20.* the 
bluetooth is not detected and can't be switched on.

  hciconfig -a
  Produces no result

  $ bluetoothctl
  Agent registered
  [bluetooth]# show
  No default controller available
  [bluetooth]# devices
  No default controller available
  [bluetooth]#

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1813463/+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 1830792] Re: [i915] Rotated display is overscaled and overdrawn while i915 crashes repeatedly

[Christopher Nelson]

This time I turned off the displayed, unplugged it, then left it
unplugged while I rebooted. After rebooting and logging in, I turned on
the display and plugged it in. Attached is the dmesg from this boot.

** Attachment added: "dmesg from functional boot"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5270411/+files/dmesg.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/1830792

Title:
  [i915] Rotated display is overscaled and overdrawn while i915 crashes
  repeatedly

Status in gnome-shell package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  On my system I have two display: one in landscape, and one in
  portrait. The landscape display is fine, but the portrait display is
  corrupted. If I unplug the display from the computer for some time and
  then plug it back in it will occasionally fix the problem.

  Once the problem is fixed, the display works perfectly fine,
  indefinitely. However, as soon as I reboot the computer the display
  will come up corrupted again and never recovers without many rounds of
  plug/unplug turn off/turn on. It's extremely frustrating.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 28 15:57:02 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-22 (36 days ago)
  modified.conffile..etc.logrotate.d.apport: [modified]
  mtime.conffile..etc.logrotate.d.apport: 2019-01-12T15:50:59.090583

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+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 1830792] Re: [i915] Rotated display is overscaled and overdrawn while i915 crashes repeatedly

[Christopher Nelson]

** Attachment added: "journalctl -b0 from successful screen activation"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5270412/+files/journal.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/1830792

Title:
  [i915] Rotated display is overscaled and overdrawn while i915 crashes
  repeatedly

Status in gnome-shell package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  On my system I have two display: one in landscape, and one in
  portrait. The landscape display is fine, but the portrait display is
  corrupted. If I unplug the display from the computer for some time and
  then plug it back in it will occasionally fix the problem.

  Once the problem is fixed, the display works perfectly fine,
  indefinitely. However, as soon as I reboot the computer the display
  will come up corrupted again and never recovers without many rounds of
  plug/unplug turn off/turn on. It's extremely frustrating.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 28 15:57:02 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-22 (36 days ago)
  modified.conffile..etc.logrotate.d.apport: [modified]
  mtime.conffile..etc.logrotate.d.apport: 2019-01-12T15:50:59.090583

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+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 1832435] Re: Lenovo miix 510 wifi adapter cannot be turned on

[Brian Murray]

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

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

Title:
  Lenovo miix 510 wifi adapter cannot be turned on

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This problem appears when you first install ubuntu 18.04, 18.10, and
  19.10 on a Lenovo Miix 501 laptop. I have not tried previous versions
  of ubuntu.  After installation or update to a newer versio of ubuntu
  the network adaptor is set to off and cannot be turned on. I believe
  this is because of a non-existent or faulty driver for the intel 8260
  wifi adapter. It also could be that the driver is waiting for physical
  or keyboard switch to turn on the adapter. However, no such switch
  exists in this laptop model.

  The problem can be resolved by adding "blacklist ideapad_laptop" to
  the configuration file

  /etc/modprobe.d/blacklist.conf

  (this is for ubuntu 19.04. The filename and location are different for
  18.04 and 18.10)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832435/+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 961239] Re: 14e4:1648 Broadcom NIC (tg3) not working with DMA errors

[Scott Smith]

Validated functionality on 19.04 with inbox driver version 3.137
Traffic passes as expected

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

Title:
  14e4:1648 Broadcom NIC (tg3) not working with DMA errors

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  All information should be included in the attached debug information - short 
summary:
  While setting the network interface "up" after boot (ip link set up dev 
eth0), I get some DMA errors and dumps from tg3. After that the interface is 
"up", but I'm unable to pass any traffic over that network interface.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-19-generic 3.2.0-19.30
  ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
  Uname: Linux 3.2.0-19-generic x86_64
  AlsaDevices:
   total 0
   crw-rw---T 1 root audio 116,  1 Mar 19 10:43 seq
   crw-rw---T 1 root audio 116, 33 Mar 19 10:43 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Date: Mon Mar 19 10:46:05 2012
  HibernationDevice: RESUME=UUID=148f8b55-c516-40b0-98f0-aec3860ab5f3
  InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120315)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 002: ID 6189:182d Sitecom USB 2.0 Ethernet
  MachineType: IBM IBM x3850-[88631RG]-
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-19-generic 
root=/dev/mapper/main-root ro
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-19-generic N/A
   linux-backports-modules-3.2.0-19-generic  N/A
   linux-firmware1.71
  RfKill: Error: [Errno 2] No such file or directory
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2008
  dmi.bios.vendor: IBM
  dmi.bios.version: -[ZUE166AUS-1.12]-
  dmi.board.name: Node1 Processor Card
  dmi.board.vendor: IBM
  dmi.chassis.type: 17
  dmi.chassis.vendor: IBM
  dmi.modalias: 
dmi:bvnIBM:bvr-[ZUE166AUS-1.12]-:bd02/15/2008:svnIBM:pnIBMx3850-[88631RG]-:pvr:rvnIBM:rnNode1ProcessorCard:rvr:cvnIBM:ct17:cvr:
  dmi.product.name: IBM x3850-[88631RG]-
  dmi.sys.vendor: IBM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/961239/+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 1832435] [NEW] Lenovo miix 510 wifi adapter cannot be turned on

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

This problem appears when you first install ubuntu 18.04, 18.10, and
19.10 on a Lenovo Miix 501 laptop. I have not tried previous versions of
ubuntu.  After installation or update to a newer versio of ubuntu the
network adaptor is set to off and cannot be turned on. I believe this is
because of a non-existent or faulty driver for the intel 8260 wifi
adapter. It also could be that the driver is waiting for physical or
keyboard switch to turn on the adapter. However, no such switch exists
in this laptop model.

The problem can be resolved by adding "blacklist ideapad_laptop" to the
configuration file

/etc/modprobe.d/blacklist.conf

(this is for ubuntu 19.04. The filename and location are different for
18.04 and 18.10)

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


** Tags: bot-comment
-- 
Lenovo miix 510 wifi adapter cannot be turned on
https://bugs.launchpad.net/bugs/1832435
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1819116] Re: sync_file_range02 in ubuntu_ltp_syscalls fails

[Sean Feole]

This also affects Eoan 5.2.0-4.5-generic, on bare-metal or the AWS
cloud.

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
   Status: Incomplete

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

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

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

** Tags added: eoan linux-generic sru-20190603

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

Title:
  sync_file_range02 in ubuntu_ltp_syscalls fails

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-gke package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-aws source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux-gke source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux-aws source package in Cosmic:
  New
Status in linux-azure source package in Cosmic:
  New
Status in linux source package in Disco:
  Incomplete
Status in linux-aws source package in Disco:
  New
Status in linux-azure source package in Disco:
  New
Status in linux source package in Eoan:
  Incomplete
Status in linux-aws source package in Eoan:
  New
Status in linux-azure source package in Eoan:
  New
Status in linux-gke source package in Eoan:
  New

Bug description:
  syslog output attached as attachment.

  <<>>
  incrementing stop
  tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2'
  tst_supported_fs_types.c:72: INFO: Kernel supports ext2
  tst_supported_fs_types.c:56: INFO: mkfs.ext2 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports ext3
  tst_supported_fs_types.c:56: INFO: mkfs.ext3 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports ext4
  tst_supported_fs_types.c:56: INFO: mkfs.ext4 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports xfs
  tst_supported_fs_types.c:56: INFO: mkfs.xfs does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports btrfs
  tst_supported_fs_types.c:56: INFO: mkfs.btrfs does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports vfat
  tst_supported_fs_types.c:56: INFO: mkfs.vfat does exist
  tst_supported_fs_types.c:95: INFO: Filesystem exfat is not supported
  tst_supported_fs_types.c:72: INFO: Kernel supports ntfs
  tst_supported_fs_types.c:56: INFO: mkfs.ntfs does exist
  tst_test.c:1157: INFO: Testing on ext2
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts=''
  mke2fs 1.44.6 (5-Mar-2019)
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on ext3
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext3 opts='' extra opts=''
  mke2fs 1.44.6 (5-Mar-2019)
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on ext4
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext4 opts='' extra opts=''
  mke2fs 1.44.6 (5-Mar-2019)
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on xfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with xfs opts='' extra opts=''
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on btrfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with btrfs opts='' extra opts=''
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on vfat
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with vfat opts='' extra opts=''
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on ntfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ntfs opts='' extra opts=''
  The partition start sector was not specified for /dev/loop2 and it could not 
be obtained automatically.  It has been set to 0.
  The number of sectors per track was not specified for /dev/loop2 and it could 
not be obtained automatically.  It has been set to 0.
  The number of heads was not specified for /dev/loop2 and it could not be 
obtained automatically.  It has been set to 0.
  To boot from a device, Windows needs the 'partition start sector', the 
'sectors per track' and the 'number of heads' to be set.
  Windows will not be able to boot from this device.
  safe_macros.c:739: INFO: Trying FUSE...
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  

[Kernel-packages] [Bug 1813463] [NEW] no bluetooth intel ac 9260

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hi All

Using a laptop with the intel AC 9260 wireless card that also has Bluetooth 5.0.
Booting either ubuntu 18.04 or 18.10 with kernel 4.18.* through to 4.20.* the 
bluetooth is not detected and can't be switched on.

hciconfig -a
Produces no result

$ bluetoothctl
Agent registered
[bluetooth]# show
No default controller available
[bluetooth]# devices
No default controller available
[bluetooth]#

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


** Tags: bot-comment
-- 
no bluetooth intel ac 9260
https://bugs.launchpad.net/bugs/1813463
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to bluez in Ubuntu.

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

[Kernel-packages] [Bug 1819116] Re: sync_file_range02 in ubuntu_ltp_syscalls fails

[Sean Feole]

** Attachment added: "client.DEBUG"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819116/+attachment/5270409/+files/client.DEBUG

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

Title:
  sync_file_range02 in ubuntu_ltp_syscalls fails

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-gke package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-aws source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux-gke source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux-aws source package in Cosmic:
  New
Status in linux-azure source package in Cosmic:
  New
Status in linux source package in Disco:
  Incomplete
Status in linux-aws source package in Disco:
  New
Status in linux-azure source package in Disco:
  New
Status in linux source package in Eoan:
  Incomplete
Status in linux-aws source package in Eoan:
  New
Status in linux-azure source package in Eoan:
  New
Status in linux-gke source package in Eoan:
  New

Bug description:
  syslog output attached as attachment.

  <<>>
  incrementing stop
  tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2'
  tst_supported_fs_types.c:72: INFO: Kernel supports ext2
  tst_supported_fs_types.c:56: INFO: mkfs.ext2 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports ext3
  tst_supported_fs_types.c:56: INFO: mkfs.ext3 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports ext4
  tst_supported_fs_types.c:56: INFO: mkfs.ext4 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports xfs
  tst_supported_fs_types.c:56: INFO: mkfs.xfs does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports btrfs
  tst_supported_fs_types.c:56: INFO: mkfs.btrfs does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports vfat
  tst_supported_fs_types.c:56: INFO: mkfs.vfat does exist
  tst_supported_fs_types.c:95: INFO: Filesystem exfat is not supported
  tst_supported_fs_types.c:72: INFO: Kernel supports ntfs
  tst_supported_fs_types.c:56: INFO: mkfs.ntfs does exist
  tst_test.c:1157: INFO: Testing on ext2
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts=''
  mke2fs 1.44.6 (5-Mar-2019)
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on ext3
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext3 opts='' extra opts=''
  mke2fs 1.44.6 (5-Mar-2019)
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on ext4
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext4 opts='' extra opts=''
  mke2fs 1.44.6 (5-Mar-2019)
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on xfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with xfs opts='' extra opts=''
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on btrfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with btrfs opts='' extra opts=''
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on vfat
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with vfat opts='' extra opts=''
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on ntfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ntfs opts='' extra opts=''
  The partition start sector was not specified for /dev/loop2 and it could not 
be obtained automatically.  It has been set to 0.
  The number of sectors per track was not specified for /dev/loop2 and it could 
not be obtained automatically.  It has been set to 0.
  The number of heads was not specified for /dev/loop2 and it could not be 
obtained automatically.  It has been set to 0.
  To boot from a device, Windows needs the 'partition start sector', the 
'sectors per track' and the 'number of heads' to be set.
  Windows will not be able to boot from this device.
  safe_macros.c:739: INFO: Trying FUSE...
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:56: FAIL: Synced 0, expected 33554432

  Summary:
  passed   6
  failed   1
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=11 termination_type=exited termination_id=1 corefile=no
  cutime=10 cstime=157
  <<>>
  INFO: ltp-pan reported some tests FAIL
  LTP Version: 20190115

 

[Kernel-packages] [Bug 1818134] Re: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic

[Steve Langasek]

Thanks for confirming.

> Should the shim-signed package have a dependency on a kernel that is
new enough?

For better or worse, there is no straightforward way to express such a
dependency.  But also, the fundamental problem here is not that shim-
signed has new requirements.  The fundamental problem is that you and
other users have been running a kernel that has had no security updates
for over 2 years and didn't know it.  While it was stated at the time
that these kernels would have security support for a limited time and
that users who had these kernels installed would not be automatically
rolled forward to the next series (as this might introduce regressions
in hardware support), evidently this information was not communicated in
a way that made it clear to users that they were out of security
support.

I will look into what can be done to improve the communication to users
in all the usual places that information about security updates are
communicated, to let users know they are running unsupported kernels.

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1818134/+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 1832634] [NEW] libhugetlbfs FAIL small_const is not hugepage

[Sean Feole]

Public bug reported:

Series: Eoan
Kernel: 5.2.0-4.5-generic
Metal Or Clouds Affected: (Bare Metal Intel) & AWS
Instance Type: Any

This bug has been seen in prior series, however not really officially tracked  
and followed up on. We will do that here. 
 
libhugetlbfs fails with the following.

06/12 18:56:14 DEBUG| utils:0153| [stdout] linkhuge_rw (2M: 64):PASS
06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=R linkhuge_rw 
(2M: 64):   FAILsmall_const is not hugepage
06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=W linkhuge_rw 
(2M: 64):
06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=RW linkhuge_rw 
(2M: 64):  FAILsmall_data is not hugepage
06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=no linkhuge_rw 
(2M: 64):  PASS
06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=R 
HUGETLB_MINIMAL_COPY=no linkhuge_rw (2M: 64):   FAILsmall_const is not 
hugepage
06/12 18:56:16 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=W 
HUGETLB_MINIMAL_COPY=no linkhuge_rw (2M: 64):   FAILsmall_data is not 
hugepage
06/12 18:56:16 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=RW 
HUGETLB_MINIMAL_COPY=no linkhuge_rw (2M: 64):  FAILsmall_data is not 
hugepage
06/12 18:56:16 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=0 HUGETLB_ELFMAP=R 
linkhuge_rw (2M: 64):   FAILsmall_const is not hugepage
06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=1 HUGETLB_ELFMAP=R 
linkhuge_rw (2M: 64):   FAILsmall_const is not hugepage
06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=0 HUGETLB_ELFMAP=W 
linkhuge_rw (2M: 64):
06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=1 HUGETLB_ELFMAP=W 
linkhuge_rw (2M: 64):
06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=0 
HUGETLB_ELFMAP=RW linkhuge_rw (2M: 64):  FAILsmall_data is not hugepage
06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=1 
HUGETLB_ELFMAP=RW linkhuge_rw (2M: 64):  FAILsmall_data is not hugepage
06/12 18:56:17 DEBUG| utils:0153| [stdout] chunk-overcommit (2M: 64):   
PASS

Full logs attached.

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: Confirmed

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

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


** Tags: amd64 eoan libhugetlbfs linux-generic sru-20190603

** Attachment added: "client.DEBUG"
   
https://bugs.launchpad.net/bugs/1832634/+attachment/5270406/+files/client.DEBUG

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

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

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
   Status: Confirmed

** Description changed:

  Series: Eoan
  Kernel: 5.2.0-4.5-generic
- Clouds Affected: AWS
+ Metal Or Clouds Affected: (Bare Metal Intel) & AWS
  Instance Type: Any
  
  libhugetlbfs fails with the following.
  
- 
  06/12 18:56:14 DEBUG| utils:0153| [stdout] linkhuge_rw (2M: 64):  PASS
  06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=R linkhuge_rw 
(2M: 64): FAILsmall_const is not hugepage
- 06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=W linkhuge_rw 
(2M: 64): 
+ 06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=W linkhuge_rw 
(2M: 64):
  06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=RW linkhuge_rw 
(2M: 64):FAILsmall_data is not hugepage
  06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=no linkhuge_rw 
(2M: 64):PASS
  06/12 18:56:15 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=R 
HUGETLB_MINIMAL_COPY=no linkhuge_rw (2M: 64): FAILsmall_const is not 
hugepage
  06/12 18:56:16 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=W 
HUGETLB_MINIMAL_COPY=no linkhuge_rw (2M: 64): FAILsmall_data is not hugepage
  06/12 18:56:16 DEBUG| utils:0153| [stdout] HUGETLB_ELFMAP=RW 
HUGETLB_MINIMAL_COPY=no linkhuge_rw (2M: 64):FAILsmall_data is not 
hugepage
  06/12 18:56:16 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=0 
HUGETLB_ELFMAP=R linkhuge_rw (2M: 64): FAILsmall_const is not hugepage
  06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=1 
HUGETLB_ELFMAP=R linkhuge_rw (2M: 64): FAILsmall_const is not hugepage
- 06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=0 
HUGETLB_ELFMAP=W linkhuge_rw (2M: 64): 
- 06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=1 
HUGETLB_ELFMAP=W linkhuge_rw (2M: 64): 
+ 06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=0 
HUGETLB_ELFMAP=W linkhuge_rw (2M: 64):
+ 06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=1 
HUGETLB_ELFMAP=W linkhuge_rw (2M: 64):
  06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=0 
HUGETLB_ELFMAP=RW linkhuge_rw (2M: 64):FAILsmall_data is not 
hugepage
  06/12 18:56:17 DEBUG| utils:0153| [stdout] HUGETLB_SHARE=1 

[Kernel-packages] [Bug 1681909] Re: kdump is not captured in remote host when kdump over ssh is configured

[Guilherme G. Piccoli]

It came to my attention that this issue still exists; an user report on
x84-64 machine confirms that it's not only a ppc64 issue, it's a generic
problem due to some NICs behavior; even with link up, they are really
not ready to xmit packets. So, I could reproduce this by modifying
virtio to mimic this scenario, and I'm working in a solution/quirk on
kdump-tools (makedumpfile) package.

Cheers,


Guilherme

** Summary changed:

- [FEAT 18.10] dump is not captured in remote host when kdump over ssh is 
configured on firestone.
+ kdump is not captured in remote host when kdump over ssh is configured

** No longer affects: makedumpfile (Ubuntu)

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

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

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

** Changed in: makedumpfile (Ubuntu)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

** Also affects: makedumpfile (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

** Also affects: makedumpfile (Ubuntu Eoan)
   Importance: Medium
 Assignee: Guilherme G. Piccoli (gpiccoli)
   Status: Confirmed

** Also affects: makedumpfile (Ubuntu Disco)
   Importance: Undecided
   Status: New

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

** Changed in: makedumpfile (Ubuntu Bionic)
   Status: New => Confirmed

** Changed in: makedumpfile (Ubuntu Cosmic)
   Status: New => Confirmed

** Changed in: makedumpfile (Ubuntu Disco)
   Status: New => Confirmed

** Changed in: makedumpfile (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: makedumpfile (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: makedumpfile (Ubuntu Cosmic)
   Importance: Undecided => Medium

** Changed in: makedumpfile (Ubuntu Disco)
   Importance: Undecided => Medium

** Changed in: makedumpfile (Ubuntu Disco)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

** Changed in: makedumpfile (Ubuntu Cosmic)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

** Changed in: makedumpfile (Ubuntu Bionic)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

** Changed in: makedumpfile (Ubuntu Xenial)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

** Tags removed: targetmilestone-inin16043
** Tags added: sts

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

Title:
  kdump is not captured in remote host when kdump over ssh is configured

Status in The Ubuntu-power-systems project:
  Incomplete
Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Xenial:
  Confirmed
Status in makedumpfile source package in Bionic:
  Confirmed
Status in makedumpfile source package in Cosmic:
  Confirmed
Status in makedumpfile source package in Disco:
  Confirmed
Status in makedumpfile source package in Eoan:
  Confirmed

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH  - 2017-03-07 
05:00:29 ==
  ---Problem Description---

  Ubuntu 17.04: dump is not captured in remote host when kdump over ssh
  is configured on firestone.

  ---Steps to Reproduce---

  1. Configure kdump.
  2. Check whether kdump is operational using ?# kdump-config show?.
  3. Install ?kernel-debuginfo? and ?kernel-debuginfo-common? rpms.
  4. Setup password less ssh connection, generate rsa key.
  # ssh-keygen -t rsa
  5. verify id_rsa and id_rsa.pub are created under /root/.ssh/
  6. Edit /etc/default/kdump-tools and add below entries.
  SSH="ubuntu@9.114.15.239"
  SSH_KEY=/root/.ssh/id_rsa
  7. Propagate RSA key.
  # kdump-config propagate
  8. Restart kdump service.
  # kdump-config load
  9. Trigger Crash using below commands.
  # echo "1" > /proc/sys/kernel/sysrq
  # echo "c" > /proc/sysrq-trigger
  10. Verify dump is available in remote server in configured path.

  Machine details
  ===

  $ ipmitool -I lanplus -H  9.47.70.3 -U ADMIN -P admin sol activate

  $ ssh ubuntu@9.47.70.29

  PW: shriya101

  
  Attaching logs

  == Comment: #1 - PAVITHRA R. PRAKASH  -
  2017-03-07 05:01:42 ==

  
  == Comment: #5 - PAVITHRA R. PRAKASH  - 2017-03-07 
23:19:46 ==
  Hi, 

  Attaching the logs.

  Network info:

  root@ltc-firep3:~# hwinfo --network
  36: None 00.0: 10700 Loopback   
[Created at net.126]
Unique ID: ZsBS.GQNx7L4uPNA
SysFS ID: /class/net/lo
Hardware Class: network interface
Model: "Loopback network interface"
Device File: lo
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown

  37: None 00.0: 10701 Ethernet
[Created at net.126]
  

[Kernel-packages] [Bug 1694976] Re: libhugetlbfs linkhuge test failures

[Sean Feole]

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

** This bug has been marked a duplicate of bug 1832634
   libhugetlbfs FAIL small_const is not hugepage

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

Title:
  libhugetlbfs linkhuge test failures

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In artful some of the tests in the hugetlbfs linkhuge test are
  failing.

  xB.linkhuge (2M: 32):   FAILsmall_bss is not hugepage
  HUGETLB_SHARE=0 xB.linkhuge (2M: 32):   FAILsmall_bss is not hugepage
  HUGETLB_SHARE=1 xB.linkhuge (2M: 32):   FAILsmall_bss is not hugepage
  HUGETLB_ELFMAP=R linkhuge_rw (2M: 32):  FAILsmall_const is not hugepage
  HUGETLB_ELFMAP=W HUGETLB_MINIMAL_COPY=no linkhuge_rw (2M: 32):  FAIL
small_data is not hugepage
  HUGETLB_ELFMAP=RW HUGETLB_MINIMAL_COPY=no linkhuge_rw (2M: 32): FAIL
small_data is not hugepage
  HUGETLB_SHARE=0 HUGETLB_ELFMAP=R linkhuge_rw (2M: 32):  FAILsmall_const 
is not hugepage
  HUGETLB_SHARE=1 HUGETLB_ELFMAP=R linkhuge_rw (2M: 32):  FAILsmall_const 
is not hugepage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694976/+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 1832623] Re: [UBUNTU] kernel: Fix gcm-aes-s390 wrong scatter-gather list processing

[Andrew Cloke]

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: ubuntu-z-systems
   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/1832623

Title:
  [UBUNTU] kernel: Fix gcm-aes-s390 wrong scatter-gather list processing

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Description:   kernel: Fix gcm-aes-s390 wrong scatter-gather list processing
  Symptom:   gcm-aes-s390 wrong en/decryption processing
  Problem:   The current gcm aes s390 implementation does not process
 scatter-gather input and output lists correct when list
 entries with sizes not multiples of the blocksize of 16
 bytes are used. Result may be wrong calculated encrypted
 or decrypted data.
 This can only happen on z14 (this is the only machine
 which supports aes-gcm in hardware via CPACF). Please note
 that applications using aes-gcm via the AF_ALG interface are
 not affected as this API ensures scatter/gather list entries
 with chunk sizes in multiples of 16 bytes. However, all
 exploiters of aes-gcm within the kernel may be affected.
  Solution:  Rework of the scatter/gather walk within the aes_s390 kernel
 module implementation with the goal to support any list
 entry size.
  Reproduction:  With kernel 5.1 there has been an improvement on the crypto
 selftests. There are now tests run with fragmented
 scatter/gather lists. So:
 1. You need at least a z14 and kernel >= 5.1.
 2. If disabled, enable the crypto self tests.
 3. Watch for syslog entries during modprobe of the aes_s390
kernel module. As this module usually gets automatically
inserted during system startup you may need to unload the
aes_s390 kernel module before re-inserting it.
 4. Without the fix something like
"kernel: alg: aead: gcm-aes-s390 encryption test failed
(wrong result) on test vector 1,..."
will show up. With the fix, all selftests will pass and
nothing is reported in syslog.

  Component: kernel
  Upstream-ID:   bef9f0ba300a55d79a69aa172156072182176515

  This request is targeted for 19.10, but should also be applied to
  18.04 and 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1832623/+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 1832624] Re: [UBUNTU] kernel: Fix wrong dispatching for control domain CPRBs

[Andrew Cloke]

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
   Importance: Undecided => High

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

Title:
  [UBUNTU] kernel: Fix wrong dispatching for control domain CPRBs

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Description:   kernel: Fix wrong dispatching for control domain CPRBs

  Symptom:   Unable to maintain control-only crypto domains

  Problem:   LPARs may have control-only crypto domains assigned.
 Such a domain can be controlled (for example master keys can
 be set) but can't be used for regualar crypto load (usage).
 A crypto domain may be assigned for control-and-usage to
 only one active LPAR. But the very same domain may be
 assigned for control-only to one or more other LPARs.
 However, trying to communicate in any way with a
 control-only crypto domain did not work. So a simple query
 for the state of the master keys on a control-only domain
 failed and the TKE does not even show this domain. Even
 worse, when the lowest domain (in a numerically sense) is a
 control-only domain, the TKE does not even see the crypto
 cards at all.

  Solution:  This fix introduces some code which checks if an CCA CPRB is
 addressing a control-only domain. If that's the case and
 there is a default control-and-usage domain available the
 CPRB is send to this other domain instead. The target domain
 field within the CPRB is untouched and the crypto card
 firmware code detects this working-as-designed mismatch and
 does the right job and addresses the control domain.

  Reproduction:  1. Add a control-only domain to the crypto configuration of
an LPAR and re-activate the LPAR.
 2. Connect the TKE the LPAR and try to visit the master key
verification patterns of this control-only domain.
 3. Will fail without the fix, will succeed with the fix.

  Component: kernel
  Upstream-ID:   7379e652797c0b9b5f6caea1576f2dff9ce6a708

  This fix is requested for 19.10 but should also be applied to 18.04
  and 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1832624/+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 1832625] Re: [UBUNTU] pkey: Indicate old mkvp only if old and curr. mkvp are different

[Andrew Cloke]

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
   Importance: Undecided => High

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

Title:
  [UBUNTU] pkey: Indicate old mkvp only if old and curr. mkvp are
  different

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Description:   pkey: Indicate old mkvp only if old and curr. mkvp are
  different

  Symptom:   zkey validate shows wrong information about master key
  registers

  Problem:   When the CCA master key is set twice with the same master key,
 then the old and the current master key are the same and thus
 the verification patterns are the same, too. The check to 
report
 if a secure key is currently wrapped by the old master key 
 erroneously reports old mkvp in this case.

  Solution:  Fix this by checking current and old mkvp and report OLD only 
if
 current and old mkvp are different.

  Reproduction:  Change the CCA master key but set the exact same master
  key that is already used. Then do a 'zkey validate' command on a
  secure key

  Component: kernel 5.1 rc1
  Upstream-ID:   ebb7c695d3bc7a4986b92edc8d9ef43491be183e

  This fix will be provided with kernel >=5.1 , will be integrate in 19.10 by 
default.
  But should also be applied to 18.04 and 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1832625/+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 1822133] Re: Azure Instance never recovered during series of instance reboots.

[Tom Wilberding]

@sfeole, checking with our devops folks. I don't have Azure access to
the hosts in question.

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

Title:
  Azure Instance never recovered during series of instance reboots.

Status in linux-azure package in Ubuntu:
  In Progress

Bug description:
  Description: During SRU Testing of various Azure Instances, there will
  be some cases where the instance will not respond following a system
  reboot.  SRU Testing only restarts a giving instance once, after it
  preps all of the necessary files to-be-tested.

  Series: Disco
  Instance Size: Basic_A3
  Region: (Default) US-WEST-2
  Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  I initiated a series of tests which rebooted Azure Cloud instances 50
  times. During the 49th Reboot, an Instance failed to return from a
  reboot.. Upon grabbing the console output the following was seen
  scrolling endlessly. I have seen this failure in cases where the
  instance only restarted a handful of times >5

  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus

  In another test attempt I saw the following failure:

  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes

  
  Both of these failures broke networking, Both of these failures were seen at 
least twice to three times, thus may explain why in some cases we never recover 
from an instance reboot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822133/+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 1832508] Re: linux: 4.18.0-23.24 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1832507 (bionic/linux-hwe)
  derivatives: bug 1832496 (linux-raspi2), bug 1832499 (linux-aws), bug 1832503 
(linux-azure), bug 1832505 (linux-gcp), bug 1832506 (linux-kvm)
  
  -- swm properties --
- phase: Ready for Packaging
- phase-changed: Wednesday, 12. June 2019 11:33 UTC
+ phase: Packaging
+ phase-changed: Wednesday, 12. June 2019 18:00 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded
  variant: debs

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

Title:
  linux: 4.18.0-23.24 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1832507 (bionic/linux-hwe)
  derivatives: bug 1832496 (linux-raspi2), bug 1832499 (linux-aws), bug 1832503 
(linux-azure), bug 1832505 (linux-gcp), bug 1832506 (linux-kvm)

  -- swm properties --
  phase: Packaging
  phase-changed: Wednesday, 12. June 2019 18:00 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832508/+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 1832623] [NEW] [UBUNTU] kernel: Fix gcm-aes-s390 wrong scatter-gather list processing

[bugproxy]

Public bug reported:

Description:   kernel: Fix gcm-aes-s390 wrong scatter-gather list processing
Symptom:   gcm-aes-s390 wrong en/decryption processing
Problem:   The current gcm aes s390 implementation does not process
   scatter-gather input and output lists correct when list
   entries with sizes not multiples of the blocksize of 16
   bytes are used. Result may be wrong calculated encrypted
   or decrypted data.
   This can only happen on z14 (this is the only machine
   which supports aes-gcm in hardware via CPACF). Please note
   that applications using aes-gcm via the AF_ALG interface are
   not affected as this API ensures scatter/gather list entries
   with chunk sizes in multiples of 16 bytes. However, all
   exploiters of aes-gcm within the kernel may be affected.
Solution:  Rework of the scatter/gather walk within the aes_s390 kernel
   module implementation with the goal to support any list
   entry size.
Reproduction:  With kernel 5.1 there has been an improvement on the crypto
   selftests. There are now tests run with fragmented
   scatter/gather lists. So:
   1. You need at least a z14 and kernel >= 5.1.
   2. If disabled, enable the crypto self tests.
   3. Watch for syslog entries during modprobe of the aes_s390
  kernel module. As this module usually gets automatically
  inserted during system startup you may need to unload the
  aes_s390 kernel module before re-inserting it.
   4. Without the fix something like
  "kernel: alg: aead: gcm-aes-s390 encryption test failed
  (wrong result) on test vector 1,..."
  will show up. With the fix, all selftests will pass and
  nothing is reported in syslog.

Component: kernel
Upstream-ID:   bef9f0ba300a55d79a69aa172156072182176515

This request is targeted for 19.10, but should also be applied to 18.04
and 19.04

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-178123 severity-high 
targetmilestone-inin1910

** Tags added: architecture-s39064 bugnameltc-178123 severity-high
targetmilestone-inin1910

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

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

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

Title:
  [UBUNTU] kernel: Fix gcm-aes-s390 wrong scatter-gather list processing

Status in linux package in Ubuntu:
  New

Bug description:
  Description:   kernel: Fix gcm-aes-s390 wrong scatter-gather list processing
  Symptom:   gcm-aes-s390 wrong en/decryption processing
  Problem:   The current gcm aes s390 implementation does not process
 scatter-gather input and output lists correct when list
 entries with sizes not multiples of the blocksize of 16
 bytes are used. Result may be wrong calculated encrypted
 or decrypted data.
 This can only happen on z14 (this is the only machine
 which supports aes-gcm in hardware via CPACF). Please note
 that applications using aes-gcm via the AF_ALG interface are
 not affected as this API ensures scatter/gather list entries
 with chunk sizes in multiples of 16 bytes. However, all
 exploiters of aes-gcm within the kernel may be affected.
  Solution:  Rework of the scatter/gather walk within the aes_s390 kernel
 module implementation with the goal to support any list
 entry size.
  Reproduction:  With kernel 5.1 there has been an improvement on the crypto
 selftests. There are now tests run with fragmented
 scatter/gather lists. So:
 1. You need at least a z14 and kernel >= 5.1.
 2. If disabled, enable the crypto self tests.
 3. Watch for syslog entries during modprobe of the aes_s390
kernel module. As this module usually gets automatically
inserted during system startup you may need to unload the
aes_s390 kernel module before re-inserting it.
 4. Without the fix something like
"kernel: alg: aead: gcm-aes-s390 encryption test failed
(wrong result) on test vector 1,..."
will show up. With the fix, all selftests will pass and
nothing is reported in syslog.

  Component: kernel
  Upstream-ID:   

[Kernel-packages] [Bug 1832624] [NEW] [UBUNTU] kernel: Fix wrong dispatching for control domain CPRBs

[bugproxy]

Public bug reported:

Description:   kernel: Fix wrong dispatching for control domain CPRBs

Symptom:   Unable to maintain control-only crypto domains

Problem:   LPARs may have control-only crypto domains assigned.
   Such a domain can be controlled (for example master keys can
   be set) but can't be used for regualar crypto load (usage).
   A crypto domain may be assigned for control-and-usage to
   only one active LPAR. But the very same domain may be
   assigned for control-only to one or more other LPARs.
   However, trying to communicate in any way with a
   control-only crypto domain did not work. So a simple query
   for the state of the master keys on a control-only domain
   failed and the TKE does not even show this domain. Even
   worse, when the lowest domain (in a numerically sense) is a
   control-only domain, the TKE does not even see the crypto
   cards at all.

Solution:  This fix introduces some code which checks if an CCA CPRB is
   addressing a control-only domain. If that's the case and
   there is a default control-and-usage domain available the
   CPRB is send to this other domain instead. The target domain
   field within the CPRB is untouched and the crypto card
   firmware code detects this working-as-designed mismatch and
   does the right job and addresses the control domain.

Reproduction:  1. Add a control-only domain to the crypto configuration of
  an LPAR and re-activate the LPAR.
   2. Connect the TKE the LPAR and try to visit the master key
  verification patterns of this control-only domain.
   3. Will fail without the fix, will succeed with the fix.

Component: kernel
Upstream-ID:   7379e652797c0b9b5f6caea1576f2dff9ce6a708

This fix is requested for 19.10 but should also be applied to 18.04 and
19.04

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-178125 severity-high 
targetmilestone-inin1910

** Tags added: architecture-s39064 bugnameltc-178125 severity-high
targetmilestone-inin1910

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

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

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

Title:
  [UBUNTU] kernel: Fix wrong dispatching for control domain CPRBs

Status in linux package in Ubuntu:
  New

Bug description:
  Description:   kernel: Fix wrong dispatching for control domain CPRBs

  Symptom:   Unable to maintain control-only crypto domains

  Problem:   LPARs may have control-only crypto domains assigned.
 Such a domain can be controlled (for example master keys can
 be set) but can't be used for regualar crypto load (usage).
 A crypto domain may be assigned for control-and-usage to
 only one active LPAR. But the very same domain may be
 assigned for control-only to one or more other LPARs.
 However, trying to communicate in any way with a
 control-only crypto domain did not work. So a simple query
 for the state of the master keys on a control-only domain
 failed and the TKE does not even show this domain. Even
 worse, when the lowest domain (in a numerically sense) is a
 control-only domain, the TKE does not even see the crypto
 cards at all.

  Solution:  This fix introduces some code which checks if an CCA CPRB is
 addressing a control-only domain. If that's the case and
 there is a default control-and-usage domain available the
 CPRB is send to this other domain instead. The target domain
 field within the CPRB is untouched and the crypto card
 firmware code detects this working-as-designed mismatch and
 does the right job and addresses the control domain.

  Reproduction:  1. Add a control-only domain to the crypto configuration of
an LPAR and re-activate the LPAR.
 2. Connect the TKE the LPAR and try to visit the master key
verification patterns of this control-only domain.
 3. Will fail without the fix, will succeed with the fix.

  Component: kernel
  Upstream-ID:   7379e652797c0b9b5f6caea1576f2dff9ce6a708

  This fix is requested for 19.10 but should also be applied to 18.04
  and 19.04

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1832625] [NEW] [UBUNTU] pkey: Indicate old mkvp only if old and curr. mkvp are different

[bugproxy]

Public bug reported:

Description:   pkey: Indicate old mkvp only if old and curr. mkvp are
different

Symptom:   zkey validate shows wrong information about master key
registers

Problem:   When the CCA master key is set twice with the same master key,
   then the old and the current master key are the same and thus
   the verification patterns are the same, too. The check to report
   if a secure key is currently wrapped by the old master key 
   erroneously reports old mkvp in this case.

Solution:  Fix this by checking current and old mkvp and report OLD only if
   current and old mkvp are different.

Reproduction:  Change the CCA master key but set the exact same master
key that is already used. Then do a 'zkey validate' command on a secure
key

Component: kernel 5.1 rc1
Upstream-ID:   ebb7c695d3bc7a4986b92edc8d9ef43491be183e

This fix will be provided with kernel >=5.1 , will be integrate in 19.10 by 
default.
But should also be applied to 18.04 and 19.04

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-178127 severity-high 
targetmilestone-inin1910

** Tags added: architecture-s39064 bugnameltc-178127 severity-high
targetmilestone-inin1910

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

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

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

Title:
  [UBUNTU] pkey: Indicate old mkvp only if old and curr. mkvp are
  different

Status in linux package in Ubuntu:
  New

Bug description:
  Description:   pkey: Indicate old mkvp only if old and curr. mkvp are
  different

  Symptom:   zkey validate shows wrong information about master key
  registers

  Problem:   When the CCA master key is set twice with the same master key,
 then the old and the current master key are the same and thus
 the verification patterns are the same, too. The check to 
report
 if a secure key is currently wrapped by the old master key 
 erroneously reports old mkvp in this case.

  Solution:  Fix this by checking current and old mkvp and report OLD only 
if
 current and old mkvp are different.

  Reproduction:  Change the CCA master key but set the exact same master
  key that is already used. Then do a 'zkey validate' command on a
  secure key

  Component: kernel 5.1 rc1
  Upstream-ID:   ebb7c695d3bc7a4986b92edc8d9ef43491be183e

  This fix will be provided with kernel >=5.1 , will be integrate in 19.10 by 
default.
  But should also be applied to 18.04 and 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832625/+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 1822133] Re: Azure Instance never recovered during series of instance reboots.

[Sean Feole]

@tom-wilberding  Hey Tom, are you able to capture the console logs of
the instance when this occurs?

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

Title:
  Azure Instance never recovered during series of instance reboots.

Status in linux-azure package in Ubuntu:
  In Progress

Bug description:
  Description: During SRU Testing of various Azure Instances, there will
  be some cases where the instance will not respond following a system
  reboot.  SRU Testing only restarts a giving instance once, after it
  preps all of the necessary files to-be-tested.

  Series: Disco
  Instance Size: Basic_A3
  Region: (Default) US-WEST-2
  Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  I initiated a series of tests which rebooted Azure Cloud instances 50
  times. During the 49th Reboot, an Instance failed to return from a
  reboot.. Upon grabbing the console output the following was seen
  scrolling endlessly. I have seen this failure in cases where the
  instance only restarted a handful of times >5

  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus

  In another test attempt I saw the following failure:

  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes

  
  Both of these failures broke networking, Both of these failures were seen at 
least twice to three times, thus may explain why in some cases we never recover 
from an instance reboot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822133/+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 1832508] Re: linux: 4.18.0-23.24 -proposed tracker

[Stefan Bader]

** Summary changed:

- linux:  -proposed tracker
+ linux: 4.18.0-23.24 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

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

Title:
  linux: 4.18.0-23.24 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1832507 (bionic/linux-hwe)
  derivatives: bug 1832496 (linux-raspi2), bug 1832499 (linux-aws), bug 1832503 
(linux-azure), bug 1832505 (linux-gcp), bug 1832506 (linux-kvm)

  -- swm properties --
  phase: Ready for Packaging
  phase-changed: Wednesday, 12. June 2019 11:33 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832508/+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 1832625] [NEW] [UBUNTU] pkey: Indicate old mkvp only if old and curr. mkvp are different

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Description:   pkey: Indicate old mkvp only if old and curr. mkvp are
different

Symptom:   zkey validate shows wrong information about master key
registers

Problem:   When the CCA master key is set twice with the same master key,
   then the old and the current master key are the same and thus
   the verification patterns are the same, too. The check to report
   if a secure key is currently wrapped by the old master key 
   erroneously reports old mkvp in this case.

Solution:  Fix this by checking current and old mkvp and report OLD only if
   current and old mkvp are different.

Reproduction:  Change the CCA master key but set the exact same master
key that is already used. Then do a 'zkey validate' command on a secure
key

Component: kernel 5.1 rc1
Upstream-ID:   ebb7c695d3bc7a4986b92edc8d9ef43491be183e

This fix will be provided with kernel >=5.1 , will be integrate in 19.10 by 
default.
But should also be applied to 18.04 and 19.04

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-178127 severity-high 
targetmilestone-inin1910
-- 
[UBUNTU] pkey: Indicate old mkvp only if old and curr. mkvp are different
https://bugs.launchpad.net/bugs/1832625
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1832624] [NEW] [UBUNTU] kernel: Fix wrong dispatching for control domain CPRBs

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Description:   kernel: Fix wrong dispatching for control domain CPRBs

Symptom:   Unable to maintain control-only crypto domains

Problem:   LPARs may have control-only crypto domains assigned.
   Such a domain can be controlled (for example master keys can
   be set) but can't be used for regualar crypto load (usage).
   A crypto domain may be assigned for control-and-usage to
   only one active LPAR. But the very same domain may be
   assigned for control-only to one or more other LPARs.
   However, trying to communicate in any way with a
   control-only crypto domain did not work. So a simple query
   for the state of the master keys on a control-only domain
   failed and the TKE does not even show this domain. Even
   worse, when the lowest domain (in a numerically sense) is a
   control-only domain, the TKE does not even see the crypto
   cards at all.

Solution:  This fix introduces some code which checks if an CCA CPRB is
   addressing a control-only domain. If that's the case and
   there is a default control-and-usage domain available the
   CPRB is send to this other domain instead. The target domain
   field within the CPRB is untouched and the crypto card
   firmware code detects this working-as-designed mismatch and
   does the right job and addresses the control domain.

Reproduction:  1. Add a control-only domain to the crypto configuration of
  an LPAR and re-activate the LPAR.
   2. Connect the TKE the LPAR and try to visit the master key
  verification patterns of this control-only domain.
   3. Will fail without the fix, will succeed with the fix.

Component: kernel
Upstream-ID:   7379e652797c0b9b5f6caea1576f2dff9ce6a708

This fix is requested for 19.10 but should also be applied to 18.04 and
19.04

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-178125 severity-high 
targetmilestone-inin1910
-- 
[UBUNTU] kernel: Fix wrong dispatching for control domain CPRBs
https://bugs.launchpad.net/bugs/1832624
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1832623] [NEW] [UBUNTU] kernel: Fix gcm-aes-s390 wrong scatter-gather list processing

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Description:   kernel: Fix gcm-aes-s390 wrong scatter-gather list processing
Symptom:   gcm-aes-s390 wrong en/decryption processing
Problem:   The current gcm aes s390 implementation does not process
   scatter-gather input and output lists correct when list
   entries with sizes not multiples of the blocksize of 16
   bytes are used. Result may be wrong calculated encrypted
   or decrypted data.
   This can only happen on z14 (this is the only machine
   which supports aes-gcm in hardware via CPACF). Please note
   that applications using aes-gcm via the AF_ALG interface are
   not affected as this API ensures scatter/gather list entries
   with chunk sizes in multiples of 16 bytes. However, all
   exploiters of aes-gcm within the kernel may be affected.
Solution:  Rework of the scatter/gather walk within the aes_s390 kernel
   module implementation with the goal to support any list
   entry size.
Reproduction:  With kernel 5.1 there has been an improvement on the crypto
   selftests. There are now tests run with fragmented
   scatter/gather lists. So:
   1. You need at least a z14 and kernel >= 5.1.
   2. If disabled, enable the crypto self tests.
   3. Watch for syslog entries during modprobe of the aes_s390
  kernel module. As this module usually gets automatically
  inserted during system startup you may need to unload the
  aes_s390 kernel module before re-inserting it.
   4. Without the fix something like
  "kernel: alg: aead: gcm-aes-s390 encryption test failed
  (wrong result) on test vector 1,..."
  will show up. With the fix, all selftests will pass and
  nothing is reported in syslog.

Component: kernel
Upstream-ID:   bef9f0ba300a55d79a69aa172156072182176515

This request is targeted for 19.10, but should also be applied to 18.04
and 19.04

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-178123 severity-high 
targetmilestone-inin1910
-- 
[UBUNTU] kernel: Fix gcm-aes-s390 wrong scatter-gather list processing
https://bugs.launchpad.net/bugs/1832623
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1757422] Re: Fix Runtime PM for r8169

[Kai-Heng Feng]

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

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

Title:
  Fix Runtime PM for r8169

Status in HWE Next:
  New
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  Triaged
Status in linux-oem source package in Bionic:
  New

Bug description:
  ===SRU Justification===
  [Impact]
  r8169 stays in D0 even when no ethernet cable is plugged in. This drains
  lots of power (~3W). The tested laptop uses 5.5W when r8169 is in D0,
  1.8W when r8169 is in D3. The power saved is substantial.

  [Fix]
  Improved rumtime PM logic to let the device gets suspended (D3) when the
  port is not in used and the link is down.

  [Test Case]
  The chip version is 8168h/8111h.
  Test when no ethernet gets plugged.

  Powertop shows power consumption is roughly 5.5W.
  lspci shows the device is in D0.

  With the patch,
  The power consumption is reduced to 1.8W.
  lspci shows the device is in D3, PME# is correctly enabled.
  Plug ethernet cable can corretly wake up the device.
  Unplug the cable, the device gets suspended to D3 correctly.

  [Regression Potential]
  Medium.
  - r8169 is so ubiquitous, with lots of different chip versions. It's
hard to test all of them.
  - PCI D3 needs system firmware (ACPI) support, this might hit some
plaform bugs.
  - the code is still in v4.16-rc*, so it's not well tested by end users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1757422/+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 1822133] Re: Azure Instance never recovered during series of instance reboots.

[Tom Wilberding]

It looks like people are resolving this by upgrading to latest Disco
with 5.0.0-1007.7 kernel?

We are on 18.04.1 LTS and having similar symptoms. Is there a fix in the
works for 18.04.1?

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

Title:
  Azure Instance never recovered during series of instance reboots.

Status in linux-azure package in Ubuntu:
  In Progress

Bug description:
  Description: During SRU Testing of various Azure Instances, there will
  be some cases where the instance will not respond following a system
  reboot.  SRU Testing only restarts a giving instance once, after it
  preps all of the necessary files to-be-tested.

  Series: Disco
  Instance Size: Basic_A3
  Region: (Default) US-WEST-2
  Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  I initiated a series of tests which rebooted Azure Cloud instances 50
  times. During the 49th Reboot, an Instance failed to return from a
  reboot.. Upon grabbing the console output the following was seen
  scrolling endlessly. I have seen this failure in cases where the
  instance only restarted a handful of times >5

  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus

  In another test attempt I saw the following failure:

  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes

  
  Both of these failures broke networking, Both of these failures were seen at 
least twice to three times, thus may explain why in some cases we never recover 
from an instance reboot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822133/+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 1832492] Re: linux: 5.0.0-18.19 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1832489 (bionic/linux-hwe-edge), bug 1832491 
(bionic/linux-oem-osp1)
  derivatives: bug 1832483 (linux-raspi2), bug 1832484 (linux-aws), bug 1832485 
(linux-azure), bug 1832486 (linux-gcp), bug 1832487 (linux-kvm), bug 1832488 
(linux-snapdragon)
  
  -- swm properties --
- phase: Ready for Packaging
- phase-changed: Wednesday, 12. June 2019 10:32 UTC
+ phase: Packaging
+ phase-changed: Wednesday, 12. June 2019 17:30 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-lrm: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded
  variant: debs

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

Title:
  linux: 5.0.0-18.19 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-lrm series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1832489 (bionic/linux-hwe-edge), bug 1832491 
(bionic/linux-oem-osp1)
  derivatives: bug 1832483 (linux-raspi2), bug 1832484 (linux-aws), bug 1832485 
(linux-azure), bug 1832486 (linux-gcp), bug 1832487 (linux-kvm), bug 1832488 
(linux-snapdragon)

  -- swm properties --
  phase: Packaging
  phase-changed: Wednesday, 12. June 2019 17:30 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-lrm: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  variant: debs

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

[Stefan Bader]

** Summary changed:

- linux:  -proposed tracker
+ linux: 5.0.0-18.19 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

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

** Changed in: kernel-sru-workflow/prepare-package-lrm
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

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

Title:
  linux: 5.0.0-18.19 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-lrm series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1832489 (bionic/linux-hwe-edge), bug 1832491 
(bionic/linux-oem-osp1)
  derivatives: bug 1832483 (linux-raspi2), bug 1832484 (linux-aws), bug 1832485 
(linux-azure), bug 1832486 (linux-gcp), bug 1832487 (linux-kvm), bug 1832488 
(linux-snapdragon)

  -- swm properties --
  phase: Packaging
  phase-changed: Wednesday, 12. June 2019 17:30 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-lrm: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832492/+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 1443924]

[tayyebaziz078]

Clip Studio Paint 1.9.0 License Key {New Update}
Clip Studio Paint Crack is an efficient and versatile program for creating 
different types of digital art. It is a great successor to comic or Manga 
studio. And is a very essential tool for creating various types of manga, comic 
as well as cartoons. It has specialized features for adding amazing details and 
colors to your work.

It has the ability to add new tools such as pens, brushes, color tones,
styles, 3D models and many more. Many new tools and features are
released from manufactures for advanced functionality. allows users to
share different artwork with your social circle as well as the whole
world. It offers perfect functions for creating amazing cartoons,
animations, clip art, illustration and much more with complete ease.

Clip Studio Paint Serial Number is a comprehensive program for creating
different digital art project from start to end phase. It offers a
complete art studio in digital device for any artist. The user can use
it express their creativity in any way they want without any limitation.
The user can easily zoom in and out for adding a different level of
detail to the painting. It has all the required tools for creating
different types of comic strips and manga novels.

With this software, the user can add a different dimension to their
artwork. Clip Studio Paint Crack has features for adding unique
textures, shadows, lights and many other effects to your artwork as
well. It has a large collection of art, clips, animation, and many other
objects. Which you can just add by drag and drop to your drawings.https://windowactivator.org/;>Window Activator Such as user
can add different styles of dialogue balloons for adding conservations
to comic books.

Clip Studio Paint Full Torrent [Mac+Windows]2019

Clip Studio Paint Key Feature:
The pen will be searched for pen color procession strips.
It seems like a real pen.
A large number of drawing tools Markers, brushes, and similar equivalents
Jewelry devices can make a posh sample with a single stroke.
Make samples reminiscent of plants, grasses, chains, and many different things.
Create vector layers and trace them and draw different items.
Clip Studio Paint 1.8.5 Crack, Change the objects on vector layers. Equal to 
increase, scale, and scale
of scales width
Get supplies and different things to look great on your artwork.
There are plenty of ruler varieties. To draw the right picture
The symmetrical ruler allows you to create a symmetrical shape in the artwork.
With perspective rulers, you will be able to add an approach to your artwork.
Clip Studio Paint Torrent, Determine and create 3D in your drawing.
Transfer any part of the 3D motion set by the mouse.
Make a great amount of color in your lines.
With auto-action, you will be able to perform many duties without delay.
What’s new in Clip Studio Paint Crack?
Export and import your drawings in Photoshop.
Clip Studio Paint 1.8.5 Crack
Now you can import and export in CMYK color.
You may change the interface and customize the format.
Now export your artwork in PDF format.
System Requirements:
Home windows 7 | 8 \ 8.1 / Mac OS X 10.9 | 10.10 | 10.11 or newer.
2 GHz CPU.
512 MB Graphics.
2 GB RAM

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

Title:
  1814:0201 ieee80211 phy0: rt2x00queue_flush_queue:Warning - Queue 0
  failed to flush

Status in Linux:
  Won't Fix
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Philips i386 PC with rt2x00 pci is suffering loss of WiFi connectivity
  after installing 15.04 Beta.

  The system did work correctly with older Ubuntu versions (like 12.04)
  and had this problem show up after upgrading to Trusty (as I already
  reported in bug #1318837). Using Trusty the problem went away when
  switching from the stock 3.13.0-XX-generic kernel to builds of newer
  kernels (like 3.14.1-031401).

  Now the same problem shows up again after installing Vivid Beta. It seems to 
be the same problem reported for other Ubuntu releases (see bugs #1318837 and 
#1383555) and also the same problem of this upstream kernel bug:
  https://bugzilla.kernel.org/show_bug.cgi?id=61621

  Someone on kernel's bug mentions turning off MSI interrupts and I can confirm 
it did change the situation:
  - normally the system looses WiFi connectivity mere seconds after boot (eg. 
can't ping anything after boot)
  - if I boot with "pci=nomsi" the system will remain connected to the WiFi for 
a much longer period (eg. I am able to apt-get install something after boot)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-extra-3.19.0-13-generic 3.19.0-13.13
  ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3
  Uname: Linux 3.19.0-13-generic i686
  ApportVersion: 2.17-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luca

[Kernel-packages] [Bug 1443924]

[alvinakaith]

ReSharper 2019.1 [Crack Incl License Key]!
Resharper Keygen

ReSharper 2019.1 Crack– This is the smart tool that works inside the
visual studio. It is a productivity extension in the visual studio for
detecting errors. In addition, it will work for code correction,
redundancies problems, syntax issues, and many more. In addition, You
can make your code simple and easy. This will help the user to write the
bast codes. Furthermore, it works as an intelligent code correction.
Therefore, You can also explore the code using code structure, styles,
types, and value chain. This extension will lead you to find problems,
particular code, errors, bugs, and more. It has 2000 on the fly code
inspection for JAVA, VB, C++ etc. Finally, install and indent your code
in a better way.https://crackscoop.com/;>crack scoop
Finally, Resharper with License key is now activated.

Resharper 2019.1 Keygen With Activation key
Resharper 2019.1 Keygen is available for full software. You will get all 
features after registration. In addition,  You can manage C#, XAML, VB>NET, 
Type Scripts, Java Scripts, HTML, XML, CSS, and ASP. This keygen setup gives 
robust of the features. Its new features checks code automatically and suggest 
the best solution. This version provides the best programming solution. In 
addition, we have fixed the bugs with crack. Get it and make well indent your 
code for better efficiency. The main feature is the language 
cross-functionality. You can write any script in IDE. it will work for all 
languages. Finally, Use the torrent file and download the full version 
including all new features.

Resharper Keygen

Key Features

Easy to download and install.
Ease your code correction.
Works for many programming languages.
Best programming way.
It supports for visual studio 2017 RTM.
Easy code testing.
Supports for C#
Unit testing feature.
Easy editor configuration.
Code cleaning, code styles, and easy formatting options.
It supports for Type Scripts and java scripts.
easy command line profiler.
What’s New

Eliminate errors and indent the code.
Provides instantly traversing.
Here is code quality analysis.
best code editors.
How to Crack?

Download and run the setup.
Extract files into a folder.
Run the setup and install it.
Configure the setting.
Turn off the internet.
Run Crack and install it.
Thank you.

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

Title:
  1814:0201 ieee80211 phy0: rt2x00queue_flush_queue:Warning - Queue 0
  failed to flush

Status in Linux:
  Won't Fix
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Philips i386 PC with rt2x00 pci is suffering loss of WiFi connectivity
  after installing 15.04 Beta.

  The system did work correctly with older Ubuntu versions (like 12.04)
  and had this problem show up after upgrading to Trusty (as I already
  reported in bug #1318837). Using Trusty the problem went away when
  switching from the stock 3.13.0-XX-generic kernel to builds of newer
  kernels (like 3.14.1-031401).

  Now the same problem shows up again after installing Vivid Beta. It seems to 
be the same problem reported for other Ubuntu releases (see bugs #1318837 and 
#1383555) and also the same problem of this upstream kernel bug:
  https://bugzilla.kernel.org/show_bug.cgi?id=61621

  Someone on kernel's bug mentions turning off MSI interrupts and I can confirm 
it did change the situation:
  - normally the system looses WiFi connectivity mere seconds after boot (eg. 
can't ping anything after boot)
  - if I boot with "pci=nomsi" the system will remain connected to the WiFi for 
a much longer period (eg. I am able to apt-get install something after boot)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-extra-3.19.0-13-generic 3.19.0-13.13
  ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3
  Uname: Linux 3.19.0-13-generic i686
  ApportVersion: 2.17-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luca   1997 F pulseaudio
  CurrentDesktop: LXDE
  Date: Tue Apr 14 14:19:19 2015
  HibernationDevice: RESUME=UUID=cbd1e136-ffc4-48b9-b2aa-c15264b9b132
  MachineType: Freeline Freeline Series
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-13-generic 
root=UUID=6110f881-b32b-426d-910a-c63b355c179c ro quiet splash vt.handoff=7 
pci=nomsi
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-13-generic N/A
   linux-backports-modules-3.19.0-13-generic  N/A
   linux-firmware 1.143
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log 

[Kernel-packages] [Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600

[Paul Dufresne]

The patch is included in:
Linux 4.14.125
Linux 4.19.50
Linux 5.1.9
I don't have access to the laptop on which I investigated this problem anymore.

But it could be tested from the built kernel packages at:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14.125/
https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.50/
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1.9/
Install linux-headers then linux-modules then linux-image (I think)

In fact, testing on other ATI hardware too see not bad results happen
would be... reassuring.

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

Title:
  ubuntu 18.04 flickering screen with Radeon X1600

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

Bug description:
  my laptop: HP Compaq nx9420
  my grafic card: 
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller])

  attachment:
  the bug-apport-file

  Description:
  I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode;
  -> as soon as the kernel-module radeon.ko is loaded the screen starts 
flickering
  when starting the grafic-mode the flickering continues; so the screen is 
unusable.

  when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the 
screen does not flicker
  but the resolution is limited to 1400x1050 (instead of natural 1680x1050)
  so I can not use this as work-around

  when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157)
  the screen is o.k. NO flickering in textmode, nice grafic, NO flickering 
  xrandr tells: 1680x1050 60.1

  so I must stay on old ubuntu 14.04.05 ???

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1791312/+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 1731699] Re: Unable to transfer files via bluetooth to paired android phone

[Lukas Bradley]

Also affects Ubuntu 19.04 using Google Pixel 2 XL on Android 9 Build
Number PQ3A.190605.003.

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

Title:
  Unable to transfer files via bluetooth to paired android phone

Status in bluez package in Ubuntu:
  Expired

Bug description:
  I'm trying to transfer files to my phone (Nexus 6P - Android 8.0) from
  Ubuntu 17.10, but when I pair the laptop and phone, I don't think it's
  pairing in a way which permits file transfers. When I pair, my phone
  gives me a checkbox "Allow xx to access your contacts and call
  history", but there is no option to allow file transfers.

  Then, when I attempt to transfer a file via Bluetooth from Ubuntu the
  transfer fails and I get the message "There was an error". My phone
  doesn't seem to recognise there's been any attempt to send a file.

  Discussed at https://ubuntuforums.org/showthread.php?t=2377286

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731699/+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 1804183] Re: netronome firmware symlinks are overwritten by package upgrade

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

Title:
  netronome firmware symlinks are overwritten by package upgrade

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  The linux-firmware package includes symlinks to installed Netronome
  firmware files. These links may be updated by a user but are
  overwritten when the linux-firmware package is upgraded whereas the
  desired behaviour is to leave existing symlinks unmodified.

  # apt install linux-firmware 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following package was automatically installed and is no longer required:
grub-pc-bin
  Use 'apt autoremove' to remove it.
  The following NEW packages will be installed:
linux-firmware
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 64.6 MB of archives.
  After this operation, 278 MB of additional disk space will be used.
  Get:1 http://lon1.mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 
linux-firmware all 1.173.1 [64.6 MB]
  Fetched 64.6 MB in 1s (43.8 MB/s) 
  Selecting previously unselected package linux-firmware.
  (Reading database ... 59988 files and directories currently installed.)
  Preparing to unpack .../linux-firmware_1.173.1_all.deb ...
  Unpacking linux-firmware (1.173.1) ...
  Setting up linux-firmware (1.173.1) ...
  update-initramfs: Generating /boot/initrd.img-4.15.0-38-generic
  # cd /lib/firmware/netronome/
  # ls -l
  total 8
  drwxr-xr-x 2 root root 4096 Nov 20 09:07 flower
  drwxr-xr-x 2 root root 4096 Nov 20 09:07 nic
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0081-0001_1x40.nffw -> 
nic/nic_AMDA0081-0001_1x40.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0081-0001_4x10.nffw -> 
nic/nic_AMDA0081-0001_4x10.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0096-0001_2x10.nffw -> 
nic/nic_AMDA0096-0001_2x10.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0097-0001_2x40.nffw -> 
nic/nic_AMDA0097-0001_2x40.nffw
  lrwxrwxrwx 1 root root   36 May 18  2018 nic_AMDA0097-0001_4x10_1x40.nffw -> 
nic/nic_AMDA0097-0001_4x10_1x40.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0097-0001_8x10.nffw -> 
nic/nic_AMDA0097-0001_8x10.nffw
  lrwxrwxrwx 1 root root   36 May 18  2018 nic_AMDA0099-0001_1x10_1x25.nffw -> 
nic/nic_AMDA0099-0001_1x10_1x25.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0099-0001_2x10.nffw -> 
nic/nic_AMDA0099-0001_2x10.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0099-0001_2x25.nffw -> 
nic/nic_AMDA0099-0001_2x25.nffw
  # for i in $(find flower/ -type l); do ln -sf $i $(basename $i); done
  # ls -l
  total 8
  drwxr-xr-x 2 root root 4096 Nov 20 09:07 flower
  drwxr-xr-x 2 root root 4096 Nov 20 09:07 nic
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0081-0001_1x40.nffw -> 
flower/nic_AMDA0081-0001_1x40.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0081-0001_4x10.nffw -> 
flower/nic_AMDA0081-0001_4x10.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0096-0001_2x10.nffw -> 
flower/nic_AMDA0096-0001_2x10.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0097-0001_2x40.nffw -> 
flower/nic_AMDA0097-0001_2x40.nffw
  lrwxrwxrwx 1 root root   39 Nov 20 09:09 nic_AMDA0097-0001_4x10_1x40.nffw -> 
flower/nic_AMDA0097-0001_4x10_1x40.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0097-0001_8x10.nffw -> 
flower/nic_AMDA0097-0001_8x10.nffw
  lrwxrwxrwx 1 root root   36 May 18  2018 nic_AMDA0099-0001_1x10_1x25.nffw -> 
nic/nic_AMDA0099-0001_1x10_1x25.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0099-0001_2x10.nffw -> 
flower/nic_AMDA0099-0001_2x10.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0099-0001_2x25.nffw -> 
flower/nic_AMDA0099-0001_2x25.nffw
  # apt update
  ...
  # apt install linux-firmware
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following package was automatically installed and is no longer required:
grub-pc-bin
  Use 'apt autoremove' to remove it.
  The following packages will be upgraded:
linux-firmware
  1 upgraded, 0 newly installed, 0 to remove and 49 not upgraded.
  Need to get 64.6 MB of archives.
  After this operation, 30.7 kB of additional disk space will be used.
  Get:1 http://lon1.mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 
linux-firmware all 1.173.2 [64.6 MB]
  Fetched 64.6 MB in 1s (55.1 MB/s) 
  (Reading database ... 61821 files and directories currently installed.)
  Preparing to unpack .../linux-firmware_1.173.2_all.deb ...
  Unpacking linux-firmware (1.173.2) over (1.173.1) ...
  Setting up linux-firmware (1.173.2) ...
  update-initramfs: Generating /boot/initrd.img-4.15.0-38-generic
  root@ubuntu-s-1vcpu-1gb-ams3-01:/lib/firmware/netronome# ls -l
  total 8

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

[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 1832613

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

Title:
  Settings are simply broken  >:]

Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Fedora:
  Unknown

Bug description:
  
  Anything that's allowed to set lowest to highest setting
  seems simply broken for some reason.

  
  e.g. volume, brightness settings are broken,
  as is scroll (web browser for example).

  More interesting example would be relocating
  focused tab to first position before closing
  it, for example in Chromium browser.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832613/+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 1832613] [NEW] Settings are simply broken >:]

[klfyt]

Public bug reported:


Anything that's allowed to set lowest to highest setting
seems simply broken for some reason.


e.g. volume, brightness settings are broken,
as is scroll (web browser for example).

More interesting example would be relocating
focused tab to first position before closing
it, for example in Chromium browser.

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

** Affects: linux (Fedora)
 Importance: Unknown
 Status: Unknown

** Attachment added: "settings hack  >:]"
   
https://bugs.launchpad.net/bugs/1832613/+attachment/5270394/+files/settings%20bug%20hack.png

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

** Also affects: linux (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1693960
   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/1832613

Title:
  Settings are simply broken  >:]

Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Fedora:
  Unknown

Bug description:
  
  Anything that's allowed to set lowest to highest setting
  seems simply broken for some reason.

  
  e.g. volume, brightness settings are broken,
  as is scroll (web browser for example).

  More interesting example would be relocating
  focused tab to first position before closing
  it, for example in Chromium browser.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832613/+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 1818134] Re: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic

[vandebo]

I've confirmed that the problem went away by upgrading to the xenial
kernel -- I reinstall shim-signed, rebooted to the new kernel and it
worked. I also reinstalled the nvidia package after rebooting and it
still worked.

Should the shim-signed package have a dependency on a kernel that is new
enough?

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1818134/+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 1832101] Re: systemd-networkd: Lost carrier e1000

[Kai-Heng Feng]

Does disabling TSO 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/1832101

Title:
  systemd-networkd:   Lost carrier e1000

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Just installed a fresh installation of ubuntu 19 on our server and
  we're having a lot of carrier-lost erros.

  There is no really good indicaton why this is hapening.

  Tried the following : disabled ipv6 (just to be sure), on nic set GSO,GRO,TSO 
to off.
  removed netplan, switched to systemd-networkd and added 
configurewithoutcarrier to true, the option ignorecarrierlost is not accepted 
by systemd.

  Description:Ubuntu 19.04
  Release:19.04

  
  Kernel Log

  Jun  8 12:11:17 mc2 kernel: [30304.199050] [ cut here 
]
  Jun  8 12:11:17 mc2 kernel: [30304.199052] NETDEV WATCHDOG: eno1 (e1000e): 
transmit queue 0 timed out
  Jun  8 12:11:17 mc2 kernel: [30304.199062] WARNING: CPU: 8 PID: 0 at 
net/sched/sch_generic.c:461 dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199062] Modules linked in: intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
crct10dif_pclmul 
  crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd 
glue_helper intel_cstate intel_rapl_perf intel_wmi_thunderbolt wmi_bmof 
intel_pch_thermal mac_hid acpi_pad ip6t_REJE
  CT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 
nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype 
sch_fq_codel xt_conntrack ip6
  table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
iptable_filter bpfilter ip_
  tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath 
linear raid1 e1000e
   nvme ahci i2c_i801 libahci nvme_core wmi video pinctrl_cannonlake 
pinctrl_intel
  Jun  8 12:11:17 mc2 kernel: [30304.199080] CPU: 8 PID: 0 Comm: swapper/8 Not 
tainted 5.0.0-16-generic #17-Ubuntu
  Jun  8 12:11:17 mc2 kernel: [30304.199081] Hardware name: Gigabyte Technology 
Co., Ltd. B360 HD3P-LM/B360HD3PLM-CF, BIOS F4 HZ 04/30/2019
  Jun  8 12:11:17 mc2 kernel: [30304.199082] RIP: 0010:dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199083] Code: 00 49 63 4e e0 eb 92 4c 89 
ef c6 05 9a 92 f0 00 01 e8 13 38 fc ff 89 d9 4c 89 ee 48 c7 c7 68 5e da 95 48 
89 c2 e8 71 f1 79 ff
   <0f> 0b eb c0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48
  Jun  8 12:11:17 mc2 kernel: [30304.199083] RSP: 0018:93adff203e68 EFLAGS: 
00010286
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RAX:  RBX: 
 RCX: 0006
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RDX: 0007 RSI: 
0096 RDI: 93adff216440
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RBP: 93adff203e98 R08: 
0001 R09: 0c61
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R10: 0004 R11: 
 R12: 0001
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R13: 93adec48 R14: 
93adec4804c0 R15: 93adeca74080
  Jun  8 12:11:17 mc2 kernel: [30304.199086] FS:  () 
GS:93adff20() knlGS:
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CS:  0010 DS:  ES:  CR0: 
80050033
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CR2: 7f7783ea4300 CR3: 
00043920e003 CR4: 003606e0
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR0:  DR1: 
 DR2: 
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Jun  8 12:11:17 mc2 kernel: [30304.199087] Call Trace:
  Jun  8 12:11:17 mc2 kernel: [30304.199088]  
  Jun  8 12:11:17 mc2 kernel: [30304.199090]  ? pfifo_fast_enqueue+0x120/0x120
  Jun  8 12:11:17 mc2 kernel: [30304.199091]  call_timer_fn+0x30/0x130
  Jun  8 12:11:17 mc2 kernel: [30304.199092]  run_timer_softirq+0x3e4/0x420
  Jun  8 12:11:17 mc2 kernel: [30304.199093]  ? ktime_get+0x3c/0xa0
  Jun  8 12:11:17 mc2 kernel: [30304.199095]  ? lapic_next_deadline+0x26/0x30
  Jun  8 12:11:17 mc2 kernel: [30304.199096]  ? 
clockevents_program_event+0x93/0xf0
  Jun  8 12:11:17 mc2 kernel: [30304.199097]  __do_softirq+0xdc/0x2f3
  Jun  8 12:11:17 mc2 kernel: [30304.199099]  irq_exit+0xc0/0xd0
  Jun  8 12:11:17 mc2 kernel: [30304.199099]  
smp_apic_timer_interrupt+0x79/0x140
  Jun  8 12:11:17 mc2 kernel: [30304.199100]  apic_timer_interrupt+0xf/0x20
  Jun  8 12:11:17 mc2 kernel: [30304.199101]  
  Jun  8 12:11:17 mc2 kernel: [30304.199102] RIP: 
0010:cpuidle_enter_state+0xbd/0x450
  Jun  8 12:11:17 mc2 kernel: [30304.199103] Code: ff e8 87 36 87 ff 80 7d c7 
00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 

[Kernel-packages] [Bug 1778087] Re: ELAN1200 touchpad jumps around and disconnects

[gianfilippo]

Hello,
same issue here on 
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: UX331UN

with kernel: 
Linux shadow 5.0.0-16-generic #17~18.04.1-Ubuntu SMP Mon May 20 14:00:27 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

Occasionally, the touchpad freezes. Following message is printed in dmesg:
Jun 12 17:35:32 shadow kernel: [  522.384692] i2c_hid i2c-ELAN1200:00: 
i2c_hid_get_input: IRQ triggered but there's no data

The touchpad then needs to be disabled/reenabled using feature key on
keyboard.

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

Title:
  ELAN1200 touchpad jumps around and disconnects

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is on an ASUS GL503VD laptop and would probably affect other ASUS
  laptops equipped with the ELAN1200 touchpad.

  I am on Kernel 4.17.2 because older kernels did not enable the
  touchpad at all(It was just unrecognized or i2c-hid stopped the
  computer from booting)

  The touchpad works but it has erratic behaviour and disconnects
  randomly. After it disconnects the only way to bring it back is to
  `modprobe -r hid-multitouch && modprobe hid-multitouch`

  Libinput and synaptics can handle the touchpad though I found
  synaptics to be more stable.

  dmesg gets spammed with this whenever I move the touchpad:
  [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report 
(16/65535)

  I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad
  Because from what I understand the "jumpy/disconnect" problem is associated 
to the incomplete reports and Mishurov managed to mitigate those. Unfortunately 
some symbols were deprecated in kernel 4.17.2 and it did not compile for my 
system.

  While I can use my touchpad as is right now, and "restart" it with
  modprobe when needed, it would be nice to have it function bug-free.
  (Right after I typed this my touchpad disconnected and I needed to
  modprobe again, I am considering making a cronjob for that)

  Let me know if anything else is needed. Will wait for an apport collection to 
add log files.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-10 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 4.17.2 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778087/+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 1804183] Re: netronome firmware symlinks are overwritten by package upgrade

[Seth Forshee]

This seems like a bit of an abuse of conffiles, as those files aren't
really intended for user modification. It seems like this is a pretty
niche use case that doesn't apply to the vast majority of users.

Have you looked at dpkg-divert? This can be used to force packages to
install specific files to a diverted location. For example, 'dpkg-divert
--add --rename --divert /lib/firmware/nic_AMDA0058-0011_2x40.nffw.foo
/lib/firmware/nic_AMDA0058-0011_2x40.nffw' should cause the
nic_AMDA0058-0011_2x40.nffw file from linux-firmware updates to be
written to nic_AMDA0058-0011_2x40.nffw.foo.

https://debian-administration.org/article/118
/Replacing_binaries_with_dpkg-divert

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

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

Title:
  netronome firmware symlinks are overwritten by package upgrade

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  The linux-firmware package includes symlinks to installed Netronome
  firmware files. These links may be updated by a user but are
  overwritten when the linux-firmware package is upgraded whereas the
  desired behaviour is to leave existing symlinks unmodified.

  # apt install linux-firmware 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following package was automatically installed and is no longer required:
grub-pc-bin
  Use 'apt autoremove' to remove it.
  The following NEW packages will be installed:
linux-firmware
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 64.6 MB of archives.
  After this operation, 278 MB of additional disk space will be used.
  Get:1 http://lon1.mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 
linux-firmware all 1.173.1 [64.6 MB]
  Fetched 64.6 MB in 1s (43.8 MB/s) 
  Selecting previously unselected package linux-firmware.
  (Reading database ... 59988 files and directories currently installed.)
  Preparing to unpack .../linux-firmware_1.173.1_all.deb ...
  Unpacking linux-firmware (1.173.1) ...
  Setting up linux-firmware (1.173.1) ...
  update-initramfs: Generating /boot/initrd.img-4.15.0-38-generic
  # cd /lib/firmware/netronome/
  # ls -l
  total 8
  drwxr-xr-x 2 root root 4096 Nov 20 09:07 flower
  drwxr-xr-x 2 root root 4096 Nov 20 09:07 nic
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0081-0001_1x40.nffw -> 
nic/nic_AMDA0081-0001_1x40.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0081-0001_4x10.nffw -> 
nic/nic_AMDA0081-0001_4x10.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0096-0001_2x10.nffw -> 
nic/nic_AMDA0096-0001_2x10.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0097-0001_2x40.nffw -> 
nic/nic_AMDA0097-0001_2x40.nffw
  lrwxrwxrwx 1 root root   36 May 18  2018 nic_AMDA0097-0001_4x10_1x40.nffw -> 
nic/nic_AMDA0097-0001_4x10_1x40.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0097-0001_8x10.nffw -> 
nic/nic_AMDA0097-0001_8x10.nffw
  lrwxrwxrwx 1 root root   36 May 18  2018 nic_AMDA0099-0001_1x10_1x25.nffw -> 
nic/nic_AMDA0099-0001_1x10_1x25.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0099-0001_2x10.nffw -> 
nic/nic_AMDA0099-0001_2x10.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0099-0001_2x25.nffw -> 
nic/nic_AMDA0099-0001_2x25.nffw
  # for i in $(find flower/ -type l); do ln -sf $i $(basename $i); done
  # ls -l
  total 8
  drwxr-xr-x 2 root root 4096 Nov 20 09:07 flower
  drwxr-xr-x 2 root root 4096 Nov 20 09:07 nic
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0081-0001_1x40.nffw -> 
flower/nic_AMDA0081-0001_1x40.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0081-0001_4x10.nffw -> 
flower/nic_AMDA0081-0001_4x10.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0096-0001_2x10.nffw -> 
flower/nic_AMDA0096-0001_2x10.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0097-0001_2x40.nffw -> 
flower/nic_AMDA0097-0001_2x40.nffw
  lrwxrwxrwx 1 root root   39 Nov 20 09:09 nic_AMDA0097-0001_4x10_1x40.nffw -> 
flower/nic_AMDA0097-0001_4x10_1x40.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0097-0001_8x10.nffw -> 
flower/nic_AMDA0097-0001_8x10.nffw
  lrwxrwxrwx 1 root root   36 May 18  2018 nic_AMDA0099-0001_1x10_1x25.nffw -> 
nic/nic_AMDA0099-0001_1x10_1x25.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0099-0001_2x10.nffw -> 
flower/nic_AMDA0099-0001_2x10.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0099-0001_2x25.nffw -> 
flower/nic_AMDA0099-0001_2x25.nffw
  # apt update
  ...
  # apt install linux-firmware
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following package was automatically installed and is no longer required:
grub-pc-bin
  Use 'apt autoremove' to remove it.
  The following packages will be upgraded:

[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security

[Tom Reynolds]

Eric: This issue should only affect Ubuntu running bare metal on Intel
systems, so not Ubuntu running in a VM. Put differently: if you do not
run Ubuntu as the primary operating system on this MacBook Pro then
please file a separate bug report, or (ideally beforehand) see if you
can get this sorted with commercial (https://ubuntu.com/support) or
community / volunteer (https://ubuntu.com/support/community-support)
support. Thanks.

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

Title:
  intel-microcode on ASUS makes kernel stuck during loading initramfs on
  bionic-updates, bionic-security

Status in intel-microcode package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed

Bug description:
  Description:
  - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of 
booting, after grub)
  - does not even show the enter cryptsetup passphrase
  - affected kernels:
  # apt list --installed |grep linux-signed
  WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.
  linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 
[installed]
  linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 
4.18.0.20.70 amd64 [installed]
  linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 
5.0.0.15.71 amd64 [installed]

  - the setup is not new, has been working perfectly before (about 7
  days since my last restart?)

  System:
  - HW: ASUS Zenbook 14 UX433FN
  - Ubuntu 18.04, runing latest HWE, fully updated
  - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup),

  Suspected/possible cause?:
  - recent intel-microcode package update
  - recent kernel package updates

  Steps taken:
  - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding 
nosplash, noplymouth)
  - completely removed nvidia drivers (apt purge *nvidia*)
  - completely purged and reinstalled grub (grup-pc)
  - completely purged and reinstalled all kernels (headers, modules, image, ..)
  - toggle BIOS "fastboot" (now using OFF)
  - toggle UEFI SecureBoot (now using ON)
  - remove plymouth (apt remove *plymouth* , but the workaround is working with 
plymouth installed)

  Workaround:
  - so far, I'm only able to boot with non-Ubuntu kernel! 
(linux-image-liquorix-amd64)
  - which needs "splash" option ON
  - reinstall cryptsetup & update-grub (as suggested in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 )

  I am not sure how to get you more debug info, as this setup has been
  working before, and it's a very eary boot-process bug, so I can't even
  access dmesg etc.

  EDIT:

  Hypothesis:
  Only affects ASUS with i7-8565U Whiskey Lake Intel CPU

  Upstream Bug Report:
  https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1

  WORKAROUND 1: disable intel microcode updates during boot
  From this bug: 
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920
  1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub
  2/ update-grub

  WORKAROUND 2: downgrade (and hold) intel-microcode to older version from 
bionic/main
  apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: KDE neon 18.04
  InstallationDate: Installed on 2012-12-23 (2337 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Package: linux-hwe-edge (not installed)
  Tags:  bionic wayland-session
  Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video
  _MarkForUpload: True
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: KDE neon 18.04
  InstallationDate: Installed on 2012-12-23 (2339 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Package: linux-hwe-edge
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6
  Tags: third-party-packages bionic wayland-session
  Uname: Linux 5.0.0-15-generic x86_64
  UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny 
balíky třetích stran a zkuste to znovu.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm libvirtd lpadmin netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions

-- 
Mailing list: 

[Kernel-packages] [Bug 1832573] Re: linux-azure: -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1832575
+ phase: Holding before Packaging
+ phase-changed: Wednesday, 12. June 2019 14:36 UTC
+ reason:
+   prepare-package: Stalled -- waiting for master bug
  variant: debs

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

Title:
  linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1832575
  phase: Holding before Packaging
  phase-changed: Wednesday, 12. June 2019 14:36 UTC
  reason:
prepare-package: Stalled -- waiting for master bug
  variant: debs

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

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1832573 (trusty/linux-azure)
  derivatives: bug 1832571 (azure-kernel), bug 1832572 (linux-azure-edge)
  
  -- swm properties --
  kernel-stable-master-bug: 1832578
+ phase: Holding before Packaging
+ phase-changed: Wednesday, 12. June 2019 14:36 UTC
+ reason:
+   prepare-package: Stalled -- waiting for master bug
  variant: debs

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

Title:
  linux-azure:  -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1832573 (trusty/linux-azure)
  derivatives: bug 1832571 (azure-kernel), bug 1832572 (linux-azure-edge)

  -- swm properties --
  kernel-stable-master-bug: 1832578
  phase: Holding before Packaging
  phase-changed: Wednesday, 12. June 2019 14:36 UTC
  reason:
prepare-package: Stalled -- waiting for master bug
  variant: debs

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

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1832567 (xenial/linux-oracle)
  
  -- swm properties --
  kernel-stable-master-bug: 1832578
+ phase: Holding before Packaging
+ phase-changed: Wednesday, 12. June 2019 14:35 UTC
+ reason:
+   prepare-package: Stalled -- waiting for master bug
  variant: debs

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

Title:
  linux-oracle:  -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1832567 (xenial/linux-oracle)

  -- swm properties --
  kernel-stable-master-bug: 1832578
  phase: Holding before Packaging
  phase-changed: Wednesday, 12. June 2019 14:35 UTC
  reason:
prepare-package: Stalled -- waiting for master bug
  variant: debs

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

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1832578
+ phase: Holding before Packaging
+ phase-changed: Wednesday, 12. June 2019 14:35 UTC
+ reason:
+   prepare-package: Stalled -- waiting for master bug
  variant: debs

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

Title:
  linux-fips:  -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1832578
  phase: Holding before Packaging
  phase-changed: Wednesday, 12. June 2019 14:35 UTC
  reason:
prepare-package: Stalled -- waiting for master bug
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832570/+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 1804183] Re: netronome firmware symlinks are overwritten by package upgrade

[Simon Horman]

Hi,

Netronome would like to propose the following fix, which is to mark the 
symlinks as conffiles.
This produces a debian package which does not overwrite the symlinks when 
installed.

** Patch added: 
"0001-UBUNTU-Mark-netronome-firmware-symlinks-as-config-fi.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1804183/+attachment/5270366/+files/0001-UBUNTU-Mark-netronome-firmware-symlinks-as-config-fi.patch

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

Title:
  netronome firmware symlinks are overwritten by package upgrade

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  The linux-firmware package includes symlinks to installed Netronome
  firmware files. These links may be updated by a user but are
  overwritten when the linux-firmware package is upgraded whereas the
  desired behaviour is to leave existing symlinks unmodified.

  # apt install linux-firmware 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following package was automatically installed and is no longer required:
grub-pc-bin
  Use 'apt autoremove' to remove it.
  The following NEW packages will be installed:
linux-firmware
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 64.6 MB of archives.
  After this operation, 278 MB of additional disk space will be used.
  Get:1 http://lon1.mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 
linux-firmware all 1.173.1 [64.6 MB]
  Fetched 64.6 MB in 1s (43.8 MB/s) 
  Selecting previously unselected package linux-firmware.
  (Reading database ... 59988 files and directories currently installed.)
  Preparing to unpack .../linux-firmware_1.173.1_all.deb ...
  Unpacking linux-firmware (1.173.1) ...
  Setting up linux-firmware (1.173.1) ...
  update-initramfs: Generating /boot/initrd.img-4.15.0-38-generic
  # cd /lib/firmware/netronome/
  # ls -l
  total 8
  drwxr-xr-x 2 root root 4096 Nov 20 09:07 flower
  drwxr-xr-x 2 root root 4096 Nov 20 09:07 nic
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0081-0001_1x40.nffw -> 
nic/nic_AMDA0081-0001_1x40.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0081-0001_4x10.nffw -> 
nic/nic_AMDA0081-0001_4x10.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0096-0001_2x10.nffw -> 
nic/nic_AMDA0096-0001_2x10.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0097-0001_2x40.nffw -> 
nic/nic_AMDA0097-0001_2x40.nffw
  lrwxrwxrwx 1 root root   36 May 18  2018 nic_AMDA0097-0001_4x10_1x40.nffw -> 
nic/nic_AMDA0097-0001_4x10_1x40.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0097-0001_8x10.nffw -> 
nic/nic_AMDA0097-0001_8x10.nffw
  lrwxrwxrwx 1 root root   36 May 18  2018 nic_AMDA0099-0001_1x10_1x25.nffw -> 
nic/nic_AMDA0099-0001_1x10_1x25.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0099-0001_2x10.nffw -> 
nic/nic_AMDA0099-0001_2x10.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0099-0001_2x25.nffw -> 
nic/nic_AMDA0099-0001_2x25.nffw
  # for i in $(find flower/ -type l); do ln -sf $i $(basename $i); done
  # ls -l
  total 8
  drwxr-xr-x 2 root root 4096 Nov 20 09:07 flower
  drwxr-xr-x 2 root root 4096 Nov 20 09:07 nic
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0081-0001_1x40.nffw -> 
flower/nic_AMDA0081-0001_1x40.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0081-0001_4x10.nffw -> 
flower/nic_AMDA0081-0001_4x10.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0096-0001_2x10.nffw -> 
flower/nic_AMDA0096-0001_2x10.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0097-0001_2x40.nffw -> 
flower/nic_AMDA0097-0001_2x40.nffw
  lrwxrwxrwx 1 root root   39 Nov 20 09:09 nic_AMDA0097-0001_4x10_1x40.nffw -> 
flower/nic_AMDA0097-0001_4x10_1x40.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0097-0001_8x10.nffw -> 
flower/nic_AMDA0097-0001_8x10.nffw
  lrwxrwxrwx 1 root root   36 May 18  2018 nic_AMDA0099-0001_1x10_1x25.nffw -> 
nic/nic_AMDA0099-0001_1x10_1x25.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0099-0001_2x10.nffw -> 
flower/nic_AMDA0099-0001_2x10.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0099-0001_2x25.nffw -> 
flower/nic_AMDA0099-0001_2x25.nffw
  # apt update
  ...
  # apt install linux-firmware
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following package was automatically installed and is no longer required:
grub-pc-bin
  Use 'apt autoremove' to remove it.
  The following packages will be upgraded:
linux-firmware
  1 upgraded, 0 newly installed, 0 to remove and 49 not upgraded.
  Need to get 64.6 MB of archives.
  After this operation, 30.7 kB of additional disk space will be used.
  Get:1 http://lon1.mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 
linux-firmware all 1.173.2 [64.6 MB]
  Fetched 

[Kernel-packages] [Bug 1832567] Re: linux-oracle: -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1832569
+ phase: Holding before Packaging
+ phase-changed: Wednesday, 12. June 2019 14:35 UTC
+ reason:
+   prepare-package: Stalled -- waiting for master bug
  variant: debs

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

Title:
  linux-oracle:  -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1832569
  phase: Holding before Packaging
  phase-changed: Wednesday, 12. June 2019 14:35 UTC
  reason:
prepare-package: Stalled -- waiting for master bug
  variant: debs

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

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1832593
+ phase: Holding before Packaging
+ phase-changed: Wednesday, 12. June 2019 14:37 UTC
+ reason:
+   prepare-package: Stalled -- waiting for master bug
  variant: debs

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

Title:
  linux-fips:  -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1832593
  phase: Holding before Packaging
  phase-changed: Wednesday, 12. June 2019 14:37 UTC
  reason:
prepare-package: Stalled -- waiting for master bug
  variant: debs

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

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  derivatives: bug 1832581 (aws-kernel)
  
  -- swm properties --
  kernel-stable-master-bug: 1832593
+ phase: Holding before Packaging
+ phase-changed: Wednesday, 12. June 2019 14:36 UTC
+ reason:
+   prepare-package: Stalled -- waiting for master bug
  variant: debs

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

Title:
  linux-aws:  -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  derivatives: bug 1832581 (aws-kernel)

  -- swm properties --
  kernel-stable-master-bug: 1832593
  phase: Holding before Packaging
  phase-changed: Wednesday, 12. June 2019 14:36 UTC
  reason:
prepare-package: Stalled -- waiting for master bug
  variant: debs

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

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1832593
+ phase: Holding before Packaging
+ phase-changed: Wednesday, 12. June 2019 14:37 UTC
+ reason:
+   prepare-package: Stalled -- waiting for master bug
  variant: debs

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

Title:
  linux-kvm:  -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1832593
  phase: Holding before Packaging
  phase-changed: Wednesday, 12. June 2019 14:37 UTC
  reason:
prepare-package: Stalled -- waiting for master bug
  variant: debs

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

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  derivatives: bug 1832587 (dragonboard-kernel)
  
  -- swm properties --
  kernel-stable-master-bug: 1832593
+ phase: Holding before Packaging
+ phase-changed: Wednesday, 12. June 2019 14:37 UTC
+ reason:
+   prepare-package: Stalled -- waiting for master bug
  variant: debs

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

Title:
  linux-snapdragon:  -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:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  derivatives: bug 1832587 (dragonboard-kernel)

  -- swm properties --
  kernel-stable-master-bug: 1832593
  phase: Holding before Packaging
  phase-changed: Wednesday, 12. June 2019 14:37 UTC
  reason:
prepare-package: Stalled -- waiting for master bug
  variant: debs

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

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  derivatives: bug 1832584 (pi2-kernel)
  
  -- swm properties --
  kernel-stable-master-bug: 1832593
+ phase: Holding before Packaging
+ phase-changed: Wednesday, 12. June 2019 14:37 UTC
+ reason:
+   prepare-package: Stalled -- waiting for master bug
  variant: debs

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

Title:
  linux-raspi2:  -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:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  derivatives: bug 1832584 (pi2-kernel)

  -- swm properties --
  kernel-stable-master-bug: 1832593
  phase: Holding before Packaging
  phase-changed: Wednesday, 12. June 2019 14:37 UTC
  reason:
prepare-package: Stalled -- waiting for master bug
  variant: debs

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

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1832593
+ phase: Holding before Packaging
+ phase-changed: Wednesday, 12. June 2019 14:38 UTC
+ reason:
+   prepare-package: Stalled -- waiting for master bug
  variant: debs

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

Title:
  linux-aws:  -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1832593
  phase: Holding before Packaging
  phase-changed: Wednesday, 12. June 2019 14:38 UTC
  reason:
prepare-package: Stalled -- waiting for master bug
  variant: debs

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

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  derivatives: bug 1832543 (dragonboard-kernel)
  
  -- swm properties --
  kernel-stable-master-bug: 1832578
+ phase: Holding before Packaging
+ phase-changed: Wednesday, 12. June 2019 14:34 UTC
+ reason:
+   prepare-package: Stalled -- waiting for master bug
  variant: debs

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

Title:
  linux-snapdragon:  -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:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  derivatives: bug 1832543 (dragonboard-kernel)

  -- swm properties --
  kernel-stable-master-bug: 1832578
  phase: Holding before Packaging
  phase-changed: Wednesday, 12. June 2019 14:34 UTC
  reason:
prepare-package: Stalled -- waiting for master bug
  variant: debs

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

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1832578
+ phase: Holding before Packaging
+ phase-changed: Wednesday, 12. June 2019 14:34 UTC
+ reason:
+   prepare-package: Stalled -- waiting for master bug
  variant: debs

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

Title:
  linux-oem:  -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:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1832578
  phase: Holding before Packaging
  phase-changed: Wednesday, 12. June 2019 14:34 UTC
  reason:
prepare-package: Stalled -- waiting for master bug
  variant: debs

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

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  derivatives: bug 1832541 (pi-kernel)
  
  -- swm properties --
  kernel-stable-master-bug: 1832578
+ phase: Holding before Packaging
+ phase-changed: Wednesday, 12. June 2019 14:34 UTC
+ reason:
+   prepare-package: Stalled -- waiting for master bug
  variant: debs

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

Title:
  linux-raspi2:  -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:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  derivatives: bug 1832541 (pi-kernel)

  -- swm properties --
  kernel-stable-master-bug: 1832578
  phase: Holding before Packaging
  phase-changed: Wednesday, 12. June 2019 14:34 UTC
  reason:
prepare-package: Stalled -- waiting for master bug
  variant: debs

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