[Kernel-packages] [Bug 2055153] Re: [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA driver is installed

[Fabian Gasser]

@alvinjinsung were you able to resolve this issue somehow by playing
around with the above mentioned suggestions? I'm experiencing the same
issue with my new Lenovo Legion Pro 5 16IRX8 on Ubuntu 22.04 when using
the nvidia-driver-535 (proprietary, tested). When I switch back to the
open source driver the issue also again disappeared, but then my
external monitor isn't detected.

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

Title:
  [Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVIDIA
  driver is installed

Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  New

Bug description:
  I have booting related issue everytime I install NVIDIA-driver on
  Ubuntu 22.04 So the main problem is everytime I boot, Ubuntu would
  either

  (1) boot fine (25% of the time)
  (2) boot takes long time(about 2 min) (50% of the time)
  (3) boot fails (25% of the time)

  This symptom disappears when I uninstall NVIDIA driver so I'm pretty
  sure it is related to NVIDIA driver but I don't know how to fix it.

  For case (2) (boot takes long time), black screen with

  '/dev/nvme0n1p6: clean, *** files, *** blocks'

  hang for a long time.

  For case (3) (boot fails), blackscreen with

  'iwlwifi : invalid buffer destination'
  'ACPI BIOS Error (bug): could not resolve symbol [\_TZ.ETMD], AE NOT_FOUND'
  'ACPI Error: Aborting method \_SB.IETM._OSC due to previos error 
(AE_NOT_FOUND)'
  'Bluetooth: hci0: Malformed MSFT vendor event: 0x02'
  'INFO: task plymouthd: *** blocked for more than *** seconds'
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'
  'INFO: task gpu-manager: *** blocked for more than *** seconds' 
  '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message'

  This screen appears and doesn't boot or blackscreen with cursor
  appears and doesn't boot. It happens quite randomly and it really is
  frustrating and want to resolve this issue. I've tried various things
  but it didn't work out. Here are some things I tried

  - deleting and reinstalling NVIDIA driver with 'purge, autoremove, apt 
install'
  - Installing different driver version(525, 535, 545)
  - trying boot-repair program
  - disabling nouveau by modifying /etc/modprobe.d/blacklist.conf
  - 'nomodeset' by modifying /etc/default/grub (made it worse.. all boot 
fails)
  - tried various kernel version with various Ubuntu version (my laptop is very 
new device so 20.04 had issues with touchpad, wifi, etc, therefore I mainly 
tried 22.04)

  However none of them seemed to resolve the problem I am facing. It
  showed different symptoms time-to-time but mostly all of them were
  boot-related. I am using a dualboot with windows

  I am kind of lost and kindly ask for help. Here are some of the
  specification that would be helpful

  Laptop: lenovo legion pro 7 16irx8h

  $ uname -a
  Linux alvin-Legion-Pro-7-16IRX8H 6.5.0-21-generic 
  #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb  9 13:32:52 UTC 2 x86_64 
x86_64 x86_64 GNU/Linux

  $ lspci
  00:00.0 Host bridge: Intel Corporation Device a702 (rev 01)
  00:01.0 PCI bridge: Intel Corporation Device a70d (rev 01)
  00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-S UHD 
Graphics (rev 04)
  00:04.0 Signal processing controller: Intel Corporation Raptor Lake Dynamic 
Platform and Thermal Framework Processor Participant (rev 01)
  00:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port (rev 
01)
  00:0a.0 Signal processing controller: Intel Corporation Raptor Lake Crashlog 
and Telemetry (rev 01)
  00:14.0 USB controller: Intel Corporation Raptor Lake USB 3.2 Gen 2x2 (20 
Gb/s) XHCI Host Controller (rev 11)
  00:14.2 RAM memory: Intel Corporation Raptor Lake-S PCH Shared SRAM (rev 11)
  00:14.3 Network controller: Intel Corporation Raptor Lake-S PCH CNVi WiFi 
(rev 11)
  00:15.0 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #0 (rev 11)
  00:15.1 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #1 (rev 11)
  00:15.2 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C 
Host Controller #2 (rev 11)
  00:16.0 Communication controller: Intel Corporation Raptor Lake CSME HECI #1 
(rev 11)
  00:19.0 Serial bus controller: Intel Corporation Device 7a7c (rev 11)
  00:19.1 Serial bus controller: Intel Corporation Device 7a7d (rev 11)
  00:1a.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #25 
(rev 11)
  00:1b.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #17 
(rev 11)
  00:1b.5 PCI bridge: Intel Corporation Device 7a45 (rev 11)
  00:1d.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Po

[Kernel-packages] [Bug 2034745] Re: [regression] Unable to initialize SGX enclaves with XFRM other than 3

[Fabian Grünbichler]

FWIW, this not only affects the 5.15/jammy kernel series, but also at
least 6.2/lunar: https://github.com/openzfs/zfs/issues/15223 , and also
affects non-SGX use cases like OpenZFS features that benefit from AVX
support (raidz, encryption, ..)

** Bug watch added: github.com/openzfs/zfs/issues #15223
   https://github.com/openzfs/zfs/issues/15223

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

Title:
  [regression] Unable to initialize SGX enclaves with XFRM other than 3

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

Bug description:
  SRU Justification

  [Impact]

  In 5.15.0-1045, only loading enclaves with XFRM set to 3 works,
  sgx_encl_init returns EINVAL. The only reason this wouldn't work
  properly is if sgx_drv_init thinks XSAVE isn't enabled. This works
  fine in 5.15.0-1043.

  Likely cause:
  1045 adds this patch: 
https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4
 . This later patch indicates that the former patch introduced some ordering 
problems. 
https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5
 . That later patch isn't applied to 1045.

  [Test Plan]

  User test results pending, but its a fix commit so should likely be
  applied regardless.

  [Regression Potential]

  SGX could continue to fail.

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


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

[Kernel-packages] [Bug 2028440] Re: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: el subproceso instalado paquete linux-headers-6.2.0-25-generic script post-installatio

[Victor Fabian Miramontes]

Hi, I could finally found the issue and do the upgrade.
It was a matter of three old kernel modules to manage a WiFi USB stick.
I've recover my system from a previous rear archive, removed the modules with 
dkms utility and
the upgrade could be successfully completed.
Thanks

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

Title:
  package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to
  install/upgrade: el subproceso instalado paquete linux-
  headers-6.2.0-25-generic script post-installation devolvió el código
  de salida de error 1

Status in linux package in Ubuntu:
  New

Bug description:
  Upgrade from version 22.10 to 23.04

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-25-generic 6.2.0-25.25
  ProcVersionSignature: Ubuntu 5.19.0-46.47-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  victor 2813 F wireplumber
   /dev/snd/controlC0:  victor 2813 F wireplumber
   /dev/snd/controlC1:  victor 2813 F wireplumber
   /dev/snd/seq:victor 2810 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Sat Jul 22 17:33:12 2023
  ErrorMessage: el subproceso instalado paquete linux-headers-6.2.0-25-generic 
script post-installation devolvió el código de salida de error 1
  InstallationDate: Installed on 2020-09-23 (1032 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   lono wireless extensions.
   
   enp6s0no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. A320M-H
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic 
root=UUID=9d64e1b5-0fff-48b0-91a4-226c99539bd9 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  RfKill:
   
  SourcePackage: linux
  Title: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to 
install/upgrade: el subproceso instalado paquete linux-headers-6.2.0-25-generic 
script post-installation devolvió el código de salida de error 1
  UpgradeStatus: Upgraded to lunar on 2023-07-22 (0 days ago)
  dmi.bios.date: 04/28/2020
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F51
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF51:bd04/28/2020:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnA320M-H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

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


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

[Kernel-packages] [Bug 2028440] [NEW] package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: el subproceso instalado paquete linux-headers-6.2.0-25-generic script post-installat

[Victor Fabian Miramontes]

Public bug reported:

Upgrade from version 22.10 to 23.04

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-headers-6.2.0-25-generic 6.2.0-25.25
ProcVersionSignature: Ubuntu 5.19.0-46.47-generic 5.19.17
Uname: Linux 5.19.0-46-generic x86_64
NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  victor 2813 F wireplumber
 /dev/snd/controlC0:  victor 2813 F wireplumber
 /dev/snd/controlC1:  victor 2813 F wireplumber
 /dev/snd/seq:victor 2810 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
Date: Sat Jul 22 17:33:12 2023
ErrorMessage: el subproceso instalado paquete linux-headers-6.2.0-25-generic 
script post-installation devolvió el código de salida de error 1
InstallationDate: Installed on 2020-09-23 (1032 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
IwConfig:
 lono wireless extensions.
 
 enp6s0no wireless extensions.
 
 docker0   no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. A320M-H
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic 
root=UUID=9d64e1b5-0fff-48b0-91a4-226c99539bd9 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc 2.06-2ubuntu16
RfKill:
 
SourcePackage: linux
Title: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to 
install/upgrade: el subproceso instalado paquete linux-headers-6.2.0-25-generic 
script post-installation devolvió el código de salida de error 1
UpgradeStatus: Upgraded to lunar on 2023-07-22 (0 days ago)
dmi.bios.date: 04/28/2020
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F51
dmi.board.asset.tag: Default string
dmi.board.name: A320M-H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF51:bd04/28/2020:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnA320M-H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: A320M-H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

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


** Tags: amd64 apport-package lunar

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

Title:
  package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to
  install/upgrade: el subproceso instalado paquete linux-
  headers-6.2.0-25-generic script post-installation devolvió el código
  de salida de error 1

Status in linux package in Ubuntu:
  New

Bug description:
  Upgrade from version 22.10 to 23.04

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-25-generic 6.2.0-25.25
  ProcVersionSignature: Ubuntu 5.19.0-46.47-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  victor 2813 F wireplumber
   /dev/snd/controlC0:  victor 2813 F wireplumber
   /dev/snd/controlC1:  victor 2813 F wireplumber
   /dev/snd/seq:victor 2810 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Sat Jul 22 17:33:12 2023
  ErrorMessage: el subproceso instalado paquete linux-headers-6.2.0-25-generic 
script post-installation devolvió el código de salida de error 1
  InstallationDate: Installed on 2020-09-23 (1032 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   lono wireless extensions.
   
   enp6s0no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. A320M-H
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic 
root=UUID=9d64e1b5-0fff-48b0-91a4-226c99539bd9 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained

[Kernel-packages] [Bug 1973065] Re: Zfsutils-Linux: "zvol_wait" script shows error with encrypted volumes

[Fabian Lichtenegger-Lukas]

Hi,

any updates on this?

thx

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

Title:
  Zfsutils-Linux: "zvol_wait" script shows error with encrypted volumes

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  We are currently encounter an issue in the zfsutils-package with
  encrypted zvols.

  The service zfs-volume-wait throws the following error message:
  "Apr 22 13:08:19 test1 zvol_wait[806]: cannot open 
'rpool/export/vault/block': dataset does not exist"

  How to reproduce the error:
  1. zpool create main /dev/sdb
  2. zfs create -o encryption=on -o keylocation=prompt -o keyformat=passphrase 
-V 500M main/test
  3. reboot
  4. systemctl status zfs-volume-wait
  ● zfs-volume-wait.service - Wait for ZFS Volume (zvol) links in /dev
  Loaded: loaded (/lib/systemd/system/zfs-volume-wait.service; enabled; vendor 
preset: enabled)
  Active: active (exited) since Fri 2022-04-22 13:08:19 UTC; 58s ago
  Process: 758 ExecStart=/sbin/zvol_wait (code=exited, status=0/SUCCESS)
  Main PID: 758 (code=exited, status=0/SUCCESS)

  Apr 22 13:08:19 test1 systemd[1]: Starting Wait for ZFS Volume (zvol) links 
in /dev...
  Apr 22 13:08:19 test1 zvol_wait[758]: Testing 1 zvol links
  Apr 22 13:08:19 test1 zvol_wait[806]: cannot open 'rpool/export/vault/block': 
dataset does not exist
  Apr 22 13:08:19 test1 zvol_wait[758]: All zvol links are now present.
  Apr 22 13:08:19 test1 systemd[1]: Finished Wait for ZFS Volume (zvol) links 
in /dev.

  zfs-volume-wait service calls /sbin/zvol_wait which is part of the package 
"zfsutils-linux".
  Line 29, in script "zvol_wait" seems to be causing this error:
  27 filter_out_locked_zvols() {
  28 while read -r zvol; do
  29 if ! [ "$(zfs list -H -o keystatus rpool/export/vault/block "$zvol")" = 
"unavailable" ]; then
  30 echo "$zvol"
  31 fi
  32 done
  33 }

  It seems that this command does not respect the "zfs list" syntax, which 
should be
  "zfs list [-r|-d depth] [-H] [-o property[,...]] [ -t type[,...]] [ -s 
property ] ... [ -S property ] ... [filesystem|volume|snapshot] ..." 
(https://linux.die.net/man/8/zfs)

  Bug was already reported here:
  # https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1969457
  # https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997980

  This fix is causing the issue:
  # https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1888405

  I created an git patch which fixes the issue:
  --- zvol_wait 2022-04-21 19:09:21.57200 +
  +++ zvol_wait_new 2022-04-22 13:25:26.989422811 +
  @@ -26,7 +26,7 @@

  filter_out_locked_zvols() {
  while read -r zvol; do
  - if ! [ "$(zfs list -H -o keystatus rpool/export/vault/block "$zvol")" = 
"unavailable" ]; then
  + if ! [ "$(zfs list -H -o keystatus "$zvol")" = "unavailable" ]; then
  echo "$zvol"
  fi
  done

  After the patch was applied the command works fine:
  root@test1:/sbin# zvol_wait_new
  Testing 1 zvol links
  All zvol links are now present.

  Did i miss anything or is this really a bug?

  Thank you for your help

  Further information:
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  
  Package: zfsutils-linux
  Version: 0.8.3-1ubuntu12.13
  Priority: extra
  Section: admin
  Source: zfs-linux
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian ZFS on Linux maintainers 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 1,297 kB
  Provides: zfsutils
  Depends: libnvpair1linux (= 0.8.3-1ubuntu12.13), libuutil1linux (= 
0.8.3-1ubuntu12.13), libzfs2linux (= 0.8.3-1ubuntu12.13), libzpool2linux (= 
0.8.3-1ubuntu12.13), python3, libblkid1 (>= 2.16), libc6 (>= 2.17), libuuid1 
(>= 2.16)
  Recommends: lsb-base, zfs-zed
  Suggests: nfs-kernel-server, samba-common-bin (>= 3.0.23), zfs-initramfs | 
zfs-dracut
  Conflicts: zfs, zfs-fuse
  Breaks: openrc, spl (<< 0.7.9-2), spl-dkms (<< 0.8.0~rc1), zfs-dkms (<< 
0.7.9-2)
  Replaces: spl (<< 0.7.9-2), spl-dkms
  Homepage: https://zfsonlinux.org/
  Task: ubuntu-live, xubuntu-live, ubuntustudio-dvd-live, ubuntukylin-live, 
ubuntu-mate-live, ubuntu-budgie-live
  Phased-Update-Percentage: 30
  Download-Size: 354 kB
  APT-Manual-Installed: yes
  APT-Sources: http://landscape.test.local/repository/standalone/ubuntu 
focal-updates/main amd64 Packages

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


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

[Kernel-packages] [Bug 1973065] [NEW] Zfsutils-Linux: "zvol_wait" script shows error with encrypted volumes

[Fabian Lichtenegger-Lukas]

Public bug reported:

We are currently encounter an issue in the zfsutils-package with
encrypted zvols.

The service zfs-volume-wait throws the following error message:
"Apr 22 13:08:19 test1 zvol_wait[806]: cannot open 'rpool/export/vault/block': 
dataset does not exist"

How to reproduce the error:
1. zpool create main /dev/sdb
2. zfs create -o encryption=on -o keylocation=prompt -o keyformat=passphrase -V 
500M main/test
3. reboot
4. systemctl status zfs-volume-wait
● zfs-volume-wait.service - Wait for ZFS Volume (zvol) links in /dev
Loaded: loaded (/lib/systemd/system/zfs-volume-wait.service; enabled; vendor 
preset: enabled)
Active: active (exited) since Fri 2022-04-22 13:08:19 UTC; 58s ago
Process: 758 ExecStart=/sbin/zvol_wait (code=exited, status=0/SUCCESS)
Main PID: 758 (code=exited, status=0/SUCCESS)

Apr 22 13:08:19 test1 systemd[1]: Starting Wait for ZFS Volume (zvol) links in 
/dev...
Apr 22 13:08:19 test1 zvol_wait[758]: Testing 1 zvol links
Apr 22 13:08:19 test1 zvol_wait[806]: cannot open 'rpool/export/vault/block': 
dataset does not exist
Apr 22 13:08:19 test1 zvol_wait[758]: All zvol links are now present.
Apr 22 13:08:19 test1 systemd[1]: Finished Wait for ZFS Volume (zvol) links in 
/dev.

zfs-volume-wait service calls /sbin/zvol_wait which is part of the package 
"zfsutils-linux".
Line 29, in script "zvol_wait" seems to be causing this error:
27 filter_out_locked_zvols() {
28 while read -r zvol; do
29 if ! [ "$(zfs list -H -o keystatus rpool/export/vault/block "$zvol")" = 
"unavailable" ]; then
30 echo "$zvol"
31 fi
32 done
33 }

It seems that this command does not respect the "zfs list" syntax, which should 
be
"zfs list [-r|-d depth] [-H] [-o property[,...]] [ -t type[,...]] [ -s property 
] ... [ -S property ] ... [filesystem|volume|snapshot] ..." 
(https://linux.die.net/man/8/zfs)

Bug was already reported here:
# https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1969457
# https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997980

This fix is causing the issue:
# https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1888405

I created an git patch which fixes the issue:
--- zvol_wait 2022-04-21 19:09:21.57200 +
+++ zvol_wait_new 2022-04-22 13:25:26.989422811 +
@@ -26,7 +26,7 @@

filter_out_locked_zvols() {
while read -r zvol; do
- if ! [ "$(zfs list -H -o keystatus rpool/export/vault/block "$zvol")" = 
"unavailable" ]; then
+ if ! [ "$(zfs list -H -o keystatus "$zvol")" = "unavailable" ]; then
echo "$zvol"
fi
done

After the patch was applied the command works fine:
root@test1:/sbin# zvol_wait_new
Testing 1 zvol links
All zvol links are now present.

Did i miss anything or is this really a bug?

Thank you for your help

Further information:
Description:Ubuntu 20.04.4 LTS
Release:20.04


Package: zfsutils-linux
Version: 0.8.3-1ubuntu12.13
Priority: extra
Section: admin
Source: zfs-linux
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Debian ZFS on Linux maintainers 

Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 1,297 kB
Provides: zfsutils
Depends: libnvpair1linux (= 0.8.3-1ubuntu12.13), libuutil1linux (= 
0.8.3-1ubuntu12.13), libzfs2linux (= 0.8.3-1ubuntu12.13), libzpool2linux (= 
0.8.3-1ubuntu12.13), python3, libblkid1 (>= 2.16), libc6 (>= 2.17), libuuid1 
(>= 2.16)
Recommends: lsb-base, zfs-zed
Suggests: nfs-kernel-server, samba-common-bin (>= 3.0.23), zfs-initramfs | 
zfs-dracut
Conflicts: zfs, zfs-fuse
Breaks: openrc, spl (<< 0.7.9-2), spl-dkms (<< 0.8.0~rc1), zfs-dkms (<< 0.7.9-2)
Replaces: spl (<< 0.7.9-2), spl-dkms
Homepage: https://zfsonlinux.org/
Task: ubuntu-live, xubuntu-live, ubuntustudio-dvd-live, ubuntukylin-live, 
ubuntu-mate-live, ubuntu-budgie-live
Phased-Update-Percentage: 30
Download-Size: 354 kB
APT-Manual-Installed: yes
APT-Sources: http://landscape.test.local/repository/standalone/ubuntu 
focal-updates/main amd64 Packages

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


** Tags: zfs zfsutils-linux

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

Title:
  Zfsutils-Linux: "zvol_wait" script shows error with encrypted volumes

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  We are currently encounter an issue in the zfsutils-package with
  encrypted zvols.

  The service zfs-volume-wait throws the following error message:
  "Apr 22 13:08:19 test1 zvol_wait[806]: cannot open 
'rpool/export/vault/block': dataset does not exist"

  How to reproduce the error:
  1. zpool create main /dev/sdb
  2. zfs create -o encryption=on -o keylocation=prompt -o keyformat=passphrase 
-V 500M main/test
  3. reboot
  4. systemctl status zfs-volume-wait
  ● zfs-volume-wait.service - Wait for ZFS Volume (zvol) links in /dev
  Loaded: loaded (/lib/systemd/system/zfs-volume-wait.service; enabled; vendor 
preset: enabled)
  Active: active (exited) si

[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works

[Fabian Bernhard]

Hello, thanks for the fast update.

Unfortunately my personal problem isn't fixed with it. I'm using a Ryzen 7 
5700U (on a hp envy x360-15eu000), with ubuntu 21.10. 
I use full disk encryption with luks, and when I try to boot with the new 
kernel (5.13.0-23, or now the newer 5.13.0-25) I type in the correct password 
and get stuck after this (last appearing message: [...] successfully decypted).
Usually (e.g with the 5.13.0-22 kernel), after decrypting the partition the 
system boots up and a row of instructions appear. With this kernel(s) it's 
completely stuck and nothing happens.

Is anyone else experiencing this issue?

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

Title:
  amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22
  works

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Impish:
  Fix Released

Bug description:
  SRU Justification

  Impact:

  This does not occur with linux-image-5.13.0-22-generic, but does with 
linux-image-5.13.0-23-generic.
  On startup, I get about a 60 second hang, with the following in the kernel 
dmesg:
  Jan  4 15:26:36 inspiron-3505 kernel: [   34.160572] amdgpu :04:00.0: 
amdgp : failed to write reg 28b4 wait reg 28c6
  Jan  4 15:26:56 inspiron-3505 kernel: [   54.189055] amdgpu :04:00.0: 
amdgp : failed to write reg 1a6f4 wait reg 1a706
  Jan  4 15:27:16 inspiron-3505 kernel: [   74.329264] amdgpu :04:00.0: 
amdgp : failed to write reg 28b4 wait reg 28c6
  Jan  4 15:27:36 inspiron-3505 kernel: [   94.337904] amdgpu :04:00.0: 
amdgp : failed to write reg 1a6f4 wait reg 1a706
  I have the following GPU:
  04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Picass
  o (rev c2) (prog-if 00 [VGA controller])
  04:00.0 0300: 1002:15d8 (rev c2)
  (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.)

  I get a similar hang if I start firefox (when it's probing OpenGL
  contexts), and even with glxgears and glxinfo. Seems like anything
  that'd kick on a OpenGL context does it.  I had a freeze as well when
  I tried running firefox and glxgears both.  Along with odd BUG:
  messages logged (I have some in the attached log.)

  I was running with "iommu=pt", but did try with this removed, still
  got the errors (I think amdgpu driver uses the IOMMU even when it's
  set to IOMMU=pt though.).  See the attached log for some very odd
  "[Hardware Error]" messages that were logged on one test run.  I think
  this was when I tried to run firestorm (second life viewer) -- that
  had a large pause then opened to a black window.

  Per Google, I see there was a bug like this that turned up in kernel
  5.14.15 but fixed in 5.14.17.  See
  https://gitlab.freedesktop.org/drm/amd/-/issues/1770

  Thanks!
  --Henry

  Fix:
  upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is 
disabled in Picasso.")

  Patch was included in the Impish kernel in -proposed (5.13.0.24.24)
  from an upstream patch set. multiple confirmations the problem is
  resolved with the kernel in -proposed.

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


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

[Kernel-packages] [Bug 1956396] Re: kernel 5.13.0-23 extremely slow boot on AMD proc/graphics

[Fabian Mettler]

I have a similar bug on my pc with Ubuntu 21.10 after an upgrade to
5.13.0-23 with an AMD Ryzen 3200G. Although in my case, my external
monitor goes to sleep when booting this Kernel version and cannot be
woken up.

Fortunately, I can boot the system with the previous version 5.13.0-19

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

Title:
   kernel 5.13.0-23 extremely slow boot on AMD proc/graphics

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  5.13.0-23 HWE kernel on Linux Mint 20.2 Xfce (Ubuntu 20.04.3)
  Had been using the 5.13 HWE kernel for months with no problems.
  Today the kernel and linux-firmware updated.
  5.13.0-23 kernel now takes about 2 minutes to boot to the login screen.
  Normal boot time is 8 seconds.
  During that time the pc is frozen with only a _ underline cursor that doesn't 
flash.
  Can't change terminals with Ctrl+Alt+F1, etc.
  Problem does not occur when booting 5.11.0-44 or 5.4.0-92 so I'm pretty sure 
the problem is in the kernel and not linux-firmware.

  System information (while using 5.11 kernel)
  CPU:   Topology: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega 
Graphics bits: 64 type: MT MCP
     arch: Zen+ rev: 1 L2 cache: 2048 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 59089
     Speed: 1259 MHz min/max: 1400/3700 MHz boost: enabled Core speeds 
(MHz): 1: 1258 2: 1258
     3: 1258 4: 1258 5: 1257 6: 1260 7: 1267 8: 1330

  Graphics:  Device-1: AMD Picasso vendor: Hewlett-Packard driver: amdgpu v: 
kernel bus ID: 0c:00.0
     chip ID: 1002:15d8
     Display: x11 server: X.Org 1.20.13 driver: amdgpu resolution: 
1920x1080~60Hz
     OpenGL:
     renderer: AMD Radeon Vega 11 Graphics (RAVEN DRM 3.40.0 
5.11.0-44-generic LLVM 12.0.0)
     v: 4.6 Mesa 21.0.3 direct render: Yes

  Forums threads about it:
  https://ubuntuforums.org/showthread.php?t=2470574
  https://forums.linuxmint.com/viewtopic.php?f=46&t=364729

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


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

[Kernel-packages] [Bug 1884997] [NEW] no touchpad detected, not working at all

[Fabian Rücker]

Public bug reported:

hello,

i bought a new pc and installed ubuntu 20.04 and windows 10 on it.
on ubuntu os my touchpad doesn't work at all, since installation process but it 
does on windows.
the pc is a lenovo pc and one of the latest released one.

when i plug in a usb mouse the mouse works fine but the touchpad still don't.
it even doesn't show the touchpad when i type in (1) "cat 
/proc/bus/input/devices".
only the usb mouse twice.

i tryed a lot and don't know how to help myself any further.

i attached a file "devices" where printed my output of (1).

thanks for any help.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-37-generic 5.4.0-37.41
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  fabian 1032 F pulseaudio
 /dev/snd/pcmC0D0p:   fabian 1032 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 24 18:21:17 2020
InstallationDate: Installed on 2020-06-17 (6 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 81WE
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=a65a602e-ae73-4354-94f9-2f99e2bff055 ro i8042.reset quiet splash 
vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-37-generic N/A
 linux-backports-modules-5.4.0-37-generic  N/A
 linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/06/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: EMCN13WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad 3 15IIL05
dmi.modalias: 
dmi:bvnLENOVO:bvrEMCN13WW:bd03/06/2020:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad315IIL05:
dmi.product.family: IdeaPad 3 15IIL05
dmi.product.name: 81WE
dmi.product.sku: LENOVO_MT_81WE_BU_idea_FM_IdeaPad 3 15IIL05
dmi.product.version: IdeaPad 3 15IIL05
dmi.sys.vendor: LENOVO

** Affects: linux (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 in Ubuntu.
https://bugs.launchpad.net/bugs/1884997

Title:
  no touchpad detected, not working at all

Status in linux package in Ubuntu:
  New

Bug description:
  hello,

  i bought a new pc and installed ubuntu 20.04 and windows 10 on it.
  on ubuntu os my touchpad doesn't work at all, since installation process but 
it does on windows.
  the pc is a lenovo pc and one of the latest released one.

  when i plug in a usb mouse the mouse works fine but the touchpad still don't.
  it even doesn't show the touchpad when i type in (1) "cat 
/proc/bus/input/devices".
  only the usb mouse twice.

  i tryed a lot and don't know how to help myself any further.

  i attached a file "devices" where printed my output of (1).

  thanks for any help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-37-generic 5.4.0-37.41
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fabian 1032 F pulseaudio
   /dev/snd/pcmC0D0p:   fabian 1032 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 24 18:21:17 2020
  InstallationDate: Installed on 2020-06-17 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81WE
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=a65a602e-ae73-4354-94f9-2f99e2bff055 ro i8042.reset quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-37-generic N/A
   linux-backports-modules-5.4.0-37-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EMCN13WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO As

[Kernel-packages] [Bug 1857040] Re: zfs: upstream support for hardware-accelerated encryption

[Fabian Grünbichler]

the following backport from the 0.8.3 queue should be what you are
looking for:

https://github.com/zfsonlinux/zfs/pull/9776/commits/ed3d9f4420dcb04d2b78de4e4adb25797dc93b0d

it does not include/depend on either of the problematic commits, but
does contain all known squashed follow-up fixes.

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

Title:
  zfs: upstream support for hardware-accelerated encryption

Status in linux package in Ubuntu:
  In Progress

Bug description:
  I understand that in Linux 5.0+, certain encryption-related symbols
  have been marked GPL-only, making them unavailable for use by zfs.  As
  a result, using encryption in zfs pools increases cpu load / decreases
  disk throughput.

  There are a pair of upstream pull requests that should improve the
  performance (with performance measurement done on x86-64).  Can these
  be pulled into the Ubuntu kernel?

  https://github.com/zfsonlinux/zfs/pull/9515
  https://github.com/zfsonlinux/zfs/pull/9296

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

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

[Kernel-packages] [Bug 1851709] Re: Ubuntu-5.0.0-33.35 introduces KVM regression with old Intel CPUs and Linux guests

[Fabian Grünbichler]

https://lore.kernel.org/lkml/68d02406-b9cc-2fc1-848c-
5d272d9a3...@proxmox.com/ contains upstream discussion, with mention of
a backported fix for 4.14 and 4.19..

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

Title:
  Ubuntu-5.0.0-33.35 introduces KVM regression with old Intel CPUs and
  Linux guests

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Mostly the same info as on a related kernel.org bugzilla entr[0].

  [0]: https://bugzilla.kernel.org/show_bug.cgi?id=205441

  We got issues reported with old Intel CPUs and Linux guest run with
  QEMU/KVM after a recent kernel update which is based on
  Ubuntu-5.0.0-33.35.

  I bisected this here, with following result:
  git bisect log 
  # bad: [3b931173c97b0d73f80ea55b72bb2966a246167f] UBUNTU: Ubuntu-5.0.0-33.35
  # good: [5d5a6b36e94909962297fae609bff487de3cc43a] UBUNTU: Ubuntu-5.0.0-30.32
  git bisect start '3b931173c97b0d73f80ea55b72bb2966a246167f'
  '5d5a6b36e94909962297fae609bff487de3cc43a'
  # good: [7b4f844b33969ab166800f8936beef153fab736e] net/ibmvnic: free reset 
work
  of removed device from queue
  git bisect good 7b4f844b33969ab166800f8936beef153fab736e
  # bad: [6c1fc88702a4f33886b44ce5b6f374893b95e369] arm64: tlb: Ensure we 
execute
  an ISB following walk cache invalidation
  git bisect bad 6c1fc88702a4f33886b44ce5b6f374893b95e369
  # good: [e627a027b54eccc95f9e374d69aead7f1498877b] loop: Add 
LOOP_SET_DIRECT_IO
  to compat ioctl
  git bisect good e627a027b54eccc95f9e374d69aead7f1498877b
  # good: [29919eff6333bc67ec580b454afdd8b49883df2f] libata/ahci: Drop PCS quirk
  for Denverton and beyond
  git bisect good 29919eff6333bc67ec580b454afdd8b49883df2f
  # good: [cb44193f94af73928f8df049ffbb6b4a0be136ae] PM / devfreq: passive: fix
  compiler warning
  git bisect good cb44193f94af73928f8df049ffbb6b4a0be136ae
  # good: [b1d479b27b26966aea931094b31864979d7f8102] scsi: implement .cleanup_rq
  callback
  git bisect good b1d479b27b26966aea931094b31864979d7f8102
  # bad: [ec15813844b05d8cbd4352c65a20e57d16f9f936] media: sn9c20x: Add MSI
  MS-1039 laptop to flip_dmi_table
  git bisect bad ec15813844b05d8cbd4352c65a20e57d16f9f936
  # good: [e83601f51a90d9739ced9ff42b6f202f8f802c72] parisc: Disable HP HSC-PCI
  Cards to prevent kernel crash
  git bisect good e83601f51a90d9739ced9ff42b6f202f8f802c72
  # good: [6d393bdf3b3f4b629070329488d3c6a3e142602b] KVM: x86: set
  ctxt->have_exception in x86_decode_insn()
  git bisect good 6d393bdf3b3f4b629070329488d3c6a3e142602b
  # bad: [208007519a7385a57b0c0a3c180142a521594876] KVM: x86: Manually calculate
  reserved bits when loading PDPTRS
  git bisect bad 208007519a7385a57b0c0a3c180142a521594876
  # first bad commit: [208007519a7385a57b0c0a3c180142a521594876] KVM: x86:
  Manually calculate reserved bits when loading PDPTRS

  Which is:

 KVM: x86: Manually calculate reserved bits when loading PDPTRS

  BugLink: https://bugs.launchpad.net/bugs/1848367

  commit 16cfacc8085782dab8e365979356ce1ca87fd6cc upstream.

  Manually generate the PDPTR reserved bit mask when explicitly loading
  PDPTRs.  The reserved bits that are being tracked by the MMU reflect the
  current paging mode, which is unlikely to be PAE paging in the vast
  majority of flows that use load_pdptrs(), e.g. CR0 and CR4 emulation,
  __set_sregs(), etc...  This can cause KVM to incorrectly signal a bad
  PDPTR, or more likely, miss a reserved bit check and subsequently fail
  a VM-Enter due to a bad VMCS.GUEST_PDPTR.

  Add a one off helper to generate the reserved bits instead of sharing
  code across the MMU's calculations and the PDPTR emulation.  The PDPTR
  reserved bits are basically set in stone, and pushing a helper into
  the MMU's calculation adds unnecessary complexity without improving
  readability.

  Oppurtunistically fix/update the comment for load_pdptrs().

  Note, the buggy commit also introduced a deliberate functional change,
  "Also remove bit 5-6 from rsvd_bits_mask per latest SDM.", which was
  effectively (and correctly) reverted by commit cd9ae5fe47df ("KVM: x86:
  Fix page-tables reserved bits").  A bit of SDM archaeology shows that
  the SDM from late 2008 had a bug (likely a copy+paste error) where it
  listed bits 6:5 as AVL and A for PDPTEs used for 4k entries but reserved
  for 2mb entries.  I.e. the SDM contradicted itself, and bits 6:5 are and
  always have been reserved.

  Fixes: 20c466b56168d ("KVM: Use rsvd_bits_mask in load_pdptrs()")
  Cc: sta...@vger.kernel.org
  Cc: Nadav Amit 
  Reported-by: Doug Reiland 
  Signed-off-by: Sean Christopherson 
  Reviewed-by: Peter Xu 
  Signed-off-by: Paolo Bonzini 
  Signed-off-by: Greg Kroah-Hartman 
  Signed-off-by: Kamal Mostafa 
  Signed-off-by: Kleber Sacilotto de Souza 

  
  This one is also inclu

[Kernel-packages] [Bug 1851709] Re: Ubuntu-5.0.0-33.35 introduces KVM regression with old Intel CPUs and Linux guests

[Fabian Grünbichler]

https://lore.kernel.org/lkml/2019225423.29309-1-sean.j.christopher...@intel.com/
is the fix for 4.19

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

Title:
  Ubuntu-5.0.0-33.35 introduces KVM regression with old Intel CPUs and
  Linux guests

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Mostly the same info as on a related kernel.org bugzilla entr[0].

  [0]: https://bugzilla.kernel.org/show_bug.cgi?id=205441

  We got issues reported with old Intel CPUs and Linux guest run with
  QEMU/KVM after a recent kernel update which is based on
  Ubuntu-5.0.0-33.35.

  I bisected this here, with following result:
  git bisect log 
  # bad: [3b931173c97b0d73f80ea55b72bb2966a246167f] UBUNTU: Ubuntu-5.0.0-33.35
  # good: [5d5a6b36e94909962297fae609bff487de3cc43a] UBUNTU: Ubuntu-5.0.0-30.32
  git bisect start '3b931173c97b0d73f80ea55b72bb2966a246167f'
  '5d5a6b36e94909962297fae609bff487de3cc43a'
  # good: [7b4f844b33969ab166800f8936beef153fab736e] net/ibmvnic: free reset 
work
  of removed device from queue
  git bisect good 7b4f844b33969ab166800f8936beef153fab736e
  # bad: [6c1fc88702a4f33886b44ce5b6f374893b95e369] arm64: tlb: Ensure we 
execute
  an ISB following walk cache invalidation
  git bisect bad 6c1fc88702a4f33886b44ce5b6f374893b95e369
  # good: [e627a027b54eccc95f9e374d69aead7f1498877b] loop: Add 
LOOP_SET_DIRECT_IO
  to compat ioctl
  git bisect good e627a027b54eccc95f9e374d69aead7f1498877b
  # good: [29919eff6333bc67ec580b454afdd8b49883df2f] libata/ahci: Drop PCS quirk
  for Denverton and beyond
  git bisect good 29919eff6333bc67ec580b454afdd8b49883df2f
  # good: [cb44193f94af73928f8df049ffbb6b4a0be136ae] PM / devfreq: passive: fix
  compiler warning
  git bisect good cb44193f94af73928f8df049ffbb6b4a0be136ae
  # good: [b1d479b27b26966aea931094b31864979d7f8102] scsi: implement .cleanup_rq
  callback
  git bisect good b1d479b27b26966aea931094b31864979d7f8102
  # bad: [ec15813844b05d8cbd4352c65a20e57d16f9f936] media: sn9c20x: Add MSI
  MS-1039 laptop to flip_dmi_table
  git bisect bad ec15813844b05d8cbd4352c65a20e57d16f9f936
  # good: [e83601f51a90d9739ced9ff42b6f202f8f802c72] parisc: Disable HP HSC-PCI
  Cards to prevent kernel crash
  git bisect good e83601f51a90d9739ced9ff42b6f202f8f802c72
  # good: [6d393bdf3b3f4b629070329488d3c6a3e142602b] KVM: x86: set
  ctxt->have_exception in x86_decode_insn()
  git bisect good 6d393bdf3b3f4b629070329488d3c6a3e142602b
  # bad: [208007519a7385a57b0c0a3c180142a521594876] KVM: x86: Manually calculate
  reserved bits when loading PDPTRS
  git bisect bad 208007519a7385a57b0c0a3c180142a521594876
  # first bad commit: [208007519a7385a57b0c0a3c180142a521594876] KVM: x86:
  Manually calculate reserved bits when loading PDPTRS

  Which is:

 KVM: x86: Manually calculate reserved bits when loading PDPTRS

  BugLink: https://bugs.launchpad.net/bugs/1848367

  commit 16cfacc8085782dab8e365979356ce1ca87fd6cc upstream.

  Manually generate the PDPTR reserved bit mask when explicitly loading
  PDPTRs.  The reserved bits that are being tracked by the MMU reflect the
  current paging mode, which is unlikely to be PAE paging in the vast
  majority of flows that use load_pdptrs(), e.g. CR0 and CR4 emulation,
  __set_sregs(), etc...  This can cause KVM to incorrectly signal a bad
  PDPTR, or more likely, miss a reserved bit check and subsequently fail
  a VM-Enter due to a bad VMCS.GUEST_PDPTR.

  Add a one off helper to generate the reserved bits instead of sharing
  code across the MMU's calculations and the PDPTR emulation.  The PDPTR
  reserved bits are basically set in stone, and pushing a helper into
  the MMU's calculation adds unnecessary complexity without improving
  readability.

  Oppurtunistically fix/update the comment for load_pdptrs().

  Note, the buggy commit also introduced a deliberate functional change,
  "Also remove bit 5-6 from rsvd_bits_mask per latest SDM.", which was
  effectively (and correctly) reverted by commit cd9ae5fe47df ("KVM: x86:
  Fix page-tables reserved bits").  A bit of SDM archaeology shows that
  the SDM from late 2008 had a bug (likely a copy+paste error) where it
  listed bits 6:5 as AVL and A for PDPTEs used for 4k entries but reserved
  for 2mb entries.  I.e. the SDM contradicted itself, and bits 6:5 are and
  always have been reserved.

  Fixes: 20c466b56168d ("KVM: Use rsvd_bits_mask in load_pdptrs()")
  Cc: sta...@vger.kernel.org
  Cc: Nadav Amit 
  Reported-by: Doug Reiland 
  Signed-off-by: Sean Christopherson 
  Reviewed-by: Peter Xu 
  Signed-off-by: Paolo Bonzini 
  Signed-off-by: Greg Kroah-Hartman 
  Signed-off-by: Kamal Mostafa 
  Signed-off-by: Kleber Sacilotto de Souza 

  
  This one is also included in the 4.19.81 (or more correctly, it's there since 
 

[Kernel-packages] [Bug 1852047] Re: [Bionic][Regression] Disabling EPT results in KVM guests that won't start

[Fabian Grünbichler]

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

** This bug has been marked a duplicate of bug 1851709
   Ubuntu-5.0.0-33.35 introduces KVM regression with old Intel CPUs and Linux 
guests

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

Title:
  [Bionic][Regression] Disabling EPT results in KVM guests that won't
  start

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

Bug description:
  [Impact]
  On CPUs with no EPT support, or when disabling kvm-intel ept support by use 
of ept=0 module parameter, users are not able to launch a linux VM.

  [Test case]
  # modprobe kvm-intel ept=0
  # cat /sys/module/kvm_intel/parameters/ept
  N
  # qemu-system-x86_64 -enable-kvm -kernel /boot/vmlinuz-4.15.0-68-generic

  Make sure you get console log at all. With the bug, there is not a
  single line of output.

  [Regression potential]
  The fix might cause some very specific use of virtualization to fail, but no 
pratical case is known.

  
  ===

  Starting with 4.15.0-68.77, currently in bionic-proposed, I can no
  longer launch VMs when I disable EPT support in the kvm_intel module.
  This works fine under 4.15.0-66.75 from bionic-security.

   ubuntu@vought:~$ cat /proc/version_signature
   Ubuntu 4.15.0-68.77-generic 4.15.18
   ubuntu@vought:~$ sudo rmmod kvm_intel
   ubuntu@vought:~$ sudo modprobe kvm_intel ept=0
   ubuntu@vought:~$ cat /sys/module/kvm_intel/parameters/ept
   N
   ubuntu@vought:~$ virsh start --console l1
   Domain l1 started
   Connected to domain l1
   Escape character is ^]

  Under 4.15.0-66.75, I see full console output from the guest and reach
  a login prompt. Under 4.15.0-68.77, I see no output and the VM is
  unresponsive. I see nothing of use in /var/log/libvirt/qemu/l1.log.

  I see this on the following system:

  ubuntu@vought:~$ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  96
  On-line CPU(s) list: 0-95
  Thread(s) per core:  2
  Core(s) per socket:  24
  Socket(s):   2
  NUMA node(s):2
  Vendor ID:   GenuineIntel
  CPU family:  6
  Model:   85
  Model name:  Intel(R) Xeon(R) Gold 6252 CPU @ 2.10GHz
  Stepping:6
  CPU MHz: 1000.135
  CPU max MHz: 3700.
  CPU min MHz: 1000.
  BogoMIPS:4200.00
  Virtualization:  VT-x
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:1024K
  L3 cache:36608K
  NUMA node0 CPU(s):   0-23,48-71
  NUMA node1 CPU(s):   24-47,72-95
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl 
xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx 
smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe 
popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch 
cpuid_fault epb cat_l3 cdp_l3 invpcid_single ssbd mba ibrs ibpb stibp 
ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 
hle avx2 smep bmi2 erms invpcid rtm cqm mpx rdt_a avx512f avx512dq rdseed adx 
smap clflushopt clwb intel_pt avx512cd avx512bw avx512vl xsaveopt xsavec 
xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida 
arat pln pts hwp hwp_act_window hwp_epp hwp_pkg_req pku ospke avx512_vnni 
md_clear flush_l1d arch_capabilities

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

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

[Kernel-packages] [Bug 1842850] Re: NULL pointer dereference in kvm_mmu_flush_or_zap

[Fabian Zimmermann]

We had the issue 2 times within ~3 weeks, so we moved the system out of
production, updated every firmware possible, started loadtesting - but
are unable to enforce it.

We now moved the system back to production so see if the issue happens
again (~2 weeks ago).

I will report as soon as we have the issue again.

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

Title:
  NULL pointer dereference in kvm_mmu_flush_or_zap

Status in linux package in Ubuntu:
  Expired

Bug description:
  tonight one of our systems run into the following panic

  --
  kernel NULL pointer dereference at 
  kernel: [2468259.002689] IP: kvm_mmu_flush_or_zap+0x5/0x40 [kvm]
  kernel: [2468259.007758] PGD 0 P4D 0 
  kernel: [2468259.010483] Oops:  [#1] SMP PTI
  kernel: [2468259.014161] Modules linked in: vhost_net vhost tap xt_nat 
xt_REDIRECT nf_nat_redirect ip6table_mangle xt_mark xt_connmark xt_multiport 
xt_set ip_set_hash_net ip_set xt_CT xt_mac veth vxlan ip6_udp_tunnel udp_tunnel 
ip6table_raw xt_physdev xt_comment xt_CHECKSUM xt_tcpudp iptable_mangle 
iptable_raw ebtable_filter ebtables nf_conntrack_netlink nfnetlink xfrm_user 
xfrm_algo br_netfilter bridge aufs rbd libceph binfmt_misc 8021q garp mrp stp 
llc bonding openvswitch nsh nf_conntrack_ipv6 nf_nat_ipv6 rdma_ucm(OE) 
ib_ucm(OE) nf_defrag_ipv6 ib_ipoib(OE) ip6table_filter ib_umad(OE) xt_conntrack 
mlx5_fpga_tools(OE) mlx5_ib(OE) ib_uverbs(OE) iptable_filter mlx4_ib(OE) 
mlx4_en(OE) mlx4_core(OE) ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_addrtype 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack
  kernel: [2468259.085884]  ip_tables ipmi_ssif intel_rapl skx_edac 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 
crypto_simd glue_helper dell_smbios dcdbas cryptd intel_cstate 
dell_wmi_descriptor wmi_bmof intel_rapl_perf mei_me mei lpc_ich shpchp ipmi_si 
ipmi_devintf ipmi_msghandler acpi_power_meter mac_hid rdma_cm(OE) iw_cm(OE) 
ib_cm(OE) ib_core(OE) iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
ip6_tables x_tables autofs4 mgag200 i2c_algo_bit ttm mlx5_core(OE) mlxfw(OE) 
devlink drm_kms_helper syscopyarea sysfillrect bnx2x mlx_compat(OE) sysimgblt 
ptp fb_sys_fops pps_core mdio drm libcrc32c ahci libahci wmi
  kernel: [2468259.148257] CPU: 21 PID: 3455197 Comm: CPU 11/KVM Tainted: G 
  OE4.15.0-55-generic #60~16.04.2-Ubuntu
  kernel: [2468259.158712] Hardware name: Dell Inc. PowerEdge R640/0PHYDR, BIOS 
2.2.10 05/15/2019
  kernel: [2468259.166510] RIP: 0010:kvm_mmu_flush_or_zap+0x5/0x40 [kvm]
  kernel: [2468259.172097] RSP: 0018:ad129f5b3ac8 EFLAGS: 00010246
  kernel: [2468259.177514] RAX:  RBX: 93dcbb5df5a8 RCX: 

  kernel: [2468259.184840] RDX:  RSI:  RDI: 
940b7ff38000
  kernel: [2468259.192168] RBP: ad129f5b3b30 R08: 0001 R09: 

  kernel: [2468259.199495] R10: 0001 R11: 0781 R12: 
940b7ff38000
  kernel: [2468259.206820] R13:  R14:  R15: 
00802800
  kernel: [2468259.214151] FS:  7f6de8ff9700() 
GS:9411ff28() knlGS:964c1f4c
  kernel: [2468259.222431] CS:  0010 DS:  ES:  CR0: 80050033
  kernel: [2468259.228369] CR2:  CR3: 00b54b6f8002 CR4: 
007626e0
  kernel: [2468259.235694] DR0:  DR1:  DR2: 

  kernel: [2468259.243018] DR3:  DR6: fffe0ff0 DR7: 
0400
  kernel: [2468259.250348] PKRU: 5554
  kernel: [2468259.253245] Call Trace:
  kernel: [2468259.255910]  ? kvm_mmu_get_page+0x29a/0x6b0 [kvm]
  kernel: [2468259.260814]  __direct_map.part.124+0xf5/0x220 [kvm]
  kernel: [2468259.265901]  tdp_page_fault+0x264/0x290 [kvm]
  kernel: [2468259.270462]  kvm_mmu_page_fault+0x62/0x170 [kvm]
  kernel: [2468259.275278]  handle_ept_violation+0xae/0x140 [kvm_intel]
  kernel: [2468259.280781]  vmx_handle_exit+0xb3/0xcd0 [kvm_intel]
  kernel: [2468259.285867]  ? vmx_vcpu_run+0x41d/0x600 [kvm_intel]
  kernel: [2468259.290960]  vcpu_enter_guest+0x451/0x1280 [kvm]
  kernel: [2468259.295774]  ? vmx_sync_pir_to_irr+0x39/0x70 [kvm_intel]
  kernel: [2468259.301307]  kvm_arch_vcpu_ioctl_run+0x270/0x3d0 [kvm]
  kernel: [2468259.306652]  ? kvm_arch_vcpu_ioctl_run+0x270/0x3d0 [kvm]
  kernel: [2468259.312163]  kvm_vcpu_ioctl+0x33a/0x610 [kvm]
  kernel: [2468259.317432]  ? do_futex+0x10f/0x500
  kernel: [2468259.321830]  do_vfs_ioctl+0xa4/0x600
  kernel: [2468259.326244]  ? SyS_futex+0x7f/0x180
  kernel: [2468259.330523]  SyS_ioctl+0x79/0x90
  kernel: [2468259.334561]  do_syscall_64+0x73/0x130
  kernel: [2468259.338992]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  kernel: [2468259.344817] R

[Kernel-packages] [Bug 1842850] [NEW] NULL pointer dereference in kvm_mmu_flush_or_zap

[Fabian Zimmermann]

Public bug reported:

tonight one of our systems run into the following panic

--
kernel NULL pointer dereference at 
kernel: [2468259.002689] IP: kvm_mmu_flush_or_zap+0x5/0x40 [kvm]
kernel: [2468259.007758] PGD 0 P4D 0 
kernel: [2468259.010483] Oops:  [#1] SMP PTI
kernel: [2468259.014161] Modules linked in: vhost_net vhost tap xt_nat 
xt_REDIRECT nf_nat_redirect ip6table_mangle xt_mark xt_connmark xt_multiport 
xt_set ip_set_hash_net ip_set xt_CT xt_mac veth vxlan ip6_udp_tunnel udp_tunnel 
ip6table_raw xt_physdev xt_comment xt_CHECKSUM xt_tcpudp iptable_mangle 
iptable_raw ebtable_filter ebtables nf_conntrack_netlink nfnetlink xfrm_user 
xfrm_algo br_netfilter bridge aufs rbd libceph binfmt_misc 8021q garp mrp stp 
llc bonding openvswitch nsh nf_conntrack_ipv6 nf_nat_ipv6 rdma_ucm(OE) 
ib_ucm(OE) nf_defrag_ipv6 ib_ipoib(OE) ip6table_filter ib_umad(OE) xt_conntrack 
mlx5_fpga_tools(OE) mlx5_ib(OE) ib_uverbs(OE) iptable_filter mlx4_ib(OE) 
mlx4_en(OE) mlx4_core(OE) ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_addrtype 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack
kernel: [2468259.085884]  ip_tables ipmi_ssif intel_rapl skx_edac 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 
crypto_simd glue_helper dell_smbios dcdbas cryptd intel_cstate 
dell_wmi_descriptor wmi_bmof intel_rapl_perf mei_me mei lpc_ich shpchp ipmi_si 
ipmi_devintf ipmi_msghandler acpi_power_meter mac_hid rdma_cm(OE) iw_cm(OE) 
ib_cm(OE) ib_core(OE) iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
ip6_tables x_tables autofs4 mgag200 i2c_algo_bit ttm mlx5_core(OE) mlxfw(OE) 
devlink drm_kms_helper syscopyarea sysfillrect bnx2x mlx_compat(OE) sysimgblt 
ptp fb_sys_fops pps_core mdio drm libcrc32c ahci libahci wmi
kernel: [2468259.148257] CPU: 21 PID: 3455197 Comm: CPU 11/KVM Tainted: G   
OE4.15.0-55-generic #60~16.04.2-Ubuntu
kernel: [2468259.158712] Hardware name: Dell Inc. PowerEdge R640/0PHYDR, BIOS 
2.2.10 05/15/2019
kernel: [2468259.166510] RIP: 0010:kvm_mmu_flush_or_zap+0x5/0x40 [kvm]
kernel: [2468259.172097] RSP: 0018:ad129f5b3ac8 EFLAGS: 00010246
kernel: [2468259.177514] RAX:  RBX: 93dcbb5df5a8 RCX: 

kernel: [2468259.184840] RDX:  RSI:  RDI: 
940b7ff38000
kernel: [2468259.192168] RBP: ad129f5b3b30 R08: 0001 R09: 

kernel: [2468259.199495] R10: 0001 R11: 0781 R12: 
940b7ff38000
kernel: [2468259.206820] R13:  R14:  R15: 
00802800
kernel: [2468259.214151] FS:  7f6de8ff9700() GS:9411ff28() 
knlGS:964c1f4c
kernel: [2468259.222431] CS:  0010 DS:  ES:  CR0: 80050033
kernel: [2468259.228369] CR2:  CR3: 00b54b6f8002 CR4: 
007626e0
kernel: [2468259.235694] DR0:  DR1:  DR2: 

kernel: [2468259.243018] DR3:  DR6: fffe0ff0 DR7: 
0400
kernel: [2468259.250348] PKRU: 5554
kernel: [2468259.253245] Call Trace:
kernel: [2468259.255910]  ? kvm_mmu_get_page+0x29a/0x6b0 [kvm]
kernel: [2468259.260814]  __direct_map.part.124+0xf5/0x220 [kvm]
kernel: [2468259.265901]  tdp_page_fault+0x264/0x290 [kvm]
kernel: [2468259.270462]  kvm_mmu_page_fault+0x62/0x170 [kvm]
kernel: [2468259.275278]  handle_ept_violation+0xae/0x140 [kvm_intel]
kernel: [2468259.280781]  vmx_handle_exit+0xb3/0xcd0 [kvm_intel]
kernel: [2468259.285867]  ? vmx_vcpu_run+0x41d/0x600 [kvm_intel]
kernel: [2468259.290960]  vcpu_enter_guest+0x451/0x1280 [kvm]
kernel: [2468259.295774]  ? vmx_sync_pir_to_irr+0x39/0x70 [kvm_intel]
kernel: [2468259.301307]  kvm_arch_vcpu_ioctl_run+0x270/0x3d0 [kvm]
kernel: [2468259.306652]  ? kvm_arch_vcpu_ioctl_run+0x270/0x3d0 [kvm]
kernel: [2468259.312163]  kvm_vcpu_ioctl+0x33a/0x610 [kvm]
kernel: [2468259.317432]  ? do_futex+0x10f/0x500
kernel: [2468259.321830]  do_vfs_ioctl+0xa4/0x600
kernel: [2468259.326244]  ? SyS_futex+0x7f/0x180
kernel: [2468259.330523]  SyS_ioctl+0x79/0x90
kernel: [2468259.334561]  do_syscall_64+0x73/0x130
kernel: [2468259.338992]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
kernel: [2468259.344817] RIP: 0033:0x7f6e379b2f47
kernel: [2468259.349187] RSP: 002b:7f6de8ff88f8 EFLAGS: 0246 ORIG_RAX: 
0010
kernel: [2468259.357529] RAX: ffda RBX: ae80 RCX: 
7f6e379b2f47
kernel: [2468259.365415] RDX:  RSI: ae80 RDI: 
002e
kernel: [2468259.373286] RBP: 55e3147d6a40 R08: 55e311e25810 R09: 
0001
kernel: [2468259.381202] R10: 0046 R11: 0246 R12: 

kernel: [2468259.389103] R13: 7f6e3c867000 R14: 0006 R15: 
55e3147d6a40
kernel: [2468259.396946] Code: 89 fa 4c 89 f6 e8 2c 8c e6 ef 49 8b 04 24 48 85 
c0 75

[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)

[Fabian]

Hi,

a little update from my side: It seems that faulty memory was the reason
for the data corruptions in my case. I have replaced the memory module
and everything seems to work fine now. I was quite surprised though that
the memory was defective since I did test it carefully for many hours
with memtest (20+ passes without any errors). The errors only occured
when running Ubuntu ...

The memory was the only thing I have changed, so I am very sure that
this was the cause ...

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lz   

[Kernel-packages] [Bug 1820419] Re: linux-generic should depend on linux-base >=4.1

[Fabian Zimmermann]

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

** No longer affects: linux (Ubuntu)

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

Title:
  linux-generic should depend on linux-base >=4.1

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,

  we run a automated pipeline which automatically installs ubuntu 16.04
  by pxe / netinstall.

  This pipeline stopped working tonight, so I did some research.

  Looks like linux-generic depends on linux-base, but requires a
  tool/script which was added in 4.1 (linux-update-symlinks).

  packages.ubuntu.com only shows linux-base 4.5, but if I take a look
  into the packages.gz of /ubuntu/ there is still a 4.0
  available.

  So somehow(tm) it seems netinstall is installing the 4.0 version of
  linux-base instead of the required 4.5 (4.1+).

  In my opinion if a pkg needs a feature which is only available in a
  newer version of a pkg, this pkg should be a depend, so linux-generic
  should depend on linux-base >= 4.1 instead of just depend on linux-
  base.

  I workarounded the problem by installing the hwe-kernel which has a
  correct dependency on linux-base 4.5.

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

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

[Kernel-packages] [Bug 1820419] [NEW] linux-generic should depend on linux-base >=4.1

[Fabian Zimmermann]

Public bug reported:

Hi,

we run a automated pipeline which automatically installs ubuntu 16.04 by
pxe / netinstall.

This pipeline stopped working tonight, so I did some research.

Looks like linux-generic depends on linux-base, but requires a
tool/script which was added in 4.1 (linux-update-symlinks).

packages.ubuntu.com only shows linux-base 4.5, but if I take a look into
the packages.gz of /ubuntu/ there is still a 4.0 available.

So somehow(tm) it seems netinstall is installing the 4.0 version of
linux-base instead of the required 4.5 (4.1+).

In my opinion if a pkg needs a feature which is only available in a
newer version of a pkg, this pkg should be a depend, so linux-generic
should depend on linux-base >= 4.1 instead of just depend on linux-base.

I workarounded the problem by installing the hwe-kernel which has a
correct dependency on linux-base 4.5.

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

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

Title:
  linux-generic should depend on linux-base >=4.1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  we run a automated pipeline which automatically installs ubuntu 16.04
  by pxe / netinstall.

  This pipeline stopped working tonight, so I did some research.

  Looks like linux-generic depends on linux-base, but requires a
  tool/script which was added in 4.1 (linux-update-symlinks).

  packages.ubuntu.com only shows linux-base 4.5, but if I take a look
  into the packages.gz of /ubuntu/ there is still a 4.0
  available.

  So somehow(tm) it seems netinstall is installing the 4.0 version of
  linux-base instead of the required 4.5 (4.1+).

  In my opinion if a pkg needs a feature which is only available in a
  newer version of a pkg, this pkg should be a depend, so linux-generic
  should depend on linux-base >= 4.1 instead of just depend on linux-
  base.

  I workarounded the problem by installing the hwe-kernel which has a
  correct dependency on linux-base 4.5.

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

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

[Kernel-packages] [Bug 1684240] Re: Lagging square around mouse pointer

[Fabian Weise]

Hi,

are there any updates on this bug so far? Still interested in whether
this may be patched at some time. Just installed Kubuntu 16.04 using an
NVIDIA Quadro P1000 and I am experiencing the same issues.

** Information type changed from Public Security to Public

** Information type changed from Public to Public Security

** Information type changed from Public Security to Public

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

Title:
  Lagging square around mouse pointer

Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in plasma-workspace package in Ubuntu:
  Confirmed

Bug description:
  (This can also be an nvidia related problem)

  Mouse pointer behaves as if it has an invisible square attached to it.
  This square covers some area next to the pointer, but it is not always
  clear exactly where (a link to a screenshot is shown below, please
  note the white square with some text from the previous webpage
  displayed in that window).

  This makes selecting text difficult, as one never knows where exactly
  the selection ends. Also, scrolling in some windows becomes
  problematic, as the pointer shadows a part of the scrollbar. When a
  text is being typed, one needs to make sure that the pointer is parked
  sufficiently far from the text (so, to make a long story short, this
  is very annoying).

  This behavior does not depend on the choice of the cursor theme.

  (A link to the screenshot: https://goo.gl/photos/92KKGyFs3AkdxYb79)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: plasma-workspace 4:5.9.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 19 10:41:58 2017
  InstallationDate: Installed on 2015-06-05 (684 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: plasma-workspace
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (5 days ago)

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

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

[Kernel-packages] [Bug 1684240] Re: Lagging square around mouse pointer

[Fabian Weise]

** Information type changed from Public to Public Security

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

Title:
  Lagging square around mouse pointer

Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in plasma-workspace package in Ubuntu:
  Confirmed

Bug description:
  (This can also be an nvidia related problem)

  Mouse pointer behaves as if it has an invisible square attached to it.
  This square covers some area next to the pointer, but it is not always
  clear exactly where (a link to a screenshot is shown below, please
  note the white square with some text from the previous webpage
  displayed in that window).

  This makes selecting text difficult, as one never knows where exactly
  the selection ends. Also, scrolling in some windows becomes
  problematic, as the pointer shadows a part of the scrollbar. When a
  text is being typed, one needs to make sure that the pointer is parked
  sufficiently far from the text (so, to make a long story short, this
  is very annoying).

  This behavior does not depend on the choice of the cursor theme.

  (A link to the screenshot: https://goo.gl/photos/92KKGyFs3AkdxYb79)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: plasma-workspace 4:5.9.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 19 10:41:58 2017
  InstallationDate: Installed on 2015-06-05 (684 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: plasma-workspace
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (5 days ago)

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

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

[Kernel-packages] [Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"

[Fabian Schlenz]

4.15.0-38-generic is also affected. I had zero problems with xenial,
this only happens since I upgraded to bionic...

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

Title:
  Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-
  Off"

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  Hardware: HPE ProLiant DL360 gen9
  Ubuntu Version: 18.04

  Problem: When rebooting the server, everything goes well (shutting
  down services, unmounting etc) until the last step where it reads
  "Starting Reboot". At this point the system is getting stuck and
  nothing else can can be done than holding the power button in for a
  long enough time to turn it off. At the same time as the system get
  stuck, a red error light is lightening up on the server. This light is
  green until it reaches this "Starting Reboot" stage. The same happens
  if the server is shutdown, with the difference that the last message
  is "Starting Power-Off" instead of "Starting Reboot".

  The server is installed with a new clean 18.04 installation. This
  server was rebooting/shutting down without a problem with all releases
  between 16.04 and 17.10.

  This problem is serious as it prevents remote reboot.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 13 11:16 seq
   crw-rw 1 root audio 116, 33 Jun 13 11:16 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=none
  MachineType: HP ProLiant DL360 Gen9
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic 
root=ZFS=rpool/ROOT/ubuntu ro
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/21/2018
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd05/21/2018:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)

[Fabian]

I have tried two things:

(1) Fresh install, Ubuntu 18.04 (about ten days ago), ext4. No errors
during the installation. However, when installing stuff via apt
afterwards (or upgrading), I got many errors along the lines described
above (e.g., "compressed data is corrupt...  unexpected end of file or
stream"). This happened for, I guess, arbitrary packages. No errors for
initramfs update for me ...

(2) Fresh install, Ubuntu 18.04 (about four days ago), btrfs for /. No
errors at all.

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/control

[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)

[Fabian]

I have had the same issues with Ubuntu 18.04 and a Samsung MZ-V7E1T0
1000GB M.2 PCI Express 3.0 and the default installation (ext4): Plenty
of errors, especially when upgrading/installing packages via apt.

I have reinstalled the whole system. Instead of the standard journaling
file system (ext4), I have btrfs for the root mount point (/). System
works perfectly now, no errors for a couple of days with plenty of
software being installed.

Not sure, might be a ext4/kernel bug (?).

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0: 

[Kernel-packages] [Bug 1738972] Re: [A] KVM Windows BSOD on 4.13.x

[Fabian Grünbichler]

** Tags removed: verification-needed-artful
** Tags added: verification-done-artful

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

Title:
  [A] KVM Windows BSOD on 4.13.x

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Fix Committed

Bug description:
  == SRU Justification ==

  Impact: Windows 2016 and 10 VMs running in Qemu VMs using KVM trigger
  BSODs under certain memory conditions

  Fix: Single follow-up upstream cherry pick which fixes the problem.

  Regression Potential: Merged in 4.15 and 4.14.6, tested by multiple
  affected users.

  ---

  see https://marc.info/?l=linux-kernel&m=151203441531472&w=2 for the
  long writeup

  58582f04bc87b9d8d848d9163ce3355dd6f00602 is the cherry-pick in 4.14-6 (only 
context changes outside of the actual diff)
  b1394e745b9453dcb5b0671c205b770e87dedb87 is the fix as applied in 4.15-rc3

  I'll send the SRU patch as well.

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

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

[Kernel-packages] [Bug 1738975] Re: [A] skb leak in vhost_net / tun / tap

[Fabian Grünbichler]

** Tags removed: verification-needed-artful
** Tags added: verification-done-artful

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

Title:
  [A] skb leak in vhost_net / tun / tap

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Fix Committed

Bug description:
  == SRU Justification ==

  Impact: Up to 30% performance regression for traffic from hypervisor
  host to VM, caused by a memory leak

  Fix: Cherry-picks from upstream stable tree to fix the memory leak

  Regression Potential: Merged in 4.15 and 4.14.7, tested and verified
  by multiple people.

  --

  See 
https://lkml.kernel.org/r/<4c7e2924-b10f-0e97-c388-c8809ecfd...@linux.vnet.ibm.com>
 for the original report and extensive discussion
  See 
https://lkml.kernel.org/r/<1512123038-15773-1-git-send-email-w...@redhat.com> 
for the patch series in question

  I'll send an SRU patch set with cherry-picks from 4.14.7 .

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

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

[Kernel-packages] [Bug 1741081] Re: zfs-import-cache.service fails on startup

[Fabian Grünbichler]

IMHO this is completely backwards, see
https://github.com/zfsonlinux/zfs/pull/7259 for an upstream discussion
similar to this.

systemd service units are not the proper place to load modules - there
is {/lib,/etc}/modules-load.d/ which gets parsed by systemd-load-
modules.service early in the boot process, and ZoL even ships a
(disabled by default) snippet for /lib that supports. just flip that one
to enabled (admin can override via /etc) and you don't need to introduce
bogus services.

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

Title:
  zfs-import-cache.service fails on startup

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

Bug description:
  == SRU Request, Artful ==

  Enable ZFS module to be loaded without the broken ubuntu-load-zfs-
  unconditionally.patch.

  == Fix ==

  Add a new zfs-load-module.service script that modprobes the ZFS module
  and remove any hard coded module loading from zfs-import-cache.service
  & zfs-import-scan.service and make these latter scripts require the
  new zfs-load-module.service script.  Also remove the now defunct
  ubuntu-load-zfs-unconditionally.patch as this will no longer be
  required.

  == Testcase ==

  On a clean VM, install with the fixed package, zfs should load
  automatically.

  == Regression potential ==

  ZFS module may not load if the changes are broken. However, testing
  proves this not to be the case.

  

  I just noticed on my test VM of artful that zfs-import-cache.service
  does not have a ConditionPathExists=/etc/zfs/zpool.cache. Because of
  that, it fails on startup, since the cache file does not exist.

  This line is being deleted by 
debian/patches/ubuntu-load-zfs-unconditionally.patch. This patch seems to exist 
per:
  https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1672749

  This patch still exists in bionic, so I assume it will be similarly
  broken.

  If the goal of the patch is to load the module (and only that), I
  think it should create a third unit instead:

  zfs-load-module.service
   ^^ runs modprobe zfs

  zfs-import-cache.service & zfs-import-scan.service
    ^^ per upstream minus modprobe plus Requires=zfs-load-module.service

  I have tested this manually and it works. I can submit a package patch
  if this is the desired solution.

  Interestingly, before this change, zfs-import-scan.service wasn't
  starting. If started manually, it worked. I had to give it a
  `systemctl enable zfs-import-scan.service` to create the Wants
  symlinks. Looking at the zfsutils-linux.postinst, I see the correct
  boilerplate from dh_systemd, so I'm not sure why this wasn't already
  done. Can anyone confirm or deny whether zfs-import-scan.service is
  enabled out-of-the-box on their system?

  Is the zfs-import-scan.service not starting actually the cause of the
  original bug? The design is that *either* zfs-import-cache.service or
  zfs-import-scan.service starts. They both call modprobe zfs.

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

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

[Kernel-packages] [Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task

[Fabian Grünbichler]

the following upstream patch seems like a likely fix:

https://patchwork.kernel.org/patch/10154587/

otherwise, reverting the buggy commit seems to solve the issue as well
as a temporary measure.

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

Title:
  Unable to handle kernel NULL pointer dereference at
  isci_task_abort_task

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  So I just upgrade from zesty zapus to artful aardvark. At boot, right
  after I enter my drive encryption password, it kernel panics with the
  above message.

  It doesn't even get far enough along in the boot process for syslog to
  log this panic, so the only info I have is a photo of the panic.

  In short, I can't boot using the latest artful aardvark kernel, and I
  have to boot with the latest zesty zapus kernel.

  :~$ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  linux-image-4.13.0-16-generic

  I expect this isn't normal and I should be able to boot with the new
  kernel, which I can't.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lost   2071 F pulseaudio
   /dev/snd/controlC2:  lost   2071 F pulseaudio
   /dev/snd/controlC0:  lost   2071 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct 23 12:52:20 2017
  HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6
  InstallationDate: Installed on 2016-11-01 (355 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 11361Q0
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.169
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago)
  dmi.bios.date: 09/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A3KT57AUS
  dmi.board.name: LENOVO
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: 573921
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE:
  dmi.product.name: 11361Q0
  dmi.product.version: ThinkStation C30
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1738982] Re: [A] KVM module in 4.13 no longer supports old Intel CPUs

[Fabian Grünbichler]

patch sent

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

Title:
  [A] KVM module in 4.13 no longer supports old Intel CPUs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  == SRU Justification ==

  Impact: systems with CPUs lacking virtual NMI support are no longer
  able to load the kvm_intel module, and thus not able to use KVM
  functionality

  Fix: cherry-pick re-introducing support for software NMI support

  Regression Potential: applied upstream in 4.15 and 4.14.3, tested and
  verified by multiple people

  --

  the original dropping of support was (functionally) reverted after
  upstream got notified of how many CPUs were actually affected

  see 
https://lkml.kernel.org/r/<1509971473-74491-1-git-send-email-pbonz...@redhat.com>
 for upstream patch re-introducing support
  see 
https://lkml.kernel.org/r/<1490618297-10581-2-git-send-email-pbonz...@redhat.com>
 for the original upstream patch dropping support and following discusison

  I'll send an SRU patch.

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

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

[Kernel-packages] [Bug 1738982] [NEW] [A] KVM module in 4.13 no longer supports old Intel CPUs

[Fabian Grünbichler]

Public bug reported:

== SRU Justification ==

Impact: systems with CPUs lacking virtual NMI support are no longer able
to load the kvm_intel module, and thus not able to use KVM functionality

Fix: cherry-pick re-introducing support for software NMI support

Regression Potential: applied upstream in 4.15 and 4.14.3, tested and
verified by multiple people

--

the original dropping of support was (functionally) reverted after
upstream got notified of how many CPUs were actually affected

see 
https://lkml.kernel.org/r/<1509971473-74491-1-git-send-email-pbonz...@redhat.com>
 for upstream patch re-introducing support
see 
https://lkml.kernel.org/r/<1490618297-10581-2-git-send-email-pbonz...@redhat.com>
 for the original upstream patch dropping support and following discusison

I'll send an SRU patch.

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

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

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

Title:
  [A] KVM module in 4.13 no longer supports old Intel CPUs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  == SRU Justification ==

  Impact: systems with CPUs lacking virtual NMI support are no longer
  able to load the kvm_intel module, and thus not able to use KVM
  functionality

  Fix: cherry-pick re-introducing support for software NMI support

  Regression Potential: applied upstream in 4.15 and 4.14.3, tested and
  verified by multiple people

  --

  the original dropping of support was (functionally) reverted after
  upstream got notified of how many CPUs were actually affected

  see 
https://lkml.kernel.org/r/<1509971473-74491-1-git-send-email-pbonz...@redhat.com>
 for upstream patch re-introducing support
  see 
https://lkml.kernel.org/r/<1490618297-10581-2-git-send-email-pbonz...@redhat.com>
 for the original upstream patch dropping support and following discusison

  I'll send an SRU patch.

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

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

[Kernel-packages] [Bug 1738972] Re: [A] KVM Windows BSOD on 4.13.x

[Fabian Grünbichler]

patch sent

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

Title:
  [A] KVM Windows BSOD on 4.13.x

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  == SRU Justification ==

  Impact: Windows 2016 and 10 VMs running in Qemu VMs using KVM trigger
  BSODs under certain memory conditions

  Fix: Single follow-up upstream cherry pick which fixes the problem.

  Regression Potential: Merged in 4.15 and 4.14.6, tested by multiple
  affected users.

  ---

  see https://marc.info/?l=linux-kernel&m=151203441531472&w=2 for the
  long writeup

  58582f04bc87b9d8d848d9163ce3355dd6f00602 is the cherry-pick in 4.14-6 (only 
context changes outside of the actual diff)
  b1394e745b9453dcb5b0671c205b770e87dedb87 is the fix as applied in 4.15-rc3

  I'll send the SRU patch as well.

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

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

[Kernel-packages] [Bug 1738975] Re: [A] skb leak in vhost_net / tun / tap

[Fabian Grünbichler]

patch set sent

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

Title:
  [A] skb leak in vhost_net / tun / tap

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  == SRU Justification ==

  Impact: Up to 30% performance regression for traffic from hypervisor
  host to VM, caused by a memory leak

  Fix: Cherry-picks from upstream stable tree to fix the memory leak

  Regression Potential: Merged in 4.15 and 4.14.7, tested and verified
  by multiple people.

  --

  See 
https://lkml.kernel.org/r/<4c7e2924-b10f-0e97-c388-c8809ecfd...@linux.vnet.ibm.com>
 for the original report and extensive discussion
  See 
https://lkml.kernel.org/r/<1512123038-15773-1-git-send-email-w...@redhat.com> 
for the patch series in question

  I'll send an SRU patch set with cherry-picks from 4.14.7 .

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

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

[Kernel-packages] [Bug 1738972] Re: [A] KVM Windows BSOD on 4.13.x

[Fabian Grünbichler]

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

Title:
  [A] KVM Windows BSOD on 4.13.x

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  == SRU Justification ==

  Impact: Windows 2016 and 10 VMs running in Qemu VMs using KVM trigger
  BSODs under certain memory conditions

  Fix: Single follow-up upstream cherry pick which fixes the problem.

  Regression Potential: Merged in 4.15 and 4.14.6, tested by multiple
  affected users.

  ---

  see https://marc.info/?l=linux-kernel&m=151203441531472&w=2 for the
  long writeup

  58582f04bc87b9d8d848d9163ce3355dd6f00602 is the cherry-pick in 4.14-6 (only 
context changes outside of the actual diff)
  b1394e745b9453dcb5b0671c205b770e87dedb87 is the fix as applied in 4.15-rc3

  I'll send the SRU patch as well.

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

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

[Kernel-packages] [Bug 1738975] [NEW] [A] skb leak in vhost_net / tun / tap

[Fabian Grünbichler]

Public bug reported:

== SRU Justification ==

Impact: Up to 30% performance regression for traffic from hypervisor
host to VM, caused by a memory leak

Fix: Cherry-picks from upstream stable tree to fix the memory leak

Regression Potential: Merged in 4.15 and 4.14.7, tested and verified by
multiple people.

--

See 
https://lkml.kernel.org/r/<4c7e2924-b10f-0e97-c388-c8809ecfd...@linux.vnet.ibm.com>
 for the original report and extensive discussion
See 
https://lkml.kernel.org/r/<1512123038-15773-1-git-send-email-w...@redhat.com> 
for the patch series in question

I'll send an SRU patch set with cherry-picks from 4.14.7 .

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

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

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

Title:
  [A] skb leak in vhost_net / tun / tap

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  == SRU Justification ==

  Impact: Up to 30% performance regression for traffic from hypervisor
  host to VM, caused by a memory leak

  Fix: Cherry-picks from upstream stable tree to fix the memory leak

  Regression Potential: Merged in 4.15 and 4.14.7, tested and verified
  by multiple people.

  --

  See 
https://lkml.kernel.org/r/<4c7e2924-b10f-0e97-c388-c8809ecfd...@linux.vnet.ibm.com>
 for the original report and extensive discussion
  See 
https://lkml.kernel.org/r/<1512123038-15773-1-git-send-email-w...@redhat.com> 
for the patch series in question

  I'll send an SRU patch set with cherry-picks from 4.14.7 .

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

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

[Kernel-packages] [Bug 1738972] [NEW] [A] KVM Windows BSOD on 4.13.x

[Fabian Grünbichler]

Public bug reported:

== SRU Justification ==

Impact: Windows 2016 and 10 VMs running in Qemu VMs using KVM trigger
BSODs under certain memory conditions

Fix: Single follow-up upstream cherry pick which fixes the problem.

Regression Potential: Merged in 4.15 and 4.14.6, tested by multiple
affected users.

---

see https://marc.info/?l=linux-kernel&m=151203441531472&w=2 for the long
writeup

58582f04bc87b9d8d848d9163ce3355dd6f00602 is the cherry-pick in 4.14-6 (only 
context changes outside of the actual diff)
b1394e745b9453dcb5b0671c205b770e87dedb87 is the fix as applied in 4.15-rc3

I'll send the SRU patch as well.

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

** Summary changed:

- [Z] KVM Windows BSOD on 4.13.x
+ [A] KVM Windows BSOD on 4.13.x

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

Title:
  [A] KVM Windows BSOD on 4.13.x

Status in linux package in Ubuntu:
  New

Bug description:
  == SRU Justification ==

  Impact: Windows 2016 and 10 VMs running in Qemu VMs using KVM trigger
  BSODs under certain memory conditions

  Fix: Single follow-up upstream cherry pick which fixes the problem.

  Regression Potential: Merged in 4.15 and 4.14.6, tested by multiple
  affected users.

  ---

  see https://marc.info/?l=linux-kernel&m=151203441531472&w=2 for the
  long writeup

  58582f04bc87b9d8d848d9163ce3355dd6f00602 is the cherry-pick in 4.14-6 (only 
context changes outside of the actual diff)
  b1394e745b9453dcb5b0671c205b770e87dedb87 is the fix as applied in 4.15-rc3

  I'll send the SRU patch as well.

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

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

[Kernel-packages] [Bug 1729637] Re: Samba mount/umount in docker container triggers kernel Oops

[Fabian Holler]

I could not reproduce the bug with 4.4.0-102-generic or
4.10.0-41-generic

** Tags removed: verification-needed-xenial verification-needed-zesty
** Tags added: verification-done-xenial verification-done-zesty

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

Title:
  Samba mount/umount in docker container triggers kernel Oops

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

Bug description:
  == SRU Justification ==
  This bug causes Samba mount and umounts in docker container to trigger 
  a kernel Oops.  When running 2 docker containers, one as samba server and 
  another one as samba client that mounts and umounts a smb share a kernel 
  OOps can be triggered.  

  This bug happens in Xenial and Zesty, and is fixed by the following two 
commits:
  76da0704507b ("ipv6: only call ip6_route_dev_notify() once for 
NETDEV_UNREGISTER")
  12d94a804946 ("ipv6: fix NULL dereference in ip6_route_dev_notify()")

  Both commits are clean cherry picks.  76da0704507b is in mainline as of v4.12.
  Commit 12d94a804946 is in mainline as of v4.13-rc6. 
  
  == Fixes ==
  commit 76da0704507bbc51875013f6557877ab308cfd0a
  Author: WANG Cong 
  Date:   Tue Jun 20 11:42:27 2017 -0700

  ipv6: only call ip6_route_dev_notify() once for NETDEV_UNREGISTER

  commit 12d94a804946af291e24b80fc53ec86264765781
  Author: Eric Dumazet 
  Date:   Tue Aug 15 04:09:51 2017 -0700

  ipv6: fix NULL dereference in ip6_route_dev_notify()

  == Regression Potential ==
  Both commits are specific to ipv6 and fix a regression introduced into Xenial 
and Zesty.

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


  The kernel message:
    unregister_netdevice: waiting for lo to become free. Usage count = 1
  shows up, some minutes later the oops and/or warnings happens.

  The scripts to trigger the kernel Oops can be found at: 
https://github.com/fho/docker-samba-loop
  I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation 
with:

  - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
  - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
  - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1

  In a different scenario were Ubuntu 16.04 servers were running
  multiple docker containers with Nginx or small network applications in
  parallel, I was also able to reproduce the kernel Oopses also on:

  - linux-image-4.10.0-1004-gcp
  - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830

  I haven't tried again to reproduce it with those kernels on a clean Ubuntu
  installation and unfortunately didn't kept the kernel logs.

  The "unregister_netdevice: waiting for lo to become free. Usage count
  = 1" messages are related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is
  handled as separate issue.

  According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
  https://patchwork.ozlabs.org/patch/801533/
  https://patchwork.ozlabs.org/patch/778449/
  ---
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  3 09:51 seq
   crw-rw 1 root audio 116, 33 Nov  3 09:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Google Google Compute Engine
  Package: linux (not installed)
  PciMultimedia:

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

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=bf9a017a-931d-4191-84bc-b8434dbba527 ro scsi_mod.use_blk_mq=Y 
console=ttyS0
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images xenial uec-images
  Uname: Linux 4.10.0-37-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: False
  dmi.bios.date: 01/01/2011
  dmi.bios.vendor: Google
  dmi.bios.version: Google
  dmi.board.asset.tag: A3DDBB61-646B-C60C-3999-1F1D7B7A334A
  dmi.board.name: Google Compute Engine
  dmi.board.ve

[Kernel-packages] [Bug 1733230] Re: 'zfs recv' hangs when receiving from a FreeBSD zfs

[Fabian Grünbichler]

but, upgrading ZFS to 0.7.x would fix it on the receiving side, so that
might be an option for you ;)

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

Title:
  'zfs recv' hangs when receiving from a FreeBSD zfs

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  When creating a pool snapshot on a freenas/freebsd like this:

  ```
  root@freenas:~ # uname -a
  FreeBSD freenas.local 11.0-STABLE FreeBSD 11.0-STABLE #0 
r321665+25fe8ba8d06(freenas/11.0-stable): Mon Sep 25 06:24:11 UTC 2017 
root@gauntlet:/freenas-11-releng/freenas/_BE/objs/freenas-11-releng/freenas/_BE/os/sys/FreeNAS.amd64
  amd64
  freenas# zpool create tank gptid/62a26be7-cd4a-11e7-927b-0800278dcda9
  freenas# dd if=/dev/zero of=/tank/ur.bin bs=64K count=1
  freenas# zfs snap tank@example
  ```

  And trying to `zfs send | zfs recv` it to an ubuntu zfs like this:
  ```
  space@ubuntu:~$ apt-cache policy zfsutils-linux
  zfsutils-linux:
Installed: 0.6.5.11-1ubuntu3
Candidate: 0.6.5.11-1ubuntu3
Version table:
   *** 0.6.5.11-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status
  space@ubuntu:~$ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  root@ubuntu:~$ ssh root@freenas zfs send tank@example > freenas11.zfssend
  root@ubuntu:~# cat ./freenas11.zfssend | zfs recv tank/something
  ```

  The `zfs recv` process burns 100% CPU and hangs forever. I have
  attached an example freenas11.zfssend file, though it's easily
  reproduced.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: zfsutils-linux 0.6.5.11-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Sun Nov 19 22:10:15 2017
  ExecutablePath: /sbin/zfs
  InstallationDate: Installed on 2017-11-17 (2 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   PATH=(custom, no user)
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1733230] Re: 'zfs recv' hangs when receiving from a FreeBSD zfs

[Fabian Grünbichler]

see https://github.com/zfsonlinux/zfs/pull/6616 for the fix in ZFS on
Linux 0.7.3 (on the sender side). not yet backported to Open-ZFS, and
thus not in FreeBSDs ZFS either.

this is not really a bug in ZFS on the receiver side, it was an
accidental break of backwards compatibility.

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

Title:
  'zfs recv' hangs when receiving from a FreeBSD zfs

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  When creating a pool snapshot on a freenas/freebsd like this:

  ```
  root@freenas:~ # uname -a
  FreeBSD freenas.local 11.0-STABLE FreeBSD 11.0-STABLE #0 
r321665+25fe8ba8d06(freenas/11.0-stable): Mon Sep 25 06:24:11 UTC 2017 
root@gauntlet:/freenas-11-releng/freenas/_BE/objs/freenas-11-releng/freenas/_BE/os/sys/FreeNAS.amd64
  amd64
  freenas# zpool create tank gptid/62a26be7-cd4a-11e7-927b-0800278dcda9
  freenas# dd if=/dev/zero of=/tank/ur.bin bs=64K count=1
  freenas# zfs snap tank@example
  ```

  And trying to `zfs send | zfs recv` it to an ubuntu zfs like this:
  ```
  space@ubuntu:~$ apt-cache policy zfsutils-linux
  zfsutils-linux:
Installed: 0.6.5.11-1ubuntu3
Candidate: 0.6.5.11-1ubuntu3
Version table:
   *** 0.6.5.11-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status
  space@ubuntu:~$ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  root@ubuntu:~$ ssh root@freenas zfs send tank@example > freenas11.zfssend
  root@ubuntu:~# cat ./freenas11.zfssend | zfs recv tank/something
  ```

  The `zfs recv` process burns 100% CPU and hangs forever. I have
  attached an example freenas11.zfssend file, though it's easily
  reproduced.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: zfsutils-linux 0.6.5.11-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Sun Nov 19 22:10:15 2017
  ExecutablePath: /sbin/zfs
  InstallationDate: Installed on 2017-11-17 (2 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   PATH=(custom, no user)
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1729637] Re: Samba mount/umount in docker container triggers kernel Oops

[Fabian Holler]

No, the hung task warning is bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407

Without the patches the kernel probably crashed during my tests before
the hung task could happen.

On artful the hung task warning does not happen.

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

Title:
  Samba mount/umount in docker container triggers kernel Oops

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

Bug description:
  When running 2 docker containers, one as samba server and another one
  as samba client that mounts and umounts a smb share a kernel OOps can
  be triggered on multiple kernels.

  The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
  shows up, some minutes later the oops and/or warnings happens.

  
  The scripts to trigger the kernel Oops can be found at: 
https://github.com/fho/docker-samba-loop
  I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation 
with:

  - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
  - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
  - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1

  In a different scenario were Ubuntu 16.04 servers were running
  multiple docker containers with Nginx or small network applications in
  parallel, I was also able to reproduce the kernel Oopses also on:

  - linux-image-4.10.0-1004-gcp
  - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830

  I haven't tried again to reproduce it with those kernels on a clean Ubuntu
  installation and unfortunately didn't kept the kernel logs.

  The "unregister_netdevice: waiting for lo to become free. Usage count
  = 1" messages are related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is
  handled as separate issue.

  
  According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
  https://patchwork.ozlabs.org/patch/801533/
  https://patchwork.ozlabs.org/patch/778449/
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  3 09:51 seq
   crw-rw 1 root audio 116, 33 Nov  3 09:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Google Google Compute Engine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=bf9a017a-931d-4191-84bc-b8434dbba527 ro scsi_mod.use_blk_mq=Y 
console=ttyS0
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images xenial uec-images
  Uname: Linux 4.10.0-37-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 01/01/2011
  dmi.bios.vendor: Google
  dmi.bios.version: Google
  dmi.board.asset.tag: A3DDBB61-646B-C60C-3999-1F1D7B7A334A
  dmi.board.name: Google Compute Engine
  dmi.board.vendor: Google
  dmi.chassis.type: 1
  dmi.chassis.vendor: Google
  dmi.modalias: 
dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr:
  dmi.product.name: Google Compute Engine
  dmi.sys.vendor: Google

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

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

[Kernel-packages] [Bug 1729637] Re: Samba mount/umount in docker container triggers kernel Oops

[Fabian Holler]

Thanks for the fast reply.

I tried both kernels and was not able to trigger an Oops.

On the 4.4.0-98.121~lp1729637-generic kernel a hung task warning
happened:

[  +0.750497] unregister_netdevice: waiting for lo to become free. Usage count 
= 1
[  +0.992665] aufs au_opts_verify:1597:dockerd[1620]: dirperm1 breaks the 
protection by the permission bits on the lower branch
[  +0.016910] aufs au_opts_verify:1597:dockerd[1620]: dirperm1 breaks the 
protection by the permission bits on the lower branch
[  +0.015247] aufs au_opts_verify:1597:dockerd[1592]: dirperm1 breaks the 
protection by the permission bits on the lower branch
[  +0.006387] device veth7d3bee3 entered promiscuous mode
[  +0.000923] IPv6: ADDRCONF(NETDEV_UP): veth7d3bee3: link is not ready
[  +9.051406] unregister_netdevice: waiting for lo to become free. Usage count 
= 1
[ +10.067531] unregister_netdevice: waiting for lo to become free. Usage count 
= 1
[ +10.083551] unregister_netdevice: waiting for lo to become free. Usage count 
= 1
[Nov 3 18:53] unregister_netdevice: waiting for lo to become free. Usage count 
= 1
[  +8.055656] INFO: task exe:2868 blocked for more than 120 seconds.
[  +0.006363]   Not tainted 4.4.0-98-generic #121~lp1729637
[  +0.005970] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  +0.008347] exe D 88012a0e3cb8 0  2868  1 0x
[  +0.06]  88012a0e3cb8 821db9a0 81e11500 
8800ba25f000
[  +0.02]  88012a0e4000 81ef7a64 8800ba25f000 

[  +0.02]  81ef7a68 88012a0e3cd0 818405d5 
81ef7a60
[  +0.02] Call Trace:
[  +0.11]  [] schedule+0x35/0x80
[  +0.04]  [] schedule_preempt_disabled+0xe/0x10
[  +0.03]  [] __mutex_lock_slowpath+0xb9/0x130
[  +0.02]  [] mutex_lock+0x1f/0x30
[  +0.07]  [] copy_net_ns+0x6e/0x120
[  +0.10]  [] create_new_namespaces+0x11b/0x1d0
[  +0.01]  [] copy_namespaces+0x6d/0xa0
[  +0.05]  [] copy_process+0x8e2/0x1b30
[  +0.03]  [] _do_fork+0x80/0x360
[  +0.02]  [] SyS_clone+0x19/0x20
[  +0.04]  [] entry_SYSCALL_64_fastpath+0x16/0x71
[  +1.999139] unregister_netdevice: waiting for lo to become free. Usage count 
= 1

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

Title:
  Samba mount/umount in docker container triggers kernel Oops

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

Bug description:
  When running 2 docker containers, one as samba server and another one
  as samba client that mounts and umounts a smb share a kernel OOps can
  be triggered on multiple kernels.

  The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
  shows up, some minutes later the oops and/or warnings happens.

  
  The scripts to trigger the kernel Oops can be found at: 
https://github.com/fho/docker-samba-loop
  I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation 
with:

  - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
  - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
  - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1

  In a different scenario were Ubuntu 16.04 servers were running
  multiple docker containers with Nginx or small network applications in
  parallel, I was also able to reproduce the kernel Oopses also on:

  - linux-image-4.10.0-1004-gcp
  - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830

  I haven't tried again to reproduce it with those kernels on a clean Ubuntu
  installation and unfortunately didn't kept the kernel logs.

  The "unregister_netdevice: waiting for lo to become free. Usage count
  = 1" messages are related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is
  handled as separate issue.

  
  According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
  https://patchwork.ozlabs.org/patch/801533/
  https://patchwork.ozlabs.org/patch/778449/
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  3 09:51 seq
   crw-rw 1 root audio 116, 33 Nov  3 09:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Google Google Compute Engine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcK

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

[Fabian Holler]

apport information

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

Title:
  Samba mount/umount in docker container triggers kernel Oops

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When running 2 docker containers, one as samba server and another one
  as samba client that mounts and umounts a smb share a kernel OOps can
  be triggered on multiple kernels.

  The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
  shows up, some minutes later the oops and/or warnings happens.

  
  The scripts to trigger the kernel Oops can be found at: 
https://github.com/fho/docker-samba-loop
  I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation 
with:

  - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
  - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
  - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1

  In a different scenario were Ubuntu 16.04 servers were running
  multiple docker containers with Nginx or small network applications in
  parallel, I was also able to reproduce the kernel Oopses also on:

  - linux-image-4.10.0-1004-gcp
  - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830

  I haven't tried again to reproduce it with those kernels on a clean Ubuntu
  installation and unfortunately didn't kept the kernel logs.

  The "unregister_netdevice: waiting for lo to become free. Usage count
  = 1" messages are related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is
  handled as separate issue.

  
  According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
  https://patchwork.ozlabs.org/patch/801533/
  https://patchwork.ozlabs.org/patch/778449/
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  3 09:51 seq
   crw-rw 1 root audio 116, 33 Nov  3 09:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Google Google Compute Engine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=bf9a017a-931d-4191-84bc-b8434dbba527 ro scsi_mod.use_blk_mq=Y 
console=ttyS0
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images xenial uec-images
  Uname: Linux 4.10.0-37-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 01/01/2011
  dmi.bios.vendor: Google
  dmi.bios.version: Google
  dmi.board.asset.tag: A3DDBB61-646B-C60C-3999-1F1D7B7A334A
  dmi.board.name: Google Compute Engine
  dmi.board.vendor: Google
  dmi.chassis.type: 1
  dmi.chassis.vendor: Google
  dmi.modalias: 
dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr:
  dmi.product.name: Google Compute Engine
  dmi.sys.vendor: Google

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

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

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

[Fabian Holler]

apport information

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

Title:
  Samba mount/umount in docker container triggers kernel Oops

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When running 2 docker containers, one as samba server and another one
  as samba client that mounts and umounts a smb share a kernel OOps can
  be triggered on multiple kernels.

  The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
  shows up, some minutes later the oops and/or warnings happens.

  
  The scripts to trigger the kernel Oops can be found at: 
https://github.com/fho/docker-samba-loop
  I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation 
with:

  - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
  - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
  - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1

  In a different scenario were Ubuntu 16.04 servers were running
  multiple docker containers with Nginx or small network applications in
  parallel, I was also able to reproduce the kernel Oopses also on:

  - linux-image-4.10.0-1004-gcp
  - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830

  I haven't tried again to reproduce it with those kernels on a clean Ubuntu
  installation and unfortunately didn't kept the kernel logs.

  The "unregister_netdevice: waiting for lo to become free. Usage count
  = 1" messages are related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is
  handled as separate issue.

  
  According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
  https://patchwork.ozlabs.org/patch/801533/
  https://patchwork.ozlabs.org/patch/778449/
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  3 09:51 seq
   crw-rw 1 root audio 116, 33 Nov  3 09:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Google Google Compute Engine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=bf9a017a-931d-4191-84bc-b8434dbba527 ro scsi_mod.use_blk_mq=Y 
console=ttyS0
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images xenial uec-images
  Uname: Linux 4.10.0-37-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 01/01/2011
  dmi.bios.vendor: Google
  dmi.bios.version: Google
  dmi.board.asset.tag: A3DDBB61-646B-C60C-3999-1F1D7B7A334A
  dmi.board.name: Google Compute Engine
  dmi.board.vendor: Google
  dmi.chassis.type: 1
  dmi.chassis.vendor: Google
  dmi.modalias: 
dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr:
  dmi.product.name: Google Compute Engine
  dmi.sys.vendor: Google

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

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

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

[Fabian Holler]

apport information

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

Title:
  Samba mount/umount in docker container triggers kernel Oops

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When running 2 docker containers, one as samba server and another one
  as samba client that mounts and umounts a smb share a kernel OOps can
  be triggered on multiple kernels.

  The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
  shows up, some minutes later the oops and/or warnings happens.

  
  The scripts to trigger the kernel Oops can be found at: 
https://github.com/fho/docker-samba-loop
  I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation 
with:

  - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
  - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
  - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1

  In a different scenario were Ubuntu 16.04 servers were running
  multiple docker containers with Nginx or small network applications in
  parallel, I was also able to reproduce the kernel Oopses also on:

  - linux-image-4.10.0-1004-gcp
  - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830

  I haven't tried again to reproduce it with those kernels on a clean Ubuntu
  installation and unfortunately didn't kept the kernel logs.

  The "unregister_netdevice: waiting for lo to become free. Usage count
  = 1" messages are related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is
  handled as separate issue.

  
  According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
  https://patchwork.ozlabs.org/patch/801533/
  https://patchwork.ozlabs.org/patch/778449/
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  3 09:51 seq
   crw-rw 1 root audio 116, 33 Nov  3 09:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Google Google Compute Engine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=bf9a017a-931d-4191-84bc-b8434dbba527 ro scsi_mod.use_blk_mq=Y 
console=ttyS0
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images xenial uec-images
  Uname: Linux 4.10.0-37-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 01/01/2011
  dmi.bios.vendor: Google
  dmi.bios.version: Google
  dmi.board.asset.tag: A3DDBB61-646B-C60C-3999-1F1D7B7A334A
  dmi.board.name: Google Compute Engine
  dmi.board.vendor: Google
  dmi.chassis.type: 1
  dmi.chassis.vendor: Google
  dmi.modalias: 
dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr:
  dmi.product.name: Google Compute Engine
  dmi.sys.vendor: Google

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

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

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

[Fabian Holler]

apport information

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

Title:
  Samba mount/umount in docker container triggers kernel Oops

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When running 2 docker containers, one as samba server and another one
  as samba client that mounts and umounts a smb share a kernel OOps can
  be triggered on multiple kernels.

  The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
  shows up, some minutes later the oops and/or warnings happens.

  
  The scripts to trigger the kernel Oops can be found at: 
https://github.com/fho/docker-samba-loop
  I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation 
with:

  - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
  - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
  - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1

  In a different scenario were Ubuntu 16.04 servers were running
  multiple docker containers with Nginx or small network applications in
  parallel, I was also able to reproduce the kernel Oopses also on:

  - linux-image-4.10.0-1004-gcp
  - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830

  I haven't tried again to reproduce it with those kernels on a clean Ubuntu
  installation and unfortunately didn't kept the kernel logs.

  The "unregister_netdevice: waiting for lo to become free. Usage count
  = 1" messages are related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is
  handled as separate issue.

  
  According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
  https://patchwork.ozlabs.org/patch/801533/
  https://patchwork.ozlabs.org/patch/778449/
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  3 09:51 seq
   crw-rw 1 root audio 116, 33 Nov  3 09:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Google Google Compute Engine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=bf9a017a-931d-4191-84bc-b8434dbba527 ro scsi_mod.use_blk_mq=Y 
console=ttyS0
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images xenial uec-images
  Uname: Linux 4.10.0-37-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 01/01/2011
  dmi.bios.vendor: Google
  dmi.bios.version: Google
  dmi.board.asset.tag: A3DDBB61-646B-C60C-3999-1F1D7B7A334A
  dmi.board.name: Google Compute Engine
  dmi.board.vendor: Google
  dmi.chassis.type: 1
  dmi.chassis.vendor: Google
  dmi.modalias: 
dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr:
  dmi.product.name: Google Compute Engine
  dmi.sys.vendor: Google

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

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

[Kernel-packages] [Bug 1729637] Re: Samba mount/umount in docker container triggers kernel Oops

[Fabian Holler]

The collected apport informations are from a fresh start of the machine
because the bugs causes the machine to crash.

Attached are the logs of a kernel crash that happened by the described
method.

** Attachment added: "Logs from kernel Oops on 
linux-image-4.10.0-37-generic=4.10.0-37.41~16.04.1"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729637/+attachment/5002904/+files/kern.log

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

Title:
  Samba mount/umount in docker container triggers kernel Oops

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When running 2 docker containers, one as samba server and another one
  as samba client that mounts and umounts a smb share a kernel OOps can
  be triggered on multiple kernels.

  The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
  shows up, some minutes later the oops and/or warnings happens.

  
  The scripts to trigger the kernel Oops can be found at: 
https://github.com/fho/docker-samba-loop
  I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation 
with:

  - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
  - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
  - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1

  In a different scenario were Ubuntu 16.04 servers were running
  multiple docker containers with Nginx or small network applications in
  parallel, I was also able to reproduce the kernel Oopses also on:

  - linux-image-4.10.0-1004-gcp
  - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830

  I haven't tried again to reproduce it with those kernels on a clean Ubuntu
  installation and unfortunately didn't kept the kernel logs.

  The "unregister_netdevice: waiting for lo to become free. Usage count
  = 1" messages are related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is
  handled as separate issue.

  
  According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
  https://patchwork.ozlabs.org/patch/801533/
  https://patchwork.ozlabs.org/patch/778449/
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  3 09:51 seq
   crw-rw 1 root audio 116, 33 Nov  3 09:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Google Google Compute Engine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=bf9a017a-931d-4191-84bc-b8434dbba527 ro scsi_mod.use_blk_mq=Y 
console=ttyS0
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images xenial uec-images
  Uname: Linux 4.10.0-37-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 01/01/2011
  dmi.bios.vendor: Google
  dmi.bios.version: Google
  dmi.board.asset.tag: A3DDBB61-646B-C60C-3999-1F1D7B7A334A
  dmi.board.name: Google Compute Engine
  dmi.board.vendor: Google
  dmi.chassis.type: 1
  dmi.chassis.vendor: Google
  dmi.modalias: 
dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr:
  dmi.product.name: Google Compute Engine
  dmi.sys.vendor: Google

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

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

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

[Fabian Holler]

apport information

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

Title:
  Samba mount/umount in docker container triggers kernel Oops

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When running 2 docker containers, one as samba server and another one
  as samba client that mounts and umounts a smb share a kernel OOps can
  be triggered on multiple kernels.

  The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
  shows up, some minutes later the oops and/or warnings happens.

  
  The scripts to trigger the kernel Oops can be found at: 
https://github.com/fho/docker-samba-loop
  I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation 
with:

  - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
  - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
  - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1

  In a different scenario were Ubuntu 16.04 servers were running
  multiple docker containers with Nginx or small network applications in
  parallel, I was also able to reproduce the kernel Oopses also on:

  - linux-image-4.10.0-1004-gcp
  - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830

  I haven't tried again to reproduce it with those kernels on a clean Ubuntu
  installation and unfortunately didn't kept the kernel logs.

  The "unregister_netdevice: waiting for lo to become free. Usage count
  = 1" messages are related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is
  handled as separate issue.

  
  According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
  https://patchwork.ozlabs.org/patch/801533/
  https://patchwork.ozlabs.org/patch/778449/
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  3 09:51 seq
   crw-rw 1 root audio 116, 33 Nov  3 09:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Google Google Compute Engine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=bf9a017a-931d-4191-84bc-b8434dbba527 ro scsi_mod.use_blk_mq=Y 
console=ttyS0
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images xenial uec-images
  Uname: Linux 4.10.0-37-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 01/01/2011
  dmi.bios.vendor: Google
  dmi.bios.version: Google
  dmi.board.asset.tag: A3DDBB61-646B-C60C-3999-1F1D7B7A334A
  dmi.board.name: Google Compute Engine
  dmi.board.vendor: Google
  dmi.chassis.type: 1
  dmi.chassis.vendor: Google
  dmi.modalias: 
dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr:
  dmi.product.name: Google Compute Engine
  dmi.sys.vendor: Google

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

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

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

[Fabian Holler]

apport information

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

Title:
  Samba mount/umount in docker container triggers kernel Oops

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When running 2 docker containers, one as samba server and another one
  as samba client that mounts and umounts a smb share a kernel OOps can
  be triggered on multiple kernels.

  The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
  shows up, some minutes later the oops and/or warnings happens.

  
  The scripts to trigger the kernel Oops can be found at: 
https://github.com/fho/docker-samba-loop
  I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation 
with:

  - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
  - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
  - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1

  In a different scenario were Ubuntu 16.04 servers were running
  multiple docker containers with Nginx or small network applications in
  parallel, I was also able to reproduce the kernel Oopses also on:

  - linux-image-4.10.0-1004-gcp
  - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830

  I haven't tried again to reproduce it with those kernels on a clean Ubuntu
  installation and unfortunately didn't kept the kernel logs.

  The "unregister_netdevice: waiting for lo to become free. Usage count
  = 1" messages are related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is
  handled as separate issue.

  
  According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
  https://patchwork.ozlabs.org/patch/801533/
  https://patchwork.ozlabs.org/patch/778449/
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  3 09:51 seq
   crw-rw 1 root audio 116, 33 Nov  3 09:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Google Google Compute Engine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=bf9a017a-931d-4191-84bc-b8434dbba527 ro scsi_mod.use_blk_mq=Y 
console=ttyS0
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images xenial uec-images
  Uname: Linux 4.10.0-37-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 01/01/2011
  dmi.bios.vendor: Google
  dmi.bios.version: Google
  dmi.board.asset.tag: A3DDBB61-646B-C60C-3999-1F1D7B7A334A
  dmi.board.name: Google Compute Engine
  dmi.board.vendor: Google
  dmi.chassis.type: 1
  dmi.chassis.vendor: Google
  dmi.modalias: 
dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr:
  dmi.product.name: Google Compute Engine
  dmi.sys.vendor: Google

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

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

[Kernel-packages] [Bug 1729637] Re: Samba mount/umount in docker container triggers kernel Oops

[Fabian Holler]

apport information

** Tags added: apport-collected uec-images xenial

** Description changed:

  When running 2 docker containers, one as samba server and another one as
  samba client that mounts and umounts a smb share a kernel OOps can be
  triggered on multiple kernels.
  
  The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
  shows up, some minutes later the oops and/or warnings happens.
  
  
  The scripts to trigger the kernel Oops can be found at: 
https://github.com/fho/docker-samba-loop
  I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation 
with:
  
  - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
  - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
  - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1
  
  In a different scenario were Ubuntu 16.04 servers were running multiple
  docker containers with Nginx or small network applications in parallel,
  I was also able to reproduce the kernel Oopses also on:
  
  - linux-image-4.10.0-1004-gcp
  - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830
  
  I haven't tried again to reproduce it with those kernels on a clean Ubuntu
  installation and unfortunately didn't kept the kernel logs.
  
  The "unregister_netdevice: waiting for lo to become free. Usage count =
  1" messages are related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is
  handled as separate issue.
  
  
  According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
  https://patchwork.ozlabs.org/patch/801533/
  https://patchwork.ozlabs.org/patch/778449/
+ --- 
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 Nov  3 09:51 seq
+  crw-rw 1 root audio 116, 33 Nov  3 09:51 timer
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.20.1-0ubuntu2.10
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ CRDA: N/A
+ DistroRelease: Ubuntu 16.04
+ IwConfig: Error: [Errno 2] No such file or directory
+ Lsusb: Error: command ['lsusb'] failed with exit code 1:
+ MachineType: Google Google Compute Engine
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  TERM=rxvt-unicode-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=bf9a017a-931d-4191-84bc-b8434dbba527 ro scsi_mod.use_blk_mq=Y 
console=ttyS0
+ ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
+ RelatedPackageVersions:
+  linux-restricted-modules-4.10.0-37-generic N/A
+  linux-backports-modules-4.10.0-37-generic  N/A
+  linux-firmware N/A
+ RfKill: Error: [Errno 2] No such file or directory
+ Tags:  xenial uec-images xenial uec-images
+ Uname: Linux 4.10.0-37-generic x86_64
+ UnreportableReason: The report belongs to a package that is not installed.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: False
+ dmi.bios.date: 01/01/2011
+ dmi.bios.vendor: Google
+ dmi.bios.version: Google
+ dmi.board.asset.tag: A3DDBB61-646B-C60C-3999-1F1D7B7A334A
+ dmi.board.name: Google Compute Engine
+ dmi.board.vendor: Google
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: Google
+ dmi.modalias: 
dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr:
+ dmi.product.name: Google Compute Engine
+ dmi.sys.vendor: Google

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

Title:
  Samba mount/umount in docker container triggers kernel Oops

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When running 2 docker containers, one as samba server and another one
  as samba client that mounts and umounts a smb share a kernel OOps can
  be triggered on multiple kernels.

  The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
  shows up, some minutes later the oops and/or warnings happens.

  
  The scripts to trigger the kernel Oops can be found at: 
https://github.com/fho/docker-samba-loop
  I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation 
with:

  - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
  - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
  - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1

  In a different scenario were Ubuntu 16.04 servers were running
  multiple docker containers with Nginx or small network applications in
  parallel, I was also able to reproduce the kernel Oopses also on:

  - linux-image-4.10.0-1004-gcp
  - linux

[Kernel-packages] [Bug 1729637] JournalErrors.txt

[Fabian Holler]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1729637/+attachment/5002897/+files/JournalErrors.txt

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

Title:
  Samba mount/umount in docker container triggers kernel Oops

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When running 2 docker containers, one as samba server and another one
  as samba client that mounts and umounts a smb share a kernel OOps can
  be triggered on multiple kernels.

  The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
  shows up, some minutes later the oops and/or warnings happens.

  
  The scripts to trigger the kernel Oops can be found at: 
https://github.com/fho/docker-samba-loop
  I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation 
with:

  - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
  - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
  - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1

  In a different scenario were Ubuntu 16.04 servers were running
  multiple docker containers with Nginx or small network applications in
  parallel, I was also able to reproduce the kernel Oopses also on:

  - linux-image-4.10.0-1004-gcp
  - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830

  I haven't tried again to reproduce it with those kernels on a clean Ubuntu
  installation and unfortunately didn't kept the kernel logs.

  The "unregister_netdevice: waiting for lo to become free. Usage count
  = 1" messages are related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is
  handled as separate issue.

  
  According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
  https://patchwork.ozlabs.org/patch/801533/
  https://patchwork.ozlabs.org/patch/778449/
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  3 09:51 seq
   crw-rw 1 root audio 116, 33 Nov  3 09:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Google Google Compute Engine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=bf9a017a-931d-4191-84bc-b8434dbba527 ro scsi_mod.use_blk_mq=Y 
console=ttyS0
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images xenial uec-images
  Uname: Linux 4.10.0-37-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 01/01/2011
  dmi.bios.vendor: Google
  dmi.bios.version: Google
  dmi.board.asset.tag: A3DDBB61-646B-C60C-3999-1F1D7B7A334A
  dmi.board.name: Google Compute Engine
  dmi.board.vendor: Google
  dmi.chassis.type: 1
  dmi.chassis.vendor: Google
  dmi.modalias: 
dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr:
  dmi.product.name: Google Compute Engine
  dmi.sys.vendor: Google

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

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

[Kernel-packages] [Bug 1729637] Re: Samba mount/umount in docker container triggers kernel Oops

[Fabian Holler]

** Attachment added: "Kernel log from Oops with 
linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729637/+attachment/5002525/+files/kernoops-4.4.0-93.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/1729637

Title:
  Samba mount/umount in docker container triggers kernel Oops

Status in linux package in Ubuntu:
  New

Bug description:
  When running 2 docker containers, one as samba server and another one
  as samba client that mounts and umounts a smb share a kernel OOps can
  be triggered on multiple kernels.

  The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
  shows up, some minutes later the oops and/or warnings happens.

  
  The scripts to trigger the kernel Oops can be found at: 
https://github.com/fho/docker-samba-loop
  I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation 
with:

  - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
  - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
  - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1

  In a different scenario were Ubuntu 16.04 servers were running
  multiple docker containers with Nginx or small network applications in
  parallel, I was also able to reproduce the kernel Oopses also on:

  - linux-image-4.10.0-1004-gcp
  - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830

  I haven't tried again to reproduce it with those kernels on a clean Ubuntu
  installation and unfortunately didn't kept the kernel logs.

  The "unregister_netdevice: waiting for lo to become free. Usage count
  = 1" messages are related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is
  handled as separate issue.

  
  According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
  https://patchwork.ozlabs.org/patch/801533/
  https://patchwork.ozlabs.org/patch/778449/

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

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

[Kernel-packages] [Bug 1729637] Re: Samba mount/umount in docker container triggers kernel Oops

[Fabian Holler]

** Attachment added: "Kernel log from Oops with 
linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729637/+attachment/5002527/+files/kernoops-4.11.0-14.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/1729637

Title:
  Samba mount/umount in docker container triggers kernel Oops

Status in linux package in Ubuntu:
  New

Bug description:
  When running 2 docker containers, one as samba server and another one
  as samba client that mounts and umounts a smb share a kernel OOps can
  be triggered on multiple kernels.

  The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
  shows up, some minutes later the oops and/or warnings happens.

  
  The scripts to trigger the kernel Oops can be found at: 
https://github.com/fho/docker-samba-loop
  I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation 
with:

  - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
  - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
  - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1

  In a different scenario were Ubuntu 16.04 servers were running
  multiple docker containers with Nginx or small network applications in
  parallel, I was also able to reproduce the kernel Oopses also on:

  - linux-image-4.10.0-1004-gcp
  - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830

  I haven't tried again to reproduce it with those kernels on a clean Ubuntu
  installation and unfortunately didn't kept the kernel logs.

  The "unregister_netdevice: waiting for lo to become free. Usage count
  = 1" messages are related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is
  handled as separate issue.

  
  According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
  https://patchwork.ozlabs.org/patch/801533/
  https://patchwork.ozlabs.org/patch/778449/

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

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

[Kernel-packages] [Bug 1729637] Re: Samba mount/umount in docker container triggers kernel Oops

[Fabian Holler]

** Attachment added: "Kernel log from Oops with 
linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729637/+attachment/5002526/+files/kernoops-4.10.0-32.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/1729637

Title:
  Samba mount/umount in docker container triggers kernel Oops

Status in linux package in Ubuntu:
  New

Bug description:
  When running 2 docker containers, one as samba server and another one
  as samba client that mounts and umounts a smb share a kernel OOps can
  be triggered on multiple kernels.

  The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
  shows up, some minutes later the oops and/or warnings happens.

  
  The scripts to trigger the kernel Oops can be found at: 
https://github.com/fho/docker-samba-loop
  I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation 
with:

  - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
  - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
  - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1

  In a different scenario were Ubuntu 16.04 servers were running
  multiple docker containers with Nginx or small network applications in
  parallel, I was also able to reproduce the kernel Oopses also on:

  - linux-image-4.10.0-1004-gcp
  - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830

  I haven't tried again to reproduce it with those kernels on a clean Ubuntu
  installation and unfortunately didn't kept the kernel logs.

  The "unregister_netdevice: waiting for lo to become free. Usage count
  = 1" messages are related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is
  handled as separate issue.

  
  According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
  https://patchwork.ozlabs.org/patch/801533/
  https://patchwork.ozlabs.org/patch/778449/

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

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

[Kernel-packages] [Bug 1729637] [NEW] Samba mount/umount in docker container triggers kernel Oops

[Fabian Holler]

Public bug reported:

When running 2 docker containers, one as samba server and another one as
samba client that mounts and umounts a smb share a kernel OOps can be
triggered on multiple kernels.

The kernel message:
  unregister_netdevice: waiting for lo to become free. Usage count = 1
shows up, some minutes later the oops and/or warnings happens.


The scripts to trigger the kernel Oops can be found at: 
https://github.com/fho/docker-samba-loop
I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation 
with:

- linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
- linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
- linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1

In a different scenario were Ubuntu 16.04 servers were running multiple
docker containers with Nginx or small network applications in parallel,
I was also able to reproduce the kernel Oopses also on:

- linux-image-4.10.0-1004-gcp
- linux-image-4.12.10-041210-generic=4.12.10-041210.20170830

I haven't tried again to reproduce it with those kernels on a clean Ubuntu
installation and unfortunately didn't kept the kernel logs.

The "unregister_netdevice: waiting for lo to become free. Usage count =
1" messages are related to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is
handled as separate issue.


According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
https://patchwork.ozlabs.org/patch/801533/
https://patchwork.ozlabs.org/patch/778449/

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

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

Title:
  Samba mount/umount in docker container triggers kernel Oops

Status in linux package in Ubuntu:
  New

Bug description:
  When running 2 docker containers, one as samba server and another one
  as samba client that mounts and umounts a smb share a kernel OOps can
  be triggered on multiple kernels.

  The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
  shows up, some minutes later the oops and/or warnings happens.

  
  The scripts to trigger the kernel Oops can be found at: 
https://github.com/fho/docker-samba-loop
  I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation 
with:

  - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
  - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
  - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1

  In a different scenario were Ubuntu 16.04 servers were running
  multiple docker containers with Nginx or small network applications in
  parallel, I was also able to reproduce the kernel Oopses also on:

  - linux-image-4.10.0-1004-gcp
  - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830

  I haven't tried again to reproduce it with those kernels on a clean Ubuntu
  installation and unfortunately didn't kept the kernel logs.

  The "unregister_netdevice: waiting for lo to become free. Usage count
  = 1" messages are related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is
  handled as separate issue.

  
  According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
  https://patchwork.ozlabs.org/patch/801533/
  https://patchwork.ozlabs.org/patch/778449/

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

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

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

[Fabian Holler]

Ok, seems that I'm than in the wrong ticket with my issues. :-)
Should separate Ubuntu bug reports be created (if they don't exist already) 
regarding the kernel 
crashes?

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  New
Status in linux source package in Xenial:
  New
Status in linux source package in Zesty:
  New
Status in linux source package in Artful:
  Confirmed
Status in linux source package in Bionic:
  New

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

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

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

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

[Fabian Holler]

According to https://github.com/moby/moby/issues/35068 the crash is
fixed by:

https://patchwork.ozlabs.org/patch/801533/
https://patchwork.ozlabs.org/patch/778449/

** Bug watch added: github.com/moby/moby/issues #35068
   https://github.com/moby/moby/issues/35068

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  New
Status in linux source package in Xenial:
  New
Status in linux source package in Zesty:
  New
Status in linux source package in Artful:
  Confirmed
Status in linux source package in Bionic:
  New

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

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

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

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

[Fabian Holler]

Hello Dan,

thanks for the analysis!

That the startup of containers is delayed is annoying. 
The much bigger issue is that it can reproducible cause a kernel Oops and crash 
a whole machine.

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  New
Status in linux source package in Xenial:
  New
Status in linux source package in Zesty:
  New
Status in linux source package in Artful:
  Confirmed
Status in linux source package in Bionic:
  New

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

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

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

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

[Fabian Holler]

I could not reproduce the bug with the described method with kernel
4.4.0-81-generic and neither with 4.13.0-041300rc7-generic. 4.4.0-81
logged a hung tasks but does not Oops.

So the bug might have been reintroduced between 4.4.0-82 and 4.4.0-93
and 4.13 seems to contain a fix.

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  ?

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

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

[Kernel-packages] [Bug 1709073] Re: [SRU][ZESTY]kernel BUG at /build/linux-H5UzH8/linux-4.10.0/drivers/nvme/host/pci.c:567!

[Fabian Grünbichler]

no longer have the test hardware to verify the kernel in -proposed, but
I did verify that the commit in question fixes the problem (hence my
report ;)).

** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty

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

Title:
  [SRU][ZESTY]kernel BUG at /build/linux-
  H5UzH8/linux-4.10.0/drivers/nvme/host/pci.c:567!

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  SRU Justification:

  Impact: reliably reproducible kernel BUG_ON leading to complete system hang
  Fix: cherry-pick upstream followup commit
  Testcase: mkfs.btrfs on Samsung SM/PM961 no longer triggers the BUG_ON

  Detailed description:

  the fix for http://bugs.launchpad.net/bugs/1657539 which cherry-picked

  729204ef49ec00b788ce23deb9eb922a5769f55d block: relax check on sg gap

  is missing a follow-up fix commit

  5a8d75a1b8c99bdc926ba69b7b7dbe4fae81a5af block: fix bio_will_gap() for
  first bvec with offset

  without, the following BUG_ON is triggered using a mkfs.btrfs
  /dev/nvme0n1 on a Samsung SM961/PM961 M.2 device:

  Aug 07 09:19:09 ubuntu kernel: kernel BUG at 
/build/linux-H5UzH8/linux-4.10.0/drivers/nvme/host/pci.c:567!
  Aug 07 09:19:09 ubuntu kernel: invalid opcode:  [#1] SMP
  Aug 07 09:19:09 ubuntu kernel: Modules linked in: nls_iso8859_1 ppdev 
snd_hda_intel snd_hda_codec snd_hda_core joydev snd_hwdep snd_pcm snd_ti
  Aug 07 09:19:09 ubuntu kernel: CPU: 0 PID: 2071 Comm: mkfs.btrfs Not tainted 
4.10.0-30-generic #34-Ubuntu
  Aug 07 09:19:09 ubuntu kernel: Hardware name: QEMU Standard PC (Q35 + ICH9, 
2009), BIOS 0.0.0 02/06/2015
  Aug 07 09:19:09 ubuntu kernel: task: 8e537417bfc0 task.stack: 
b580c1698000
  Aug 07 09:19:09 ubuntu kernel: RIP: 0010:nvme_queue_rq+0x746/0x8e0 [nvme]
  Aug 07 09:19:09 ubuntu kernel: RSP: 0018:b580c169b950 EFLAGS: 00010286
  Aug 07 09:19:09 ubuntu kernel: RAX: 0078 RBX: fa00 
RCX: 1000
  Aug 07 09:19:09 ubuntu kernel: RDX: 0010 RSI: 0200 
RDI: 0246
  Aug 07 09:19:09 ubuntu kernel: RBP: b580c169ba28 R08: 8e53733cb000 
R09: fa00
  Aug 07 09:19:09 ubuntu kernel: R10: 1000 R11: 8e53733d 
R12: 000273a8a000
  Aug 07 09:19:09 ubuntu kernel: R13: 0002fc00 R14: 8e53733cb000 
R15: 0200
  Aug 07 09:19:09 ubuntu kernel: FS:  7f92511ba080() 
GS:8e537fc0() knlGS:
  Aug 07 09:19:09 ubuntu kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Aug 07 09:19:09 ubuntu kernel: CR2: 7ffeecdc9000 CR3: 000274323000 
CR4: 06f0
  Aug 07 09:19:09 ubuntu kernel: DR0:  DR1:  
DR2: 
  Aug 07 09:19:09 ubuntu kernel: DR3:  DR6: fffe0ff0 
DR7: 0400
  Aug 07 09:19:09 ubuntu kernel: Call Trace:
  Aug 07 09:19:09 ubuntu kernel:  blk_mq_try_issue_directly+0x7e/0x100
  Aug 07 09:19:09 ubuntu kernel:  blk_mq_make_request+0x3cf/0x4e0
  Aug 07 09:19:09 ubuntu kernel:  generic_make_request+0x110/0x2d0
  Aug 07 09:19:09 ubuntu kernel:  submit_bio+0x73/0x150
  Aug 07 09:19:09 ubuntu kernel:  ? __percpu_counter_add+0x4f/0x60
  Aug 07 09:19:09 ubuntu kernel:  submit_bh_wbc+0x152/0x180
  Aug 07 09:19:09 ubuntu kernel:  __block_write_full_page+0x176/0x360
  Aug 07 09:19:09 ubuntu kernel:  ? I_BDEV+0x20/0x20
  Aug 07 09:19:09 ubuntu kernel:  ? I_BDEV+0x20/0x20
  Aug 07 09:19:09 ubuntu kernel:  block_write_full_page+0x13b/0x160
  Aug 07 09:19:09 ubuntu kernel:  blkdev_writepage+0x18/0x20
  Aug 07 09:19:09 ubuntu kernel:  __writepage+0x13/0x30
  Aug 07 09:19:09 ubuntu kernel:  write_cache_pages+0x205/0x530
  Aug 07 09:19:09 ubuntu kernel:  ? wb_position_ratio+0x1f0/0x1f0
  Aug 07 09:19:09 ubuntu kernel:  generic_writepages+0x56/0x90
  Aug 07 09:19:09 ubuntu kernel:  blkdev_writepages+0x2f/0x40
  Aug 07 09:19:09 ubuntu kernel:  do_writepages+0x1e/0x30
  Aug 07 09:19:09 ubuntu kernel:  __filemap_fdatawrite_range+0xc6/0x100
  Aug 07 09:19:09 ubuntu kernel:  SyS_fadvise64+0x25e/0x290
  Aug 07 09:19:09 ubuntu kernel:  entry_SYSCALL_64_fastpath+0x1e/0xad
  Aug 07 09:19:09 ubuntu kernel: RIP: 0033:0x7f925066debd
  Aug 07 09:19:09 ubuntu kernel: RSP: 002b:7ffeecd46a38 EFLAGS: 0246 
ORIG_RAX: 00dd
  Aug 07 09:19:09 ubuntu kernel: RAX: ffda RBX: 7ffeecd45a30 
RCX: 7f925066debd
  Aug 07 09:19:09 ubuntu kernel: RDX:  RSI:  
RDI: 0004
  Aug 07 09:19:09 ubuntu kernel: RBP:  R08:  
R09: 1001
  Aug 07 09:19:09 ubuntu kernel: R10: 0004 R11: 0246 
R12: 0010
  Aug 07 09:19:09 ubuntu kernel: R13: 7ffeecd45a40 R14: 0004 
R15: 000

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

[Fabian Holler]

Attached are the logs for an Oops on Ubuntu 14.04 on kernel linux-
image-4.4.0-93-generic=4.4.0-93.116~14.04.1

** Attachment added: "kernoops-4.4.0-93.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407/+attachment/4941963/+files/kernoops-4.4.0-93.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/1711407

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  ?

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

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

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

[Fabian Holler]

With https://github.com/fho/docker-samba-loop I was able to reproduce
kernel Oopses on a clean Ubuntu 16.0.4 installation with:

- linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
- linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1

On 4.11.0-14 it was much harder to reproduce. Sometimes only a warning
happened, 1x time I was able to produce an Oops with
https://github.com/fho/docker-samba-loop/commits/more_stress
But I don't know if the changes in the branch made it more likely to happen or
if it was only a coincidence.


The kernel message:
  unregister_netdevice: waiting for lo to become free. Usage count = 1
shows up, some minutes later the oops and/or warning happens.


In a different scenario were the Ubuntu 16.04 servers were running multiple 
docker containers with Nginx or small network applications in parallel, I was 
also able to reproduce the kernel Oopses also on:

- linux-image-4.10.0-1004-gcp
- linux-image-4.4.0-93-generic
- linux-image-4.11.0-14-generic
- linux-image-4.12.10-041210-generic=4.12.10-041210.20170830

I haven't tried again to reproduce it with those kernels on a clean Ubuntu
installation and unfortunately didn't kept the kernel logs.


Kernel logs can be found in the attached file.

** Attachment added: "kernel-logs.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407/+attachment/4941935/+files/kernel-logs.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/1711407

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  ?

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

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

[Kernel-packages] [Bug 1709073] Re: [SRU][ZESTY]kernel BUG at /build/linux-H5UzH8/linux-4.10.0/drivers/nvme/host/pci.c:567!

[Fabian Grünbichler]

apport-collect does not work after triggering the issue, and I have
included the relevant kernel traces anyway. => confirmed

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

Title:
  [SRU][ZESTY]kernel BUG at /build/linux-
  H5UzH8/linux-4.10.0/drivers/nvme/host/pci.c:567!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SRU Justification:

  Impact: reliably reproducible kernel BUG_ON leading to complete system hang
  Fix: cherry-pick upstream followup commit
  Testcase: mkfs.btrfs on Samsung SM/PM961 no longer triggers the BUG_ON

  Detailed description:

  the fix for http://bugs.launchpad.net/bugs/1657539 which cherry-picked

  729204ef49ec00b788ce23deb9eb922a5769f55d block: relax check on sg gap

  is missing a follow-up fix commit

  5a8d75a1b8c99bdc926ba69b7b7dbe4fae81a5af block: fix bio_will_gap() for
  first bvec with offset

  without, the following BUG_ON is triggered using a mkfs.btrfs
  /dev/nvme0n1 on a Samsung SM961/PM961 M.2 device:

  Aug 07 09:19:09 ubuntu kernel: kernel BUG at 
/build/linux-H5UzH8/linux-4.10.0/drivers/nvme/host/pci.c:567!
  Aug 07 09:19:09 ubuntu kernel: invalid opcode:  [#1] SMP
  Aug 07 09:19:09 ubuntu kernel: Modules linked in: nls_iso8859_1 ppdev 
snd_hda_intel snd_hda_codec snd_hda_core joydev snd_hwdep snd_pcm snd_ti
  Aug 07 09:19:09 ubuntu kernel: CPU: 0 PID: 2071 Comm: mkfs.btrfs Not tainted 
4.10.0-30-generic #34-Ubuntu
  Aug 07 09:19:09 ubuntu kernel: Hardware name: QEMU Standard PC (Q35 + ICH9, 
2009), BIOS 0.0.0 02/06/2015
  Aug 07 09:19:09 ubuntu kernel: task: 8e537417bfc0 task.stack: 
b580c1698000
  Aug 07 09:19:09 ubuntu kernel: RIP: 0010:nvme_queue_rq+0x746/0x8e0 [nvme]
  Aug 07 09:19:09 ubuntu kernel: RSP: 0018:b580c169b950 EFLAGS: 00010286
  Aug 07 09:19:09 ubuntu kernel: RAX: 0078 RBX: fa00 
RCX: 1000
  Aug 07 09:19:09 ubuntu kernel: RDX: 0010 RSI: 0200 
RDI: 0246
  Aug 07 09:19:09 ubuntu kernel: RBP: b580c169ba28 R08: 8e53733cb000 
R09: fa00
  Aug 07 09:19:09 ubuntu kernel: R10: 1000 R11: 8e53733d 
R12: 000273a8a000
  Aug 07 09:19:09 ubuntu kernel: R13: 0002fc00 R14: 8e53733cb000 
R15: 0200
  Aug 07 09:19:09 ubuntu kernel: FS:  7f92511ba080() 
GS:8e537fc0() knlGS:
  Aug 07 09:19:09 ubuntu kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Aug 07 09:19:09 ubuntu kernel: CR2: 7ffeecdc9000 CR3: 000274323000 
CR4: 06f0
  Aug 07 09:19:09 ubuntu kernel: DR0:  DR1:  
DR2: 
  Aug 07 09:19:09 ubuntu kernel: DR3:  DR6: fffe0ff0 
DR7: 0400
  Aug 07 09:19:09 ubuntu kernel: Call Trace:
  Aug 07 09:19:09 ubuntu kernel:  blk_mq_try_issue_directly+0x7e/0x100
  Aug 07 09:19:09 ubuntu kernel:  blk_mq_make_request+0x3cf/0x4e0
  Aug 07 09:19:09 ubuntu kernel:  generic_make_request+0x110/0x2d0
  Aug 07 09:19:09 ubuntu kernel:  submit_bio+0x73/0x150
  Aug 07 09:19:09 ubuntu kernel:  ? __percpu_counter_add+0x4f/0x60
  Aug 07 09:19:09 ubuntu kernel:  submit_bh_wbc+0x152/0x180
  Aug 07 09:19:09 ubuntu kernel:  __block_write_full_page+0x176/0x360
  Aug 07 09:19:09 ubuntu kernel:  ? I_BDEV+0x20/0x20
  Aug 07 09:19:09 ubuntu kernel:  ? I_BDEV+0x20/0x20
  Aug 07 09:19:09 ubuntu kernel:  block_write_full_page+0x13b/0x160
  Aug 07 09:19:09 ubuntu kernel:  blkdev_writepage+0x18/0x20
  Aug 07 09:19:09 ubuntu kernel:  __writepage+0x13/0x30
  Aug 07 09:19:09 ubuntu kernel:  write_cache_pages+0x205/0x530
  Aug 07 09:19:09 ubuntu kernel:  ? wb_position_ratio+0x1f0/0x1f0
  Aug 07 09:19:09 ubuntu kernel:  generic_writepages+0x56/0x90
  Aug 07 09:19:09 ubuntu kernel:  blkdev_writepages+0x2f/0x40
  Aug 07 09:19:09 ubuntu kernel:  do_writepages+0x1e/0x30
  Aug 07 09:19:09 ubuntu kernel:  __filemap_fdatawrite_range+0xc6/0x100
  Aug 07 09:19:09 ubuntu kernel:  SyS_fadvise64+0x25e/0x290
  Aug 07 09:19:09 ubuntu kernel:  entry_SYSCALL_64_fastpath+0x1e/0xad
  Aug 07 09:19:09 ubuntu kernel: RIP: 0033:0x7f925066debd
  Aug 07 09:19:09 ubuntu kernel: RSP: 002b:7ffeecd46a38 EFLAGS: 0246 
ORIG_RAX: 00dd
  Aug 07 09:19:09 ubuntu kernel: RAX: ffda RBX: 7ffeecd45a30 
RCX: 7f925066debd
  Aug 07 09:19:09 ubuntu kernel: RDX:  RSI:  
RDI: 0004
  Aug 07 09:19:09 ubuntu kernel: RBP:  R08:  
R09: 1001
  Aug 07 09:19:09 ubuntu kernel: R10: 0004 R11: 0246 
R12: 0010
  Aug 07 09:19:09 ubuntu kernel: R13: 7ffeecd45a40 R14: 0004 
R15: 
  Aug 07 09:19:09 ubuntu kernel: Code: f1 61 26 d5 8b 95 48 ff ff ff 48 89 85 
60 ff ff 

[Kernel-packages] [Bug 1709073] Re: [SRU][ZESTY]kernel BUG at /build/linux-H5UzH8/linux-4.10.0/drivers/nvme/host/pci.c:567!

[Fabian Grünbichler]

** Tags added: zesty

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

Title:
  [SRU][ZESTY]kernel BUG at /build/linux-
  H5UzH8/linux-4.10.0/drivers/nvme/host/pci.c:567!

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  SRU Justification:

  Impact: reliably reproducible kernel BUG_ON leading to complete system hang
  Fix: cherry-pick upstream followup commit
  Testcase: mkfs.btrfs on Samsung SM/PM961 no longer triggers the BUG_ON

  Detailed description:

  the fix for http://bugs.launchpad.net/bugs/1657539 which cherry-picked

  729204ef49ec00b788ce23deb9eb922a5769f55d block: relax check on sg gap

  is missing a follow-up fix commit

  5a8d75a1b8c99bdc926ba69b7b7dbe4fae81a5af block: fix bio_will_gap() for
  first bvec with offset

  without, the following BUG_ON is triggered using a mkfs.btrfs
  /dev/nvme0n1 on a Samsung SM961/PM961 M.2 device:

  Aug 07 09:19:09 ubuntu kernel: kernel BUG at 
/build/linux-H5UzH8/linux-4.10.0/drivers/nvme/host/pci.c:567!
  Aug 07 09:19:09 ubuntu kernel: invalid opcode:  [#1] SMP
  Aug 07 09:19:09 ubuntu kernel: Modules linked in: nls_iso8859_1 ppdev 
snd_hda_intel snd_hda_codec snd_hda_core joydev snd_hwdep snd_pcm snd_ti
  Aug 07 09:19:09 ubuntu kernel: CPU: 0 PID: 2071 Comm: mkfs.btrfs Not tainted 
4.10.0-30-generic #34-Ubuntu
  Aug 07 09:19:09 ubuntu kernel: Hardware name: QEMU Standard PC (Q35 + ICH9, 
2009), BIOS 0.0.0 02/06/2015
  Aug 07 09:19:09 ubuntu kernel: task: 8e537417bfc0 task.stack: 
b580c1698000
  Aug 07 09:19:09 ubuntu kernel: RIP: 0010:nvme_queue_rq+0x746/0x8e0 [nvme]
  Aug 07 09:19:09 ubuntu kernel: RSP: 0018:b580c169b950 EFLAGS: 00010286
  Aug 07 09:19:09 ubuntu kernel: RAX: 0078 RBX: fa00 
RCX: 1000
  Aug 07 09:19:09 ubuntu kernel: RDX: 0010 RSI: 0200 
RDI: 0246
  Aug 07 09:19:09 ubuntu kernel: RBP: b580c169ba28 R08: 8e53733cb000 
R09: fa00
  Aug 07 09:19:09 ubuntu kernel: R10: 1000 R11: 8e53733d 
R12: 000273a8a000
  Aug 07 09:19:09 ubuntu kernel: R13: 0002fc00 R14: 8e53733cb000 
R15: 0200
  Aug 07 09:19:09 ubuntu kernel: FS:  7f92511ba080() 
GS:8e537fc0() knlGS:
  Aug 07 09:19:09 ubuntu kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Aug 07 09:19:09 ubuntu kernel: CR2: 7ffeecdc9000 CR3: 000274323000 
CR4: 06f0
  Aug 07 09:19:09 ubuntu kernel: DR0:  DR1:  
DR2: 
  Aug 07 09:19:09 ubuntu kernel: DR3:  DR6: fffe0ff0 
DR7: 0400
  Aug 07 09:19:09 ubuntu kernel: Call Trace:
  Aug 07 09:19:09 ubuntu kernel:  blk_mq_try_issue_directly+0x7e/0x100
  Aug 07 09:19:09 ubuntu kernel:  blk_mq_make_request+0x3cf/0x4e0
  Aug 07 09:19:09 ubuntu kernel:  generic_make_request+0x110/0x2d0
  Aug 07 09:19:09 ubuntu kernel:  submit_bio+0x73/0x150
  Aug 07 09:19:09 ubuntu kernel:  ? __percpu_counter_add+0x4f/0x60
  Aug 07 09:19:09 ubuntu kernel:  submit_bh_wbc+0x152/0x180
  Aug 07 09:19:09 ubuntu kernel:  __block_write_full_page+0x176/0x360
  Aug 07 09:19:09 ubuntu kernel:  ? I_BDEV+0x20/0x20
  Aug 07 09:19:09 ubuntu kernel:  ? I_BDEV+0x20/0x20
  Aug 07 09:19:09 ubuntu kernel:  block_write_full_page+0x13b/0x160
  Aug 07 09:19:09 ubuntu kernel:  blkdev_writepage+0x18/0x20
  Aug 07 09:19:09 ubuntu kernel:  __writepage+0x13/0x30
  Aug 07 09:19:09 ubuntu kernel:  write_cache_pages+0x205/0x530
  Aug 07 09:19:09 ubuntu kernel:  ? wb_position_ratio+0x1f0/0x1f0
  Aug 07 09:19:09 ubuntu kernel:  generic_writepages+0x56/0x90
  Aug 07 09:19:09 ubuntu kernel:  blkdev_writepages+0x2f/0x40
  Aug 07 09:19:09 ubuntu kernel:  do_writepages+0x1e/0x30
  Aug 07 09:19:09 ubuntu kernel:  __filemap_fdatawrite_range+0xc6/0x100
  Aug 07 09:19:09 ubuntu kernel:  SyS_fadvise64+0x25e/0x290
  Aug 07 09:19:09 ubuntu kernel:  entry_SYSCALL_64_fastpath+0x1e/0xad
  Aug 07 09:19:09 ubuntu kernel: RIP: 0033:0x7f925066debd
  Aug 07 09:19:09 ubuntu kernel: RSP: 002b:7ffeecd46a38 EFLAGS: 0246 
ORIG_RAX: 00dd
  Aug 07 09:19:09 ubuntu kernel: RAX: ffda RBX: 7ffeecd45a30 
RCX: 7f925066debd
  Aug 07 09:19:09 ubuntu kernel: RDX:  RSI:  
RDI: 0004
  Aug 07 09:19:09 ubuntu kernel: RBP:  R08:  
R09: 1001
  Aug 07 09:19:09 ubuntu kernel: R10: 0004 R11: 0246 
R12: 0010
  Aug 07 09:19:09 ubuntu kernel: R13: 7ffeecd45a40 R14: 0004 
R15: 
  Aug 07 09:19:09 ubuntu kernel: Code: f1 61 26 d5 8b 95 48 ff ff ff 48 89 85 
60 ff ff ff 4c 8b 50 10 44 8b 48 18 8b 8d 50 ff ff ff 44 8b 9d 58
  Aug 07 09:19:09 ubuntu kernel: RIP: nvme_queue_rq+0x746/0x8e0 [nvme] RSP: 
b580c169b950

  LKML reference: htt

[Kernel-packages] [Bug 1709073] [NEW] [SRU][ZESTY]kernel BUG at /build/linux-H5UzH8/linux-4.10.0/drivers/nvme/host/pci.c:567!

[Fabian Grünbichler]

Public bug reported:

SRU Justification:

Impact: reliably reproducible kernel BUG_ON leading to complete system hang
Fix: cherry-pick upstream followup commit
Testcase: mkfs.btrfs on Samsung SM/PM961 no longer triggers the BUG_ON

Detailed description:

the fix for http://bugs.launchpad.net/bugs/1657539 which cherry-picked

729204ef49ec00b788ce23deb9eb922a5769f55d block: relax check on sg gap

is missing a follow-up fix commit

5a8d75a1b8c99bdc926ba69b7b7dbe4fae81a5af block: fix bio_will_gap() for
first bvec with offset

without, the following BUG_ON is triggered using a mkfs.btrfs
/dev/nvme0n1 on a Samsung SM961/PM961 M.2 device:

Aug 07 09:19:09 ubuntu kernel: kernel BUG at 
/build/linux-H5UzH8/linux-4.10.0/drivers/nvme/host/pci.c:567!
Aug 07 09:19:09 ubuntu kernel: invalid opcode:  [#1] SMP
Aug 07 09:19:09 ubuntu kernel: Modules linked in: nls_iso8859_1 ppdev 
snd_hda_intel snd_hda_codec snd_hda_core joydev snd_hwdep snd_pcm snd_ti
Aug 07 09:19:09 ubuntu kernel: CPU: 0 PID: 2071 Comm: mkfs.btrfs Not tainted 
4.10.0-30-generic #34-Ubuntu
Aug 07 09:19:09 ubuntu kernel: Hardware name: QEMU Standard PC (Q35 + ICH9, 
2009), BIOS 0.0.0 02/06/2015
Aug 07 09:19:09 ubuntu kernel: task: 8e537417bfc0 task.stack: 
b580c1698000
Aug 07 09:19:09 ubuntu kernel: RIP: 0010:nvme_queue_rq+0x746/0x8e0 [nvme]
Aug 07 09:19:09 ubuntu kernel: RSP: 0018:b580c169b950 EFLAGS: 00010286
Aug 07 09:19:09 ubuntu kernel: RAX: 0078 RBX: fa00 RCX: 
1000
Aug 07 09:19:09 ubuntu kernel: RDX: 0010 RSI: 0200 RDI: 
0246
Aug 07 09:19:09 ubuntu kernel: RBP: b580c169ba28 R08: 8e53733cb000 R09: 
fa00
Aug 07 09:19:09 ubuntu kernel: R10: 1000 R11: 8e53733d R12: 
000273a8a000
Aug 07 09:19:09 ubuntu kernel: R13: 0002fc00 R14: 8e53733cb000 R15: 
0200
Aug 07 09:19:09 ubuntu kernel: FS:  7f92511ba080() 
GS:8e537fc0() knlGS:
Aug 07 09:19:09 ubuntu kernel: CS:  0010 DS:  ES:  CR0: 80050033
Aug 07 09:19:09 ubuntu kernel: CR2: 7ffeecdc9000 CR3: 000274323000 CR4: 
06f0
Aug 07 09:19:09 ubuntu kernel: DR0:  DR1:  DR2: 

Aug 07 09:19:09 ubuntu kernel: DR3:  DR6: fffe0ff0 DR7: 
0400
Aug 07 09:19:09 ubuntu kernel: Call Trace:
Aug 07 09:19:09 ubuntu kernel:  blk_mq_try_issue_directly+0x7e/0x100
Aug 07 09:19:09 ubuntu kernel:  blk_mq_make_request+0x3cf/0x4e0
Aug 07 09:19:09 ubuntu kernel:  generic_make_request+0x110/0x2d0
Aug 07 09:19:09 ubuntu kernel:  submit_bio+0x73/0x150
Aug 07 09:19:09 ubuntu kernel:  ? __percpu_counter_add+0x4f/0x60
Aug 07 09:19:09 ubuntu kernel:  submit_bh_wbc+0x152/0x180
Aug 07 09:19:09 ubuntu kernel:  __block_write_full_page+0x176/0x360
Aug 07 09:19:09 ubuntu kernel:  ? I_BDEV+0x20/0x20
Aug 07 09:19:09 ubuntu kernel:  ? I_BDEV+0x20/0x20
Aug 07 09:19:09 ubuntu kernel:  block_write_full_page+0x13b/0x160
Aug 07 09:19:09 ubuntu kernel:  blkdev_writepage+0x18/0x20
Aug 07 09:19:09 ubuntu kernel:  __writepage+0x13/0x30
Aug 07 09:19:09 ubuntu kernel:  write_cache_pages+0x205/0x530
Aug 07 09:19:09 ubuntu kernel:  ? wb_position_ratio+0x1f0/0x1f0
Aug 07 09:19:09 ubuntu kernel:  generic_writepages+0x56/0x90
Aug 07 09:19:09 ubuntu kernel:  blkdev_writepages+0x2f/0x40
Aug 07 09:19:09 ubuntu kernel:  do_writepages+0x1e/0x30
Aug 07 09:19:09 ubuntu kernel:  __filemap_fdatawrite_range+0xc6/0x100
Aug 07 09:19:09 ubuntu kernel:  SyS_fadvise64+0x25e/0x290
Aug 07 09:19:09 ubuntu kernel:  entry_SYSCALL_64_fastpath+0x1e/0xad
Aug 07 09:19:09 ubuntu kernel: RIP: 0033:0x7f925066debd
Aug 07 09:19:09 ubuntu kernel: RSP: 002b:7ffeecd46a38 EFLAGS: 0246 
ORIG_RAX: 00dd
Aug 07 09:19:09 ubuntu kernel: RAX: ffda RBX: 7ffeecd45a30 RCX: 
7f925066debd
Aug 07 09:19:09 ubuntu kernel: RDX:  RSI:  RDI: 
0004
Aug 07 09:19:09 ubuntu kernel: RBP:  R08:  R09: 
1001
Aug 07 09:19:09 ubuntu kernel: R10: 0004 R11: 0246 R12: 
0010
Aug 07 09:19:09 ubuntu kernel: R13: 7ffeecd45a40 R14: 0004 R15: 

Aug 07 09:19:09 ubuntu kernel: Code: f1 61 26 d5 8b 95 48 ff ff ff 48 89 85 60 
ff ff ff 4c 8b 50 10 44 8b 48 18 8b 8d 50 ff ff ff 44 8b 9d 58
Aug 07 09:19:09 ubuntu kernel: RIP: nvme_queue_rq+0x746/0x8e0 [nvme] RSP: 
b580c169b950

LKML reference: https://lkml.org/lkml/2017/4/13/105

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


** Tags: zesty

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

Title:
  [SRU][ZESTY]kernel BUG at /build/linux-
  H5UzH8/linux-4.10.0/drivers/nvme/host/pci.c:567!

Status in linux package in Ubuntu:
  New

Bug description:
  S

[Kernel-packages] [Bug 1682368] Re: refcount underflow / kernel NULL dereference after attempting to add basic tc filter

[Fabian Grünbichler]

** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty

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

Title:
  refcount underflow / kernel NULL dereference after attempting to add
  basic tc filter

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

Bug description:
  == SRU Justification ==

  Impact: adding a tc filter sometimes fails, potentially followed by
  kernel hangs and kernel NULL pointer dereference

  Fix: proposed upstream by Wolfgang Bumiller [1,2]

  Regression Potential: Since nobody else noticed this issue in 4.11 >=
  rc1 or Ubuntu 4.10 >= 15.17, and the fix only touches the broken code,
  the regression potential should be minimal ;)

  1: http://marc.info/?l=linux-netdev&m=149200746116365
  2: http://marc.info/?l=linux-netdev&m=149200742616349

  ---

  Commit 1045ba77a which was backported for #1674087 in
  fc0cef7a8ec1e63ee3405f642983dd86e04ab6cc (first released with
  Ubuntu-4.10.0-15.17) introduces the problematic code. Note that while
  the traces below were generated using a custom patched kernel, the
  same issue is reproducible using Ubuntu Zesty's 4.10.0-15.17 (and
  later) kernels.

  The full cover letter of the proposed fix by my colleague Wolfgang
  Bumiller follows:

  Commit 1045ba77a ("net sched actions: Add support for user cookies")
  added code to net/sched/act_api.c's tcf_action_init_1 using the `tb`
  nlattr array unconditionally, while it was otherwise used as well as
  initialized only when `name == NULL`:

if (name == NULL) {
err = nla_parse_nested(tb, TCA_ACT_MAX, nla, NULL);

  In the other case `nla` is instead passed over to ->init to be parsed
  there (using a different set of TCA_ enum values, iow. TCA_ACT_COOKIE
  then "clashes" with some other value). This lead to the following three
  example commands resulting in errors (sometimes followed by more traces
  and hangups some time later (although the hangups happened seconds or
  sometimes minutes later, sometimes not at all - results differed between
  different kernel versions (linux git-master vs ubuntu's mainline 4.11
  rc6 vs. pve 4.10.5 (based off ubuntu's zesty kernel where the commit is
  cherry-picked)...))):

   # ip link add ve0 type veth peer name ve0b
   # tc qdisc add dev ve0 handle : ingress
   # tc filter add dev ve0 parent : prio 50 basic police rate 1000bps burst 
1000b drop

  The 3rd command would sometimes succeed, sometimes error with:

   RTNETLINK answers: Invalid argument
   We have an error talking to the kernel

  and sometimes error with:

   RTNETLINK answers: Cannot allocate memory
   We have an error talking to the kernel

  In the latter case I assume `cklen` became negative, which passes the
  TC_COOKIE_MAX_SIZE check since it is signed but becomes unsigned later
  in kmemdup() (see the crash dump below)

  When the `tc filter add` command fails a backtrace shows up in dmesg,
  added below.

  I'm not sure why the TC_ACT_COOKIE code was added to tcf_action_init_1
  where it is now. It makes me think that it's supposed to be available
  universally, but the `name == NULL` check for how nla is used or passed
  to ->init() shows that the there are various different TC_ACT_* enums in
  use at this point, hence the 'RFC' part of the patches, I'm not that
  familiar with the code yet.

  Backtrace when running `tc filter add`:

  Apr 12 11:31:38 testmachine kernel: [ cut here ]
  Apr 12 11:31:38 testmachine kernel: WARNING: CPU: 7 PID: 16596 at 
mm/page_alloc.c:3541 __alloc_pages_slowpath+0x9fe/0xba0
  Apr 12 11:31:38 testmachine kernel: Modules linked in: act_police 
cls_basic sch_ingress veth nfsv3 nfs_acl nfs lockd grace ip6t_REJECT 
nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables 
xt_mac ipt_REJECT nf_reject_ipv4 xt_physdev xt_comment nf_conntrack_ipv4 
nf_defrag_ipv4 xt_tcpudp xt_mark xt_set xt_addrtype xt_multiport xt_conntrack 
nf_conntrack ip_set_hash_net ip_set arc4 md4 nls_utf8 cifs ccm fscache ipta
  Apr 12 11:31:38 testmachine kernel:  snd_hda_codec_realtek 
snd_hda_codec_generic aesni_intel aes_x86_64 crypto_simd drm_kms_helper 
glue_helper cryptd drm snd_hda_intel intel_cstate snd_hda_codec i2c_algo_bit 
fb_sys_fops snd_hda_core joydev syscopyarea snd_hwdep sysfillrect input_leds 
sysimgblt intel_rapl_perf snd_pcm snd_timer snd pcspkr soundcore mei_me lpc_ich 
mei shpchp tpm_infineon mac_hid wmi acpi_pad video vhost_net vhost macv
  Apr 12 11:31:38 testmachine kernel: CPU: 7 PID: 16596 Comm: tc Tainted: P 
  O4.10.5-1-pve #1
  Apr 12 11:31:38 testmachine kernel: Hardware name: ASUS All Series/Z97-A, 
BIOS 2801 11/11/2015
  Apr 12 11:31:38 testmachine kernel: Call Trace:
  Apr 12 11:31:38 testmachine kernel:  dump_stack+0x63/0x81
  Apr 1

[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

[Fabian Grünbichler]

@tasman: it's already slated for inclusion into one of the next kernel
packages: https://lists.ubuntu.com/archives/kernel-
team/2017-May/083976.html

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

Title:
  kernel BUG at /build/linux-
  7LGLH_/linux-4.10.0/include/linux/swapops.h:129

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-edge package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux-hwe-edge source package in Zesty:
  In Progress

Bug description:
  Randomly, khugepaged process will take 100% CPU, and I can only
  restart the computer to recover it.

  Relevant dmesg attached (dmesg_crash.txt).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mathieu2221 F pulseaudio
   /dev/snd/pcmC1D0p:   mathieu2221 F...m pulseaudio
   /dev/snd/controlC1:  mathieu2221 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar 21 23:03:23 2017
  HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd
  InstallationDate: Installed on 2016-01-31 (415 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: LENOVO 20344
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1682368] Re: refcount underflow / kernel NULL dereference after attempting to add basic tc filter

[Fabian Grünbichler]

and applied in v4.11-rc8:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e0535ce58b92d7baf0b33284a6c4f8f0338f943e

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

Title:
  refcount underflow / kernel NULL dereference after attempting to add
  basic tc filter

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

Bug description:
  == SRU Justification ==

  Impact: adding a tc filter sometimes fails, potentially followed by
  kernel hangs and kernel NULL pointer dereference

  Fix: proposed upstream by Wolfgang Bumiller [1,2]

  Regression Potential: Since nobody else noticed this issue in 4.11 >=
  rc1 or Ubuntu 4.10 >= 15.17, and the fix only touches the broken code,
  the regression potential should be minimal ;)

  1: http://marc.info/?l=linux-netdev&m=149200746116365
  2: http://marc.info/?l=linux-netdev&m=149200742616349

  ---

  Commit 1045ba77a which was backported for #1674087 in
  fc0cef7a8ec1e63ee3405f642983dd86e04ab6cc (first released with
  Ubuntu-4.10.0-15.17) introduces the problematic code. Note that while
  the traces below were generated using a custom patched kernel, the
  same issue is reproducible using Ubuntu Zesty's 4.10.0-15.17 (and
  later) kernels.

  The full cover letter of the proposed fix by my colleague Wolfgang
  Bumiller follows:

  Commit 1045ba77a ("net sched actions: Add support for user cookies")
  added code to net/sched/act_api.c's tcf_action_init_1 using the `tb`
  nlattr array unconditionally, while it was otherwise used as well as
  initialized only when `name == NULL`:

if (name == NULL) {
err = nla_parse_nested(tb, TCA_ACT_MAX, nla, NULL);

  In the other case `nla` is instead passed over to ->init to be parsed
  there (using a different set of TCA_ enum values, iow. TCA_ACT_COOKIE
  then "clashes" with some other value). This lead to the following three
  example commands resulting in errors (sometimes followed by more traces
  and hangups some time later (although the hangups happened seconds or
  sometimes minutes later, sometimes not at all - results differed between
  different kernel versions (linux git-master vs ubuntu's mainline 4.11
  rc6 vs. pve 4.10.5 (based off ubuntu's zesty kernel where the commit is
  cherry-picked)...))):

   # ip link add ve0 type veth peer name ve0b
   # tc qdisc add dev ve0 handle : ingress
   # tc filter add dev ve0 parent : prio 50 basic police rate 1000bps burst 
1000b drop

  The 3rd command would sometimes succeed, sometimes error with:

   RTNETLINK answers: Invalid argument
   We have an error talking to the kernel

  and sometimes error with:

   RTNETLINK answers: Cannot allocate memory
   We have an error talking to the kernel

  In the latter case I assume `cklen` became negative, which passes the
  TC_COOKIE_MAX_SIZE check since it is signed but becomes unsigned later
  in kmemdup() (see the crash dump below)

  When the `tc filter add` command fails a backtrace shows up in dmesg,
  added below.

  I'm not sure why the TC_ACT_COOKIE code was added to tcf_action_init_1
  where it is now. It makes me think that it's supposed to be available
  universally, but the `name == NULL` check for how nla is used or passed
  to ->init() shows that the there are various different TC_ACT_* enums in
  use at this point, hence the 'RFC' part of the patches, I'm not that
  familiar with the code yet.

  Backtrace when running `tc filter add`:

  Apr 12 11:31:38 testmachine kernel: [ cut here ]
  Apr 12 11:31:38 testmachine kernel: WARNING: CPU: 7 PID: 16596 at 
mm/page_alloc.c:3541 __alloc_pages_slowpath+0x9fe/0xba0
  Apr 12 11:31:38 testmachine kernel: Modules linked in: act_police 
cls_basic sch_ingress veth nfsv3 nfs_acl nfs lockd grace ip6t_REJECT 
nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables 
xt_mac ipt_REJECT nf_reject_ipv4 xt_physdev xt_comment nf_conntrack_ipv4 
nf_defrag_ipv4 xt_tcpudp xt_mark xt_set xt_addrtype xt_multiport xt_conntrack 
nf_conntrack ip_set_hash_net ip_set arc4 md4 nls_utf8 cifs ccm fscache ipta
  Apr 12 11:31:38 testmachine kernel:  snd_hda_codec_realtek 
snd_hda_codec_generic aesni_intel aes_x86_64 crypto_simd drm_kms_helper 
glue_helper cryptd drm snd_hda_intel intel_cstate snd_hda_codec i2c_algo_bit 
fb_sys_fops snd_hda_core joydev syscopyarea snd_hwdep sysfillrect input_leds 
sysimgblt intel_rapl_perf snd_pcm snd_timer snd pcspkr soundcore mei_me lpc_ich 
mei shpchp tpm_infineon mac_hid wmi acpi_pad video vhost_net vhost macv
  Apr 12 11:31:38 testmachine kernel: CPU: 7 PID: 16596 Comm: tc Tainted: P 
  O4.10.5-1-pve #1
  Apr 12 11:31:38 testmachine kernel: Hardware name: ASUS All Series/Z97-A, 
BIOS 2801 11/11/2015
  Apr 12 11:31:38 testmachine kernel: Call Trace:
  Apr 12 11

[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

[Fabian Grünbichler]

the only big mm changes pulled in from 4.11.x that I could find with a
quick look through the history are related to KSM, but those are missing
a later fixup (from 4.11.x as well):

d75450ff40df0199bf13dfb19f435519ff947138 which fixes ace71a19cec5 ("mm:
introduce page_vma_mapped_walk()")

ace71a19cec5 was first contained in Ubuntu-4.10.0-14.16, which AFAICT
fits nicely into the working/non-working kernels reported by various
users here?

there are also a few other commits by the same upstream author, which do
not explicitly contain any followup/fixes tags but touch similar code,
some of which were picked.

since I cannot reproduce the problem at hand, I cannot tell whether
including that fixup helps, but it might be worth a shot.

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

Title:
  kernel BUG at /build/linux-
  7LGLH_/linux-4.10.0/include/linux/swapops.h:129

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

Bug description:
  Randomly, khugepaged process will take 100% CPU, and I can only
  restart the computer to recover it.

  Relevant dmesg attached (dmesg_crash.txt).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mathieu2221 F pulseaudio
   /dev/snd/pcmC1D0p:   mathieu2221 F...m pulseaudio
   /dev/snd/controlC1:  mathieu2221 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar 21 23:03:23 2017
  HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd
  InstallationDate: Installed on 2016-01-31 (415 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: LENOVO 20344
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1682368] Re: refcount underflow / kernel NULL dereference after attempting to add basic tc filter

[Fabian Grünbichler]

the proposed fix has been queue for -stable in v3, now as a single patch:
http://marc.info/?t=14926902325

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

Title:
  refcount underflow / kernel NULL dereference after attempting to add
  basic tc filter

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

Bug description:
  == SRU Justification ==

  Impact: adding a tc filter sometimes fails, potentially followed by
  kernel hangs and kernel NULL pointer dereference

  Fix: proposed upstream by Wolfgang Bumiller [1,2]

  Regression Potential: Since nobody else noticed this issue in 4.11 >=
  rc1 or Ubuntu 4.10 >= 15.17, and the fix only touches the broken code,
  the regression potential should be minimal ;)

  1: http://marc.info/?l=linux-netdev&m=149200746116365
  2: http://marc.info/?l=linux-netdev&m=149200742616349

  ---

  Commit 1045ba77a which was backported for #1674087 in
  fc0cef7a8ec1e63ee3405f642983dd86e04ab6cc (first released with
  Ubuntu-4.10.0-15.17) introduces the problematic code. Note that while
  the traces below were generated using a custom patched kernel, the
  same issue is reproducible using Ubuntu Zesty's 4.10.0-15.17 (and
  later) kernels.

  The full cover letter of the proposed fix by my colleague Wolfgang
  Bumiller follows:

  Commit 1045ba77a ("net sched actions: Add support for user cookies")
  added code to net/sched/act_api.c's tcf_action_init_1 using the `tb`
  nlattr array unconditionally, while it was otherwise used as well as
  initialized only when `name == NULL`:

if (name == NULL) {
err = nla_parse_nested(tb, TCA_ACT_MAX, nla, NULL);

  In the other case `nla` is instead passed over to ->init to be parsed
  there (using a different set of TCA_ enum values, iow. TCA_ACT_COOKIE
  then "clashes" with some other value). This lead to the following three
  example commands resulting in errors (sometimes followed by more traces
  and hangups some time later (although the hangups happened seconds or
  sometimes minutes later, sometimes not at all - results differed between
  different kernel versions (linux git-master vs ubuntu's mainline 4.11
  rc6 vs. pve 4.10.5 (based off ubuntu's zesty kernel where the commit is
  cherry-picked)...))):

   # ip link add ve0 type veth peer name ve0b
   # tc qdisc add dev ve0 handle : ingress
   # tc filter add dev ve0 parent : prio 50 basic police rate 1000bps burst 
1000b drop

  The 3rd command would sometimes succeed, sometimes error with:

   RTNETLINK answers: Invalid argument
   We have an error talking to the kernel

  and sometimes error with:

   RTNETLINK answers: Cannot allocate memory
   We have an error talking to the kernel

  In the latter case I assume `cklen` became negative, which passes the
  TC_COOKIE_MAX_SIZE check since it is signed but becomes unsigned later
  in kmemdup() (see the crash dump below)

  When the `tc filter add` command fails a backtrace shows up in dmesg,
  added below.

  I'm not sure why the TC_ACT_COOKIE code was added to tcf_action_init_1
  where it is now. It makes me think that it's supposed to be available
  universally, but the `name == NULL` check for how nla is used or passed
  to ->init() shows that the there are various different TC_ACT_* enums in
  use at this point, hence the 'RFC' part of the patches, I'm not that
  familiar with the code yet.

  Backtrace when running `tc filter add`:

  Apr 12 11:31:38 testmachine kernel: [ cut here ]
  Apr 12 11:31:38 testmachine kernel: WARNING: CPU: 7 PID: 16596 at 
mm/page_alloc.c:3541 __alloc_pages_slowpath+0x9fe/0xba0
  Apr 12 11:31:38 testmachine kernel: Modules linked in: act_police 
cls_basic sch_ingress veth nfsv3 nfs_acl nfs lockd grace ip6t_REJECT 
nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables 
xt_mac ipt_REJECT nf_reject_ipv4 xt_physdev xt_comment nf_conntrack_ipv4 
nf_defrag_ipv4 xt_tcpudp xt_mark xt_set xt_addrtype xt_multiport xt_conntrack 
nf_conntrack ip_set_hash_net ip_set arc4 md4 nls_utf8 cifs ccm fscache ipta
  Apr 12 11:31:38 testmachine kernel:  snd_hda_codec_realtek 
snd_hda_codec_generic aesni_intel aes_x86_64 crypto_simd drm_kms_helper 
glue_helper cryptd drm snd_hda_intel intel_cstate snd_hda_codec i2c_algo_bit 
fb_sys_fops snd_hda_core joydev syscopyarea snd_hwdep sysfillrect input_leds 
sysimgblt intel_rapl_perf snd_pcm snd_timer snd pcspkr soundcore mei_me lpc_ich 
mei shpchp tpm_infineon mac_hid wmi acpi_pad video vhost_net vhost macv
  Apr 12 11:31:38 testmachine kernel: CPU: 7 PID: 16596 Comm: tc Tainted: P 
  O4.10.5-1-pve #1
  Apr 12 11:31:38 testmachine kernel: Hardware name: ASUS All Series/Z97-A, 
BIOS 2801 11/11/2015
  Apr 12 11:31:38 testmachine kernel: Call Trace:
  Apr 12 11:31:38 testmachine kernel:  dump_sta

[Kernel-packages] [Bug 1684731] Re: zfs-share.service: Failed at step EXEC spawning /usr/bin/rm: No such file or directory

[Fabian Grünbichler]

Also tracked in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842237
, where it was prematurely closed.

** Bug watch added: Debian Bug tracker #842237
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842237

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

Title:
  zfs-share.service: Failed at step EXEC spawning /usr/bin/rm: No such
  file or directory

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  wrong `rm` path on /lib/systemd/system/zfs-share.service

  ExecStartPre=-/usr/bin/rm -f /etc/dfs/sharetab

  there is no file such /usr/bin/rm

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

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

[Kernel-packages] [Bug 1682368] Re: refcount underflow / kernel NULL dereference after attempting to add basic tc filter

[Fabian Grünbichler]

2017-7979 was assigned (http://cve.mitre.org/cgi-
bin/cvename.cgi?name=CVE-2017-7979), but is not yet known to LP it
seems..

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-7979

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

Title:
  refcount underflow / kernel NULL dereference after attempting to add
  basic tc filter

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

Bug description:
  == SRU Justification ==

  Impact: adding a tc filter sometimes fails, potentially followed by
  kernel hangs and kernel NULL pointer dereference

  Fix: proposed upstream by Wolfgang Bumiller [1,2]

  Regression Potential: Since nobody else noticed this issue in 4.11 >=
  rc1 or Ubuntu 4.10 >= 15.17, and the fix only touches the broken code,
  the regression potential should be minimal ;)

  1: http://marc.info/?l=linux-netdev&m=149200746116365
  2: http://marc.info/?l=linux-netdev&m=149200742616349

  ---

  Commit 1045ba77a which was backported for #1674087 in
  fc0cef7a8ec1e63ee3405f642983dd86e04ab6cc (first released with
  Ubuntu-4.10.0-15.17) introduces the problematic code. Note that while
  the traces below were generated using a custom patched kernel, the
  same issue is reproducible using Ubuntu Zesty's 4.10.0-15.17 (and
  later) kernels.

  The full cover letter of the proposed fix by my colleague Wolfgang
  Bumiller follows:

  Commit 1045ba77a ("net sched actions: Add support for user cookies")
  added code to net/sched/act_api.c's tcf_action_init_1 using the `tb`
  nlattr array unconditionally, while it was otherwise used as well as
  initialized only when `name == NULL`:

if (name == NULL) {
err = nla_parse_nested(tb, TCA_ACT_MAX, nla, NULL);

  In the other case `nla` is instead passed over to ->init to be parsed
  there (using a different set of TCA_ enum values, iow. TCA_ACT_COOKIE
  then "clashes" with some other value). This lead to the following three
  example commands resulting in errors (sometimes followed by more traces
  and hangups some time later (although the hangups happened seconds or
  sometimes minutes later, sometimes not at all - results differed between
  different kernel versions (linux git-master vs ubuntu's mainline 4.11
  rc6 vs. pve 4.10.5 (based off ubuntu's zesty kernel where the commit is
  cherry-picked)...))):

   # ip link add ve0 type veth peer name ve0b
   # tc qdisc add dev ve0 handle : ingress
   # tc filter add dev ve0 parent : prio 50 basic police rate 1000bps burst 
1000b drop

  The 3rd command would sometimes succeed, sometimes error with:

   RTNETLINK answers: Invalid argument
   We have an error talking to the kernel

  and sometimes error with:

   RTNETLINK answers: Cannot allocate memory
   We have an error talking to the kernel

  In the latter case I assume `cklen` became negative, which passes the
  TC_COOKIE_MAX_SIZE check since it is signed but becomes unsigned later
  in kmemdup() (see the crash dump below)

  When the `tc filter add` command fails a backtrace shows up in dmesg,
  added below.

  I'm not sure why the TC_ACT_COOKIE code was added to tcf_action_init_1
  where it is now. It makes me think that it's supposed to be available
  universally, but the `name == NULL` check for how nla is used or passed
  to ->init() shows that the there are various different TC_ACT_* enums in
  use at this point, hence the 'RFC' part of the patches, I'm not that
  familiar with the code yet.

  Backtrace when running `tc filter add`:

  Apr 12 11:31:38 testmachine kernel: [ cut here ]
  Apr 12 11:31:38 testmachine kernel: WARNING: CPU: 7 PID: 16596 at 
mm/page_alloc.c:3541 __alloc_pages_slowpath+0x9fe/0xba0
  Apr 12 11:31:38 testmachine kernel: Modules linked in: act_police 
cls_basic sch_ingress veth nfsv3 nfs_acl nfs lockd grace ip6t_REJECT 
nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables 
xt_mac ipt_REJECT nf_reject_ipv4 xt_physdev xt_comment nf_conntrack_ipv4 
nf_defrag_ipv4 xt_tcpudp xt_mark xt_set xt_addrtype xt_multiport xt_conntrack 
nf_conntrack ip_set_hash_net ip_set arc4 md4 nls_utf8 cifs ccm fscache ipta
  Apr 12 11:31:38 testmachine kernel:  snd_hda_codec_realtek 
snd_hda_codec_generic aesni_intel aes_x86_64 crypto_simd drm_kms_helper 
glue_helper cryptd drm snd_hda_intel intel_cstate snd_hda_codec i2c_algo_bit 
fb_sys_fops snd_hda_core joydev syscopyarea snd_hwdep sysfillrect input_leds 
sysimgblt intel_rapl_perf snd_pcm snd_timer snd pcspkr soundcore mei_me lpc_ich 
mei shpchp tpm_infineon mac_hid wmi acpi_pad video vhost_net vhost macv
  Apr 12 11:31:38 testmachine kernel: CPU: 7 PID: 16596 Comm: tc Tainted: P 
  O4.10.5-1-pve #1
  Apr 12 11:31:38 testmachine kernel: Hardware name: ASUS All Series/Z97-A, 
BIOS 2801 11/11/2015
  Apr 12 1

[Kernel-packages] [Bug 1682368] Re: refcount underflow / kernel NULL dereference after attempting to add basic tc filter

[Fabian Grünbichler]

CVE requested, will include once I get a reply.

Note that Canonical is listed as CNA for "Ubuntu/Linux issues" at
http://cve.mitre.org/cve/cna.html - maybe that list needs an update
then?

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

Title:
  refcount underflow / kernel NULL dereference after attempting to add
  basic tc filter

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

Bug description:
  == SRU Justification ==

  Impact: adding a tc filter sometimes fails, potentially followed by
  kernel hangs and kernel NULL pointer dereference

  Fix: proposed upstream by Wolfgang Bumiller [1,2]

  Regression Potential: Since nobody else noticed this issue in 4.11 >=
  rc1 or Ubuntu 4.10 >= 15.17, and the fix only touches the broken code,
  the regression potential should be minimal ;)

  1: http://marc.info/?l=linux-netdev&m=149200746116365
  2: http://marc.info/?l=linux-netdev&m=149200742616349

  ---

  Commit 1045ba77a which was backported for #1674087 in
  fc0cef7a8ec1e63ee3405f642983dd86e04ab6cc (first released with
  Ubuntu-4.10.0-15.17) introduces the problematic code. Note that while
  the traces below were generated using a custom patched kernel, the
  same issue is reproducible using Ubuntu Zesty's 4.10.0-15.17 (and
  later) kernels.

  The full cover letter of the proposed fix by my colleague Wolfgang
  Bumiller follows:

  Commit 1045ba77a ("net sched actions: Add support for user cookies")
  added code to net/sched/act_api.c's tcf_action_init_1 using the `tb`
  nlattr array unconditionally, while it was otherwise used as well as
  initialized only when `name == NULL`:

if (name == NULL) {
err = nla_parse_nested(tb, TCA_ACT_MAX, nla, NULL);

  In the other case `nla` is instead passed over to ->init to be parsed
  there (using a different set of TCA_ enum values, iow. TCA_ACT_COOKIE
  then "clashes" with some other value). This lead to the following three
  example commands resulting in errors (sometimes followed by more traces
  and hangups some time later (although the hangups happened seconds or
  sometimes minutes later, sometimes not at all - results differed between
  different kernel versions (linux git-master vs ubuntu's mainline 4.11
  rc6 vs. pve 4.10.5 (based off ubuntu's zesty kernel where the commit is
  cherry-picked)...))):

   # ip link add ve0 type veth peer name ve0b
   # tc qdisc add dev ve0 handle : ingress
   # tc filter add dev ve0 parent : prio 50 basic police rate 1000bps burst 
1000b drop

  The 3rd command would sometimes succeed, sometimes error with:

   RTNETLINK answers: Invalid argument
   We have an error talking to the kernel

  and sometimes error with:

   RTNETLINK answers: Cannot allocate memory
   We have an error talking to the kernel

  In the latter case I assume `cklen` became negative, which passes the
  TC_COOKIE_MAX_SIZE check since it is signed but becomes unsigned later
  in kmemdup() (see the crash dump below)

  When the `tc filter add` command fails a backtrace shows up in dmesg,
  added below.

  I'm not sure why the TC_ACT_COOKIE code was added to tcf_action_init_1
  where it is now. It makes me think that it's supposed to be available
  universally, but the `name == NULL` check for how nla is used or passed
  to ->init() shows that the there are various different TC_ACT_* enums in
  use at this point, hence the 'RFC' part of the patches, I'm not that
  familiar with the code yet.

  Backtrace when running `tc filter add`:

  Apr 12 11:31:38 testmachine kernel: [ cut here ]
  Apr 12 11:31:38 testmachine kernel: WARNING: CPU: 7 PID: 16596 at 
mm/page_alloc.c:3541 __alloc_pages_slowpath+0x9fe/0xba0
  Apr 12 11:31:38 testmachine kernel: Modules linked in: act_police 
cls_basic sch_ingress veth nfsv3 nfs_acl nfs lockd grace ip6t_REJECT 
nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables 
xt_mac ipt_REJECT nf_reject_ipv4 xt_physdev xt_comment nf_conntrack_ipv4 
nf_defrag_ipv4 xt_tcpudp xt_mark xt_set xt_addrtype xt_multiport xt_conntrack 
nf_conntrack ip_set_hash_net ip_set arc4 md4 nls_utf8 cifs ccm fscache ipta
  Apr 12 11:31:38 testmachine kernel:  snd_hda_codec_realtek 
snd_hda_codec_generic aesni_intel aes_x86_64 crypto_simd drm_kms_helper 
glue_helper cryptd drm snd_hda_intel intel_cstate snd_hda_codec i2c_algo_bit 
fb_sys_fops snd_hda_core joydev syscopyarea snd_hwdep sysfillrect input_leds 
sysimgblt intel_rapl_perf snd_pcm snd_timer snd pcspkr soundcore mei_me lpc_ich 
mei shpchp tpm_infineon mac_hid wmi acpi_pad video vhost_net vhost macv
  Apr 12 11:31:38 testmachine kernel: CPU: 7 PID: 16596 Comm: tc Tainted: P 
  O4.10.5-1-pve #1
  Apr 12 11:31:38 testmachine kernel: Hardware name: ASUS All Series/Z97-A, 
BIOS 2801 11/11/2015
  Apr 12 11:31:38 test

[Kernel-packages] [Bug 1682368] Re: refcount underflow / kernel NULL dereference after attempting to add basic tc filter

[Fabian Grünbichler]

@seth-arnold: no, not yet. shall we request one from Mitre or does
Ubuntu/Canonical have a pool to assign one?

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

Title:
  refcount underflow / kernel NULL dereference after attempting to add
  basic tc filter

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

Bug description:
  == SRU Justification ==

  Impact: adding a tc filter sometimes fails, potentially followed by
  kernel hangs and kernel NULL pointer dereference

  Fix: proposed upstream by Wolfgang Bumiller [1,2]

  Regression Potential: Since nobody else noticed this issue in 4.11 >=
  rc1 or Ubuntu 4.10 >= 15.17, and the fix only touches the broken code,
  the regression potential should be minimal ;)

  1: http://marc.info/?l=linux-netdev&m=149200746116365
  2: http://marc.info/?l=linux-netdev&m=149200742616349

  ---

  Commit 1045ba77a which was backported for #1674087 in
  fc0cef7a8ec1e63ee3405f642983dd86e04ab6cc (first released with
  Ubuntu-4.10.0-15.17) introduces the problematic code. Note that while
  the traces below were generated using a custom patched kernel, the
  same issue is reproducible using Ubuntu Zesty's 4.10.0-15.17 (and
  later) kernels.

  The full cover letter of the proposed fix by my colleague Wolfgang
  Bumiller follows:

  Commit 1045ba77a ("net sched actions: Add support for user cookies")
  added code to net/sched/act_api.c's tcf_action_init_1 using the `tb`
  nlattr array unconditionally, while it was otherwise used as well as
  initialized only when `name == NULL`:

if (name == NULL) {
err = nla_parse_nested(tb, TCA_ACT_MAX, nla, NULL);

  In the other case `nla` is instead passed over to ->init to be parsed
  there (using a different set of TCA_ enum values, iow. TCA_ACT_COOKIE
  then "clashes" with some other value). This lead to the following three
  example commands resulting in errors (sometimes followed by more traces
  and hangups some time later (although the hangups happened seconds or
  sometimes minutes later, sometimes not at all - results differed between
  different kernel versions (linux git-master vs ubuntu's mainline 4.11
  rc6 vs. pve 4.10.5 (based off ubuntu's zesty kernel where the commit is
  cherry-picked)...))):

   # ip link add ve0 type veth peer name ve0b
   # tc qdisc add dev ve0 handle : ingress
   # tc filter add dev ve0 parent : prio 50 basic police rate 1000bps burst 
1000b drop

  The 3rd command would sometimes succeed, sometimes error with:

   RTNETLINK answers: Invalid argument
   We have an error talking to the kernel

  and sometimes error with:

   RTNETLINK answers: Cannot allocate memory
   We have an error talking to the kernel

  In the latter case I assume `cklen` became negative, which passes the
  TC_COOKIE_MAX_SIZE check since it is signed but becomes unsigned later
  in kmemdup() (see the crash dump below)

  When the `tc filter add` command fails a backtrace shows up in dmesg,
  added below.

  I'm not sure why the TC_ACT_COOKIE code was added to tcf_action_init_1
  where it is now. It makes me think that it's supposed to be available
  universally, but the `name == NULL` check for how nla is used or passed
  to ->init() shows that the there are various different TC_ACT_* enums in
  use at this point, hence the 'RFC' part of the patches, I'm not that
  familiar with the code yet.

  Backtrace when running `tc filter add`:

  Apr 12 11:31:38 testmachine kernel: [ cut here ]
  Apr 12 11:31:38 testmachine kernel: WARNING: CPU: 7 PID: 16596 at 
mm/page_alloc.c:3541 __alloc_pages_slowpath+0x9fe/0xba0
  Apr 12 11:31:38 testmachine kernel: Modules linked in: act_police 
cls_basic sch_ingress veth nfsv3 nfs_acl nfs lockd grace ip6t_REJECT 
nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables 
xt_mac ipt_REJECT nf_reject_ipv4 xt_physdev xt_comment nf_conntrack_ipv4 
nf_defrag_ipv4 xt_tcpudp xt_mark xt_set xt_addrtype xt_multiport xt_conntrack 
nf_conntrack ip_set_hash_net ip_set arc4 md4 nls_utf8 cifs ccm fscache ipta
  Apr 12 11:31:38 testmachine kernel:  snd_hda_codec_realtek 
snd_hda_codec_generic aesni_intel aes_x86_64 crypto_simd drm_kms_helper 
glue_helper cryptd drm snd_hda_intel intel_cstate snd_hda_codec i2c_algo_bit 
fb_sys_fops snd_hda_core joydev syscopyarea snd_hwdep sysfillrect input_leds 
sysimgblt intel_rapl_perf snd_pcm snd_timer snd pcspkr soundcore mei_me lpc_ich 
mei shpchp tpm_infineon mac_hid wmi acpi_pad video vhost_net vhost macv
  Apr 12 11:31:38 testmachine kernel: CPU: 7 PID: 16596 Comm: tc Tainted: P 
  O4.10.5-1-pve #1
  Apr 12 11:31:38 testmachine kernel: Hardware name: ASUS All Series/Z97-A, 
BIOS 2801 11/11/2015
  Apr 12 11:31:38 testmachine kernel: Call Trace:
  Apr 12 11:31:38 testmachine kernel:  dump_st

[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

[Fabian Tröster]

When is the fix out of 'proposed'? I don't want 'proposed' updates. If
I'd want that I'd install 16.10

What is the point of an LTS if these bugs can't be fixed?!

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

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
  Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
  Feb 21 07:17:03 orin kernel: [  190.625241] rtl8192cu: Board Type 0
  Feb 21 07:17:03 orin kernel: [  190.626355] rtl_usb: rx_max_size 15360, 
rx_urb_num 8, in_ep 1
  Feb 21 07:17:03 orin kernel: [  190.626408] rtl8192cu: Loading firmware 
rtlwifi/rtl8192cufw_TMSC.bin
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7698] (wlan0): 
using nl80211 for WiFi device control
  Feb 21 07:17:03 orin kernel: [  190.636625] ieee80211 phy0: Selected rate 
control algorithm 'rtl_rc'
  Feb 21 07:17:03 orin kernel: [  190.637211] usbcore: registered new interface 
driver rtl8192cu
  Feb 21 07:17:03 orin systemd[1]: Starting Load/Save RF Kill Switch Status...
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7780] device 
(wlan0): driver supports Access Point (AP) mode
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7798] manager: 
(wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/4)
  Feb

[Kernel-packages] [Bug 1682368] Re: refcount underflow / kernel NULL dereference after attempting to add basic tc filter

[Fabian Grünbichler]

** Attachment added: "journal-1"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682368/+attachment/4861894/+files/journal-1

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

Title:
  refcount underflow / kernel NULL dereference after attempting to add
  basic tc filter

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

Bug description:
  == SRU Justification ==

  Impact: adding a tc filter sometimes fails, potentially followed by
  kernel hangs and kernel NULL pointer dereference

  Fix: proposed upstream by Wolfgang Bumiller [1,2]

  Regression Potential: Since nobody else noticed this issue in 4.11 >=
  rc1 or Ubuntu 4.10 >= 15.17, and the fix only touches the broken code,
  the regression potential should be minimal ;)

  1: http://marc.info/?l=linux-netdev&m=149200746116365
  2: http://marc.info/?l=linux-netdev&m=149200742616349

  ---

  Commit 1045ba77a which was backported for #1674087 in
  fc0cef7a8ec1e63ee3405f642983dd86e04ab6cc (first released with
  Ubuntu-4.10.0-15.17) introduces the problematic code. Note that while
  the traces below were generated using a custom patched kernel, the
  same issue is reproducible using Ubuntu Zesty's 4.10.0-15.17 (and
  later) kernels.

  The full cover letter of the proposed fix by my colleague Wolfgang
  Bumiller follows:

  Commit 1045ba77a ("net sched actions: Add support for user cookies")
  added code to net/sched/act_api.c's tcf_action_init_1 using the `tb`
  nlattr array unconditionally, while it was otherwise used as well as
  initialized only when `name == NULL`:

if (name == NULL) {
err = nla_parse_nested(tb, TCA_ACT_MAX, nla, NULL);

  In the other case `nla` is instead passed over to ->init to be parsed
  there (using a different set of TCA_ enum values, iow. TCA_ACT_COOKIE
  then "clashes" with some other value). This lead to the following three
  example commands resulting in errors (sometimes followed by more traces
  and hangups some time later (although the hangups happened seconds or
  sometimes minutes later, sometimes not at all - results differed between
  different kernel versions (linux git-master vs ubuntu's mainline 4.11
  rc6 vs. pve 4.10.5 (based off ubuntu's zesty kernel where the commit is
  cherry-picked)...))):

   # ip link add ve0 type veth peer name ve0b
   # tc qdisc add dev ve0 handle : ingress
   # tc filter add dev ve0 parent : prio 50 basic police rate 1000bps burst 
1000b drop

  The 3rd command would sometimes succeed, sometimes error with:

   RTNETLINK answers: Invalid argument
   We have an error talking to the kernel

  and sometimes error with:

   RTNETLINK answers: Cannot allocate memory
   We have an error talking to the kernel

  In the latter case I assume `cklen` became negative, which passes the
  TC_COOKIE_MAX_SIZE check since it is signed but becomes unsigned later
  in kmemdup() (see the crash dump below)

  When the `tc filter add` command fails a backtrace shows up in dmesg,
  added below.

  I'm not sure why the TC_ACT_COOKIE code was added to tcf_action_init_1
  where it is now. It makes me think that it's supposed to be available
  universally, but the `name == NULL` check for how nla is used or passed
  to ->init() shows that the there are various different TC_ACT_* enums in
  use at this point, hence the 'RFC' part of the patches, I'm not that
  familiar with the code yet.

  Backtrace when running `tc filter add`:

  Apr 12 11:31:38 testmachine kernel: [ cut here ]
  Apr 12 11:31:38 testmachine kernel: WARNING: CPU: 7 PID: 16596 at 
mm/page_alloc.c:3541 __alloc_pages_slowpath+0x9fe/0xba0
  Apr 12 11:31:38 testmachine kernel: Modules linked in: act_police 
cls_basic sch_ingress veth nfsv3 nfs_acl nfs lockd grace ip6t_REJECT 
nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables 
xt_mac ipt_REJECT nf_reject_ipv4 xt_physdev xt_comment nf_conntrack_ipv4 
nf_defrag_ipv4 xt_tcpudp xt_mark xt_set xt_addrtype xt_multiport xt_conntrack 
nf_conntrack ip_set_hash_net ip_set arc4 md4 nls_utf8 cifs ccm fscache ipta
  Apr 12 11:31:38 testmachine kernel:  snd_hda_codec_realtek 
snd_hda_codec_generic aesni_intel aes_x86_64 crypto_simd drm_kms_helper 
glue_helper cryptd drm snd_hda_intel intel_cstate snd_hda_codec i2c_algo_bit 
fb_sys_fops snd_hda_core joydev syscopyarea snd_hwdep sysfillrect input_leds 
sysimgblt intel_rapl_perf snd_pcm snd_timer snd pcspkr soundcore mei_me lpc_ich 
mei shpchp tpm_infineon mac_hid wmi acpi_pad video vhost_net vhost macv
  Apr 12 11:31:38 testmachine kernel: CPU: 7 PID: 16596 Comm: tc Tainted: P 
  O4.10.5-1-pve #1
  Apr 12 11:31:38 testmachine kernel: Hardware name: ASUS All Series/Z97-A, 
BIOS 2801 11/11/2015
  Apr 12 11:31:38 testmachine kernel: Call Trace:
  Apr 12 11:31:38 test

[Kernel-packages] [Bug 1682368] Re: refcount underflow / kernel NULL dereference after attempting to add basic tc filter

[Fabian Grünbichler]

** Attachment added: "transcript"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682368/+attachment/4861893/+files/transcript

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

Title:
  refcount underflow / kernel NULL dereference after attempting to add
  basic tc filter

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

Bug description:
  == SRU Justification ==

  Impact: adding a tc filter sometimes fails, potentially followed by
  kernel hangs and kernel NULL pointer dereference

  Fix: proposed upstream by Wolfgang Bumiller [1,2]

  Regression Potential: Since nobody else noticed this issue in 4.11 >=
  rc1 or Ubuntu 4.10 >= 15.17, and the fix only touches the broken code,
  the regression potential should be minimal ;)

  1: http://marc.info/?l=linux-netdev&m=149200746116365
  2: http://marc.info/?l=linux-netdev&m=149200742616349

  ---

  Commit 1045ba77a which was backported for #1674087 in
  fc0cef7a8ec1e63ee3405f642983dd86e04ab6cc (first released with
  Ubuntu-4.10.0-15.17) introduces the problematic code. Note that while
  the traces below were generated using a custom patched kernel, the
  same issue is reproducible using Ubuntu Zesty's 4.10.0-15.17 (and
  later) kernels.

  The full cover letter of the proposed fix by my colleague Wolfgang
  Bumiller follows:

  Commit 1045ba77a ("net sched actions: Add support for user cookies")
  added code to net/sched/act_api.c's tcf_action_init_1 using the `tb`
  nlattr array unconditionally, while it was otherwise used as well as
  initialized only when `name == NULL`:

if (name == NULL) {
err = nla_parse_nested(tb, TCA_ACT_MAX, nla, NULL);

  In the other case `nla` is instead passed over to ->init to be parsed
  there (using a different set of TCA_ enum values, iow. TCA_ACT_COOKIE
  then "clashes" with some other value). This lead to the following three
  example commands resulting in errors (sometimes followed by more traces
  and hangups some time later (although the hangups happened seconds or
  sometimes minutes later, sometimes not at all - results differed between
  different kernel versions (linux git-master vs ubuntu's mainline 4.11
  rc6 vs. pve 4.10.5 (based off ubuntu's zesty kernel where the commit is
  cherry-picked)...))):

   # ip link add ve0 type veth peer name ve0b
   # tc qdisc add dev ve0 handle : ingress
   # tc filter add dev ve0 parent : prio 50 basic police rate 1000bps burst 
1000b drop

  The 3rd command would sometimes succeed, sometimes error with:

   RTNETLINK answers: Invalid argument
   We have an error talking to the kernel

  and sometimes error with:

   RTNETLINK answers: Cannot allocate memory
   We have an error talking to the kernel

  In the latter case I assume `cklen` became negative, which passes the
  TC_COOKIE_MAX_SIZE check since it is signed but becomes unsigned later
  in kmemdup() (see the crash dump below)

  When the `tc filter add` command fails a backtrace shows up in dmesg,
  added below.

  I'm not sure why the TC_ACT_COOKIE code was added to tcf_action_init_1
  where it is now. It makes me think that it's supposed to be available
  universally, but the `name == NULL` check for how nla is used or passed
  to ->init() shows that the there are various different TC_ACT_* enums in
  use at this point, hence the 'RFC' part of the patches, I'm not that
  familiar with the code yet.

  Backtrace when running `tc filter add`:

  Apr 12 11:31:38 testmachine kernel: [ cut here ]
  Apr 12 11:31:38 testmachine kernel: WARNING: CPU: 7 PID: 16596 at 
mm/page_alloc.c:3541 __alloc_pages_slowpath+0x9fe/0xba0
  Apr 12 11:31:38 testmachine kernel: Modules linked in: act_police 
cls_basic sch_ingress veth nfsv3 nfs_acl nfs lockd grace ip6t_REJECT 
nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables 
xt_mac ipt_REJECT nf_reject_ipv4 xt_physdev xt_comment nf_conntrack_ipv4 
nf_defrag_ipv4 xt_tcpudp xt_mark xt_set xt_addrtype xt_multiport xt_conntrack 
nf_conntrack ip_set_hash_net ip_set arc4 md4 nls_utf8 cifs ccm fscache ipta
  Apr 12 11:31:38 testmachine kernel:  snd_hda_codec_realtek 
snd_hda_codec_generic aesni_intel aes_x86_64 crypto_simd drm_kms_helper 
glue_helper cryptd drm snd_hda_intel intel_cstate snd_hda_codec i2c_algo_bit 
fb_sys_fops snd_hda_core joydev syscopyarea snd_hwdep sysfillrect input_leds 
sysimgblt intel_rapl_perf snd_pcm snd_timer snd pcspkr soundcore mei_me lpc_ich 
mei shpchp tpm_infineon mac_hid wmi acpi_pad video vhost_net vhost macv
  Apr 12 11:31:38 testmachine kernel: CPU: 7 PID: 16596 Comm: tc Tainted: P 
  O4.10.5-1-pve #1
  Apr 12 11:31:38 testmachine kernel: Hardware name: ASUS All Series/Z97-A, 
BIOS 2801 11/11/2015
  Apr 12 11:31:38 testmachine kernel: Call Trace:
  Apr 12 11:31:38 te

[Kernel-packages] [Bug 1682368] Re: refcount underflow / kernel NULL dereference after attempting to add basic tc filter

[Fabian Grünbichler]

** Attachment added: "journal-2"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682368/+attachment/4861895/+files/journal-2

** Information type changed from Public to Public Security

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

Title:
  refcount underflow / kernel NULL dereference after attempting to add
  basic tc filter

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

Bug description:
  == SRU Justification ==

  Impact: adding a tc filter sometimes fails, potentially followed by
  kernel hangs and kernel NULL pointer dereference

  Fix: proposed upstream by Wolfgang Bumiller [1,2]

  Regression Potential: Since nobody else noticed this issue in 4.11 >=
  rc1 or Ubuntu 4.10 >= 15.17, and the fix only touches the broken code,
  the regression potential should be minimal ;)

  1: http://marc.info/?l=linux-netdev&m=149200746116365
  2: http://marc.info/?l=linux-netdev&m=149200742616349

  ---

  Commit 1045ba77a which was backported for #1674087 in
  fc0cef7a8ec1e63ee3405f642983dd86e04ab6cc (first released with
  Ubuntu-4.10.0-15.17) introduces the problematic code. Note that while
  the traces below were generated using a custom patched kernel, the
  same issue is reproducible using Ubuntu Zesty's 4.10.0-15.17 (and
  later) kernels.

  The full cover letter of the proposed fix by my colleague Wolfgang
  Bumiller follows:

  Commit 1045ba77a ("net sched actions: Add support for user cookies")
  added code to net/sched/act_api.c's tcf_action_init_1 using the `tb`
  nlattr array unconditionally, while it was otherwise used as well as
  initialized only when `name == NULL`:

if (name == NULL) {
err = nla_parse_nested(tb, TCA_ACT_MAX, nla, NULL);

  In the other case `nla` is instead passed over to ->init to be parsed
  there (using a different set of TCA_ enum values, iow. TCA_ACT_COOKIE
  then "clashes" with some other value). This lead to the following three
  example commands resulting in errors (sometimes followed by more traces
  and hangups some time later (although the hangups happened seconds or
  sometimes minutes later, sometimes not at all - results differed between
  different kernel versions (linux git-master vs ubuntu's mainline 4.11
  rc6 vs. pve 4.10.5 (based off ubuntu's zesty kernel where the commit is
  cherry-picked)...))):

   # ip link add ve0 type veth peer name ve0b
   # tc qdisc add dev ve0 handle : ingress
   # tc filter add dev ve0 parent : prio 50 basic police rate 1000bps burst 
1000b drop

  The 3rd command would sometimes succeed, sometimes error with:

   RTNETLINK answers: Invalid argument
   We have an error talking to the kernel

  and sometimes error with:

   RTNETLINK answers: Cannot allocate memory
   We have an error talking to the kernel

  In the latter case I assume `cklen` became negative, which passes the
  TC_COOKIE_MAX_SIZE check since it is signed but becomes unsigned later
  in kmemdup() (see the crash dump below)

  When the `tc filter add` command fails a backtrace shows up in dmesg,
  added below.

  I'm not sure why the TC_ACT_COOKIE code was added to tcf_action_init_1
  where it is now. It makes me think that it's supposed to be available
  universally, but the `name == NULL` check for how nla is used or passed
  to ->init() shows that the there are various different TC_ACT_* enums in
  use at this point, hence the 'RFC' part of the patches, I'm not that
  familiar with the code yet.

  Backtrace when running `tc filter add`:

  Apr 12 11:31:38 testmachine kernel: [ cut here ]
  Apr 12 11:31:38 testmachine kernel: WARNING: CPU: 7 PID: 16596 at 
mm/page_alloc.c:3541 __alloc_pages_slowpath+0x9fe/0xba0
  Apr 12 11:31:38 testmachine kernel: Modules linked in: act_police 
cls_basic sch_ingress veth nfsv3 nfs_acl nfs lockd grace ip6t_REJECT 
nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables 
xt_mac ipt_REJECT nf_reject_ipv4 xt_physdev xt_comment nf_conntrack_ipv4 
nf_defrag_ipv4 xt_tcpudp xt_mark xt_set xt_addrtype xt_multiport xt_conntrack 
nf_conntrack ip_set_hash_net ip_set arc4 md4 nls_utf8 cifs ccm fscache ipta
  Apr 12 11:31:38 testmachine kernel:  snd_hda_codec_realtek 
snd_hda_codec_generic aesni_intel aes_x86_64 crypto_simd drm_kms_helper 
glue_helper cryptd drm snd_hda_intel intel_cstate snd_hda_codec i2c_algo_bit 
fb_sys_fops snd_hda_core joydev syscopyarea snd_hwdep sysfillrect input_leds 
sysimgblt intel_rapl_perf snd_pcm snd_timer snd pcspkr soundcore mei_me lpc_ich 
mei shpchp tpm_infineon mac_hid wmi acpi_pad video vhost_net vhost macv
  Apr 12 11:31:38 testmachine kernel: CPU: 7 PID: 16596 Comm: tc Tainted: P 
  O4.10.5-1-pve #1
  Apr 12 11:31:38 testmachine kernel: Hardware name: ASUS All Series/Z97-A, 
BIOS 2801 11/11/2015
  Apr 12 11:31:3

[Kernel-packages] [Bug 1682368] Re: refcount underflow / kernel NULL dereference after attempting to add basic tc filter

[Fabian Grünbichler]

this is easily reproducible and triggers at least a DoS on a freshly
installed 17.04 system, from within an unprivileged LXD container. see
the transcript for the executed commands, and journal-1 and journal-2
for the first and second kernel traces (caused by the second to last and
last "tc" commands executed in the container).

the end result is a complete hang/crash of the system.

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

Title:
  refcount underflow / kernel NULL dereference after attempting to add
  basic tc filter

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

Bug description:
  == SRU Justification ==

  Impact: adding a tc filter sometimes fails, potentially followed by
  kernel hangs and kernel NULL pointer dereference

  Fix: proposed upstream by Wolfgang Bumiller [1,2]

  Regression Potential: Since nobody else noticed this issue in 4.11 >=
  rc1 or Ubuntu 4.10 >= 15.17, and the fix only touches the broken code,
  the regression potential should be minimal ;)

  1: http://marc.info/?l=linux-netdev&m=149200746116365
  2: http://marc.info/?l=linux-netdev&m=149200742616349

  ---

  Commit 1045ba77a which was backported for #1674087 in
  fc0cef7a8ec1e63ee3405f642983dd86e04ab6cc (first released with
  Ubuntu-4.10.0-15.17) introduces the problematic code. Note that while
  the traces below were generated using a custom patched kernel, the
  same issue is reproducible using Ubuntu Zesty's 4.10.0-15.17 (and
  later) kernels.

  The full cover letter of the proposed fix by my colleague Wolfgang
  Bumiller follows:

  Commit 1045ba77a ("net sched actions: Add support for user cookies")
  added code to net/sched/act_api.c's tcf_action_init_1 using the `tb`
  nlattr array unconditionally, while it was otherwise used as well as
  initialized only when `name == NULL`:

if (name == NULL) {
err = nla_parse_nested(tb, TCA_ACT_MAX, nla, NULL);

  In the other case `nla` is instead passed over to ->init to be parsed
  there (using a different set of TCA_ enum values, iow. TCA_ACT_COOKIE
  then "clashes" with some other value). This lead to the following three
  example commands resulting in errors (sometimes followed by more traces
  and hangups some time later (although the hangups happened seconds or
  sometimes minutes later, sometimes not at all - results differed between
  different kernel versions (linux git-master vs ubuntu's mainline 4.11
  rc6 vs. pve 4.10.5 (based off ubuntu's zesty kernel where the commit is
  cherry-picked)...))):

   # ip link add ve0 type veth peer name ve0b
   # tc qdisc add dev ve0 handle : ingress
   # tc filter add dev ve0 parent : prio 50 basic police rate 1000bps burst 
1000b drop

  The 3rd command would sometimes succeed, sometimes error with:

   RTNETLINK answers: Invalid argument
   We have an error talking to the kernel

  and sometimes error with:

   RTNETLINK answers: Cannot allocate memory
   We have an error talking to the kernel

  In the latter case I assume `cklen` became negative, which passes the
  TC_COOKIE_MAX_SIZE check since it is signed but becomes unsigned later
  in kmemdup() (see the crash dump below)

  When the `tc filter add` command fails a backtrace shows up in dmesg,
  added below.

  I'm not sure why the TC_ACT_COOKIE code was added to tcf_action_init_1
  where it is now. It makes me think that it's supposed to be available
  universally, but the `name == NULL` check for how nla is used or passed
  to ->init() shows that the there are various different TC_ACT_* enums in
  use at this point, hence the 'RFC' part of the patches, I'm not that
  familiar with the code yet.

  Backtrace when running `tc filter add`:

  Apr 12 11:31:38 testmachine kernel: [ cut here ]
  Apr 12 11:31:38 testmachine kernel: WARNING: CPU: 7 PID: 16596 at 
mm/page_alloc.c:3541 __alloc_pages_slowpath+0x9fe/0xba0
  Apr 12 11:31:38 testmachine kernel: Modules linked in: act_police 
cls_basic sch_ingress veth nfsv3 nfs_acl nfs lockd grace ip6t_REJECT 
nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables 
xt_mac ipt_REJECT nf_reject_ipv4 xt_physdev xt_comment nf_conntrack_ipv4 
nf_defrag_ipv4 xt_tcpudp xt_mark xt_set xt_addrtype xt_multiport xt_conntrack 
nf_conntrack ip_set_hash_net ip_set arc4 md4 nls_utf8 cifs ccm fscache ipta
  Apr 12 11:31:38 testmachine kernel:  snd_hda_codec_realtek 
snd_hda_codec_generic aesni_intel aes_x86_64 crypto_simd drm_kms_helper 
glue_helper cryptd drm snd_hda_intel intel_cstate snd_hda_codec i2c_algo_bit 
fb_sys_fops snd_hda_core joydev syscopyarea snd_hwdep sysfillrect input_leds 
sysimgblt intel_rapl_perf snd_pcm snd_timer snd pcspkr soundcore mei_me lpc_ich 
mei shpchp tpm_infineon mac_hid wmi acpi_pad video vhost_net vhost macv
  Apr 12 11:31:38 testmachine kernel: C

[Kernel-packages] [Bug 1682368] Re: refcount underflow / kernel NULL dereference after attempting to add basic tc filter

[Fabian Grünbichler]

See https://bugzilla.proxmox.com/show_bug.cgi?id=1351 and
https://forum.proxmox.com/threads/proxmox-
ve-5-0-beta1-released.33731/page-4#post-167127 for downstream reports by
users.

** Bug watch added: bugzilla.proxmox.com/ #1351
   https://bugzilla.proxmox.com/show_bug.cgi?id=1351

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

Title:
  refcount underflow / kernel NULL dereference after attempting to add
  basic tc filter

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  == SRU Justification ==

  Impact: adding a tc filter sometimes fails, potentially followed by
  kernel hangs and kernel NULL pointer dereference

  Fix: proposed upstream by Wolfgang Bumiller [1,2]

  Regression Potential: Since nobody else noticed this issue in 4.11 >=
  rc1 or Ubuntu 4.10 >= 15.17, and the fix only touches the broken code,
  the regression potential should be minimal ;)

  1: http://marc.info/?l=linux-netdev&m=149200746116365
  2: http://marc.info/?l=linux-netdev&m=149200742616349

  ---

  Commit 1045ba77a which was backported for #1674087 in
  fc0cef7a8ec1e63ee3405f642983dd86e04ab6cc (first released with
  Ubuntu-4.10.0-15.17) introduces the problematic code. Note that while
  the traces below were generated using a custom patched kernel, the
  same issue is reproducible using Ubuntu Zesty's 4.10.0-15.17 (and
  later) kernels.

  The full cover letter of the proposed fix by my colleague Wolfgang
  Bumiller follows:

  Commit 1045ba77a ("net sched actions: Add support for user cookies")
  added code to net/sched/act_api.c's tcf_action_init_1 using the `tb`
  nlattr array unconditionally, while it was otherwise used as well as
  initialized only when `name == NULL`:

if (name == NULL) {
err = nla_parse_nested(tb, TCA_ACT_MAX, nla, NULL);

  In the other case `nla` is instead passed over to ->init to be parsed
  there (using a different set of TCA_ enum values, iow. TCA_ACT_COOKIE
  then "clashes" with some other value). This lead to the following three
  example commands resulting in errors (sometimes followed by more traces
  and hangups some time later (although the hangups happened seconds or
  sometimes minutes later, sometimes not at all - results differed between
  different kernel versions (linux git-master vs ubuntu's mainline 4.11
  rc6 vs. pve 4.10.5 (based off ubuntu's zesty kernel where the commit is
  cherry-picked)...))):

   # ip link add ve0 type veth peer name ve0b
   # tc qdisc add dev ve0 handle : ingress
   # tc filter add dev ve0 parent : prio 50 basic police rate 1000bps burst 
1000b drop

  The 3rd command would sometimes succeed, sometimes error with:

   RTNETLINK answers: Invalid argument
   We have an error talking to the kernel

  and sometimes error with:

   RTNETLINK answers: Cannot allocate memory
   We have an error talking to the kernel

  In the latter case I assume `cklen` became negative, which passes the
  TC_COOKIE_MAX_SIZE check since it is signed but becomes unsigned later
  in kmemdup() (see the crash dump below)

  When the `tc filter add` command fails a backtrace shows up in dmesg,
  added below.

  I'm not sure why the TC_ACT_COOKIE code was added to tcf_action_init_1
  where it is now. It makes me think that it's supposed to be available
  universally, but the `name == NULL` check for how nla is used or passed
  to ->init() shows that the there are various different TC_ACT_* enums in
  use at this point, hence the 'RFC' part of the patches, I'm not that
  familiar with the code yet.

  Backtrace when running `tc filter add`:

  Apr 12 11:31:38 testmachine kernel: [ cut here ]
  Apr 12 11:31:38 testmachine kernel: WARNING: CPU: 7 PID: 16596 at 
mm/page_alloc.c:3541 __alloc_pages_slowpath+0x9fe/0xba0
  Apr 12 11:31:38 testmachine kernel: Modules linked in: act_police 
cls_basic sch_ingress veth nfsv3 nfs_acl nfs lockd grace ip6t_REJECT 
nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables 
xt_mac ipt_REJECT nf_reject_ipv4 xt_physdev xt_comment nf_conntrack_ipv4 
nf_defrag_ipv4 xt_tcpudp xt_mark xt_set xt_addrtype xt_multiport xt_conntrack 
nf_conntrack ip_set_hash_net ip_set arc4 md4 nls_utf8 cifs ccm fscache ipta
  Apr 12 11:31:38 testmachine kernel:  snd_hda_codec_realtek 
snd_hda_codec_generic aesni_intel aes_x86_64 crypto_simd drm_kms_helper 
glue_helper cryptd drm snd_hda_intel intel_cstate snd_hda_codec i2c_algo_bit 
fb_sys_fops snd_hda_core joydev syscopyarea snd_hwdep sysfillrect input_leds 
sysimgblt intel_rapl_perf snd_pcm snd_timer snd pcspkr soundcore mei_me lpc_ich 
mei shpchp tpm_infineon mac_hid wmi acpi_pad video vhost_net vhost macv
  Apr 12 11:31:38 testmachine kernel: CPU: 7 PID: 16596 Comm: tc Tainted: P 
  O4.10.5-1-pve #1
  Apr 12 11:31:38 testmachine kernel: Hardware name: ASUS All Series/Z97-A, 
BIOS 2801 

[Kernel-packages] [Bug 1682368] Re: refcount underflow / kernel NULL dereference after attempting to add basic tc filter

[Fabian Grünbichler]

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

Title:
  refcount underflow / kernel NULL dereference after attempting to add
  basic tc filter

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  == SRU Justification ==

  Impact: adding a tc filter sometimes fails, potentially followed by
  kernel hangs and kernel NULL pointer dereference

  Fix: proposed upstream by Wolfgang Bumiller [1,2]

  Regression Potential: Since nobody else noticed this issue in 4.11 >=
  rc1 or Ubuntu 4.10 >= 15.17, and the fix only touches the broken code,
  the regression potential should be minimal ;)

  1: http://marc.info/?l=linux-netdev&m=149200746116365
  2: http://marc.info/?l=linux-netdev&m=149200742616349

  ---

  Commit 1045ba77a which was backported for #1674087 in
  fc0cef7a8ec1e63ee3405f642983dd86e04ab6cc (first released with
  Ubuntu-4.10.0-15.17) introduces the problematic code. Note that while
  the traces below were generated using a custom patched kernel, the
  same issue is reproducible using Ubuntu Zesty's 4.10.0-15.17 (and
  later) kernels.

  The full cover letter of the proposed fix by my colleague Wolfgang
  Bumiller follows:

  Commit 1045ba77a ("net sched actions: Add support for user cookies")
  added code to net/sched/act_api.c's tcf_action_init_1 using the `tb`
  nlattr array unconditionally, while it was otherwise used as well as
  initialized only when `name == NULL`:

if (name == NULL) {
err = nla_parse_nested(tb, TCA_ACT_MAX, nla, NULL);

  In the other case `nla` is instead passed over to ->init to be parsed
  there (using a different set of TCA_ enum values, iow. TCA_ACT_COOKIE
  then "clashes" with some other value). This lead to the following three
  example commands resulting in errors (sometimes followed by more traces
  and hangups some time later (although the hangups happened seconds or
  sometimes minutes later, sometimes not at all - results differed between
  different kernel versions (linux git-master vs ubuntu's mainline 4.11
  rc6 vs. pve 4.10.5 (based off ubuntu's zesty kernel where the commit is
  cherry-picked)...))):

   # ip link add ve0 type veth peer name ve0b
   # tc qdisc add dev ve0 handle : ingress
   # tc filter add dev ve0 parent : prio 50 basic police rate 1000bps burst 
1000b drop

  The 3rd command would sometimes succeed, sometimes error with:

   RTNETLINK answers: Invalid argument
   We have an error talking to the kernel

  and sometimes error with:

   RTNETLINK answers: Cannot allocate memory
   We have an error talking to the kernel

  In the latter case I assume `cklen` became negative, which passes the
  TC_COOKIE_MAX_SIZE check since it is signed but becomes unsigned later
  in kmemdup() (see the crash dump below)

  When the `tc filter add` command fails a backtrace shows up in dmesg,
  added below.

  I'm not sure why the TC_ACT_COOKIE code was added to tcf_action_init_1
  where it is now. It makes me think that it's supposed to be available
  universally, but the `name == NULL` check for how nla is used or passed
  to ->init() shows that the there are various different TC_ACT_* enums in
  use at this point, hence the 'RFC' part of the patches, I'm not that
  familiar with the code yet.

  Backtrace when running `tc filter add`:

  Apr 12 11:31:38 testmachine kernel: [ cut here ]
  Apr 12 11:31:38 testmachine kernel: WARNING: CPU: 7 PID: 16596 at 
mm/page_alloc.c:3541 __alloc_pages_slowpath+0x9fe/0xba0
  Apr 12 11:31:38 testmachine kernel: Modules linked in: act_police 
cls_basic sch_ingress veth nfsv3 nfs_acl nfs lockd grace ip6t_REJECT 
nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables 
xt_mac ipt_REJECT nf_reject_ipv4 xt_physdev xt_comment nf_conntrack_ipv4 
nf_defrag_ipv4 xt_tcpudp xt_mark xt_set xt_addrtype xt_multiport xt_conntrack 
nf_conntrack ip_set_hash_net ip_set arc4 md4 nls_utf8 cifs ccm fscache ipta
  Apr 12 11:31:38 testmachine kernel:  snd_hda_codec_realtek 
snd_hda_codec_generic aesni_intel aes_x86_64 crypto_simd drm_kms_helper 
glue_helper cryptd drm snd_hda_intel intel_cstate snd_hda_codec i2c_algo_bit 
fb_sys_fops snd_hda_core joydev syscopyarea snd_hwdep sysfillrect input_leds 
sysimgblt intel_rapl_perf snd_pcm snd_timer snd pcspkr soundcore mei_me lpc_ich 
mei shpchp tpm_infineon mac_hid wmi acpi_pad video vhost_net vhost macv
  Apr 12 11:31:38 testmachine kernel: CPU: 7 PID: 16596 Comm: tc Tainted: P 
  O4.10.5-1-pve #1
  Apr 12 11:31:38 testmachine kernel: Hardware name: ASUS All Series/Z97-A, 
BIOS 2801 11/11/2015
  Apr 12 11:31:38 testmachine kernel: Call Trace:
  Apr 12 11:31:38 testmachine kernel:  dump_stack+0x63/0x81
  Apr 12 11:31:38 testmachine kernel:  __warn+0xcb/0xf0
  Apr 12 11:31:38 tes

[Kernel-packages] [Bug 1682368] Re: refcount underflow / kernel NULL dereference after attempting to add basic tc filter

[Fabian Grünbichler]

SRU request sent to kernel-team list.

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

Title:
  refcount underflow / kernel NULL dereference after attempting to add
  basic tc filter

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == SRU Justification ==

  Impact: adding a tc filter sometimes fails, potentially followed by
  kernel hangs and kernel NULL pointer dereference

  Fix: proposed upstream by Wolfgang Bumiller [1,2]

  Regression Potential: Since nobody else noticed this issue in 4.11 >=
  rc1 or Ubuntu 4.10 >= 15.17, and the fix only touches the broken code,
  the regression potential should be minimal ;)

  1: http://marc.info/?l=linux-netdev&m=149200746116365
  2: http://marc.info/?l=linux-netdev&m=149200742616349

  ---

  Commit 1045ba77a which was backported for #1674087 in
  fc0cef7a8ec1e63ee3405f642983dd86e04ab6cc (first released with
  Ubuntu-4.10.0-15.17) introduces the problematic code. Note that while
  the traces below were generated using a custom patched kernel, the
  same issue is reproducible using Ubuntu Zesty's 4.10.0-15.17 (and
  later) kernels.

  The full cover letter of the proposed fix by my colleague Wolfgang
  Bumiller follows:

  Commit 1045ba77a ("net sched actions: Add support for user cookies")
  added code to net/sched/act_api.c's tcf_action_init_1 using the `tb`
  nlattr array unconditionally, while it was otherwise used as well as
  initialized only when `name == NULL`:

if (name == NULL) {
err = nla_parse_nested(tb, TCA_ACT_MAX, nla, NULL);

  In the other case `nla` is instead passed over to ->init to be parsed
  there (using a different set of TCA_ enum values, iow. TCA_ACT_COOKIE
  then "clashes" with some other value). This lead to the following three
  example commands resulting in errors (sometimes followed by more traces
  and hangups some time later (although the hangups happened seconds or
  sometimes minutes later, sometimes not at all - results differed between
  different kernel versions (linux git-master vs ubuntu's mainline 4.11
  rc6 vs. pve 4.10.5 (based off ubuntu's zesty kernel where the commit is
  cherry-picked)...))):

   # ip link add ve0 type veth peer name ve0b
   # tc qdisc add dev ve0 handle : ingress
   # tc filter add dev ve0 parent : prio 50 basic police rate 1000bps burst 
1000b drop

  The 3rd command would sometimes succeed, sometimes error with:

   RTNETLINK answers: Invalid argument
   We have an error talking to the kernel

  and sometimes error with:

   RTNETLINK answers: Cannot allocate memory
   We have an error talking to the kernel

  In the latter case I assume `cklen` became negative, which passes the
  TC_COOKIE_MAX_SIZE check since it is signed but becomes unsigned later
  in kmemdup() (see the crash dump below)

  When the `tc filter add` command fails a backtrace shows up in dmesg,
  added below.

  I'm not sure why the TC_ACT_COOKIE code was added to tcf_action_init_1
  where it is now. It makes me think that it's supposed to be available
  universally, but the `name == NULL` check for how nla is used or passed
  to ->init() shows that the there are various different TC_ACT_* enums in
  use at this point, hence the 'RFC' part of the patches, I'm not that
  familiar with the code yet.

  Backtrace when running `tc filter add`:

  Apr 12 11:31:38 testmachine kernel: [ cut here ]
  Apr 12 11:31:38 testmachine kernel: WARNING: CPU: 7 PID: 16596 at 
mm/page_alloc.c:3541 __alloc_pages_slowpath+0x9fe/0xba0
  Apr 12 11:31:38 testmachine kernel: Modules linked in: act_police 
cls_basic sch_ingress veth nfsv3 nfs_acl nfs lockd grace ip6t_REJECT 
nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables 
xt_mac ipt_REJECT nf_reject_ipv4 xt_physdev xt_comment nf_conntrack_ipv4 
nf_defrag_ipv4 xt_tcpudp xt_mark xt_set xt_addrtype xt_multiport xt_conntrack 
nf_conntrack ip_set_hash_net ip_set arc4 md4 nls_utf8 cifs ccm fscache ipta
  Apr 12 11:31:38 testmachine kernel:  snd_hda_codec_realtek 
snd_hda_codec_generic aesni_intel aes_x86_64 crypto_simd drm_kms_helper 
glue_helper cryptd drm snd_hda_intel intel_cstate snd_hda_codec i2c_algo_bit 
fb_sys_fops snd_hda_core joydev syscopyarea snd_hwdep sysfillrect input_leds 
sysimgblt intel_rapl_perf snd_pcm snd_timer snd pcspkr soundcore mei_me lpc_ich 
mei shpchp tpm_infineon mac_hid wmi acpi_pad video vhost_net vhost macv
  Apr 12 11:31:38 testmachine kernel: CPU: 7 PID: 16596 Comm: tc Tainted: P 
  O4.10.5-1-pve #1
  Apr 12 11:31:38 testmachine kernel: Hardware name: ASUS All Series/Z97-A, 
BIOS 2801 11/11/2015
  Apr 12 11:31:38 testmachine kernel: Call Trace:
  Apr 12 11:31:38 testmachine kernel:  dump_stack+0x63/0x81
  Apr 12 11:31:38 testmachine kernel:  __warn+0xcb/0xf0
  Apr 12 11:31:38 testmachine kernel:  warn_slowpat

[Kernel-packages] [Bug 1682368] [NEW] refcount underflow / kernel NULL dereference after attempting to add basic tc filter

[Fabian Grünbichler]

Public bug reported:

== SRU Justification ==

Impact: adding a tc filter sometimes fails, potentially followed by
kernel hangs and kernel NULL pointer dereference

Fix: proposed upstream by Wolfgang Bumiller [1,2]

Regression Potential: Since nobody else noticed this issue in 4.11 >=
rc1 or Ubuntu 4.10 >= 15.17, and the fix only touches the broken code,
the regression potential should be minimal ;)

1: http://marc.info/?l=linux-netdev&m=149200746116365
2: http://marc.info/?l=linux-netdev&m=149200742616349

---

Commit 1045ba77a which was backported for #1674087 in
fc0cef7a8ec1e63ee3405f642983dd86e04ab6cc (first released with
Ubuntu-4.10.0-15.17) introduces the problematic code. Note that while
the traces below were generated using a custom patched kernel, the same
issue is reproducible using Ubuntu Zesty's 4.10.0-15.17 (and later)
kernels.

The full cover letter of the proposed fix by my colleague Wolfgang
Bumiller follows:

Commit 1045ba77a ("net sched actions: Add support for user cookies")
added code to net/sched/act_api.c's tcf_action_init_1 using the `tb`
nlattr array unconditionally, while it was otherwise used as well as
initialized only when `name == NULL`:

if (name == NULL) {
err = nla_parse_nested(tb, TCA_ACT_MAX, nla, NULL);

In the other case `nla` is instead passed over to ->init to be parsed
there (using a different set of TCA_ enum values, iow. TCA_ACT_COOKIE
then "clashes" with some other value). This lead to the following three
example commands resulting in errors (sometimes followed by more traces
and hangups some time later (although the hangups happened seconds or
sometimes minutes later, sometimes not at all - results differed between
different kernel versions (linux git-master vs ubuntu's mainline 4.11
rc6 vs. pve 4.10.5 (based off ubuntu's zesty kernel where the commit is
cherry-picked)...))):

 # ip link add ve0 type veth peer name ve0b
 # tc qdisc add dev ve0 handle : ingress
 # tc filter add dev ve0 parent : prio 50 basic police rate 1000bps burst 
1000b drop

The 3rd command would sometimes succeed, sometimes error with:

 RTNETLINK answers: Invalid argument
 We have an error talking to the kernel

and sometimes error with:

 RTNETLINK answers: Cannot allocate memory
 We have an error talking to the kernel

In the latter case I assume `cklen` became negative, which passes the
TC_COOKIE_MAX_SIZE check since it is signed but becomes unsigned later
in kmemdup() (see the crash dump below)

When the `tc filter add` command fails a backtrace shows up in dmesg,
added below.

I'm not sure why the TC_ACT_COOKIE code was added to tcf_action_init_1
where it is now. It makes me think that it's supposed to be available
universally, but the `name == NULL` check for how nla is used or passed
to ->init() shows that the there are various different TC_ACT_* enums in
use at this point, hence the 'RFC' part of the patches, I'm not that
familiar with the code yet.

Backtrace when running `tc filter add`:

Apr 12 11:31:38 testmachine kernel: [ cut here ]
Apr 12 11:31:38 testmachine kernel: WARNING: CPU: 7 PID: 16596 at 
mm/page_alloc.c:3541 __alloc_pages_slowpath+0x9fe/0xba0
Apr 12 11:31:38 testmachine kernel: Modules linked in: act_police cls_basic 
sch_ingress veth nfsv3 nfs_acl nfs lockd grace ip6t_REJECT nf_reject_ipv6 
nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_mac ipt_REJECT 
nf_reject_ipv4 xt_physdev xt_comment nf_conntrack_ipv4 nf_defrag_ipv4 xt_tcpudp 
xt_mark xt_set xt_addrtype xt_multiport xt_conntrack nf_conntrack 
ip_set_hash_net ip_set arc4 md4 nls_utf8 cifs ccm fscache ipta
Apr 12 11:31:38 testmachine kernel:  snd_hda_codec_realtek 
snd_hda_codec_generic aesni_intel aes_x86_64 crypto_simd drm_kms_helper 
glue_helper cryptd drm snd_hda_intel intel_cstate snd_hda_codec i2c_algo_bit 
fb_sys_fops snd_hda_core joydev syscopyarea snd_hwdep sysfillrect input_leds 
sysimgblt intel_rapl_perf snd_pcm snd_timer snd pcspkr soundcore mei_me lpc_ich 
mei shpchp tpm_infineon mac_hid wmi acpi_pad video vhost_net vhost macv
Apr 12 11:31:38 testmachine kernel: CPU: 7 PID: 16596 Comm: tc Tainted: P   
O4.10.5-1-pve #1
Apr 12 11:31:38 testmachine kernel: Hardware name: ASUS All Series/Z97-A, 
BIOS 2801 11/11/2015
Apr 12 11:31:38 testmachine kernel: Call Trace:
Apr 12 11:31:38 testmachine kernel:  dump_stack+0x63/0x81
Apr 12 11:31:38 testmachine kernel:  __warn+0xcb/0xf0
Apr 12 11:31:38 testmachine kernel:  warn_slowpath_null+0x1d/0x20
Apr 12 11:31:38 testmachine kernel:  __alloc_pages_slowpath+0x9fe/0xba0
Apr 12 11:31:38 testmachine kernel:  ? get_page_from_freelist+0x46a/0xb20
Apr 12 11:31:38 testmachine kernel:  ? schedule+0x36/0x80
Apr 12 11:31:38 testmachine kernel:  ? schedule_timeout+0x22a/0x3f0
Apr 12 11:31:38 testmachine kernel:  __alloc_pages_nodemask+0x209/0x260
Apr 12 11:31:38 testmachine kernel:  alloc_pages_current+0x95/0x140
Apr 12 11:31

[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

[Fabian Tröster]

Well, alright, I tested kernel 4.4.0-72. Didn't really work for me. It's 
actually not really helping, because with it Unity is broken, not all icons are 
loading (workspace switcher is gone), no mouse at all. Something utterly wrong 
with USB support. At least the system doesn't freeze, so I could recover by 
switching to a virtual console.
Enabling Xenial proposed didn't really help with the package management either. 
Got a red alert symbol from the update manager. I had to revert everything, 
actually took two reboots with 4.4.0-62 until the network was working again. 
Now I'm back on 4.4.0-62 with Xenial proposed diabled and it will stay that way.

What is wrong with Ubuntu? This is the first time I have had such issues
ever and I have been using Ubuntu version 7.10

I will have to check whether Raspbian is also affected by this bug. The reason 
is: I am using Edimax EW-7811Un (RTL8188 chipset) on several Rasperry Pi 
computers.
Sorry, but I really do not understand how such things can happen.

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

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
  Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
  Feb 21 07:17:03 orin kernel: [  190.625241] rtl8192cu: Board Type 0
  Feb 21 07:17:03 ori

[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

[Fabian Tröster]

Sorry, Joseph, a bit more information please: Which proposed kernel version 
specifically? I thought this had been done before. Anyway: I activated the 
Xenial proposed repository, but I can't see any kernel newer than 4.4.0-72 -- 
is this the version supposed to fix this issue?
To be honest, after six weeks I would have hoped you have already fixed this 
issue. I mean, it isn't really expensive to buy a WiFi with RTL8188 chipset, 
right?

Can you answer the simple question: Why does it take so long to get
something working again which did work in the past?

Please name the kernel version to install and test.

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

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
  Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
  Feb 21 07:17:03 orin kernel: [  190.625241] rtl8192cu: Board Type 0
  Feb 21 07:17:03 orin kernel: [  190.626355] rtl_usb: rx_max_size 15360, 
rx_urb_num 8, in_ep 1
  Feb 21 07:17:03 orin kernel: [  190.626408] rtl8192cu: Loading firmware 
rtlwifi/rtl8192cufw_TMSC.bin
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7698] (wlan0): 
using nl80211 for WiFi device control
  Feb 21 07:17:03 orin kernel: [  190.636625] ieee80211 phy0: Selected rate 
control algorithm 'rtl_rc'

[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

[Fabian Tröster]

@Alexandru: Thank you for that suggestion. I'm not willing to add a PPA
for something as important as the kernel. The whole point of having a
LTS release is that it receives updates for five years. Bugs like this
can not happen in 2017! Or at least they need to be fixed ASAP. We're
six weeks in and no fix.

It seems to me that some kernel dev ruined the RTL8188 and RTL8192
drivers and now they can't seem to be bothered to fix the issue. That's
simply unacceptable and if this would happen to Microsoft they would
receive a good beating for that and rightfully so. Sorry for the rant,
but this is really completely unacceptable.

And before anyone asks me for help in fixing this issue -- because it is Open 
Source and so on -- I am no kernel developer and because I know nothing about 
how to develop drivers I make sure of not touching them.
So, I ask again: Can Joseph Salisbury please comment on the situation and why 
there is still no fix for this issue? (FYI: The last entry in the referenced 
bug #1667920 is from March 17th, which is three weeks ago.)

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

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
  Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
  Feb 21 07:17:03 orin kernel: [  190.62

[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

[Fabian Tröster]

Is someone still working on this issue? It doesn't look like it given the 
status "Fix Committed". Correct me if I'm wrong but the WiFi chipsets affected 
by this bug are in widespread use and I think it is a shame that it seems to be 
impossible to fix something which was demonstrably working in a previous 
version.
Can the dev working on it please comment? Greatly appreciated.

Sticking with kernel 4.4.0-62 indefinitely can't be the solution, or can
it?

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

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
  Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
  Feb 21 07:17:03 orin kernel: [  190.625241] rtl8192cu: Board Type 0
  Feb 21 07:17:03 orin kernel: [  190.626355] rtl_usb: rx_max_size 15360, 
rx_urb_num 8, in_ep 1
  Feb 21 07:17:03 orin kernel: [  190.626408] rtl8192cu: Loading firmware 
rtlwifi/rtl8192cufw_TMSC.bin
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7698] (wlan0): 
using nl80211 for WiFi device control
  Feb 21 07:17:03 orin kernel: [  190.636625] ieee80211 phy0: Selected rate 
control algorithm 'rtl_rc'
  Feb 21 07:17:03 orin kernel: [  190.637211] usbcore: registered new interface 
driver rtl8192cu
  Feb 21 07:17:03 orin systemd[1]: Starting Load/Save RF Ki

[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

[Fabian Tröster]

Hi, unfortunately 4.4.0-69 has been withdrawn from the 16.04 repository.
(See here: https://launchpad.net/ubuntu/xenial/+package/linux-
tools-4.4.0-69-generic )

Additional information: 4.4.0-71 crashes with WiFi RTL8188CUS chipset
(Edimax EW-7811Un), too. Probably same driver as for RTL8192.

Currently stuck at kernel 4.4.0-62, which is the only one working on the
system. Crashes first encountered with kernel 4.4.0-64

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

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
  Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
  Feb 21 07:17:03 orin kernel: [  190.625241] rtl8192cu: Board Type 0
  Feb 21 07:17:03 orin kernel: [  190.626355] rtl_usb: rx_max_size 15360, 
rx_urb_num 8, in_ep 1
  Feb 21 07:17:03 orin kernel: [  190.626408] rtl8192cu: Loading firmware 
rtlwifi/rtl8192cufw_TMSC.bin
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7698] (wlan0): 
using nl80211 for WiFi device control
  Feb 21 07:17:03 orin kernel: [  190.636625] ieee80211 phy0: Selected rate 
control algorithm 'rtl_rc'
  Feb 21 07:17:03 orin kernel: [  190.637211] usbcore: registered new interface 
driver rtl8192cu
  Feb 21 07:17:03 orin systemd[1]: Starting Load/Save RF Kill Switch Status...
  Feb 21 07:17:03

[Kernel-packages] [Bug 1668594] Re: Recent KVM RTC cherry-picks break (some) Windows Live-Migrations

[Fabian Grünbichler]

works as expected, thanks.

** Tags removed: verification-needed-xenial
** Tags added: verification-done-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/1668594

Title:
  Recent KVM RTC cherry-picks break (some) Windows Live-Migrations

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

Bug description:
  == SRU Justification ==

  Impact: Windows Live-Migration does not work reliably anymore with
  recent KVM RTC cherry-picks.

  Fix: Single follow-up upstream cherry pick which fixes the problem.

  Regression Potential: The patch has been upstream since 4.8, so it
  should be well-tested at this point. Thus regressions are unlikely.

  ---

  The fix for
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649718 cherry-
  picked three commits from upstream 4.6 related to RTC interrupt
  handling. Unfortunately, the followup commit included in 4.8 was
  missed. As a result, Windwos Live-Migration in Qemu is broken on
  certain hardware.

  Test system's CPU:
   cat /proc/cpuinfo
  processor   : 0
  vendor_id   : GenuineIntel
  cpu family  : 6
  model   : 79
  model name  : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
  stepping: 1
  microcode   : 0xb1b
  cpu MHz : 1425.621
  cache size  : 20480 KB
  physical id : 0
  siblings: 16
  core id : 0
  cpu cores   : 8
  apicid  : 0
  initial apicid  : 0
  fpu : yes
  fpu_exception   : yes
  cpuid level : 20
  wp  : yes
  flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb 
intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle 
avx2 smep bmi2 erms invpcid rtm cqm rdseed adx smap xsaveopt cqm_llc 
cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm arat pln pts
  bugs:
  bogomips: 4199.88
  clflush size: 64
  cache_alignment : 64
  address sizes   : 46 bits physical, 48 bits virtual
  power management:

  Live-Migrating a Windows Server 2016 VM (Qemu commandline below) hangs
  the VM in about 1/3 attempts. Interestingly, migrating the VM back to
  the original host allows the VM to run normally again (but subsequent
  migration attempts might hang it again as well).

  non-minimized qemu command line:
  /usr/bin/kvm -id 101 -chardev 
'socket,id=qmp,path=/var/run/qemu-server/101.qmp,server,nowait' -mon 
'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/101.pid -daemonize 
-smbios 'type=1,uuid=a6e1bea5-09ab-4f8a-b1c2-3991725892f5' -drive 
'if=pflash,unit=0,format=raw,readonly,file=/usr/share/kvm/OVMF_CODE-pure-efi.fd'
 -drive 'if=pflash,unit=1,format=raw,file=/tmp/101-ovmf.fd' -name Windows2016 
-smp '2,sockets=1,cores=2,maxcpus=2' -nodefaults -boot 
'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg'
 -vga std -vnc unix:/var/run/qemu-server/101.vnc,x509,password -no-hpet -cpu 
'host,+kvm_pv_unhalt,+kvm_pv_eoi,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,hv_relaxed'
 -m 2048 -k de -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' 
-device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 
'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 
'usb-tablet,id=tablet,bus=uhci.0,port=1' -chardev 'socket,path=/
 var/run/qemu-server/101.qga,server,nowait,id=qga0' -device 
'virtio-serial,id=qga0,bus=pci.0,addr=0x8' -device 
'virtserialport,chardev=qga0,name=org.qemu.guest_agent.0' -device 
'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 
'initiator-name=iqn.1993-08.org.debian:01:98525b424092' -drive 
'file=PATH,if=none,id=drive-ide2,media=cdrom,aio=threads' -device 
'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -device 
'virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5' -drive 
'file=PATH,if=none,id=drive-scsi0,cache=writeback,discard=on,format=raw,aio=threads,detect-zeroes=unmap'
 -device 
'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100'
 -netdev 
'type=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on'
 -device 
'virtio-net-pci,mac=32:F5:16:78:A7:F0,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'
 -rtc 'driftfix=slew,base=localtime' -global 'kvm-pit.lost_tick
 _policy=discard'

  The causing commits were triaged via git bisect, applying the follow-
  up commit b0eaf4506f5f95d15d6731d72c0ddf4a2179eefa fixes the iss

[Kernel-packages] [Bug 1647511] Re: During kernel upgrade, /usr/sbin/dkms falsely reports that initrd.img won't be created

[Fabian Raab]

Also affects linux-image-4.4.0-66-generic

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

Title:
  During kernel upgrade, /usr/sbin/dkms falsely reports that initrd.img
  won't be created

Status in dkms package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu release
  ==

  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  Version of package
  ==

  dkms:
Installed: 2.2.0.3-2ubuntu11.3
Candidate: 2.2.0.3-2ubuntu11.3
Version table:
   *** 2.2.0.3-2ubuntu11.3 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages
  100 /var/lib/dpkg/status
   2.2.0.3-2ubuntu11 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages

  The problem
  ===

  When setting up `linux-image-4.4.0-53-generic`, the following warning
  appears three times:

  : Unable to find an initial ram disk that I know how to handle.
  Will not try to make an initrd.

  However, when setting up `linux-image-extra-4.4.0-53-generic`, the
  following message appears:

  update-initramfs: Generating /boot/initrd.img-4.4.0-53-generic

  The text "Unable to find an initial ram disk" appears in
  `/usr/sbin/dkms`, though it may appear elsewhere.

  What should happen
  ==

  The warning message should not appear.

  Messages when setting up the two packages
  =

  Setting up linux-image-4.4.0-53-generic (4.4.0-53.74) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-53-generic 
/boot/vmlinuz-4.4.0-53-generic
  run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-53-generic 
/boot/vmlinuz-4.4.0-53-generic
  : Unable to find an initial ram disk that I know how to handle.
  Will not try to make an initrd.
  : Unable to find an initial ram disk that I know how to handle.
  Will not try to make an initrd.
  : Unable to find an initial ram disk that I know how to handle.
  Will not try to make an initrd.
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-53-generic 
/boot/vmlinuz-4.4.0-53-generic
  update-initramfs: Generating /boot/initrd.img-4.4.0-53-generic
  run-parts: executing /etc/kernel/postinst.d/pm-utils 4.4.0-53-generic 
/boot/vmlinuz-4.4.0-53-generic
  run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 
4.4.0-53-generic /boot/vmlinuz-4.4.0-53-generic
  run-parts: executing /etc/kernel/postinst.d/update-notifier 4.4.0-53-generic 
/boot/vmlinuz-4.4.0-53-generic
  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-53-generic 
/boot/vmlinuz-4.4.0-53-generic
  Generating grub configuration file ...
  Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is 
set is no longer supported.
  Found linux image: /boot/vmlinuz-4.4.0-53-generic
  Found initrd image: /boot/initrd.img-4.4.0-53-generic
  Found linux image: /boot/vmlinuz-4.4.0-51-generic
  Found initrd image: /boot/initrd.img-4.4.0-51-generic
  Found linux image: /boot/vmlinuz-4.4.0-47-generic
  Found initrd image: /boot/initrd.img-4.4.0-47-generic
  Adding boot menu entry for EFI firmware configuration
  done
  Setting up linux-image-extra-4.4.0-53-generic (4.4.0-53.74) ...
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-53-generic 
/boot/vmlinuz-4.4.0-53-generic
  run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-53-generic 
/boot/vmlinuz-4.4.0-53-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-53-generic 
/boot/vmlinuz-4.4.0-53-generic
  update-initramfs: Generating /boot/initrd.img-4.4.0-53-generic
  run-parts: executing /etc/kernel/postinst.d/pm-utils 4.4.0-53-generic 
/boot/vmlinuz-4.4.0-53-generic
  run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 
4.4.0-53-generic /boot/vmlinuz-4.4.0-53-generic
  run-parts: executing /etc/kernel/postinst.d/update-notifier 4.4.0-53-generic 
/boot/vmlinuz-4.4.0-53-generic
  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-53-generic 
/boot/vmlinuz-4.4.0-53-generic
  Generating grub configuration file ...
  Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is 
set is no longer supported.
  Found linux image: /boot/vmlinuz-4.4.0-53-generic
  Found initrd image: /boot/initrd.img-4.4.0-53-generic
  Found linux image: /boot/vmlinuz-4.4.0-51-generic
  Found initrd image: /boot/initrd.img-4.4.0-51-generic
  Found linux image: /boot/vmlinuz-4.4.0-47-generic
  Found initrd image: /boot/initrd.img-4.4.0-47-generic
  Adding boot menu entry for EFI firmware configuration
  done

  ProblemType: Bug
  Dis

[Kernel-packages] [Bug 1668594] [NEW] Recent KVM RTC cherry-picks break (some) Windows Live-Migrations

[Fabian Grünbichler]

Public bug reported:

== SRU Justification ==

Impact: Windows Live-Migration does not work reliably anymore with
recent KVM RTC cherry-picks.

Fix: Single follow-up upstream cherry pick which fixes the problem.

Regression Potential: The patch has been upstream since 4.8, so it
should be well-tested at this point. Thus regressions are unlikely.

---

The fix for https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649718
cherry-picked three commits from upstream 4.6 related to RTC interrupt
handling. Unfortunately, the followup commit included in 4.8 was missed.
As a result, Windwos Live-Migration in Qemu is broken on certain
hardware.

Test system's CPU:
 cat /proc/cpuinfo
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 79
model name  : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
stepping: 1
microcode   : 0xb1b
cpu MHz : 1425.621
cache size  : 20480 KB
physical id : 0
siblings: 16
core id : 0
cpu cores   : 8
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 20
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb 
intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle 
avx2 smep bmi2 erms invpcid rtm cqm rdseed adx smap xsaveopt cqm_llc 
cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm arat pln pts
bugs:
bogomips: 4199.88
clflush size: 64
cache_alignment : 64
address sizes   : 46 bits physical, 48 bits virtual
power management:

Live-Migrating a Windows Server 2016 VM (Qemu commandline below) hangs
the VM in about 1/3 attempts. Interestingly, migrating the VM back to
the original host allows the VM to run normally again (but subsequent
migration attempts might hang it again as well).

non-minimized qemu command line:
/usr/bin/kvm -id 101 -chardev 
'socket,id=qmp,path=/var/run/qemu-server/101.qmp,server,nowait' -mon 
'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/101.pid -daemonize 
-smbios 'type=1,uuid=a6e1bea5-09ab-4f8a-b1c2-3991725892f5' -drive 
'if=pflash,unit=0,format=raw,readonly,file=/usr/share/kvm/OVMF_CODE-pure-efi.fd'
 -drive 'if=pflash,unit=1,format=raw,file=/tmp/101-ovmf.fd' -name Windows2016 
-smp '2,sockets=1,cores=2,maxcpus=2' -nodefaults -boot 
'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg'
 -vga std -vnc unix:/var/run/qemu-server/101.vnc,x509,password -no-hpet -cpu 
'host,+kvm_pv_unhalt,+kvm_pv_eoi,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,hv_relaxed'
 -m 2048 -k de -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' 
-device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 
'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 
'usb-tablet,id=tablet,bus=uhci.0,port=1' -chardev 'socket,path=/va
 r/run/qemu-server/101.qga,server,nowait,id=qga0' -device 
'virtio-serial,id=qga0,bus=pci.0,addr=0x8' -device 
'virtserialport,chardev=qga0,name=org.qemu.guest_agent.0' -device 
'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 
'initiator-name=iqn.1993-08.org.debian:01:98525b424092' -drive 
'file=PATH,if=none,id=drive-ide2,media=cdrom,aio=threads' -device 
'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -device 
'virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5' -drive 
'file=PATH,if=none,id=drive-scsi0,cache=writeback,discard=on,format=raw,aio=threads,detect-zeroes=unmap'
 -device 
'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100'
 -netdev 
'type=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on'
 -device 
'virtio-net-pci,mac=32:F5:16:78:A7:F0,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'
 -rtc 'driftfix=slew,base=localtime' -global 'kvm-pit.lost_tick_p
 olicy=discard'

The causing commits were triaged via git bisect, applying the follow-up
commit b0eaf4506f5f95d15d6731d72c0ddf4a2179eefa fixes the issue with no
observable side-effects. Mainline 4.6 is also affected and triggers the
bug just like Ubuntu kernels >= Ubuntu-4.4.0-63.84

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

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

Title:
  Recent KVM RTC cherry-picks break (some) Windows Live-Migrations

Status in linux package in Ubuntu:
  New

Bug description:
  == SRU Justification ==

  Impact: Windo

[Kernel-packages] [Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59

[Fabian Grünbichler]

you could also try cherry-picking
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-
stable.git/commit/?id=6b4e3181d7bd5ca5ab6f45929e4a5ffa7ab4ab7f , but
that will probably need some more inbetween patches as well..

reverting the two commits fixed the issue for our users (Proxmox VE,
which uses a kernel based on the 4.4.x one from 16.04)

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

Title:
  "Out of memory" errors after upgrade to 4.4.0-59

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

Bug description:
  I recently replaced some Xenial servers, and started experiencing "Out
  of memory" problems with the default kernel.

  We bake Amazon AMIs based on an official Ubuntu-provided image (ami-
  e6b58e85, in ap-southeast-2, from https://cloud-
  images.ubuntu.com/locator/ec2/).  Previous versions of our AMI
  included "4.4.0-57-generic", but the latest version picked up
  "4.4.0-59-generic" as part of a "dist-upgrade".

  Instances booted using the new AMI have been using more memory, and
  experiencing OOM issues - sometimes during boot, and sometimes a while
  afterwards.  An example from the system log is:

  [  130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' 
at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds.
  [  130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 
2017 22:09:35 +. Datasource DataSourceEc2.  Up 130.09 seconds
  [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice 
child
  [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, 
anon-rss:51184kB, file-rss:2164kB
  [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or 
sacrifice child
  [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, 
anon-rss:6676kB, file-rss:0kB
  [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or 
sacrifice child
  [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, 
anon-rss:23956kB, file-rss:1356kB

  I have a hunch that this may be related to the fix for
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400,
  introduced in linux (4.4.0-58.79).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 06:29 seq
   crw-rw 1 root audio 116, 33 Jan 12 06:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 06:38:45 2017
  Ec2AMI: ami-0f93966c
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/09/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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

[Kernel-packages] [Bug 1647400] Re: system freeze when swapping to encrypted swap partition

[Fabian Grünbichler]

Continuing in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842 ?

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

Title:
  system freeze when swapping to encrypted swap partition

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Released

Bug description:
  == Comment: #0 - Bernd-Rainer Bresser  - 2016-12-05 
04:27:00 ==
  +++ This bug was initially created as a clone of Bug #147836 +++

  ---Problem Description---
  When the system is installed with encrypted swap partition the attempt to 
swap ends in a system freeze. No error, no dump, the system needs to be 
reloaded.
   
  Contact Information = Bernd-Rainer Bresser/Germany/IBM, Wen Yi AG 
Gao/China/IBM 
   
  ---uname output---
  Linux s38lp65 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:05:09 UTC 2016 
s390x s390x s390x GNU/Linux
   
  Machine Type = z13 LPAR 
   
  ---System Hang---
   System is frozen. No error, no dump, the system needs to be reloaded.
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. install a system with encrypted swap partition. This can be done using 
the installer or via manual updates to /etc/fstab and /etc/crypttab.

  2. Verify encrypted swap partition exists
   cryptsetup status kvmibm-swap
  /dev/mapper/kvmibm-swap is active and is in use.
type:PLAIN
cipher:  aes-xts-plain64:sha256
keysize: 256 bits
device:  /dev/dasda2
offset:  0 sectors
size:8388672 sectors
mode:read/write

  3. force swapping
  this can be done by a command like this (if the system has 8GB memory)
  dd if=/dev/zero of=/dev/null ibs=16k obs=8G count=2MB
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Location:
   
   
  *Additional Instructions for Bernd-Rainer Bresser/Germany/IBM, Wen Yi AG 
Gao/China/IBM: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Bernd-Rainer Bresser  - 2016-12-05 
04:33:24 ==
  - the problem was originally found on KVM for IBM z 1.1.3
  - test on Ubuntu 16.04.1 showed the same issue here
  - on KVM for IBM z 1.1.3 the problem could be solved/circumvented by reverting
 commit 564e81a57f9788b1475127012e0fd44e9049e342
Author: Tetsuo Handa 
Date:   Fri Feb 5 15:36:30 2016 -0800
  mm, vmstat: fix wrong WQ sleep when memory reclaim doesn't make 
any progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1647400/+subscriptions

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

[Kernel-packages] [Bug 1647400] Re: system freeze when swapping to encrypted swap partition

[Fabian Grünbichler]

cherry-picking these two commits should also be accompanied by cherry-
picking https://git.kernel.org/cgit/linux/kernel/git/stable/linux-
stable.git/commit/?id=6b4e3181d7bd5ca5ab6f45929e4a5ffa7ab4ab7f ,
otherwise users will see a lot of pre-mature OOM kills..

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

Title:
  system freeze when swapping to encrypted swap partition

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  == Comment: #0 - Bernd-Rainer Bresser  - 2016-12-05 
04:27:00 ==
  +++ This bug was initially created as a clone of Bug #147836 +++

  ---Problem Description---
  When the system is installed with encrypted swap partition the attempt to 
swap ends in a system freeze. No error, no dump, the system needs to be 
reloaded.
   
  Contact Information = Bernd-Rainer Bresser/Germany/IBM, Wen Yi AG 
Gao/China/IBM 
   
  ---uname output---
  Linux s38lp65 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:05:09 UTC 2016 
s390x s390x s390x GNU/Linux
   
  Machine Type = z13 LPAR 
   
  ---System Hang---
   System is frozen. No error, no dump, the system needs to be reloaded.
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. install a system with encrypted swap partition. This can be done using 
the installer or via manual updates to /etc/fstab and /etc/crypttab.

  2. Verify encrypted swap partition exists
   cryptsetup status kvmibm-swap
  /dev/mapper/kvmibm-swap is active and is in use.
type:PLAIN
cipher:  aes-xts-plain64:sha256
keysize: 256 bits
device:  /dev/dasda2
offset:  0 sectors
size:8388672 sectors
mode:read/write

  3. force swapping
  this can be done by a command like this (if the system has 8GB memory)
  dd if=/dev/zero of=/dev/null ibs=16k obs=8G count=2MB
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Location:
   
   
  *Additional Instructions for Bernd-Rainer Bresser/Germany/IBM, Wen Yi AG 
Gao/China/IBM: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Bernd-Rainer Bresser  - 2016-12-05 
04:33:24 ==
  - the problem was originally found on KVM for IBM z 1.1.3
  - test on Ubuntu 16.04.1 showed the same issue here
  - on KVM for IBM z 1.1.3 the problem could be solved/circumvented by reverting
 commit 564e81a57f9788b1475127012e0fd44e9049e342
Author: Tetsuo Handa 
Date:   Fri Feb 5 15:36:30 2016 -0800
  mm, vmstat: fix wrong WQ sleep when memory reclaim doesn't make 
any progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1647400/+subscriptions

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

[Kernel-packages] [Bug 1636517] Re: zfs: importing zpool with vdev on zvol hangs kernel

[Fabian Grünbichler]

issue does not occur anymore for xenial (Ubuntu-4.4.0-49.70)

** Tags removed: verification-needed-xenial
** Tags added: verification-done-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/1636517

Title:
  zfs: importing zpool with vdev on zvol hangs kernel

Status in linux package in Ubuntu:
  Triaged
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in zfs-linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Triaged
Status in zfs-linux source package in Zesty:
  Fix Released

Bug description:
  [SRU Request][Xenial][Yakkety]

  if a zvol of an existing, already imported zpool is a vdev of another
  zpool, a call to "zpool import" will everything zfs related. the stack
  trace is as follows:

  [] taskq_wait+0x74/0xe0 [spl]
  [] taskq_destroy+0x4b/0x100 [spl]
  [] vdev_open_children+0x12d/0x180 [zfs]
  [] vdev_root_open+0x3c/0xc0 [zfs]
  [] vdev_open+0xf5/0x4d0 [zfs]
  [] spa_load+0x39e/0x1c60 [zfs]
  [] spa_tryimport+0xad/0x450 [zfs]
  [] zfs_ioc_pool_tryimport+0x64/0xa0 [zfs]
  [] zfsdev_ioctl+0x44b/0x4e0 [zfs]
  [] do_vfs_ioctl+0x29f/0x490
  [] SyS_ioctl+0x79/0x90
  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [] 0x

  [Fix]
  zfsutils-linux:

  Zesty: https://launchpadlibrarian.net/290907232/zfs-
  linux_0.6.5.8-0ubuntu4_0.6.5.8-0ubuntu5.diff.gz

  Yakkety, likewise
  Xenial, likewise

  Sync'd fixes into kernel repos, patches in:
  http://kernel.ubuntu.com/~cking/zfs-lp-1636517

  [Regression Potential]

  Minimal. This just touched one line in the zfs module
  module/zfs/zvol.cand a shim wrapper in include/linux/blkdev_compat.h

  Tested and passes with the ubuntu kernel team autotest client zfs
  regression tests.

  =

  I traced this back to 193fb6a2c94fab8eb8ce70a5da4d21c7d4023bee (erged
  in 4.4.0-6.21), which added a second parameter to lookup_bdev without
  patching the zfs module (which needs to special case the vdev-on-zvol
  case, and uses this exact method only in this special casing code
  path).

  attached you can find the output of "zfs send -R" ing such a zvol
  ("brokenvol.raw"), running "zfs receive POOL/TARGET < FILE" followed
  by "zpool import" should reproduce the hang.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-45-generic 4.4.0-45.66
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 25 15:46 seq
   crw-rw 1 root audio 116, 33 Oct 25 15:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Oct 25 15:49:51 2016
  HibernationDevice: RESUME=/dev/mapper/xenial--vg-swap_1
  InstallationDate: Installed on 2016-10-25 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:

  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic 
root=/dev/mapper/hostname--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.7
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.7
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1636517] Re: zfs: importing zpool with vdev on zvol hangs kernel

[Fabian Grünbichler]

can confirm that the test packages correctly allow importing of such
pools. thanks for the quick reaction!

minor nitpick since you referenced me in the changelog, please either
spell my last name "Grünbichler" (with 'ü'), or transcribed with 'ue',
and not with an 'i' - thanks! :)

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

Title:
  zfs: importing zpool with vdev on zvol hangs kernel

Status in linux package in Ubuntu:
  Triaged
Status in zfs-linux package in Ubuntu:
  New

Bug description:
  [SRU Request][Xenial][Yakkety]

  if a zvol of an existing, already imported zpool is a vdev of another
  zpool, a call to "zpool import" will everything zfs related. the stack
  trace is as follows:

  [] taskq_wait+0x74/0xe0 [spl]
  [] taskq_destroy+0x4b/0x100 [spl]
  [] vdev_open_children+0x12d/0x180 [zfs]
  [] vdev_root_open+0x3c/0xc0 [zfs]
  [] vdev_open+0xf5/0x4d0 [zfs]
  [] spa_load+0x39e/0x1c60 [zfs]
  [] spa_tryimport+0xad/0x450 [zfs]
  [] zfs_ioc_pool_tryimport+0x64/0xa0 [zfs]
  [] zfsdev_ioctl+0x44b/0x4e0 [zfs]
  [] do_vfs_ioctl+0x29f/0x490
  [] SyS_ioctl+0x79/0x90
  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [] 0x

  [Fix]
  zfsutils-linux:

  Zesty: https://launchpadlibrarian.net/290907232/zfs-
  linux_0.6.5.8-0ubuntu4_0.6.5.8-0ubuntu5.diff.gz

  Yakkety, likewise
  Xenial, likewise

  Sync'd fixes into kernel repos, patches in:
  http://kernel.ubuntu.com/~cking/zfs-lp-1636517

  [Regression Potential]

  Minimal. This just touched one line in the zfs module
  module/zfs/zvol.cand a shim wrapper in include/linux/blkdev_compat.h

  Tested and passes with the ubuntu kernel team autotest client zfs
  regression tests.

  =

  I traced this back to 193fb6a2c94fab8eb8ce70a5da4d21c7d4023bee (erged
  in 4.4.0-6.21), which added a second parameter to lookup_bdev without
  patching the zfs module (which needs to special case the vdev-on-zvol
  case, and uses this exact method only in this special casing code
  path).

  attached you can find the output of "zfs send -R" ing such a zvol
  ("brokenvol.raw"), running "zfs receive POOL/TARGET < FILE" followed
  by "zpool import" should reproduce the hang.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-45-generic 4.4.0-45.66
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 25 15:46 seq
   crw-rw 1 root audio 116, 33 Oct 25 15:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Oct 25 15:49:51 2016
  HibernationDevice: RESUME=/dev/mapper/xenial--vg-swap_1
  InstallationDate: Installed on 2016-10-25 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:

  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic 
root=/dev/mapper/hostname--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.7
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.7
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1636517] Re: zfs: importing zpool with vdev on zvol hangs kernel

[Fabian Grünbichler]

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

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

Title:
  zfs: importing zpool with vdev on zvol hangs kernel

Status in linux package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  New

Bug description:
  if a zvol of an existing, already imported zpool is a vdev of another
  zpool, a call to "zpool import" will everything zfs related. the stack
  trace is as follows:

  [] taskq_wait+0x74/0xe0 [spl]
  [] taskq_destroy+0x4b/0x100 [spl]
  [] vdev_open_children+0x12d/0x180 [zfs]
  [] vdev_root_open+0x3c/0xc0 [zfs]
  [] vdev_open+0xf5/0x4d0 [zfs]
  [] spa_load+0x39e/0x1c60 [zfs]
  [] spa_tryimport+0xad/0x450 [zfs]
  [] zfs_ioc_pool_tryimport+0x64/0xa0 [zfs]
  [] zfsdev_ioctl+0x44b/0x4e0 [zfs]
  [] do_vfs_ioctl+0x29f/0x490
  [] SyS_ioctl+0x79/0x90
  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [] 0x

  I traced this back to 193fb6a2c94fab8eb8ce70a5da4d21c7d4023bee (merged
  in 4.4.0-6.21), which added a second parameter to lookup_bdev without
  patching the zfs module (which needs to special case the vdev-on-zvol
  case, and uses this exact method only in this special casing code
  path).

  attached you can find the output of "zfs send -R" ing such a zvol
  ("brokenvol.raw"), running "zfs receive POOL/TARGET < FILE" followed
  by "zpool import" should reproduce the hang.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-45-generic 4.4.0-45.66
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 25 15:46 seq
   crw-rw 1 root audio 116, 33 Oct 25 15:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Oct 25 15:49:51 2016
  HibernationDevice: RESUME=/dev/mapper/xenial--vg-swap_1
  InstallationDate: Installed on 2016-10-25 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic 
root=/dev/mapper/hostname--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.7
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.7
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1636517] [NEW] zfs: importing zpool with vdev on zvol hangs kernel

[Fabian Grünbichler]

Public bug reported:

if a zvol of an existing, already imported zpool is a vdev of another
zpool, a call to "zpool import" will everything zfs related. the stack
trace is as follows:

[] taskq_wait+0x74/0xe0 [spl]
[] taskq_destroy+0x4b/0x100 [spl]
[] vdev_open_children+0x12d/0x180 [zfs]
[] vdev_root_open+0x3c/0xc0 [zfs]
[] vdev_open+0xf5/0x4d0 [zfs]
[] spa_load+0x39e/0x1c60 [zfs]
[] spa_tryimport+0xad/0x450 [zfs]
[] zfs_ioc_pool_tryimport+0x64/0xa0 [zfs]
[] zfsdev_ioctl+0x44b/0x4e0 [zfs]
[] do_vfs_ioctl+0x29f/0x490
[] SyS_ioctl+0x79/0x90
[] entry_SYSCALL_64_fastpath+0x16/0x71
[] 0x

I traced this back to 193fb6a2c94fab8eb8ce70a5da4d21c7d4023bee (merged
in 4.4.0-6.21), which added a second parameter to lookup_bdev without
patching the zfs module (which needs to special case the vdev-on-zvol
case, and uses this exact method only in this special casing code path).

attached you can find the output of "zfs send -R" ing such a zvol
("brokenvol.raw"), running "zfs receive POOL/TARGET < FILE" followed by
"zpool import" should reproduce the hang.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-45-generic 4.4.0-45.66
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Oct 25 15:46 seq
 crw-rw 1 root audio 116, 33 Oct 25 15:46 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Tue Oct 25 15:49:51 2016
HibernationDevice: RESUME=/dev/mapper/xenial--vg-swap_1
InstallationDate: Installed on 2016-10-25 (0 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
 
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic 
root=/dev/mapper/hostname--vg-root ro
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-45-generic N/A
 linux-backports-modules-4.4.0-45-generic  N/A
 linux-firmware1.157.4
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-2.7
dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-2.7
dmi.sys.vendor: QEMU

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


** Tags: amd64 apport-bug xenial

** Attachment added: "brokenvol.raw"
   
https://bugs.launchpad.net/bugs/1636517/+attachment/4767000/+files/brokenvol.raw

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

Title:
  zfs: importing zpool with vdev on zvol hangs kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  if a zvol of an existing, already imported zpool is a vdev of another
  zpool, a call to "zpool import" will everything zfs related. the stack
  trace is as follows:

  [] taskq_wait+0x74/0xe0 [spl]
  [] taskq_destroy+0x4b/0x100 [spl]
  [] vdev_open_children+0x12d/0x180 [zfs]
  [] vdev_root_open+0x3c/0xc0 [zfs]
  [] vdev_open+0xf5/0x4d0 [zfs]
  [] spa_load+0x39e/0x1c60 [zfs]
  [] spa_tryimport+0xad/0x450 [zfs]
  [] zfs_ioc_pool_tryimport+0x64/0xa0 [zfs]
  [] zfsdev_ioctl+0x44b/0x4e0 [zfs]
  [] do_vfs_ioctl+0x29f/0x490
  [] SyS_ioctl+0x79/0x90
  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [] 0x

  I traced this back to 193fb6a2c94fab8eb8ce70a5da4d21c7d4023bee (merged
  in 4.4.0-6.21), which added a second parameter to lookup_bdev without
  patching the zfs module (which needs to special case the vdev-on-zvol
  case, and uses this exact method only in this special casing code
  path).

  attached you can find the output of "zfs send -R" ing such a zvol
  ("brokenvol.raw"), running "zfs receive POOL/TARGET < FILE" followed
  by "zpool import" should reproduce the hang.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-45-generic 4.4.0-45.66
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices:
   total 0

[Kernel-packages] [Bug 1636517] Re: zfs: importing zpool with vdev on zvol hangs kernel

[Fabian Grünbichler]

attached patch with fix tested with 4.4.0-45.66

note that instead of hardcoding the patched variant of lookup_bdev, it
might make sense to adapt the zfs automake files to autodetect and
handle both one parameter and two parameter variants?

that way, all three variations of building the zfs module would work:

dkms source with either an Ubuntu or upstream kernel
Ubuntu kernel with zfs module source in module/zfs/

** Patch added: "zfs-fix-zpool-import-bug-with-nested-pools.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636517/+attachment/4767015/+files/zfs-fix-zpool-import-bug-with-nested-pools.patch

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

Title:
  zfs: importing zpool with vdev on zvol hangs kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  if a zvol of an existing, already imported zpool is a vdev of another
  zpool, a call to "zpool import" will everything zfs related. the stack
  trace is as follows:

  [] taskq_wait+0x74/0xe0 [spl]
  [] taskq_destroy+0x4b/0x100 [spl]
  [] vdev_open_children+0x12d/0x180 [zfs]
  [] vdev_root_open+0x3c/0xc0 [zfs]
  [] vdev_open+0xf5/0x4d0 [zfs]
  [] spa_load+0x39e/0x1c60 [zfs]
  [] spa_tryimport+0xad/0x450 [zfs]
  [] zfs_ioc_pool_tryimport+0x64/0xa0 [zfs]
  [] zfsdev_ioctl+0x44b/0x4e0 [zfs]
  [] do_vfs_ioctl+0x29f/0x490
  [] SyS_ioctl+0x79/0x90
  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [] 0x

  I traced this back to 193fb6a2c94fab8eb8ce70a5da4d21c7d4023bee (merged
  in 4.4.0-6.21), which added a second parameter to lookup_bdev without
  patching the zfs module (which needs to special case the vdev-on-zvol
  case, and uses this exact method only in this special casing code
  path).

  attached you can find the output of "zfs send -R" ing such a zvol
  ("brokenvol.raw"), running "zfs receive POOL/TARGET < FILE" followed
  by "zpool import" should reproduce the hang.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-45-generic 4.4.0-45.66
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 25 15:46 seq
   crw-rw 1 root audio 116, 33 Oct 25 15:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Oct 25 15:49:51 2016
  HibernationDevice: RESUME=/dev/mapper/xenial--vg-swap_1
  InstallationDate: Installed on 2016-10-25 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic 
root=/dev/mapper/hostname--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.7
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.7
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1566465] Re: [regression]: Failed to call clock_adjtime(): Invalid argument

[Fabian Grünbichler]

This seems to be caused by the call to "timeval_inject_offset_valid()"
introduced in kernel/time/ntp.c (in "ntp_validate_timex()") by
2ed8b5bac95a96e2334a6b9bcbe99eabaf83f931. timeval_inject_offset_valid
only handles timevals with microseconds, but systemd-timesyncd uses the
ADJ_NANO mode which stores nanosecond values in tv_usec. upstream 4.5
already has a fix to handle this situation by copying the tv content to
a (temporary) timespec and validating that iff ADJ_NANO is used.

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

Title:
  [regression]: Failed to call clock_adjtime(): Invalid argument

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

Bug description:
  Steps to reproduce:

  1) Force a time delta
  date -s "now - 1 hour"
  2) Restart systemd-timesyncd to have it fix the time
  systemctl restart systemd-timesyncd

  Expected behavior:

  The clock should be back in sync.

  Actual (problematic) behavior:

  The clock stays out of sync because the call to clock_adjtime()
  failed.

  # systemctl status systemd-timesyncd.service 
  ● systemd-timesyncd.service - Network Time Synchronization
 Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
 └─disable-with-time-daemon.conf
 Active: active (running) since Tue 2016-04-05 14:26:25 EDT; 1s ago
   Docs: man:systemd-timesyncd.service(8)
   Main PID: 11567 (systemd-timesyn)
 Status: "Synchronized to time server 172.24.21.1:123 (ntp.ubuntu.com)."
  Tasks: 2 (limit: 512)
 Memory: 260.0K
CPU: 15ms
 CGroup: /system.slice/systemd-timesyncd.service
 └─11567 /lib/systemd/systemd-timesyncd

  Apr 05 14:26:25 simon-laptop systemd[1]: Starting Network Time 
Synchronization...
  Apr 05 14:26:25 simon-laptop systemd[1]: Started Network Time Synchronization.
  Apr 05 14:26:25 simon-laptop systemd-timesyncd[11567]: Failed to call 
clock_adjtime(): Invalid argument
  Apr 05 14:26:25 simon-laptop systemd-timesyncd[11567]: Synchronized to time 
server 172.24.21.1:123 (ntp.ubuntu.com).

  
  This problem doesn't happen when running kernel 4.4.0-16.32. Looking at the 
changelog of 4.4.0-17.33 it could be because of the new feature introduced in 
LP: #1519625.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-17-generic 4.4.0-17.33
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  simon  5198 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Tue Apr  5 14:21:22 2016
  HibernationDevice: RESUME=/dev/mapper/crypt-swap
  MachineType: LENOVO 2516CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-17-generic 
root=/dev/mapper/crypt-xroot ro quiet splash 
cryptopts=target=crypt,source=/dev/sda1,lvm=crypt-xroot possible_cpus=4 
nmi_watchdog=0 kaslr quiet splash 
cryptopts=target=crypt,source=/dev/sda1,lvm=crypt-xroot possible_cpus=4 
nmi_watchdog=0 kaslr vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-17-generic N/A
   linux-backports-modules-4.4.0-17-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET85WW (1.45 )
  dmi.board.name: 2516CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2516CTO
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1560869] Re: Concurrent zfs create and rename operations can lock a zpool completely

[Fabian Grünbichler]

Does not trigger anymore with linux-image-4.4.0-16-generic 4.4.0-16.32 /
zfs.ko v0.6.5.6-0ubuntu1. zfsutils-linux and friends are still on
0.6.5.4-0ubuntu6.

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

Title:
  Concurrent zfs create and rename operations can lock a zpool
  completely

Status in linux package in Ubuntu:
  Incomplete
Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  When doing "zfs create -V" and "zfs rename" operations on the same
  zpool in parallel, there is a high chance for a deadlock leading to a
  complete hang of the zpool in question (i.e., all further zfs
  operations hang indefinitely).

  Attached you find a simple perl script that should trigger the bug
  (the pool variable needs to be set to your pool name), if run in two
  shells at the same time:

  $ for i in `seq 1 100`; do sudo ./zfsrenamebug.pl "A$i"; done

  $ for i in `seq 1 100`; do sudo ./zfsrenamebug.pl "B$i"; done

  Reported upstream in https://github.com/zfsonlinux/zfs/issues/4404 and 
apparently fixed with the linked commits.
  --- 
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=41b79831-ff2c-4d62-8d09-0fd00a3fafad
  InstallationDate: Installed on 2016-03-18 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  IwConfig:
   ens18 no wireless extensions.
   
   lono wireless extensions.
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: zfs-linux
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=ff5bf1a3-8ced-46a8-9e2e-e3e7d0e522c0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.8.2-0-g33fbe13 by qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.5
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.8.2-0-g33fbe13byqemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.5
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1560869] Re: Concurrent zfs create and rename operations can lock a zpool completely

[Fabian Grünbichler]

Should be fixed with upstream version 0.6.5.6, so I guess this can be
closed once that version hits the archive.

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

Title:
  Concurrent zfs create and rename operations can lock a zpool
  completely

Status in linux package in Ubuntu:
  Incomplete
Status in zfs-linux package in Ubuntu:
  New

Bug description:
  When doing "zfs create -V" and "zfs rename" operations on the same
  zpool in parallel, there is a high chance for a deadlock leading to a
  complete hang of the zpool in question (i.e., all further zfs
  operations hang indefinitely).

  Attached you find a simple perl script that should trigger the bug
  (the pool variable needs to be set to your pool name), if run in two
  shells at the same time:

  $ for i in `seq 1 100`; do sudo ./zfsrenamebug.pl "A$i"; done

  $ for i in `seq 1 100`; do sudo ./zfsrenamebug.pl "B$i"; done

  Reported upstream in https://github.com/zfsonlinux/zfs/issues/4404 and 
apparently fixed with the linked commits.
  --- 
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=41b79831-ff2c-4d62-8d09-0fd00a3fafad
  InstallationDate: Installed on 2016-03-18 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  IwConfig:
   ens18 no wireless extensions.
   
   lono wireless extensions.
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: zfs-linux
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=ff5bf1a3-8ced-46a8-9e2e-e3e7d0e522c0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.8.2-0-g33fbe13 by qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.5
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.8.2-0-g33fbe13byqemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.5
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1560869] Re: Concurrent zfs create and rename operations can lock a zpool completely

[Fabian Grünbichler]

Another note: this can also be triggered only with rename operations on
zvols:

$ sudo zfs create -V 4096k pool1/zfsrename 1
$ sudo zfs create -V 4096k pool1/zfsrename 3

and then in two shells in parallel:

$ while : ; do echo "RENAME" `date`; sudo zfs rename pool1/testrename3
pool1/testrename4; sudo zfs rename pool1/testrename4 pool1/testrename3;
done

$ while : ; do echo "RENAME" `date`; sudo zfs rename pool1/testrename1
pool1/testrename2; sudo zfs rename pool1/testrename2 pool1/testrename1;
done

takes a bit longer than with the create rename destroy script from
above, but triggers after 10-15 seconds in the same test VM:

user@test:~$ sudo cat /proc/6338/stack
[] spa_open_common+0x61/0x480 [zfs]
[] spa_open+0x13/0x20 [zfs]
[] pool_status_check.part.24+0x32/0xa0 [zfs]
[] zfsdev_ioctl+0x389/0x4b0 [zfs]
[] do_vfs_ioctl+0x29f/0x490
[] SyS_ioctl+0x79/0x90
[] entry_SYSCALL_64_fastpath+0x16/0x71
[] 0x
user@test:~$ sudo cat /proc/6333/stack
[] cv_wait_common+0x109/0x140 [spl]
[] __cv_wait+0x15/0x20 [spl]
[] txg_wait_synced+0xe5/0x130 [zfs]
[] dsl_sync_task+0x179/0x260 [zfs]
[] dsl_dir_rename+0x5b/0x80 [zfs]
[] zfs_ioc_rename+0x10d/0x120 [zfs]
[] zfsdev_ioctl+0x423/0x4b0 [zfs]
[] do_vfs_ioctl+0x29f/0x490
[] SyS_ioctl+0x79/0x90
[] entry_SYSCALL_64_fastpath+0x16/0x71
[] 0x


** Attachment added: "ps faxl output"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1560869/+attachment/4608435/+files/psfaxl.log

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

Title:
  Concurrent zfs create and rename operations can lock a zpool
  completely

Status in linux package in Ubuntu:
  Incomplete
Status in zfs-linux package in Ubuntu:
  New

Bug description:
  When doing "zfs create -V" and "zfs rename" operations on the same
  zpool in parallel, there is a high chance for a deadlock leading to a
  complete hang of the zpool in question (i.e., all further zfs
  operations hang indefinitely).

  Attached you find a simple perl script that should trigger the bug
  (the pool variable needs to be set to your pool name), if run in two
  shells at the same time:

  $ for i in `seq 1 100`; do sudo ./zfsrenamebug.pl "A$i"; done

  $ for i in `seq 1 100`; do sudo ./zfsrenamebug.pl "B$i"; done

  Reported upstream in https://github.com/zfsonlinux/zfs/issues/4404 and 
apparently fixed with the linked commits.
  --- 
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=41b79831-ff2c-4d62-8d09-0fd00a3fafad
  InstallationDate: Installed on 2016-03-18 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  IwConfig:
   ens18 no wireless extensions.
   
   lono wireless extensions.
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: zfs-linux
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=ff5bf1a3-8ced-46a8-9e2e-e3e7d0e522c0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.8.2-0-g33fbe13 by qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.5
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.8.2-0-g33fbe13byqemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.5
  dmi.sys.vendor: QEMU

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

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