[Kernel-packages] [Bug 1840626] Re: [nvidia] Slowness and sometimes the computer freezes

[Launchpad Bug Tracker]

[Expired for nvidia-graphics-drivers-390 (Ubuntu) because there has been
no activity for 60 days.]

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [nvidia] Slowness and sometimes the computer freezes

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  Since maybe two months, my computer deosn't work correctly. There is
  slowness and sometime the computer freeze.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Aug 19 00:42:31 2019
  DistUpgraded: 2019-02-23 11:53:16,014 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.116, 4.15.0-58-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 5500 [1025:0974]
 Subsystem: Acer Incorporated [ALI] GK208BM [GeForce 920M] [1025:0974]
  InstallationDate: Installed on 2019-02-21 (178 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  MachineType: Acer Aspire E5-772G
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic 
root=UUID=377aa352-9018-46e8-bfee-2799a1be51e6 ro persistent quiet splash 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-02-23 (176 days ago)
  dmi.bios.date: 07/28/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire E5-772G
  dmi.board.vendor: Acer
  dmi.board.version: V1.09
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd07/28/2015:svnAcer:pnAspireE5-772G:pvrV1.09:rvnAcer:rnAspireE5-772G:rvrV1.09:cvnAcer:ct10:cvrV1.09:
  dmi.product.family: BDW
  dmi.product.name: Aspire E5-772G
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Aug 19 00:38:49 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1840626/+subscriptions

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

[Kernel-packages] [Bug 1840626] Re: [nvidia] Slowness and sometimes the computer freezes

[Launchpad Bug Tracker]

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

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [nvidia] Slowness and sometimes the computer freezes

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  Since maybe two months, my computer deosn't work correctly. There is
  slowness and sometime the computer freeze.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Aug 19 00:42:31 2019
  DistUpgraded: 2019-02-23 11:53:16,014 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.116, 4.15.0-58-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 5500 [1025:0974]
 Subsystem: Acer Incorporated [ALI] GK208BM [GeForce 920M] [1025:0974]
  InstallationDate: Installed on 2019-02-21 (178 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  MachineType: Acer Aspire E5-772G
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic 
root=UUID=377aa352-9018-46e8-bfee-2799a1be51e6 ro persistent quiet splash 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-02-23 (176 days ago)
  dmi.bios.date: 07/28/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire E5-772G
  dmi.board.vendor: Acer
  dmi.board.version: V1.09
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd07/28/2015:svnAcer:pnAspireE5-772G:pvrV1.09:rvnAcer:rnAspireE5-772G:rvrV1.09:cvnAcer:ct10:cvrV1.09:
  dmi.product.family: BDW
  dmi.product.name: Aspire E5-772G
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Aug 19 00:38:49 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1840626/+subscriptions

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

[Kernel-packages] [Bug 1842320] Re: Out of Memory on boot with 5.2.0 kernel

[Steven Mackenzie]

Update: My machine boots normally from the USB install media.

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

Title:
  Out of Memory on boot with 5.2.0 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgraded from 19.04 to current 19.10 using "do-release-upgrade -d".
  Can still boot using the previous 5.0.0-25-generic kernel, but the
  5.2.0-15-generic fails to start.

  On selecting Ubuntu from Grub, the message "error: out of memory." is
  immediately shown. Pressing a key attempts to start boot-up but fails
  to mount root fs.

  Machine is HP Spectre X360 with 8GB RAM. Under kernel 5.0.0, free
  shows the following (run from Gnome terminal):

    totalusedfree  shared  buff/cache   
available
  Mem:7906564 1761196 3833240 1020216 2312128 
4849224
  Swap:   1003516   0 1003516

  Kernel packages installed:

  linux-generic  5.2.0.15.16 amd64
  linux-headers-5.2.0-15 5.2.0-15.16 all
  linux-headers-5.2.0-15-generic 5.2.0-15.16 amd64
  linux-headers-generic  5.2.0.15.16 amd64
  linux-image-5.0.0-25-generic   5.0.0-25.26 amd64
  linux-image-5.2.0-15-generic   5.2.0-15.16+signed1 amd64
  linux-image-generic5.2.0.15.16 amd64
  linux-modules-5.0.0-25-generic 5.0.0-25.26 amd64
  linux-modules-5.2.0-15-generic 5.2.0-15.16 amd64
  linux-modules-extra-5.0.0-25-generic   5.0.0-25.26 amd64
  linux-modules-extra-5.2.0-15-generic   5.2.0-15.16 amd64

  Photo of kernel panic attached.

  NVMe drive partition layout (GPT):

  Device   StartEnd   Sectors   Size Type
  /dev/nvme0n1p120481050623   1048576   512M EFI System
  /dev/nvme0n1p2 10506242549759   1499136   732M Linux filesystem
  /dev/nvme0n1p3 2549760 1000214527 997664768 475.7G Linux filesystem

  $ sudo pvs
    PV  VGFmt  Attr PSizePFree
    /dev/mapper/nvme0n1p3_crypt ubuntu-vg lvm2 a--  <475.71g0

  $ sudo lvs
    LV VGAttr   LSize   Pool Origin Data%  Meta%  Move Log 
Cpy%Sync Convert
    root   ubuntu-vg -wi-ao 474.75g
    swap_1 ubuntu-vg -wi-ao 980.00m

  Partition 3 is LUKS encrypted. Root LV is ext4.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gmckeown   1647 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-08-15 (18 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd HP Wide Vision 
FHD Camera
   Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-25-generic N/A
   linux-backports-modules-5.0.0-25-generic  N/A
   linux-firmware1.181
  Tags:  eoan
  Uname: Linux 5.0.0-25-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-02 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/17/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.43
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.25:bd05/17/2019:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.43:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.product.sku: 2QH38EA#ABU
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1848894] Re: Intel(R) Dual Band Wireless AC 8265 doesn't work on Disco

[You-Sheng Yang]

You may also want to install backport-iwlwifi dkms[1] on Disco instead.

[1]: https://launchpad.net/~vicamo/+archive/ubuntu/backport-iwlwifi-dkms

** Summary changed:

- Intel(R) Dual Band Wireless AC 8265 doesn't work on Disco
+ Intel(R) Dual Band Wireless AC 8265 doesn't work on Disco on HP Envy 13

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

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

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

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

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

Title:
  Intel(R) Dual Band Wireless AC 8265 doesn't work on Disco on HP Envy
  13

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

Bug description:
  I have hp evny 13. i had installed ubuntu 19.4. it had wifi
  connectivity issue. i have download 2 times IOS and installed OS but
  issue was same. I came back on 18.4. Kindly fix this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-65-generic 4.15.0-65.74
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mhr1474 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 03:41:36 2019
  HibernationDevice: RESUME=UUID=d0158205-dd99-46e8-8a20-d2c71d64c2b4
  InstallationDate: Installed on 2019-10-18 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5670 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY Notebook 13-ab0XX
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-65-generic 
root=UUID=00dd5801-1cb5-42f3-9b3d-1206e1fb9882 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-65-generic N/A
   linux-backports-modules-4.15.0-65-generic  N/A
   linux-firmware 1.173.9
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 82B9
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 03.18
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.11:bd12/09/2016:svnHP:pnHPENVYNotebook13-ab0XX:pvrType1ProductConfigId:rvnHP:rn82B9:rvrKBCVersion03.18:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY Notebook 13-ab0XX
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1848894] Re: Intel(R) Dual Band Wireless AC 8265 doesn't work on Disco on HP Envy 13

[You-Sheng Yang]

I'm closing this as WONTFIX for Disco. Please don't hesitate to reopen
it if it is not working on Eoan/Focal, either.

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

Title:
  Intel(R) Dual Band Wireless AC 8265 doesn't work on Disco on HP Envy
  13

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

Bug description:
  I have hp evny 13. i had installed ubuntu 19.4. it had wifi
  connectivity issue. i have download 2 times IOS and installed OS but
  issue was same. I came back on 18.4. Kindly fix this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-65-generic 4.15.0-65.74
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mhr1474 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 03:41:36 2019
  HibernationDevice: RESUME=UUID=d0158205-dd99-46e8-8a20-d2c71d64c2b4
  InstallationDate: Installed on 2019-10-18 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5670 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY Notebook 13-ab0XX
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-65-generic 
root=UUID=00dd5801-1cb5-42f3-9b3d-1206e1fb9882 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-65-generic N/A
   linux-backports-modules-4.15.0-65-generic  N/A
   linux-firmware 1.173.9
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 82B9
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 03.18
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.11:bd12/09/2016:svnHP:pnHPENVYNotebook13-ab0XX:pvrType1ProductConfigId:rvnHP:rn82B9:rvrKBCVersion03.18:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY Notebook 13-ab0XX
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1848894] Re: Wifi not working

[You-Sheng Yang]

AX/AC support in iwlwifi is left as-is for Disco generic kernel while
back ported to Bionic LTS linux-oem-osp1 kernel. You can install linux-
oem-osp1 kernel on Disco as well if you insist, or upgrade to just
released Eoan as recommended.

** Summary changed:

- Wifi not working 
+ Intel(R) Dual Band Wireless AC 8265 doesn't work on Disco

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

Title:
  Intel(R) Dual Band Wireless AC 8265 doesn't work on Disco on HP Envy
  13

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

Bug description:
  I have hp evny 13. i had installed ubuntu 19.4. it had wifi
  connectivity issue. i have download 2 times IOS and installed OS but
  issue was same. I came back on 18.4. Kindly fix this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-65-generic 4.15.0-65.74
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mhr1474 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 03:41:36 2019
  HibernationDevice: RESUME=UUID=d0158205-dd99-46e8-8a20-d2c71d64c2b4
  InstallationDate: Installed on 2019-10-18 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5670 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY Notebook 13-ab0XX
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-65-generic 
root=UUID=00dd5801-1cb5-42f3-9b3d-1206e1fb9882 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-65-generic N/A
   linux-backports-modules-4.15.0-65-generic  N/A
   linux-firmware 1.173.9
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 82B9
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 03.18
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.11:bd12/09/2016:svnHP:pnHPENVYNotebook13-ab0XX:pvrType1ProductConfigId:rvnHP:rn82B9:rvrKBCVersion03.18:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY Notebook 13-ab0XX
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts

[Dexuan Cui]

I'm not sure what exact issues you're reporting.

Your VM takes too much time to boot up? How long? "systemd-analyze
blame" should collect the info for your VM.

Your VM's screen is somehow messed up temporarily during the boot-up
process? Or the boot-up process is stuck in the "text cursor"  screen
for a long period of time (about 1 minute?) and you'd like to figure out
what's happening during that period of time? But since it looks your VM
is able to boot up in 2 minutes or so (?), it looks there is no fatal
issue?

You're saying you can reproduce the issue with a fresh VM created from
the .iso file (ubuntu-19.10-desktop-amd64.iso)?

It would be helpful if you can share your output of the same commands I
ran.

A video of your VM's boot-up process would be helpful, if that's not
difficult. I don't know how you would share the video. :-)

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

Title:
  [Microsoft Hyper-V guest] System shows graphic artifacts for a moment,
  then text cursor for about minute and then starts

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  New

