[Kernel-packages] [Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver

[Brian Murray]

I don't see an upload of ubuntu-drivers-common in the unapproved queue
or in -proposed which addresses this bug so I'm setting it back to In
Progress. Fix Committed should *not* be used for Ubuntu bug tasks if the
fix is in some "upstream" branch.

** Changed in: ubuntu-drivers-common (Ubuntu Jammy)
   Status: Fix Committed => In Progress

** Changed in: ubuntu-drivers-common (Ubuntu)
   Status: Fix Committed => In Progress

** Changed in: ubuntu-drivers-common (Ubuntu Noble)
   Status: Fix Committed => In Progress

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

Title:
  Phantom "Unknown Display" shown in Settings after installing the
  Nvidia driver

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-550 package in Ubuntu:
  Won't Fix
Status in ubuntu-drivers-common package in Ubuntu:
  In Progress
Status in ubuntu-drivers-common source package in Jammy:
  In Progress
Status in ubuntu-drivers-common source package in Noble:
  In Progress

Bug description:
  [ Impact ]

  After installing Nvidia driver 545 on a single (27") monitor system,
  Settings shows a phantom 46" monitor of the same resolution.

  It looks like the phantom monitor is /dev/dri/card0 which is still
  controlled by simpledrm, while Nvidia uses /dev/dri/card1.

  This also seems to be triggering bug 2062426 and bug 2066126.

  [ Temporary Workaround ]

  1. sudo rm /dev/dri/card0
  2. Log in again.

  [ Permanent Workaround ]

  Add kernel parameter:
  initcall_blacklist=simpledrm_platform_driver_init

  [ Test Plan ]

  Open Settings and verify the only monitors shown are your real
  monitors.

  [ Where problems could occur ]

  Removing the simpledrm card is only safe when it's not being used. If
  somehow a machine wasn't using the installed Nvidia driver then there
  could be a risk of deleting the only working display.

  [ Other Info ]

  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:dan4631 F pipewire
   /dev/snd/controlC1:  dan4636 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-01-04 (92 days ago)
  InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
  MachineType: Intel(R) Client Systems NUC12DCMi7
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 simpledrmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic 
root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-11-generic N/A
   linux-backports-modules-6.8.0-11-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu1
  Tags: noble
  Uname: Linux 6.8.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/20/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: EDADL579.0046.2021.1220.2351
  dmi.board.name: NUC12EDBi7
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M27908-302
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 3.7
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7:
  dmi.product.family: DC
  dmi.product.name: NUC12DCMi7
  dmi.product.sku: RNUC12DCMi7
  dmi.product.version: M30143-302
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2060268/+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 1750046] Re: linux: 4.13.0-36.40 -proposed tracker

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: linux (Ubuntu Artful)
   Status: Confirmed => Won't Fix

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

Title:
  linux: 4.13.0-36.40 -proposed tracker

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

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

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

  backports: bug 1750047 (linux-azure), bug 1750048 (linux-azure-edge), bug 
1750049 (linux-gcp), bug 1750052 (linux-hwe), bug 1750053 (linux-hwe-edge), bug 
1750055 (linux-oem)
  derivatives: bug 1750057 (linux-raspi2)
  -- swm properties --
  flag:
boot-testing-requested: true
proposed-announcement-sent: true
proposed-testing-requested: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Released
  reason: {}
  ~~:
clamps:
  self: 4.13.0-36.40
tracker:
  last-message: '2024-07-31 19:14:20.758260+00:00'

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1750046/+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 1766300] Re: hv-fcopy-daemon service fails to start if /dev/vmbus/hv_fcopy doesn't exist

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: linux-azure (Ubuntu Artful)
   Status: New => Won't Fix

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

Title:
  hv-fcopy-daemon service fails to start if /dev/vmbus/hv_fcopy doesn't
  exist

Status in linux package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Trusty:
  New
Status in linux-azure source package in Trusty:
  New
Status in linux source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux source package in Artful:
  Won't Fix
Status in linux-azure source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  Incomplete
Status in linux-azure source package in Bionic:
  New

Bug description:
  On VMs launched in Azure, /dev/vmbus/hv_fcopy doesn't exist, so hv-
  fcopy-daemon fails to start.  This means that boot is degraded by
  default:

  $ systemctl list-units --failed --no-legend
  hv-fcopy-daemon.service loaded failed failed Hyper-V File Copy Protocol Daemon

  $ systemctl is-system-running 
  degraded

  which makes detecting other failures much harder to automate.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-cloud-tools-common 4.15.0-15.16
  ProcVersionSignature: User Name 4.15.0-1004.4-azure 4.15.15
  Uname: Linux 4.15.0-1004-azure x86_64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  Date: Mon Apr 23 16:27:47 2018
  Dependencies:
   
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  PackageArchitecture: all
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1004-azure 
root=UUID=fda9466a-9068-447f-8572-6d8d310eabd3 ro console=tty1 console=ttyS0 
earlyprintk=ttyS0 rootdelay=300
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1004-azure N/A
   linux-backports-modules-4.15.0-1004-azure  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/02/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090007
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.uuid: 44FD5ABF-DE16-AD4A-B2E0-6E70167950AF
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766300/+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 1766300] Re: hv-fcopy-daemon service fails to start if /dev/vmbus/hv_fcopy doesn't exist

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: linux (Ubuntu Artful)
   Status: New => Won't Fix

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

Title:
  hv-fcopy-daemon service fails to start if /dev/vmbus/hv_fcopy doesn't
  exist

Status in linux package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Trusty:
  New
Status in linux-azure source package in Trusty:
  New
Status in linux source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux source package in Artful:
  Won't Fix
Status in linux-azure source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  Incomplete
Status in linux-azure source package in Bionic:
  New

Bug description:
  On VMs launched in Azure, /dev/vmbus/hv_fcopy doesn't exist, so hv-
  fcopy-daemon fails to start.  This means that boot is degraded by
  default:

  $ systemctl list-units --failed --no-legend
  hv-fcopy-daemon.service loaded failed failed Hyper-V File Copy Protocol Daemon

  $ systemctl is-system-running 
  degraded

  which makes detecting other failures much harder to automate.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-cloud-tools-common 4.15.0-15.16
  ProcVersionSignature: User Name 4.15.0-1004.4-azure 4.15.15
  Uname: Linux 4.15.0-1004-azure x86_64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  Date: Mon Apr 23 16:27:47 2018
  Dependencies:
   
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  PackageArchitecture: all
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1004-azure 
root=UUID=fda9466a-9068-447f-8572-6d8d310eabd3 ro console=tty1 console=ttyS0 
earlyprintk=ttyS0 rootdelay=300
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1004-azure N/A
   linux-backports-modules-4.15.0-1004-azure  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/02/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090007
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.uuid: 44FD5ABF-DE16-AD4A-B2E0-6E70167950AF
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766300/+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 1743638] Re: Missing install-time driver for QLogic QED 25/40/100Gb Ethernet NIC

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: debian-installer (Ubuntu Artful)
   Status: Fix Committed => Won't Fix

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

Title:
  Missing install-time driver for QLogic QED 25/40/100Gb Ethernet NIC

Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in debian-installer source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux-hwe source package in Xenial:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in debian-installer source package in Artful:
  Won't Fix
Status in linux source package in Artful:
  Fix Released
Status in linux-firmware source package in Artful:
  Won't Fix
Status in linux-hwe source package in Artful:
  Invalid
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in debian-installer source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-hwe source package in Bionic:
  Invalid
Status in linux-hwe-edge source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Network installs over a QLogic QED 25/40/100Gb Ethernet NIC will not work.

  [Test Case]
  Attempt to use the netinst installer to install a system over this NIC.

  [Regression Risk]
  The fix is just add to add additional kernel modules and firmware to the 
installer to support this NIC. The biggest risk I see there is that it 
increases the size of the installer, which could potentially grow to bit for 
some smaller systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1743638/+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 1735170] Re: Remove Joule audio topology firmware

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: linux-firmware (Ubuntu Artful)
   Status: New => Won't Fix

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

Title:
  Remove Joule audio topology firmware

Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux-firmware source package in Xenial:
  New
Status in linux-firmware source package in Zesty:
  New
Status in linux-firmware source package in Artful:
  Won't Fix

Bug description:
  SRU Justification

  Impact: This firmware was added in bug 1689497, but packages for Joule
  no longer exist and is no longer needed.

  Fix: Remove the firmware file.

  Test Case: Verify that the file is no longer present in the package.

  Regression Potential: Since the firmware is not used by any supported
  kernels there is virtually no regression potential to removing it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1735170/+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 1752507] Re: add i915/glk_dmc_ver1_04.bin

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: linux-firmware (Ubuntu Artful)
   Status: Fix Committed => Won't Fix

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

Title:
  add i915/glk_dmc_ver1_04.bin

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux-firmware source package in Artful:
  Won't Fix

