[Kernel-packages] [Bug 1864293] Re: Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full disk encryption

[Neil McPhail]

** This bug is no longer a duplicate of bug 1864360
   cryptsetup-run is transitional package, but removing it also removes 
cryptsetup-initramfs

** Summary changed:

- Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full disk 
encryption
+ apt autoremove removes cryptsetup-initramfs which causes boot to drop to 
initramfs shell on machine with LVM and full disk encryption

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

** No longer affects: linux-5.4 (Ubuntu)

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

Title:
  apt autoremove removes cryptsetup-initramfs which causes boot to drop
  to initramfs shell on machine with LVM and full disk encryption

Status in cryptsetup package in Ubuntu:
  New

Bug description:
  Ubuntu Mate 20.04 dev release, upgraded from 19.10. LVM/disk encrypion
  had been set up from the 19.10 installer and had been working
  perfectly.

  Today, when I try to boot, the splash screen stalls at the throbber
  and doesn't open a prompt for my encryption key. After a minute or so
  it drops to the initramfs shell. Rebooting without "silent splash" on
  the cmdline shows that `/dev/mapper/vgubuntu--mate-root` cannot be
  found, and running `ls /dev/mapper` outputs only `control`.

  Rebooting with the 5.4.0-12 kernel works without any problems.

  I've added `mitigations=off` to my default boot flags some time ago,
  if that's relevant?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-14-generic 5.4.0-14.17
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3193 F pulseaudio
  CurrentDesktop: MATE
  Date: Sat Feb 22 12:29:27 2020
  InstallationDate: Installed on 2019-10-11 (133 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux-5.4
  UpgradeStatus: Upgraded to focal on 2020-02-07 (15 days ago)
  dmi.bios.date: 06/19/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETB3WW (2.73 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325A39
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETB3WW(2.73):bd06/19/2018:svnLENOVO:pn2325A39:pvrThinkPadX230:rvnLENOVO:rn2325A39:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2325A39
  dmi.product.sku: LENOVO_MT_2325
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1862215] Re: Failure to boot with LVM + encrypted root disk

[Neil McPhail]

Running cat /proc/modules gives:
i915
i2c_algo_bit
crc32_pclmul
drm_kms_helper
syscopyarea
sysfillrect
sysimgblt
fb_sys_fops
psmouse
sdhci_pci
cqhci
sdhci
lpc_ich
i2c_i801
ahci
drm
libahci
e1000e
wmi
video

(There may be a transcription error or 2 in there, so photo is at
http://ovh.themcphails.uk/index.php/s/t94YwXRktqrYHsb )

Certainly no evidence of dm-crypt or similar.

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

Title:
  Failure to boot with LVM + encrypted root disk

Status in linux-5.4 package in Ubuntu:
  Confirmed

Bug description:
  Attempting to boot linux-image-5.4.0-12-generic and it failed to find
  my LVM VG. -9 worked without issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-generic 5.4.0.12.15
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  6 17:20:45 2020
  InstallationDate: Installed on 2016-11-01 (1192 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: linux-meta-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-20 (17 days ago)

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

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

[Kernel-packages] [Bug 1864293] Re: Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full disk encryption

[Neil McPhail]

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

** This bug has been marked a duplicate of bug 1862215
   Failure to boot with LVM + encrypted root disk

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

Title:
  Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full
  disk encryption

Status in linux-5.4 package in Ubuntu:
  New

Bug description:
  Ubuntu Mate 20.04 dev release, upgraded from 19.10. LVM/disk encrypion
  had been set up from the 19.10 installer and had been working
  perfectly.

  Today, when I try to boot, the splash screen stalls at the throbber
  and doesn't open a prompt for my encryption key. After a minute or so
  it drops to the initramfs shell. Rebooting without "silent splash" on
  the cmdline shows that `/dev/mapper/vgubuntu--mate-root` cannot be
  found, and running `ls /dev/mapper` outputs only `control`.

  Rebooting with the 5.4.0-12 kernel works without any problems.

  I've added `mitigations=off` to my default boot flags some time ago,
  if that's relevant?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-14-generic 5.4.0-14.17
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3193 F pulseaudio
  CurrentDesktop: MATE
  Date: Sat Feb 22 12:29:27 2020
  InstallationDate: Installed on 2019-10-11 (133 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux-5.4
  UpgradeStatus: Upgraded to focal on 2020-02-07 (15 days ago)
  dmi.bios.date: 06/19/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETB3WW (2.73 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325A39
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETB3WW(2.73):bd06/19/2018:svnLENOVO:pn2325A39:pvrThinkPadX230:rvnLENOVO:rn2325A39:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2325A39
  dmi.product.sku: LENOVO_MT_2325
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1862215] Re: Failure to boot with LVM + encrypted root disk

[Neil McPhail]

Oddly, I've just had this on 5.4.0-14, whereas 5.4.0-12 works perfectly.
Maybe something is messed up in initramfs generation?

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

Title:
  Failure to boot with LVM + encrypted root disk

Status in linux-5.4 package in Ubuntu:
  Confirmed

Bug description:
  Attempting to boot linux-image-5.4.0-12-generic and it failed to find
  my LVM VG. -9 worked without issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-generic 5.4.0.12.15
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  6 17:20:45 2020
  InstallationDate: Installed on 2016-11-01 (1192 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: linux-meta-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-20 (17 days ago)

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

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

[Kernel-packages] [Bug 1864293] Re: Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full disk encryption

[Neil McPhail]

** Summary changed:

- Booting 5.4.0-14 drops to initramfs shell on machine with LVM and fudd disk 
encryption
+ Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full disk 
encryption

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

Title:
  Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full
  disk encryption

Status in linux-5.4 package in Ubuntu:
  New

Bug description:
  Ubuntu Mate 20.04 dev release, upgraded from 19.10. LVM/disk encrypion
  had been set up from the 19.10 installer and had been working
  perfectly.

  Today, when I try to boot, the splash screen stalls at the throbber
  and doesn't open a prompt for my encryption key. After a minute or so
  it drops to the initramfs shell. Rebooting without "silent splash" on
  the cmdline shows that `/dev/mapper/vgubuntu--mate-root` cannot be
  found, and running `ls /dev/mapper` outputs only `control`.

  Rebooting with the 5.4.0-12 kernel works without any problems.

  I've added `mitigations=off` to my default boot flags some time ago,
  if that's relevant?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-14-generic 5.4.0-14.17
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3193 F pulseaudio
  CurrentDesktop: MATE
  Date: Sat Feb 22 12:29:27 2020
  InstallationDate: Installed on 2019-10-11 (133 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux-5.4
  UpgradeStatus: Upgraded to focal on 2020-02-07 (15 days ago)
  dmi.bios.date: 06/19/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETB3WW (2.73 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325A39
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETB3WW(2.73):bd06/19/2018:svnLENOVO:pn2325A39:pvrThinkPadX230:rvnLENOVO:rn2325A39:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2325A39
  dmi.product.sku: LENOVO_MT_2325
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1864293] [NEW] Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full disk encryption

[Neil McPhail]

Public bug reported:

Ubuntu Mate 20.04 dev release, upgraded from 19.10. LVM/disk encrypion
had been set up from the 19.10 installer and had been working perfectly.

Today, when I try to boot, the splash screen stalls at the throbber and
doesn't open a prompt for my encryption key. After a minute or so it
drops to the initramfs shell. Rebooting without "silent splash" on the
cmdline shows that `/dev/mapper/vgubuntu--mate-root` cannot be found,
and running `ls /dev/mapper` outputs only `control`.

Rebooting with the 5.4.0-12 kernel works without any problems.

I've added `mitigations=off` to my default boot flags some time ago, if
that's relevant?

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-14-generic 5.4.0-14.17
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu17
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  neil   3193 F pulseaudio
CurrentDesktop: MATE
Date: Sat Feb 22 12:29:27 2020
InstallationDate: Installed on 2019-10-11 (133 days ago)
InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
MachineType: LENOVO 2325A39
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-12-generic N/A
 linux-backports-modules-5.4.0-12-generic  N/A
 linux-firmware1.186
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux-5.4
UpgradeStatus: Upgraded to focal on 2020-02-07 (15 days ago)
dmi.bios.date: 06/19/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ETB3WW (2.73 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2325A39
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETB3WW(2.73):bd06/19/2018:svnLENOVO:pn2325A39:pvrThinkPadX230:rvnLENOVO:rn2325A39:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X230
dmi.product.name: 2325A39
dmi.product.sku: LENOVO_MT_2325
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

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

Title:
  Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full
  disk encryption

Status in linux-5.4 package in Ubuntu:
  New

Bug description:
  Ubuntu Mate 20.04 dev release, upgraded from 19.10. LVM/disk encrypion
  had been set up from the 19.10 installer and had been working
  perfectly.

  Today, when I try to boot, the splash screen stalls at the throbber
  and doesn't open a prompt for my encryption key. After a minute or so
  it drops to the initramfs shell. Rebooting without "silent splash" on
  the cmdline shows that `/dev/mapper/vgubuntu--mate-root` cannot be
  found, and running `ls /dev/mapper` outputs only `control`.

  Rebooting with the 5.4.0-12 kernel works without any problems.

  I've added `mitigations=off` to my default boot flags some time ago,
  if that's relevant?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-14-generic 5.4.0-14.17
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3193 F pulseaudio
  CurrentDesktop: MATE
  Date: Sat Feb 22 12:29:27 2020
  InstallationDate: Installed on 2019-10-11 (133 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux-5.4
  UpgradeStatus: Upgraded to focal on 2020-02-07 (15 days ago)
  dmi.bios.date: 06/19/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETB3WW (2.73 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325A39
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not 

[Kernel-packages] [Bug 1860512] Re: Suspend unreliable (possibly FUSE related)

[Neil McPhail]

I can partially reproduce this on Ubuntu Mate 20.04 development release,
updated from 19.10. Hardware is a ThinkPad X230.

Steps to reproduce:

- mount an rclone remote drive
- do something which keeps the mountpoint busy (e.g. open the file manager and 
navigate to a photos folder on the remote drive so the thumbnailer kicks in)
- attempt to suspend

What should happen:

- Laptop suspends

What actually happens:

- mouse pointer becomes unresponsive for about 30 seconds. WiFi status
icon changes to disconnected for a few seconds. Laptop does not suspend.
WiFi reconnects and mouse pointer becomes responsive again.

Note that simply making the fuse mount with rclone does not inhibit
suspend; the problem only occurs if the mount point is busy.

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

Title:
  Suspend unreliable (possibly FUSE related)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since updating to Focal my laptop stopped suspending reliably. It will
  sit there either without display or with the desktop stuck for almost
  a minute before it goes back to work again.

  Looking at the kernel logs this seems to be related to a FUSE mount
  that I have running:

  sty 22 09:00:49 michal-laptop kernel: Call Trace:
  sty 22 09:00:49 michal-laptop kernel:  __schedule+0x2e3/0x740
  sty 22 09:00:49 michal-laptop kernel:  schedule+0x42/0xb0
  sty 22 09:00:49 michal-laptop kernel:  request_wait_answer+0xa0/0x200
  sty 22 09:00:49 michal-laptop kernel:  ? wait_woken+0x80/0x80
  sty 22 09:00:49 michal-laptop kernel:  fuse_simple_request+0x177/0x260
  sty 22 09:00:49 michal-laptop kernel:  fuse_send_readpages.isra.0+0xea/0xf0
  sty 22 09:00:49 michal-laptop kernel:  fuse_readpages+0xbc/0x110
  sty 22 09:00:49 michal-laptop kernel:  read_pages+0x71/0x1a0
  sty 22 09:00:49 michal-laptop kernel:  __do_page_cache_readahead+0x180/0x1a0
  sty 22 09:00:49 michal-laptop kernel:  ondemand_readahead+0x192/0x2d0
  sty 22 09:00:49 michal-laptop kernel:  page_cache_sync_readahead+0x78/0xc0
  sty 22 09:00:49 michal-laptop kernel:  generic_file_buffered_read+0x571/0xc00
  sty 22 09:00:49 michal-laptop kernel:  ? ima_file_check+0x5a/0x80
  sty 22 09:00:49 michal-laptop kernel:  ? do_last+0x194/0x940
  sty 22 09:00:49 michal-laptop kernel:  generic_file_read_iter+0xdc/0x140
  sty 22 09:00:49 michal-laptop kernel:  fuse_file_read_iter+0x101/0x130
  sty 22 09:00:49 michal-laptop kernel:  ? do_filp_open+0xa5/0x100
  sty 22 09:00:49 michal-laptop kernel:  new_sync_read+0x122/0x1b0
  sty 22 09:00:49 michal-laptop kernel:  __vfs_read+0x29/0x40
  sty 22 09:00:49 michal-laptop kernel:  vfs_read+0xab/0x160
  sty 22 09:00:49 michal-laptop kernel:  ksys_read+0x67/0xe0
  sty 22 09:00:49 michal-laptop kernel:  __x64_sys_read+0x1a/0x20
  sty 22 09:00:49 michal-laptop kernel:  do_syscall_64+0x57/0x190
  sty 22 09:00:49 michal-laptop kernel:  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  sty 22 09:00:49 michal-laptop kernel: RIP: 0033:0x7f432f9e4b1d
  sty 22 09:00:49 michal-laptop kernel: Code: Bad RIP value.
  sty 22 09:00:49 michal-laptop kernel: RSP: 002b:7f430bffda28 EFLAGS: 
0246 ORIG_RAX: 
  sty 22 09:00:49 michal-laptop kernel: RAX: ffda RBX: 
492a RCX: 7f432f9e4b1d
  sty 22 09:00:49 michal-laptop kernel: RDX: 1000 RSI: 
7f430bffda40 RDI: 0011
  sty 22 09:00:49 michal-laptop kernel: RBP: 7f430bffda40 R08: 
 R09: 7f430bffd9a8
  sty 22 09:00:49 michal-laptop kernel: R10:  R11: 
0246 R12: 7f434670
  sty 22 09:00:49 michal-laptop kernel: R13: 562dc32aaac0 R14: 
0011 R15: 562dc32aaac0

  A longer kernel log is attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-9-generic 5.4.0-9.12
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  michal 6829 F pulseaudio
   /dev/snd/controlC0:  michal 6829 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 22 08:54:14 2020
  InstallationDate: Installed on 2019-11-19 (63 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. XPS 12-9Q33
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i2bkio@/vmlinuz-5.4.0-9-generic 
root=ZFS=rpool/ROOT/ubuntu_i2bkio ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware  

[Kernel-packages] [Bug 1854225] Re: Kernel oops and system lock up when invoking wg-quick up

[Neil McPhail]

apport information

** Tags added: apport-collected focal

** Description changed:

  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my laptop
  start whirring and the system gradually becomes unresponsive before my
  desktop crashes and the system becomes completely unresponsive. On both
  occasions I opened another window to run "top" to see what process was
  consuming resources but "top" never actually runs. On the second
  occasion I managed to run "dmesg" before the system crashed completely
  and saw multiple lines of text about a kernel oops and red-highlighted
  text about a null-pointer dereference.
  
  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted with
  the "system problem detected" dialog, but selecting the "report" option
  didn't seem to do anything. I have 2 reports in /var/crash from the last
  oops which I will attach to this report.
  
  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from suspend,
  but invoking "wg-quick" after waking from suspend doesn't trigger it on
  demand. On the first occasion I was running with stock boot options. On
  the second, I was running with "mitigations=off" as an experiment.
  
  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10
  
  $ apt policy wireguard
  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
  
  $ apt policy wireguard-tools 
  wireguard-tools:
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
  100 /var/lib/dpkg/status
  
  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux
  
  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1
  
  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0
  
  
  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I don't
  know how to access or send the old dmesg information, so please let me
  know how to access this or how to collect it if the crash recurs.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu16
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  neil   3007 F pulseaudio
+  /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2019-10-11 (118 days ago)
+ InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
+ MachineType: LENOVO 2325A39
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
+ RelatedPackageVersions:
+  linux-restricted-modules-5.4.0-12-generic N/A
+  linux-backports-modules-5.4.0-12-generic  N/A
+  linux-firmware1.186
+ RfKill:
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
+ Tags:  focal
+ Uname: Linux 5.4.0-12-generic x86_64
+ UpgradeStatus: Upgraded to focal on 2020-02-07 (0 days ago)
+ UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 06/19/2018
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: G2ETB3WW (2.73 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 2325A39
+ dmi.board.vendor: LENOVO
+ dmi.board.version: Not Defined
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: Not Available
+ dmi.modalias: 

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

[Neil McPhail]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1854225/+attachment/5326231/+files/ProcInterrupts.txt

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  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

  $ apt policy wireguard-tools 
  wireguard-tools:
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
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/19/2018
  

[Kernel-packages] [Bug 1854225] Lsusb-v.txt

[Neil McPhail]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1854225/+attachment/5326227/+files/Lsusb-v.txt

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  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

  $ apt policy wireguard-tools 
  wireguard-tools:
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
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/19/2018
  

[Kernel-packages] [Bug 1854225] PulseList.txt

[Neil McPhail]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1854225/+attachment/5326234/+files/PulseList.txt

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  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

  $ apt policy wireguard-tools 
  wireguard-tools:
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
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/19/2018
  

[Kernel-packages] [Bug 1854225] Lsusb-t.txt

[Neil McPhail]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1854225/+attachment/5326226/+files/Lsusb-t.txt

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  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

  $ apt policy wireguard-tools 
  wireguard-tools:
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
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/19/2018
  

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

[Neil McPhail]

apport information

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

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  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

  $ apt policy wireguard-tools 
  wireguard-tools:
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
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/19/2018
  

[Kernel-packages] [Bug 1854225] ProcEnviron.txt

[Neil McPhail]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1854225/+attachment/5326230/+files/ProcEnviron.txt

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  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

  $ apt policy wireguard-tools 
  wireguard-tools:
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
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/19/2018
  

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

[Neil McPhail]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1854225/+attachment/5326235/+files/UdevDb.txt

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  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

  $ apt policy wireguard-tools 
  wireguard-tools:
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
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/19/2018
  dmi.bios.vendor: 

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

[Neil McPhail]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1854225/+attachment/5326225/+files/Lsusb.txt

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  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

  $ apt policy wireguard-tools 
  wireguard-tools:
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
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/19/2018
  dmi.bios.vendor: 

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

[Neil McPhail]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1854225/+attachment/5326221/+files/CRDA.txt

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  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

  $ apt policy wireguard-tools 
  wireguard-tools:
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
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/19/2018
  dmi.bios.vendor: 

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

[Neil McPhail]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1854225/+attachment/5326228/+files/ProcCpuinfo.txt

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  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

  $ apt policy wireguard-tools 
  wireguard-tools:
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
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/19/2018
  

[Kernel-packages] [Bug 1854225] Re: Kernel oops and system lock up when invoking wg-quick up

[Neil McPhail]

Note that this bug is quite old now, and I upgraded this machine to
20.04 last night. I have no idea if the information collected by apport
has any relevance any more.

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

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  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

  $ apt policy wireguard-tools 
  wireguard-tools:
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
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 days ago)
  UserGroups: adm audio cdrom dip 

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

[Neil McPhail]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1854225/+attachment/5326232/+files/ProcModules.txt

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  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

  $ apt policy wireguard-tools 
  wireguard-tools:
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
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/19/2018
  

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

[Neil McPhail]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1854225/+attachment/5326224/+files/Lspci.txt

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  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

  $ apt policy wireguard-tools 
  wireguard-tools:
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
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/19/2018
  dmi.bios.vendor: 

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

[Neil McPhail]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1854225/+attachment/5326229/+files/ProcCpuinfoMinimal.txt

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  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

  $ apt policy wireguard-tools 
  wireguard-tools:
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
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 

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

[Neil McPhail]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1854225/+attachment/5326222/+files/CurrentDmesg.txt

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  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

  $ apt policy wireguard-tools 
  wireguard-tools:
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
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/19/2018
  

[Kernel-packages] [Bug 1854225] IwConfig.txt

[Neil McPhail]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1854225/+attachment/5326223/+files/IwConfig.txt

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  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

  $ apt policy wireguard-tools 
  wireguard-tools:
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
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/19/2018
  

[Kernel-packages] [Bug 1574102] Re: Regression (constant vibration of device) in xpad driver in Ubuntu 16.04

[Neil McPhail]

Thanks jsalisbury. The bug seems to be fixed with that kernel build.

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

Title:
  Regression (constant vibration of device) in xpad driver in Ubuntu
  16.04

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

Bug description:
  Since upgrading to 16.04, I cannot launch Saints Row 2 or 3 from Steam
  without constant vibration from my Xbox360 controller. The symptoms
  are the same as outlined in https://github.com/paroj/xpad/issues/27.
  (I believe that github user submits xpad patches to upstream.) If I
  compile the f23507b version from that git repo, the problem resolves.
  This was not an issue on 15.10.

  Fix commit:
  https://github.com/paroj/xpad/commit/ef9e5b156c4b0042a75897697a792e7b1c5fde4b

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neil   2398 F pulseaudio
   /dev/snd/controlC2:  neil   2398 F pulseaudio
   /dev/snd/controlC0:  neil   2398 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 23 20:48:46 2016
  InstallationDate: Installed on 2015-10-23 (183 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: MSI MS-7721
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=UUID=a3f3cb16-7fb4-411c-9649-b40f12c5ff51 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V30.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-E35 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV30.6:bd12/15/2014:svnMSI:pnMS-7721:pvr6.0:rvnMSI:rnA55M-E35(MS-7721):rvr6.0:cvnMSI:ct3:cvr6.0:
  dmi.product.name: MS-7721
  dmi.product.version: 6.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1574102] Re: Regression (constant vibration of device) in xpad driver in Ubuntu 16.04

[Neil McPhail]

The fix from paroj's repo works for me. Can we get this backported?
Although the importance of this bug is marked as "medium", it is a bug
which can damage hardware and surrounding equipment as unexpectedly-
vibrating joypads have a tendency to fall off surfaces.

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

Title:
  Regression (constant vibration of device) in xpad driver in Ubuntu
  16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to 16.04, I cannot launch Saints Row 2 or 3 from Steam
  without constant vibration from my Xbox360 controller. The symptoms
  are the same as outlined in https://github.com/paroj/xpad/issues/27.
  (I believe that github user submits xpad patches to upstream.) If I
  compile the f23507b version from that git repo, the problem resolves.
  This was not an issue on 15.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neil   2398 F pulseaudio
   /dev/snd/controlC2:  neil   2398 F pulseaudio
   /dev/snd/controlC0:  neil   2398 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 23 20:48:46 2016
  InstallationDate: Installed on 2015-10-23 (183 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: MSI MS-7721
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=UUID=a3f3cb16-7fb4-411c-9649-b40f12c5ff51 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V30.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-E35 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV30.6:bd12/15/2014:svnMSI:pnMS-7721:pvr6.0:rvnMSI:rnA55M-E35(MS-7721):rvr6.0:cvnMSI:ct3:cvr6.0:
  dmi.product.name: MS-7721
  dmi.product.version: 6.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1574102] Re: Regression (constant vibration of device) in xpad driver in Ubuntu 16.04

[Neil McPhail]

Thanks Matt.

The proposed fix doesn't do anything for me. I've appended details to
the upstream github tracker.

To clarify the original bug report, I am using a _wired_ Xbox 360
controller.

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

Title:
  Regression (constant vibration of device) in xpad driver in Ubuntu
  16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to 16.04, I cannot launch Saints Row 2 or 3 from Steam
  without constant vibration from my Xbox360 controller. The symptoms
  are the same as outlined in https://github.com/paroj/xpad/issues/27.
  (I believe that github user submits xpad patches to upstream.) If I
  compile the f23507b version from that git repo, the problem resolves.
  This was not an issue on 15.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neil   2398 F pulseaudio
   /dev/snd/controlC2:  neil   2398 F pulseaudio
   /dev/snd/controlC0:  neil   2398 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 23 20:48:46 2016
  InstallationDate: Installed on 2015-10-23 (183 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: MSI MS-7721
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=UUID=a3f3cb16-7fb4-411c-9649-b40f12c5ff51 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V30.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-E35 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV30.6:bd12/15/2014:svnMSI:pnMS-7721:pvr6.0:rvnMSI:rnA55M-E35(MS-7721):rvr6.0:cvnMSI:ct3:cvr6.0:
  dmi.product.name: MS-7721
  dmi.product.version: 6.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1574102] Re: Regression (constant vibration of device) in xpad driver in Ubuntu 16.04

[Neil McPhail]

$ uname -r
4.6.0-040600rc6-generic

$ apt-cache policy linux-image-4.6.0-040600rc6-generic 
linux-image-4.6.0-040600rc6-generic:
  Installed: 4.6.0-040600rc6.201605012031
  Candidate: 4.6.0-040600rc6.201605012031
  Version table:
 *** 4.6.0-040600rc6.201605012031 100
100 /var/lib/dpkg/status

Bug still exists here.

** Tags added: kernel-bug-exists-upstream

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

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

Title:
  Regression (constant vibration of device) in xpad driver in Ubuntu
  16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to 16.04, I cannot launch Saints Row 2 or 3 from Steam
  without constant vibration from my Xbox360 controller. The symptoms
  are the same as outlined in https://github.com/paroj/xpad/issues/27.
  (I believe that github user submits xpad patches to upstream.) If I
  compile the f23507b version from that git repo, the problem resolves.
  This was not an issue on 15.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neil   2398 F pulseaudio
   /dev/snd/controlC2:  neil   2398 F pulseaudio
   /dev/snd/controlC0:  neil   2398 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 23 20:48:46 2016
  InstallationDate: Installed on 2015-10-23 (183 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: MSI MS-7721
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=UUID=a3f3cb16-7fb4-411c-9649-b40f12c5ff51 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V30.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-E35 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV30.6:bd12/15/2014:svnMSI:pnMS-7721:pvr6.0:rvnMSI:rnA55M-E35(MS-7721):rvr6.0:cvnMSI:ct3:cvr6.0:
  dmi.product.name: MS-7721
  dmi.product.version: 6.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1574102] Re: Regression (constant vibration of device) in xpad driver in Ubuntu 16.04

[Neil McPhail]

You'll see an "URB submitted while active" error in my dmesg when
running the older driver. These messages were frequent on previous
Ubuntu releases. I think the current patches were to "fix" this, but
seem to have prompted the regression.

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

Title:
  Regression (constant vibration of device) in xpad driver in Ubuntu
  16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to 16.04, I cannot launch Saints Row 2 or 3 from Steam
  without constant vibration from my Xbox360 controller. The symptoms
  are the same as outlined in https://github.com/paroj/xpad/issues/27.
  (I believe that github user submits xpad patches to upstream.) If I
  compile the f23507b version from that git repo, the problem resolves.
  This was not an issue on 15.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neil   2398 F pulseaudio
   /dev/snd/controlC2:  neil   2398 F pulseaudio
   /dev/snd/controlC0:  neil   2398 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 23 20:48:46 2016
  InstallationDate: Installed on 2015-10-23 (183 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: MSI MS-7721
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=UUID=a3f3cb16-7fb4-411c-9649-b40f12c5ff51 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V30.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-E35 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV30.6:bd12/15/2014:svnMSI:pnMS-7721:pvr6.0:rvnMSI:rnA55M-E35(MS-7721):rvr6.0:cvnMSI:ct3:cvr6.0:
  dmi.product.name: MS-7721
  dmi.product.version: 6.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1574102] [NEW] Regression (constant vibration of device) in xpad driver in Ubuntu 16.04

[Neil McPhail]

Public bug reported:

Since upgrading to 16.04, I cannot launch Saints Row 2 or 3 from Steam
without constant vibration from my Xbox360 controller. The symptoms are
the same as outlined in https://github.com/paroj/xpad/issues/27. (I
believe that github user submits xpad patches to upstream.) If I compile
the f23507b version from that git repo, the problem resolves. This was
not an issue on 15.10.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-21-generic 4.4.0-21.37
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  neil   2398 F pulseaudio
 /dev/snd/controlC2:  neil   2398 F pulseaudio
 /dev/snd/controlC0:  neil   2398 F pulseaudio
CurrentDesktop: Unity
Date: Sat Apr 23 20:48:46 2016
InstallationDate: Installed on 2015-10-23 (183 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: MSI MS-7721
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=UUID=a3f3cb16-7fb4-411c-9649-b40f12c5ff51 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-21-generic N/A
 linux-backports-modules-4.4.0-21-generic  N/A
 linux-firmware1.157
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)
dmi.bios.date: 12/15/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V30.6
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A55M-E35 (MS-7721)
dmi.board.vendor: MSI
dmi.board.version: 6.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 6.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV30.6:bd12/15/2014:svnMSI:pnMS-7721:pvr6.0:rvnMSI:rnA55M-E35(MS-7721):rvr6.0:cvnMSI:ct3:cvr6.0:
dmi.product.name: MS-7721
dmi.product.version: 6.0
dmi.sys.vendor: MSI

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


** Tags: amd64 apport-bug xenial

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

Title:
  Regression (constant vibration of device) in xpad driver in Ubuntu
  16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to 16.04, I cannot launch Saints Row 2 or 3 from Steam
  without constant vibration from my Xbox360 controller. The symptoms
  are the same as outlined in https://github.com/paroj/xpad/issues/27.
  (I believe that github user submits xpad patches to upstream.) If I
  compile the f23507b version from that git repo, the problem resolves.
  This was not an issue on 15.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neil   2398 F pulseaudio
   /dev/snd/controlC2:  neil   2398 F pulseaudio
   /dev/snd/controlC0:  neil   2398 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 23 20:48:46 2016
  InstallationDate: Installed on 2015-10-23 (183 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: MSI MS-7721
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=UUID=a3f3cb16-7fb4-411c-9649-b40f12c5ff51 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V30.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-E35 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV30.6:bd12/15/2014:svnMSI:pnMS-7721:pvr6.0:rvnMSI:rnA55M-E35(MS-7721):rvr6.0:cvnMSI:ct3:cvr6.0:
  dmi.product.name: MS-7721
  dmi.product.version: 6.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth

[Neil McPhail]

And the syslog...

** Attachment added: "bluetooth_syslog"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1435040/+attachment/4527538/+files/bluetooth_syslog

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

Title:
  Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  With my FORD Focus Car, pairing does not work. The bluetooth system in
  the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition"
  and then prompts me to connect with a 4-digit pin code, but the Ubuntu
  phone doesn't react at all and after a while the car system says that
  it failed to connect.

  image: 20150310-3201c0a
  KRILIN01A-S15A_BQ_L100EN_2020_150312
  OS Build 20

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions

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

[Kernel-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth

[Neil McPhail]

I cannot connect to the unit in my Hyundai i40, and switching to the
latest rc-proposed with bluez5 hasn't changed anything.

Symptoms:
(1) When car unit is asked to search for devices, the phone is not seen at all. 
My other bluetooth devices get picked up by this search. I have checked, and 
the Ubuntu phone should be advertising
(2) Putting my car into listening mode, my phone can see it as "i40". If I try 
to connect, I get the PIN input screen on my phone but nothing happens after I 
input my PIN. The phone says the i40 is "disconnected" and the car doesn't 
register anything at all.

I have attached debugging info as per
https://wiki.ubuntu.com/DebuggingBluetooth.

** Attachment added: "bluetoothctl_dump.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1435040/+attachment/4527537/+files/bluetoothctl_dump.txt

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

Title:
  Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  With my FORD Focus Car, pairing does not work. The bluetooth system in
  the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition"
  and then prompts me to connect with a 4-digit pin code, but the Ubuntu
  phone doesn't react at all and after a while the car system says that
  it failed to connect.

  image: 20150310-3201c0a
  KRILIN01A-S15A_BQ_L100EN_2020_150312
  OS Build 20

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions

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