Bug description:
  AFter upgrade system shows graphic artefacts for a moment and then
  text cursor for about minute (it looks like hanged) and then starts.

  In 19.04 startup required 1 or 2 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 17:42:27 2019
  InstallationDate: Installed on 2019-07-04 (104 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-10-17 17:03:47,139 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  InstallationDate: Installed on 2019-07-04 (105 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: xorg-server (not installed)
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=17409d40-25e9-4051-9fd9-758e2a02ebc3 ro quiet splash 
video=hyperv_fb:1900x900 elevator=noop vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  RfKill:
   
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-18-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 2831-3616-6111-5725-4803-1162-28
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.0
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: 

[Kernel-packages] [Bug 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts

[Dexuan Cui]

Hi M, I can not reproduce the issue: just now I downloaded
http://dt0cinyuc0rrg.cloudfront.net/ubuntu-19.10-desktop-amd64.iso and
created a Generation-2 VM on Hyper-V with the .iso file. The VM boots up
fast: it boots up to the Xorg desktop in 28 seconds with 1 CPU and 2GB
memory, and in 21 seconds with 8 CPUs and 8GB memory.

I don't see anything unusual.

I believe you're also using Generation-2 VM since your "lspci" returns
nothing.

FYI: I got the below in my VM:

decui@decui-u1910-gen2:~$ uname -a
Linux decui-u1910-gen2 5.0.0-32-generic #34-Ubuntu SMP Wed Oct 2 02:06:48 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

decui@decui-u1910-gen2:~$ dmesg | grep "Hyper-V Host Build"
[0.00] Hyper-V Host Build:18928-10.0-1-0.1044

decui@decui-u1910-gen2:~$ systemd-analyze
Startup finished in 303ms (firmware) + 663ms (loader) + 1.087s (kernel) + 
35.041s (userspace) = 37.096s
graphical.target reached after 34.963s in userspace

decui@decui-u1910-gen2:~$ systemd-analyze blame
 31.530s plymouth-quit-wait.service
 10.598s gdm.service
  1.817s dev-sda2.device
   944ms networkd-dispatcher.service
   866ms NetworkManager-wait-online.service
  .

decui@decui-u1910-gen2:~$  systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @34.963s
└─multi-user.target @34.963s
  └─kerneloops.service @4.213s +34ms
└─network-online.target @4.170s
  └─NetworkManager-wait-online.service @3.301s +866ms
└─NetworkManager.service @2.983s +317ms
  └─dbus.service @2.912s
└─basic.target @2.765s
  └─sockets.target @2.765s
└─snapd.socket @2.754s +10ms
  └─sysinit.target @2.731s
└─apparmor.service @2.199s +530ms
  └─local-fs.target @2.173s
└─run-user-1000-gvfs.mount @17.395s
  └─run-user-1000.mount @14.119s
└─local-fs-pre.target @456ms
  └─keyboard-setup.service @223ms +232ms
└─systemd-journald.socket @218ms
  └─-.mount @206ms
└─system.slice @206ms
  └─-.slice @206ms

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

Title:
  [Microsoft Hyper-V guest] System shows graphic artifacts for a moment,
  then text cursor for about minute and then starts

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  New

Bug description:
  AFter upgrade system shows graphic artefacts for a moment and then
  text cursor for about minute (it looks like hanged) and then starts.

  In 19.04 startup required 1 or 2 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 17:42:27 2019
  InstallationDate: Installed on 2019-07-04 (104 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-10-17 17:03:47,139 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  InstallationDate: Installed on 2019-07-04 (105 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: xorg-server (not installed)
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=17409d40-25e9-4051-9fd9-758e2a02ebc3 ro quiet splash 
video=hyperv_fb:1900x900 elevator=noop vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  

[Kernel-packages] [Bug 1848831] Re: Intel WiFi AX200 firmware loading error resulting in no wifi

[Ari]

Based on a few references and the issue in my system, it seems ax200 has
issues with (at least) specific PCIE slot types X16, again at least with
certain motherboards.X1/X4/X8 slots seem to work ok consistently.
Hopefully this is fixable via firmware, so will retest once Intel
releases the next few version

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

Title:
  Intel WiFi AX200 firmware loading error resulting in no wifi

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10 - stock kernel - Intel AX200 PCI card in a desktop PC

  uname -a
  Linux nahuatl 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  The card is detected OK as dmesg shows, however the card's firmware
  fails immediately after loading (see dmesg output below) and wifi
  doesn't work at all. Big disappointment since the AX200 chip was
  supposed to be supported on 19.10.

  Ubuntu includes two ax200 firmware versions, version 48 loads by
  default in my system (and fails). I tried version 46 (by renaming the
  version 48 file) and it failed in the exact same manner

  $ ls /lib/firmware/iwlwifi-cc-*
  /lib/firmware/iwlwifi-cc-a0-46.ucode  /lib/firmware/iwlwifi-cc-a0-48.ucode

  
  The card's Bluetooth functionality is also detected and it works fine. It's 
just the wifi FW loading what seems broken in ubuntu's 5.3 kernel.

  $ rfkill list
  0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no



  ~$ dmesg | grep iwl
  [   12.312443] iwlwifi :01:00.0: enabling device ( -> 0002)
  [   12.321098] iwlwifi :01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 
43.2.23.17
  [   12.321101] iwlwifi :01:00.0: Found debug destination: EXTERNAL_DRAM
  [   12.321102] iwlwifi :01:00.0: Found debug configuration: 0
  [   12.321309] iwlwifi :01:00.0: loaded firmware version 48.4fa0041f.0 
op_mode iwlmvm
  [   12.390389] iwlwifi :01:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, 
REV=0x340
  [   12.400654] iwlwifi :01:00.0: Applying debug destination EXTERNAL_DRAM
  [   12.400893] iwlwifi :01:00.0: Allocated 0x0040 bytes for firmware 
monitor.
  [   13.414781] iwlwifi :01:00.0: Collecting data: trigger 15 fired.
  [   13.414908] iwlwifi :01:00.0: Start IWL Error Log Dump:
  [   13.414910] iwlwifi :01:00.0: Status: 0x, count: 6
  [   13.414911] iwlwifi :01:00.0: Loaded firmware version: 48.4fa0041f.0
  [   13.414912] iwlwifi :01:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
  [   13.414913] iwlwifi :01:00.0: 0x002022F0 | trm_hw_status0
  [   13.414913] iwlwifi :01:00.0: 0x | trm_hw_status1
  [   13.414914] iwlwifi :01:00.0: 0x004F8E3C | branchlink2
  [   13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink1
  [   13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink2
  [   13.414916] iwlwifi :01:00.0: 0x004F3DB0 | data1
  [   13.414917] iwlwifi :01:00.0: 0x1000 | data2
  [   13.414917] iwlwifi :01:00.0: 0xF000 | data3
  [   13.414918] iwlwifi :01:00.0: 0x | beacon time
  [   13.414919] iwlwifi :01:00.0: 0x795F | tsf low
  [   13.414919] iwlwifi :01:00.0: 0x | tsf hi
  [   13.414920] iwlwifi :01:00.0: 0x | time gp1
  [   13.414921] iwlwifi :01:00.0: 0xDFD5 | time gp2
  [   13.414921] iwlwifi :01:00.0: 0x0001 | uCode revision type
  [   13.414922] iwlwifi :01:00.0: 0x0030 | uCode version major
  [   13.414923] iwlwifi :01:00.0: 0x4FA0041F | uCode version minor
  [   13.414923] iwlwifi :01:00.0: 0x0340 | hw version
  [   13.414924] iwlwifi :01:00.0: 0x18C89000 | board version
  [   13.414925] iwlwifi :01:00.0: 0x8002FF03 | hcmd
  [   13.414925] iwlwifi :01:00.0: 0x0002 | isr0
  [   13.414926] iwlwifi :01:00.0: 0x | isr1
  [   13.414926] iwlwifi :01:00.0: 0x08F2 | isr2
  [   13.414927] iwlwifi :01:00.0: 0x00CC | isr3
  [   13.414928] iwlwifi :01:00.0: 0x | isr4
  [   13.414928] iwlwifi :01:00.0: 0x | last cmd Id
  [   13.414929] iwlwifi :01:00.0: 0x004F3DB0 | wait_event
  [   13.414930] iwlwifi :01:00.0: 0x | l2p_control
  [   13.414930] iwlwifi :01:00.0: 0x0020 | l2p_duration
  [   13.414931] iwlwifi :01:00.0: 0x | l2p_mhvalid
  [   13.414932] iwlwifi :01:00.0: 0x | l2p_addr_match
  [   13.414932] iwlwifi :01:00.0: 0x0009 | lmpm_pmg_sel
  [   13.414933] iwlwifi :01:00.0: 0x | timestamp
  [   13.414934] iwlwifi :01:00.0: 0xF81C | flow_handler
  [   13.414974] iwlwifi :01:00.0: Start IWL Error Log Dump:
  [   13.414975] iwlwifi :01:00.0: Status: 0x, count: 7
  [   13.414976] iwlwifi :01:00.0: 0x201000A3 | ADVANCED_SYSASSERT
  [   13.414976] iwlwifi :01:00.0: 0x | umac branchlink1
 

[Kernel-packages] [Bug 1847478] Re: eoan kernel does not contain "ipv6: do not free rt if FIB_LOOKUP_NOREF is set on suppress rule"

[Jeremy Bicha]

** Information type changed from Public to Public Security

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

Title:
  eoan kernel does not contain "ipv6: do not free rt if FIB_LOOKUP_NOREF
  is set on suppress rule"

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

Bug description:
  [Impact]

  An unprivileged local attacker could cause a denial of service, or
  possibly execute arbitrary code due to an ipv6 regression.

  [Test Case]

  An unpatched system will crash with the following command:

  $ unshare -rUn sh -c 'ip link add dummy1 type dummy && ip link set
  dummy1 up && ip -6 route add default dev dummy1 && ip -6 rule add
  table main suppress_prefixlength 0 && ping -f 1234::1'

  [Regression Potential]

  Low. The change could theoretically introduce a memory leak but that
  would still be an improvement over immediate loss of system
  availability.

  [Original Description]

  Having recently upgraded to Eoan Ermine from Disco Dingo, my
  previously rock-solid wireguard now locks the system up shortly after
  I take the connection down with wg-quick down wg0.

  Package:

  wireguard:
    Installed: 0.0.20190913-1ubuntu1
    Candidate: 0.0.20190913-1ubuntu1
    Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe i386 Packages
  100 /var/lib/dpkg/status

  Kernel:
  5.3.0-13-generic

  Snipped from /var/log/syslog:

  kernel: [  776.930804] BUG: unable to handle page fault for address: 
1070
  kernel: [  776.930807] #PF: supervisor read access in kernel mode
  kernel: [  776.930808] #PF: error_code(0x) - not-present page
  kernel: [  776.930809] PGD 0 P4D 0
  kernel: [  776.930811] Oops:  [#1] SMP NOPTI
  kernel: [  776.930813] CPU: 3 PID: 2598 Comm: Chrome_ChildIOT Tainted: G  
 OE 5.3.0-13-generic #14-Ubuntu
  kernel: [  776.930813] Hardware name: Dell Inc. XPS 13 9380/0KTW76, BIOS 
1.7.0 08/05/2019
  kernel: [  776.930817] RIP: 0010:ip6_sk_dst_store_flow+0x80/0xc0
  kernel: [  776.930819] Code: 48 8b 42 30 48 33 47 40 48 09 c1 0f b6 4f 12 b8 
01 00 00 00 4d 0f 45 e9 31 db d3 e0 a9 bf ef ff ff 74 07 48 8b 9f f8 02 00 00 
<48> 8b 46 70 31 d2 48 85 c0 74 0c 48 8b 40 10 48 85 c0 74 03 8b 50
  kernel: [  776.930820] RSP: 0018:beb841a9fcd8 EFLAGS: 00010202
  kernel: [  776.930821] RAX: 0080 RBX: a0933c829360 RCX: 
0007
  kernel: [  776.930822] RDX: beb841a9fd20 RSI: 1000 RDI: 
a0933c828f00
  kernel: [  776.930823] RBP: beb841a9fcf0 R08:  R09: 

  kernel: [  776.930823] R10:  R11: a093948fd800 R12: 
a0933c829360
  kernel: [  776.930824] R13: a0933c828f38 R14: 0001 R15: 
a0933c829360
  kernel: [  776.930825] FS:  7fbcd8a82700() GS:a0939e4c() 
knlGS:
  kernel: [  776.930826] CS:  0010 DS:  ES:  CR0: 80050033
  kernel: [  776.930827] CR2: 1070 CR3: 00049172a004 CR4: 
003606e0
  kernel: [  776.930828] Call Trace:
  kernel: [  776.930832]  ip6_datagram_dst_update+0x15e/0x280
  kernel: [  776.930835]  ? _raw_read_unlock_bh+0x20/0x30
  kernel: [  776.930837]  __ip6_datagram_connect+0x1da/0x380
  kernel: [  776.930839]  ip6_datagram_connect+0x2d/0x50
  kernel: [  776.930841]  inet_dgram_connect+0x3f/0xc0
  kernel: [  776.930843]  __sys_connect+0xf1/0x130
  kernel: [  776.930846]  ? do_fcntl+0xe4/0x550
  kernel: [  776.930848]  ? fput+0x13/0x15
  kernel: [  776.930849]  __x64_sys_connect+0x1a/0x20
  kernel: [  776.930852]  do_syscall_64+0x5a/0x130
  kernel: [  776.930854]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  kernel: [  776.930855] RIP: 0033:0x7fbcde6324eb
  kernel: [  776.930856] Code: 83 ec 18 89 54 24 0c 48 89 34 24 89 7c 24 08 e8 
ab fa ff ff 8b 54 24 0c 48 8b 34 24 41 89 c0 8b 7c 24 08 b8 2a 00 00 00 0f 05 
<48> 3d 00 f0 ff ff 77 2f 44 89 c7 89 44 24 08 e8 e1 fa ff ff 8b 44
  kernel: [  776.930857] RSP: 002b:7fbcd8a7ec90 EFLAGS: 0293 ORIG_RAX: 
002a
  kernel: [  776.930859] RAX: ffda RBX: ff94 RCX: 
7fbcde6324eb
  kernel: [  776.930859] RDX: 001c RSI: 7fbcd8a7ecf0 RDI: 
0022
  kernel: [  776.930860] RBP: 7fbcd8a7edb0 R08:  R09: 
7fbcd8a7edf8
  kernel: [  776.930861] R10: 7fbcd8a7edf0 R11: 0293 R12: 
250e77c19710
  kernel: [  776.930862] R13: 250e77c19900 R14: 7fbcd8a7edc8 R15: 
7fbcd8a7edc8
  kernel: [  776.930863] Modules linked in: binfmt_misc wireguard(OE) 
ip6_udp_tunnel udp_tunnel ccm rfcomm uhid algif_hash algif_skcipher af_alg cmac 
bnep sof_pci_dev snd_sof_intel_hda_common snd_sof_intel_byt snd_sof_intel_ipc 

[Kernel-packages] [Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices

[Adam T]

Setting total_mem=2048 or 3072 in /boot/firmware/usercfg.txt allowed me
to boot Pi4 4GB with 19.10 64bit with working USB. Of course I have less
RAM now, but working USB.

Likely the above patch will fix it.

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

Title:
  Raspberry Pi 4 - USB Bus not detecting any devices

Status in linux-raspi2 package in Ubuntu:
  Confirmed

Bug description:
  Pi 4 new install.  System boots up but USB bus is not working.

  Tried 3 keyboards no key presses detected, 2 usb memory drives don't
  show up in lsblk.

  output of $lspci
  00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 2711 (rev 10)
  01:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller 
(rev 01) 

  output of $dmesg on pastebin here http://pastebin.com/h7A3n9xa or
  attached to this bug report.

  Not the only one experiencing bug.  Another user created a post on the ubuntu 
forums: 
  
https://ubuntuforums.org/showthread.php?t=2429396=01a0c4b0cb4c05e605cbf9d41f660e08=13898142#post13898142


  64bit raspberry pi 4&4 image pulled from
  https://ubuntu.com/download/iot/raspberry-pi page.  Specifically
  http://cdimage.ubuntu.com/releases/19.10/release/ubuntu-19.10
  -preinstalled-server-arm64+raspi3.img.xz

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

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

[Kernel-packages] [Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices

[Andrew Davis]

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

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

Title:
  Raspberry Pi 4 - USB Bus not detecting any devices

Status in linux-raspi2 package in Ubuntu:
  Confirmed

Bug description:
  Pi 4 new install.  System boots up but USB bus is not working.

  Tried 3 keyboards no key presses detected, 2 usb memory drives don't
  show up in lsblk.

  output of $lspci
  00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 2711 (rev 10)
  01:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller 
(rev 01) 

  output of $dmesg on pastebin here http://pastebin.com/h7A3n9xa or
  attached to this bug report.

  Not the only one experiencing bug.  Another user created a post on the ubuntu 
forums: 
  
https://ubuntuforums.org/showthread.php?t=2429396=01a0c4b0cb4c05e605cbf9d41f660e08=13898142#post13898142


  64bit raspberry pi 4&4 image pulled from
  https://ubuntu.com/download/iot/raspberry-pi page.  Specifically
  http://cdimage.ubuntu.com/releases/19.10/release/ubuntu-19.10
  -preinstalled-server-arm64+raspi3.img.xz

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

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

[Kernel-packages] [Bug 1848790] Re: USB not working under arm64 on Pi4

[Adam T]

Setting total_mem=2048 in /boot/firmware/usercfg.txt allowed me to boot
Pi4 4GB with 19.10 64bit with working USB. Of course I have less RAM
now, but working USB.

Likely the above patch will fix it.

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

Title:
  USB not working under arm64 on Pi4

Status in linux-raspi2 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard
  which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10
  armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the
  keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the
  keyboard worked successfully.

  Output of lsusb under arm64 on a Pi 3:

  ubuntu@ubuntu:~$ lsusb
  Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard
  Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
  Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of lsusb under armhf on a Pi 4 (same keyboard attached):

  ubuntu@ubuntu:~$ lsusb
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard
  Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of lsusb under arm64 on the same Pi 4 (same keyboard attached):

  ubuntu@ubuntu:~$ lsusb
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  The fact even the VIA Labs hub doesn't show up (which is built in)
  suggests the kernel is (for some reason) unable to enumerate anything
  against the USB hubs.

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

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

[Kernel-packages] [Bug 1848703] [NEW] Raspberry Pi 4 - USB Bus not detecting any devices

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Pi 4 new install.  System boots up but USB bus is not working.

Tried 3 keyboards no key presses detected, 2 usb memory drives don't
show up in lsblk.

output of $lspci
00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 2711 (rev 10)
01:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller 
(rev 01) 

output of $dmesg on pastebin here http://pastebin.com/h7A3n9xa or
attached to this bug report.

Not the only one experiencing bug.  Another user created a post on the ubuntu 
forums: 
https://ubuntuforums.org/showthread.php?t=2429396=01a0c4b0cb4c05e605cbf9d41f660e08=13898142#post13898142


64bit raspberry pi 4&4 image pulled from https://ubuntu.com/download/iot
/raspberry-pi page.  Specifically
http://cdimage.ubuntu.com/releases/19.10/release/ubuntu-19.10
-preinstalled-server-arm64+raspi3.img.xz

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


** Tags: bot-comment
-- 
Raspberry Pi 4 - USB Bus not detecting any devices
https://bugs.launchpad.net/bugs/1848703
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-raspi2 in Ubuntu.

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

[Kernel-packages] [Bug 1848898] Re: /home/user/lspci-vnvn.log

[Chris Guiver]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

What is the problem?  I don't see any description of the problem, what
you are trying to do, what you did, what occurred, or what you expected
to occur.

Unfortunately, we cannot work on this bug because your description
didn't include enough information. You may find it helpful to read "How
to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Thanks!

ps:  If you believe I'm in error, please return this bug status back to
"New" and leave a reason as to why (what I missed etc).

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

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

Title:
  /home/user/lspci-vnvn.log

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  00:00.0 Host bridge [0600]: Intel Corporation Mobile 915GM/PM/GMS/910GML 
Express Processor to DRAM Controller [8086:2590] (rev 03)
Subsystem: Acer Incorporated [ALI] Mobile 915GM/PM/GMS/910GML Express 
Processor to DRAM Controller [1025:008f]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: agpgart-intel

  00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 
915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 00 
[VGA controller])
Subsystem: Acer Incorporated [ALI] Mobile 915GM/GMS/910GML Express 
Graphics Controller [1025:008f]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: i915
Kernel modules: i915, intelfb

  00:02.1 Display controller [0380]: Intel Corporation Mobile 915GM/GMS/910GML 
Express Graphics Controller [8086:2792] (rev 03)
Subsystem: Acer Incorporated [ALI] Mobile 915GM/GMS/910GML Express 
Graphics Controller [1025:008f]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag+ RBE-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit 
Latency L0s <1us, L1 <4us
ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ 
DLActive- BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ 
Surprise+
Slot #2, PowerLimit 6.500W; Interlock- NoCompl-
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet+ CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- 
Interlock-
Changed: MRL- PresDet- LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address:   Data: 
Capabilities: [90] Subsystem: Acer Incorporated [ALI] 
82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 [1025:008f]
Capabilities: [a0] Power Management version 2

[Kernel-packages] [Bug 1848898] [NEW] /home/user/lspci-vnvn.log

[maria teresa]

Public bug reported:

00:00.0 Host bridge [0600]: Intel Corporation Mobile 915GM/PM/GMS/910GML 
Express Processor to DRAM Controller [8086:2590] (rev 03)
Subsystem: Acer Incorporated [ALI] Mobile 915GM/PM/GMS/910GML Express 
Processor to DRAM Controller [1025:008f]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: agpgart-intel

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 
915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 00 
[VGA controller])
Subsystem: Acer Incorporated [ALI] Mobile 915GM/GMS/910GML Express 
Graphics Controller [1025:008f]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: i915
Kernel modules: i915, intelfb

00:02.1 Display controller [0380]: Intel Corporation Mobile 915GM/GMS/910GML 
Express Graphics Controller [8086:2792] (rev 03)
Subsystem: Acer Incorporated [ALI] Mobile 915GM/GMS/910GML Express 
Graphics Controller [1025:008f]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag+ RBE-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit 
Latency L0s <1us, L1 <4us
ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ 
DLActive- BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ 
Surprise+
Slot #2, PowerLimit 6.500W; Interlock- NoCompl-
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet+ CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- 
Interlock-
Changed: MRL- PresDet- LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address:   Data: 
Capabilities: [90] Subsystem: Acer Incorporated [ALI] 
82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 [1025:008f]
Capabilities: [a0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] Virtual Channel
Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
Arb:Fixed+ WRR32- WRR64- WRR128-
Ctrl:   ArbSelect=Fixed
Status: InProgress-
VC0:Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb:Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending- InProgress-
VC1:Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb:Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl:   Enable- ID=0 ArbSelect=Fixed TC/VC=00
Status: NegoPending- InProgress-
Capabilities: [180 v1] Root Complex Link
Desc:   PortNumber=01 ComponentID=02 EltType=Config
Link0:  Desc:   TargetPort=00 TargetComponent=02 AssocRCRB- 
LinkType=MemMapped LinkValid+
Addr:   f0008001
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.1 PCI bridge [0604]: Intel 

[Kernel-packages] [Bug 1848894] Re: Wifi not working

[Chris Guiver]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Wifi appears to be working on your 18.04 system where you filed the bug.
To gain information about problems with 19.04 the bug should be filed
whilst running Ubuntu 19.04

Ubuntu 19.04 is also 2/3rd through it's life-cycle, with it's
replacement Ubuntu 19.10 having been released; so I'd suggest seeking
support, or trying the latest Ubuntu 19.10.  Bug reports are more about
fixing the problem for subsequent users, and you're reporting a bug on a
prior/older release (which is not the latest), where as support is about
fixing your specific problem (ie. getting wifi working on your 19.04
system like it does on 18.04)

This bug report can be converted to a question (which is aimed at
support). You can also find help with your problem in the support forum
of your local Ubuntu community http://loco.ubuntu.com/ or asking at
https://askubuntu.com or https://ubuntuforums.org, or for more support
options please look at https://discourse.ubuntu.com/t/community-
support/709

I've marked this bug incomplete as normal support steps don't appear to
have been tried, or evidence of them hasn't been provided. If you
believe I'm in error, or can provide additional detail of steps done,
please change status back to "New" and leave comment, or additional
information as to what was attempted.  I would also suggest you try the
latest Ubuntu 19.10.

Thanks again for helping make Ubuntu better.

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

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

Title:
  Wifi not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have hp evny 13. i had installed ubuntu 19.4. it had wifi
  connectivity issue. i have download 2 times IOS and installed OS but
  issue was same. I came back on 18.4. Kindly fix this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-65-generic 4.15.0-65.74
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mhr1474 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 03:41:36 2019
  HibernationDevice: RESUME=UUID=d0158205-dd99-46e8-8a20-d2c71d64c2b4
  InstallationDate: Installed on 2019-10-18 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5670 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY Notebook 13-ab0XX
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-65-generic 
root=UUID=00dd5801-1cb5-42f3-9b3d-1206e1fb9882 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-65-generic N/A
   linux-backports-modules-4.15.0-65-generic  N/A
   linux-firmware 1.173.9
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 82B9
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 03.18
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.11:bd12/09/2016:svnHP:pnHPENVYNotebook13-ab0XX:pvrType1ProductConfigId:rvnHP:rn82B9:rvrKBCVersion03.18:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY Notebook 13-ab0XX
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1848894] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Wifi not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have hp evny 13. i had installed ubuntu 19.4. it had wifi
  connectivity issue. i have download 2 times IOS and installed OS but
  issue was same. I came back on 18.4. Kindly fix this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-65-generic 4.15.0-65.74
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mhr1474 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 03:41:36 2019
  HibernationDevice: RESUME=UUID=d0158205-dd99-46e8-8a20-d2c71d64c2b4
  InstallationDate: Installed on 2019-10-18 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5670 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY Notebook 13-ab0XX
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-65-generic 
root=UUID=00dd5801-1cb5-42f3-9b3d-1206e1fb9882 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-65-generic N/A
   linux-backports-modules-4.15.0-65-generic  N/A
   linux-firmware 1.173.9
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 82B9
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 03.18
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.11:bd12/09/2016:svnHP:pnHPENVYNotebook13-ab0XX:pvrType1ProductConfigId:rvnHP:rn82B9:rvrKBCVersion03.18:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY Notebook 13-ab0XX
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1848894] [NEW] Wifi not working

[Muhammad Hassan Rasheed]

Public bug reported:

I have hp evny 13. i had installed ubuntu 19.4. it had wifi connectivity
issue. i have download 2 times IOS and installed OS but issue was same.
I came back on 18.4. Kindly fix this issue.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-65-generic 4.15.0-65.74
ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
Uname: Linux 4.15.0-65-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mhr1474 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 20 03:41:36 2019
HibernationDevice: RESUME=UUID=d0158205-dd99-46e8-8a20-d2c71d64c2b4
InstallationDate: Installed on 2019-10-18 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 002: ID 13d3:5670 IMC Networks 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP ENVY Notebook 13-ab0XX
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-65-generic 
root=UUID=00dd5801-1cb5-42f3-9b3d-1206e1fb9882 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-65-generic N/A
 linux-backports-modules-4.15.0-65-generic  N/A
 linux-firmware 1.173.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/09/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.11
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 82B9
dmi.board.vendor: HP
dmi.board.version: KBC Version 03.18
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.11:bd12/09/2016:svnHP:pnHPENVYNotebook13-ab0XX:pvrType1ProductConfigId:rvnHP:rn82B9:rvrKBCVersion03.18:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
dmi.product.name: HP ENVY Notebook 13-ab0XX
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug bionic

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

Title:
  Wifi not working

Status in linux package in Ubuntu:
  New

Bug description:
  I have hp evny 13. i had installed ubuntu 19.4. it had wifi
  connectivity issue. i have download 2 times IOS and installed OS but
  issue was same. I came back on 18.4. Kindly fix this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-65-generic 4.15.0-65.74
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mhr1474 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 03:41:36 2019
  HibernationDevice: RESUME=UUID=d0158205-dd99-46e8-8a20-d2c71d64c2b4
  InstallationDate: Installed on 2019-10-18 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5670 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY Notebook 13-ab0XX
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-65-generic 
root=UUID=00dd5801-1cb5-42f3-9b3d-1206e1fb9882 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-65-generic N/A
   linux-backports-modules-4.15.0-65-generic  N/A
   linux-firmware 1.173.9
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 82B9
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 03.18
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.11:bd12/09/2016:svnHP:pnHPENVYNotebook13-ab0XX:pvrType1ProductConfigId:rvnHP:rn82B9:rvrKBCVersion03.18:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY Notebook 13-ab0XX
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1612916] Re: Internal speakers don't work after standby

[S. Joseph]

Looks like the issue has not been resoled yet. I can confirm I have the
same issue on a Toshiba z20t-B with Ubuntu 19.10 ( 5.3.0-18-generic
kernel).

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

Title:
  Internal speakers don't work after standby

Status in linux package in Ubuntu:
  Triaged
Status in linux package in Debian:
  New

Bug description:
  I've a Toshiba x20t-C-121 (Skylake m7-6Y75 based). On initial boot,
  sound on internal speakers is working. After standby it doesn work
  anymore, but a analog headset does. Switching around in pavucontrol
  doesn't work... Internal microphone works.

  I'm using Ubuntu 16.04 64 bit on a 4.4.0-34-generic kernel.
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michi  6510 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/1tb-swap
  MachineType: TOSHIBA PORTEGE Z20t-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/1tb-miniubuntu ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/27/2016
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.60
  dmi.board.asset.tag: 00
  dmi.board.name: PORTEGE Z20t-C
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.60:bd06/27/2016:svnTOSHIBA:pnPORTEGEZ20t-C:pvrPT16BE-00W006GR:rvnTOSHIBA:rnPORTEGEZ20t-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE Z20t-C
  dmi.product.version: PT16BE-00W006GR
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1721345] Re: ALC295 codec seems to have Master and PCM channels swapped

[Mario Vukelic]

Still occurs on 19.10 after upgrade, on the same Asus ZenBook Flip 15 UX561UD 
as in comment #30. 
As the upgrade replaced 
"/usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common", had to 
reapply the workaround from comment #8 (which is kind of bearable on a machine 
that is has a proper admin, but sucks for normal people)

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

Title:
  ALC295 codec seems to have Master and PCM channels swapped

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When trying to use pulseaudio to control volume on my ASUS Zenbook Pro
  UX550VE *uses AC295 audio codec) I noticed that pulseuadio is varying
  the Master ALSA channel. If I vary that channel in alsamixer I get no
  variation in volume. If I vary the PCM channel instead I get the
  desired effect that volume buttons should have. Since pulseaudio
  varies the Master channel by default and does not respect any
  configuration settings telling it to use other settings, I suggest
  swapping these two channels so that pulseaudio works out of the box.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dylan  1532 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Oct  4 19:25:38 2017
  HibernationDevice: RESUME=UUID=2b6908b4-d463-4170-9be5-556145c71a0e
  InstallationDate: Installed on 2017-10-02 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5755 IMC Networks 
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX550VE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=aa3dfd29-caf8-4882-906e-1b31b672d2c2 ro quiet splash threadirqs 
acpi_osi=! acpi_osi=Linux acpi_backlight=native vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550VE.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550VE
  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.:bvrUX550VE.300:bd06/05/2017:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX550VE
  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/1721345/+subscriptions

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

[Kernel-packages] [Bug 1848790] Re: USB not working under arm64 on Pi4

[Ken Howe]

fixed links

User on lingon on raspberry pi forum posted the following:

The USB-problem concerning the Raspberry Pi 4GB RAM model might be due to the 
issue seen earlier that using more RAM than 3072 MB breaks the USB:
[url]https://www.raspberrypi.org/forums/viewtopic.php?f=63=246766=25[/url]

The issue was solved by a kernel patch:
[url]https://www.raspberrypi.org/forums/viewtopic.php?f=63=246766=50#p1517839[/url]

and the kernel patch was this one:
[url]https://github.com/raspberrypi/linux/issues/3093#issuecomment-520269280[/url]

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

Title:
  USB not working under arm64 on Pi4

Status in linux-raspi2 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard
  which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10
  armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the
  keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the
  keyboard worked successfully.

  Output of lsusb under arm64 on a Pi 3:

  ubuntu@ubuntu:~$ lsusb
  Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard
  Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
  Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of lsusb under armhf on a Pi 4 (same keyboard attached):

  ubuntu@ubuntu:~$ lsusb
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard
  Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of lsusb under arm64 on the same Pi 4 (same keyboard attached):

  ubuntu@ubuntu:~$ lsusb
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  The fact even the VIA Labs hub doesn't show up (which is built in)
  suggests the kernel is (for some reason) unable to enumerate anything
  against the USB hubs.

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

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

[Kernel-packages] [Bug 1848790] Re: USB not working under arm64 on Pi4

[Ken Howe]

Fixed links

User on lingon on raspberry pi forum posted the following:

The USB-problem concerning the Raspberry Pi 4GB RAM model might be due to the 
issue seen earlier that using more RAM than 3072 MB breaks the USB:
[url]https://www.raspberrypi.org/forums/viewtopic.php?f=63=246766=25[/url]

The issue was solved by a kernel patch:
[url]https://www.raspberrypi.org/forums/viewtopic.php?f=63=246766=50#p1517839[/url]

and the kernel patch was this one:
[url]https://github.com/raspberrypi/linux/issues/3093#issuecomment-520269280[/url]

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

Title:
  USB not working under arm64 on Pi4

Status in linux-raspi2 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard
  which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10
  armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the
  keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the
  keyboard worked successfully.

  Output of lsusb under arm64 on a Pi 3:

  ubuntu@ubuntu:~$ lsusb
  Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard
  Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
  Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of lsusb under armhf on a Pi 4 (same keyboard attached):

  ubuntu@ubuntu:~$ lsusb
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard
  Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of lsusb under arm64 on the same Pi 4 (same keyboard attached):

  ubuntu@ubuntu:~$ lsusb
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  The fact even the VIA Labs hub doesn't show up (which is built in)
  suggests the kernel is (for some reason) unable to enumerate anything
  against the USB hubs.

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

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

[Kernel-packages] [Bug 1848790] Re: USB not working under arm64 on Pi4

[Ken Howe]

fixed links

User on lingon on raspberry pi forum posted the following:

The USB-problem concerning the Raspberry Pi 4GB RAM model might be due to the 
issue seen earlier that using more RAM than 3072 MB breaks the USB:
https://www.raspberrypi.org/forums/v...46766=25

The issue was solved by a kernel patch:
https://www.raspberrypi.org/forums/v...rt=50#p1517839

and the kernel patch was this one:
https://github.com/raspberrypi/linux...ment-520269280

** Bug watch added: github.com/raspberrypi/linux/issues #3093
   https://github.com/raspberrypi/linux/issues/3093

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

Title:
  USB not working under arm64 on Pi4

Status in linux-raspi2 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard
  which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10
  armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the
  keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the
  keyboard worked successfully.

  Output of lsusb under arm64 on a Pi 3:

  ubuntu@ubuntu:~$ lsusb
  Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard
  Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
  Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of lsusb under armhf on a Pi 4 (same keyboard attached):

  ubuntu@ubuntu:~$ lsusb
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard
  Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of lsusb under arm64 on the same Pi 4 (same keyboard attached):

  ubuntu@ubuntu:~$ lsusb
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  The fact even the VIA Labs hub doesn't show up (which is built in)
  suggests the kernel is (for some reason) unable to enumerate anything
  against the USB hubs.

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

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

[Kernel-packages] [Bug 1848790] Re: USB not working under arm64 on Pi4

[Ken Howe]

User on lingon on raspberry pi forum posted the following:

The USB-problem concerning the Raspberry Pi 4GB RAM model might be due to the 
issue seen earlier that using more RAM than 3072 MB breaks the USB:
https://www.raspberrypi.org/forums/view ... 6=25

The issue was solved by a kernel patch:
https://www.raspberrypi.org/forums/view ... 0#p1517839

and the kernel patch was this one:
https://github.com/raspberrypi/linux/is ... -520269280

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

Title:
  USB not working under arm64 on Pi4

Status in linux-raspi2 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard
  which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10
  armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the
  keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the
  keyboard worked successfully.

  Output of lsusb under arm64 on a Pi 3:

  ubuntu@ubuntu:~$ lsusb
  Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard
  Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
  Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of lsusb under armhf on a Pi 4 (same keyboard attached):

  ubuntu@ubuntu:~$ lsusb
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard
  Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of lsusb under arm64 on the same Pi 4 (same keyboard attached):

  ubuntu@ubuntu:~$ lsusb
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  The fact even the VIA Labs hub doesn't show up (which is built in)
  suggests the kernel is (for some reason) unable to enumerate anything
  against the USB hubs.

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

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

[Kernel-packages] [Bug 1836986] Re: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260

[Jeremy]

Does the command iwconfig show power management on/off or no results

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

Title:
  Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu version:
  Description:  Ubuntu Eoan Ermine (development branch)
  Release:  19.10


  System type:
  description: Notebook
  product: Precision 5530 (087D)
  vendor: Dell Inc.

  
  Hardware having issue:
  (wireless card info from previous working kernel)
 *-network
  description: Wireless interface
  product: Wireless-AC 9260
  vendor: Intel Corporation
  physical id: 0
  bus info: pci@:3b:00.0
  logical name: wlp59s0
  version: 29
  serial: 48:89:e7:d5:ab:b5
  width: 64 bits
  clock: 33MHz
  capabilities: pm msi pciexpress msix bus_master cap_list 
ethernet physical wireless
  configuration: broadcast=yes driver=iwlwifi 
driverversion=5.0.0-20-generic firmware=43.95eb4e97.0 ip=10.80.13.232 latency=0 
link=yes multicast=yes wireless=IEEE 802.11
  resources: irq:16 memory:ed40-ed403fff

  
  Grub config with settings for Dell laptop hardware set:
  /etc/default/grub
  # If you change this file, run 'update-grub' afterwards to update
  # /boot/grub/grub.cfg.
  # For full documentation of the options in this file, see:
  #   info -f grub -n 'Simple configuration'

  GRUB_DEFAULT=0
  GRUB_TIMEOUT=0
  GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
  #GRUB_CMDLINE_LINUX_DEFAULT="nosplash"
  GRUB_CMDLINE_LINUX="nouveau.blacklist=1 acpi_rev_override=1 acpi_osi=Linux 
nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 
nouveau.runpm=0 mem_sleep_default=deep"

  # Uncomment to enable BadRAM filtering, modify to suit your needs
  # This works with Linux (no patch required) and with any kernel that obtains
  # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
  #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

  # Uncomment to disable graphical terminal (grub-pc only)
  #GRUB_TERMINAL=console

  # The resolution used on graphical terminal
  # note that you can use only modes which your graphic card supports via VBE
  # you can see them in real GRUB with the command `vbeinfo'
  #GRUB_GFXMODE=640x480

  # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
  #GRUB_DISABLE_LINUX_UUID=true

  # Uncomment to disable generation of recovery mode menu entries
  #GRUB_DISABLE_RECOVERY="true"

  # Uncomment to get a beep at grub start
  #GRUB_INIT_TUNE="480 440 1"


  Iwlwifi config with 11n disabled, 11n wasn't ever stable before, so left it 
disabled.
  /etc/modprobe.d/iwlwifi.conf 
  # /etc/modprobe.d/iwlwifi.conf
  # iwlwifi will dyamically load either iwldvm or iwlmvm depending on the
  # microcode file installed on the system.  When removing iwlwifi, first
  # remove the iwl?vm module and then iwlwifi.
  remove iwlwifi \
  (/sbin/lsmod | grep -o -e ^iwlmvm -e ^iwldvm -e ^iwlwifi | xargs /sbin/rmmod) 
\
  && /sbin/modprobe -r mac80211
  options iwlwifi 11n_disable=1


  Linux-Firmware package = 1.180
  Nvidia Driver version = 430.34-0ubuntu2

  Issue:
  Problem with kernel 5.2.0-8-generic - Wifi firmware fails to load.  Works 
with 5.0.0.-20-generic kernel.

  Syslog:
  Jul 17 15:13:31 Lappy kernel: [   85.319088] iwlwifi :3b:00.0: Microcode 
SW error detected. Restarting 0x0.
  Jul 17 15:13:31 Lappy kernel: [   85.320158] iwlwifi :3b:00.0: Start IWL 
Error Log Dump:
  Jul 17 15:13:31 Lappy kernel: [   85.320161] iwlwifi :3b:00.0: Status: 
0x0080, count: 6
  Jul 17 15:13:31 Lappy kernel: [   85.320162] iwlwifi :3b:00.0: Loaded 
firmware version: 46.a41adfe7.0
  Jul 17 15:13:31 Lappy kernel: [   85.320164] iwlwifi :3b:00.0: 0x0071 
| NMI_INTERRUPT_UMAC_FATAL
  Jul 17 15:13:31 Lappy kernel: [   85.320166] iwlwifi :3b:00.0: 0x00A022F0 
| trm_hw_status0
  Jul 17 15:13:31 Lappy kernel: [   85.320167] iwlwifi :3b:00.0: 0x 
| trm_hw_status1
  Jul 17 15:13:31 Lappy kernel: [   85.320168] iwlwifi :3b:00.0: 0x004882F2 
| branchlink2
  Jul 17 15:13:31 Lappy kernel: [   85.320169] iwlwifi :3b:00.0: 0x004793A2 
| interruptlink1
  Jul 17 15:13:31 Lappy kernel: [   85.320171] iwlwifi :3b:00.0: 0x00480EA2 
| interruptlink2
  Jul 17 15:13:31 Lappy kernel: [   85.320172] iwlwifi :3b:00.0: 0x0001A7D2 
| data1
  Jul 17 15:13:31 Lappy kernel: [   85.320173] iwlwifi :3b:00.0: 0x1000 
| data2
  Jul 17 15:13:31 Lappy kernel: [   85.320174] iwlwifi :3b:00.0: 0xE008 
| data3
  Jul 17 

[Kernel-packages] [Bug 1848831] Re: Intel WiFi AX200 firmware loading error resulting in no wifi

[Ari]

@vicamo I tested various combinations, here's the dmesg output:

stock 5.3 kernel + iwlwifi backport:
https://paste.ubuntu.com/p/j6WDwqDJcd/


mainline 5.4rc3: https://paste.ubuntu.com/p/VnY6vZvqnC/

mainline 5.4rc3 + backported iwlwifi (there was an error inthe install,
see notes in log): https://paste.ubuntu.com/p/WwpmGmPdvh/

Unfortunately no luck - in all cases the firmware errors out immediately after 
loading.
I noticed the 'trigger' is different with the backported iwlwifi.

FWIW I've seen some old reports of people getting AX200 to work on
ubuntu 19.04 using 'mainline kernels' from June/July this year, and also
19.10 some ppl using the chipset on 19.10 daily builds prior to launch -
this is why I decided to upgrade SW + change wifi card.


I also notice that the mainline iwlwifi module looks for firmware 50, then 49, 
and finally loads 48 which is the one that ubuntu ships. The one in the kernel 
tree is also 48, I wonder if intel keeps a "-next" tree of some sort somewhere 
where versions 49/50 could be present.


I found these kernel bug reports: 

https://bugzilla.kernel.org/show_bug.cgi?id=205123

https://bugzilla.kernel.org/show_bug.cgi?id=204821

They both refer to the use of PCI slot adapters triggering the problem,
which do not apply on my case. Motherboard: ASUS Maximus Gene Viii

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

Title:
  Intel WiFi AX200 firmware loading error resulting in no wifi

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10 - stock kernel - Intel AX200 PCI card in a desktop PC

  uname -a
  Linux nahuatl 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  The card is detected OK as dmesg shows, however the card's firmware
  fails immediately after loading (see dmesg output below) and wifi
  doesn't work at all. Big disappointment since the AX200 chip was
  supposed to be supported on 19.10.

  Ubuntu includes two ax200 firmware versions, version 48 loads by
  default in my system (and fails). I tried version 46 (by renaming the
  version 48 file) and it failed in the exact same manner

  $ ls /lib/firmware/iwlwifi-cc-*
  /lib/firmware/iwlwifi-cc-a0-46.ucode  /lib/firmware/iwlwifi-cc-a0-48.ucode

  
  The card's Bluetooth functionality is also detected and it works fine. It's 
just the wifi FW loading what seems broken in ubuntu's 5.3 kernel.

  $ rfkill list
  0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no



  ~$ dmesg | grep iwl
  [   12.312443] iwlwifi :01:00.0: enabling device ( -> 0002)
  [   12.321098] iwlwifi :01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 
43.2.23.17
  [   12.321101] iwlwifi :01:00.0: Found debug destination: EXTERNAL_DRAM
  [   12.321102] iwlwifi :01:00.0: Found debug configuration: 0
  [   12.321309] iwlwifi :01:00.0: loaded firmware version 48.4fa0041f.0 
op_mode iwlmvm
  [   12.390389] iwlwifi :01:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, 
REV=0x340
  [   12.400654] iwlwifi :01:00.0: Applying debug destination EXTERNAL_DRAM
  [   12.400893] iwlwifi :01:00.0: Allocated 0x0040 bytes for firmware 
monitor.
  [   13.414781] iwlwifi :01:00.0: Collecting data: trigger 15 fired.
  [   13.414908] iwlwifi :01:00.0: Start IWL Error Log Dump:
  [   13.414910] iwlwifi :01:00.0: Status: 0x, count: 6
  [   13.414911] iwlwifi :01:00.0: Loaded firmware version: 48.4fa0041f.0
  [   13.414912] iwlwifi :01:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
  [   13.414913] iwlwifi :01:00.0: 0x002022F0 | trm_hw_status0
  [   13.414913] iwlwifi :01:00.0: 0x | trm_hw_status1
  [   13.414914] iwlwifi :01:00.0: 0x004F8E3C | branchlink2
  [   13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink1
  [   13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink2
  [   13.414916] iwlwifi :01:00.0: 0x004F3DB0 | data1
  [   13.414917] iwlwifi :01:00.0: 0x1000 | data2
  [   13.414917] iwlwifi :01:00.0: 0xF000 | data3
  [   13.414918] iwlwifi :01:00.0: 0x | beacon time
  [   13.414919] iwlwifi :01:00.0: 0x795F | tsf low
  [   13.414919] iwlwifi :01:00.0: 0x | tsf hi
  [   13.414920] iwlwifi :01:00.0: 0x | time gp1
  [   13.414921] iwlwifi :01:00.0: 0xDFD5 | time gp2
  [   13.414921] iwlwifi :01:00.0: 0x0001 | uCode revision type
  [   13.414922] iwlwifi :01:00.0: 0x0030 | uCode version major
  [   13.414923] iwlwifi :01:00.0: 0x4FA0041F | uCode version minor
  [   13.414923] iwlwifi :01:00.0: 0x0340 | hw version
  [   13.414924] iwlwifi :01:00.0: 0x18C89000 | board version
  [   13.414925] iwlwifi :01:00.0: 0x8002FF03 | hcmd
  [   13.414925] iwlwifi :01:00.0: 0x0002 | isr0
  [   13.414926] iwlwifi :01:00.0: 0x | isr1
  [   

[Kernel-packages] [Bug 1848883] Re: Lenovo S130-11IGM Unable to read emmc

[Jim]

attaching 4.15.0-20 lspci output for comparison

** Attachment added: "lspci-vnvn-4.15.0-20.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+attachment/5298448/+files/lspci-vnvn-4.15.0-20.log

** Summary changed:

- Lenovo S130-11IGM Unable to read emmc
+ (Lenovo S130-11IGM) emmc not working in 19.04

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

Title:
  (Lenovo S130-11IGM) emmc not working in 19.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  
  I don't think this is the same issue as ;
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407
  although I have read a lot of issues with emmc disks.

  Booting from lubuntu CD1 19.04 takes about an hour before I get to the
  desktop. The installer runs through to the partitioning sections and
  is able to see the disk, but it fails to create the partitions. The
  laptop has a 32gb emmc disk. There is some kind of timeout during boot
  on the dhpci probe. The only OS/kernel match I have got to work on
  this device is Lubuntu/18.04 4.15.0-20 (every single function works).
  After installing 18.04 there is an auto update to 4.15.0-65 but the
  touchpad stops working so I defaulted grub back to -20 (this failure
  is not caused by libinput or synaptics drivers). Neither kernels have
  a working wifi module but rtl8821ce install fixes this so not an issue
  for me.

  Attaching as many logs as I can grab.. please let me know and
  I'll happily get any other requested logging.

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

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

[Kernel-packages] [Bug 1848883] Re: Lenovo S130-11IGM Unable to read emmc

[Jim]

Adding successful boot from 4.15.0-20  lunbuntu 18.04

** Attachment added: "dmesg-4.15.0-20.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+attachment/5298447/+files/dmesg-4.15.0-20.log

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

Title:
  (Lenovo S130-11IGM) emmc not working in 19.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  
  I don't think this is the same issue as ;
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407
  although I have read a lot of issues with emmc disks.

  Booting from lubuntu CD1 19.04 takes about an hour before I get to the
  desktop. The installer runs through to the partitioning sections and
  is able to see the disk, but it fails to create the partitions. The
  laptop has a 32gb emmc disk. There is some kind of timeout during boot
  on the dhpci probe. The only OS/kernel match I have got to work on
  this device is Lubuntu/18.04 4.15.0-20 (every single function works).
  After installing 18.04 there is an auto update to 4.15.0-65 but the
  touchpad stops working so I defaulted grub back to -20 (this failure
  is not caused by libinput or synaptics drivers). Neither kernels have
  a working wifi module but rtl8821ce install fixes this so not an issue
  for me.

  Attaching as many logs as I can grab.. please let me know and
  I'll happily get any other requested logging.

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

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

[Kernel-packages] [Bug 1848831] Re: Intel WiFi AX200 firmware loading error resulting in no wifi

[Ari]

@vicamo I tested various combinations, here's the dmesg output:

stock 5.3 kernel + iwlwifi backport:
https://paste.ubuntu.com/p/j6WDwqDJcd/


mainline 5.4rc3: https://paste.ubuntu.com/p/VnY6vZvqnC/

mainline 5.4rc3 + backported iwlwifi (there was an error inthe install,
see notes in log): https://paste.ubuntu.com/p/WwpmGmPdvh/

Unfortunately no luck - in all cases the firmware errors out immediately after 
loading.
I noticed the 'trigger' is different with the backported iwlwifi.

FWIW I've seen some old reports of people getting AX200 to work on
ubuntu 19.04 using 'mainline kernels' from June/July this year, and also
19.10 some ppl using the chipset on 19.10 daily builds prior to launch -
this is why I decided to upgrade SW + change wifi card.


I also notice that the mainline iwlwifi module looks for firmware 50, then 49, 
and finally loads 48 which is the one that ubuntu ships. The one in the kernel 
tree is also 48, I wonder if intel keeps a "-next" tree of some sort somewhere 
where versions 49/50 could be present.


I found these kernel bug reports: 

https://bugzilla.kernel.org/show_bug.cgi?id=205123

https://bugzilla.kernel.org/show_bug.cgi?id=204821

They both refer to the use of PCI slot adapters triggering the problem,
which do not apply on my case. Motherboard: ASUS Maximus Gene Viii


** Bug watch added: Linux Kernel Bug Tracker #205123
   https://bugzilla.kernel.org/show_bug.cgi?id=205123

** Bug watch added: Linux Kernel Bug Tracker #204821
   https://bugzilla.kernel.org/show_bug.cgi?id=204821

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

Title:
  Intel WiFi AX200 firmware loading error resulting in no wifi

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10 - stock kernel - Intel AX200 PCI card in a desktop PC

  uname -a
  Linux nahuatl 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  The card is detected OK as dmesg shows, however the card's firmware
  fails immediately after loading (see dmesg output below) and wifi
  doesn't work at all. Big disappointment since the AX200 chip was
  supposed to be supported on 19.10.

  Ubuntu includes two ax200 firmware versions, version 48 loads by
  default in my system (and fails). I tried version 46 (by renaming the
  version 48 file) and it failed in the exact same manner

  $ ls /lib/firmware/iwlwifi-cc-*
  /lib/firmware/iwlwifi-cc-a0-46.ucode  /lib/firmware/iwlwifi-cc-a0-48.ucode

  
  The card's Bluetooth functionality is also detected and it works fine. It's 
just the wifi FW loading what seems broken in ubuntu's 5.3 kernel.

  $ rfkill list
  0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no



  ~$ dmesg | grep iwl
  [   12.312443] iwlwifi :01:00.0: enabling device ( -> 0002)
  [   12.321098] iwlwifi :01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 
43.2.23.17
  [   12.321101] iwlwifi :01:00.0: Found debug destination: EXTERNAL_DRAM
  [   12.321102] iwlwifi :01:00.0: Found debug configuration: 0
  [   12.321309] iwlwifi :01:00.0: loaded firmware version 48.4fa0041f.0 
op_mode iwlmvm
  [   12.390389] iwlwifi :01:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, 
REV=0x340
  [   12.400654] iwlwifi :01:00.0: Applying debug destination EXTERNAL_DRAM
  [   12.400893] iwlwifi :01:00.0: Allocated 0x0040 bytes for firmware 
monitor.
  [   13.414781] iwlwifi :01:00.0: Collecting data: trigger 15 fired.
  [   13.414908] iwlwifi :01:00.0: Start IWL Error Log Dump:
  [   13.414910] iwlwifi :01:00.0: Status: 0x, count: 6
  [   13.414911] iwlwifi :01:00.0: Loaded firmware version: 48.4fa0041f.0
  [   13.414912] iwlwifi :01:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
  [   13.414913] iwlwifi :01:00.0: 0x002022F0 | trm_hw_status0
  [   13.414913] iwlwifi :01:00.0: 0x | trm_hw_status1
  [   13.414914] iwlwifi :01:00.0: 0x004F8E3C | branchlink2
  [   13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink1
  [   13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink2
  [   13.414916] iwlwifi :01:00.0: 0x004F3DB0 | data1
  [   13.414917] iwlwifi :01:00.0: 0x1000 | data2
  [   13.414917] iwlwifi :01:00.0: 0xF000 | data3
  [   13.414918] iwlwifi :01:00.0: 0x | beacon time
  [   13.414919] iwlwifi :01:00.0: 0x795F | tsf low
  [   13.414919] iwlwifi :01:00.0: 0x | tsf hi
  [   13.414920] iwlwifi :01:00.0: 0x | time gp1
  [   13.414921] iwlwifi :01:00.0: 0xDFD5 | time gp2
  [   13.414921] iwlwifi :01:00.0: 0x0001 | uCode revision type
  [   13.414922] iwlwifi :01:00.0: 0x0030 | uCode version major
  [   13.414923] iwlwifi :01:00.0: 0x4FA0041F | uCode version minor
  [   13.414923] iwlwifi :01:00.0: 0x0340 | hw version
  [   13.414924] iwlwifi 

[Kernel-packages] [Bug 1848883] Re: Lenovo S130-11IGM Unable to read emmc

[Jim]

I should point out my reason for trying 19.04 is due to 4.15.0-65
stopping the touchpad working and having to revert back to 4.15.0-20.
Was hoping 19.04 with the 5.0 kernel might resolve the touchpad issue
(which it does). Also tried kernel 5.0.0.31 on 18.04 with exact same
emmc 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/1848883

Title:
  Lenovo S130-11IGM Unable to read emmc

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  
  I don't think this is the same issue as ;
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407
  although I have read a lot of issues with emmc disks.

  Booting from lubuntu CD1 19.04 takes about an hour before I get to the
  desktop. The installer runs through to the partitioning sections and
  is able to see the disk, but it fails to create the partitions. The
  laptop has a 32gb emmc disk. There is some kind of timeout during boot
  on the dhpci probe. The only OS/kernel match I have got to work on
  this device is Lubuntu/18.04 4.15.0-20 (every single function works).
  After installing 18.04 there is an auto update to 4.15.0-65 but the
  touchpad stops working so I defaulted grub back to -20 (this failure
  is not caused by libinput or synaptics drivers). Neither kernels have
  a working wifi module but rtl8821ce install fixes this so not an issue
  for me.

  Attaching as many logs as I can grab.. please let me know and
  I'll happily get any other requested logging.

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

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

[Kernel-packages] [Bug 1848883] Re: Lenovo S130-11IGM Unable to read emmc

[Jim]

xorg log attached to confirm touchpad working under libinput with this
kernel

** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+attachment/5298445/+files/Xorg.0.log

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

Title:
  Lenovo S130-11IGM Unable to read emmc

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  
  I don't think this is the same issue as ;
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407
  although I have read a lot of issues with emmc disks.

  Booting from lubuntu CD1 19.04 takes about an hour before I get to the
  desktop. The installer runs through to the partitioning sections and
  is able to see the disk, but it fails to create the partitions. The
  laptop has a 32gb emmc disk. There is some kind of timeout during boot
  on the dhpci probe. The only OS/kernel match I have got to work on
  this device is Lubuntu/18.04 4.15.0-20 (every single function works).
  After installing 18.04 there is an auto update to 4.15.0-65 but the
  touchpad stops working so I defaulted grub back to -20 (this failure
  is not caused by libinput or synaptics drivers). Neither kernels have
  a working wifi module but rtl8821ce install fixes this so not an issue
  for me.

  Attaching as many logs as I can grab.. please let me know and
  I'll happily get any other requested logging.

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

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

[Kernel-packages] [Bug 1848883] Re: Lenovo S130-11IGM Unable to read emmc

[Jim]

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+attachment/5298441/+files/syslog

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

Title:
  Lenovo S130-11IGM Unable to read emmc

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  
  I don't think this is the same issue as ;
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407
  although I have read a lot of issues with emmc disks.

  Booting from lubuntu CD1 19.04 takes about an hour before I get to the
  desktop. The installer runs through to the partitioning sections and
  is able to see the disk, but it fails to create the partitions. The
  laptop has a 32gb emmc disk. There is some kind of timeout during boot
  on the dhpci probe. The only OS/kernel match I have got to work on
  this device is Lubuntu/18.04 4.15.0-20 (every single function works).
  After installing 18.04 there is an auto update to 4.15.0-65 but the
  touchpad stops working so I defaulted grub back to -20 (this failure
  is not caused by libinput or synaptics drivers). Neither kernels have
  a working wifi module but rtl8821ce install fixes this so not an issue
  for me.

  Attaching as many logs as I can grab.. please let me know and
  I'll happily get any other requested logging.

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

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

[Kernel-packages] [Bug 1848883] Re: Lenovo S130-11IGM Unable to read emmc

[Jim]

** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+attachment/5298443/+files/version.log

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

Title:
  Lenovo S130-11IGM Unable to read emmc

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  
  I don't think this is the same issue as ;
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407
  although I have read a lot of issues with emmc disks.

  Booting from lubuntu CD1 19.04 takes about an hour before I get to the
  desktop. The installer runs through to the partitioning sections and
  is able to see the disk, but it fails to create the partitions. The
  laptop has a 32gb emmc disk. There is some kind of timeout during boot
  on the dhpci probe. The only OS/kernel match I have got to work on
  this device is Lubuntu/18.04 4.15.0-20 (every single function works).
  After installing 18.04 there is an auto update to 4.15.0-65 but the
  touchpad stops working so I defaulted grub back to -20 (this failure
  is not caused by libinput or synaptics drivers). Neither kernels have
  a working wifi module but rtl8821ce install fixes this so not an issue
  for me.

  Attaching as many logs as I can grab.. please let me know and
  I'll happily get any other requested logging.

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

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

[Kernel-packages] [Bug 1848883] Re: Lenovo S130-11IGM Unable to read emmc

[Jim]

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+attachment/5298440/+files/lspci-vnvn.log

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

Title:
  Lenovo S130-11IGM Unable to read emmc

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  
  I don't think this is the same issue as ;
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407
  although I have read a lot of issues with emmc disks.

  Booting from lubuntu CD1 19.04 takes about an hour before I get to the
  desktop. The installer runs through to the partitioning sections and
  is able to see the disk, but it fails to create the partitions. The
  laptop has a 32gb emmc disk. There is some kind of timeout during boot
  on the dhpci probe. The only OS/kernel match I have got to work on
  this device is Lubuntu/18.04 4.15.0-20 (every single function works).
  After installing 18.04 there is an auto update to 4.15.0-65 but the
  touchpad stops working so I defaulted grub back to -20 (this failure
  is not caused by libinput or synaptics drivers). Neither kernels have
  a working wifi module but rtl8821ce install fixes this so not an issue
  for me.

  Attaching as many logs as I can grab.. please let me know and
  I'll happily get any other requested logging.

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

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

[Kernel-packages] [Bug 1848883] Re: Lenovo S130-11IGM Unable to read emmc

[Jim]

mokutil output to confirm secure boot disabled

** Attachment added: "mokutil.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+attachment/5298444/+files/mokutil.log

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

Title:
  Lenovo S130-11IGM Unable to read emmc

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  
  I don't think this is the same issue as ;
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407
  although I have read a lot of issues with emmc disks.

  Booting from lubuntu CD1 19.04 takes about an hour before I get to the
  desktop. The installer runs through to the partitioning sections and
  is able to see the disk, but it fails to create the partitions. The
  laptop has a 32gb emmc disk. There is some kind of timeout during boot
  on the dhpci probe. The only OS/kernel match I have got to work on
  this device is Lubuntu/18.04 4.15.0-20 (every single function works).
  After installing 18.04 there is an auto update to 4.15.0-65 but the
  touchpad stops working so I defaulted grub back to -20 (this failure
  is not caused by libinput or synaptics drivers). Neither kernels have
  a working wifi module but rtl8821ce install fixes this so not an issue
  for me.

  Attaching as many logs as I can grab.. please let me know and
  I'll happily get any other requested logging.

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1848883

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

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

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

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

Title:
  Lenovo S130-11IGM Unable to read emmc

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  
  I don't think this is the same issue as ;
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407
  although I have read a lot of issues with emmc disks.

  Booting from lubuntu CD1 19.04 takes about an hour before I get to the
  desktop. The installer runs through to the partitioning sections and
  is able to see the disk, but it fails to create the partitions. The
  laptop has a 32gb emmc disk. There is some kind of timeout during boot
  on the dhpci probe. The only OS/kernel match I have got to work on
  this device is Lubuntu/18.04 4.15.0-20 (every single function works).
  After installing 18.04 there is an auto update to 4.15.0-65 but the
  touchpad stops working so I defaulted grub back to -20 (this failure
  is not caused by libinput or synaptics drivers). Neither kernels have
  a working wifi module but rtl8821ce install fixes this so not an issue
  for me.

  Attaching as many logs as I can grab.. please let me know and
  I'll happily get any other requested logging.

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

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

[Kernel-packages] [Bug 1848883] Re: Lenovo S130-11IGM Unable to read emmc

[Ubuntu Kernel Bot]

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

** Tags added: disco

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

Title:
  Lenovo S130-11IGM Unable to read emmc

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  
  I don't think this is the same issue as ;
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407
  although I have read a lot of issues with emmc disks.

  Booting from lubuntu CD1 19.04 takes about an hour before I get to the
  desktop. The installer runs through to the partitioning sections and
  is able to see the disk, but it fails to create the partitions. The
  laptop has a 32gb emmc disk. There is some kind of timeout during boot
  on the dhpci probe. The only OS/kernel match I have got to work on
  this device is Lubuntu/18.04 4.15.0-20 (every single function works).
  After installing 18.04 there is an auto update to 4.15.0-65 but the
  touchpad stops working so I defaulted grub back to -20 (this failure
  is not caused by libinput or synaptics drivers). Neither kernels have
  a working wifi module but rtl8821ce install fixes this so not an issue
  for me.

  Attaching as many logs as I can grab.. please let me know and
  I'll happily get any other requested logging.

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

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

[Kernel-packages] [Bug 1848883] Re: Lenovo S130-11IGM Unable to read emmc

[Jim]

dmesg

** Attachment added: "dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+attachment/5298439/+files/dmesg.log

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

Title:
  Lenovo S130-11IGM Unable to read emmc

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  
  I don't think this is the same issue as ;
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407
  although I have read a lot of issues with emmc disks.

  Booting from lubuntu CD1 19.04 takes about an hour before I get to the
  desktop. The installer runs through to the partitioning sections and
  is able to see the disk, but it fails to create the partitions. The
  laptop has a 32gb emmc disk. There is some kind of timeout during boot
  on the dhpci probe. The only OS/kernel match I have got to work on
  this device is Lubuntu/18.04 4.15.0-20 (every single function works).
  After installing 18.04 there is an auto update to 4.15.0-65 but the
  touchpad stops working so I defaulted grub back to -20 (this failure
  is not caused by libinput or synaptics drivers). Neither kernels have
  a working wifi module but rtl8821ce install fixes this so not an issue
  for me.

  Attaching as many logs as I can grab.. please let me know and
  I'll happily get any other requested logging.

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

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

[Kernel-packages] [Bug 1848883] [NEW] Lenovo S130-11IGM Unable to read emmc

[Jim]

Public bug reported:

Hi,


I don't think this is the same issue as ;
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407
although I have read a lot of issues with emmc disks.

Booting from lubuntu CD1 19.04 takes about an hour before I get to the
desktop. The installer runs through to the partitioning sections and is
able to see the disk, but it fails to create the partitions. The laptop
has a 32gb emmc disk. There is some kind of timeout during boot on the
dhpci probe. The only OS/kernel match I have got to work on this device
is Lubuntu/18.04 4.15.0-20 (every single function works). After
installing 18.04 there is an auto update to 4.15.0-65 but the touchpad
stops working so I defaulted grub back to -20 (this failure is not
caused by libinput or synaptics drivers). Neither kernels have a working
wifi module but rtl8821ce install fixes this so not an issue for me.

Attaching as many logs as I can grab.. please let me know and
I'll happily get any other requested logging.

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


** Tags: disco

** Attachment added: "lsb_release.log"
   
https://bugs.launchpad.net/bugs/1848883/+attachment/5298438/+files/lsb_release.log

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

Title:
  Lenovo S130-11IGM Unable to read emmc

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  
  I don't think this is the same issue as ;
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407
  although I have read a lot of issues with emmc disks.

  Booting from lubuntu CD1 19.04 takes about an hour before I get to the
  desktop. The installer runs through to the partitioning sections and
  is able to see the disk, but it fails to create the partitions. The
  laptop has a 32gb emmc disk. There is some kind of timeout during boot
  on the dhpci probe. The only OS/kernel match I have got to work on
  this device is Lubuntu/18.04 4.15.0-20 (every single function works).
  After installing 18.04 there is an auto update to 4.15.0-65 but the
  touchpad stops working so I defaulted grub back to -20 (this failure
  is not caused by libinput or synaptics drivers). Neither kernels have
  a working wifi module but rtl8821ce install fixes this so not an issue
  for me.

  Attaching as many logs as I can grab.. please let me know and
  I'll happily get any other requested logging.

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

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

[Kernel-packages] [Bug 1848632] Re: eoan/linux-azure: 5.3.0-1004.4 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848648
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Saturday, 19. October 2019 06:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   stakeholder-signoff: Pending -- waiting for signoff
+   stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  eoan/linux-azure: 5.3.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Eoan:
  Invalid

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848648
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Saturday, 19. October 2019 06:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848632/+subscriptions

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

[Kernel-packages] [Bug 1811254] Re: HP ProBook 470 G5, LED's in Hotkeys f5, f8 and f11 without function

[kuehhe1]

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

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

Title:
  HP ProBook 470 G5, LED's in Hotkeys f5, f8 and f11 without function

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

Bug description:
  Notebook: HP ProBook 470 G5 (3KZ03EA)
  Distro: Linux Mint 19.1 Tessa
  Desktop: Cinnamon 4.0.8
  Kernel: 4.15.0-43-generic x86_64 bits: 64

  The functions of all hotkeys are given, but the LED's in the [f5]
  Speaker-mute, [f8] Micro-mute and [f11] Wireless on/off Buttons do not
  show the status. Disturbing is also the LED in [f11] permanently lit.

  This is my first bug report to launchpad and I ask for leniency and
  troubleshooting support.

  I created 12 logs, unfortunately the upload did not work at once:

  acpi_listen.txt
  apt-cache-policy
  dmesg.log
  lsb_release
  lsinput.log
  lspci-vnvn.log
  rfkill_list.txt
  udev-db.txt
  version.log
  xev keypress test.txt
  xkbcomp.txt
  xkbmap.txt

  Previous attempts:
  My on-board search for other HP ProBook Hotkey LED-issues led me to this bug 
report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705586

  but the solution to the file: /etc/modprobe.d/alsa-base.conf
  to supplement the entry: options snd-hda-intel mode = mute-led-gpio

  did not lead to the solution here. Presumably, the failure results
  from a different ubuntu-version and/or a another kernel.

  Information: This problem was previously discussed on
  linuxmintusers.de:
  https://www.linuxmintusers.de/index.php?topic=51737.msg710376#msg710376

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

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

[Kernel-packages] [Bug 1819968] Re: Colour banding in Lenovo G50-80 laptop display (i915)

[Alexandru Cosmin]

I've just installed 5.3.7 and the problem persists.

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

Title:
  Colour banding in Lenovo G50-80 laptop display (i915)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Colour bandind is visible everywhere in the system. I believe it's not
  a hardware problem, since booting with 'nomodeset' works as expected
  and the previously installed Ubuntu 14.04 also worked.

  I tried installing kernel 4.18.0-16.17 from ppa:canonical-kernel-
  team/ppa but the problem remained.

  There were already similar bugs,
  https://bugs.launchpad.net/bugs/1749420 ,
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794387 and
  https://bugs.launchpad.net/bugs/1788308, but the fixes provided for
  those bugs did not work for my specific monitor.

  cat /proc/version_signature
  Ubuntu 4.15.0-46.49-generic 4.15.18

  sudo lspci -vnvn
  00:00.0 Host bridge [0600]: Intel Corporation Haswell-ULT DRAM Controller 
[8086:0a04] (rev 0b)
   Subsystem: Lenovo Haswell-ULT DRAM Controller [17aa:390b]
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: hsw_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT 
Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:390b]
   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/1819968/+subscriptions

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

[Kernel-packages] [Bug 1848857] Re: iwlwifi - repeated kernel OOPS when wifi turned on

[You-Sheng Yang]

This seems a duplicate of bug 1846016 to me. Could you try
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc2/ ?

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

Title:
  iwlwifi - repeated kernel OOPS when wifi turned on

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a fresh 19.10 install, I get repeated (every ~10s) kernel
  backtraces when wifi is enabled

  This is an example of the trace:

  [ 3963.367576] iwlwifi :04:00.0: Failed to get geographic profile info -5
  [ 3963.367591] [ cut here ]
  [ 3963.367660] WARNING: CPU: 3 PID: 27181 at 
drivers/net/wireless/intel/iwlwifi/mvm/scan.c:1874 
iwl_mvm_rx_umac_scan_complete_notif.cold+0xc/0x13 [iwlmvm]
  [ 3963.367662] Modules linked in: unix_diag rfcomm scsi_transport_iscsi 
binfmt_misc veth ccm xt_comment dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack 
ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle 
iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables 
nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc 
aufs overlay cmac bnep nls_iso8859_1 intel_rapl_m
  sr mei_hdcp snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi 
snd_hda_codec_hdmi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine 
snd_hda_codec_realtek snd_usb_audio snd_hda_codec_generic snd_usbmidi_lib 
snd_hda_intel snd_seq_midi snd_hda_codec snd_seq_midi_event snd_hda_core 
snd_hwdep snd_pcm intel_rapl_common x86_pkg_temp_thermal intel_
  powerclamp snd_rawmidi iwlmvm coretemp snd_seq mac80211 kvm_intel libarc4 kvm 
iwlwifi irqbypass snd_seq_device intel_cstate intel_rapl_perf snd_timer
  [ 3963.367710]  thinkpad_acpi serio_raw cfg80211 nvram uvcvideo wmi_bmof 
btusb videobuf2_vmalloc joydev rtsx_pci_ms mei_me ledtrig_audio memstick 
input_leds mei btrtl videobuf2_memops intel_pch_thermal btbcm videobuf2_v4l2 
btintel videobuf2_common bluetooth videodev mc snd ecdh_generic ecc 
intel_xhci_usb_role_switch roles soundcore mac_hid sch_fq_codel parport_pc 
ppdev lp parport ip_tables x_tables autofs4 btrfs xor zstd_c
  ompress raid6_pq libcrc32c dm_crypt hid_lenovo hid_generic usbhid hid 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 aesni_intel aes_x86_64 
crypto_simd i2c_algo_bit ahci rtsx_pci_sdmmc libahci drm_kms_helper cryptd 
glue_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse e1000e drm 
i2c_i801 rtsx_pci wmi video
  [ 3963.367764] CPU: 3 PID: 27181 Comm: kworker/3:0 Tainted: GW
 5.3.0-18-generic #19-Ubuntu
  [ 3963.367766] Hardware name: LENOVO 20F6CTO1WW/20F6CTO1WW, BIOS R02ET71W 
(1.44 ) 05/08/2019
  [ 3963.367782] Workqueue: events iwl_mvm_async_handlers_wk [iwlmvm]
  [ 3963.367806] RIP: 0010:iwl_mvm_rx_umac_scan_complete_notif.cold+0xc/0x13 
[iwlmvm]
  [ 3963.367810] Code: 48 c7 c7 00 19 ea c0 e8 df 7c e7 ec 0f 0b 49 8b 47 10 44 
8b a0 9c 00 00 00 e9 a2 3e fe ff 48 c7 c7 00 19 ea c0 e8 c1 7c e7 ec <0f> 0b e9 
dc 43 fe ff 48 c7 c7 00 19 ea c0 e8 ae 7c e7 ec 0f 0b 41
  [ 3963.367813] RSP: 0018:b5498370bdd0 EFLAGS: 00010246
  [ 3963.367816] RAX: 0024 RBX: 967ee2199040 RCX: 
0006
  [ 3963.367818] RDX:  RSI: 0082 RDI: 
9681b1397440
  [ 3963.367820] RBP: b5498370be08 R08: 0729 R09: 
0004
  [ 3963.367822] R10:  R11: 0001 R12: 
b5498370be20
  [ 3963.367823] R13: 9681a5049e28 R14:  R15: 
9681755c3b00
  [ 3963.367826] FS:  () GS:9681b138() 
knlGS:
  [ 3963.367829] CS:  0010 DS:  ES:  CR0: 80050033
  [ 3963.367831] CR2: 08e554b32000 CR3: 00037a00a001 CR4: 
003606e0
  [ 3963.367833] DR0:  DR1:  DR2: 

  [ 3963.367835] DR3:  DR6: fffe0ff0 DR7: 
0400
  [ 3963.367837] Call Trace:
  [ 3963.367853]  iwl_mvm_async_handlers_wk+0xb0/0x140 [iwlmvm]
  [ 3963.367859]  process_one_work+0x1db/0x380
  [ 3963.367863]  worker_thread+0x4d/0x400
  [ 3963.367869]  kthread+0x104/0x140
  [ 3963.367873]  ? process_one_work+0x380/0x380
  [ 3963.367878]  ? kthread_park+0x80/0x80
  [ 3963.367884]  ret_from_fork+0x35/0x40
  [ 3963.367889] ---[ end trace d7c13f3a9f33f0d0 ]---
  [ 3963.941981] iwlwifi :04:00.0: Applying debug destination EXTERNAL_DRAM
  [ 3964.090765] iwlwifi :04:00.0: Applying debug destination EXTERNAL_DRAM
  [ 3964.173015] iwlwifi :04:00.0: FW already configured (0) - 
re-configuring

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-generic 5.3.0.18.21
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: 

[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

[Ulf Dellbrügge]

I tested MX Linux for the past weeks and it was stable as a whole, but
WLAN, bluetooth and USB often dissapeared for no reason and forced me to
reboot.

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Triaged

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions

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

[Kernel-packages] [Bug 1848857] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  iwlwifi - repeated kernel OOPS when wifi turned on

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a fresh 19.10 install, I get repeated (every ~10s) kernel
  backtraces when wifi is enabled

  This is an example of the trace:

  [ 3963.367576] iwlwifi :04:00.0: Failed to get geographic profile info -5
  [ 3963.367591] [ cut here ]
  [ 3963.367660] WARNING: CPU: 3 PID: 27181 at 
drivers/net/wireless/intel/iwlwifi/mvm/scan.c:1874 
iwl_mvm_rx_umac_scan_complete_notif.cold+0xc/0x13 [iwlmvm]
  [ 3963.367662] Modules linked in: unix_diag rfcomm scsi_transport_iscsi 
binfmt_misc veth ccm xt_comment dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack 
ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle 
iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables 
nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc 
aufs overlay cmac bnep nls_iso8859_1 intel_rapl_m
  sr mei_hdcp snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi 
snd_hda_codec_hdmi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine 
snd_hda_codec_realtek snd_usb_audio snd_hda_codec_generic snd_usbmidi_lib 
snd_hda_intel snd_seq_midi snd_hda_codec snd_seq_midi_event snd_hda_core 
snd_hwdep snd_pcm intel_rapl_common x86_pkg_temp_thermal intel_
  powerclamp snd_rawmidi iwlmvm coretemp snd_seq mac80211 kvm_intel libarc4 kvm 
iwlwifi irqbypass snd_seq_device intel_cstate intel_rapl_perf snd_timer
  [ 3963.367710]  thinkpad_acpi serio_raw cfg80211 nvram uvcvideo wmi_bmof 
btusb videobuf2_vmalloc joydev rtsx_pci_ms mei_me ledtrig_audio memstick 
input_leds mei btrtl videobuf2_memops intel_pch_thermal btbcm videobuf2_v4l2 
btintel videobuf2_common bluetooth videodev mc snd ecdh_generic ecc 
intel_xhci_usb_role_switch roles soundcore mac_hid sch_fq_codel parport_pc 
ppdev lp parport ip_tables x_tables autofs4 btrfs xor zstd_c
  ompress raid6_pq libcrc32c dm_crypt hid_lenovo hid_generic usbhid hid 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 aesni_intel aes_x86_64 
crypto_simd i2c_algo_bit ahci rtsx_pci_sdmmc libahci drm_kms_helper cryptd 
glue_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse e1000e drm 
i2c_i801 rtsx_pci wmi video
  [ 3963.367764] CPU: 3 PID: 27181 Comm: kworker/3:0 Tainted: GW
 5.3.0-18-generic #19-Ubuntu
  [ 3963.367766] Hardware name: LENOVO 20F6CTO1WW/20F6CTO1WW, BIOS R02ET71W 
(1.44 ) 05/08/2019
  [ 3963.367782] Workqueue: events iwl_mvm_async_handlers_wk [iwlmvm]
  [ 3963.367806] RIP: 0010:iwl_mvm_rx_umac_scan_complete_notif.cold+0xc/0x13 
[iwlmvm]
  [ 3963.367810] Code: 48 c7 c7 00 19 ea c0 e8 df 7c e7 ec 0f 0b 49 8b 47 10 44 
8b a0 9c 00 00 00 e9 a2 3e fe ff 48 c7 c7 00 19 ea c0 e8 c1 7c e7 ec <0f> 0b e9 
dc 43 fe ff 48 c7 c7 00 19 ea c0 e8 ae 7c e7 ec 0f 0b 41
  [ 3963.367813] RSP: 0018:b5498370bdd0 EFLAGS: 00010246
  [ 3963.367816] RAX: 0024 RBX: 967ee2199040 RCX: 
0006
  [ 3963.367818] RDX:  RSI: 0082 RDI: 
9681b1397440
  [ 3963.367820] RBP: b5498370be08 R08: 0729 R09: 
0004
  [ 3963.367822] R10:  R11: 0001 R12: 
b5498370be20
  [ 3963.367823] R13: 9681a5049e28 R14:  R15: 
9681755c3b00
  [ 3963.367826] FS:  () GS:9681b138() 
knlGS:
  [ 3963.367829] CS:  0010 DS:  ES:  CR0: 80050033
  [ 3963.367831] CR2: 08e554b32000 CR3: 00037a00a001 CR4: 
003606e0
  [ 3963.367833] DR0:  DR1:  DR2: 

  [ 3963.367835] DR3:  DR6: fffe0ff0 DR7: 
0400
  [ 3963.367837] Call Trace:
  [ 3963.367853]  iwl_mvm_async_handlers_wk+0xb0/0x140 [iwlmvm]
  [ 3963.367859]  process_one_work+0x1db/0x380
  [ 3963.367863]  worker_thread+0x4d/0x400
  [ 3963.367869]  kthread+0x104/0x140
  [ 3963.367873]  ? process_one_work+0x380/0x380
  [ 3963.367878]  ? kthread_park+0x80/0x80
  [ 3963.367884]  ret_from_fork+0x35/0x40
  [ 3963.367889] ---[ end trace d7c13f3a9f33f0d0 ]---
  [ 3963.941981] iwlwifi :04:00.0: Applying debug destination EXTERNAL_DRAM
  [ 3964.090765] iwlwifi :04:00.0: Applying debug destination EXTERNAL_DRAM
  [ 3964.173015] iwlwifi :04:00.0: FW already configured (0) - 
re-configuring

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-generic 5.3.0.18.21
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: 

[Kernel-packages] [Bug 1848857] [NEW] iwlwifi - repeated kernel OOPS when wifi turned on

[Alberto Donato]

Public bug reported:

On a fresh 19.10 install, I get repeated (every ~10s) kernel backtraces
when wifi is enabled

This is an example of the trace:

[ 3963.367576] iwlwifi :04:00.0: Failed to get geographic profile info -5
[ 3963.367591] [ cut here ]
[ 3963.367660] WARNING: CPU: 3 PID: 27181 at 
drivers/net/wireless/intel/iwlwifi/mvm/scan.c:1874 
iwl_mvm_rx_umac_scan_complete_notif.cold+0xc/0x13 [iwlmvm]
[ 3963.367662] Modules linked in: unix_diag rfcomm scsi_transport_iscsi 
binfmt_misc veth ccm xt_comment dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack 
ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle 
iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables 
nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc 
aufs overlay cmac bnep nls_iso8859_1 intel_rapl_m
sr mei_hdcp snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi 
snd_hda_codec_hdmi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine 
snd_hda_codec_realtek snd_usb_audio snd_hda_codec_generic snd_usbmidi_lib 
snd_hda_intel snd_seq_midi snd_hda_codec snd_seq_midi_event snd_hda_core 
snd_hwdep snd_pcm intel_rapl_common x86_pkg_temp_thermal intel_
powerclamp snd_rawmidi iwlmvm coretemp snd_seq mac80211 kvm_intel libarc4 kvm 
iwlwifi irqbypass snd_seq_device intel_cstate intel_rapl_perf snd_timer
[ 3963.367710]  thinkpad_acpi serio_raw cfg80211 nvram uvcvideo wmi_bmof btusb 
videobuf2_vmalloc joydev rtsx_pci_ms mei_me ledtrig_audio memstick input_leds 
mei btrtl videobuf2_memops intel_pch_thermal btbcm videobuf2_v4l2 btintel 
videobuf2_common bluetooth videodev mc snd ecdh_generic ecc 
intel_xhci_usb_role_switch roles soundcore mac_hid sch_fq_codel parport_pc 
ppdev lp parport ip_tables x_tables autofs4 btrfs xor zstd_c
ompress raid6_pq libcrc32c dm_crypt hid_lenovo hid_generic usbhid hid 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 aesni_intel aes_x86_64 
crypto_simd i2c_algo_bit ahci rtsx_pci_sdmmc libahci drm_kms_helper cryptd 
glue_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse e1000e drm 
i2c_i801 rtsx_pci wmi video
[ 3963.367764] CPU: 3 PID: 27181 Comm: kworker/3:0 Tainted: GW 
5.3.0-18-generic #19-Ubuntu
[ 3963.367766] Hardware name: LENOVO 20F6CTO1WW/20F6CTO1WW, BIOS R02ET71W (1.44 
) 05/08/2019
[ 3963.367782] Workqueue: events iwl_mvm_async_handlers_wk [iwlmvm]
[ 3963.367806] RIP: 0010:iwl_mvm_rx_umac_scan_complete_notif.cold+0xc/0x13 
[iwlmvm]
[ 3963.367810] Code: 48 c7 c7 00 19 ea c0 e8 df 7c e7 ec 0f 0b 49 8b 47 10 44 
8b a0 9c 00 00 00 e9 a2 3e fe ff 48 c7 c7 00 19 ea c0 e8 c1 7c e7 ec <0f> 0b e9 
dc 43 fe ff 48 c7 c7 00 19 ea c0 e8 ae 7c e7 ec 0f 0b 41
[ 3963.367813] RSP: 0018:b5498370bdd0 EFLAGS: 00010246
[ 3963.367816] RAX: 0024 RBX: 967ee2199040 RCX: 0006
[ 3963.367818] RDX:  RSI: 0082 RDI: 9681b1397440
[ 3963.367820] RBP: b5498370be08 R08: 0729 R09: 0004
[ 3963.367822] R10:  R11: 0001 R12: b5498370be20
[ 3963.367823] R13: 9681a5049e28 R14:  R15: 9681755c3b00
[ 3963.367826] FS:  () GS:9681b138() 
knlGS:
[ 3963.367829] CS:  0010 DS:  ES:  CR0: 80050033
[ 3963.367831] CR2: 08e554b32000 CR3: 00037a00a001 CR4: 003606e0
[ 3963.367833] DR0:  DR1:  DR2: 
[ 3963.367835] DR3:  DR6: fffe0ff0 DR7: 0400
[ 3963.367837] Call Trace:
[ 3963.367853]  iwl_mvm_async_handlers_wk+0xb0/0x140 [iwlmvm]
[ 3963.367859]  process_one_work+0x1db/0x380
[ 3963.367863]  worker_thread+0x4d/0x400
[ 3963.367869]  kthread+0x104/0x140
[ 3963.367873]  ? process_one_work+0x380/0x380
[ 3963.367878]  ? kthread_park+0x80/0x80
[ 3963.367884]  ret_from_fork+0x35/0x40
[ 3963.367889] ---[ end trace d7c13f3a9f33f0d0 ]---
[ 3963.941981] iwlwifi :04:00.0: Applying debug destination EXTERNAL_DRAM
[ 3964.090765] iwlwifi :04:00.0: Applying debug destination EXTERNAL_DRAM
[ 3964.173015] iwlwifi :04:00.0: FW already configured (0) - re-configuring

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-generic 5.3.0.18.21
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Oct 19 16:37:59 2019
InstallationDate: Installed on 2019-10-19 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 20F6CTO1WW
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic 
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-18-generic N/A
 linux-backports-modules-5.3.0-18-generic  N/A
 

[Kernel-packages] [Bug 1848790] Re: USB not working under arm64 on Pi4

[Alexander Agnarson]

Reported and discussed here too:
https://bugs.launchpad.net/ubuntu/+bug/1848703

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

Title:
  USB not working under arm64 on Pi4

Status in linux-raspi2 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard
  which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10
  armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the
  keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the
  keyboard worked successfully.

  Output of lsusb under arm64 on a Pi 3:

  ubuntu@ubuntu:~$ lsusb
  Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard
  Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
  Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of lsusb under armhf on a Pi 4 (same keyboard attached):

  ubuntu@ubuntu:~$ lsusb
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard
  Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of lsusb under arm64 on the same Pi 4 (same keyboard attached):

  ubuntu@ubuntu:~$ lsusb
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  The fact even the VIA Labs hub doesn't show up (which is built in)
  suggests the kernel is (for some reason) unable to enumerate anything
  against the USB hubs.

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

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

[Kernel-packages] [Bug 1848848] [NEW] Firmware for Radeon RX5700 (navi10) missing / boot failure

[Christian Borss]

Public bug reported:

As an owner of a Radeon RX5700 GPU, I was really looking forward to the
Eoan release which includes the Linux Kernel 5.3 and Mesa 19.2 - both
with finally Radeon RX5700 (navi10) support. However, upgrading my
system from Kubuntu 18.10 (working) via 19.04 (does not boot) to 19.10
resulted in a boot failure. Last message shown on the screen is:

fb0: switching to amdgpudrmfb from EFI VGA

After some research I found that the package linux-firmware does not
include the necessary files /lib/firmware/amdgpu/navi10_*. After I
manually copied the missing files from the repository
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git, I was able to boot normally.

Please update the package linux-firmware and add the needed firmware.


$ lsb_release -rd
Description:Ubuntu 19.10
Release:19.10
$ apt-cache policy linux-firmware
linux-firmware:
  Installiert:   1.183
  Installationskandidat: 1.183
  Versionstabelle:
 *** 1.183 500
500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
500 http://de.archive.ubuntu.com/ubuntu eoan/main i386 Packages
100 /var/lib/dpkg/status

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


** Tags: amdgpudrmfb navi10 radeon rx5700

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

Title:
  Firmware for Radeon RX5700 (navi10) missing / boot failure

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  As an owner of a Radeon RX5700 GPU, I was really looking forward to
  the Eoan release which includes the Linux Kernel 5.3 and Mesa 19.2 -
  both with finally Radeon RX5700 (navi10) support. However, upgrading
  my system from Kubuntu 18.10 (working) via 19.04 (does not boot) to
  19.10 resulted in a boot failure. Last message shown on the screen is:

  fb0: switching to amdgpudrmfb from EFI VGA

  After some research I found that the package linux-firmware does not
  include the necessary files /lib/firmware/amdgpu/navi10_*. After I
  manually copied the missing files from the repository
  git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git, I was able to boot normally.

  Please update the package linux-firmware and add the needed firmware.

  
  $ lsb_release -rd
  Description:Ubuntu 19.10
  Release:19.10
  $ apt-cache policy linux-firmware
  linux-firmware:
Installiert:   1.183
Installationskandidat: 1.183
Versionstabelle:
   *** 1.183 500
  500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu eoan/main i386 Packages
  100 /var/lib/dpkg/status

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

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

[Kernel-packages] [Bug 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts

[M]

I've tried to (1) boot the same machine with kernel 5.0.0.32 (2) create
new machine without upgrading from 19.04

Results were the same, anybody?

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

Title:
  [Microsoft Hyper-V guest] System shows graphic artifacts for a moment,
  then text cursor for about minute and then starts

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  New

Bug description:
  AFter upgrade system shows graphic artefacts for a moment and then
  text cursor for about minute (it looks like hanged) and then starts.

  In 19.04 startup required 1 or 2 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 17:42:27 2019
  InstallationDate: Installed on 2019-07-04 (104 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-10-17 17:03:47,139 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  InstallationDate: Installed on 2019-07-04 (105 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: xorg-server (not installed)
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=17409d40-25e9-4051-9fd9-758e2a02ebc3 ro quiet splash 
video=hyperv_fb:1900x900 elevator=noop vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  RfKill:
   
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-18-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 2831-3616-6111-5725-4803-1162-28
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.0
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1847212] Re: touchpad not working after upgrade to 5.0.0-31 kernel

[Kai-Heng Feng]

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

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

Title:
  touchpad not working after upgrade to 5.0.0-31 kernel

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  touchpad is not avaliable after upgrade to linux-image-5.0.0-31-generic
  It works on 5.0.0-29 kernel.
  Laptop model: MSI GS40 6QE-091RU

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-31-generic 5.0.0-31.33
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vkovalen   1900 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Oct  8 10:37:31 2019
  InstallationDate: Installed on 2019-05-18 (142 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 004: ID 0cf3:e300 Qualcomm Atheros Communications 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Micro-Star International Co., Ltd. GS40 6QE Phantom
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=84c66d52-4ba6-49d7-8d50-e582f93d9b5c ro quiet nouveau.modeset=0 
rd.driver.blacklist=nouveau acpi_osi=! "acpi_osi=Windows 2009" 
acpi_backlight=vendor resume=UUID=f7c3465a-6b62-428f-8477-67b678e6fe6e
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-31-generic N/A
   linux-backports-modules-5.0.0-31-generic  N/A
   linux-firmware1.178.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E14A1IMS.113
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-14A1
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE14A1IMS.113:bd01/15/2018:svnMicro-StarInternationalCo.,Ltd.:pnGS406QEPhantom:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14A1:rvrREV0.C:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: GS40 6QE Phantom
  dmi.product.sku: Default string
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Kernel-packages] [Bug 1842320] Re: Out of Memory on boot with 5.2.0 kernel

[Steven Mackenzie]

I have a similar issue. I upgraded to 19.10 from 19.04 today.

After grub, I get this message:

"error: out of memory.
Press any key to continue..."

Then kernel panic message (image attached).

I have been unable to successfully boot using the workaround above.

The kernel is shown in grub is 5.3.0-18.
My computer is an Intel NUC (Skull Canyon), 16GB RAM, Intel NVMe, 2 x 2560 x 
1440 displays.

** Attachment added: "Kernel panic screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/+attachment/5298357/+files/IMG_20191019_174025.jpg

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

Title:
  Out of Memory on boot with 5.2.0 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgraded from 19.04 to current 19.10 using "do-release-upgrade -d".
  Can still boot using the previous 5.0.0-25-generic kernel, but the
  5.2.0-15-generic fails to start.

  On selecting Ubuntu from Grub, the message "error: out of memory." is
  immediately shown. Pressing a key attempts to start boot-up but fails
  to mount root fs.

  Machine is HP Spectre X360 with 8GB RAM. Under kernel 5.0.0, free
  shows the following (run from Gnome terminal):

    totalusedfree  shared  buff/cache   
available
  Mem:7906564 1761196 3833240 1020216 2312128 
4849224
  Swap:   1003516   0 1003516

  Kernel packages installed:

  linux-generic  5.2.0.15.16 amd64
  linux-headers-5.2.0-15 5.2.0-15.16 all
  linux-headers-5.2.0-15-generic 5.2.0-15.16 amd64
  linux-headers-generic  5.2.0.15.16 amd64
  linux-image-5.0.0-25-generic   5.0.0-25.26 amd64
  linux-image-5.2.0-15-generic   5.2.0-15.16+signed1 amd64
  linux-image-generic5.2.0.15.16 amd64
  linux-modules-5.0.0-25-generic 5.0.0-25.26 amd64
  linux-modules-5.2.0-15-generic 5.2.0-15.16 amd64
  linux-modules-extra-5.0.0-25-generic   5.0.0-25.26 amd64
  linux-modules-extra-5.2.0-15-generic   5.2.0-15.16 amd64

  Photo of kernel panic attached.

  NVMe drive partition layout (GPT):

  Device   StartEnd   Sectors   Size Type
  /dev/nvme0n1p120481050623   1048576   512M EFI System
  /dev/nvme0n1p2 10506242549759   1499136   732M Linux filesystem
  /dev/nvme0n1p3 2549760 1000214527 997664768 475.7G Linux filesystem

  $ sudo pvs
    PV  VGFmt  Attr PSizePFree
    /dev/mapper/nvme0n1p3_crypt ubuntu-vg lvm2 a--  <475.71g0

  $ sudo lvs
    LV VGAttr   LSize   Pool Origin Data%  Meta%  Move Log 
Cpy%Sync Convert
    root   ubuntu-vg -wi-ao 474.75g
    swap_1 ubuntu-vg -wi-ao 980.00m

  Partition 3 is LUKS encrypted. Root LV is ext4.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gmckeown   1647 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-08-15 (18 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd HP Wide Vision 
FHD Camera
   Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-25-generic N/A
   linux-backports-modules-5.0.0-25-generic  N/A
   linux-firmware1.181
  Tags:  eoan
  Uname: Linux 5.0.0-25-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-02 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/17/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.43
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.25:bd05/17/2019:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.43:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.product.sku: 2QH38EA#ABU
  dmi.sys.vendor: HP

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1848635] Re: eoan/linux-gcp: 5.3.0-1005.5 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Incomplete

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848648
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Saturday, 19. October 2019 06:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  eoan/linux-gcp: 5.3.0-1005.5 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848648
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Saturday, 19. October 2019 06:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848635/+subscriptions

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

[Kernel-packages] [Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU)

[Mathew Hodson]

** Project changed: gnome-shell => gdm

** No longer affects: gnome-shell (Ubuntu)

** No longer affects: mutter (Ubuntu)

** No longer affects: nvidia-graphics-drivers-375 (Ubuntu)

** No longer affects: nvidia-graphics-drivers-384 (Ubuntu)

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

Title:
  Ubuntu boots to blank screen when using Nvidia (on a desktop with an
  unused Intel GPU)

Status in gdm:
  Fix Released
Status in gdm3 package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu boots to blank screen when using Nvidia drivers (on a desktop
  with an unused Intel GPU).

  WORKAROUNDS (you only need one):

  * Uncomment #WaylandEnable=false in /etc/gdm3/custom.conf

  * Disable integrated graphics/GPU in your BIOS

  * Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then
    run:  sudo update-initramfs
    and reboot.

  * Add a line to /usr/lib/udev/rules.d/61-gdm.rules:
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"

  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1705369/+subscriptions

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

[Kernel-packages] [Bug 1572132] Re: SMBv2+ does not show all files when mounting a windows share

[Mathew Hodson]

** Also affects: ubuntu-release-notes
   Importance: Undecided
   Status: New

** Changed in: ubuntu-release-notes
   Status: New => Fix Released

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

Title:
  SMBv2+ does not show all files when mounting a windows share

Status in Linux:
  Unknown
Status in Release Notes for Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Debian:
  Confirmed

Bug description:
  When using the SMBv2 Protocol to mount a top level windows share (such
  as C:\) not all files (or directories) are shown that exist  on the
  server side. Exactly 2 files are always missing...

  Steps to reproduce:
  On a windows7 PC (or Server) e.g. C:\ must be published as Share (must be top 
level share - a subfolder like C:\data\ seems to work)

  sudo mount -t cifs //SERVER/SHARE_NAME /mnt -o
  domain=DOMAIN_NAME,username=${USER},uid=1000,gid=1000,nounix,vers=2.0

  As a result always 2 Files (or directories) are missing in the mounted
  directory of the ubuntu installation.

  Seems to be a kernel bug (source tree: linux/fs/cifs).

  The ubuntu versions I have checked:
  Ubuntu 14.04LTS amd64
  Ubuntu 15.10 amd64
  Ubuntu 16.04 amd64

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.12
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Tue Apr 19 14:50:02 2016
  InstallationDate: Installed on 2016-04-19 (0 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160417.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1842037] Re: Oops when Kerberos credentials are invalid

[Matthew Ruffell]

Hi Frank,

It has been 9 days, or slightly over a week since you applied the respun
test kernel to your systems.

Are your systems stable now? Are they suffering any symptoms of Bug
1842037 or Bug 1828978?

Is the test kernel more stable than regular released Ubuntu kernels? Do
you think the patches you requested fix the problems you were having?

Does the test kernel still crash when mis-behaving NFS clients connect?

Let me know how the respun test kernel is going. If things are good, I
can begin the process of getting the patches into an official Ubuntu
kernel. If things are not good, if you provide some logs of call traces
you are seeing, we can keep working on solving your problem.

Thanks,
Matthew

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

Title:
  Oops when Kerberos credentials are invalid

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Disco:
  In Progress

Bug description:
  There's a bug in Linux Kernel 5.0 which is triggered by invalid
  credentials when the NFS clients is trying to aquire them via GSSD.
  This affects NFS-Shares that are protected by krb5* security. They
  become unusable until the system is re-booted. The problem is quite
  severe on terminal servers with multiple users - some of them not
  caring about refreshing their kerberos tickets.

  A fix is available here:

  


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

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

[Kernel-packages] [Bug 1846128] Re: xenial/linux-deeplens: 4.15.0-1010.10 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846130
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
- phase: Testing
- phase-changed: Friday, 18. October 2019 16:25 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Saturday, 19. October 2019 07:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- cycle not ready to release
  variant: debs

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

Title:
  xenial/linux-deeplens: 4.15.0-1010.10 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846130
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
  phase: Holding before Promote to Updates
  phase-changed: Saturday, 19. October 2019 07:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- cycle not ready to release
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846128/+subscriptions

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

[Kernel-packages] [Bug 1848648] Re: eoan/linux: 5.3.0-19.20 -proposed tracker

[Steve Beattie]

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

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  eoan/linux: 5.3.0-19.20 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 19. October 2019 06:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe-edge: bug 1848645
eoan/linux-aws: bug 1848631
eoan/linux-azure: bug 1848632
eoan/linux-gcp: bug 1848635
eoan/linux-kvm: bug 1848642
eoan/linux-oracle: bug 1848644
eoan/linux-raspi2: bug 1848630
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848648/+subscriptions

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

[Kernel-packages] [Bug 1848631] Re: eoan/linux-aws: 5.3.0-1004.4 -proposed tracker

[Steve Beattie]

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

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  eoan/linux-aws: 5.3.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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-lrm 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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Eoan:
  Invalid

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848648
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Saturday, 19. October 2019 00:15 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848631/+subscriptions

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

[Kernel-packages] [Bug 1848632] Re: eoan/linux-azure: 5.3.0-1004.4 -proposed tracker

[Steve Beattie]

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

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  eoan/linux-azure: 5.3.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Eoan:
  Invalid

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848648
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Saturday, 19. October 2019 06:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848632/+subscriptions

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

[Kernel-packages] [Bug 1848630] Re: eoan/linux-raspi2: 5.3.0-1008.9 -proposed tracker

[Steve Beattie]

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

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: (unassigned) => Steve Beattie (sbeattie)

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

Title:
  eoan/linux-raspi2: 5.3.0-1008.9 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848648
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Saturday, 19. October 2019 00:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848630/+subscriptions

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

[Kernel-packages] [Bug 1848642] Re: eoan/linux-kvm: 5.3.0-1004.4 -proposed tracker

[Steve Beattie]

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

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  eoan/linux-kvm: 5.3.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Eoan:
  Invalid

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848648
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Testing
  phase-changed: Saturday, 19. October 2019 00:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848642/+subscriptions

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

[Kernel-packages] [Bug 1848635] Re: eoan/linux-gcp: 5.3.0-1005.5 -proposed tracker

[Steve Beattie]

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

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  eoan/linux-gcp: 5.3.0-1005.5 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Eoan:
  Invalid

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848648
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Saturday, 19. October 2019 06:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848635/+subscriptions

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

[Kernel-packages] [Bug 1846128] Re: xenial/linux-deeplens: 4.15.0-1010.10 -proposed tracker

[Gavin Lin]

Kernel deb testing completes, no regressions found. Ready for Updates. Results 
here:
DeepLens:
https://certification.canonical.com/hardware/201801-26078/submission/152906/
DeepRacer:
https://certification.canonical.com/hardware/201903-26883/submission/152905/

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

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

Title:
  xenial/linux-deeplens: 4.15.0-1010.10 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846130
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
  phase: Holding before Promote to Updates
  phase-changed: Saturday, 19. October 2019 07:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- cycle not ready to release
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846128/+subscriptions

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

[Kernel-packages] [Bug 1848648] Re: eoan/linux: 5.3.0-19.20 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Incomplete

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 19. October 2019 06:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe-edge: bug 1848645
eoan/linux-aws: bug 1848631
eoan/linux-azure: bug 1848632
eoan/linux-gcp: bug 1848635
eoan/linux-kvm: bug 1848642
eoan/linux-oracle: bug 1848644
eoan/linux-raspi2: bug 1848630
  variant: debs

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

Title:
  eoan/linux: 5.3.0-19.20 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 19. October 2019 06:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe-edge: bug 1848645
eoan/linux-aws: bug 1848631
eoan/linux-azure: bug 1848632
eoan/linux-gcp: bug 1848635
eoan/linux-kvm: bug 1848642
eoan/linux-oracle: bug 1848644
eoan/linux-raspi2: bug 1848630
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848648/+subscriptions

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

[Kernel-packages] [Bug 1848642] Re: eoan/linux-kvm: 5.3.0-1004.4 -proposed tracker

[Ubuntu Kernel Bot]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848648
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Testing
  phase-changed: Saturday, 19. October 2019 00:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  eoan/linux-kvm: 5.3.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Eoan:
  Invalid

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848648
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Testing
  phase-changed: Saturday, 19. October 2019 00:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848642/+subscriptions

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

[Kernel-packages] [Bug 1730924]

[gbhat]

Hi Andy,

>PCI core *does* the same (*) for you already.

OK; I see, with this change, command timeout is not recreated; without
this change, just after second iteration I see the issue(as given in
comment#103);

>Does it mean we have some race there?
I need to understand more on this; I was just trying this change because, 
different open source wireless drivers have this in their resume handler;

Regards,
Ganapathi

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

Title:
  Wifi does down "crash" in Surface Pro 4

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

Bug description:
  I have a Surface Pro 4. The wifi works well in principle, but unfortunately 
it drops every x minutes. The only way to fix it I've found is to reboot the 
computer.
  lsb_release -rd
  Description:Ubuntu 17.10
  Release:17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  predatux   1537 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Nov  8 10:41:26 2017
  HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b
  Lsusb:
   Bus 002 Device 002: ID 045e:090c Microsoft Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. 
   Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface Pro 4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago)
  dmi.bios.date: 02/24/2017
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: 106.1624.768
  dmi.board.name: Surface Pro 4
  dmi.board.vendor: Microsoft Corporation
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 4
  dmi.product.version: D:0B:08F:1C:03P:38
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1730924]

[andy.shevchenko]

(In reply to Ganapathi Bhat from comment #105)
> Created attachment 285537 [details]
> 0001-mwifiex-set-PCIE-to-PCI_D0-power-state-on-resume
> 
> Hi Tsuchiya/Verdre,
> 
> Could please give a try with attached change;
> 
> Regards,
> Ganapathi


I'm wondering if it has any effect on any system. PCI core *does* the same (*) 
for you already. Does it mean we have some race there?

*) See implementation of pci_pm_resume().

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

Title:
  Wifi does down "crash" in Surface Pro 4

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

Bug description:
  I have a Surface Pro 4. The wifi works well in principle, but unfortunately 
it drops every x minutes. The only way to fix it I've found is to reboot the 
computer.
  lsb_release -rd
  Description:Ubuntu 17.10
  Release:17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  predatux   1537 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Nov  8 10:41:26 2017
  HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b
  Lsusb:
   Bus 002 Device 002: ID 045e:090c Microsoft Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. 
   Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface Pro 4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago)
  dmi.bios.date: 02/24/2017
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: 106.1624.768
  dmi.board.name: Surface Pro 4
  dmi.board.vendor: Microsoft Corporation
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 4
  dmi.product.version: D:0B:08F:1C:03P:38
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1848630] Re: eoan/linux-raspi2: 5.3.0-1008.9 -proposed tracker

[Ubuntu Kernel Bot]

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848648
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Saturday, 19. October 2019 00:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  eoan/linux-raspi2: 5.3.0-1008.9 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848648
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Saturday, 19. October 2019 00:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848630/+subscriptions

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

[Kernel-packages] [Bug 1847478] Re: eoan kernel does not contain "ipv6: do not free rt if FIB_LOOKUP_NOREF is set on suppress rule"

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag 'verification-needed-eoan' to 'verification-failed-eoan'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-eoan

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

Title:
  eoan kernel does not contain "ipv6: do not free rt if FIB_LOOKUP_NOREF
  is set on suppress rule"

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

Bug description:
  [Impact]

  An unprivileged local attacker could cause a denial of service, or
  possibly execute arbitrary code due to an ipv6 regression.

  [Test Case]

  An unpatched system will crash with the following command:

  $ unshare -rUn sh -c 'ip link add dummy1 type dummy && ip link set
  dummy1 up && ip -6 route add default dev dummy1 && ip -6 rule add
  table main suppress_prefixlength 0 && ping -f 1234::1'

  [Regression Potential]

  Low. The change could theoretically introduce a memory leak but that
  would still be an improvement over immediate loss of system
  availability.

  [Original Description]

  Having recently upgraded to Eoan Ermine from Disco Dingo, my
  previously rock-solid wireguard now locks the system up shortly after
  I take the connection down with wg-quick down wg0.

  Package:

  wireguard:
    Installed: 0.0.20190913-1ubuntu1
    Candidate: 0.0.20190913-1ubuntu1
    Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe i386 Packages
  100 /var/lib/dpkg/status

  Kernel:
  5.3.0-13-generic

  Snipped from /var/log/syslog:

  kernel: [  776.930804] BUG: unable to handle page fault for address: 
1070
  kernel: [  776.930807] #PF: supervisor read access in kernel mode
  kernel: [  776.930808] #PF: error_code(0x) - not-present page
  kernel: [  776.930809] PGD 0 P4D 0
  kernel: [  776.930811] Oops:  [#1] SMP NOPTI
  kernel: [  776.930813] CPU: 3 PID: 2598 Comm: Chrome_ChildIOT Tainted: G  
 OE 5.3.0-13-generic #14-Ubuntu
  kernel: [  776.930813] Hardware name: Dell Inc. XPS 13 9380/0KTW76, BIOS 
1.7.0 08/05/2019
  kernel: [  776.930817] RIP: 0010:ip6_sk_dst_store_flow+0x80/0xc0
  kernel: [  776.930819] Code: 48 8b 42 30 48 33 47 40 48 09 c1 0f b6 4f 12 b8 
01 00 00 00 4d 0f 45 e9 31 db d3 e0 a9 bf ef ff ff 74 07 48 8b 9f f8 02 00 00 
<48> 8b 46 70 31 d2 48 85 c0 74 0c 48 8b 40 10 48 85 c0 74 03 8b 50
  kernel: [  776.930820] RSP: 0018:beb841a9fcd8 EFLAGS: 00010202
  kernel: [  776.930821] RAX: 0080 RBX: a0933c829360 RCX: 
0007
  kernel: [  776.930822] RDX: beb841a9fd20 RSI: 1000 RDI: 
a0933c828f00
  kernel: [  776.930823] RBP: beb841a9fcf0 R08:  R09: 

  kernel: [  776.930823] R10:  R11: a093948fd800 R12: 
a0933c829360
  kernel: [  776.930824] R13: a0933c828f38 R14: 0001 R15: 
a0933c829360
  kernel: [  776.930825] FS:  7fbcd8a82700() GS:a0939e4c() 
knlGS:
  kernel: [  776.930826] CS:  0010 DS:  ES:  CR0: 80050033
  kernel: [  776.930827] CR2: 1070 CR3: 00049172a004 CR4: 
003606e0
  kernel: [  776.930828] Call Trace:
  kernel: [  776.930832]  ip6_datagram_dst_update+0x15e/0x280
  kernel: [  776.930835]  ? _raw_read_unlock_bh+0x20/0x30
  kernel: [  776.930837]  __ip6_datagram_connect+0x1da/0x380
  kernel: [  776.930839]  ip6_datagram_connect+0x2d/0x50
  kernel: [  776.930841]  inet_dgram_connect+0x3f/0xc0
  kernel: [  776.930843]  __sys_connect+0xf1/0x130
  kernel: [  776.930846]  ? do_fcntl+0xe4/0x550
  kernel: [  776.930848]  ? fput+0x13/0x15
  kernel: [  776.930849]  __x64_sys_connect+0x1a/0x20
  kernel: [  776.930852]  do_syscall_64+0x5a/0x130
  kernel: [  776.930854]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  kernel: [  776.930855] RIP: 0033:0x7fbcde6324eb
  kernel: [  776.930856] Code: 83 ec 18 89 54 24 0c 48 89 34 24 89 7c 24 08 e8 
ab fa ff ff 8b 54 24 0c 48 8b 34 24 41 89 c0 8b 7c 24 08 b8 2a 00 00 00 0f 05 
<48> 3d 00 f0 ff ff 77 2f 44 89 c7 89 44 24 08 e8 e1 fa ff ff 8b 44
  kernel: [  776.930857] RSP: 002b:7fbcd8a7ec90 EFLAGS: 0293 ORIG_RAX: 
002a
  kernel: [  776.930859] RAX: ffda RBX: ff94 RCX: 
7fbcde6324eb
  kernel: [  

[Kernel-packages] [Bug 1848642] Re: eoan/linux-kvm: 5.3.0-1004.4 -proposed tracker

[Ubuntu Kernel Bot]

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848648
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Testing
  phase-changed: Saturday, 19. October 2019 00:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  eoan/linux-kvm: 5.3.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Eoan:
  Invalid

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848648
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Testing
  phase-changed: Saturday, 19. October 2019 00:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848642/+subscriptions

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

[Kernel-packages] [Bug 1848631] Re: eoan/linux-aws: 5.3.0-1004.4 -proposed tracker

[Ubuntu Kernel Bot]

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848648
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Saturday, 19. October 2019 00:15 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  eoan/linux-aws: 5.3.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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-lrm 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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Eoan:
  Invalid

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848648
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Saturday, 19. October 2019 00:15 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848631/+subscriptions

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

[Kernel-packages] [Bug 1848632] Re: eoan/linux-azure: 5.3.0-1004.4 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848648
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Promote to Proposed
- phase-changed: Friday, 18. October 2019 21:55 UTC
+ phase: Testing
+ phase-changed: Saturday, 19. October 2019 06:02 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   stakeholder-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  eoan/linux-azure: 5.3.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Eoan:
  Invalid

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848648
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Saturday, 19. October 2019 06:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848632/+subscriptions

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

[Kernel-packages] [Bug 1848635] Re: eoan/linux-gcp: 5.3.0-1005.5 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848648
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Promote to Proposed
- phase-changed: Friday, 18. October 2019 22:02 UTC
+ phase: Testing
+ phase-changed: Saturday, 19. October 2019 06:02 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  eoan/linux-gcp: 5.3.0-1005.5 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Eoan:
  Invalid

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848648
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Saturday, 19. October 2019 06:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848635/+subscriptions

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

[Kernel-packages] [Bug 1848648] Re: eoan/linux: 5.3.0-19.20 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
+ bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
- phase: Promote to Proposed
- phase-changed: Friday, 18. October 2019 21:41 UTC
+ phase: Testing
+ phase-changed: Saturday, 19. October 2019 06:01 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   certification-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe-edge: bug 1848645
eoan/linux-aws: bug 1848631
eoan/linux-azure: bug 1848632
eoan/linux-gcp: bug 1848635
eoan/linux-kvm: bug 1848642
eoan/linux-oracle: bug 1848644
eoan/linux-raspi2: bug 1848630
  variant: debs

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

Title:
  eoan/linux: 5.3.0-19.20 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Saturday, 19. October 2019 06:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe-edge: bug 1848645
eoan/linux-aws: bug 1848631
eoan/linux-azure: bug 1848632
eoan/linux-gcp: bug 1848635
eoan/linux-kvm: bug 1848642
eoan/linux-oracle: bug 1848644
eoan/linux-raspi2: bug 1848630
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848648/+subscriptions

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