Bug description:
  SRU Justification

  Impact: New firmware is needed to fix issues with S3 for i915 on
  Geminilake hardware.

  Fix: Add the mising firmware.

  Test Case: Test S3 on affected hardware.

  Regression Potential: Limited as the firmware is only loaded for
  specific hardware. Regressions are possible, but none are known, and
  the new firmware does fix a known problem.

  ---

  Intel Gemini Lake needs DMC firmware to fix some S3 issues on xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1752507/+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 1745123] Re: Elasticsearch 2.4.6 cause a Oops: 0010 [#37] SMP NOPTI

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: elasticsearch (Ubuntu Artful)
   Status: Confirmed => Won't Fix

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

Title:
  Elasticsearch 2.4.6 cause a Oops: 0010 [#37] SMP NOPTI

Status in elasticsearch package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in elasticsearch source package in Artful:
  Won't Fix
Status in linux source package in Artful:
  Won't Fix

Bug description:
  Elasticsearch 2.4.6 can't start since new kernel upgrade
  (4.13.0-31-generic #34~16.04.1-Ubuntu)

  Kernel log contains :

  [ 4308.595429] Oops: 0010 [#37] SMP NOPTI
  [ 4308.595430] Modules linked in: btrfs xor raid6_pq ufs qnx4 hfsplus hfs 
minix ntfs msdos jfs xfs libcrc32c bnep pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) bluetooth ecdh_generic binfmt_misc nls_iso8859_1 
snd_hda_codec_hdmi edac_mce_amd snd_hda_codec_realtek snd_hda_codec_generic 
snd_hda_intel eeepc_wmi kvm_amd asus_wmi snd_hda_codec sparse_keymap 
snd_hda_core video wmi_bmof kvm input_leds joydev snd_hwdep snd_pcm irqbypass 
crct10dif_pclmul snd_seq_midi crc32_pclmul snd_seq_midi_event 
ghash_clmulni_intel snd_rawmidi pcbc nvidia_uvm(POE) snd_seq aesni_intel 
snd_seq_device snd_timer snd aes_x86_64 crypto_simd soundcore ccp glue_helper 
cryptd shpchp i2c_piix4 8250_dw wmi mac_hid parport_pc ppdev lp parport autofs4 
hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE)
  [ 4308.595462]  drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
drm r8169 ahci mii libahci gpio_amdpt gpio_generic
  [ 4308.595468] CPU: 0 PID: 9314 Comm: java Tainted: P  DOE   
4.13.0-31-generic #34~16.04.1-Ubuntu
  [ 4308.595470] Hardware name: System manufacturer System Product Name/PRIME 
B350M-A, BIOS 0502 02/24/2017
  [ 4308.595471] task: 8dfa07b945c0 task.stack: b2b6033f4000
  [ 4308.595472] RIP: 0010:0x6987877
  [ 4308.595473] RSP: 0018:b2b6033f7f50 EFLAGS: 00010202
  [ 4308.595474] RAX: 03e7 RBX:  RCX: 
7f20e3d314d9
  [ 4308.595475] RDX: 7f20dc6686c0 RSI: 4d73aa93 RDI: 

  [ 4308.595476] RBP:  R08: 7f20e319caa4 R09: 
000c
  [ 4308.595477] R10: 06987877 R11: 8dfa07b945c0 R12: 

  [ 4308.595478] R13:  R14:  R15: 

  [ 4308.595479] FS:  7f20e4823700() GS:8dfac660() 
knlGS:
  [ 4308.595480] CS:  0010 DS:  ES:  CR0: 80050033
  [ 4308.595481] CR2: 06987877 CR3: 0003b723e000 CR4: 
003406f0
  [ 4308.595482] Call Trace:
  [ 4308.595487]  ? entry_SYSCALL_64_fastpath+0x33/0xa3
  [ 4308.595489] Code:  Bad RIP value.
  [ 4308.595490] RIP: 0x6987877 RSP: b2b6033f7f50
  [ 4308.595491] CR2: 06987877
  [ 4308.595493] ---[ end trace ba92d9f3b2090708 ]---

  
  It related to new kernel update, it work when starting with an older kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/elasticsearch/+bug/1745123/+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 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: linux (Ubuntu Artful)
   Status: Confirmed => Won't Fix

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

Title:
  gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive pike series:
  Fix Released
Status in Ubuntu Cloud Archive queens series:
  Fix Released
Status in neutron:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in openvswitch package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Won't Fix
Status in openvswitch source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Confirmed
Status in openvswitch source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  OpenStack Clouds using GRE overlay tunnels with > 1500 MTU's will observe 
packet fragmentation/networking issues for traffic in overlay networks.

  [Test Case]
  Deploy OpenStack Pike (xenial + pike UCA or artful)
  Create tenant networks using GRE segmentation
  Boot instances
  Instance networking will be broken/slow

  gre_sys devices will be set to mtu=1472 on hypervisor hosts.

  [Regression Potential]
  Minimal; the fix to OVS works around an issue for GRE tunnel port setup via 
rtnetlink by performing a second request once the gre device is setup to set 
the MTU to a high value (65000).

  
  [Original Bug Report]
  Setup:
  Pike neutron 11.0.2-0ubuntu1.1~cloud0
  OVS 2.8.0
  Jumbo frames setttings per: 
https://docs.openstack.org/mitaka/networking-guide/config-mtu.html
  global_physnet_mtu = 9000
  path_mtu = 9000

  Symptoms:
  gre_sys MTU is 1472
  Instances with MTUs > 1500 fail to communicate across GRE

  Temporary Workaround:
  ifconfig gre_sys MTU 9000
  Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set 
back to default 1472.

  Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue.

  Previous behavior:
  With Ocata or Pike and OVS 2.6.x
  gre_sys MTU defaults to 65490
  It remains at 65490 through restarts.

  This may be related to some combination of the following changes in OVS which 
seem to imply MTUs must be set in the ovs database for tunnel interfaces and 
patches:
  
https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1
  
https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f
  
https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1742505/+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 1722603] Re: No automatic driver install for Apple facetime camera ( experimental working driver available)

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: ubuntu-drivers-common (Ubuntu Artful)
   Status: New => Won't Fix

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

Title:
  No automatic driver install for Apple facetime camera ( experimental
  working driver available)

Status in linux package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  New
Status in linux source package in Artful:
  Won't Fix
Status in ubuntu-drivers-common source package in Artful:
  Won't Fix

Bug description:
  the integrated facetime camera does not work on Ubuntu 22.04 out of
  the box.

  the current workaround is outlined here:
  https://github.com/patjak/bcwc_pcie/wiki/Get-Started#additional-notes

  would it be possible to have this driver supported by ubuntu-drivers ?

  
  Manual Dkms Solution : 

  git clone https://github.com/ekimiateam/facetimehd
  git clone https://github.com/patjak/facetimehd-firmware
  make -C facetimehd-firmware/ deb 
  cp facetimehd-firmware/debian/*.deb .
  cd facetimehd/
  dpkg-buildpackage -us -uc
  cd ..
  sudo apt install ./facetimehd*.deb

  -

  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peter  1906 F pulseaudio
   /dev/snd/controlC1:  peter  1906 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-04-05 (553 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  MachineType: Apple Inc. MacBookPro12,1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed 
root=UUID=540e40c6-4d83-4c9e-8dfe-18c9ab5e2234 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-12-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-09 (1 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/18/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B33.1706181928
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722603/+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 1741467] Re: Process's swap use blocks all other processes as well

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: linux (Ubuntu Artful)
   Status: Confirmed => Won't Fix

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

Title:
  Process's swap use blocks all other processes as well

Status in linux package in Ubuntu:
  Confirmed
Status in linux-base package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  Won't Fix
Status in linux-base source package in Artful:
  Invalid

Bug description:
  What happens:
  1. My process runs out of memory
  2. Some of its pages get swapped to disk
  3. While this happens all processes stop and wait

  What i expect to happen:
  Other processes should continue as usual.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-base 4.5ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jan  5 15:27:18 2018
  InstallationDate: Installed on 2017-12-14 (22 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  PackageArchitecture: all
  SourcePackage: linux-base
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  volodya1620 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=7b8f7f86-5017-44ec-bf81-976c66d77a44
  InstallationDate: Installed on 2017-12-14 (131 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: ASUSTeK COMPUTER INC. N76VB
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-38-generic.efi.signed 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-38-generic N/A
   linux-backports-modules-4.13.0-38-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful
  Uname: Linux 4.13.0-38-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N76VB.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N76VB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN76VB.205:bd05/24/2013:svnASUSTeKCOMPUTERINC.:pnN76VB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN76VB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N76VB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741467/+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 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: glibc (Ubuntu Artful)
   Status: New => Won't Fix

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial), please disable LLMNR

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in glibc source package in Artful:
  Won't Fix
Status in linux source package in Artful:
  Won't Fix
Status in systemd source package in Artful:
  Won't Fix
Status in glibc source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739672/+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 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: linux (Ubuntu Artful)
   Status: New => Won't Fix

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial), please disable LLMNR

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in glibc source package in Artful:
  Won't Fix
Status in linux source package in Artful:
  Won't Fix
Status in systemd source package in Artful:
  Won't Fix
Status in glibc source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739672/+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 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: systemd (Ubuntu Artful)
   Status: New => Won't Fix

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial), please disable LLMNR

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in glibc source package in Artful:
  Won't Fix
Status in linux source package in Artful:
  Won't Fix
Status in systemd source package in Artful:
  Won't Fix
Status in glibc source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739672/+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 1749776] Re: kpti must be disabled on ThunderX systems

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: linux (Ubuntu Artful)
   Status: In Progress => Won't Fix

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

Title:
  kpti must be disabled on ThunderX systems

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

Bug description:
  Our arm64 kpti backport is missing a series that disables KPTI on ThunderX 
platforms. KPTI is not necessary on this system, and it can lead to icache 
corruption:
  http://lists.infradead.org/pipermail/linux-arm-kernel/2018-January/556304.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749776/+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 1743638] Re: Missing install-time driver for QLogic QED 25/40/100Gb Ethernet NIC

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: linux-firmware (Ubuntu Artful)
   Status: Fix Committed => Won't Fix

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

Title:
  Missing install-time driver for QLogic QED 25/40/100Gb Ethernet NIC

Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in debian-installer source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux-hwe source package in Xenial:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in debian-installer source package in Artful:
  Won't Fix
Status in linux source package in Artful:
  Fix Released
Status in linux-firmware source package in Artful:
  Won't Fix
Status in linux-hwe source package in Artful:
  Invalid
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in debian-installer source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-hwe source package in Bionic:
  Invalid
Status in linux-hwe-edge source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Network installs over a QLogic QED 25/40/100Gb Ethernet NIC will not work.

  [Test Case]
  Attempt to use the netinst installer to install a system over this NIC.

  [Regression Risk]
  The fix is just add to add additional kernel modules and firmware to the 
installer to support this NIC. The biggest risk I see there is that it 
increases the size of the installer, which could potentially grow to bit for 
some smaller systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1743638/+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 1746463] Re: apparmor profile load in stacked policy container fails

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: apparmor (Ubuntu Artful)
   Status: Fix Committed => Won't Fix

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

Title:
  apparmor profile load in stacked policy container fails

Status in snapd:
  Triaged
Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Won't Fix
Status in linux source package in Xenial:
  Invalid
Status in linux-gcp source package in Xenial:
  Fix Released
Status in apparmor source package in Artful:
  Won't Fix
Status in linux source package in Artful:
  Fix Released
Status in linux-gcp source package in Artful:
  Invalid
Status in apparmor source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux-gcp source package in Bionic:
  Fix Released

Bug description:
  LXD containers on an artful or bionic host with aa namespaces, should
  be able to load the lxc policies. However /lib/apparmor/profile-load
  skips that part when running in a container.

  aa-status shows 0 policies

  /lib/apparmor/profile-load is failing due to
  is_container_with_internal_policy() failing

  due to

  /sys/kernel/security/apparmor/.ns_name being empty which causes

if [ "${ns_name#lxd-*}" = "$ns_name" ] && \
   [ "${ns_name#lxc-*}" = "$ns_name" ]; then
return 1
fi

  to fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1746463/+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 1757565] Re: btrfs and tar sparse truncate archives

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: tar (Ubuntu Artful)
   Status: New => Won't Fix

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

Title:
  btrfs and tar sparse truncate archives

Status in linux package in Ubuntu:
  Fix Released
Status in tar package in Ubuntu:
  New
Status in linux source package in Artful:
  Fix Released
Status in tar source package in Artful:
  Won't Fix

Bug description:
  
  == SRU Justification ==
  This bug causes btrfs and tar sparse to truncate archives.  This bug has been 
  fixed in v4.15-rc3 by commit e3b8a4858566, which has a prereq commit of 
f48bf66b662e.

  These commits were cc'd to upstream stable and are already in Bionic.  
However, upstream
  4.13 is EOL, so Artful never recieved the fixes, which is the reason for
  the SRU request.

  == Fixes ==
  f48bf66b662e ("Btrfs: move definition of the function 
btrfs_find_new_delalloc_bytes")
  e3b8a4858566 ("Btrfs: fix reported number of inode blocks after buffered 
append writes")

  == Regression Potential ==
  Low.  This fix was also sent and accepted to stable, so it has had additional 
upstream review.

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



  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  root@ubuntu:~# apt-cache policy linux-image-virtual
  linux-image-virtual:
    Installed: 4.13.0.37.40
    Candidate: 4.13.0.37.40
    Version table:
   *** 4.13.0.37.40 500
  500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.13.0.16.17 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages

  3. Taring files into an archive are not truncated
  4. Files included in tar are filled with NULLs

  To reproduce, run an Artful system with one spare disk:

  - mkfs.btrfs -f /dev/sda
  - mount /dev/sda /mnt
  - grep sda /proc/mounts
  /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0

  Then run this script which copies a 4MB binary to a btrfs filesystem,
  tars the directory up containing the binary; then untars to stdout and
  md5sum compares, showing it's different.

  % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum
  e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
  0ce8c4139740198926273853defcb12a  -

  And now without the sparse flag:

  # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum
  e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
  e4121d2f3126b8c364bfa1aaa82371a3  -

  This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an 
actual fix.
  Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 
kernel appears to be fixed as well though I'm not sure what the difference is.

  References:

  https://patchwork.kernel.org/patch/10151037/
  https://www.spinics.net/lists/linux-btrfs/msg56768.html
  https://www.spinics.net/lists/linux-btrfs/msg57111.html

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-virtual 4.13.0.37.40
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 21 22:55 seq
   crw-rw 1 root audio 116, 33 Mar 21 22:55 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  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:
  CRDA: N/A
  Date: Wed Mar 21 23:08:05 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-37-generic N/A
   linux-backports-modules-4.13.0-37-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfk

[Kernel-packages] [Bug 1753489] Re: kernel BUG at /build/linux-hwe-Fuabdm/linux-hwe-4.13.0/fs/jbd2/transaction.c:1868!

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: linux (Ubuntu Artful)
   Status: Confirmed => Won't Fix

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

Title:
  kernel BUG at /build/linux-hwe-Fuabdm/linux-
  hwe-4.13.0/fs/jbd2/transaction.c:1868!

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  Incomplete

Bug description:
  [ 1678.415861] kernel BUG at 
/build/linux-hwe-Fuabdm/linux-hwe-4.13.0/fs/jbd2/transaction.c:1868!
  [ 1678.425019] Internal error: Oops - BUG: 0 [#1] SMP
  [ 1678.430358] Modules linked in: nls_iso8859_1 i2c_thunderx i2c_smbus 
cavium_rng_vf thunderx_edac thunderx_zip shpchp ipmi_ssif cavium_rng gpio_keys 
ipmi_devintf ipmi_msghandler uio_pdrv_genirq uio ib_iser rdma_cm iw_cm ib_cm 
ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs 
algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
nicvf nicpf ast i2c_algo_bit ttm drm_kms_helper syscopyarea aes_ce_blk 
sysfillrect sysimgblt aes_ce_cipher fb_sys_fops crc32_ce crct10dif_ce drm 
ghash_ce sha2_ce sha1_ce ahci libahci thunder_bgx thunder_xcv mdio_thunder 
thunderx_mmc mdio_cavium aes_neon_bs aes_neon_blk crypto_simd cryptd
  [ 1678.503033] CPU: 3 PID: 776 Comm: jbd2/dm-1-8 Tainted: GWL  
4.13.0-36-generic #40~16.04.1-Ubuntu
  [ 1678.515386] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., 
BIOS 5.11 12/12/2012
  [ 1678.525143] task: 801f8a75e900 task.stack: 801f633fc000
  [ 1678.532489] PC is at __jbd2_journal_temp_unlink_buffer+0x104/0x160
  [ 1678.540140] LR is at __jbd2_journal_file_buffer+0x8c/0x1f8
  [ 1678.547111] pc : [] lr : [] pstate: 
80400145
  [ 1678.556071] sp : 801f633ffb70
  [ 1678.560960] x29: 801f633ffb70 x28: 7e007ca625c0
  [ 1678.567890] x27:  x26: 801ecd5776e8
  [ 1678.574845] x25:  x24: 01400040
  [ 1678.581812] x23: 0001 x22: 801f3f4bb8f0
  [ 1678.588799] x21: 0003 x20: 801f3f4bb8f0
  [ 1678.595787] x19: 801f4a18ea50 x18: 
  [ 1678.602807] x17:  x16: 
  [ 1678.609844] x15: ddd41681 x14: 3a7accb0
  [ 1678.616895] x13: 4d1a8a2c x12: 91b5ac46
  [ 1678.623964] x11: 801f79729770 x10: 093c8c08
  [ 1678.631058] x9 : 001d x8 : 801ecd577750
  [ 1678.638182] x7 :  x6 : 0001
  [ 1678.645323] x5 :  x4 : 0040
  [ 1678.652468] x3 : 0016 x2 : 801f6d655a28
  [ 1678.659633] x1 :  x0 : 801f6d655a00
  [ 1678.666808] Process jbd2/dm-1-8 (pid: 776, stack limit = 
0x801f633fc000)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753489/+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 1726730] Re: IPRoute pkg is in different version than kernel

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: iproute2 (Ubuntu Artful)
   Status: New => Won't Fix

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

Title:
  IPRoute pkg is in different version than kernel

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Zesty:
  New
Status in iproute2 source package in Artful:
  Won't Fix
Status in iproute2 source package in Bionic:
  Fix Released

Bug description:
  Hello,

  At the moment there is a problem with Iproute package in Zesty and
  artful.

  In Zesty the kernel version is 4.10.0, and the Iproute package is 4.9.0. 
  In Artful the kernel version is 4.13, and the Iproute is 4.9.0 too. 

  This is causing some problems in the BPF/XDP setup, some code is in
  the kernel but doesn't have the same version in Iproute, so it'll
  fail.

  Found the problem using cilium project
   and the problem was
  validated by Daniel Borkmann (iproute mantainer)

  I didn't find any related bug related to updating. If you need help to
  test/update, I can help you.

  Regards and many thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1726730/+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 1728115] Re: crashkernel offset prevents kernel boot

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: linux (Ubuntu Artful)
   Status: New => Won't Fix

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

Title:
  crashkernel offset prevents kernel boot

Status in linux package in Ubuntu:
  Incomplete
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Won't Fix
Status in makedumpfile source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Incomplete
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On Power Systems, the kernel won't boot when given a crashkernel parameter 
with an offset/start address of 32M. No output will be shown, giving no clue to 
the user why the system has not booted, or what the problem is.

  [Test Case]
  Installing kdump-tools on artful, then booting the system. It won't boot. 
With the fix, it boots and the crash kernel is reserved.

  [Regression Potential]
  Some Power Systems might have problems loading the kernel at this address. 
LP#1567539 is not really clear if PowerNV systems won't kdump when using an 
address different from 32M. However, it has been requested from an IBM person 
to test it with 128M instead, and no particular problem was shown. It's 
possible that there was no reason at first to use 32M, and no problems will be 
found on either PowerNV or other systems on the field. On the other hand, it's 
possible they might break kdump. But, right now, those systems won't even boot 
the first kernel without this change.

  

  The linux kernel won't boot when crashkernel parameter tells it to
  load a crash kernel at 32Mi on ppc64el on artful.

  This happens because the artful kernel is too big. In fact, multiple
  requirements on the architecture lead to that:

  Kernel memory at address 0 is reserved.
  crashkernel must be at first RMO, so architecture puts it at 128Mi. However, 
kdump-tools currently puts it at @32Mi because of bug 
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1567539.
  PACA and LPPACA need to be at the first RMO as well, and with 2048 CPUs, they 
take more than 5MB and 2MiB, respectively.

  With the kernel now taking around 25MB from stext to _end, the kernel
  can't reserve enough memory for PACA or LPPACA right after boot, and
  it panics.

  So, right after installing kdump-tools on artful, and rebooting, the
  kernel won't boot, with no sign of life as we haven't even started any
  console. Investigation for this issue took an entire day.

  The fix would be setting the loading address to 128MiB, and start
  reducing size of PACA and maybe remove some of the requirements for
  the location of PACA and crash kernel.

  I would not even set the loading address of the crash kernel in the
  parameter itself, and leave it to the kernel to decide it, which it
  already does and already would put it at 128Mi.

  Cascardo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728115/+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 2074302] Re: Asus Laptop (R558U) does not suspend after upgrade to 24.04

[Brian Murray]

It also looks like you version of the kernel is out of date. You might
try updating to 6.8.0-39.39 and see if that helps resolve the issue.

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

Title:
  Asus Laptop (R558U) does not suspend after upgrade to 24.04

Status in linux package in Ubuntu:
  New
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  I was previously running Ubuntu 23.10 on my laptop. I performed a
  `dist-upgrade` about a week back. Since the upgrade to 24.04 my laptop
  does not suspend - either by pressing the power-key (previously
  working on 23.10) or by using the GNOME system power menu.

  My laptop has integrated Intel graphics as well as NVIDIA GeForce
  930MX (GM108M), but i haven't installed proprietary video drivers. It
  is currently using xserver-x-org-video-nouveau as the video driver. My
  system reports as running a wayland session, but I find the above
  X.Org detail confusing.

  There is currently one inhibitor running `gsd-media-keys`.

  I filed a bug under systemd as ubuntu-bug would not let me file a bug
  without a package name. If this is incorrect, please change the
  package-name as appropriate.

  I would like to restore previous functionality - system suspend on
  command.

  I'd be happy to provide additional logs and to troubleshoot any
  possible fixes.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: systemd 255.4-1ubuntu8.2
  ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
  Uname: Linux 6.8.0-38-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 28 19:11:12 2024
  InstallationDate: Installed on 2019-04-20 (1926 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: ASUSTeK COMPUTER INC. X556UR
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-38-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to noble on 2024-07-20 (8 days ago)
  dmi.bios.date: 10/24/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X556UR.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X556UR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX556UR.309:bd10/24/2016:br5.11:svnASUSTeKCOMPUTERINC.:pnX556UR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: X
  dmi.product.name: X556UR
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074302/+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 1809624] Re: net test in ubuntu_kernel_selftest failed on s390x KVM

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: New => Won't Fix

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

Title:
  net test in ubuntu_kernel_selftest failed on s390x KVM

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  Verified with the testing tool in the upstream kernel, this issue can
  be reproduced with it.

   not ok 1..4 selftests:  reuseport_dualstack [FAIL]
   selftests: reuseaddr_conflict

  Please find the complete test report here:
  https://pastebin.ubuntu.com/p/3sRh6Nr9KR/

  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 s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Mon Dec 24 03:10:49 2018
  HibernationDevice: RESUME=UUID=caaee9b2-6bc1-4c8e-b26c-69038c092091
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=c7d7bbcb-a039-4ead-abfe-7672dea0add4 
crashkernel=196M
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809624/+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 1675949] Re: perf report can't annotate kernel and dbgsym package has wrong addresses

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: New => Won't Fix

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

Title:
  perf report can't annotate kernel and dbgsym package has wrong
  addresses

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Won't Fix

Bug description:
  Impact:

  Under some condition, 'perf report' is unable to show the assembly
  code of a kernel function (perf report -> select a kernel function ->
  annotate).

  This is not an issue of the kernel itself or the perf tool, instead
  it's your environment that is missing the objdump binary (and perf,
  unfortunately, doesn't complain about it).

  Make sure binutils is not installed, or move away the objdump binary:

  # mv /usr/bin/objdump /usr/bin/objdump.foo

  Run a perf session and write down all events:

  # perf record -a -- sleep 10

  # perf report

  selct a kernel function, press 'Annotate', a blank screen will appears
  (instead of the assembly code).

  Now put the objdump binary back (or install binutils):

  # mv /usr/bin/objdump.foo /usr/bin/objdump

  and run again perf report:

  # perf report

  select a kernel function, annotate, the disassembly will show up.

  Fix:

  Make binutils a Depends in SRCPKGNAME-tools-PKGVER-ABINUM - see the
  attached patch.

  How to test:

  Install a patched linux-tools-PKGVER-ABINUM.deb package: it will
  require binutils.

  Regression:

  We are adding a new dependency on a package, so code wise there's no
  regression potential - on the other hand, image creation, or
  development environment will experience a slight increase in size
  (1.8MB on x86-64 and 2.1M on arm64) if they didn't install binutils
  already.

  --

  Running zesty 4.10.0-13-generic kernel and running:
  $ perf record

  followed by

  $ perf report

  results in output that can't be annotated (even when run as root). The 
following message appears:
  Couldn't annotate do_io_submit:
  No vmlinux file with build id 81ba79d482fa9e3ea58486de8f119b27fe6db55e
  was found in the path.

  Note that annotation using /proc/kcore requires CAP_SYS_RAWIO
  capability.

  Please use:

  perf buildid-cache -vu vmlinux

  Note this is being run as root and /proc/kcore is accessible with dd from the 
same shell:
  $ dd if=/proc/kcore bs=8 count=16 | hexdump
  000 457f 464c 0102 0001    
  010 0004 00b7 0001     
  020 0040       
  030   0040 0038 0003   
  040 0004    00e8   

  Additionally, installing the linux-image-4.10.0-13-generic-dbgsym
  actually hurts the situation because the symbol addresses in the
  dbgsym don't match the kernel addresses.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675949/+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 1809843] Re: sky2 ethernet card link not up after suspend

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  sky2 ethernet card link not up after suspend

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released

Bug description:
  Issue is as described by the user 'kris' in #1798921
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921).

  Sometimes when bringing my laptop up from suspended state my Ethernet
  card shows link connection and activity via port LEDs but ethtool
  indicates the link is not up. This does not happen every time I resume
  from suspend, about one in 5 times. When it does happen, the following
  additional message is present in my dmesg output:

  [  686.804877] do_IRQ: 1.37 No irq handler for vector

  
  The lspci -vvnn output for the Ethernet card is:

  02:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. 88E8057 
PCI-E Gigabit Ethernet Controller [11ab:4380] (rev 10)
Subsystem: Acer Incorporated [ALI] 88E8057 PCI-E Gigabit Ethernet 
Controller [1025:028e]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/comments/34, in 
the hopes that this specific card will be added to the relevant MSI quirks 
table. If I do not suffer from the same issue as kris in the above linked 
issue, I will be happy to provide any additional information, test fixes etc. I 
would like to avoid using the 'pci=nomsi,noaer' workaround he mentioned if 
possible.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   maridius   2260 F...m pulseaudio
   /dev/snd/controlC0:  maridius   2260 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=0840edd3-6052-4916-bcc2-4c5b13edb862
  InstallationDate: Installed on 2015-09-01 (1212 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Gateway P-79
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=ad05ff21-9786-4f03-8641-85f2f416363d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45+PHC-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/30/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 79.07.00
  dmi.board.name: Godzilla-N10
  dmi.board.vendor: Gateway
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr79.07.00:bd09/30/2009:svnGateway:pnP-79:pvr0100:rvnGateway:rnGodzilla-N10:rvrRev:cvnGateway:ct10:cvrN/A:
  dmi.product.name: P-79
  dmi.product.version: 0100
  dmi.sys.vendor: Gateway

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809843/+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 1810384] Re: 6113077cd319e747875ec71227d2b5cb54e08c76 in btrfs_kernel_fixes failed on B/C/D

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: New => Won't Fix

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

Title:
  6113077cd319e747875ec71227d2b5cb54e08c76  in btrfs_kernel_fixes failed
  on B/C/D

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Won't Fix

Bug description:
  Test failed with disk quota exceeded when trying to create subvolume,
  and error traces could be found in the kernel log.

  This patch exists in the Bionic kernel tree:
  
https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?id=6113077cd319e747875ec71227d2b5cb54e08c76

  Invoking test 6113077cd319e747875ec71227d2b5cb54e08c76

  fix 6113077cd319e747875ec71227d2b5cb54e08c76

  Btrfs: fix missing qgroup reservation before fallocating

  Steps to reproduce:
  mkfs.btrfs 
  mount  
  btrfs quota enable 
  btrfs sub create /subv
  btrfs qgroup limit 10M /subv
  fallocate --length 20M /subv/data

  For the above example, fallocating will return successfully which
  is not expected, we try to fix it by doing qgroup reservation before
  fallocating.

  Create subvolume '/tmp/mnt-6113077cd319e747875ec71227d2b5cb54e08c76/subv'
  fallocate: fallocate failed: Disk quota exceeded

  Found kernel issue:

  [  829.940603] Invoking test 6113077cd319e747875ec71227d2b5cb54e08c76
  [  830.001738] BTRFS: device fsid 134f6701-7984-42bc-affc-e423f4e6c750 devid 
1 transid 5 /dev/loop0
  [  830.005573] BTRFS info (device loop0): disk space caching is enabled
  [  830.005574] BTRFS info (device loop0): has skinny extents
  [  830.005575] BTRFS info (device loop0): flagging fs with big metadata 
feature
  [  830.006375] BTRFS info (device loop0): creating UUID tree
  [  830.038054] BTRFS info (device loop0): qgroup scan completed 
(inconsistency flag cleared)
  [  830.042133] WARNING: CPU: 1 PID: 15933 at 
/build/linux-oem-RkS9Vy/linux-oem-4.15.0/fs/btrfs/extent-tree.c:4433 
btrfs_free_reserved_data_space_noquota+0xcb/0xe0 [btrfs]
  [  830.042133] Modules linked in: btrfs zstd_compress intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass ppdev 
input_leds intel_cstate joydev intel_rapl_perf intel_pch_thermal parport_pc 
ipmi_si parport lpc_ich mac_hid ipmi_devintf ipmi_msghandler sch_fq_codel 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear i915 mgag200 crct10dif_pclmul 
crc32_pclmul ttm ghash_clmulni_intel pcbc igb drm_kms_helper hid_generic 
aesni_intel dca syscopyarea i2c_algo_bit sysfillrect aes_x86_64 sysimgblt 
fb_sys_fops crypto_simd ptp ahci usbhid glue_helper cryptd drm libahci hid 
pps_core video [last unloaded: zstd_compress]
  [  830.042166] CPU: 1 PID: 15933 Comm: fallocate Not tainted 4.15.0-1030-oem 
#35-Ubuntu
  [  830.042167] Hardware name: Intel Corporation S1200RP/S1200RP, BIOS 
S1200RP.86B.03.02.0003.070120151022 07/01/2015
  [  830.042176] RIP: 0010:btrfs_free_reserved_data_space_noquota+0xcb/0xe0 
[btrfs]
  [  830.042177] RSP: 0018:aa474a647d88 EFLAGS: 00010287
  [  830.042178] RAX:  RBX: 0140 RCX: 
0140
  [  830.042178] RDX: 0001 RSI:  RDI: 
8febd2814200
  [  830.042179] RBP: aa474a647db0 R08: 00027fc0 R09: 
c0877688
  [  830.042180] R10: 8feb877f R11: 0001 R12: 
8febd2814200
  [  830.042180] R13: 8feb877f R14: 8feb1ff25f40 R15: 
0140
  [  830.042181] FS:  7f7b7a10c540() GS:8febe084() 
knlGS:
  [  830.042182] CS:  0010 DS:  ES:  CR0: 80050033
  [  830.042183] CR2: 7f7b79f4baa0 CR3: 00045a996004 CR4: 
003606e0
  [  830.042184] DR0:  DR1:  DR2: 

  [  830.042184] DR3:  DR6: fffe0ff0 DR7: 
0400
  [  830.042185] Call Trace:
  [  830.042194]  btrfs_free_reserved_data_space+0x50/0x70 [btrfs]
  [  830.042205]  btrfs_fallocate+0x3f8/0x750 [btrfs]
  [  830.042208]  vfs_fallocate+0x144/0x260
  [  830.042209]  SyS_fallocate+0x48/0x80
  [  830.042211]  do_syscall_64+0x73/0x130
  [  830.042214]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [  830.042215] RIP: 0033:0x7f7b79c13857
  [  830.042215] RSP: 002b:7ffc1ad01498 EFLAGS: 0246 ORIG_RAX: 
011d
  [  830.042216] RAX: ffda RBX:  RCX: 

[Kernel-packages] [Bug 1812988] Re: ff76b0565523319d7c1c0b51d5a5a8915d33efab in ubuntu_btrfs_kernel_fixes generate kernel traces on Cosmic

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: New => Won't Fix

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

Title:
  ff76b0565523319d7c1c0b51d5a5a8915d33efab in ubuntu_btrfs_kernel_fixes
  generate kernel traces on Cosmic

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-kvm source package in Cosmic:
  Won't Fix

Bug description:
  This issue can only be reproduced on certain HW, node "daedalus"
  (AMD64), "modoc" P8

  And this can only be reproduced when running the whole test suite, it
  will be fine if you just run this test:

Invoking test ff76b0565523319d7c1c0b51d5a5a8915d33efab

fix ff76b0565523319d7c1c0b51d5a5a8915d33efab

Btrfs: Don't allocate inode that is already in use

Due to an off-by-one error, it is possible to reproduce a bug
when the inode cache is used.

The same inode number is assigned twice, the second time this
leads to an EEXIST in btrfs_insert_empty_items().

Create subvolume '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s1'
Create a snapshot of '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s1' 
in '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s2'
Create a snapshot of '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s2' 
in '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s3'

Found kernel issue:

[ 2713.591492] WARNING: CPU: 18 PID: 61234 at fs/btrfs/inode.c:9256 
btrfs_destroy_inode+0x1d7/0x210 [btrfs]
[ 2713.591494] Modules linked in: btrfs zstd_compress nls_iso8859_1 
ipmi_ssif intel_rapl skx_edac nfit x86_pkg_temp_thermal intel_powerclamp joydev 
input_leds coretemp kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel intel_cstate intel_rapl_perf mei_me mei ioatdma ipmi_si dca 
ipmi_devintf ipmi_msghandler acpi_pad acpi_power_meter mac_hid sch_fq_codel 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ast i2c_algo_bit ttm hid_generic 
drm_kms_helper aesni_intel aes_x86_64 syscopyarea usbhid sysfillrect 
crypto_simd hid sysimgblt cryptd fb_sys_fops ahci glue_helper i40e drm lpc_ich 
libahci wmi [last unloaded: zstd_compress]
[ 2713.591577] CPU: 18 PID: 61234 Comm: umount Tainted: GW 
4.18.0-14-generic #15-Ubuntu
[ 2713.591579] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS 
SE5C620.86B.01.00.0412.020920172159 02/09/2017
[ 2713.591611] RIP: 0010:btrfs_destroy_inode+0x1d7/0x210 [btrfs]
[ 2713.591612] Code: d0 31 d2 48 89 83 e0 fe ff ff 49 8b 85 e0 03 00 00 48 
85 c0 0f 94 c2 e9 4c ff ff ff 0f 0b e9 60 fe ff ff 0f 0b e9 67 fe ff ff <0f> 0b 
e9 6e fe ff ff 0f 0b e9 75 fe ff ff 0f 0b e9 7c fe ff ff 0f 
[ 2713.591666] RSP: 0018:a966b0bbfc48 EFLAGS: 00010206
[ 2713.591669] RAX: 90c5bf3e6800 RBX: 90c5e06bbc30 RCX: 

[ 2713.591671] RDX:  RSI:  RDI: 
90c5e06bbc30
[ 2713.591673] RBP: a966b0bbfc78 R08: 0001 R09: 
c08fe101
[ 2713.591674] R10: 90c58aac2510 R11: 0001 R12: 
90c5e06bbcb8
[ 2713.591676] R13: c0972940 R14: 90c5e06bbd88 R15: 
a966b0bbfd48
[ 2713.591679] FS:  7f31837e8080() GS:90c61fa8() 
knlGS:
[ 2713.591681] CS:  0010 DS:  ES:  CR0: 80050033
[ 2713.591682] CR2: 7f3183b70308 CR3: 00080167a002 CR4: 
007606e0
[ 2713.591685] DR0:  DR1:  DR2: 

[ 2713.591686] DR3:  DR6: fffe0ff0 DR7: 
0400
[ 2713.591688] PKRU: 5554
[ 2713.591689] Call Trace:
[ 2713.591702]  destroy_inode+0x3e/0x60
[ 2713.591707]  evict+0x139/0x1a0
[ 2713.591711]  iput+0x148/0x210
[ 2713.591739]  free_fs_root+0x1b/0xc0 [btrfs]
[ 2713.591766]  btrfs_drop_and_free_fs_root+0x7c/0xf0 [btrfs]
[ 2713.591793]  btrfs_free_fs_roots+0xdc/0x170 [btrfs]
[ 2713.591824]  ? __btrfs_sysfs_remove_fsid+0x68/0x70 [btrfs]
[ 2713.591852]  close_ctree+0x10c/0x2d0 [btrfs]
[ 2713.591872]  btrfs_put_super+0x15/0x20 [btrfs]
[ 2713.591878]  generic_shutdown_super+0x72/0x110
[ 2713.591882]  kill_anon_super+0x12/0x20
[ 2713.591904]  btrfs_kill_super+0x18/0x110 [btrfs]
[ 2713.591906]  deactivate_locked_super+0x3a/0x80
[ 2713.591907]  deactivate_super+0x51/0x60
[ 2713.591909]  cleanup_mnt+0x3f/0x70
[ 2713.5919

[Kernel-packages] [Bug 1812988] Re: ff76b0565523319d7c1c0b51d5a5a8915d33efab in ubuntu_btrfs_kernel_fixes generate kernel traces on Cosmic

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux-kvm (Ubuntu Cosmic)
   Status: New => Won't Fix

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

Title:
  ff76b0565523319d7c1c0b51d5a5a8915d33efab in ubuntu_btrfs_kernel_fixes
  generate kernel traces on Cosmic

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-kvm source package in Cosmic:
  Won't Fix

Bug description:
  This issue can only be reproduced on certain HW, node "daedalus"
  (AMD64), "modoc" P8

  And this can only be reproduced when running the whole test suite, it
  will be fine if you just run this test:

Invoking test ff76b0565523319d7c1c0b51d5a5a8915d33efab

fix ff76b0565523319d7c1c0b51d5a5a8915d33efab

Btrfs: Don't allocate inode that is already in use

Due to an off-by-one error, it is possible to reproduce a bug
when the inode cache is used.

The same inode number is assigned twice, the second time this
leads to an EEXIST in btrfs_insert_empty_items().

Create subvolume '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s1'
Create a snapshot of '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s1' 
in '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s2'
Create a snapshot of '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s2' 
in '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s3'

Found kernel issue:

[ 2713.591492] WARNING: CPU: 18 PID: 61234 at fs/btrfs/inode.c:9256 
btrfs_destroy_inode+0x1d7/0x210 [btrfs]
[ 2713.591494] Modules linked in: btrfs zstd_compress nls_iso8859_1 
ipmi_ssif intel_rapl skx_edac nfit x86_pkg_temp_thermal intel_powerclamp joydev 
input_leds coretemp kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel intel_cstate intel_rapl_perf mei_me mei ioatdma ipmi_si dca 
ipmi_devintf ipmi_msghandler acpi_pad acpi_power_meter mac_hid sch_fq_codel 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ast i2c_algo_bit ttm hid_generic 
drm_kms_helper aesni_intel aes_x86_64 syscopyarea usbhid sysfillrect 
crypto_simd hid sysimgblt cryptd fb_sys_fops ahci glue_helper i40e drm lpc_ich 
libahci wmi [last unloaded: zstd_compress]
[ 2713.591577] CPU: 18 PID: 61234 Comm: umount Tainted: GW 
4.18.0-14-generic #15-Ubuntu
[ 2713.591579] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS 
SE5C620.86B.01.00.0412.020920172159 02/09/2017
[ 2713.591611] RIP: 0010:btrfs_destroy_inode+0x1d7/0x210 [btrfs]
[ 2713.591612] Code: d0 31 d2 48 89 83 e0 fe ff ff 49 8b 85 e0 03 00 00 48 
85 c0 0f 94 c2 e9 4c ff ff ff 0f 0b e9 60 fe ff ff 0f 0b e9 67 fe ff ff <0f> 0b 
e9 6e fe ff ff 0f 0b e9 75 fe ff ff 0f 0b e9 7c fe ff ff 0f 
[ 2713.591666] RSP: 0018:a966b0bbfc48 EFLAGS: 00010206
[ 2713.591669] RAX: 90c5bf3e6800 RBX: 90c5e06bbc30 RCX: 

[ 2713.591671] RDX:  RSI:  RDI: 
90c5e06bbc30
[ 2713.591673] RBP: a966b0bbfc78 R08: 0001 R09: 
c08fe101
[ 2713.591674] R10: 90c58aac2510 R11: 0001 R12: 
90c5e06bbcb8
[ 2713.591676] R13: c0972940 R14: 90c5e06bbd88 R15: 
a966b0bbfd48
[ 2713.591679] FS:  7f31837e8080() GS:90c61fa8() 
knlGS:
[ 2713.591681] CS:  0010 DS:  ES:  CR0: 80050033
[ 2713.591682] CR2: 7f3183b70308 CR3: 00080167a002 CR4: 
007606e0
[ 2713.591685] DR0:  DR1:  DR2: 

[ 2713.591686] DR3:  DR6: fffe0ff0 DR7: 
0400
[ 2713.591688] PKRU: 5554
[ 2713.591689] Call Trace:
[ 2713.591702]  destroy_inode+0x3e/0x60
[ 2713.591707]  evict+0x139/0x1a0
[ 2713.591711]  iput+0x148/0x210
[ 2713.591739]  free_fs_root+0x1b/0xc0 [btrfs]
[ 2713.591766]  btrfs_drop_and_free_fs_root+0x7c/0xf0 [btrfs]
[ 2713.591793]  btrfs_free_fs_roots+0xdc/0x170 [btrfs]
[ 2713.591824]  ? __btrfs_sysfs_remove_fsid+0x68/0x70 [btrfs]
[ 2713.591852]  close_ctree+0x10c/0x2d0 [btrfs]
[ 2713.591872]  btrfs_put_super+0x15/0x20 [btrfs]
[ 2713.591878]  generic_shutdown_super+0x72/0x110
[ 2713.591882]  kill_anon_super+0x12/0x20
[ 2713.591904]  btrfs_kill_super+0x18/0x110 [btrfs]
[ 2713.591906]  deactivate_locked_super+0x3a/0x80
[ 2713.591907]  deactivate_super+0x51/0x60
[ 2713.591909]  cleanup_mnt+0x3f/0x70
[ 2713.

[Kernel-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: New => Won't Fix

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

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Won't Fix
Status in systemd source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Won't Fix
Status in systemd source package in Eoan:
  Won't Fix
Status in systemd package in Debian:
  Fix Released

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

  --
  sru template for systemd upload:

  [impact]
  buffer overflow can cause memory corruption; this is seen in failed 
autopkgtests

  [test case]
  see comment 6

  [regression potential]
  the patch is minimal and clearly correct; however the regression potential is 
around invalid/corrupted keys read from the keyring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+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 1821390] Re: apic-split will fail in kvm_units_tests

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux-azure (Ubuntu Cosmic)
   Status: New => Won't Fix

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

Title:
  apic-split will fail in kvm_units_tests

Status in ubuntu-kernel-tests:
  Triaged
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 source package in Xenial:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-aws source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-aws source package in Cosmic:
  Won't Fix
Status in linux-azure source package in Cosmic:
  Won't Fix

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make

  4.) TESTNAME=apic-split TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat
  -smp 2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split

  root@ip-172-31-5-254:/home/ubuntu/kvm-unit-tests# TESTNAME=apic-split 
TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu 
qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel x86/apic.flat -smp 
2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split # -initrd 
/tmp/tmp.ZHQwPUOuLD
  qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
  qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
  enabling apic
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 459000
  cr4 = 20
  apic version: 1050014
  PASS: apic existence
  PASS: xapic id matches cpuid
  PASS: writeable xapic id
  PASS: non-writeable x2apic id
  PASS: sane x2apic id
  PASS: x2apic id matches cpuid
  PASS: correct xapic id after reset
  PASS: apic_disable: Local apic disabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear
  PASS: apic_disable: *0xfee00030: 
  PASS: apic_disable: CR8: 0
  PASS: apic_disable: CR8: f
  PASS: apic_disable: *0xfee00080: 
  PASS: apic_disable: Local apic enabled in xAPIC mode
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: *0xfee00030: 1050014
  PASS: apic_disable: *0xfee00080: 0
  PASS: apic_disable: *0xfee00080: f0
  PASS: apic_disable: Local apic enabled in x2APIC mode
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: *0xfee00030: 
  PASS: apic_disable: CR8: 0
  PASS: apic_disable: CR8: f
  PASS: apic_disable: *0xfee00080: 
  x2apic enabled
  PASS: x2apic enabled to invalid state
  PASS: x2apic enabled to apic enabled
  PASS: x2apic enabled to disabled state
  PASS: disabled to invalid state
  PASS: disabled to x2apic enabled
  PASS: apic enabled to invalid state
  PASS: apicbase: relocate apic
  PASS: apicbase: reserved physaddr bits
  PASS: apicbase: reserved low bits
  PASS: self ipi
  starting broadcast (x2apic)
  PASS: APIC physical broadcast address
  PASS: APIC physical broadcast shorthand
  FAIL: PV IPIs testing
  PASS: nmi-after-sti
  PASS: multiple nmi
  PASS: APIC LVT timer one shot
  starting apic change mode
  PASS: TMICT value reset
  PASS: TMCCT should have a non-zero value
  PASS: TMCCT should have reached 0
  PASS: TMCCT should have a non-zero value
  PASS: TMCCT should not be reset to TMICT value
  PASS: TMCCT should be reset to the initial-count
  PASS: TMCCT should not be reset to init
  PASS: TMCCT should have reach zero
  PASS: TMCCT should stay at zero
  PASS: tsc deadline timer
  PASS: tsc deadline timer clearing
  SUMMARY: 51 tests, 1 unexpected failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821390/+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 1821390] Re: apic-split will fail in kvm_units_tests

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux-aws (Ubuntu Cosmic)
   Status: New => Won't Fix

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

Title:
  apic-split will fail in kvm_units_tests

Status in ubuntu-kernel-tests:
  Triaged
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 source package in Xenial:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-aws source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-aws source package in Cosmic:
  Won't Fix
Status in linux-azure source package in Cosmic:
  Won't Fix

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make

  4.) TESTNAME=apic-split TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat
  -smp 2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split

  root@ip-172-31-5-254:/home/ubuntu/kvm-unit-tests# TESTNAME=apic-split 
TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu 
qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel x86/apic.flat -smp 
2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split # -initrd 
/tmp/tmp.ZHQwPUOuLD
  qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
  qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
  enabling apic
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 459000
  cr4 = 20
  apic version: 1050014
  PASS: apic existence
  PASS: xapic id matches cpuid
  PASS: writeable xapic id
  PASS: non-writeable x2apic id
  PASS: sane x2apic id
  PASS: x2apic id matches cpuid
  PASS: correct xapic id after reset
  PASS: apic_disable: Local apic disabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear
  PASS: apic_disable: *0xfee00030: 
  PASS: apic_disable: CR8: 0
  PASS: apic_disable: CR8: f
  PASS: apic_disable: *0xfee00080: 
  PASS: apic_disable: Local apic enabled in xAPIC mode
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: *0xfee00030: 1050014
  PASS: apic_disable: *0xfee00080: 0
  PASS: apic_disable: *0xfee00080: f0
  PASS: apic_disable: Local apic enabled in x2APIC mode
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: *0xfee00030: 
  PASS: apic_disable: CR8: 0
  PASS: apic_disable: CR8: f
  PASS: apic_disable: *0xfee00080: 
  x2apic enabled
  PASS: x2apic enabled to invalid state
  PASS: x2apic enabled to apic enabled
  PASS: x2apic enabled to disabled state
  PASS: disabled to invalid state
  PASS: disabled to x2apic enabled
  PASS: apic enabled to invalid state
  PASS: apicbase: relocate apic
  PASS: apicbase: reserved physaddr bits
  PASS: apicbase: reserved low bits
  PASS: self ipi
  starting broadcast (x2apic)
  PASS: APIC physical broadcast address
  PASS: APIC physical broadcast shorthand
  FAIL: PV IPIs testing
  PASS: nmi-after-sti
  PASS: multiple nmi
  PASS: APIC LVT timer one shot
  starting apic change mode
  PASS: TMICT value reset
  PASS: TMCCT should have a non-zero value
  PASS: TMCCT should have reached 0
  PASS: TMCCT should have a non-zero value
  PASS: TMCCT should not be reset to TMICT value
  PASS: TMCCT should be reset to the initial-count
  PASS: TMCCT should not be reset to init
  PASS: TMCCT should have reach zero
  PASS: TMCCT should stay at zero
  PASS: tsc deadline timer
  PASS: tsc deadline timer clearing
  SUMMARY: 51 tests, 1 unexpected failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821390/+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 1821390] Re: apic-split will fail in kvm_units_tests

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Incomplete => Won't Fix

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

Title:
  apic-split will fail in kvm_units_tests

Status in ubuntu-kernel-tests:
  Triaged
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 source package in Xenial:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-aws source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-aws source package in Cosmic:
  Won't Fix
Status in linux-azure source package in Cosmic:
  Won't Fix

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make

  4.) TESTNAME=apic-split TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat
  -smp 2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split

  root@ip-172-31-5-254:/home/ubuntu/kvm-unit-tests# TESTNAME=apic-split 
TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu 
qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel x86/apic.flat -smp 
2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split # -initrd 
/tmp/tmp.ZHQwPUOuLD
  qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
  qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
  enabling apic
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 459000
  cr4 = 20
  apic version: 1050014
  PASS: apic existence
  PASS: xapic id matches cpuid
  PASS: writeable xapic id
  PASS: non-writeable x2apic id
  PASS: sane x2apic id
  PASS: x2apic id matches cpuid
  PASS: correct xapic id after reset
  PASS: apic_disable: Local apic disabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear
  PASS: apic_disable: *0xfee00030: 
  PASS: apic_disable: CR8: 0
  PASS: apic_disable: CR8: f
  PASS: apic_disable: *0xfee00080: 
  PASS: apic_disable: Local apic enabled in xAPIC mode
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: *0xfee00030: 1050014
  PASS: apic_disable: *0xfee00080: 0
  PASS: apic_disable: *0xfee00080: f0
  PASS: apic_disable: Local apic enabled in x2APIC mode
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: *0xfee00030: 
  PASS: apic_disable: CR8: 0
  PASS: apic_disable: CR8: f
  PASS: apic_disable: *0xfee00080: 
  x2apic enabled
  PASS: x2apic enabled to invalid state
  PASS: x2apic enabled to apic enabled
  PASS: x2apic enabled to disabled state
  PASS: disabled to invalid state
  PASS: disabled to x2apic enabled
  PASS: apic enabled to invalid state
  PASS: apicbase: relocate apic
  PASS: apicbase: reserved physaddr bits
  PASS: apicbase: reserved low bits
  PASS: self ipi
  starting broadcast (x2apic)
  PASS: APIC physical broadcast address
  PASS: APIC physical broadcast shorthand
  FAIL: PV IPIs testing
  PASS: nmi-after-sti
  PASS: multiple nmi
  PASS: APIC LVT timer one shot
  starting apic change mode
  PASS: TMICT value reset
  PASS: TMCCT should have a non-zero value
  PASS: TMCCT should have reached 0
  PASS: TMCCT should have a non-zero value
  PASS: TMCCT should not be reset to TMICT value
  PASS: TMCCT should be reset to the initial-count
  PASS: TMCCT should not be reset to init
  PASS: TMCCT should have reach zero
  PASS: TMCCT should stay at zero
  PASS: tsc deadline timer
  PASS: tsc deadline timer clearing
  SUMMARY: 51 tests, 1 unexpected failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821390/+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 1821537] Re: Enable kernel options CONFIG_EARLY_PRINTK_USB_XDBC and USB_XHCI_DBGCAP for serial Superspeed(+) connections with kernels >= 4.16

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Confirmed => Won't Fix

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

Title:
  Enable kernel options CONFIG_EARLY_PRINTK_USB_XDBC and USB_XHCI_DBGCAP
  for serial Superspeed(+) connections with kernels >= 4.16

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  Since kernel 4.13 Linux supports an USB debug console with passive USB 3.x 
host-to-host cables aka "USB 3.0 super-speed A-to-A debugging cable".
  Beginning with kernel 4.16 a serial port (/dev/ttyDbC) has been added 
(https://www.kernel.org/doc/html/v4.16/driver-api/usb/usb3-debug-port.html#serial-tty).

  I suggest to enable USB DbC by enabling the kernel options
  "CONFIG_EARLY_PRINTK_USB_XDBC=Y" and "USB_XHCI_DBGCAP=Y" in Ubuntu
  kernels >= 4.16 for Bionic HWE and newer ubuntu versions.

  It would also be great to get feedback about line speed from others as
  USB_XHCI_DBGCAP serial ports could be used for network connections via
  tun/tap devices or PPP/SLIP.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821537/+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 1822682] Re: nvidia driver issues

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux-firmware (Ubuntu Cosmic)
   Status: Confirmed => Won't Fix

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

Title:
  nvidia driver issues

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-signed-hwe package in Ubuntu:
  Confirmed
Status in linux-firmware source package in Bionic:
  Confirmed
Status in linux-signed-hwe source package in Bionic:
  Confirmed
Status in linux-firmware source package in Cosmic:
  Won't Fix
Status in linux-signed-hwe source package in Cosmic:
  Won't Fix

Bug description:
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Kernel: Linux 4.18.0-15-generic
  Intel Core i7-7700HQ + GeForce 1050Ti
  after: sudo update-initramfs -u (i'm using this command after installing 
fresh Ubuntu because it can't reboot correctly)
  I get :
  update-initramfs: Generating /boot/initrd.img-4.18.0-16-generic
  W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/image.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/desc.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/nvdec/scrubber.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_method_init.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_bundle_init.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_nonctx.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_ctx.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_data.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_inst.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_data.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_inst.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_unload.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/unload_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/bl.bin for module 
nouveau

  Had no such trouble on Ubuntu 18.04.01 with older kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  2 00:18:33 2019
  InstallationDate: Installed on 2019-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1822682/+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 1822682] Re: nvidia driver issues

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux-signed-hwe (Ubuntu Cosmic)
   Status: Confirmed => Won't Fix

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

Title:
  nvidia driver issues

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-signed-hwe package in Ubuntu:
  Confirmed
Status in linux-firmware source package in Bionic:
  Confirmed
Status in linux-signed-hwe source package in Bionic:
  Confirmed
Status in linux-firmware source package in Cosmic:
  Won't Fix
Status in linux-signed-hwe source package in Cosmic:
  Won't Fix

Bug description:
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Kernel: Linux 4.18.0-15-generic
  Intel Core i7-7700HQ + GeForce 1050Ti
  after: sudo update-initramfs -u (i'm using this command after installing 
fresh Ubuntu because it can't reboot correctly)
  I get :
  update-initramfs: Generating /boot/initrd.img-4.18.0-16-generic
  W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/image.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/desc.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/nvdec/scrubber.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_method_init.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_bundle_init.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_nonctx.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_ctx.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_data.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_inst.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_data.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_inst.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_unload.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/unload_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/bl.bin for module 
nouveau

  Had no such trouble on Ubuntu 18.04.01 with older kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  2 00:18:33 2019
  InstallationDate: Installed on 2019-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1822682/+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 1827750] Re: Not boot with EFI

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux-raspi2 (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1827750

Title:
  Not boot with EFI

Status in linux-raspi2 package in Ubuntu:
  Fix Released
Status in linux-raspi2 source package in Bionic:
  Fix Released
Status in linux-raspi2 source package in Cosmic:
  Won't Fix
Status in linux-raspi2 source package in Disco:
  Fix Released

Bug description:
  Impact:

  The linux-raspi2 kernel doesn't have the necessary UEFI hooks to boot
  on a UEFI enabled system.

  Fix:

  Enable the relevant UEFI options (see the attached patch).

  How to test:

  On a patched kernel, UEFI presence will be check during boot:

  $ dmesg | grep -i eufi
  ...
  [0.00] efi: UEFI not found.
  ...

  Regression potential:

  Very low, some config option changes that have been enabled in generic
  for a long while.

  --

  Hello. I can't boot with linux-raspi2 kernel, but linux-generic work fine. 
Please add support kernel option CONFIG_U(EFI)_STUB=y as default.
  Thanks.

  os: ubuntu 18.04 lts arm64
  hw: raspberry pi 3b (+ tiano core uefi)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1827750/+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 1828868] Re: crashdump fails on HiSilicon D06

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  crashdump fails on HiSilicon D06

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact]
  The crashdump kernel fails to boot on HiSilicon D06, and likely other SMMUv3 
ARM systems.

  [Test Case]
  sudo apt install linux-crashdump
  Adjust crashkernel= parameter in /etc/default/grub.d/kdump-tools.cfg as 
appropriate (for D06, crashkernel=512M)
  Add "arm_smmu_v3.disable_bypass=1" to the kernel command line
  sudo reboot (needed to add crashkernel= param)
  echo 1 | sudo tee /proc/sys/kernel/sysrq
  echo c | sudo tee /proc/sysrq-trigger

  (Note to self - the following is needed on our systems w/ Mellanox adapters:
  ubuntu@d06-3:~$ grep blacklist /etc/default/kdump-tools
  KDUMP_CMDLINE_APPEND="nr_cpus=1 systemd.unit=kdump-tools-dump.service 
module_blacklist=mlx5_core")

  [Fix]
  3f54c447df34f iommu/arm-smmu-v3: Don't disable SMMU in kdump kernel

  [Regression Risk]
  Restricted to SMMUv3 arm64-based systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828868/+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 1827555] Re: [ALSA] [PATCH] Headset fixup for System76 Gazelle (gaze14)

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  [ALSA] [PATCH] Headset fixup for System76 Gazelle (gaze14)

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-hwe source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-hwe source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Fix Released
Status in linux-hwe source package in Disco:
  Invalid

Bug description:
  [Impact]

   * On the System76 Gazelle (gaze14), there is a headset microphone
  input attached to 0x1a that does not have a jack detect. In order to
  get it working, the pin configuration needs to be set correctly, and
  the ALC269_FIXUP_HEADSET_MODE_NO_HP_MIC fixup needs to be applied.
  This is identical to the patch already applied for the System76 Darter
  Pro (darp5).

  [Test Case]

   * With the affected hardware, attempt to use a headset with a
  microphone input. There will be no microphone input from the headset
  until applying this patch.

  [Regression Potential]

   * Extremely low, it specifically identifies the affected hardware.

  [Other Info]
   
   * I have attached the patch as it will be applied to upstream Linux.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827555/+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 1829306] Re: ethtool identify command doesn't blink LED on Hi1620 NICs

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  ethtool identify command doesn't blink LED on Hi1620 NICs

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Won't Fix

Bug description:
  [Impact]
  Users cannot use the ethtool --identify command to help them identify a NIC's 
physical port.

  [Test Case]
  sudo ethtool --identify 

  [Fix]
  a93f7fe134543 net: phy: marvell: add new default led configure for m88e151x

  [Regression Risk]
  The fix is restricted to the Hi1620 device and other users of the marvell phy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829306/+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 1829971] Re: leapsec_timer from time test suite in LTP failed

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Confirmed => Won't Fix

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

Title:
  leapsec_timer from time test suite in LTP failed

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  startup='Wed May 22 06:31:53 2019'
  leapsec_timer0  TINFO  :  test start at 2019-05-22 06:31:53.856622309 
+
  leapsec_timer0  TINFO  :  now is 2019-05-22 06:31:53.856669881 +
  leapsec_timer0  TINFO  :  sleep till 2019-05-22 06:31:54.856669881 +
  leapsec_timer0  TINFO  :  now is 2019-05-22 06:31:54.856816976 +
  leapsec_timer0  TINFO  :  hrtimer early expiration is not detected.
  leapsec_timer0  TINFO  :  scheduling leap second 2019-05-23 
00:00:00.0 +
  leapsec_timer0  TINFO  :  setting time to2019-05-22 
23:59:58.0 +
  leapsec_timer0  TINFO  :  2019-05-22 23:59:58.53707 + adjtimex: 
clock synchronized
  leapsec_timer0  TINFO  :  2019-05-22 23:59:58.000551000 + adjtimex: 
clock synchronized
  leapsec_timer0  TINFO  :  2019-05-22 23:59:58.000562000 + adjtimex: 
clock synchronized
  leapsec_timer0  TINFO  :  2019-05-22 23:59:58.000573000 + adjtimex: 
clock synchronized
  leapsec_timer0  TINFO  :  2019-05-22 06:31:55.357792794000 + 
adjtimex: clock synchronized
  leapsec_timer0  TINFO  :  2019-05-22 06:31:55.857973509000 + 
adjtimex: clock synchronized
  leapsec_timer0  TINFO  :  2019-05-22 06:31:56.358310277000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:31:56.858497565000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:31:57.358805606000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:31:57.858979489000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:31:58.359273808000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:31:58.859578599000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:31:59.35991891 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:31:59.860337395000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:00.360649484000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:00.860978405000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:01.361204884000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:01.861541113000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:02.361747253000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:02.862023631000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:03.362200035000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:03.862509446000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:04.362935772000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:04.863223244000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:05.36346277 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:05.863775778000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:06.364008145000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:06.864323759000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:07.364583789000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:07.864877576000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:08.365151603000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:08.865459198000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:09.365717696000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:09.866092913000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:10.366343699000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:10.866947893000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO  :  2019-05-22 06:32:11.367159166000 + 
adjtimex: insert leap second
  leapsec_timer0  TINFO

[Kernel-packages] [Bug 1827972] Re: The noise keeps occurring when Headset is plugged in on a Dell machine

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  The noise keeps occurring when Headset is plugged in on a Dell machine

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Plug in headset
  2. Select Headset mode

  Expected result:
  There is no noise when headset is plugged in

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1827972/+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 1829983] Re: memcg_stat from controllers test suite in LTP failed (hierarchical_memory_limit is 4096, 8192 expected)

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Confirmed => Won't Fix

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

Title:
  memcg_stat from controllers test suite in LTP failed
  (hierarchical_memory_limit is 4096, 8192 expected)

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux source package in Bionic:
  Confirmed
Status in linux-aws source package in Bionic:
  New
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-aws source package in Cosmic:
  Won't Fix

Bug description:
   memcg_stat_test 1 TINFO: Starting test 1
   sh: echo: I/O error
   memcg_stat_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 1 TINFO: Running memcg_process --shm -k 3 -s 135168
   memcg_stat_test 1 TINFO: Warming up pid: 31352
   memcg_stat_test 1 TINFO: Process is still here after warm up: 31352
   memcg_stat_test 1 TPASS: cache is 135168 as expected
   memcg_stat_test 2 TINFO: Starting test 2
   sh: echo: I/O error
   memcg_stat_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 2 TINFO: Running memcg_process --mmap-file -s 135168
   memcg_stat_test 2 TINFO: Warming up pid: 31380
   memcg_stat_test 2 TINFO: Process is still here after warm up: 31380
   memcg_stat_test 2 TPASS: mapped_file is 135168 as expected
   memcg_stat_test 3 TINFO: Starting test 3
   sh: echo: I/O error
   memcg_stat_test 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 3 TINFO: Running memcg_process --mmap-lock1 -s 4096
   memcg_stat_test 3 TINFO: Warming up pid: 31409
   memcg_stat_test 3 TINFO: Process is still here after warm up: 31409
   memcg_stat_test 3 TPASS: unevictable is 4096 as expected
   memcg_stat_test 4 TINFO: Starting test 4
   sh: echo: I/O error
   memcg_stat_test 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 4 TINFO: Running memcg_process --mmap-lock2 -s 4096
   memcg_stat_test 4 TINFO: Warming up pid: 31434
   memcg_stat_test 4 TINFO: Process is still here after warm up: 31434
   memcg_stat_test 4 TPASS: unevictable is 4096 as expected
   memcg_stat_test 5 TINFO: Starting test 5
   sh: echo: I/O error
   memcg_stat_test 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 5 TPASS: hierarchical_memory_limit is 4096 as expected
   memcg_stat_test 6 TINFO: Starting test 6
   sh: echo: I/O error
   memcg_stat_test 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   sh: echo: I/O error
   memcg_stat_test 6 TFAIL: hierarchical_memory_limit is 4096, 8192 expected
   memcg_stat_test 7 TINFO: Starting test 7
   sh: echo: I/O error
   memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 7 TCONF: mem+swap is not enabled
   memcg_stat_test 7 TINFO: Starting test 8
   sh: echo: I/O error
   memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 7 TCONF: mem+swap is not enabled
   tag=memcg_stat stime=1558504742 dur=4 exit=exited stat=33 core=no cu=16 cs=10

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 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:
  CurrentDmesg:
   [14538.862950] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed May 22 07:17:43 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStat

[Kernel-packages] [Bug 1829984] Re: memcg_usage_in_bytes from controllers test suite in LTP failed

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Confirmed => Won't Fix

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

Title:
  memcg_usage_in_bytes from controllers test suite in LTP failed

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux source package in Bionic:
  Confirmed
Status in linux-aws source package in Bionic:
  New
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-aws source package in Cosmic:
  Won't Fix

Bug description:
   startup='Wed May 22 05:59:09 2019'
   memcg_usage_in_bytes_test 1 TINFO: Starting test 1
   sh: echo: I/O error
   memcg_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 
4194304
   memcg_usage_in_bytes_test 1 TINFO: Warming up pid: 31689
   memcg_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 31689
   memcg_usage_in_bytes_test 1 TFAIL: memory.usage_in_bytes is 4202496, 4194304 
expected
   memcg_usage_in_bytes_test 2 TINFO: Starting test 2
   sh: echo: I/O error
   memcg_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_usage_in_bytes_test 2 TCONF: mem+swap is not enabled
   tag=memcg_usage_in_bytes stime=1558504749 dur=1 exit=exited stat=33 core=no 
cu=5 cs=3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 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:
  CurrentDmesg:
   [14538.862950] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed May 22 07:17:43 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829984/+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 1830175] Re: Add support to Comet Lake LPSS

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  Add support to Comet Lake LPSS

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-oem-osp1 source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Fix Released
Status in linux-oem-osp1 source package in Disco:
  Fix Released

Bug description:
  [Impact]
  I2C touchpad doesn't work when it's connected to Comet Lake LPSS, which isn't 
supported.

  [Fix]
  Add CML LPSS PCI IDs to intel-lpss module.

  [Test]
  The I2C touchpad connected to CML LPSS works after applying the patch.

  [Regression Potential]
  None. It's a new device enablement.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1830175/+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 1831065] Re: does not detect headphone when there is no other output devices

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  does not detect headphone when there is no other output devices

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-oem source package in Cosmic:
  Fix Released

Bug description:
  These two patches are already in the kernel-v5.0, so only B and C need
  these two patches.

  [Impact]
  On a Dell machine, there is no other output devices but a headphone
  on it, when plugging headset, the headset-mic can't work.

  [Fix]
  The headphone detection method is buggy, the driver can't detect
  the headphone, then the driver will not initialize for headset-mic,
  after applying these patches, the problem is fixed.

  [Test Case]
  Plug headset and record the sound from headset-mic, it works well.

  [Regression Risk]
  Low. the patch just change the headphone detection function, and the
  function is already in the kernel from 5.0-rc, no bug is reported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1831065/+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 1830587] Re: Reduce NAPI weight in hns driver from 256 to 64

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  Reduce NAPI weight in hns driver from 256 to 64

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Won't Fix

Bug description:
  [Impact]
  We have a warning[1] in dmesg shows hns register napi as weight 256 but not 
recommended. According to this commit[2] we shall use weight 64 as suggested.

  [1] netif_napi_add() called with weight 256
  [2] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=82dc3c63c692b1e1d59378ecee948ac88e034aad

  [Test Case]
  dmesg | grep netif_napi_add

  [Fix]
  commit acb1ce15a61154aa501891d67ebf79bc9ea26818
  Author: Yonglong Liu 
  Date: Thu Apr 4 16:46:43 2019 +0800

  net: hns: Use NAPI_POLL_WEIGHT for hns driver

  When the HNS driver loaded, always have an error print:
  "netif_napi_add() called with weight 256"

  This is because the kernel checks the NAPI polling weights
  requested by drivers and it prints an error message if a driver
  requests a weight bigger than 64.

  So use NAPI_POLL_WEIGHT to fix it.

  Signed-off-by: Yonglong Liu 
  Signed-off-by: Peng Li 
  Signed-off-by: David S. Miller 

  [Regression Risk]
  Only weight for NAPI changed. Lowest regression risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830587/+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 1831840] Re: Support new ums-realtek device

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  Support new ums-realtek device

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-oem source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux-oem source package in Disco:
  Fix Released

Bug description:
  [Impact]
  Realtek storage device uses usb-storage by default. It works but we should 
use ums-realtek to bring more functionality, e.g. enabling/disabling MMC card 
detection.

  [Fix]
  Add its device ID to the driver.

  [Test]
  After this patch applied, we can use enable_mmc module option to control MMC 
detection.

  [Regression Potential]
  Low. The scope is limited to one device, and the driver is quite stable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1831840/+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 1722226] Re: linux-azure: fix systemd ADT test failure

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux-azure (Ubuntu Cosmic)
   Status: New => Won't Fix

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

Title:
  linux-azure: fix systemd ADT test failure

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Won't Fix

Bug description:
  SRU Justification:

  Impact: systemd ADT test case is failing because the required module
  scsi_debug is missing.

  Fix: move scsi_debug to the main linux-image package.

  Testcase: systemd ADT test case should pass.

  
  [1] 
http://people.canonical.com/~kernel/status/adt-matrix/xenial-linux-meta-azure.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/176/+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 1788222] Re: Bugfix for handling of shadow doorbell buffer

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  Bugfix for handling of shadow doorbell buffer

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-gcp package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  This request is to pull in the following patch for NVMe bug from
  https://lore.kernel.org/patchwork/patch/974880/ in the linux-gcp
  kernel:

  ===
  This patch adds full memory barrier into nvme_dbbuf_update_and_check_event
  function to ensure that the shadow doorbell is written before reading
  EventIdx from memory. This is a critical bugfix for initial patch that
  added support for shadow doorbell into NVMe driver[...].

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788222/+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 1792205] Re: CONFIG_BCH_CONST_PARAMS should be unset

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  CONFIG_BCH_CONST_PARAMS should be unset

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  Quoting lib/bch.c:

   * Option CONFIG_BCH_CONST_PARAMS can be used to force fixed values of
   * parameters m and t; thus allowing extra compiler optimizations and 
providing
   * better (up to 2x) encoding performance. Using this option makes sense when
   * (m,t) are fixed and known in advance, e.g. when using BCH error correction
   * on a particular NAND flash device.

  Ubuntu's kernel targets generic hardware, so using this option is not
  a good idea.

  As a result of this option being enabled, nandsim's option "bch" is
  unusable:

  [34200.137521] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB 
size: 64
  [34200.137522] [nandsim] using 8-bit/512 bytes BCH ECC
  [34200.137524] bch encoder/decoder was configured to support parameters m=14, 
t=4 only!

  ---

  Ubuntu 18.04.1 LTS, linux-image-4.15.0-34-generic: 4.15.0-34.37
  (amd64)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792205/+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 1792387] Re: Single arch and single flavour kernels ship an unordered config file

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: In Progress => Won't Fix

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

Title:
  Single arch and single flavour kernels ship an unordered config file

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  Single arch and single flavour kernels, such as the cloud kernels, are
  currently shipping a config file (that is installed under /boot) that
  is not properly ordered as the ones generated the master kernels.

  The problem occurs because `make silendoldconfig` in
  "debian/rules.d/2-binary-arch.mk" does not re-writes the config file
  (and thus does not sort it) when no changes are made.

  Although cloud kernels and other custom kernels are affected, the
  master kernels are the correct place to fix the problem. The custom
  kernels will inherit the fix automatically when rebased.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792387/+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 1793461] Re: Improvements to the kernel source package preparation

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux-hwe-edge (Ubuntu Cosmic)
   Status: New => Won't Fix

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

Title:
  Improvements to the kernel source package preparation

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-edge package in Ubuntu:
  New
Status in linux source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  New
Status in linux source package in Bionic:
  Fix Released
Status in linux-hwe-edge source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released
Status in linux-hwe-edge source package in Cosmic:
  Won't Fix

Bug description:
  We need to improve the automation of the process that we use to
  prepare kernel source packages. That requires changes in both the
  tooling and in the kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793461/+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 1794293] Re: Please include hid-bigbenff.c driver for 18.04 and later kernels

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Triaged => Won't Fix

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

Title:
  Please include hid-bigbenff.c driver for 18.04 and later kernels

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

Bug description:
  Hi there,

  my driver submission has just been accepted for the upcoming 4.20
  mainline kernel by the input maintainers:

  
https://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git/commit/?h=for-4.20/bigbenff&id=256a90ed9e46b270bbc4e15ef05216ff049c3721

  The BigBen Interactive PS3OFMINIPAD kids' gamepad is a Playstation3
  accessory and was designed for smaller hands. The Linux kernel didn't
  support its rumble effects, so the device's HID protocol needed to be
  reverse-engineered to write this driver.

  I originally wrote this driver for the Raspberry Pi and the Retropie
  software used by my kids. But now that Steam and Proton are here, we
  are using our Ubuntu boxes more and more often for gaming, so
  including this driver in the default kernel would be nice.

  The patch applies cleanly on the kernels of 18.04 and 18.10 with no
  changes, so there's no backporting to do.

  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794293/+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 1796130] Re: Patches for Additional NVME Support

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Triaged => Won't Fix

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

Title:
  Patches for  Additional NVME Support

Status in The Dell-poweredge project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  Dell is requesting these patches for inclusion into 18.04.2 for
  additional NVME support

  PCI: Check for PCIe Link downtraining
  
https://github.com/torvalds/linux/commit/2d1ce5ec2117d16047334a1aa4b62e0cfb5a0605

  
  PCI/AER: Add sysfs attributes to provide AER stats and breakdown
  https://github.com/torvalds/linux/commit/81aa5206f9a7

  
  PCI/AER: Honor "pcie_ports=native" even if HEST sets FIRMWARE_FIRST
  https://github.com/torvalds/linux/commit/7af02fcd84c1

  
  PCI/AER: Don't clear AER bits if error handling is Firmware-First
  https://github.com/torvalds/linux/commit/45687f96c112

  
  PCI: pciehp: Differentiate between surprise and safe removal
  
https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git/commit/?h=pci/hotplug&id=e76ac5875f5d5848558edc79a0869bf20765fec3

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1796130/+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 1797154] Re: arm64: snapdragon: reduce boot noise

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Incomplete => Won't Fix

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

Title:
  arm64: snapdragon: reduce boot noise

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  Impact:

  During boot on a Dragonboard410c using a recent Bionic or Cosmic
  kernel, there's some noise like:

  ...
  [3.665431] msm_dsi_phy 1a98300.dsi-phy: Failed to get supply 'vddio': -517
  [3.669243] msm_dsi_phy 1a98300.dsi-phy: dsi_phy_regulator_init: failed to 
init regulator, ret=-517
  [3.676180] msm_dsi_phy 1a98300.dsi-phy: dsi_phy_driver_probe: failed to 
init regulator
  ...

  or

  ...
  [4.192280] qcom,pm8916-wcd-spmi-codec 200f000.spmi:pm8916@1:codec@f000: 
Failed to get supply 'vdd-cdc-io': -517
  [4.195660] qcom,pm8916-wcd-spmi-codec 200f000.spmi:pm8916@1:codec@f000: 
Failed to get regulator supplies -517
  ...

  and similar.

  This is mainly due to DRM_MSM* and SND_QCOM_MSM* that were built-in,
  and tries to initialize before the voltage regulators are ready to
  work,  resulting in a noisy bootlog.

  These patches factor out some code as modules, so when the kmods are
  loaded and initialized, regulators are already present and ready to
  attach - all these config changes shave around ~3K bytes from dmesg,
  making the bootlog easir to parse.

  Fix:

  Apply the attached patches and recompile

  How to test:

  Boot a patched kernel and check for the above noise in dmesg

  Regression potential:

  None, we are just turning some code into kmods, and turning off a
  couple of not used feature for this flavour - all the other flavours
  are untouched.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797154/+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 1800856] Re: allow kexec_file of unsigned images under lockdown

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: In Progress => Won't Fix

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

Title:
  allow kexec_file of unsigned images under lockdown

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Won't Fix

Bug description:
  [Impact]

  When using kexec -s with an unsigned image, it will fail requiring a
  signed image, even if the system is not under lockdown. kexec without
  the -s option will still work.

  [Test case]
  Tested with kexec -s with both a signed and unsigned image, both under 
lockdown and not under lockdown.

  [Potential Regressions]
  We allow unsigned kernels to be loaded even under lockdown. However, the test 
case has tested that and it still failed. Other regression would be that no 
kernel could be loaded. Also tested under test case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800856/+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 1801305] Re: Restore request-based mode to xen-blkfront for AWS kernels

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  Restore request-based mode to xen-blkfront for AWS kernels

Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux-aws source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux-aws source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux-aws source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-aws source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Won't Fix
Status in linux-aws source package in Disco:
  Fix Released

Bug description:
  In current Ubuntu kernels, PV blkfront drivers have blk-mq enabled by
  default and cannot use the old I/O scheduler.

  [Impact]
  blk-mq is not as fast as the old request-based scheduler for some workloads 
on HDD disks.

  [Fix]
  Amazon Linux has a commit which reintroduces the request-based mode. It 
disables blk-mq by default but allows it to be switched back on with a kernel 
parameter.

  For X this needs a small patch from upstream for error handling.

  For B/C this patchset is bigger as it includes the suspend/resume
  patches already in X, and a new fixup. These are desirable as the
  request mode patch assumes their presence.

  [Regression Potential]
  Could potentially break xen based disks on AWS.

  For B/C, the patches also add some code to the xen core around suspend
  and resume, this code is much smaller and also mirrors code already in
  Xenial.

  [Tests]
  Tested by AWS for Xenial, and their kernel engineers vetted the patches. I 
tested the Bionic and Cosmic patchsets with fio, the system appears stable and 
the IOPS promised for EBS Provisioned IOPS disks were met in my testing. I did 
an apt update/upgrade and everything worked (no hash-sum mismatches).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1801305/+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 1807259] Re: sky2 ethernet card doesn't work after returning from suspend

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  sky2 ethernet card doesn't work after returning from suspend

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released

Bug description:
  I am on "Linux Mint 18.2 Sonya".

  Upgrading to Kernel 4.15.0-39.42~16.04.1 leaves the ethernet adapter
  inactive after resume from suspend. I reverted to a 4.13 kernel for
  this reason for which it works.

  the bug seems to be similar to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921.

  $ lshw -class network
  WARNUNG: Sie sollten dieses Programm mit Systemverwalterrechten (root) 
ausführen.
*-network DEAKTIVIERT
 Beschreibung: Kabellose Verbindung
 Produkt: BCM4312 802.11b/g LP-PHY
 Hersteller: Broadcom Corporation
 Physische ID: 0
 Bus-Informationen: pci@:0c:00.0
 Logischer Name: wlp12s0
 Version: 01
 Seriennummer: 00:26:5e:33:a9:6d
 Breite: 64 bits
 Takt: 33MHz
 Fähigkeiten: bus_master cap_list ethernet physical wireless
 Konfiguration: broadcast=yes driver=wl0 driverversion=6.30.223.271 
(r587334) latency=0 multicast=yes wireless=IEEE 802.11
 Ressourcen: irq:17 memory:f69fc000-f69f
*-network
 Beschreibung: Ethernet interface
 Produkt: 88E8040 PCI-E Fast Ethernet Controller
 Hersteller: Marvell Technology Group Ltd.
 Physische ID: 0
 Bus-Informationen: pci@:09:00.0
 Logischer Name: enp9s0
 Version: 13
 Seriennummer: 00:25:64:4a:26:00
 Größe: 100Mbit/s
 Kapazität: 100Mbit/s
 Breite: 64 bits
 Takt: 33MHz
 Fähigkeiten: bus_master cap_list ethernet physical tp 10bt 10bt-fd 
100bt 100bt-fd autonegotiation
 Konfiguration: autonegotiation=on broadcast=yes driver=sky2 
driverversion=1.30 duplex=full ip=192.168.1.7 latency=0 link=yes multicast=yes 
port=twisted pair speed=100Mbit/s
 Ressourcen: irq:24 memory:f68fc000-f68f ioport:de00(Größe=256)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807259/+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 1806845] Re: The unsigned vf->num_mac will be decreased to below zero and cause the VF port not working

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: New => Won't Fix

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

Title:
  The unsigned vf->num_mac will be decreased to below zero and cause the
  VF port not working

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  The unsigned vf->num_mac in Ubuntu18.04.1 LTS i40e driver 2.1.14-k
  will be decreased to below zero when VF is trying to delete the MAC
  address which is added by PF and then add a new MAC address. And after
  this issue happens, VF won't be able to send/receive packets, and
  excepting for broadcast address, mac_filter_hash is empty in dumped
  VSI info.

  Ubuntu18.04.1 LTS kernel: 4.15.0-38-generic
  i40e driver: 2.1.14-k
  i40evf driver: 3.0.1-k

  Actual results:
  The unsigned vf->num_mac should decrease to below zero. The VF port doesn't 
work.

  Expected results:
  The unsigned vf->num_mac range is from 0 to 65535;
  or the vf is not allowed to delete the MAC addr which is added by PF

  Corresponding Patch is required for resolving this i40e driver issue

  i40e: Prevent deleting MAC address from VF when set by PF
  https://patchwork.ozlabs.org/patch/963036/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806845/+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 1809439] Re: cpu_hot_plug test in ubuntu_kernel_selftest failed on X/B/C s390x KVM

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: New => Won't Fix

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

Title:
  cpu_hot_plug test in ubuntu_kernel_selftest failed on X/B/C s390x KVM

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  $ sudo make -C linux/tools/testing/selftests TARGETS=cpu-hotplug run_tests
  make: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests'
  make[1]: Entering directory 
'/home/ubuntu/src/linux/tools/testing/selftests/cpu-hotplug'
  make[1]: Nothing to be done for 'all'.
  make[1]: Leaving directory 
'/home/ubuntu/src/linux/tools/testing/selftests/cpu-hotplug'
  make[1]: Entering directory 
'/home/ubuntu/src/linux/tools/testing/selftests/cpu-hotplug'
  TAP version 13
  selftests: cpu-on-off-test.sh
  
  pid 18238's current affinity mask: 3
  pid 18238's new affinity mask: 1
  CPU online/offline summary:
 Cpus in online state: 0-1
 Cpus in offline state: 2
  Limited scope test: one hotplug cpu
 (leaves cpu in the original state):
 online to offline to online: cpu 1
 offline to online to offline: cpu 2
  ./cpu-on-off-test.sh: line 85: /sys/devices/system/cpu/cpu2/online: No such 
file or directory
  online_cpu_expect_success 2: unexpected fail
  not ok 1..1 selftests:  cpu-on-off-test.sh [FAIL]
  make[1]: Leaving directory 
'/home/ubuntu/src/linux/tools/testing/selftests/cpu-hotplug'
  make: Leaving directory '/home/ubuntu/src/linux/tools/testing/selftests'

  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 s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  Date: Fri Dec 21 10:38:05 2018
  HibernationDevice: RESUME=UUID=caaee9b2-6bc1-4c8e-b26c-69038c092091
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=c7d7bbcb-a039-4ead-abfe-7672dea0add4 
crashkernel=196M
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809439/+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 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: Ubuntu Cosmic
   Status: Confirmed => Won't Fix

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

Title:
  iwlwifi  Intel 8265 firmware crashing on lenovo x1 Gen 6

Status in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in The Bionic Beaver:
  Confirmed
Status in linux-firmware source package in Bionic:
  Fix Released
Status in The Cosmic Cuttlefish:
  Won't Fix
Status in linux-firmware source package in Cosmic:
  Fix Released

Bug description:
  SRU Justification:
  ===
  [Impact]
  repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6.

  [Fix]
  New iwlwifi firmware fix it.

  [Test]
  Bug reporter verified with positive result.

  [Regression Potential]
  Upstream fix, low risk.
  Bug reporter confirms fix.

  
  Original bug report:
  =

  Seeing repeated crashes of the Intel 8265 wireless card on a Lenovo X1
  Gen6.

  Firmware: 36.7596afd4.0

  Dec 13 11:53:36 james-x1 kernel: [  856.840159] wlp2s0: send auth to 
60:38:e0:70:a2:11 (try 1/3)
  Dec 13 11:53:36 james-x1 kernel: [  856.844875] iwlwifi :02:00.0: 
Microcode SW error detected.  Restarting 0x200.
  Dec 13 11:53:36 james-x1 kernel: [  856.845015] iwlwifi :02:00.0: Start 
IWL Error Log Dump:
  Dec 13 11:53:36 james-x1 kernel: [  856.845018] iwlwifi :02:00.0: Status: 
0x0100, count: 6
  Dec 13 11:53:36 james-x1 kernel: [  856.845021] iwlwifi :02:00.0: Loaded 
firmware version: 36.7596afd4.0
  Dec 13 11:53:36 james-x1 kernel: [  856.845024] iwlwifi :02:00.0: 
0x1006 | ADVANCED_SYSASSERT
  Dec 13 11:53:36 james-x1 kernel: [  856.845026] iwlwifi :02:00.0: 
0x02F0 | trm_hw_status0
  Dec 13 11:53:36 james-x1 kernel: [  856.845029] iwlwifi :02:00.0: 
0x | trm_hw_status1
  Dec 13 11:53:36 james-x1 kernel: [  856.845031] iwlwifi :02:00.0: 
0x000248DC | branchlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845034] iwlwifi :02:00.0: 
0x0003A7DA | interruptlink1
  Dec 13 11:53:36 james-x1 kernel: [  856.845036] iwlwifi :02:00.0: 
0x | interruptlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845039] iwlwifi :02:00.0: 
0xFEDA | data1
  Dec 13 11:53:36 james-x1 kernel: [  856.845041] iwlwifi :02:00.0: 
0xDEADBEEF | data2
  Dec 13 11:53:36 james-x1 kernel: [  856.845044] iwlwifi :02:00.0: 
0xDEADBEEF | data3
  Dec 13 11:53:36 james-x1 kernel: [  856.845046] iwlwifi :02:00.0: 
0x0007E1DC | beacon time
  Dec 13 11:53:36 james-x1 kernel: [  856.845048] iwlwifi :02:00.0: 
0x003B0850 | tsf low
  Dec 13 11:53:36 james-x1 kernel: [  856.845051] iwlwifi :02:00.0: 
0x | tsf hi
  Dec 13 11:53:36 james-x1 kernel: [  856.845053] iwlwifi :02:00.0: 
0x | time gp1
  Dec 13 11:53:36 james-x1 kernel: [  856.845055] iwlwifi :02:00.0: 
0x003B0852 | time gp2
  Dec 13 11:53:36 james-x1 kernel: [  856.845058] iwlwifi :02:00.0: 
0x0001 | uCode revision type
  Dec 13 11:53:36 james-x1 kernel: [  856.845060] iwlwifi :02:00.0: 
0x0024 | uCode version major
  Dec 13 11:53:36 james-x1 kernel: [  856.845063] iwlwifi :02:00.0: 
0x7596AFD4 | uCode version minor
  Dec 13 11:53:36 james-x1 kernel: [  856.845065] iwlwifi :02:00.0: 
0x0230 | hw version
  Dec 13 11:53:36 james-x1 kernel: [  856.845068] iwlwifi :02:00.0: 
0x18489000 | board version
  Dec 13 11:53:36 james-x1 kernel: [  856.845070] iwlwifi :02:00.0: 
0x0501001C | hcmd
  Dec 13 11:53:36 james-x1 kernel: [  856.845072] iwlwifi :02:00.0: 
0x00023008 | isr0
  Dec 13 11:53:36 james-x1 kernel: [  856.845075] iwlwifi :02:00.0: 
0x000D | isr1
  Dec 13 11:53:36 james-x1 kernel: [  856.845077] iwlwifi :02:00.0: 
0x08001802 | isr2
  Dec 13 11:53:36 james-x1 kernel: [  856.845080] iwlwifi :02:00.0: 
0x0041FDC0 | isr3
  Dec 13 11:53:36 james-x1 kernel: [  856.845082] iwlwifi :02:00.0: 
0x | isr4
  Dec 13 11:53:36 james-x1 kernel: [  856.845084] iwlwifi :02:00.0: 
0x00580118 | last cmd Id
  Dec 13 11:53:36 james-x1 kernel: [  856.845087] iwlwifi :02:00.0: 
0x | wait_event
  Dec 13 11:53:36 james-x1 kernel: [  856.845089] iwlwifi :02:00.0: 
0x76DD | l2p_control
  Dec 13 11:53:36 james-x1 kernel: [  856.845091] iwlwifi :02:00.0: 
0x0020 | l2p_duration
  Dec 13 11:53:36 james-x1 kernel: [  856.845094] iwlwifi :02:00.0: 
0x | l2p_mhvalid
  Dec 13 11:53:36 james-x1 kernel: [  856.845096] iwlwifi :02:00.0: 
0x00A0 | l2p_addr_match
  Dec 13 11:53:36 james-x1 kernel: [  856.845099] iwlwifi :02:00.0: 
0x000D | lmpm_pmg_sel
  Dec 13 11:53:36 james-x1 kernel: [  856.845101] iwlwifi :02:00.0: 
0x22040707 | timestamp
  Dec 13 11:53:36 james-x1 kernel: [  856.845103] 

[Kernel-packages] [Bug 1820075] Re: [Packaging] Improve config annotations check on custom kernels

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux-oracle (Ubuntu Cosmic)
   Status: New => Won't Fix

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

Title:
  [Packaging] Improve config annotations check on custom kernels

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-gcp package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-gcp source package in Xenial:
  New
Status in linux-oracle source package in Xenial:
  New
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-gcp source package in Bionic:
  Fix Released
Status in linux-oracle source package in Bionic:
  New
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-gcp source package in Cosmic:
  Fix Released
Status in linux-oracle source package in Cosmic:
  Won't Fix
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-gcp source package in Disco:
  Won't Fix
Status in linux-oracle source package in Disco:
  Fix Released

Bug description:
  [Impact]

  Currently for custom kernels, it's necessary to keep a separate
  annotations file that often gets out of sync with the corresponding
  file in debian.master/.

  The "debian/scripts/config-check" script can be changed to allow
  additional annotations files to act as overlays over the original
  annotations file, allowing custom kernels to override the policies
  just for the relevant configs.

  The proposal is to add support for an include directive in the
  annotations file so custom kernels can include the annotations file
  from its base kernel and override policies on a config basis.

  [Test Case]

  A kernel build should complete successfully after the change.

  
  [Regression Potential] 

  Low regression potential since that's a change on the build process
  that doesn't affect the final kernel that is built.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1820075/+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 1828084] Re: Kernel modules generated incorrectly when system is localized to a non-English language

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  Kernel modules generated incorrectly when system is localized to a
  non-English language

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released

Bug description:
  When LANG is set to a non-English language with the relevant language
  pack installed, Kbuild's recordmcount.pl script fails to function
  correctly when building out-of-tree kernel modules on architectures
  that do not use the C version of recordmcount (e.g. ppc64le). This can
  result in invalid kernel modules being built.

  This was due to the non-C version of recordmcount relying on parsing
  the output of objdump(1), which can be localized. This is now fixed in
  the linux-kbuild tree with the following commit:

  https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-
  kbuild.git/commit/?h=kbuild&id=7b6954a982e7f60af38b835db52a06afc6e4b84c

  This commit is not in the torvalds/linux.git tree yet, but it would be
  good to backport the change to the Ubuntu kernel, particularly the
  linux-headers packages that are used for building out-of-tree kernel
  modules.

  Steps to Reproduce:
  1. Set LANG to a language other than English (e.g. ja_JP.UTF-8)
  2. Make sure that the correct language pack is installed and that 
localization is working; for example, run a command expected to print an error 
message, like `cp` with no additional arguments.
  3. Install the NVIDIA GPU driver

  Actual results:
  The kernel panics when loading the nvidia-modeset kernel module.

  Expected results:
  The driver should install and load normally.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828084/+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 1832299] Re: Add new sound card PCIID into the alsa driver

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  Add new sound card PCIID into the alsa driver

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-oem source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux-oem source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux-oem source package in Eoan:
  Fix Released

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1832299

  The 0001-xxx.patch is for adding the ICL pciid, it is not in the bionic 
kernel,
  so bionic kernel needs two patches.

  The 0002-xxx.patch is in the upstream from v5.2-rc1, it is needed for
  b/c/d/e.

  [Impact]
  We have some cometlake machines, after installing the bionic kernel, the sound
  can't work at all, we found the sound driver didn't load into the kernel.

  [Fix]
  After add the pciid in the pci_driver, the sound driver can be loaded and 
sound
  worked well.

  [Test Case]
  Boot the system and play sound or record sound, they all worked well

  [Regression Risk]
  Low. Adding new pciid, will not change existing functions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1832299/+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 1829983] Re: memcg_stat from controllers test suite in LTP failed (hierarchical_memory_limit is 4096, 8192 expected)

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux-aws (Ubuntu Cosmic)
   Status: New => Won't Fix

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

Title:
  memcg_stat from controllers test suite in LTP failed
  (hierarchical_memory_limit is 4096, 8192 expected)

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux source package in Bionic:
  Confirmed
Status in linux-aws source package in Bionic:
  New
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-aws source package in Cosmic:
  Won't Fix

Bug description:
   memcg_stat_test 1 TINFO: Starting test 1
   sh: echo: I/O error
   memcg_stat_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 1 TINFO: Running memcg_process --shm -k 3 -s 135168
   memcg_stat_test 1 TINFO: Warming up pid: 31352
   memcg_stat_test 1 TINFO: Process is still here after warm up: 31352
   memcg_stat_test 1 TPASS: cache is 135168 as expected
   memcg_stat_test 2 TINFO: Starting test 2
   sh: echo: I/O error
   memcg_stat_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 2 TINFO: Running memcg_process --mmap-file -s 135168
   memcg_stat_test 2 TINFO: Warming up pid: 31380
   memcg_stat_test 2 TINFO: Process is still here after warm up: 31380
   memcg_stat_test 2 TPASS: mapped_file is 135168 as expected
   memcg_stat_test 3 TINFO: Starting test 3
   sh: echo: I/O error
   memcg_stat_test 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 3 TINFO: Running memcg_process --mmap-lock1 -s 4096
   memcg_stat_test 3 TINFO: Warming up pid: 31409
   memcg_stat_test 3 TINFO: Process is still here after warm up: 31409
   memcg_stat_test 3 TPASS: unevictable is 4096 as expected
   memcg_stat_test 4 TINFO: Starting test 4
   sh: echo: I/O error
   memcg_stat_test 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 4 TINFO: Running memcg_process --mmap-lock2 -s 4096
   memcg_stat_test 4 TINFO: Warming up pid: 31434
   memcg_stat_test 4 TINFO: Process is still here after warm up: 31434
   memcg_stat_test 4 TPASS: unevictable is 4096 as expected
   memcg_stat_test 5 TINFO: Starting test 5
   sh: echo: I/O error
   memcg_stat_test 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 5 TPASS: hierarchical_memory_limit is 4096 as expected
   memcg_stat_test 6 TINFO: Starting test 6
   sh: echo: I/O error
   memcg_stat_test 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   sh: echo: I/O error
   memcg_stat_test 6 TFAIL: hierarchical_memory_limit is 4096, 8192 expected
   memcg_stat_test 7 TINFO: Starting test 7
   sh: echo: I/O error
   memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 7 TCONF: mem+swap is not enabled
   memcg_stat_test 7 TINFO: Starting test 8
   sh: echo: I/O error
   memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 7 TCONF: mem+swap is not enabled
   tag=memcg_stat stime=1558504742 dur=4 exit=exited stat=33 core=no cu=16 cs=10

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 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:
  CurrentDmesg:
   [14538.862950] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed May 22 07:17:43 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus

[Kernel-packages] [Bug 1833065] Re: Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux-oem-osp1 (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Won't Fix
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-hwe source package in Bionic:
  Confirmed
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-firmware source package in Cosmic:
  Fix Released
Status in linux-hwe source package in Cosmic:
  Won't Fix
Status in linux-oem-osp1 source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Won't Fix
Status in linux-firmware source package in Disco:
  Fix Released
Status in linux-hwe source package in Disco:
  Won't Fix
Status in linux-oem-osp1 source package in Disco:
  Fix Released
Status in linux-oem-osp1 source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  Intel Wireless-AC 9560 requires additional driver support as well as new 
firmware blobs to function. Without them iwlwifi cannot correctly recognize the 
device on systems with Comet Lake cpu.

  [Fix]
  These changes are cherry-picked from either mainline kernel or 
backport-iwlwifi. Firmware blob iwlwifi-QuZ-a0-jf-b0-*.ucode is also necessary.

  [Test]
  Verified on hardware 02f0:4234 with fw rev 48.

  [Regression Potential]
  Low. These changes includes only necessary changes to enable Intel 
Wireless-AC 9560.

  == Original Bug Description ==

  Wireless module not detected by the system with the following error
  messages in the log:

  00:14.3 Network controller [0280]: Intel Corporation Device [8086:02f0]
   Subsystem: Intel Corporation Device [8086:4030]
  ...
  [ 4.195232] iwlwifi :00:14.3: enabling device ( -> 0002)
  [ 4.207011] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 
op_mode iwlmvm
  [ 4.286392] iwlwifi :00:14.3: Detected Intel(R) Dual Band Wireless AC 
9560, REV=0x354
  [ 9.355720] iwlwifi :00:14.3: Failed to load firmware chunk!
  [ 9.355722] iwlwifi :00:14.3: iwlwifi transaction failed, dumping 
registers
  [ 9.355723] iwlwifi :00:14.3: iwlwifi device config registers:
  [ 9.355759] iwlwifi :00:14.3: : 02f08086 00100406 0280 
0080 c2218004   
  [ 9.355761] iwlwifi :00:14.3: 0020:    
40308086  00c8  01ff
  [ 9.355761] iwlwifi :00:14.3: iwlwifi device memory mapped registers:
  [ 9.355792] iwlwifi :00:14.3: : 18489004 0040  
    
  [ 9.355793] iwlwifi :00:14.3: 0020: 0011 0c040005 0351 
d5d5 d5d5 d5d5 80008040 001f0040
  [ 9.355822] iwlwifi :00:14.3: Could not load the [0] uCode section
  [ 9.355825] iwlwifi :00:14.3: Failed to start INIT ucode: -110
  [ 9.355827] iwlwifi :00:14.3: Collecting data: trigger 15 fired.
  [ 9.576115] iwlwifi :00:14.3: Failing on timeout while stopping DMA 
channel 8 [0x0bad1122]
  [ 9.588329] iwlwifi :00:14.3: Failed to run INIT ucode: -110

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1833065/+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 1829984] Re: memcg_usage_in_bytes from controllers test suite in LTP failed

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux-aws (Ubuntu Cosmic)
   Status: New => Won't Fix

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

Title:
  memcg_usage_in_bytes from controllers test suite in LTP failed

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux source package in Bionic:
  Confirmed
Status in linux-aws source package in Bionic:
  New
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-aws source package in Cosmic:
  Won't Fix

Bug description:
   startup='Wed May 22 05:59:09 2019'
   memcg_usage_in_bytes_test 1 TINFO: Starting test 1
   sh: echo: I/O error
   memcg_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 
4194304
   memcg_usage_in_bytes_test 1 TINFO: Warming up pid: 31689
   memcg_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 31689
   memcg_usage_in_bytes_test 1 TFAIL: memory.usage_in_bytes is 4202496, 4194304 
expected
   memcg_usage_in_bytes_test 2 TINFO: Starting test 2
   sh: echo: I/O error
   memcg_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_usage_in_bytes_test 2 TCONF: mem+swap is not enabled
   tag=memcg_usage_in_bytes stime=1558504749 dur=1 exit=exited stat=33 core=no 
cu=5 cs=3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 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:
  CurrentDmesg:
   [14538.862950] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed May 22 07:17:43 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829984/+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 1832286] Re: Remote denial of service (resource exhaustion) caused by low Maximum Segment Size values

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: New => Won't Fix

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

Title:
  Remote denial of service (resource exhaustion) caused by low Maximum
  Segment Size values

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Won't Fix

Bug description:
  Jonathan Looney discovered that a remote attacker could cause a denial
  of service (resource exhaustion) via a maliciously crafted TCP session
  that utilizes a low MSS value.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832286/+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 1831751] Re: rtlwifi: aggressive memory leak

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  rtlwifi: aggressive memory leak

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

   * Upstream commit 0a9f8f0a1ba9 "rtlwifi: fix btmpinfo timeout while
  processing C2H_BT_INFO" fixed a timeout message by adding a fast path
  which allowed commands to skip the queue to be processed immediately.
  However, the fast path doesn't free the sk_buff when it completes;
  this results in a memory leak when commands are fast-tracked.

  [Test Case]

   * This was tested in the bug report on a RTL8723BE card. As the
  system is running, a memory leak is observed until it gets to the
  point where a reboot is necessary.

   * The following patch was applied and the ever-increasing memory
  consumption no longer experienced.

  [Regression Potential]

   * This was fixed in Linux 4.20 and participants in both the LP bug
  and the Github issue reports [1] have reported positive test results
  with just this patch applied.

  [1] https://github.com/lwfinger/rtlwifi_new/issues/401

  
  Original bug description follows:
  ---

  Hey, i got a memory leak on Ubuntu 18.04.2 even in console mode (no X/GUI) 
the memory usage grows slowly to take all the available RAM when i let the 
computer running over the night (with just top and irssi), and i have to reboot 
to get things back to normal. I didn't have this problem on Ubuntu 17.10 but i 
was still flooded with message about pci aer taking lots of disk space in the 
logs, but pci=noaer fixed this problem and i had no memory leak.
  The computer is a common laptop: HP Pavilion.

  ---
  Kernel log gets spammed with AERs so owner uses "pci=noaer"; that was briefly 
disabled to capture the AERs.

  Memory seems to be consumed (~6 GB of 8GB) just by leaving PC
  overnight booted just to console (systemd.unit=multi-user.target).

  The memory leak doesn't affect Windows but owner is going to check
  Windows Event Log for signs of AERs being logged.

  ---

  Original suspect of AER is not guilty.

  This turns out to be a bug in the rtlwifi driver where in some rare
  circumstances it fails to free an sk_buf.

  Reporter has been testing a DKMS build of rtlwfi with the fix applied
  and confirms it solves the issue.

  Upstream has the commit. Can we get this cherry-picked into all
  releases?

  commit 8cfa272b0d321160ebb5b45073e39ef0a6ad73f2
  Author: Larry Finger 
  Date:   Sat Nov 17 20:55:03 2018 -0600

  rtlwifi: Fix leak of skb when processing C2H_BT_INFO

  With commit 0a9f8f0a1ba9 ("rtlwifi: fix btmpinfo timeout while processing
  C2H_BT_INFO"), calling rtl_c2hcmd_enqueue() with rtl_c2h_fast_cmd() true,
  the routine returns without freeing that skb, thereby leaking it.

  This issue has been discussed at 
https://github.com/lwfinger/rtlwifi_new/issues/401
  and the fix tested there.

  Fixes: 0a9f8f0a1ba9 ("rtlwifi: fix btmpinfo timeout while processing 
C2H_BT_INFO")
  Reported-and-tested-by: Francisco Machado Magalhães Neto 

  Cc: Francisco Machado Magalhães Neto 
  Cc: Ping-Ke Shih 
  Cc: Stable  # 4.18+
  Signed-off-by: Larry Finger 
  Signed-off-by: Kalle Valo 

  diff --git a/drivers/net/wireless/realtek/rtlwifi/base.c 
b/drivers/net/wireless/realtek/rtlwifi/base.c
  index f4122c8fdd97..ef9b502ce576 100644
  --- a/drivers/net/wireless/realtek/rtlwifi/base.c
  +++ b/drivers/net/wireless/realtek/rtlwifi/base.c
  @@ -2289,6 +2289,7 @@ void rtl_c2hcmd_enqueue(struct ieee80211_hw *hw, struct 
sk_buff *skb)

  if (rtl_c2h_fast_cmd(hw, skb)) {
  rtl_c2h_content_parsing(hw, skb);
  +   kfree_skb(skb);
  return;
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1831751/+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 1833140] Re: hns: fix ICMP6 neighbor solicitation messages discard problem

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  hns: fix ICMP6 neighbor solicitation messages discard problem

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Won't Fix

Bug description:
  [Impact]
  ICMP6 neighbor solicitation messages are discarded.

  [Test Case]
  Regression tested only

  [Fix]
  ea401685a20b5 net: hns: fix unsigned comparison to less than zero
  f058e46855dcb net: hns: fix ICMP6 neighbor solicitation messages discard 
problem

  [Regression Risk]
  Fix is restricted to the hns driver, which is the driver for the nics on the 
Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, 
such as the HiSilicon D05 board.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833140/+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 1833065] Re: Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux-hwe (Ubuntu Cosmic)
   Status: Confirmed => Won't Fix

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

Title:
  Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Won't Fix
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-hwe source package in Bionic:
  Confirmed
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-firmware source package in Cosmic:
  Fix Released
Status in linux-hwe source package in Cosmic:
  Won't Fix
Status in linux-oem-osp1 source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Won't Fix
Status in linux-firmware source package in Disco:
  Fix Released
Status in linux-hwe source package in Disco:
  Won't Fix
Status in linux-oem-osp1 source package in Disco:
  Fix Released
Status in linux-oem-osp1 source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  Intel Wireless-AC 9560 requires additional driver support as well as new 
firmware blobs to function. Without them iwlwifi cannot correctly recognize the 
device on systems with Comet Lake cpu.

  [Fix]
  These changes are cherry-picked from either mainline kernel or 
backport-iwlwifi. Firmware blob iwlwifi-QuZ-a0-jf-b0-*.ucode is also necessary.

  [Test]
  Verified on hardware 02f0:4234 with fw rev 48.

  [Regression Potential]
  Low. These changes includes only necessary changes to enable Intel 
Wireless-AC 9560.

  == Original Bug Description ==

  Wireless module not detected by the system with the following error
  messages in the log:

  00:14.3 Network controller [0280]: Intel Corporation Device [8086:02f0]
   Subsystem: Intel Corporation Device [8086:4030]
  ...
  [ 4.195232] iwlwifi :00:14.3: enabling device ( -> 0002)
  [ 4.207011] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 
op_mode iwlmvm
  [ 4.286392] iwlwifi :00:14.3: Detected Intel(R) Dual Band Wireless AC 
9560, REV=0x354
  [ 9.355720] iwlwifi :00:14.3: Failed to load firmware chunk!
  [ 9.355722] iwlwifi :00:14.3: iwlwifi transaction failed, dumping 
registers
  [ 9.355723] iwlwifi :00:14.3: iwlwifi device config registers:
  [ 9.355759] iwlwifi :00:14.3: : 02f08086 00100406 0280 
0080 c2218004   
  [ 9.355761] iwlwifi :00:14.3: 0020:    
40308086  00c8  01ff
  [ 9.355761] iwlwifi :00:14.3: iwlwifi device memory mapped registers:
  [ 9.355792] iwlwifi :00:14.3: : 18489004 0040  
    
  [ 9.355793] iwlwifi :00:14.3: 0020: 0011 0c040005 0351 
d5d5 d5d5 d5d5 80008040 001f0040
  [ 9.355822] iwlwifi :00:14.3: Could not load the [0] uCode section
  [ 9.355825] iwlwifi :00:14.3: Failed to start INIT ucode: -110
  [ 9.355827] iwlwifi :00:14.3: Collecting data: trigger 15 fired.
  [ 9.576115] iwlwifi :00:14.3: Failing on timeout while stopping DMA 
channel 8 [0x0bad1122]
  [ 9.588329] iwlwifi :00:14.3: Failed to run INIT ucode: -110

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1833065/+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 1833138] Re: Fix occasional boot time crash in hns driver

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  Fix occasional boot time crash in hns driver

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Won't Fix

Bug description:
  [Impact]
  On rare occasions, the hns driver will oops on start-up

  [Test Case]
  Reboot, watch for oops

  [Fix]
  c0b0984426814 net: hns: Fix probabilistic memory overwrite when HNS driver 
initialized

  [Regression Risk]
  Fix is restricted to the hns driver, which is the driver for the nics on the 
Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, 
such as the HiSilicon D05 board

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833138/+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 1833136] Re: use-after-free in hns_nic_net_xmit_hw

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
   use-after-free in hns_nic_net_xmit_hw

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Won't Fix

Bug description:
  [Impact]
  KASAN detected a use-after-free condition, which could lead to memory 
corruption or a crash.

  [Test Case]
  Rebuild kernel w/ CONFIG_KASAN=y, look for errors in dmesg.

  [Fix]
  3a39a12ad364a net: hns: fix KASAN: use-after-free in hns_nic_net_xmit_hw()

  [Regression Risk]
  Fix is restricted to the hns driver, which is the driver for the nics on the 
Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, 
such as the HiSilicon D05 board.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833136/+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 1833147] Re: hns: attempt to restart autoneg when disabled should report error

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  hns: attempt to restart autoneg when disabled should report error

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]
  Asking the driver to restart autonegotiation silently fails when 
autonegotation has been disabled. It should report an error.

  [Test Case]
  sudo ethtool -s ethX autoneg off
  sudo ethtool -r ethX

  [Fix]
  ed29ca8b95925 net: hns: Restart autoneg need return failed when autoneg off

  [Regression Risk]
  Fix is restricted to the hns driver, which is the driver for the nics on the 
Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, 
such as the HiSilicon D05 board.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833147/+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 1833464] Re: Request backports of ceph client commits to bionic kernel

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: New => Won't Fix

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

Title:
  Request backports of ceph client commits to bionic kernel

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Won't Fix

Bug description:
  Customer has run into a few ceph client related issues, which were root 
caused to be resolved by the following kernel commits: 
  
https://github.com/ceph/ceph-client/commit/f42a774a2123e6b29bb0ca296e166d0f089e9113
 
  
https://github.com/ceph/ceph-client/commit/093ea205acd4b047cf5aacabc0c6ffecf198d2a9
 
  Can you please backport these into bionic?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833464/+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 1833637] Re: [SRU][B/B-OEM/B-OEM-OSP-1/C/D/E] Add trackpoint middle button support of 2 new thinpads

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  [SRU][B/B-OEM/B-OEM-OSP-1/C/D/E] Add trackpoint middle button support
  of 2 new thinpads

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Won't Fix

Bug description:
  SRU justification:

  [Impact]
  Trackpoint middle button not reported to kernel.

  [Fix]
  Add these new PNPIDs support in kernel for 2 new thinkpads.

  [Test]
  Verified on hardware. Tests result are good.

  [Regression Potential]
  Low, 2 new PNPID added. No affection to other hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1833637/+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 1836170] Re: cpuhotplug06 in cpuhotplug from ubuntu_ltp failed on C ARM64

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Confirmed => Won't Fix

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

Title:
  cpuhotplug06 in cpuhotplug from ubuntu_ltp failed on C ARM64

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  This issue was only spotted on Moonshot ARM64, probably a test case
  issue:

  <<>>
  incrementing stop
  Name:   cpuhotplug06
  Date:   Thu Jul 11 08:38:03 UTC 2019
  Desc:   Does top work properly when CPU hotplug events occur?

  CPU is 1
  sh: echo: I/O error
  cpuhotplug06 1 TBROK: CPU1 cannot be offlined
   5221 pts/000:00:00 top
  <<>>
  initiation_status="ok"
  duration=1 termination_type=exited termination_id=2 corefile=no
  cutime=2 cstime=1
  <<>>

  Steps to run this test:
git clone --depth=1 https://github.com/linux-test-project/ltp.git
cd ltp; make autotools; ./configure; make; sudo make install
echo "cpuhotplug06 cpuhotplug06.sh -c 1 -l 1" > /tmp/jobs
sudo /opt/ltp/runltp -f /tmp/jobs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-25-generic 4.18.0-25.26
  ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20
  Uname: Linux 4.18.0-25-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 11 06:57 seq
   crw-rw 1 root audio 116, 33 Jul 11 06:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.4
  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:
  Date: Thu Jul 11 08:30:02 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-25-generic N/A
   linux-backports-modules-4.18.0-25-generic  N/A
   linux-firmware 1.175.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  QCA9377 isn't being recognized sometimes

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-oem source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux-oem source package in Disco:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Qualcomm WiFi/Bluetooth may disappear after boot. 

  [Fix]
  Disable USB2 LPM at shutdown phase, to prevent it from lingering in LPM
  L1. Pull back the device to full power before shutdown imitates the
  behavior on Windows.

  [Test] 
  The affected user confimed it fixes the issue.
  I can also confirm that
  a) The power drain in S5 is much lower,
  b) Both WiFi and Bluetooth are always present during reboot stress test.

  [Regression Potential]
  Low. Only a limited number of USB2 devices that support LPM.

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

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

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1364 F pulseaudio
   /dev/snd/seq:usuario1258 F timidity
  CurrentDesktop: XFCE
  Date: Tue Mar 20 14:43:42 2018
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2017-06-13 (279 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_I

[Kernel-packages] [Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Confirmed => Won't Fix

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

Title:
  With kernel 4.13 btrfs scans for devices before all devices have been
  discovered

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  See attached dmesg outputs for booting kernels 4.11.x (working) and
  4.13.x (not working).

  dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
  btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have 
been discovered by the kernel.  The btrfs RAID1 filesystem mounts, and 
everything is good.

  dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
  btrfs scans for devices after only 2 (sda, sdb) of the devices have been 
discovered by the kernel.  The btrfs RAID1 filesystem fails to mount ("failed 
to read the system array: -5").  The remaining 2 devices (sdc, sdd) are 
discovered by the kernel immediately afterward.  At the end of the log, I run 
`btrfs device scan` and mount the filesystem manually.

  Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2015-10-15 (933 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: HP ProLiant MicroServer Gen8
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@ 
rootdelay=10
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  bionic apport-hook-error
  Uname: Linux 4.15.0-20-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: HP
  dmi.bios.version: J06
  dmi.chassis.type: 7
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant MicroServer Gen8
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+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 1747463] Re: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Confirmed => Won't Fix

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

Title:
  kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  There are lots of AMD-Vi logged events and I get irq crashes or acpi
  hangups with a 'normal' boot. I got it to boot by disabling IOMMU in
  the BIOS and adding "iommu=soft" to the kernel booting options in
  grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU which
  could have a performance penalty because it has to copy all the data
  of some PCI devices to sub 4G regions.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  ---
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.

   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1747463/+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 1762385] Re: dell_wmi: Unknown key codes

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  dell_wmi: Unknown key codes

Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * Bogus keycode messages produced by the kernel / user annoyance
   * rfkill keyboard shortcuts not working as intended on some Dell machines

  [Test Case]

   * check that there are no spurious kernel messages about unknown keys
  in journalctl upon RFKill key presses

   * check that RFKill key presses work correctly and kill/restore RF
  capabilities

  [Regression Potential]

   * The change is scoped to particular SKUs and thus should only affect them
   * It is related to matching gsd support, which is in-place on xenial and up

  [Solution]
  Cherrypick upstream commit 
https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f

  [Original Bug report]

  RFKill key produces these messages in kernel log:

  dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed

  This key code is a notification and should be added as KEY_IGNORE
  here:
  https://github.com/torvalds/linux/blob/master/drivers/platform/x86/dell-
  wmi.c#L263

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmig   2737 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 18:09:03 2018
  InstallationDate: Installed on 2018-03-27 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  MachineType: Dell Inc. Inspiron 5379
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic 
root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0C6J64
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5379
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1762385/+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 1763040] Re: Merge the linux-snapdragon kernel into bionic master/snapdragon

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux-meta (Ubuntu Cosmic)
   Status: In Progress => Won't Fix

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

Title:
  Merge the linux-snapdragon kernel into bionic master/snapdragon

Status in linux package in Ubuntu:
  Fix Released
Status in linux-meta package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Released
Status in linux-meta source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-meta source package in Cosmic:
  Won't Fix

Bug description:
  Merge the linux-snapdragon arm64 kernel into a new arm64 bionic master
  flavour called -snapdragon:

  * all the enablement patches came from the qcomlt-4.14 branch [1] and were 
merged in master
  * a new master flavour called -snapdragon was created to accomodate the 
custom config and the 
resulting kernel Image (contrary to the Image.gz kernel file generated by 
generic arm64)

  
  1: http://git.linaro.org/landing-teams/working/qualcomm/kernel.git 
release/qcomlt-4.14

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763040/+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 1766857] Re: [Hyper-V] KVP daemon fails to run scripts

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux-azure (Ubuntu Cosmic)
   Status: Confirmed => Won't Fix

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

Title:
  [Hyper-V] KVP daemon fails to run scripts

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux-azure source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-azure source package in Cosmic:
  Won't Fix

Bug description:
  While testing Bionic daily build with kernel 4.15.0-20-generic we saw
  that there are 2 issues with the KVP daemon:

  1. KVP daemon crash after boot. Opened a different bug for this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779640

  2. After the KVP daemon is being started the following messages
  appear:

  Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: 
/usr/libexec/hypervkvpd/hv_get_dns_info: not found
  Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: 
/usr/libexec/hypervkvpd/hv_get_dhcp_info: not found

  The above binaries are present on the system, but the their actual
  path is /usr/sbin/hv_get_dns_info and /usr/sbin/hv_get_dhcp_info.
  Either the hv_get_dhcp_info and hv_get_dns_info binaries should be
  placed in the location where the daemon is looking for
  (/usr/libexec/hypervkvpd/), or the daemon should be set to search for
  the binaries in the /usr/sbin directory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766857/+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 1766857] Re: [Hyper-V] KVP daemon fails to run scripts

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Confirmed => Won't Fix

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

Title:
  [Hyper-V] KVP daemon fails to run scripts

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux-azure source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-azure source package in Cosmic:
  Won't Fix

Bug description:
  While testing Bionic daily build with kernel 4.15.0-20-generic we saw
  that there are 2 issues with the KVP daemon:

  1. KVP daemon crash after boot. Opened a different bug for this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779640

  2. After the KVP daemon is being started the following messages
  appear:

  Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: 
/usr/libexec/hypervkvpd/hv_get_dns_info: not found
  Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: 
/usr/libexec/hypervkvpd/hv_get_dhcp_info: not found

  The above binaries are present on the system, but the their actual
  path is /usr/sbin/hv_get_dns_info and /usr/sbin/hv_get_dhcp_info.
  Either the hv_get_dhcp_info and hv_get_dns_info binaries should be
  placed in the location where the daemon is looking for
  (/usr/libexec/hypervkvpd/), or the daemon should be set to search for
  the binaries in the /usr/sbin directory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766857/+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 1778323] Re: Touchpad doesn't work in 4.17 or later

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Confirmed => Won't Fix

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

Title:
  Touchpad doesn't work in 4.17 or later

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  Using the builds at http://kernel.ubuntu.com/~kernel-ppa/mainline/ I
  can successfully install and run 4.16.17 (Linux version
  4.16.17-041617-generic (kernel@tangerine) (gcc version 7.3.0 (Ubuntu
  7.3.0-23ubuntu2)) #201806201630 SMP Wed Jun 20 20:32:55 UTC 2018) but
  not 4.17.2 or 4.18-rc1.

  In the later ones, the touchpad does not work after boot and rebooting
  stalls:

  Jun 18 15:42:50 pkxps kernel: [  242.366528] INFO: task systemd-udevd:309 
blocked for more than 120 seconds.
  Jun 18 15:42:50 pkxps kernel: [  242.366540]   Not tainted 
4.17.2-041702-generic #201806160433
  Jun 18 15:42:50 pkxps kernel: [  242.366545] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Jun 18 15:42:50 pkxps kernel: [  242.366551] systemd-udevd   D0   309
273 0x8104
  Jun 18 15:42:50 pkxps kernel: [  242.366558] Call Trace:
  Jun 18 15:42:50 pkxps kernel: [  242.366576]  __schedule+0x291/0x870
  Jun 18 15:42:50 pkxps kernel: [  242.366582]  ? __switch_to_asm+0x34/0x70
  Jun 18 15:42:50 pkxps kernel: [  242.366587]  ? __switch_to_asm+0x40/0x70
  Jun 18 15:42:50 pkxps kernel: [  242.366596]  ? get_work_pool+0x40/0x40
  Jun 18 15:42:50 pkxps kernel: [  242.366602]  schedule+0x2c/0x80
  Jun 18 15:42:50 pkxps kernel: [  242.366609]  schedule_timeout+0x1db/0x360
  Jun 18 15:42:50 pkxps kernel: [  242.366615]  ? __schedule+0x299/0x870
  Jun 18 15:42:50 pkxps kernel: [  242.366623]  ? get_work_pool+0x40/0x40
  Jun 18 15:42:50 pkxps kernel: [  242.366629]  wait_for_completion+0xba/0x140
  Jun 18 15:42:50 pkxps kernel: [  242.366637]  ? wake_up_q+0x80/0x80
  Jun 18 15:42:50 pkxps kernel: [  242.366645]  flush_work+0x127/0x1e0
  Jun 18 15:42:50 pkxps kernel: [  242.366652]  ? 
worker_detach_from_pool+0xa0/0xa0
  Jun 18 15:42:50 pkxps kernel: [  242.31]  __cancel_work_timer+0x131/0x1b0
  Jun 18 15:42:50 pkxps kernel: [  242.39]  
cancel_delayed_work_sync+0x13/0x20
  Jun 18 15:42:50 pkxps kernel: [  242.366676]  
power_supply_unregister+0x37/0xb0
  Jun 18 15:42:50 pkxps kernel: [  242.366682]  
devm_power_supply_release+0x11/0x20
  Jun 18 15:42:50 pkxps kernel: [  242.366692]  release_nodes+0x110/0x1f0
  Jun 18 15:42:50 pkxps kernel: [  242.366701]  devres_release_group+0x7c/0xb0
  Jun 18 15:42:50 pkxps kernel: [  242.366718]  wacom_remove+0xce/0x120 [wacom]
  Jun 18 15:42:50 pkxps kernel: [  242.366733]  hid_device_remove+0x55/0xb0 
[hid]
  Jun 18 15:42:50 pkxps kernel: [  242.366741]  
device_release_driver_internal+0x15b/0x220
  Jun 18 15:42:50 pkxps kernel: [  242.366751]  ? 
__hid_bus_driver_added+0x40/0x40 [hid]
  Jun 18 15:42:50 pkxps kernel: [  242.366760]  ? hid_destroy_device+0x60/0x60 
[hid]
  Jun 18 15:42:50 pkxps kernel: [  242.366766]  device_release_driver+0x12/0x20
  Jun 18 15:42:50 pkxps kernel: [  242.366771]  device_reprobe+0x30/0x50
  Jun 18 15:42:50 pkxps kernel: [  242.366782]  
__hid_bus_reprobe_drivers+0x4b/0x60 [hid]
  Jun 18 15:42:50 pkxps kernel: [  242.366793]  bus_for_each_dev+0x74/0xb0
  Jun 18 15:42:50 pkxps kernel: [  242.366803]  
__hid_bus_driver_added+0x2c/0x40 [hid]
  --
  Jun 18 15:42:50 pkxps kernel: [  242.366859]  ? __vunmap+0x81/0xb0
  Jun 18 15:42:50 pkxps kernel: [  242.366867]  ? _cond_resched+0x19/0x40
  Jun 18 15:42:50 pkxps kernel: [  242.366874]  ? 
kmem_cache_alloc_trace+0xb8/0x1c0
  Jun 18 15:42:50 pkxps kernel: [  242.366883]  ? do_init_module+0x27/0x209
  Jun 18 15:42:50 pkxps kernel: [  242.366892]  do_init_module+0x5f/0x209
  Jun 18 15:42:50 pkxps kernel: [  242.366900]  load_module+0x1987/0x1f10
  Jun 18 15:42:50 pkxps kernel: [  242.366913]  __do_sys_finit_module+0xfc/0x120
  Jun 18 15:42:50 pkxps kernel: [  242.366919]  ? 
__do_sys_finit_module+0xfc/0x120
  Jun 18 15:42:50 pkxps kernel: [  242.366929]  __x64_sys_finit_module+0x1a/0x20
  Jun 18 15:42:50 pkxps kernel: [  242.366936]  do_syscall_64+0x5a/0x120
  Jun 18 15:42:50 pkxps kernel: [  242.366942]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Jun 18 15:42:50 pkxps kernel: [  242.366948] RIP: 0033:0x7f03e2729839
  Jun 18 15:42:50 pkxps kernel: [  242.366952] RSP: 002b:7ffde9a0e588 
EFLAGS: 0246 ORIG_RAX: 0139
  Jun 18 15:42:50 pkxps kernel: [  242.366959] RAX: ffda RBX: 
561aff969a00 RCX: 7f03e2729839
  Jun 18 15:42:50 pkxps kernel: [  242.366963] RDX:  RSI: 
7f03e24080e5 RDI: 0007
  Jun 18 15:42:50 pkxps kernel: [  242.366967] RBP: 7f03e24080e5 R08: 
 R09: 

[Kernel-packages] [Bug 1778486] Re: x86/kvm: fix LAPIC timer drift when guest uses periodic mode

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Confirmed => Won't Fix

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

Title:
  x86/kvm: fix LAPIC timer drift when guest uses periodic mode

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  
  == SRU Justification ==
  This patch fixes a regression introduced by mainline commit
  8003c9ae204e in v4.10.  Without this new patch, OpenBSD guests encounter
  timing issues when running under bionic kernel.

  See also:
  https://www.spinics.net/lists/kvm/msg161311.html

  == Fix ==
  d8f2f498d9ed ("x86/kvm: fix LAPIC timer drift when guest uses periodic mode")

  == Regression Potential ==
  Low.  This fixes a current regression.

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

  
  OpenBSD guests encounter timing issues when running under bionic kernel.

  This issue is actually present since 4.10 and is fixed by:

  https://patchwork.kernel.org/patch/10411125/

  See also

  https://www.spinics.net/lists/kvm/msg161311.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778486/+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 1770862] Re: ASUS GU501GM touchpad not detected

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Triaged => Won't Fix

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

Title:
  ASUS GU501GM touchpad not detected

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

Bug description:
  The touchpad on the new ASUS GU501GM (the junior Zephyrus M that is a
  Best Buy exclusive) does not seem to be detected whatsoever.  Below is
  a printout of "xinput list".  I've also attached output files for
  devices, dmesg, lspci -vnvn, Xorg.0.log, and version.log.  I suspect
  it is an Elantech.  I did manage to get one command to print ELAN120x
  (x being some number).  Alas, I don't remember the command now, and
  none of what I've attached is showing it.  (Sorry, I've had a long
  night of troubleshooting.)  The Windows 10 device manager won't even
  list the brand, even though it's working there.  Still, I am fairly
  confident it's Elan, as that's what ASUS seems to roll with these
  days.

  I've tried various combinations of i8042.* kernel parameters, but to
  no avail.  I've also tried blacklisting i2c_hid.  It's like it thinks
  the touchpad is a keyboard?  I'm on Ubuntu 18.04.  I've tried the
  mainstream kernel 4.16.7, also to no avail.  The latest release
  candidate (#4) for 4.17 would not let me log in past SDDM, and I
  noticed no touchpad miracle while I was in the SDDM login screen.

  If you have any further suggestions of what I could try, I would very
  much appreciate it!  Thanks in advance!

  xinput list:

  ⎡ Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
  ⎜   ↳ ASUSTeK Computer Inc. N-KEY Deviceid=14   [slave  pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouseid=15   [slave  pointer  (2)]
  ⎣ Virtual core keyboard id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
  ↳ Power Button  id=6[slave  keyboard (3)]
  ↳ Asus Wireless Radio Control   id=7[slave  keyboard (3)]
  ↳ Video Bus id=8[slave  keyboard (3)]
  ↳ Video Bus id=9[slave  keyboard (3)]
  ↳ Power Button  id=10   [slave  keyboard (3)]
  ↳ Sleep Button  id=11   [slave  keyboard (3)]
  ↳ ASUSTeK Computer Inc. N-KEY Deviceid=12   [slave  keyboard (3)]
  ↳ ASUSTeK Computer Inc. N-KEY Deviceid=13   [slave  keyboard (3)]
  ↳ USB2.0 HD UVC WebCam: USB2.0 HD   id=16   [slave  keyboard (3)]
  ↳ Asus WMI hotkeys  id=17   [slave  keyboard (3)]
  ↳ AT Translated Set 2 keyboard  id=18   [slave  keyboard (3)]
  ↳ ASUSTeK Computer Inc. N-KEY Deviceid=19   [slave  keyboard (3)]
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mustangsally   1416 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-12 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: ASUSTeK COMPUTER INC. ROG GU501GM
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=899a1b40-3034-4afc-9f21-299d52a753ab ro quiet splash i8042.noloop=1 
i8042.nomux=1 i8042.kbdreset=1 i8042.reset vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/16/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GU501GM.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GU501GM
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGU501GM.301:bd03/16/2018:svnASUSTeKCOMPUTERINC.:pnROGGU501GM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU501GM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG
  dmi.product.name: ROG GU501

[Kernel-packages] [Bug 1778282] Re: 'Precision Track Pad' not detected as input source

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Confirmed => Won't Fix

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

Title:
  'Precision Track Pad' not detected as input source

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  I own the Razer Blade 15 (2018) laptop with the Microsoft Precision
  Track pad, and the 4.16 or the 4.17 kernel was not able to detect the
  track pad.

  I do believe that this is affecting all Razer Blade 15 laptops, due to
  the nature of the issue.

  I tried both the 4.16 and 4.17 kernel, both did not detect the track
  pad. However, the 4.17 kernel didn't work with my WiFi card, so went
  back to 4.16.

  I have included my ~/dmesg, ~/devices, /var/log/Xorg.0.log. Just going 
through it myself, it appears that 'Razer Razer Blade' is sometimes being 
tagged as a mouse ([   326.038] (II) event11 - Razer Razer Blade: is tagged by 
udev as: Mouse). Weird.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 4.16.0-041600-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-22 (3 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 4.18.0-041800rc2-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778282/+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 1790513] Re: kdump-config status - not ready to kdump with v4.18 kernel

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Triaged => Won't Fix

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

Title:
  kdump-config status - not ready to kdump with v4.18 kernel

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

Bug description:
  As part of the makedumpfile autopkgtest, a test is done to make sure one can 
dump the kernel.
  The test executes

  $ kdump-config status

  and expects to find that it is ready to kdump, however it is not.

  The check fails at:
  $ cat /sys/kernel/kexec_crash_loaded

  Previously it was 1, but now it is 0.

  Is this intentional? Do we need to change something in makedumpfile?
  Or is something missing in the kernel?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xnox   9240 F pulseaudio
   /dev/snd/controlC1:  xnox   9240 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  3 17:07:41 2018
  HibernationDevice: RESUME=UUID=2bf263f1-753f-4b2e-92a6-b00381515e0c
  InstallationDate: Installed on 2012-01-12 (2425 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=UUID=6669d411-80c3-41cc-a629-ad84e1ee6854 ro splash crashkernel=384M-:128M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-:128M vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-7-generic N/A
   linux-backports-modules-4.18.0-7-generic  N/A
   linux-firmware1.175
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-06-25 (69 days ago)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F18g
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF18g:bd08/13/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790513/+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 1797296] Re: nouveau lockup

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Triaged => Won't Fix

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

Title:
  nouveau lockup

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

Bug description:
  Oct 10 11:38:30 sun kernel: [17891.545097] nouveau :03:00.0: fifo: 
SCHED_ERROR 0a [CTXSW_TIMEOUT]
  Oct 10 11:38:30 sun kernel: [17891.545109] nouveau :03:00.0: fifo: 
runlist 0: scheduled for recovery
  Oct 10 11:38:30 sun kernel: [17891.545118] nouveau :03:00.0: fifo: 
channel 12: killed
  Oct 10 11:38:30 sun kernel: [17891.545125] nouveau :03:00.0: fifo: engine 
0: scheduled for recovery
  Oct 10 11:38:30 sun kernel: [17891.545563] nouveau :03:00.0: 
systemd-logind[944]: channel 12 killed!
  Oct 10 11:42:24 sun kernel: [18125.788110] INFO: task kworker/u32:0:14726 
blocked for more than 120 seconds.
  Oct 10 11:42:24 sun kernel: [18125.788114]   Tainted: GW 
4.18.0-8-generic #9-Ubuntu
  Oct 10 11:42:24 sun kernel: [18125.788115] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Oct 10 11:42:24 sun kernel: [18125.788117] kworker/u32:0   D0 14726  
2 0x8000
  Oct 10 11:42:24 sun kernel: [18125.788154] Workqueue: events_unbound 
nv50_disp_atomic_commit_work [nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788155] Call Trace:
  Oct 10 11:42:24 sun kernel: [18125.788161]  __schedule+0x29e/0x840
  Oct 10 11:42:24 sun kernel: [18125.788178]  ? nvkm_ioctl_ntfy_get+0x5c/0x80 
[nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788180]  schedule+0x2c/0x80
  Oct 10 11:42:24 sun kernel: [18125.788181]  schedule_timeout+0x258/0x360
  Oct 10 11:42:24 sun kernel: [18125.788197]  ? nvif_object_ioctl+0x47/0x50 
[nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788220]  ? nouveau_bo_rd32+0x2a/0x30 
[nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788242]  ? nv84_fence_read+0x2c/0x30 
[nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788263]  ? 
nouveau_fence_no_signaling+0x2a/0x90 [nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788266]  dma_fence_default_wait+0x1fc/0x260
  Oct 10 11:42:24 sun kernel: [18125.788267]  ? dma_fence_release+0xa0/0xa0
  Oct 10 11:42:24 sun kernel: [18125.788269]  dma_fence_wait_timeout+0x3e/0xf0
  Oct 10 11:42:24 sun kernel: [18125.788275]  
drm_atomic_helper_wait_for_fences+0x3f/0xc0 [drm_kms_helper]
  Oct 10 11:42:24 sun kernel: [18125.788309]  
nv50_disp_atomic_commit_tail+0x78/0x860 [nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788311]  ? __switch_to_asm+0x40/0x70
  Oct 10 11:42:24 sun kernel: [18125.788312]  ? __switch_to_asm+0x34/0x70
  Oct 10 11:42:24 sun kernel: [18125.788333]  
nv50_disp_atomic_commit_work+0x12/0x20 [nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788335]  process_one_work+0x20f/0x3c0
  Oct 10 11:42:24 sun kernel: [18125.788337]  worker_thread+0x34/0x400
  Oct 10 11:42:24 sun kernel: [18125.788339]  kthread+0x120/0x140
  Oct 10 11:42:24 sun kernel: [18125.788340]  ? 
pwq_unbound_release_workfn+0xd0/0xd0
  Oct 10 11:42:24 sun kernel: [18125.788341]  ? kthread_bind+0x40/0x40
  Oct 10 11:42:24 sun kernel: [18125.788343]  ret_from_fork+0x35/0x40
  Oct 10 11:44:25 sun kernel: [18246.620114] INFO: task kworker/u32:0:14726 
blocked for more than 120 seconds.
  Oct 10 11:44:25 sun kernel: [18246.620117]   Tainted: GW 
4.18.0-8-generic #9-Ubuntu
  Oct 10 11:44:25 sun kernel: [18246.620118] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Oct 10 11:44:25 sun kernel: [18246.620120] kworker/u32:0   D0 14726  
2 0x8000
  Oct 10 11:44:25 sun kernel: [18246.620156] Workqueue: events_unbound 
nv50_disp_atomic_commit_work [nouveau]
  Oct 10 11:44:25 sun kernel: [18246.620157] Call Trace:
  Oct 10 11:44:25 sun kernel: [18246.620163]  __schedule+0x29e/0x840
  Oct 10 11:44:25 sun kernel: [18246.620180]  ? nvkm_ioctl_ntfy_get+0x5c/0x80 
[nouveau]
  Oct 10 11:44:25 sun kernel: [18246.620181]  schedule+0x2c/0x80
  Oct 10 11:44:25 sun kernel: [18246.620183]  schedule_timeout+0x258/0x360
  Oct 10 11:44:25 sun kernel: [18246.620197]  ? nvif_object_ioctl+0x47/0x50 
[nouveau]
  Oct 10 11:44:25 sun kernel: [18246.620221]  ? nouveau_bo_rd32+0x2a/0x30 
[nouveau]
  Oct 10 11:44:25 sun kernel: [18246.620242]  ? nv84_fence_read+0x2c/0x30 
[nouveau]
  Oct 10 11:44:25 sun kernel: [18246.620263]  ? 
nouveau_fence_no_signaling+0x2a/0x90 [nouveau]
  Oct 10 11:44:25 sun kernel: [18246.620265]  dma_fence_default_wait+0x1fc/0x260
  Oct 10 11:44:25 sun kernel: [18246.620267]  ? dma_fence_release+0xa0/0xa0
  Oct 10 11:44:25 sun kernel: [18246.620268]  dma_fence_wait_timeout+0x3e/0xf0
  Oct 10 11:44:25 sun kernel: [18246.620274]  
drm_atomic_helper_wait_for_fences+0x3f/0xc0 [drm_kms_helper]
  Oct 10 11

[Kernel-packages] [Bug 1778534] Re: Touchpad not working (Elantech ELAN0618)

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Triaged => Won't Fix

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

Title:
  Touchpad not working (Elantech ELAN0618)

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  For a fresh installed Ubuntu 16 (and 18), touchpad doesn't work for
  Elantech ELAN0618.

  We have modified the struct elan_acpi_id, by adding ELAN0618 to the
  list of the supported models (in the file
  drivers/input/mouse/elan_i2c_core.c from the kernel source)

  static const struct acpi_device_id elan_acpi_id[] = {
{ "ELAN", 0 },
{ "ELAN0100", 0 },
{ "ELAN0600", 0 },
{ "ELAN0602", 0 },
{ "ELAN0605", 0 },
{ "ELAN0608", 0 },
{ "ELAN0605", 0 },
{ "ELAN0609", 0 },
{ "ELAN060B", 0 },
{ "ELAN060C", 0 },
{ "ELAN0611", 0 },
{ "ELAN0618", 0 },
{ "ELAN1000", 0 },
{ }
  };

  and then built the kernel, and our problem solved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778534/+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 1783906] Re: Linux 4.15 and onwards fails to initialize some hard drives

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Confirmed => Won't Fix

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

Title:
  Linux 4.15 and onwards fails to initialize some hard drives

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  I have two hard drives, the main hard drive is a TOSHIBA DT01ACA200
  the second backup hard drive is a Western Digital WD5003AZEX. I
  installed lubuntu 18.04.1 on the Toshiba HDD and it boots just fine,
  the issue is with the second hard drive, when installing the WD HDD
  wouldn't even come as an option to install, and after boot the WD HDD
  still wouldn't come up, this is the dmesg with the stock kernel (4.15)
  https://paste.ubuntu.com/p/kpxh94v2SK/

  ata6 is the WD HDD that refuses to work. The messages:
  [  302.107650] ata6: SError: { CommWake 10B8B Dispar DevExch }
  [  302.107658] ata6: hard resetting link
  [  307.860291] ata6: link is slow to respond, please be patient (ready=0)
  [  312.120898] ata6: COMRESET failed (errno=-16)
  [  363.445120] INFO: task kworker/u8:5:201 blocked for more than 120 seconds.
  [  363.445131]   Not tainted 4.15.0-29-generic #31-Ubuntu
  [  363.445135] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.445140] kworker/u8:5D0   201  2 0x8000
  [  363.445155] Workqueue: events_unbound async_run_entry_fn
  [  363.445157] Call Trace:
  [  363.445171]  __schedule+0x291/0x8a0
  [  363.445177]  schedule+0x2c/0x80
  [  363.445182]  ata_port_wait_eh+0x7c/0xf0
  [  363.445186]  ? wait_woken+0x80/0x80
  [  363.445189]  ata_port_probe+0x28/0x40
  [  363.445192]  async_port_probe+0x2e/0x52
  [  363.445196]  async_run_entry_fn+0x3c/0x150
  [  363.445199]  process_one_work+0x1de/0x410
  [  363.445203]  worker_thread+0x32/0x410
  [  363.445207]  kthread+0x121/0x140
  [  363.445210]  ? process_one_work+0x410/0x410
  [  363.445214]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  363.445218]  ret_from_fork+0x22/0x40

  Repeat constantly. Also when I try to turn off the computer, the
  computer seem to freeze, the lights of the keyboard and mouse turn off
  and the computer just stay on.

  I tried Tiny Core 9.0 which has linux 4.14.10, and i didn't had this
  issue, i also installed linux 4.14 on this lubuntu 18.04 using Ukuu
  Kernel Update Utility. And with this kernel version, or any previous
  version the WD HDD does work again. Here's a dmesg of lubuntu 18.04
  with linux 4.14 and the WD HDD finally coming up at the end:
  https://paste.ubuntu.com/p/Gd3cGFbjTJ/

  Also tried with with linux 4.17 but the WD HDD would also refuse to
  work on this version. Here's another dmesg with this version:
  https://paste.ubuntu.com/p/PmNn96vZZv/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-29-generic 4.15.0-29.31
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-29-generic.
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  testtest756 F pulseaudio
   /dev/snd/controlC1:  testtest756 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'NVidia_1'/'HDA NVidia at 0xfe02 irq 22'
 Mixer name : 'Realtek ALC1200'
 Components : 'HDA:10ec0888,10ec,00100101 
HDA:10de0002,10de0101,0010'
 Controls  : 56
 Simple ctrls  : 21
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xfcffc000 irq 16'
 Mixer name : 'Nvidia GPU 42 HDMI/DP'
 Components : 'HDA:10de0042,38422651,00100100'
 Controls  : 21
 Simple ctrls  : 3
  CurrentDesktop: LXDE
  Date: Thu Jul 26 17:10:58 2018
  HibernationDevice: RESUME=UUID=17e70869-516d-4b63-b900-e92e3c4b73b6
  InstallationDate: Installed on 2018-07-26 (0 days ago)
  InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: 113 1
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=71cf0a32-7827-49be-a2c0-cd50a72c26a1 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: 113-M2-E113
  dmi.board.vendor: EVG

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

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

-- 
You 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
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Screen flickers when using radeon.ko.
  It's a regression, it didn't happen on Trusty.

  [Fix]
  Quote the original commit log:
  "Instead of the closest reference divider prefer the lowest".

  [Test]
  Affected user confirms it fixes the issue.

  [Regression Potential]
  Low. Only affect radeaon, and it's in upstream stable tree.

  === Original Bug Report ===
  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 1794110] Re: MPS (Max Payload Size) is not correctly programmed upon Hot Insertion NVMe PCIe SSD

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  MPS (Max Payload Size) is not correctly programmed upon Hot Insertion
  NVMe PCIe SSD

Status in The Dell-poweredge project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  Max Payload Size for the NVMe device is not getting programmed correctly. 
  The OS is trying to set the device MPS to match Root Port which is greater 
than Capability of Device, instead of looking for lowest common denominator. 

  This is fixed in upstream kernel version 4.19. Below are the commits that fix 
the issue. 
  Please help include them in Ubuntu releases.

  PCI: Skip MPS logic for Virtual Functions (VFs)
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2&id=3dbe97efe8bf450b183d6dee2305cbc032e6b8a4

  PCI: Match Root Port's MPS to endpoint's MPSS as necessary
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2&id=9f0e89359775ee21fe1ea732e34edb52aef5addf

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1794110/+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 1794766] Re: nbd device size not updated correctly

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Confirmed => Won't Fix

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

Title:
  nbd device size not updated correctly

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  nbd does not handle a disk resize correctly. This has been fixed
  upstream:
  
https://github.com/torvalds/linux/commit/639812a1ed9bf49ae2c026086fbf975339cd1eef

  On Ubuntu Bionic with a "4.15.0-34-generic #37-Ubuntu" kernel a resize
  of a (Ceph) rbd image does not propagate to a "rbd-nbd" mapped disk,
  until it's unmapped / remapped. See
  https://tracker.ceph.com/issues/23137. Other "nbd" mapped disks might
  suffer from the same behaviour (not tested).

  Ubuntu mainline kernel (4.19-rc5) works correct with regards to this
  rbd resize rbd-nbd mapped image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794766/+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 1797492] Re: 18.10 - AMD AGESA 1.0.0.4 bios causes kvm_amd to hang on load

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  18.10 -  AMD AGESA 1.0.0.4 bios causes kvm_amd to hang on load

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  Description:  Ubuntu Cosmic Cuttlefish (development branch)
  Release:  18.10

  4.18.0-8-generic #9-Ubuntu SMP Mon Sep 10 16:12:10 UTC 2018 x86_64
  x86_64 x86_64 GNU/Linux

  https://bugzilla.redhat.com/show_bug.cgi?id=1608242

  Looks like's it's fixed in kernel 4.18.10

  This is the patch:

  
https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=3702a0585e64d70d5bf73bf3e943b8d6005b72c1

  Other issues this causes is the systemd-udevd hanging on reboot.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  matt   2179 F pulseaudio
   /dev/snd/controlC0:  matt   2179 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-06 (5 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181004)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=643f18e2-2cd4-4eff-8659-4a4bbe9ecb35 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/03/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: X470 Taichi Ultimate
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/03/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470TaichiUltimate:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797492/+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 1796647] Re: Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  Shared folders cannot be mounted in ubuntu/cosmic64 due to missing
  vbox modules

Status in cloud-images:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  SRU Justification

  Impact: Vagrant environments are no longer able to use virtualbox
  feartures like shared folders. This is due to Ubuntu Cosmic kernels
  currently shipping the upstream vboxguest module and not importing
  modules from the virtualbox-guest-dkms package.

  Fix: One solution would be to use the dkms modules for Vagrant, but
  this is not ideal. At this late stage the simplest solution is to go
  back to importing the out-of-tree modules.

  Regression Potential: Minimal. Will have no impact outside of
  virtualbox environments, and the drivers being imported come from the
  virtualbox-guest-dkms package in cosmic and are thus expected to work
  well.

  ---

  In bionic, the vboxsf module was included in linux-
  modules-...-generic:

  $ dpkg -c linux-modules-4.15.0-36-generic_4.15.0-36.39_amd64.deb | grep 
vboxsf.ko
  -rw-r--r-- root/root 63238 2018-09-24 10:08 
./lib/modules/4.15.0-36-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko

  In cosmic, it isn't:

  $ dpkg -c ~/Downloads/linux-
  modules-4.18.0-9-generic_4.18.0-9.10_amd64.deb | grep vboxsf.ko

  This results in shared folders no longer being mountable in Ubuntu
  Vagrant boxes (and, as the other vbox modules are also missing,
  probably has other effects that haven't yet been reported).

  [Original Report]

  Just tried to test out the new cosmic64 vagrant box and get the
  following error;

  ```
  Vagrant was unable to mount VirtualBox shared folders. This is usually
  because the filesystem "vboxsf" is not available. This filesystem is
  made available via the VirtualBox Guest Additions and kernel module.
  Please verify that these guest additions are properly installed in the
  guest. This is not a bug in Vagrant and is usually caused by a faulty
  Vagrant box. For context, the command attempted was:

  mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant

  The error output from the command was:

  /sbin/mount.vboxsf: mounting failed with the error: No such device
  ```

  I tried with ubuntu/bionic64 and it worked fine.

  I've got;
  $ vagrant version
  Installed Version: 2.1.5
  Latest Version: 2.1.5

  You're running an up-to-date version of Vagrant!
  $ VBoxManage --version
  5.2.18r124319
  $

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1796647/+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 1805360] Re: linux-aws: 4.18.0-1006.7 -proposed tracker

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux-aws (Ubuntu Cosmic)
   Status: Confirmed => Won't Fix

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

Title:
  linux-aws: 4.18.0-1006.7 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow abi-testing series:
  New
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Cosmic:
  Won't Fix

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  flag:
proposed-announcement-sent: true
proposed-testing-requested: true
  kernel-stable-master-bug: 1802743
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Released
  phase-changed: Thursday, 29. November 2018 21:05 UTC
  reason: {}
  ~~:
clamps:
  self: 4.18.0-1006.7
tracker:
  last-message: '2024-07-26 16:48:30.172833+00:00'

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805360/+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 1812413] Re: linux-aws build rules for arm64.mk do not match amd64.mk

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux-aws (Ubuntu Cosmic)
   Status: New => Won't Fix

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

Title:
  linux-aws build rules for arm64.mk do not match amd64.mk

Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Bionic:
  New
Status in linux-aws source package in Cosmic:
  Won't Fix

Bug description:
  The debian.aws/rules.d/*.mk rules file arm64.mk differs from amd64.mk:

  +no_dumpfile = true
   loader   = grub
   vdso = vdso_install
   no_dumpfile  = true
  -uefi_signed = false
   do_tools_usbip  = true
   do_tools_cpupower = true
   do_tools_perf   = true
  -do_tools_x86 = true
  -do_tools_hyperv  = false
  +do_tools_x86   = false
  +do_tools_hyperv= true
   do_extras_package = true
   ship_extras_package = false
  -do_tools_common = false
  -do_tools_acpidbg = false
  +do_tools_common = true
   do_zfs   = true
   do_libc_dev_package = false
   disable_d_i  = true

  These should be reviewed and cleaned up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1812413/+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 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep,
  NVMe drains lots of power under s2idle

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-oem source package in Cosmic:
  Invalid
Status in linux-oem-osp1 source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Fix Released
Status in linux-oem source package in Disco:
  Fix Released
Status in linux-oem-osp1 source package in Disco:
  Fix Released

Bug description:
  It seems that the Dell 9370 is set to go into s2idle mode rather than
  deep sleep, forgoing significant power savings.

  I have confirmed this by suspending and then checking:
  sudo journalctl | grep "PM: suspend" | tail -2. If the output is

  PM: suspend entry (s2idle)
  PM: suspend exit

  cat /sys/power/mem_sleep showed

  [s2idle] deep

  As a temporary fix, I typed 
  echo deep > /sys/power/mem_sleep 
  as a root user (sudo -i). 

  Then the output of cat /sys/power/mem_sleep was
  s2idle [deep]

  After suspending now, 
  sudo journalctl | grep "PM: suspend" | tail -2 returns

  PM: suspend entry (deep)
  PM: suspend exit

  I have made this permanent by editing 
  /etc/default/grub

  and replacing
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
  with
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"

  then regenerating my grub configuration (sudo grub-mkconfig -o
  /boot/grub/grub.cfg).

  This appears to be working with no ill effects.

  Credit to https://askubuntu.com/a/1036122/470077

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron-work   3672 F pulseaudio
   /dev/snd/pcmC0D0p:   aaron-work   3672 F...m pulseaudio
  Date: Tue Dec 18 09:52:44 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1
  InstallationDate: Installed on 2018-09-04 (104 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  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.18.0-11-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep 
vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.175.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-26 (52 days ago)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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