[Kernel-packages] [Bug 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

[Jens Glathe]

Hi @xypron,

my /etc/initramfs-tools/modules is this:

---
pwm_bl
phy_qcom_qmp_pcie
pcie_qcom
phy_qcom
qmp_pcie
phy_qcom_qmp_combo
qrtr
drm-dp-aux-bus
phy_qcom_edp
gpio_sbu_mux
i2c_hid_of
i2c_qcom_geni
pmic_glink_altmode
leds_qcom_lpg
qcom_q6v5_pas
panel-edp
gpucc_sc8280xp
dispcc_sc8280xp
msm
nvme
usb_storage
uas
--

I had severe issues booting from type-c due to late-loading of
qcadsp8280.mbn, therefore I experimented a little until found. I am not
familiar with the installer at all, so I'm afraid I'm no help there. But
the loading of the firmwares goes hand in hand with my /etc/initramfs-
tools/hooks/x13s-firmware script:

-
#!/bin/sh

set -e

PREREQ=""

prereqs()
{
echo "$PREREQ"
}

case \\$1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac

. /usr/share/initramfs-tools/hook-functions

mv
/lib/firmware/updates/qcom/sc8280xp/LENOVO/21BX/qcadsp8280.mbn.disabled
/lib/firmware/updates/qcom/sc8280xp/LENOVO/21BX/qcadsp8280.mbn

# Define a list of firmware files to be included
FIRMWARE_FILES="\
/lib/firmware/updates/qcom/sc8280xp/LENOVO/21BX/qcadsp8280.mbn \
/lib/firmware/updates/qcom/sc8280xp/LENOVO/21BX/qccdsp8280.mbn \
/lib/firmware/updates/qcom/sc8280xp/LENOVO/21BX/qcdxkmsuc8280.mbn \
/lib/firmware/updates/qcom/sc8280xp/LENOVO/21BX/qcvss8280.mbn \
/lib/firmware/updates/qcom/sc8280xp/LENOVO/21BX/qcslpi8280.mbn \
/lib/firmware/qcom/a660_sqe.fw.zst \
/lib/firmware/qcom/a660_gmu.bin.zst"

# Copy each firmware file to initramfs
for file in $FIRMWARE_FILES; do
dir=$(dirname "$file")
mkdir -p "${DESTDIR}/${dir}"
cp "${file}" "${DESTDIR}/${dir}/"
done

mv /lib/firmware/updates/qcom/sc8280xp/LENOVO/21BX/qcadsp8280.mbn
/lib/firmware/updates/qcom/sc8280xp/LENOVO/21BX/qcadsp8280.mbn.disabled

---

This ensures the crucial files (and some not so crucial) are in the
initramfs and accessible before rootfs can be mounted. My boot tests
found that you actually run into trouble occasionally when you:

- have a slow boot device, like the stick plugged in swapped condition (then 
it's USB-2 only)
- have qcadsp8280.mbn in the rootfs as well. "Late" attempts to load this blob 
(after mounting rootfs from type-c) will lead to the [VBUS 
issue](https://gitlab.com/postmarketOS/pmaports/-/blob/master/device/testing/firmware-lenovo-yoga-5g/APKBUILD?ref_type=heads#L44-46)
 which I experienced for a few ... weeks ... and pulled my hair out. 
For reference: https://github.com/jglathe/linux_ms_dev_kit/discussions/14 There 
is also an X13s image that boots reliably from type-c: 
https://drive.google.com/file/d/1e8LA6o-EKKet3_sCQqXR4lOVE_TgOVNI/view?usp=sharing
 But, danger. It is deliberately rooted, root pw is FsecuritY! and can be 
reached via ssh. It is for debug purposes.

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

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

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: 

[Kernel-packages] [Bug 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

[Jens Glathe]

Hmm I see two issues here.

qcom_q6v5_pas should be in /etc/initramfs-tools/modules (it is in mine), or 
loading of adsp and cdsp firmware will be deferred until rootfs is mounted, 
with the odd VBUS interruption on type-c connectors at a moment where this will 
result in an inaccessible rootfs afterwards.
The endless loop is something I'm not seeing with my builds, looked like 
something IOMMU and DWC3 that were clashing.

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

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

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2049195] Re: Wifi missing after upgrade to 6.5 kernel

[Dr. Jens Harbott]

I can confirm that with 6.5.0.17.17~22.04.9 the issue no longer appears
for me, too.

** Changed in: linux-meta-hwe-6.5 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Wifi missing after upgrade to 6.5 kernel

Status in linux-meta-hwe-6.5 package in Ubuntu:
  Fix Released

Bug description:
  After upgrading the HWE kernel from 6.2 to 6.5 the wifi interface is
  missing.

  Hardware: Framework Laptop
  $ lspci | grep Network
  aa:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 
160MHz (rev 1a)

  With 6.2:
  $ sudo ethtool -i wlp170s0
  driver: iwlwifi
  version: 6.2.0-39-generic
  firmware-version: 72.a764baac.0 ty-a0-gf-a0-72.uc

  Messages from journalctl that seem relevant:
  Jan 12 12:21:25 fw1 kernel: iwlwifi :aa:00.0: Detected Intel(R) Wi-Fi 6 
AX210 160MHz, REV=0x420
  Jan 12 12:21:25 fw1 kernel: iwlwifi :aa:00.0: WRT: Invalid buffer 
destination

  and then some backtraces, result of

  journalctl -b-1 | grep "kernel: " > kernel-log.txt

  attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic-hwe-22.04 6.5.0.14.14~22.04.7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 12 12:32:19 2024
  InstallationDate: Installed on 2022-06-29 (561 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2049195/+subscriptions


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

[Kernel-packages] [Bug 2049195] [NEW] Wifi missing after upgrade to 6.5 kernel

[Dr. Jens Harbott]

Public bug reported:

After upgrading the HWE kernel from 6.2 to 6.5 the wifi interface is
missing.

Hardware: Framework Laptop
$ lspci | grep Network
aa:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz 
(rev 1a)

With 6.2:
$ sudo ethtool -i wlp170s0
driver: iwlwifi
version: 6.2.0-39-generic
firmware-version: 72.a764baac.0 ty-a0-gf-a0-72.uc

Messages from journalctl that seem relevant:
Jan 12 12:21:25 fw1 kernel: iwlwifi :aa:00.0: Detected Intel(R) Wi-Fi 6 
AX210 160MHz, REV=0x420
Jan 12 12:21:25 fw1 kernel: iwlwifi :aa:00.0: WRT: Invalid buffer 
destination

and then some backtraces, result of

journalctl -b-1 | grep "kernel: " > kernel-log.txt

attached.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-generic-hwe-22.04 6.5.0.14.14~22.04.7
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 12 12:32:19 2024
InstallationDate: Installed on 2022-06-29 (561 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-meta-hwe-6.5
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-meta-hwe-6.5 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy wayland-session

** Attachment added: "kernel-log.txt"
   
https://bugs.launchpad.net/bugs/2049195/+attachment/5738725/+files/kernel-log.txt

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

Title:
  Wifi missing after upgrade to 6.5 kernel

Status in linux-meta-hwe-6.5 package in Ubuntu:
  New

Bug description:
  After upgrading the HWE kernel from 6.2 to 6.5 the wifi interface is
  missing.

  Hardware: Framework Laptop
  $ lspci | grep Network
  aa:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 
160MHz (rev 1a)

  With 6.2:
  $ sudo ethtool -i wlp170s0
  driver: iwlwifi
  version: 6.2.0-39-generic
  firmware-version: 72.a764baac.0 ty-a0-gf-a0-72.uc

  Messages from journalctl that seem relevant:
  Jan 12 12:21:25 fw1 kernel: iwlwifi :aa:00.0: Detected Intel(R) Wi-Fi 6 
AX210 160MHz, REV=0x420
  Jan 12 12:21:25 fw1 kernel: iwlwifi :aa:00.0: WRT: Invalid buffer 
destination

  and then some backtraces, result of

  journalctl -b-1 | grep "kernel: " > kernel-log.txt

  attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic-hwe-22.04 6.5.0.14.14~22.04.7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 12 12:32:19 2024
  InstallationDate: Installed on 2022-06-29 (561 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2049195/+subscriptions


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

[Kernel-packages] [Bug 1942260] Re: compress firmware in /lib/firmware

[Jens Glathe]

That kernel option was not easy to find, but it's working now.

FW_LOADER_COMPRESS=y
FW_LOADER_COMPRESS_ZSTD=y

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

Title:
  compress firmware in /lib/firmware

Status in firmware-sof package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware-raspi package in Ubuntu:
  Confirmed
Status in firmware-sof source package in Mantic:
  Fix Released
Status in initramfs-tools source package in Mantic:
  Fix Released
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-firmware-raspi source package in Mantic:
  Confirmed

Bug description:
  -- initramfs-tools

  [Impact]

   * linux supports xz compressed linux-firmware which saves disk space.
  In focal, initramfs-tools only knows how to included uncompressed
  firmware files (even when kernel supports loading compressed ones).
  Newer releases of linux-firmware may use compressed firmware files
  only, in such cases it would be nice for focal's initramfs-tools to
  support compressed firmware files in case of partial or incomplete
  upgrades (i.e. linux-firmware force installed or upgraded, without
  newer initramfs-tools). The proposed changes to initramfs-tools are
  backwards and forwards compatible, they prefer to include uncompressed
  firmware files; and if missing, include compressed firmware files in
  their uncompressed form. Thus maintaining compatibility with any
  kernels, irrespective of compressed/uncompressed firmware inputs.

  [Test Plan]

   * Compress all files shipped by linux-firmware with xz

   * Rebuild initrd

   * Check that all the same firmware files are still included in the
  initramfs, in their uncompressed form as before

  [Where problems could occur]

   * This SRU is precautionary to prevent accidental installation of
  compressed linux-firmware from generating incorrect initramfs. It
  should be noted that whilst initramfs-tools would create a compatible
  initramfs with any kernels, pre-v5.3 kernels do not support xz
  compressed firmware files at runtime. Mixing this new initramfs with
  compressed firmwares and pre 5.3 kernels may lead to expectations of
  supporting compressed firmware files with them only working at initrd
  stage and not at runtime.

  [Other Info]
  Original bug report

  Some facts:
   - The linux kernel has supported loading xz compressed firmware since 5.3
   - The size of /lib/firmware in impish is ~650Mb (and growing)
   - The compressed size of firmware could be ~230Mb

  It would be nice to install compressed firmware to save space.

  Here are the plans from the Fedora project:
  https://fedoraproject.org/wiki/Changes/CompressKernelFirmware

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


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

[Kernel-packages] [Bug 2009522] Re: Upgrade Kernel 5.19.0-35-generic [Sound Blaster Recon3D / Z-Series] not detected anymore

[Jens]

the same problem here on kernel
5.19.0-35-generic #36-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 3 18:36:56 UTC 2023 
x86_64 x86_64 x86_64 GNU/Linux

Ubuntu 22.04 LTS and Ubuntu 22.10

the sound card does not work.
the sound card works without problems on kernel 5.19.0-32

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

Title:
  Upgrade Kernel 5.19.0-35-generic [Sound Blaster Recon3D / Z-Series]
  not detected anymore

Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed

Bug description:
  Upgrade Kernel 5.19.0-35-generic [Sound Blaster Recon3D / Z-Series] not 
detected anymore 
  Operating System: Kubuntu 22.10
  KDE Plasma Version: 5.27.2
  KDE Frameworks Version: 5.103.0
  Qt Version: 5.15.6
  Kernel Version: 5.19.0-35-generic (64-bit)
  Graphics Platform: X11
  Processors: 16 × Intel® Core™ i9-9900KF CPU @ 3.60GHz
  Memory: 31.3 GiB of RAM
  Graphics Processor: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2
  Manufacturer: Gigabyte Technology Co., Ltd.
  Product Name: Z390 UD

  See also https://askubuntu.com/questions/1457574/upgrade-
  kernel-5-19-0-35-generic-sound-blaster-recon3d-z-series-not-detected

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


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

[Kernel-packages] [Bug 2001545] Re: i915: repetable Kernel Oops after resuming from standby

[Jens]

e kernel: [164295.136126] RBP: b98e88c47970 R08: 
 R09: 
  Jan  3 17:16:33 linuxkiste kernel: [164295.136127] R10: 940e24fc1000 R11: 
940e090c5ad4 R12: e2fc5100
  Jan  3 17:16:33 linuxkiste kernel: [164295.136129] R13: 000a R14: 
 R15: 0230
  Jan  3 17:16:33 linuxkiste kernel: [164295.136130] FS:  
7f3c96764340() GS:94100ea8() knlGS:
  Jan  3 17:16:33 linuxkiste kernel: [164295.136131] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  3 17:16:33 linuxkiste kernel: [164295.136133] CR2: e2fc5108 CR3: 
0001f49d8001 CR4: 001706e0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jens  22753 F pulseaudio
   /dev/snd/controlC1:  jens  22753 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: KDE neon 22.04
  InstallationDate: Installed on 2022-11-26 (43 days ago)
  InstallationMedia: neon user "Jammy" - Build amd64 LIVE Binary 20221117-07:30
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic 
root=UUID=0c647c08-756d-408d-b730-0f54ea1f73d0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-57-generic N/A
   linux-backports-modules-5.15.0-57-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  jammy
  Uname: Linux 5.15.0-57-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: False
  dmi.bios.date: 04/21/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CSM-B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:br4.6:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnCSM-B85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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


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

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

[Jens]

4.600397]  ? irqentry_exit+0x1d/0x30
  Jan  3 17:16:33 linuxkiste kernel: [164294.600399]  ? 
exc_page_fault+0x89/0x170
  Jan  3 17:16:33 linuxkiste kernel: [164294.600402]  
entry_SYSCALL_64_after_hwframe+0x61/0xcb
  Jan  3 17:16:33 linuxkiste kernel: [164294.600406] RIP: 0033:0x7f3c97b93aff
  Jan  3 17:16:33 linuxkiste kernel: [164294.600408] Code: 00 48 89 44 24 18 31 
c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 
24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 
2b 04 25 28 00
  Jan  3 17:16:33 linuxkiste kernel: [164294.600410] RSP: 002b:7fffc65150c0 
EFLAGS: 0246 ORIG_RAX: 0010
  Jan  3 17:16:33 linuxkiste kernel: [164294.600412] RAX: ffda RBX: 
7fffc6515250 RCX: 7f3c97b93aff
  Jan  3 17:16:33 linuxkiste kernel: [164294.600413] RDX: 7fffc6515250 RSI: 
40406469 RDI: 0018
  Jan  3 17:16:33 linuxkiste kernel: [164294.600414] RBP: 0018 R08: 
0001 R09: 0008
  Jan  3 17:16:33 linuxkiste kernel: [164294.600416] R10: 113c0f80 R11: 
0246 R12: 7fffc6515250
  Jan  3 17:16:33 linuxkiste kernel: [164294.600417] R13:  R14: 
7f3c89c82bb8 R15: 10372000
  Jan  3 17:16:33 linuxkiste kernel: [164294.600419]  
  Jan  3 17:16:33 linuxkiste kernel: [164294.600420] Modules linked in: tls 
ntfs3 uas usb_storage nls_utf8 cifs cifs_arc4 cifs_md4 fscache netfs 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm cmac algif_hash algif_skcipher 
af_alg bnep binfmt_misc mei_hdcp intel_rapl_msr intel_rapl_common 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm rapl 
snd_hda_codec_realtek intel_cstate snd_hda_codec_generic ledtrig_audio 
snd_hda_codec_hdmi nls_iso8859_1 snd_hda_intel joydev snd_intel_dspcfg btusb 
at24 snd_intel_sdw_acpi snd_hda_codec snd_hda_core btrtl snd_hwdep btbcm 
snd_pcm input_leds snd_seq_midi btintel snd_seq_midi_event bluetooth 
snd_rawmidi ecdh_generic ecc snd_seq mei_me snd_seq_device snd_timer snd mei 
soundcore mac_hid intel_smartconnect sch_fq_codel msr parport_pc ppdev lp 
parport ramoops reed_solomon pstore_blk pstore_zone efi_pstore ip_tables 
x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c 
dm_crypt hid_generic usbhid hid i915 i2c_algo_bit t
 tm drm_kms_helper syscopyarea sysfillrect
  Jan  3 17:16:33 linuxkiste kernel: [164294.600481]  sysimgblt fb_sys_fops cec 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i2c_i801 aesni_intel ahci 
rc_core crypto_simd r8169 mxm_wmi cryptd i2c_smbus libahci lpc_ich realtek drm 
xhci_pci xhci_pci_renesas wmi video
  Jan  3 17:16:33 linuxkiste kernel: [164294.600494] CR2: e2fc5108
  Jan  3 17:16:33 linuxkiste kernel: [164294.600496] ---[ end trace 
c11e39619ebb9be7 ]---
  Jan  3 17:16:33 linuxkiste kernel: [164295.136110] RIP: 0010:kfree+0x68/0x250
  Jan  3 17:16:33 linuxkiste kernel: [164295.136119] Code: 80 49 01 dc 0f 82 f2 
01 00 00 48 c7 c0 00 00 00 80 48 2b 05 42 63 39 01 49 01 c4 49 c1 ec 0c 49 c1 
e4 06 4c 03 25 20 63 39 01 <49> 8b 44 24 08 48 8d 50 ff a8 01 4c 0f 45 e2 49 8b 
54 24 08 48 8d
  Jan  3 17:16:33 linuxkiste kernel: [164295.136121] RSP: 0018:b98e88c47930 
EFLAGS: 00010286
  Jan  3 17:16:33 linuxkiste kernel: [164295.136123] RAX: 6bf38000 RBX: 
40c0 RCX: 00392c14
  Jan  3 17:16:33 linuxkiste kernel: [164295.136125] RDX: b98e8000 RSI: 
a04d669e RDI: 40c0
  Jan  3 17:16:33 linuxkiste kernel: [164295.136126] RBP: b98e88c47970 R08: 
 R09: 
  Jan  3 17:16:33 linuxkiste kernel: [164295.136127] R10: 940e24fc1000 R11: 
940e090c5ad4 R12: e2fc5100
  Jan  3 17:16:33 linuxkiste kernel: [164295.136129] R13: 000a R14: 
 R15: 0230
  Jan  3 17:16:33 linuxkiste kernel: [164295.136130] FS:  
7f3c96764340() GS:94100ea8() knlGS:
  Jan  3 17:16:33 linuxkiste kernel: [164295.136131] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  3 17:16:33 linuxkiste kernel: [164295.136133] CR2: e2fc5108 CR3: 
0001f49d8001 CR4: 001706e0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USER    PID ACCESS COMMAND
   /dev/snd/controlC0:  jens  22753 F pulseaudio
   /dev/snd/controlC1:  jens  22753 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: KDE neon 22.04
  InstallationDate: Installed on 2022-11-26 (43 days ago)
  InstallationMedia: neon user "Jammy" - Build amd64 LIVE Binary 20221117-07:30
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic 
root=UUID=0c647c0

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

[Jens]

4.600397]  ? irqentry_exit+0x1d/0x30
  Jan  3 17:16:33 linuxkiste kernel: [164294.600399]  ? 
exc_page_fault+0x89/0x170
  Jan  3 17:16:33 linuxkiste kernel: [164294.600402]  
entry_SYSCALL_64_after_hwframe+0x61/0xcb
  Jan  3 17:16:33 linuxkiste kernel: [164294.600406] RIP: 0033:0x7f3c97b93aff
  Jan  3 17:16:33 linuxkiste kernel: [164294.600408] Code: 00 48 89 44 24 18 31 
c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 
24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 
2b 04 25 28 00
  Jan  3 17:16:33 linuxkiste kernel: [164294.600410] RSP: 002b:7fffc65150c0 
EFLAGS: 0246 ORIG_RAX: 0010
  Jan  3 17:16:33 linuxkiste kernel: [164294.600412] RAX: ffda RBX: 
7fffc6515250 RCX: 7f3c97b93aff
  Jan  3 17:16:33 linuxkiste kernel: [164294.600413] RDX: 7fffc6515250 RSI: 
40406469 RDI: 0018
  Jan  3 17:16:33 linuxkiste kernel: [164294.600414] RBP: 0018 R08: 
0001 R09: 0008
  Jan  3 17:16:33 linuxkiste kernel: [164294.600416] R10: 113c0f80 R11: 
0246 R12: 7fffc6515250
  Jan  3 17:16:33 linuxkiste kernel: [164294.600417] R13:  R14: 
7f3c89c82bb8 R15: 10372000
  Jan  3 17:16:33 linuxkiste kernel: [164294.600419]  
  Jan  3 17:16:33 linuxkiste kernel: [164294.600420] Modules linked in: tls 
ntfs3 uas usb_storage nls_utf8 cifs cifs_arc4 cifs_md4 fscache netfs 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm cmac algif_hash algif_skcipher 
af_alg bnep binfmt_misc mei_hdcp intel_rapl_msr intel_rapl_common 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm rapl 
snd_hda_codec_realtek intel_cstate snd_hda_codec_generic ledtrig_audio 
snd_hda_codec_hdmi nls_iso8859_1 snd_hda_intel joydev snd_intel_dspcfg btusb 
at24 snd_intel_sdw_acpi snd_hda_codec snd_hda_core btrtl snd_hwdep btbcm 
snd_pcm input_leds snd_seq_midi btintel snd_seq_midi_event bluetooth 
snd_rawmidi ecdh_generic ecc snd_seq mei_me snd_seq_device snd_timer snd mei 
soundcore mac_hid intel_smartconnect sch_fq_codel msr parport_pc ppdev lp 
parport ramoops reed_solomon pstore_blk pstore_zone efi_pstore ip_tables 
x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c 
dm_crypt hid_generic usbhid hid i915 i2c_algo_bit t
 tm drm_kms_helper syscopyarea sysfillrect
  Jan  3 17:16:33 linuxkiste kernel: [164294.600481]  sysimgblt fb_sys_fops cec 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i2c_i801 aesni_intel ahci 
rc_core crypto_simd r8169 mxm_wmi cryptd i2c_smbus libahci lpc_ich realtek drm 
xhci_pci xhci_pci_renesas wmi video
  Jan  3 17:16:33 linuxkiste kernel: [164294.600494] CR2: e2fc5108
  Jan  3 17:16:33 linuxkiste kernel: [164294.600496] ---[ end trace 
c11e39619ebb9be7 ]---
  Jan  3 17:16:33 linuxkiste kernel: [164295.136110] RIP: 0010:kfree+0x68/0x250
  Jan  3 17:16:33 linuxkiste kernel: [164295.136119] Code: 80 49 01 dc 0f 82 f2 
01 00 00 48 c7 c0 00 00 00 80 48 2b 05 42 63 39 01 49 01 c4 49 c1 ec 0c 49 c1 
e4 06 4c 03 25 20 63 39 01 <49> 8b 44 24 08 48 8d 50 ff a8 01 4c 0f 45 e2 49 8b 
54 24 08 48 8d
  Jan  3 17:16:33 linuxkiste kernel: [164295.136121] RSP: 0018:b98e88c47930 
EFLAGS: 00010286
  Jan  3 17:16:33 linuxkiste kernel: [164295.136123] RAX: 6bf38000 RBX: 
40c0 RCX: 00392c14
  Jan  3 17:16:33 linuxkiste kernel: [164295.136125] RDX: b98e8000 RSI: 
a04d669e RDI: 40c0
  Jan  3 17:16:33 linuxkiste kernel: [164295.136126] RBP: b98e88c47970 R08: 
 R09: 
  Jan  3 17:16:33 linuxkiste kernel: [164295.136127] R10: 940e24fc1000 R11: 
940e090c5ad4 R12: e2fc5100
  Jan  3 17:16:33 linuxkiste kernel: [164295.136129] R13: 000a R14: 
 R15: 0230
  Jan  3 17:16:33 linuxkiste kernel: [164295.136130] FS:  
7f3c96764340() GS:94100ea8() knlGS:
  Jan  3 17:16:33 linuxkiste kernel: [164295.136131] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  3 17:16:33 linuxkiste kernel: [164295.136133] CR2: e2fc5108 CR3: 
0001f49d8001 CR4: 001706e0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USER    PID ACCESS COMMAND
   /dev/snd/controlC0:  jens  22753 F pulseaudio
   /dev/snd/controlC1:  jens  22753 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: KDE neon 22.04
  InstallationDate: Installed on 2022-11-26 (43 days ago)
  InstallationMedia: neon user "Jammy" - Build amd64 LIVE Binary 20221117-07:30
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic 
root=UUID=0c647c0

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

[Jens]

97]  ? irqentry_exit+0x1d/0x30
  Jan  3 17:16:33 linuxkiste kernel: [164294.600399]  ? 
exc_page_fault+0x89/0x170
  Jan  3 17:16:33 linuxkiste kernel: [164294.600402]  
entry_SYSCALL_64_after_hwframe+0x61/0xcb
  Jan  3 17:16:33 linuxkiste kernel: [164294.600406] RIP: 0033:0x7f3c97b93aff
  Jan  3 17:16:33 linuxkiste kernel: [164294.600408] Code: 00 48 89 44 24 18 31 
c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 
24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 
2b 04 25 28 00
  Jan  3 17:16:33 linuxkiste kernel: [164294.600410] RSP: 002b:7fffc65150c0 
EFLAGS: 0246 ORIG_RAX: 0010
  Jan  3 17:16:33 linuxkiste kernel: [164294.600412] RAX: ffda RBX: 
7fffc6515250 RCX: 7f3c97b93aff
  Jan  3 17:16:33 linuxkiste kernel: [164294.600413] RDX: 7fffc6515250 RSI: 
40406469 RDI: 0018
  Jan  3 17:16:33 linuxkiste kernel: [164294.600414] RBP: 0018 R08: 
0001 R09: 0008
  Jan  3 17:16:33 linuxkiste kernel: [164294.600416] R10: 113c0f80 R11: 
0246 R12: 7fffc6515250
  Jan  3 17:16:33 linuxkiste kernel: [164294.600417] R13:  R14: 
7f3c89c82bb8 R15: 10372000
  Jan  3 17:16:33 linuxkiste kernel: [164294.600419]  
  Jan  3 17:16:33 linuxkiste kernel: [164294.600420] Modules linked in: tls 
ntfs3 uas usb_storage nls_utf8 cifs cifs_arc4 cifs_md4 fscache netfs 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm cmac algif_hash algif_skcipher 
af_alg bnep binfmt_misc mei_hdcp intel_rapl_msr intel_rapl_common 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm rapl 
snd_hda_codec_realtek intel_cstate snd_hda_codec_generic ledtrig_audio 
snd_hda_codec_hdmi nls_iso8859_1 snd_hda_intel joydev snd_intel_dspcfg btusb 
at24 snd_intel_sdw_acpi snd_hda_codec snd_hda_core btrtl snd_hwdep btbcm 
snd_pcm input_leds snd_seq_midi btintel snd_seq_midi_event bluetooth 
snd_rawmidi ecdh_generic ecc snd_seq mei_me snd_seq_device snd_timer snd mei 
soundcore mac_hid intel_smartconnect sch_fq_codel msr parport_pc ppdev lp 
parport ramoops reed_solomon pstore_blk pstore_zone efi_pstore ip_tables 
x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c 
dm_crypt hid_generic usbhid hid i915 i2c_algo_bit t
 tm drm_kms_helper syscopyarea sysfillrect
  Jan  3 17:16:33 linuxkiste kernel: [164294.600481]  sysimgblt fb_sys_fops cec 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i2c_i801 aesni_intel ahci 
rc_core crypto_simd r8169 mxm_wmi cryptd i2c_smbus libahci lpc_ich realtek drm 
xhci_pci xhci_pci_renesas wmi video
  Jan  3 17:16:33 linuxkiste kernel: [164294.600494] CR2: e2fc5108
  Jan  3 17:16:33 linuxkiste kernel: [164294.600496] ---[ end trace 
c11e39619ebb9be7 ]---
  Jan  3 17:16:33 linuxkiste kernel: [164295.136110] RIP: 0010:kfree+0x68/0x250
  Jan  3 17:16:33 linuxkiste kernel: [164295.136119] Code: 80 49 01 dc 0f 82 f2 
01 00 00 48 c7 c0 00 00 00 80 48 2b 05 42 63 39 01 49 01 c4 49 c1 ec 0c 49 c1 
e4 06 4c 03 25 20 63 39 01 <49> 8b 44 24 08 48 8d 50 ff a8 01 4c 0f 45 e2 49 8b 
54 24 08 48 8d
  Jan  3 17:16:33 linuxkiste kernel: [164295.136121] RSP: 0018:b98e88c47930 
EFLAGS: 00010286
  Jan  3 17:16:33 linuxkiste kernel: [164295.136123] RAX: 6bf38000 RBX: 
40c0 RCX: 00392c14
  Jan  3 17:16:33 linuxkiste kernel: [164295.136125] RDX: b98e8000 RSI: 
a04d669e RDI: 40c0
  Jan  3 17:16:33 linuxkiste kernel: [164295.136126] RBP: b98e88c47970 R08: 
 R09: 
  Jan  3 17:16:33 linuxkiste kernel: [164295.136127] R10: 940e24fc1000 R11: 
940e090c5ad4 R12: e2fc5100
  Jan  3 17:16:33 linuxkiste kernel: [164295.136129] R13: 000a R14: 
 R15: 0230
  Jan  3 17:16:33 linuxkiste kernel: [164295.136130] FS:  
7f3c96764340() GS:94100ea8() knlGS:
  Jan  3 17:16:33 linuxkiste kernel: [164295.136131] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  3 17:16:33 linuxkiste kernel: [164295.136133] CR2: e2fc5108 CR3: 
0001f49d8001 CR4: 001706e0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USER    PID ACCESS COMMAND
   /dev/snd/controlC0:  jens  22753 F pulseaudio
   /dev/snd/controlC1:  jens  22753 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: KDE neon 22.04
  InstallationDate: Installed on 2022-11-26 (43 days ago)
  InstallationMedia: neon user "Jammy" - Build amd64 LIVE Binary 20221117-07:30
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic 
root=UUID=0c647c08-756d-408d-b730-0f54ea

[Kernel-packages] [Bug 2001545] Lspci-vt.txt

[Jens]

164294.600397]  ? irqentry_exit+0x1d/0x30
  Jan  3 17:16:33 linuxkiste kernel: [164294.600399]  ? 
exc_page_fault+0x89/0x170
  Jan  3 17:16:33 linuxkiste kernel: [164294.600402]  
entry_SYSCALL_64_after_hwframe+0x61/0xcb
  Jan  3 17:16:33 linuxkiste kernel: [164294.600406] RIP: 0033:0x7f3c97b93aff
  Jan  3 17:16:33 linuxkiste kernel: [164294.600408] Code: 00 48 89 44 24 18 31 
c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 
24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 
2b 04 25 28 00
  Jan  3 17:16:33 linuxkiste kernel: [164294.600410] RSP: 002b:7fffc65150c0 
EFLAGS: 0246 ORIG_RAX: 0010
  Jan  3 17:16:33 linuxkiste kernel: [164294.600412] RAX: ffda RBX: 
7fffc6515250 RCX: 7f3c97b93aff
  Jan  3 17:16:33 linuxkiste kernel: [164294.600413] RDX: 7fffc6515250 RSI: 
40406469 RDI: 0018
  Jan  3 17:16:33 linuxkiste kernel: [164294.600414] RBP: 0018 R08: 
0001 R09: 0008
  Jan  3 17:16:33 linuxkiste kernel: [164294.600416] R10: 113c0f80 R11: 
0246 R12: 7fffc6515250
  Jan  3 17:16:33 linuxkiste kernel: [164294.600417] R13:  R14: 
7f3c89c82bb8 R15: 10372000
  Jan  3 17:16:33 linuxkiste kernel: [164294.600419]  
  Jan  3 17:16:33 linuxkiste kernel: [164294.600420] Modules linked in: tls 
ntfs3 uas usb_storage nls_utf8 cifs cifs_arc4 cifs_md4 fscache netfs 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm cmac algif_hash algif_skcipher 
af_alg bnep binfmt_misc mei_hdcp intel_rapl_msr intel_rapl_common 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm rapl 
snd_hda_codec_realtek intel_cstate snd_hda_codec_generic ledtrig_audio 
snd_hda_codec_hdmi nls_iso8859_1 snd_hda_intel joydev snd_intel_dspcfg btusb 
at24 snd_intel_sdw_acpi snd_hda_codec snd_hda_core btrtl snd_hwdep btbcm 
snd_pcm input_leds snd_seq_midi btintel snd_seq_midi_event bluetooth 
snd_rawmidi ecdh_generic ecc snd_seq mei_me snd_seq_device snd_timer snd mei 
soundcore mac_hid intel_smartconnect sch_fq_codel msr parport_pc ppdev lp 
parport ramoops reed_solomon pstore_blk pstore_zone efi_pstore ip_tables 
x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c 
dm_crypt hid_generic usbhid hid i915 i2c_algo_bit t
 tm drm_kms_helper syscopyarea sysfillrect
  Jan  3 17:16:33 linuxkiste kernel: [164294.600481]  sysimgblt fb_sys_fops cec 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i2c_i801 aesni_intel ahci 
rc_core crypto_simd r8169 mxm_wmi cryptd i2c_smbus libahci lpc_ich realtek drm 
xhci_pci xhci_pci_renesas wmi video
  Jan  3 17:16:33 linuxkiste kernel: [164294.600494] CR2: e2fc5108
  Jan  3 17:16:33 linuxkiste kernel: [164294.600496] ---[ end trace 
c11e39619ebb9be7 ]---
  Jan  3 17:16:33 linuxkiste kernel: [164295.136110] RIP: 0010:kfree+0x68/0x250
  Jan  3 17:16:33 linuxkiste kernel: [164295.136119] Code: 80 49 01 dc 0f 82 f2 
01 00 00 48 c7 c0 00 00 00 80 48 2b 05 42 63 39 01 49 01 c4 49 c1 ec 0c 49 c1 
e4 06 4c 03 25 20 63 39 01 <49> 8b 44 24 08 48 8d 50 ff a8 01 4c 0f 45 e2 49 8b 
54 24 08 48 8d
  Jan  3 17:16:33 linuxkiste kernel: [164295.136121] RSP: 0018:b98e88c47930 
EFLAGS: 00010286
  Jan  3 17:16:33 linuxkiste kernel: [164295.136123] RAX: 6bf38000 RBX: 
40c0 RCX: 00392c14
  Jan  3 17:16:33 linuxkiste kernel: [164295.136125] RDX: b98e8000 RSI: 
a04d669e RDI: 40c0
  Jan  3 17:16:33 linuxkiste kernel: [164295.136126] RBP: b98e88c47970 R08: 
 R09: 
  Jan  3 17:16:33 linuxkiste kernel: [164295.136127] R10: 940e24fc1000 R11: 
940e090c5ad4 R12: e2fc5100
  Jan  3 17:16:33 linuxkiste kernel: [164295.136129] R13: 000a R14: 
 R15: 0230
  Jan  3 17:16:33 linuxkiste kernel: [164295.136130] FS:  
7f3c96764340() GS:94100ea8() knlGS:
  Jan  3 17:16:33 linuxkiste kernel: [164295.136131] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  3 17:16:33 linuxkiste kernel: [164295.136133] CR2: e2fc5108 CR3: 
0001f49d8001 CR4: 001706e0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USER    PID ACCESS COMMAND
   /dev/snd/controlC0:  jens  22753 F pulseaudio
   /dev/snd/controlC1:  jens  22753 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: KDE neon 22.04
  InstallationDate: Installed on 2022-11-26 (43 days ago)
  InstallationMedia: neon user "Jammy" - Build amd64 LIVE Binary 20221117-07:30
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic 
root=UUID=0c647c0

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

[Jens]

97]  ? irqentry_exit+0x1d/0x30
  Jan  3 17:16:33 linuxkiste kernel: [164294.600399]  ? 
exc_page_fault+0x89/0x170
  Jan  3 17:16:33 linuxkiste kernel: [164294.600402]  
entry_SYSCALL_64_after_hwframe+0x61/0xcb
  Jan  3 17:16:33 linuxkiste kernel: [164294.600406] RIP: 0033:0x7f3c97b93aff
  Jan  3 17:16:33 linuxkiste kernel: [164294.600408] Code: 00 48 89 44 24 18 31 
c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 
24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 
2b 04 25 28 00
  Jan  3 17:16:33 linuxkiste kernel: [164294.600410] RSP: 002b:7fffc65150c0 
EFLAGS: 0246 ORIG_RAX: 0010
  Jan  3 17:16:33 linuxkiste kernel: [164294.600412] RAX: ffda RBX: 
7fffc6515250 RCX: 7f3c97b93aff
  Jan  3 17:16:33 linuxkiste kernel: [164294.600413] RDX: 7fffc6515250 RSI: 
40406469 RDI: 0018
  Jan  3 17:16:33 linuxkiste kernel: [164294.600414] RBP: 0018 R08: 
0001 R09: 0008
  Jan  3 17:16:33 linuxkiste kernel: [164294.600416] R10: 113c0f80 R11: 
0246 R12: 7fffc6515250
  Jan  3 17:16:33 linuxkiste kernel: [164294.600417] R13:  R14: 
7f3c89c82bb8 R15: 10372000
  Jan  3 17:16:33 linuxkiste kernel: [164294.600419]  
  Jan  3 17:16:33 linuxkiste kernel: [164294.600420] Modules linked in: tls 
ntfs3 uas usb_storage nls_utf8 cifs cifs_arc4 cifs_md4 fscache netfs 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm cmac algif_hash algif_skcipher 
af_alg bnep binfmt_misc mei_hdcp intel_rapl_msr intel_rapl_common 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm rapl 
snd_hda_codec_realtek intel_cstate snd_hda_codec_generic ledtrig_audio 
snd_hda_codec_hdmi nls_iso8859_1 snd_hda_intel joydev snd_intel_dspcfg btusb 
at24 snd_intel_sdw_acpi snd_hda_codec snd_hda_core btrtl snd_hwdep btbcm 
snd_pcm input_leds snd_seq_midi btintel snd_seq_midi_event bluetooth 
snd_rawmidi ecdh_generic ecc snd_seq mei_me snd_seq_device snd_timer snd mei 
soundcore mac_hid intel_smartconnect sch_fq_codel msr parport_pc ppdev lp 
parport ramoops reed_solomon pstore_blk pstore_zone efi_pstore ip_tables 
x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c 
dm_crypt hid_generic usbhid hid i915 i2c_algo_bit t
 tm drm_kms_helper syscopyarea sysfillrect
  Jan  3 17:16:33 linuxkiste kernel: [164294.600481]  sysimgblt fb_sys_fops cec 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i2c_i801 aesni_intel ahci 
rc_core crypto_simd r8169 mxm_wmi cryptd i2c_smbus libahci lpc_ich realtek drm 
xhci_pci xhci_pci_renesas wmi video
  Jan  3 17:16:33 linuxkiste kernel: [164294.600494] CR2: e2fc5108
  Jan  3 17:16:33 linuxkiste kernel: [164294.600496] ---[ end trace 
c11e39619ebb9be7 ]---
  Jan  3 17:16:33 linuxkiste kernel: [164295.136110] RIP: 0010:kfree+0x68/0x250
  Jan  3 17:16:33 linuxkiste kernel: [164295.136119] Code: 80 49 01 dc 0f 82 f2 
01 00 00 48 c7 c0 00 00 00 80 48 2b 05 42 63 39 01 49 01 c4 49 c1 ec 0c 49 c1 
e4 06 4c 03 25 20 63 39 01 <49> 8b 44 24 08 48 8d 50 ff a8 01 4c 0f 45 e2 49 8b 
54 24 08 48 8d
  Jan  3 17:16:33 linuxkiste kernel: [164295.136121] RSP: 0018:b98e88c47930 
EFLAGS: 00010286
  Jan  3 17:16:33 linuxkiste kernel: [164295.136123] RAX: 6bf38000 RBX: 
40c0 RCX: 00392c14
  Jan  3 17:16:33 linuxkiste kernel: [164295.136125] RDX: b98e8000 RSI: 
a04d669e RDI: 40c0
  Jan  3 17:16:33 linuxkiste kernel: [164295.136126] RBP: b98e88c47970 R08: 
 R09: 
  Jan  3 17:16:33 linuxkiste kernel: [164295.136127] R10: 940e24fc1000 R11: 
940e090c5ad4 R12: e2fc5100
  Jan  3 17:16:33 linuxkiste kernel: [164295.136129] R13: 000a R14: 
 R15: 0230
  Jan  3 17:16:33 linuxkiste kernel: [164295.136130] FS:  
7f3c96764340() GS:94100ea8() knlGS:
  Jan  3 17:16:33 linuxkiste kernel: [164295.136131] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  3 17:16:33 linuxkiste kernel: [164295.136133] CR2: e2fc5108 CR3: 
0001f49d8001 CR4: 001706e0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USER    PID ACCESS COMMAND
   /dev/snd/controlC0:  jens  22753 F pulseaudio
   /dev/snd/controlC1:  jens  22753 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: KDE neon 22.04
  InstallationDate: Installed on 2022-11-26 (43 days ago)
  InstallationMedia: neon user "Jammy" - Build amd64 LIVE Binary 20221117-07:30
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic 
root=UUID=0c647c08-756d-408d-b730-0f54ea

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

[Jens]

el: [164294.600397]  ? irqentry_exit+0x1d/0x30
  Jan  3 17:16:33 linuxkiste kernel: [164294.600399]  ? 
exc_page_fault+0x89/0x170
  Jan  3 17:16:33 linuxkiste kernel: [164294.600402]  
entry_SYSCALL_64_after_hwframe+0x61/0xcb
  Jan  3 17:16:33 linuxkiste kernel: [164294.600406] RIP: 0033:0x7f3c97b93aff
  Jan  3 17:16:33 linuxkiste kernel: [164294.600408] Code: 00 48 89 44 24 18 31 
c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 
24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 
2b 04 25 28 00
  Jan  3 17:16:33 linuxkiste kernel: [164294.600410] RSP: 002b:7fffc65150c0 
EFLAGS: 0246 ORIG_RAX: 0010
  Jan  3 17:16:33 linuxkiste kernel: [164294.600412] RAX: ffda RBX: 
7fffc6515250 RCX: 7f3c97b93aff
  Jan  3 17:16:33 linuxkiste kernel: [164294.600413] RDX: 7fffc6515250 RSI: 
40406469 RDI: 0018
  Jan  3 17:16:33 linuxkiste kernel: [164294.600414] RBP: 0018 R08: 
0001 R09: 0008
  Jan  3 17:16:33 linuxkiste kernel: [164294.600416] R10: 113c0f80 R11: 
0246 R12: 7fffc6515250
  Jan  3 17:16:33 linuxkiste kernel: [164294.600417] R13:  R14: 
7f3c89c82bb8 R15: 10372000
  Jan  3 17:16:33 linuxkiste kernel: [164294.600419]  
  Jan  3 17:16:33 linuxkiste kernel: [164294.600420] Modules linked in: tls 
ntfs3 uas usb_storage nls_utf8 cifs cifs_arc4 cifs_md4 fscache netfs 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm cmac algif_hash algif_skcipher 
af_alg bnep binfmt_misc mei_hdcp intel_rapl_msr intel_rapl_common 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm rapl 
snd_hda_codec_realtek intel_cstate snd_hda_codec_generic ledtrig_audio 
snd_hda_codec_hdmi nls_iso8859_1 snd_hda_intel joydev snd_intel_dspcfg btusb 
at24 snd_intel_sdw_acpi snd_hda_codec snd_hda_core btrtl snd_hwdep btbcm 
snd_pcm input_leds snd_seq_midi btintel snd_seq_midi_event bluetooth 
snd_rawmidi ecdh_generic ecc snd_seq mei_me snd_seq_device snd_timer snd mei 
soundcore mac_hid intel_smartconnect sch_fq_codel msr parport_pc ppdev lp 
parport ramoops reed_solomon pstore_blk pstore_zone efi_pstore ip_tables 
x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c 
dm_crypt hid_generic usbhid hid i915 i2c_algo_bit t
 tm drm_kms_helper syscopyarea sysfillrect
  Jan  3 17:16:33 linuxkiste kernel: [164294.600481]  sysimgblt fb_sys_fops cec 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i2c_i801 aesni_intel ahci 
rc_core crypto_simd r8169 mxm_wmi cryptd i2c_smbus libahci lpc_ich realtek drm 
xhci_pci xhci_pci_renesas wmi video
  Jan  3 17:16:33 linuxkiste kernel: [164294.600494] CR2: e2fc5108
  Jan  3 17:16:33 linuxkiste kernel: [164294.600496] ---[ end trace 
c11e39619ebb9be7 ]---
  Jan  3 17:16:33 linuxkiste kernel: [164295.136110] RIP: 0010:kfree+0x68/0x250
  Jan  3 17:16:33 linuxkiste kernel: [164295.136119] Code: 80 49 01 dc 0f 82 f2 
01 00 00 48 c7 c0 00 00 00 80 48 2b 05 42 63 39 01 49 01 c4 49 c1 ec 0c 49 c1 
e4 06 4c 03 25 20 63 39 01 <49> 8b 44 24 08 48 8d 50 ff a8 01 4c 0f 45 e2 49 8b 
54 24 08 48 8d
  Jan  3 17:16:33 linuxkiste kernel: [164295.136121] RSP: 0018:b98e88c47930 
EFLAGS: 00010286
  Jan  3 17:16:33 linuxkiste kernel: [164295.136123] RAX: 6bf38000 RBX: 
40c0 RCX: 00392c14
  Jan  3 17:16:33 linuxkiste kernel: [164295.136125] RDX: b98e8000 RSI: 
a04d669e RDI: 40c0
  Jan  3 17:16:33 linuxkiste kernel: [164295.136126] RBP: b98e88c47970 R08: 
 R09: 
  Jan  3 17:16:33 linuxkiste kernel: [164295.136127] R10: 940e24fc1000 R11: 
940e090c5ad4 R12: e2fc5100
  Jan  3 17:16:33 linuxkiste kernel: [164295.136129] R13: 000a R14: 
 R15: 0230
  Jan  3 17:16:33 linuxkiste kernel: [164295.136130] FS:  
7f3c96764340() GS:94100ea8() knlGS:
  Jan  3 17:16:33 linuxkiste kernel: [164295.136131] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  3 17:16:33 linuxkiste kernel: [164295.136133] CR2: e2fc5108 CR3: 
0001f49d8001 CR4: 001706e0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USER    PID ACCESS COMMAND
   /dev/snd/controlC0:  jens  22753 F pulseaudio
   /dev/snd/controlC1:  jens  22753 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: KDE neon 22.04
  InstallationDate: Installed on 2022-11-26 (43 days ago)
  InstallationMedia: neon user "Jammy" - Build amd64 LIVE Binary 20221117-07:30
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic 
root=UUID=0c647c0

[Kernel-packages] [Bug 2001545] Re: i915: repetable Kernel Oops after resuming from standby

[Jens]

: 00 48 89 44 24 18 31 
c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 
24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 
2b 04 25 28 00
  Jan  3 17:16:33 linuxkiste kernel: [164294.600410] RSP: 002b:7fffc65150c0 
EFLAGS: 0246 ORIG_RAX: 0010
  Jan  3 17:16:33 linuxkiste kernel: [164294.600412] RAX: ffda RBX: 
7fffc6515250 RCX: 7f3c97b93aff
  Jan  3 17:16:33 linuxkiste kernel: [164294.600413] RDX: 7fffc6515250 RSI: 
40406469 RDI: 0018
  Jan  3 17:16:33 linuxkiste kernel: [164294.600414] RBP: 0018 R08: 
0001 R09: 0008
  Jan  3 17:16:33 linuxkiste kernel: [164294.600416] R10: 113c0f80 R11: 
0246 R12: 7fffc6515250
  Jan  3 17:16:33 linuxkiste kernel: [164294.600417] R13:  R14: 
7f3c89c82bb8 R15: 10372000
  Jan  3 17:16:33 linuxkiste kernel: [164294.600419]  
  Jan  3 17:16:33 linuxkiste kernel: [164294.600420] Modules linked in: tls 
ntfs3 uas usb_storage nls_utf8 cifs cifs_arc4 cifs_md4 fscache netfs 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm cmac algif_hash algif_skcipher 
af_alg bnep binfmt_misc mei_hdcp intel_rapl_msr intel_rapl_common 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm rapl 
snd_hda_codec_realtek intel_cstate snd_hda_codec_generic ledtrig_audio 
snd_hda_codec_hdmi nls_iso8859_1 snd_hda_intel joydev snd_intel_dspcfg btusb 
at24 snd_intel_sdw_acpi snd_hda_codec snd_hda_core btrtl snd_hwdep btbcm 
snd_pcm input_leds snd_seq_midi btintel snd_seq_midi_event bluetooth 
snd_rawmidi ecdh_generic ecc snd_seq mei_me snd_seq_device snd_timer snd mei 
soundcore mac_hid intel_smartconnect sch_fq_codel msr parport_pc ppdev lp 
parport ramoops reed_solomon pstore_blk pstore_zone efi_pstore ip_tables 
x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c 
dm_crypt hid_generic usbhid hid i915 i2c_algo_bit t
 tm drm_kms_helper syscopyarea sysfillrect
  Jan  3 17:16:33 linuxkiste kernel: [164294.600481]  sysimgblt fb_sys_fops cec 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i2c_i801 aesni_intel ahci 
rc_core crypto_simd r8169 mxm_wmi cryptd i2c_smbus libahci lpc_ich realtek drm 
xhci_pci xhci_pci_renesas wmi video
  Jan  3 17:16:33 linuxkiste kernel: [164294.600494] CR2: e2fc5108
  Jan  3 17:16:33 linuxkiste kernel: [164294.600496] ---[ end trace 
c11e39619ebb9be7 ]---
  Jan  3 17:16:33 linuxkiste kernel: [164295.136110] RIP: 0010:kfree+0x68/0x250
  Jan  3 17:16:33 linuxkiste kernel: [164295.136119] Code: 80 49 01 dc 0f 82 f2 
01 00 00 48 c7 c0 00 00 00 80 48 2b 05 42 63 39 01 49 01 c4 49 c1 ec 0c 49 c1 
e4 06 4c 03 25 20 63 39 01 <49> 8b 44 24 08 48 8d 50 ff a8 01 4c 0f 45 e2 49 8b 
54 24 08 48 8d
  Jan  3 17:16:33 linuxkiste kernel: [164295.136121] RSP: 0018:b98e88c47930 
EFLAGS: 00010286
  Jan  3 17:16:33 linuxkiste kernel: [164295.136123] RAX: 6bf38000 RBX: 
40c0 RCX: 00392c14
  Jan  3 17:16:33 linuxkiste kernel: [164295.136125] RDX: b98e8000 RSI: 
a04d669e RDI: 40c0
  Jan  3 17:16:33 linuxkiste kernel: [164295.136126] RBP: b98e88c47970 R08: 
 R09: 
  Jan  3 17:16:33 linuxkiste kernel: [164295.136127] R10: 940e24fc1000 R11: 
940e090c5ad4 R12: e2fc5100
  Jan  3 17:16:33 linuxkiste kernel: [164295.136129] R13: 000a R14: 
 R15: 0230
  Jan  3 17:16:33 linuxkiste kernel: [164295.136130] FS:  
7f3c96764340() GS:94100ea8() knlGS:
  Jan  3 17:16:33 linuxkiste kernel: [164295.136131] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  3 17:16:33 linuxkiste kernel: [164295.136133] CR2: e2fc5108 CR3: 
0001f49d8001 CR4: 001706e0
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.3
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  jens  22753 F.... pulseaudio
+  /dev/snd/controlC1:  jens  22753 F pulseaudio
+ CRDA: N/A
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: KDE
+ DistroRelease: KDE neon 22.04
+ InstallationDate: Installed on 2022-11-26 (43 days ago)
+ InstallationMedia: neon user "Jammy" - Build amd64 LIVE Binary 20221117-07:30
+ IwConfig:
+  lono wireless extensions.
+  
+  enp2s0no wireless extensions.
+ MachineType: MSI MS-7817
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic 
root=UUID=0c647c08-756d-408d-b730-0f54ea1f73d0 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
+ RelatedPackageVersions:
+  linux-restricted-modules-5.15.0-57-generic N/A
+  linux-backports-modules-5.15.0-57-generic  N/A
+  linux-firmware 20220329.git681281e4-0ubuntu3.9
+ RfKill:
+  0: hci0: Bluetooth
+   Soft blo

[Kernel-packages] [Bug 2001545] Re: i915: repetable Kernel Oops after resuming from standby

[Jens]

** Attachment added: "lspci output"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2001545/+attachment/5638976/+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/2001545

Title:
  i915: repetable Kernel Oops after resuming from standby

Status in linux package in Ubuntu:
  New

Bug description:
  I have an Intel i915 Haswell system which - after upgrading from
  Ubuntu 20.04 to 22.04 - experiences repeated crashes when resuming
  from hibernation.

  Unfortunately, "ubuntu-bug" claims my kernel package is "not an
  official package" (which is untrue, at least to my knowledge - I
  installed from the official sources) so I cannot use 'ubuntu-bug'.

  $ cat /proc/version_signature 
  Ubuntu 5.15.0-56.62-generic 5.15.64

  I will attach the lspci output.

  This is the dmesg trace:

  Jan  3 17:16:33 linuxkiste kernel: [164294.599802] BUG: unable to handle page 
fault for address: e2fc5108
  Jan  3 17:16:33 linuxkiste kernel: [164294.599809] #PF: supervisor read 
access in kernel mode
  Jan  3 17:16:33 linuxkiste kernel: [164294.599811] #PF: error_code(0x) - 
not-present page
  Jan  3 17:16:33 linuxkiste kernel: [164294.599813] PGD 0 P4D 0
  Jan  3 17:16:33 linuxkiste kernel: [164294.599815] Oops:  [#1] SMP PTI
  Jan  3 17:16:33 linuxkiste kernel: [164294.599818] CPU: 1 PID: 93586 Comm: 
chrome Tainted: G   OE 5.15.0-56-generic #62-Ubuntu
  Jan  3 17:16:33 linuxkiste kernel: [164294.599820] Hardware name: MSI 
MS-7817/CSM-B85M-E45 (MS-7817), BIOS V10.9 04/21/2015
  Jan  3 17:16:33 linuxkiste kernel: [164294.599822] RIP: 0010:kfree+0x68/0x250
  Jan  3 17:16:33 linuxkiste kernel: [164294.599827] Code: 80 49 01 dc 0f 82 f2 
01 00 00 48 c7 c0 00 00 00 80 48 2b 05 42 63 39 01 49 01 c4 49 c1 ec 0c 49 c1 
e4 06 4c 03 25 20 63 39 01 <49> 8b 44 24 08 48 8d 50 ff a8 01 4c 0f 45 e2 49 8b 
54 24 08 48 8d
  Jan  3 17:16:33 linuxkiste kernel: [164294.599829] RSP: 0018:b98e88c47930 
EFLAGS: 00010286
  Jan  3 17:16:33 linuxkiste kernel: [164294.599831] RAX: 6bf38000 RBX: 
40c0 RCX: 00392c14
  Jan  3 17:16:33 linuxkiste kernel: [164294.599833] RDX: b98e8000 RSI: 
a04d669e RDI: 40c0
  Jan  3 17:16:33 linuxkiste kernel: [164294.599834] RBP: b98e88c47970 R08: 
 R09: 
  Jan  3 17:16:33 linuxkiste kernel: [164294.599835] R10: 940e24fc1000 R11: 
940e090c5ad4 R12: e2fc5100
  Jan  3 17:16:33 linuxkiste kernel: [164294.599836] R13: 000a R14: 
 R15: 0230
  Jan  3 17:16:33 linuxkiste kernel: [164294.599837] FS:  
7f3c96764340() GS:94100ea8() knlGS:
  Jan  3 17:16:33 linuxkiste kernel: [164294.599839] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  3 17:16:33 linuxkiste kernel: [164294.599840] CR2: e2fc5108 CR3: 
0001f49d8001 CR4: 001706e0
  Jan  3 17:16:33 linuxkiste kernel: [164294.599842] Call Trace:
  Jan  3 17:16:33 linuxkiste kernel: [164294.599843]  
  Jan  3 17:16:33 linuxkiste kernel: [164294.599845]  kvfree+0x2e/0x40
  Jan  3 17:16:33 linuxkiste kernel: [164294.599850]  
eb_relocate_parse_slow+0x133/0x470 [i915]
  Jan  3 17:16:33 linuxkiste kernel: [164294.599937]  
eb_relocate_parse+0x129/0x1b0 [i915]
  Jan  3 17:16:33 linuxkiste kernel: [164294.69]  
i915_gem_do_execbuffer+0x373/0xba0 [i915]
  Jan  3 17:16:33 linuxkiste kernel: [164294.600083]  ? 
__alloc_pages+0x311/0x330
  Jan  3 17:16:33 linuxkiste kernel: [164294.600088]  ? 
i915_memcpy_init_early+0x40/0x40 [i915]
  Jan  3 17:16:33 linuxkiste kernel: [164294.600140]  
i915_gem_execbuffer2_ioctl+0x12e/0x280 [i915]
  Jan  3 17:16:33 linuxkiste kernel: [164294.600200]  ? 
i915_gem_do_execbuffer+0xba0/0xba0 [i915]
  Jan  3 17:16:33 linuxkiste kernel: [164294.600256]  
drm_ioctl_kernel+0xb3/0x100 [drm]
  Jan  3 17:16:33 linuxkiste kernel: [164294.600290]  drm_ioctl+0x268/0x4b0 
[drm]
  Jan  3 17:16:33 linuxkiste kernel: [164294.600308]  ? 
i915_gem_do_execbuffer+0xba0/0xba0 [i915]
  Jan  3 17:16:33 linuxkiste kernel: [164294.600367]  ? 
__check_object_size.part.0+0x3a/0x150
  Jan  3 17:16:33 linuxkiste kernel: [164294.600372]  ? __fget_files+0x86/0xc0
  Jan  3 17:16:33 linuxkiste kernel: [164294.600376]  __x64_sys_ioctl+0x95/0xd0
  Jan  3 17:16:33 linuxkiste kernel: [164294.600379]  do_syscall_64+0x5c/0xc0
  Jan  3 17:16:33 linuxkiste kernel: [164294.600383]  ? __fget_files+0x86/0xc0
  Jan  3 17:16:33 linuxkiste kernel: [164294.600386]  ? fput+0x13/0x20
  Jan  3 17:16:33 linuxkiste kernel: [164294.600388]  ? 
exit_to_user_mode_prepare+0x37/0xb0
  Jan  3 17:16:33 linuxkiste kernel: [164294.600392]  ? 
syscall_exit_to_user_mode+0x27/0x50
  Jan  3 17:16:33 linuxkiste kernel: [164294.600395]  ? do_syscall_64+0x69/0xc0
  Jan  3 17:16:33 linuxkiste kernel: [164294.600397]  ? irqentry_exit+0x1d/0x30
  Jan  

[Kernel-packages] [Bug 2001545] [NEW] i915: repetable Kernel Oops after resuming from standby

[Jens]

Public bug reported:

I have an Intel i915 Haswell system which - after upgrading from Ubuntu
20.04 to 22.04 - experiences repeated crashes when resuming from
hibernation.

Unfortunately, "ubuntu-bug" claims my kernel package is "not an official
package" (which is untrue, at least to my knowledge - I installed from
the official sources) so I cannot use 'ubuntu-bug'.

$ cat /proc/version_signature 
Ubuntu 5.15.0-56.62-generic 5.15.64

I will attach the lspci output.

This is the dmesg trace:

Jan  3 17:16:33 linuxkiste kernel: [164294.599802] BUG: unable to handle page 
fault for address: e2fc5108
Jan  3 17:16:33 linuxkiste kernel: [164294.599809] #PF: supervisor read access 
in kernel mode
Jan  3 17:16:33 linuxkiste kernel: [164294.599811] #PF: error_code(0x) - 
not-present page
Jan  3 17:16:33 linuxkiste kernel: [164294.599813] PGD 0 P4D 0
Jan  3 17:16:33 linuxkiste kernel: [164294.599815] Oops:  [#1] SMP PTI
Jan  3 17:16:33 linuxkiste kernel: [164294.599818] CPU: 1 PID: 93586 Comm: 
chrome Tainted: G   OE 5.15.0-56-generic #62-Ubuntu
Jan  3 17:16:33 linuxkiste kernel: [164294.599820] Hardware name: MSI 
MS-7817/CSM-B85M-E45 (MS-7817), BIOS V10.9 04/21/2015
Jan  3 17:16:33 linuxkiste kernel: [164294.599822] RIP: 0010:kfree+0x68/0x250
Jan  3 17:16:33 linuxkiste kernel: [164294.599827] Code: 80 49 01 dc 0f 82 f2 
01 00 00 48 c7 c0 00 00 00 80 48 2b 05 42 63 39 01 49 01 c4 49 c1 ec 0c 49 c1 
e4 06 4c 03 25 20 63 39 01 <49> 8b 44 24 08 48 8d 50 ff a8 01 4c 0f 45 e2 49 8b 
54 24 08 48 8d
Jan  3 17:16:33 linuxkiste kernel: [164294.599829] RSP: 0018:b98e88c47930 
EFLAGS: 00010286
Jan  3 17:16:33 linuxkiste kernel: [164294.599831] RAX: 6bf38000 RBX: 
40c0 RCX: 00392c14
Jan  3 17:16:33 linuxkiste kernel: [164294.599833] RDX: b98e8000 RSI: 
a04d669e RDI: 40c0
Jan  3 17:16:33 linuxkiste kernel: [164294.599834] RBP: b98e88c47970 R08: 
 R09: 
Jan  3 17:16:33 linuxkiste kernel: [164294.599835] R10: 940e24fc1000 R11: 
940e090c5ad4 R12: e2fc5100
Jan  3 17:16:33 linuxkiste kernel: [164294.599836] R13: 000a R14: 
 R15: 0230
Jan  3 17:16:33 linuxkiste kernel: [164294.599837] FS:  7f3c96764340() 
GS:94100ea8() knlGS:
Jan  3 17:16:33 linuxkiste kernel: [164294.599839] CS:  0010 DS:  ES:  
CR0: 80050033
Jan  3 17:16:33 linuxkiste kernel: [164294.599840] CR2: e2fc5108 CR3: 
0001f49d8001 CR4: 001706e0
Jan  3 17:16:33 linuxkiste kernel: [164294.599842] Call Trace:
Jan  3 17:16:33 linuxkiste kernel: [164294.599843]  
Jan  3 17:16:33 linuxkiste kernel: [164294.599845]  kvfree+0x2e/0x40
Jan  3 17:16:33 linuxkiste kernel: [164294.599850]  
eb_relocate_parse_slow+0x133/0x470 [i915]
Jan  3 17:16:33 linuxkiste kernel: [164294.599937]  
eb_relocate_parse+0x129/0x1b0 [i915]
Jan  3 17:16:33 linuxkiste kernel: [164294.69]  
i915_gem_do_execbuffer+0x373/0xba0 [i915]
Jan  3 17:16:33 linuxkiste kernel: [164294.600083]  ? __alloc_pages+0x311/0x330
Jan  3 17:16:33 linuxkiste kernel: [164294.600088]  ? 
i915_memcpy_init_early+0x40/0x40 [i915]
Jan  3 17:16:33 linuxkiste kernel: [164294.600140]  
i915_gem_execbuffer2_ioctl+0x12e/0x280 [i915]
Jan  3 17:16:33 linuxkiste kernel: [164294.600200]  ? 
i915_gem_do_execbuffer+0xba0/0xba0 [i915]
Jan  3 17:16:33 linuxkiste kernel: [164294.600256]  drm_ioctl_kernel+0xb3/0x100 
[drm]
Jan  3 17:16:33 linuxkiste kernel: [164294.600290]  drm_ioctl+0x268/0x4b0 [drm]
Jan  3 17:16:33 linuxkiste kernel: [164294.600308]  ? 
i915_gem_do_execbuffer+0xba0/0xba0 [i915]
Jan  3 17:16:33 linuxkiste kernel: [164294.600367]  ? 
__check_object_size.part.0+0x3a/0x150
Jan  3 17:16:33 linuxkiste kernel: [164294.600372]  ? __fget_files+0x86/0xc0
Jan  3 17:16:33 linuxkiste kernel: [164294.600376]  __x64_sys_ioctl+0x95/0xd0
Jan  3 17:16:33 linuxkiste kernel: [164294.600379]  do_syscall_64+0x5c/0xc0
Jan  3 17:16:33 linuxkiste kernel: [164294.600383]  ? __fget_files+0x86/0xc0
Jan  3 17:16:33 linuxkiste kernel: [164294.600386]  ? fput+0x13/0x20
Jan  3 17:16:33 linuxkiste kernel: [164294.600388]  ? 
exit_to_user_mode_prepare+0x37/0xb0
Jan  3 17:16:33 linuxkiste kernel: [164294.600392]  ? 
syscall_exit_to_user_mode+0x27/0x50
Jan  3 17:16:33 linuxkiste kernel: [164294.600395]  ? do_syscall_64+0x69/0xc0
Jan  3 17:16:33 linuxkiste kernel: [164294.600397]  ? irqentry_exit+0x1d/0x30
Jan  3 17:16:33 linuxkiste kernel: [164294.600399]  ? exc_page_fault+0x89/0x170
Jan  3 17:16:33 linuxkiste kernel: [164294.600402]  
entry_SYSCALL_64_after_hwframe+0x61/0xcb
Jan  3 17:16:33 linuxkiste kernel: [164294.600406] RIP: 0033:0x7f3c97b93aff
Jan  3 17:16:33 linuxkiste kernel: [164294.600408] Code: 00 48 89 44 24 18 31 
c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 
24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 
2b 04 25 28 00
Jan  3 

[Kernel-packages] [Bug 1973839] Re: 5.15.0-30-generic : SSBD mitigation results in "unchecked MSR access error: WRMSR to 0x48 (tried to write 0x0000000000000004)" and flood of kernel traces in some cl

[Jens Bretschneider]

Same here after Updating from 20.04 to 22.04 today:

[0.00] Linux version 5.15.0-46-generic (buildd@lcy02-amd64-115) (gcc 
(Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) 
#49-Ubuntu SMP Thu Aug 4 18:03:25 UTC 2022 (Ubuntu 5.15.0-46.49-generic 5.15.39)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=8eb2528b-9477-4dcd-b796-e38b25a16b14 ro console=tty1 console=ttyS0
...
[5.239998] unchecked MSR access error: WRMSR to 0x48 (tried to write 
0x0004) at rIP: 0xbbe960f4 (native_write_msr+0x4/0x30)
[5.242224] Call Trace:
[5.242228]  
[5.242229]  ? write_spec_ctrl_current+0x45/0x50
[5.242240]  speculation_ctrl_update+0x8f/0x200
[5.245439]  speculation_ctrl_update_current+0x1f/0x30
[5.246406]  ssb_prctl_set+0x9a/0xf0
[5.247183]  arch_seccomp_spec_mitigate+0x66/0x70
[5.248195]  seccomp_set_mode_filter+0x4e2/0x530
[5.249094]  do_seccomp+0x37/0x200
[5.249829]  __x64_sys_seccomp+0x18/0x20
[5.250614]  do_syscall_64+0x5c/0xc0
[5.251371]  ? exit_to_user_mode_prepare+0x37/0xb0
[5.252268]  ? irqentry_exit_to_user_mode+0x9/0x20
[5.253181]  ? irqentry_exit+0x1d/0x30
[5.253932]  ? exc_page_fault+0x89/0x170
[5.254714]  entry_SYSCALL_64_after_hwframe+0x61/0xcb
[5.255633] RIP: 0033:0x7fd9bf82ca3d
[5.256398] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48
[5.259150] RSP: 002b:7fff2d4c0f88 EFLAGS: 0246 ORIG_RAX: 
013d
[5.260339] RAX: ffda RBX: 5604b1701620 RCX: 7fd9bf82ca3d
[5.261476] RDX: 5604b16fc390 RSI:  RDI: 0001
[5.262605] RBP:  R08: 0001 R09: 5604b16fc390
[5.263780] R10: 0001 R11: 0246 R12: 
[5.264940] R13: 0001 R14: 5604b16fc390 R15: 0001
[5.266076]  
 Starting [0;1;39mJournal Service[0m...
[5.267097] Call Trace:
[5.267721]  
[5.268288]  ? write_spec_ctrl_current+0x45/0x50
[5.269123]  __switch_to_xtra+0x110/0x4e0
[5.269919]  __switch_to+0x260/0x450
[5.270658]  __schedule+0x23d/0x590
[5.271400]  ? __do_softirq+0x27f/0x2e7
[5.272180]  schedule+0x4e/0xc0
[5.272891]  smpboot_thread_fn+0xff/0x160
[5.273696]  ? smpboot_register_percpu_thread+0x140/0x140
[5.274655]  kthread+0x12a/0x150
[5.275366]  ? set_kthread_struct+0x50/0x50
[5.276170]  ret_from_fork+0x22/0x30
[5.276930]  
[5.278397] Call Trace:

Cloud provider is https://www.ip-exchange.de/, based on OpenStack.

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

Title:
  5.15.0-30-generic :  SSBD mitigation results in "unchecked MSR access
  error: WRMSR to 0x48 (tried to write 0x0004)" and flood of
  kernel traces in some cloud providers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When booting this in one of our clouds, we see an error early in the
  kernel output

kernel: unchecked MSR access error: WRMSR to 0x48 (tried to write
  0x0004) at rIP: 0xabc90af4
  (native_write_msr+0x4/0x20)

  and then an un-ending stream of "bare" tracebacks; which I think must
  be related

  [2.285717] kernel: Call Trace:
  [2.285722] kernel:  
  [2.285723] kernel:  ? speculation_ctrl_update+0x95/0x200
  [2.292001] kernel:  speculation_ctrl_update_current+0x1f/0x30
  [2.292011] kernel:  ssb_prctl_set+0x92/0xe0
  [2.292016] kernel:  arch_seccomp_spec_mitigate+0x62/0x70
  [2.292019] kernel:  seccomp_set_mode_filter+0x4de/0x530
  [2.292024] kernel:  do_seccomp+0x37/0x1f0
  [2.292026] kernel:  __x64_sys_seccomp+0x18/0x20
  [2.292028] kernel:  do_syscall_64+0x5c/0xc0
  [2.292035] kernel:  ? handle_mm_fault+0xd8/0x2c0
  [2.299617] kernel:  ? do_user_addr_fault+0x1e3/0x670
  [2.312878] kernel:  ? exit_to_user_mode_prepare+0x37/0xb0
  [2.312894] kernel:  ? irqentry_exit_to_user_mode+0x9/0x20
  [2.312905] kernel:  ? irqentry_exit+0x19/0x30
  [2.312907] kernel:  ? exc_page_fault+0x89/0x160
  [2.312909] kernel:  ? asm_exc_page_fault+0x8/0x30
  [2.312914] kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [2.312919] kernel: RIP: 0033:0x7fcffd6eaa3d
  [2.312924] kernel: Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e 
fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 
<48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48
  [2.312926] kernel: RSP: 002b:7ffe352e2938 EFLAGS: 0246 ORIG_RAX: 
013d
  [2.312930] kernel: RAX: ffda RBX: 557d99d0c0c0 RCX: 
7fcffd6eaa3d
  [2.319941] 

[Kernel-packages] [Bug 1953554] Re: NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out

[Jens]

[335315.982132] [ cut here ]
[335315.982172] NETDEV WATCHDOG: enxf8e43ba9c6b7 (ax88179_178a): transmit queue 
0 timed out
[335315.982195] WARNING: CPU: 6 PID: 0 at net/sched/sch_generic.c:467 
dev_watchdog+0x24c/0x250
[335315.982202] Modules linked in: tcp_diag udp_diag inet_diag nfsv3 nfs_acl 
nfs lockd grace veth rbd ceph libceph fscache netfs ebtable_filter ebtables 
ip_set ip6table_raw iptable_raw ip6table_filter ip6_tables iptable_filter 
bpfilter sctp ip6_udp_tunnel udp_tunnel nf_tables bonding tls softdog 
nfnetlink_log nfnetlink cdc_mbim cdc_wdm cdc_ncm cdc_ether snd_hda_codec_hdmi 
intel_rapl_msr intel_rapl_common snd_sof_pci_intel_cnl snd_sof_intel_hda_common 
x86_pkg_temp_thermal soundwire_intel intel_powerclamp 
soundwire_generic_allocation coretemp soundwire_cadence snd_ctl_led 
snd_sof_intel_hda snd_sof_pci snd_hda_codec_realtek kvm_intel 
snd_sof_xtensa_dsp snd_hda_codec_generic snd_sof kvm snd_soc_hdac_hda iwlmvm 
snd_hda_ext_core snd_soc_acpi_intel_match irqbypass snd_soc_acpi soundwire_bus 
crct10dif_pclmul mac80211 ghash_clmulni_intel ledtrig_audio mei_hdcp libarc4 
aesni_intel snd_soc_core crypto_simd snd_compress cryptd ac97_bus 
snd_pcm_dmaengine snd_hda_intel rapl snd_intel_dspcfg intel_cstate
[335315.982343]  i915 snd_intel_sdw_acpi snd_hda_codec pcspkr snd_hda_core 
btusb snd_hwdep btrtl intel_wmi_thunderbolt wmi_bmof efi_pstore btbcm 
drm_kms_helper btintel snd_pcm cec iwlwifi rc_core bluetooth snd_timer 
i2c_algo_bit ax88179_178a fb_sys_fops snd syscopyarea ecdh_generic usbnet 
sysfillrect mii ee1004 soundcore sysimgblt ecc mei_me cfg80211 mei 
intel_pch_thermal acpi_tad mac_hid acpi_pad zfs(PO) zunicode(PO) zzstd(O) 
zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_net vhost 
vhost_iotlb tap ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp 
libiscsi scsi_transport_iscsi drm sunrpc ip_tables x_tables autofs4 btrfs 
blake2b_generic xor zstd_compress raid6_pq dm_thin_pool dm_persistent_data 
dm_bio_prison dm_bufio libcrc32c crc32_pclmul nvme sdhci_pci xhci_pci 
intel_lpss_pci i2c_i801 cqhci xhci_pci_renesas e1000e i2c_smbus sdhci 
thunderbolt nvme_core ahci intel_lpss libahci xhci_hcd idma64 wmi video 
pinctrl_cannonlake
[335315.982469] CPU: 6 PID: 0 Comm: swapper/6 Tainted: P   O  
5.13.19-6-pve #1
[335315.982472] Hardware name: Intel(R) Client Systems NUC10i7FNK/NUC10i7FNB, 
BIOS FNCML357.0038.2020.0131.1422 01/31/2020
[335315.982473] RIP: 0010:dev_watchdog+0x24c/0x250
[335315.982476] Code: fa 25 fd ff eb ab 4c 89 ff c6 05 35 da 4f 01 01 e8 e9 ee 
f9 ff 44 89 e9 4c 89 fe 48 c7 c7 80 d9 48 ae 48 89 c2 e8 bc 05 1a 00 <0f> 0b eb 
8c 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 41 56 4d 89
[335315.982479] RSP: 0018:b0bac029ce80 EFLAGS: 00010282
[335315.982481] RAX:  RBX: 9e0d86e98000 RCX: 
083f
[335315.982483] RDX:  RSI: 00f6 RDI: 
083f
[335315.982484] RBP: b0bac029ceb0 R08:  R09: 
b0bac029cc60
[335315.982485] R10: b0bac029cc58 R11: aeb55428 R12: 
9e0d86e98080
[335315.982487] R13:  R14: 9e0d92c96480 R15: 
9e0d92c96000
[335315.982488] FS:  () GS:9e10f0d0() 
knlGS:
[335315.982490] CS:  0010 DS:  ES:  CR0: 80050033
[335315.982491] CR2: 55faae44be88 CR3: 000256210006 CR4: 
003706e0
[335315.982493] Call Trace:
[335315.982495]  
[335315.982498]  ? pfifo_fast_enqueue+0x150/0x150
[335315.982500]  call_timer_fn+0x2c/0x100
[335315.982503]  __run_timers.part.0+0x1d8/0x250
[335315.982505]  ? ktime_get+0x3b/0xa0
[335315.982508]  ? lapic_next_deadline+0x2c/0x40
[335315.982512]  ? clockevents_program_event+0x8f/0xe0
[335315.982516]  run_timer_softirq+0x2a/0x50
[335315.982519]  __do_softirq+0xcb/0x281
[335315.982523]  irq_exit_rcu+0xa2/0xd0
[335315.982527]  sysvec_apic_timer_interrupt+0x7c/0x90
[335315.982529]  
[335315.982530]  
[335315.982531]  asm_sysvec_apic_timer_interrupt+0x12/0x20
[335315.982534] RIP: 0010:cpuidle_enter_state+0xcc/0x360
[335315.982538] Code: 3d f1 92 8d 52 e8 f4 54 7a ff 49 89 c6 0f 1f 44 00 00 31 
ff e8 95 60 7a ff 80 7d d7 00 0f 85 01 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 ff 
0f 88 0d 01 00 00 49 63 cf 4c 2b 75 c8 48 8d 04 49 48 89
[335315.982540] RSP: 0018:b0bac0137e68 EFLAGS: 0246
[335315.982542] RAX: 9e10f0d34ec0 RBX: 0003 RCX: 
001f
[335315.982543] RDX:  RSI: 4f9a1f43 RDI: 

[335315.982545] RBP: b0bac0137ea0 R08: 000130f7d6002b01 R09: 
0018
[335315.982546] R10: 0001 R11:  R12: 
d0babfb00500
[335315.982547] R13: aec50e00 R14: 000130f7d6002b01 R15: 
0003
[335315.982550]  ? cpuidle_enter_state+0xbb/0x360
[335315.982553]  cpuidle_enter+0x2e/0x40
[335315.982556]  do_idle+0x1ff/0x2a0
[335315.982559]  cpu_startup_entry+0x20/0x30
[335315.982561]  

[Kernel-packages] [Bug 1953554] Re: NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out

[Jens]

I'm seeing this exact same issue with a TP-Link UE300C USB-C adapter,

the thing is, I have 2 identical intel NUC's with each one of these
adaptors, and on the one machine I see this on average once a month for
the last 3 months now, on the other machine this has not happend yet.

replugging it and restarting the network seems to fix it, I'm not sure
if this is a hardware issue or not

Is there any information or debug info I can provide here to help this
issue allong?

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

Title:
  NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I am facing this problem in Focal with the USB 3.0 Ethernet Gigabit
  adapter "ASIX Electronics Corp. AX88179 Gigabit Ethernet" (waneth is
  the name I assigned to this ethernet connected to the cable
  modem/router):

  [ cut here ]
  [94104.121581] NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed 
out
  [94104.121606] WARNING: CPU: 2 PID: 217952 at net/sched/sch_generic.c:467 
dev_watchdog+0x24f/0x260
  [94104.121615] Modules linked in: binfmt_misc xt_recent nfnetlink 
nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua 
snd_sof_pci_intel_apl snd_sof_intel_hda_common soundwire_intel 
soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof soundwire_bus snd_soc_skl snd_soc_hdac_hda 
snd_hda_ext_core intel_rapl_msr snd_soc_sst_ipc intel_rapl_common 8814au(OE) 
mei_hdcp snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi intel_pmc_bxt 
snd_soc_core intel_telemetry_pltdrv intel_punit_ipc snd_compress 
intel_telemetry_core snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp 
snd_hda_codec_realtek coretemp snd_hda_codec_generic ac97_bus ledtrig_audio 
snd_pcm_dmaengine kvm_intel snd_hda_intel kvm snd_intel_dspcfg 
snd_intel_sdw_acpi snd_hda_codec rapl intel_cstate snd_hda_core snd_hwdep 
snd_pcm snd_timer ax88179_178a cfg80211 efi_pstore mei_me usbnet ee1004 snd mii 
soundcore mei mac_hid bridge ip6t_REJECT nf_reject_ipv6 stp llc xt_hl
  [94104.121696] ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog 
xt_limit xt_addrtype xt_tcpudp xt_MASQUERADE iptable_nat nf_nat xt_conntrack 
nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6table_filter ip6_tables 
sch_fq_codel iptable_filter bpfilter msr ip_tables x_tables autofs4 btrfs 
blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
uas usb_storage i915 i2c_algo_bit drm_kms_helper crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core 
aesni_intel crypto_simd i2c_i801 xhci_pci i2c_smbus cryptd r8169 realtek 
xhci_pci_renesas drm sdhci_pci ahci cqhci sdhci libahci video
  [94104.121771] CPU: 2 PID: 217952 Comm: PLUGIN[cgroups] Tainted: G OE 
5.13.0-22-generic #22~20.04.1-Ubuntu
  [94104.121775] Hardware name: GIGABYTE MZGLKDP-00/MZGLKDP-00, BIOS F1 
12/21/2017
  [94104.121777] RIP: 0010:dev_watchdog+0x24f/0x260
  [94104.121782] Code: c7 36 fd ff eb ab 4c 89 ff c6 05 60 f1 6e 01 01 e8 86 11 
fa ff 44 89 e9 4c 89 fe 48 c7 c7 20 9c ca 89 48 89 c2 e8 38 17 17 00 <0f> 0b eb 
8c 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00
  [94104.121785] RSP: 0018:b515c0138e88 EFLAGS: 00010282
  [94104.121788] RAX:  RBX: 91214fc45e00 RCX: 
0027
  [94104.121790] RDX: 0027 RSI: dfff RDI: 
9124b05189c8
  [94104.121792] RBP: b515c0138eb8 R08: 9124b05189c0 R09: 
b515c0138c60
  [94104.121794] R10: 0001 R11: 0001 R12: 
0001
  [94104.121795] R13:  R14: 912154a7d480 R15: 
912154a7d000
  [94104.121797] FS: 7f74619e5700() GS:9124b050() 
knlGS:
  [94104.121800] CS: 0010 DS:  ES:  CR0: 80050033
  [94104.121802] CR2: 5635dd41b584 CR3: 00020592a000 CR4: 
00350ee0
  [94104.121805] Call Trace:
  [94104.121807] 
  [94104.121812] ? pfifo_fast_enqueue+0x150/0x150
  [94104.121816] call_timer_fn+0x2c/0x100
  [94104.121821] run_timer_softirq+0x3d7/0x480
  [94104.121824] ? perf_trace_softirq+0x9d/0xd0
  [94104.121829] __do_softirq+0xdd/0x29b
  [94104.121835] irq_exit_rcu+0xa4/0xb0
  [94104.121837] sysvec_apic_timer_interrupt+0x7c/0x90
  [94104.121841] 
  [94104.121843] asm_sysvec_apic_timer_interrupt+0x12/0x20
  [94104.121846] RIP: 0010:errseq_sample+0x2/0x10
  [94104.121850] Code: ff 48 d3 e2 48 f7 d2 48 21 d0 0f 01 ca 48 85 c0 0f 94 c0 
0f b6 c0 c3 b8 01 00 00 00 c3 b8 f2 ff ff ff c3 cc cc cc cc cc 8b 07  00 00 
00 00 f6 c4 10 0f 44 c2 c3 66 90 8b 17 31 c0 39 16 74 1b
  [94104.121853] RSP: 0018:b515c29cfb68 EFLAGS: 0286
  [94104.121855] RAX: 

[Kernel-packages] [Bug 1961171] [NEW] System freezes when starting Eclipse

[Jens Askengren]

Public bug reported:

Starting Eclipse will 100% likely cause a complete system freeze within a few 
minutes.
Same problem occurs using Wayland and X.org.
See the attached kernel stack trace.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-28-generic 5.13.0-28.31
ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
Uname: Linux 5.13.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  jens   2427 F pulseaudio
 /dev/snd/controlC0:  jens   2427 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 17 08:38:59 2022
InstallationDate: Installed on 2019-04-12 (1042 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
Lsusb:
 Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Internal Memory Card Reader
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Internal Keyboard/Trackpad (ISO)
 Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bluetooth Host Controller
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Apple Inc. MacBookPro12,1
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-28-generic N/A
 linux-backports-modules-5.13.0-28-generic  N/A
 linux-firmware 1.201.4
SourcePackage: linux
UpgradeStatus: Upgraded to impish on 2021-10-26 (114 days ago)
dmi.bios.date: 09/17/2018
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 180.0.0.0.0
dmi.board.name: Mac-E43C1C25D4880AD6
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro12,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-E43C1C25D4880AD6
dmi.modalias: 
dmi:bvnAppleInc.:bvr180.0.0.0.0:bd09/17/2018:br0.1:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:sku:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro12,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-bug impish wayland-session

** Attachment added: "Kernel stack trace"
   
https://bugs.launchpad.net/bugs/1961171/+attachment/5561540/+files/linux-hang-backtrace.txt.gz

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

Title:
  System freezes when starting Eclipse

Status in linux package in Ubuntu:
  New

Bug description:
  Starting Eclipse will 100% likely cause a complete system freeze within a few 
minutes.
  Same problem occurs using Wayland and X.org.
  See the attached kernel stack trace.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-28-generic 5.13.0-28.31
  ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
  Uname: Linux 5.13.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jens   2427 F pulseaudio
   /dev/snd/controlC0:  jens   2427 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 17 08:38:59 2022
  InstallationDate: Installed on 2019-04-12 (1042 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  Lsusb:
   Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Internal Memory Card Reader
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Internal Keyboard/Trackpad (ISO)
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bluetooth Host Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-28-generic N/A
   linux-backports-modules-5.13.0-28-generic  N/A
   linux-firmware 1.201.4
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-10-26 (114 days ago)
  dmi.bios.date: 09/17/2018
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 180.0.0.0.0
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis

[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS

[Jens Glathe]

@k3dar7 now... I did some search on what installs libssl3.

$ ldconfig -p | grep ssl3
libssl3.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libssl3.so

$ apt-file search libssl3.so
firefox: /usr/lib/firefox/libssl3.so  
libnss3: /usr/lib/x86_64-linux-gnu/libssl3.so
thunderbird: /usr/lib/thunderbird/libssl3.so
thunderbird-dbg: /usr/lib/debug/usr/lib/thunderbird/libssl3.so

So in my case, it appears to be libnss3.

I could build and deploy 5.15.7 without issues, though.

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

Title:
  Recent mainline packages are built with Hirsuite 21.04, not Focal
  20.04 LTS

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Hi all,

  The Mainline wiki states that the mainline kernels are built with the
  previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are
  being built with Hirsuite 21.04, and before that Groovy? If this is
  intentional, then the wiki should be updated to reflect the change in
  policy.

  From https://wiki.ubuntu.com/Kernel/MainlineBuilds

Mainline kernel build toolchain
These kernels are built with the toolchain (gcc, g++, etc.) from the 
previous Ubuntu LTS release. 
(e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic 
Beaver", etc.) Therefore, 
out-of-tree kernel modules you already have built and installed for use 
with your release kernels 
are not likely to work with the mainline builds.

  The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On
  my Focal LTS system I have GCC 9.3.0.

  The Mainline kernel build toolchain
  These kernels are built with the toolchain (gcc, g++, etc.) from the previous 
Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 
18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already 
have built and installed for use with your release kernels are not likely to 
work with the mainline builds.

  The *linux-headers-generic* packages have unmet dependencies on 20.04
  LTS.

  I could install Groovy built kernels fine, but the Hirsuite ones built
  with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels
  can't be installed on Focal (libc 2.31).

  Thanks,
  Mark

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


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

[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS

[Jens Glathe]

@k3dar7 interesting, had no error yesterday on building 5.15.7 Need to
investigate.

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

Title:
  Recent mainline packages are built with Hirsuite 21.04, not Focal
  20.04 LTS

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Hi all,

  The Mainline wiki states that the mainline kernels are built with the
  previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are
  being built with Hirsuite 21.04, and before that Groovy? If this is
  intentional, then the wiki should be updated to reflect the change in
  policy.

  From https://wiki.ubuntu.com/Kernel/MainlineBuilds

Mainline kernel build toolchain
These kernels are built with the toolchain (gcc, g++, etc.) from the 
previous Ubuntu LTS release. 
(e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic 
Beaver", etc.) Therefore, 
out-of-tree kernel modules you already have built and installed for use 
with your release kernels 
are not likely to work with the mainline builds.

  The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On
  my Focal LTS system I have GCC 9.3.0.

  The Mainline kernel build toolchain
  These kernels are built with the toolchain (gcc, g++, etc.) from the previous 
Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 
18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already 
have built and installed for use with your release kernels are not likely to 
work with the mainline builds.

  The *linux-headers-generic* packages have unmet dependencies on 20.04
  LTS.

  I could install Groovy built kernels fine, but the Hirsuite ones built
  with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels
  can't be installed on Focal (libc 2.31).

  Thanks,
  Mark

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


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

[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS

[Jens Glathe]

Hmm. Got 5.14.9 running directly from the
https://kernel.ubuntu.com/~kernel-ppa/mainline/ repository. Works with
nvidia driver 4.70 on Mint 20.2 :)

build sequence:

- checkout cod/mainline/v5.14.9 from 
git://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git/mainline-crack
- install libfuse-dev (shown in the selftest fail log, so I guessed it can't 
hurt)
- time sudo debian/rules clean
- time sudo dpkg-buildpackage -d -nc --no-sign -j33
- sudo chown -R : ..

Prerequisites is having built dwarves, libbpf, and probably zstd like
mentioned in #71. Package runs successfully on several machines.

One oddity I've seen: running the build again will fail. You need to git
clean -df multiple times, and do a git reset --hard . But pretty
straight forward anyway.

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

Title:
  Recent mainline packages are built with Hirsuite 21.04, not Focal
  20.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi all,

  The Mainline wiki states that the mainline kernels are built with the
  previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are
  being built with Hirsuite 21.04, and before that Groovy? If this is
  intentional, then the wiki should be updated to reflect the change in
  policy.

  From https://wiki.ubuntu.com/Kernel/MainlineBuilds

Mainline kernel build toolchain
These kernels are built with the toolchain (gcc, g++, etc.) from the 
previous Ubuntu LTS release. 
(e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic 
Beaver", etc.) Therefore, 
out-of-tree kernel modules you already have built and installed for use 
with your release kernels 
are not likely to work with the mainline builds.

  The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On
  my Focal LTS system I have GCC 9.3.0.

  The Mainline kernel build toolchain
  These kernels are built with the toolchain (gcc, g++, etc.) from the previous 
Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 
18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already 
have built and installed for use with your release kernels are not likely to 
work with the mainline builds.

  The *linux-headers-generic* packages have unmet dependencies on 20.04
  LTS.

  I could install Groovy built kernels fine, but the Hirsuite ones built
  with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels
  can't be installed on Focal (libc 2.31).

  Thanks,
  Mark

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


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

[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS

[Jens Glathe]

Was an interesing day, I was able to build and run mainline 5.13.12 on
Mint 20.2. Was the first time I used the mainline package from
kernel.org, and it was a bit fiddly, however copying over debian/ and
debian.master/ is a great start, thanks for the tip. Only thing that
doesn't work (yet) is nVidia 460.93 driver. This will be resolved
eventually. Anyway, to build mainline on 20.04 it is sufficient to:

- build dwarves locally
- install the libbpf
- install zstd infrastructure (you might be able to configure this out of the 
kernel config)

No libc6 >=2.33 needed.

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

Title:
  Recent mainline packages are built with Hirsuite 21.04, not Focal
  20.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi all,

  The Mainline wiki states that the mainline kernels are built with the
  previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are
  being built with Hirsuite 21.04, and before that Groovy? If this is
  intentional, then the wiki should be updated to reflect the change in
  policy.

  From https://wiki.ubuntu.com/Kernel/MainlineBuilds

Mainline kernel build toolchain
These kernels are built with the toolchain (gcc, g++, etc.) from the 
previous Ubuntu LTS release. 
(e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic 
Beaver", etc.) Therefore, 
out-of-tree kernel modules you already have built and installed for use 
with your release kernels 
are not likely to work with the mainline builds.

  The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On
  my Focal LTS system I have GCC 9.3.0.

  The Mainline kernel build toolchain
  These kernels are built with the toolchain (gcc, g++, etc.) from the previous 
Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 
18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already 
have built and installed for use with your release kernels are not likely to 
work with the mainline builds.

  The *linux-headers-generic* packages have unmet dependencies on 20.04
  LTS.

  I could install Groovy built kernels fine, but the Hirsuite ones built
  with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels
  can't be installed on Focal (libc 2.31).

  Thanks,
  Mark

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


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

[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS

[Jens Glathe]

Since HWE in focal changed today (?) to 5.13.0-14, trying to get it to
run I tried #66 DanglingPointer's approach (was on the same path trying
to build from the hirsute repo on Mint 20.2 - success with 5.11.0-25
after building dwarves locally :)). libbpf was missing, installed from
debian. zstd was missing, too, installed from debian. Aaaand... it
works. Next up will be to build the impish repo on this machine.

Interesting build - detail: Running "time sudo dpkg-buildpackage -d -nc
--no-sign -j33" is faster on the same machine as using fakeroot. With
sudo the machine is maxed out, build times in the 20 minutes range on
Ryzen 9-3950X with 170A EDC limit.

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

Title:
  Recent mainline packages are built with Hirsuite 21.04, not Focal
  20.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi all,

  The Mainline wiki states that the mainline kernels are built with the
  previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are
  being built with Hirsuite 21.04, and before that Groovy? If this is
  intentional, then the wiki should be updated to reflect the change in
  policy.

  From https://wiki.ubuntu.com/Kernel/MainlineBuilds

Mainline kernel build toolchain
These kernels are built with the toolchain (gcc, g++, etc.) from the 
previous Ubuntu LTS release. 
(e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic 
Beaver", etc.) Therefore, 
out-of-tree kernel modules you already have built and installed for use 
with your release kernels 
are not likely to work with the mainline builds.

  The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On
  my Focal LTS system I have GCC 9.3.0.

  The Mainline kernel build toolchain
  These kernels are built with the toolchain (gcc, g++, etc.) from the previous 
Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 
18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already 
have built and installed for use with your release kernels are not likely to 
work with the mainline builds.

  The *linux-headers-generic* packages have unmet dependencies on 20.04
  LTS.

  I could install Groovy built kernels fine, but the Hirsuite ones built
  with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels
  can't be installed on Focal (libc 2.31).

  Thanks,
  Mark

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


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

[Kernel-packages] [Bug 1926845] [NEW] Unable to store nvidia-settings

[Jens Elkner]

Public bug reported:

Since focal a casual unprivileged user cannot save the current X Server
Display Configuration, no matter which location is used. I.e. even for
e.g. /tmp/xorg.conf or /home/$LOGNAME/xorg.conf the user gets asked for
the root password.

This really stupid '"AUTHENTICATING FOR com.ubuntu.screen-resolution-
extra.root-display" "Authenticating as: root"' bug needs to be fixed. An
unprivileged user should be able to store the config wherever he wants
to, as long as he has write permission for the related file/directory.

** Affects: nvidia-settings (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: nvidia-settings-updates (Ubuntu) => nvidia-settings
(Ubuntu)

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

Title:
  Unable to store nvidia-settings

Status in nvidia-settings package in Ubuntu:
  New

Bug description:
  Since focal a casual unprivileged user cannot save the current X
  Server Display Configuration, no matter which location is used. I.e.
  even for e.g. /tmp/xorg.conf or /home/$LOGNAME/xorg.conf the user gets
  asked for the root password.

  This really stupid '"AUTHENTICATING FOR com.ubuntu.screen-resolution-
  extra.root-display" "Authenticating as: root"' bug needs to be fixed.
  An unprivileged user should be able to store the config wherever he
  wants to, as long as he has write permission for the related
  file/directory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1926845/+subscriptions

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

[Kernel-packages] [Bug 1905160] Re: zfs-initramfs: zfs import rpool fails - too early

[Jens Elkner]

There is no apport* installed on the machine.

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

Title:
  zfs-initramfs: zfs import rpool fails - too early

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  /usr/share/initramfs-tools/scripts/zfs::import_pool() tries to import
  the root pool (in my case named rpool) before the related devices are
  available, i.e. scsi scan has been finished.

  I use the following Q workaround to fix it:
  --- /usr/share/initramfs-tools/scripts/zfs.orig 2020-08-18 11:10:41.0 
+0200
  +++ /usr/share/initramfs-tools/scripts/zfs  2020-11-22 09:03:10.17698 
+0100
  @@ -217,12 +217,21 @@
   import_pool()
   {
  local pool="$1"
  -   local dirs dir
  +   local dirs dir T=30
   
  # Verify that the pool isn't already imported
  # Make as sure as we can to not require '-f' to import.
  "${ZPOOL}" get name,guid -o value -H 2>/dev/null | grep -Fxq "$pool" && 
return 0
   
  +   # Make sure, that at least rpool devices are available. Otherwise
  +   # zfs import may fail for "no" reason.
  +   while [ ! -e /dev/chassis/SYS/DOM0p2 ]; do
  +   sleep 1
  +   let T-=1
  +   [ $T -lt 0 ] && break
  +   done
  +   /bin/udevadm settle
  +
  # For backwards compatibility, make sure that ZPOOL_IMPORT_PATH is set
  # to something we can use later with the real import(s). We want to
  # make sure we find all by* dirs, BUT by-vdev should be first (if it

  ###

  /dev/chassis/SYS/DOM0p2 is one dev of the rpool 3-way mirror [the
  others are /dev/chassis/SYS/DOM1p2 and /dev/nvme0n1p2]. DOM* are SM
  SuperDOMs sitting on */ata[56]/* bus, but get handled s scsi devices
  as well. Unfortunately things like 'udevadm settle' or 'udevadm settle
  --exit-if-exists=/dev/chassis/SYS/DOM0p2' or 'udevadm trigger
  --verbose --type=devices --subsystem-match=scsi_disk' did not fix the
  problem. Not sure whether there is a way to say, wait until scsi
  subsystem [scan] has been finished.

  To get a better idea I'll attach 2 files: xxxlong-fail.out shows the
  debug output when booting the vanilla focal, xxxlong-patched.out shows
  the debug output with the patch above applied.

  BTW: Because it takes Ubuntu ~ 29 min to boot when the 2nd pool with
  44 disks is ZoL formatted, I disabled the OPROM usage of related SAS-
  HBA in the UEFI-BIOS (so that the disks cannot be seen) which brings
  it back to ~ 1:45 min until the kernel actually starts. I guess,
  therefore Linux needs a little bit more time to initialize it and
  that's why 'zfs import ...' starts too early. However, a system boot
  time of 30+ min is unacceptable and thus letting the BIOS initialize
  the HBA is not an option. I guess that's a linux efi bootloader
  problem: Solaris did not have any problems on this machine, even with
  HBA-OPROM enabled ...

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

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

[Kernel-packages] [Bug 1905160] Re: zfs-initramfs: zfs import rpool fails - too early

[Jens Elkner]

** Attachment added: "debug output with Q fix"
   
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1905160/+attachment/5436799/+files/xxxlong-patched.out

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

Title:
  zfs-initramfs: zfs import rpool fails - too early

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  /usr/share/initramfs-tools/scripts/zfs::import_pool() tries to import
  the root pool (in my case named rpool) before the related devices are
  available, i.e. scsi scan has been finished.

  I use the following Q workaround to fix it:
  --- /usr/share/initramfs-tools/scripts/zfs.orig 2020-08-18 11:10:41.0 
+0200
  +++ /usr/share/initramfs-tools/scripts/zfs  2020-11-22 09:03:10.17698 
+0100
  @@ -217,12 +217,21 @@
   import_pool()
   {
  local pool="$1"
  -   local dirs dir
  +   local dirs dir T=30
   
  # Verify that the pool isn't already imported
  # Make as sure as we can to not require '-f' to import.
  "${ZPOOL}" get name,guid -o value -H 2>/dev/null | grep -Fxq "$pool" && 
return 0
   
  +   # Make sure, that at least rpool devices are available. Otherwise
  +   # zfs import may fail for "no" reason.
  +   while [ ! -e /dev/chassis/SYS/DOM0p2 ]; do
  +   sleep 1
  +   let T-=1
  +   [ $T -lt 0 ] && break
  +   done
  +   /bin/udevadm settle
  +
  # For backwards compatibility, make sure that ZPOOL_IMPORT_PATH is set
  # to something we can use later with the real import(s). We want to
  # make sure we find all by* dirs, BUT by-vdev should be first (if it

  ###

  /dev/chassis/SYS/DOM0p2 is one dev of the rpool 3-way mirror [the
  others are /dev/chassis/SYS/DOM1p2 and /dev/nvme0n1p2]. DOM* are SM
  SuperDOMs sitting on */ata[56]/* bus, but get handled s scsi devices
  as well. Unfortunately things like 'udevadm settle' or 'udevadm settle
  --exit-if-exists=/dev/chassis/SYS/DOM0p2' or 'udevadm trigger
  --verbose --type=devices --subsystem-match=scsi_disk' did not fix the
  problem. Not sure whether there is a way to say, wait until scsi
  subsystem [scan] has been finished.

  To get a better idea I'll attach 2 files: xxxlong-fail.out shows the
  debug output when booting the vanilla focal, xxxlong-patched.out shows
  the debug output with the patch above applied.

  BTW: Because it takes Ubuntu ~ 29 min to boot when the 2nd pool with
  44 disks is ZoL formatted, I disabled the OPROM usage of related SAS-
  HBA in the UEFI-BIOS (so that the disks cannot be seen) which brings
  it back to ~ 1:45 min until the kernel actually starts. I guess,
  therefore Linux needs a little bit more time to initialize it and
  that's why 'zfs import ...' starts too early. However, a system boot
  time of 30+ min is unacceptable and thus letting the BIOS initialize
  the HBA is not an option. I guess that's a linux efi bootloader
  problem: Solaris did not have any problems on this machine, even with
  HBA-OPROM enabled ...

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

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

[Kernel-packages] [Bug 1905160] [NEW] zfs-initramfs: zfs import rpool fails - too early

[Jens Elkner]

Public bug reported:

/usr/share/initramfs-tools/scripts/zfs::import_pool() tries to import
the root pool (in my case named rpool) before the related devices are
available, i.e. scsi scan has been finished.

I use the following Q workaround to fix it:
--- /usr/share/initramfs-tools/scripts/zfs.orig 2020-08-18 11:10:41.0 
+0200
+++ /usr/share/initramfs-tools/scripts/zfs  2020-11-22 09:03:10.17698 +0100
@@ -217,12 +217,21 @@
 import_pool()
 {
local pool="$1"
-   local dirs dir
+   local dirs dir T=30
 
# Verify that the pool isn't already imported
# Make as sure as we can to not require '-f' to import.
"${ZPOOL}" get name,guid -o value -H 2>/dev/null | grep -Fxq "$pool" && 
return 0
 
+   # Make sure, that at least rpool devices are available. Otherwise
+   # zfs import may fail for "no" reason.
+   while [ ! -e /dev/chassis/SYS/DOM0p2 ]; do
+   sleep 1
+   let T-=1
+   [ $T -lt 0 ] && break
+   done
+   /bin/udevadm settle
+
# For backwards compatibility, make sure that ZPOOL_IMPORT_PATH is set
# to something we can use later with the real import(s). We want to
# make sure we find all by* dirs, BUT by-vdev should be first (if it

###

/dev/chassis/SYS/DOM0p2 is one dev of the rpool 3-way mirror [the others
are /dev/chassis/SYS/DOM1p2 and /dev/nvme0n1p2]. DOM* are SM SuperDOMs
sitting on */ata[56]/* bus, but get handled s scsi devices as well.
Unfortunately things like 'udevadm settle' or 'udevadm settle --exit-if-
exists=/dev/chassis/SYS/DOM0p2' or 'udevadm trigger --verbose
--type=devices --subsystem-match=scsi_disk' did not fix the problem. Not
sure whether there is a way to say, wait until scsi subsystem [scan] has
been finished.

To get a better idea I'll attach 2 files: xxxlong-fail.out shows the
debug output when booting the vanilla focal, xxxlong-patched.out shows
the debug output with the patch above applied.

BTW: Because it takes Ubuntu ~ 29 min to boot when the 2nd pool with 44
disks is ZoL formatted, I disabled the OPROM usage of related SAS-HBA in
the UEFI-BIOS (so that the disks cannot be seen) which brings it back to
~ 1:45 min until the kernel actually starts. I guess, therefore Linux
needs a little bit more time to initialize it and that's why 'zfs import
...' starts too early. However, a system boot time of 30+ min is
unacceptable and thus letting the BIOS initialize the HBA is not an
option. I guess that's a linux efi bootloader problem: Solaris did not
have any problems on this machine, even with HBA-OPROM enabled ...

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

** Attachment added: "debug output when import fails"
   
https://bugs.launchpad.net/bugs/1905160/+attachment/5436798/+files/xxxlong-fail.out

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

Title:
  zfs-initramfs: zfs import rpool fails - too early

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  /usr/share/initramfs-tools/scripts/zfs::import_pool() tries to import
  the root pool (in my case named rpool) before the related devices are
  available, i.e. scsi scan has been finished.

  I use the following Q workaround to fix it:
  --- /usr/share/initramfs-tools/scripts/zfs.orig 2020-08-18 11:10:41.0 
+0200
  +++ /usr/share/initramfs-tools/scripts/zfs  2020-11-22 09:03:10.17698 
+0100
  @@ -217,12 +217,21 @@
   import_pool()
   {
  local pool="$1"
  -   local dirs dir
  +   local dirs dir T=30
   
  # Verify that the pool isn't already imported
  # Make as sure as we can to not require '-f' to import.
  "${ZPOOL}" get name,guid -o value -H 2>/dev/null | grep -Fxq "$pool" && 
return 0
   
  +   # Make sure, that at least rpool devices are available. Otherwise
  +   # zfs import may fail for "no" reason.
  +   while [ ! -e /dev/chassis/SYS/DOM0p2 ]; do
  +   sleep 1
  +   let T-=1
  +   [ $T -lt 0 ] && break
  +   done
  +   /bin/udevadm settle
  +
  # For backwards compatibility, make sure that ZPOOL_IMPORT_PATH is set
  # to something we can use later with the real import(s). We want to
  # make sure we find all by* dirs, BUT by-vdev should be first (if it

  ###

  /dev/chassis/SYS/DOM0p2 is one dev of the rpool 3-way mirror [the
  others are /dev/chassis/SYS/DOM1p2 and /dev/nvme0n1p2]. DOM* are SM
  SuperDOMs sitting on */ata[56]/* bus, but get handled s scsi devices
  as well. Unfortunately things like 'udevadm settle' or 'udevadm settle
  --exit-if-exists=/dev/chassis/SYS/DOM0p2' or 'udevadm trigger
  --verbose --type=devices --subsystem-match=scsi_disk' did not fix the
  problem. Not sure whether there is a way to say, wait until scsi
  subsystem [scan] has been finished.

  To get a better idea I'll attach 2 files: xxxlong-fail.out shows the
  debug output when booting the vanilla focal, xxxlong-patched.out shows
  the debug output with the patch 

[Kernel-packages] [Bug 1826332] Re: Something sends bad ACPI messages

[Jens Finkhäuser]

Probably eventually, sure. But my life is too busy for that right now.
Please test the version I reported?

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

Title:
  Something sends bad ACPI messages

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Duplicate of #1744737

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-47-generic 4.15.0-47.50
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   jens   8470 F...m pulseaudio
   /dev/snd/controlC0:  jens   8470 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 25 09:18:07 2019
  HibernationDevice: RESUME=UUID=a79a66e4-84c7-4763-ac78-01a4e4919103
  InstallationDate: Installed on 2017-08-04 (628 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 20J6CTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-11-12 (163 days ago)
  dmi.bios.date: 02/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0FET48W (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20J6CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0FET48W(1.28):bd02/25/2019:svnLENOVO:pn20J6CTO1WW:pvrThinkPadT470p:rvnLENOVO:rn20J6CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470p
  dmi.product.name: 20J6CTO1WW
  dmi.product.version: ThinkPad T470p
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1840854] Re: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs

[Jens Elkner]

Hi Jeff,

hmm, didn't get notified by launchpad about your answer :(((. Anyway,
tried another machine with 4.15.0-91-generic and indeed, it seems to be
fixed.

Now the problem is, that our GPU machines are running 4.15.0-58-generic
and cannot be upgraded because all the nvidia stuff is very picky and we
do not have the time to upgrade the cluster to a new kernel version.

Therefore the question: is this just a driver problem? Copying over the
kmod from a 4.15.0-91 isn't probably a problem, I guess. Or rebuilding
the kmod for 4.15.0-58 may work out of the box as well...

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

Title:
  mlx5_core reports hardware checksum error for padded packets on
  Mellanox NICs

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

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

  [Impact]

  On machines equipped with Mellanox NIC's, in this particular case,
  Mellanox 5 series NICs using the mlx5_core driver, after installing
  4.15.0-56 or later there is the following kernel splat:

  bond0: hw csum failure
  CPU: 63 PID: 2473 Comm: in:imklog Tainted: P OE 4.15.0-58-generic 
#64~16.04.1-Ubuntu
  Call Trace:
  
  dump_stack+0x63/0x8b
  netdev_rx_csum_fault+0x38/0x40
  __skb_checksum_complete+0xc0/0xd0
  nf_ip_checksum+0xca/0xf0
  tcp_error+0xe0/0x1a0 [nf_conntrack]
  ? tcp_v4_rcv+0x7c6/0xa70
  nf_conntrack_in+0xde/0x520 [nf_conntrack]
  ipv4_conntrack_in+0x1c/0x20 [nf_conntrack_ipv4]
  nf_hook_slow+0x48/0xd0
  ? skb_send_sock+0x50/0x50
  ip_rcv+0x30f/0x370
  ? inet_del_offload+0x40/0x40
  __netif_receive_skb_core+0x879/0xba0
  ? tcp4_gro_receive+0x117/0x1b0
  __netif_receive_skb+0x18/0x60
  ? __netif_receive_skb+0x18/0x60
  netif_receive_skb_internal+0x45/0xf0
  napi_gro_receive+0xd0/0xf0
  mlx5e_handle_rx_cqe_mpwrq+0x4a1/0x8a0 [mlx5_core]
  mlx5e_poll_rx_cq+0xc3/0x880 [mlx5_core]
  mlx5e_napi_poll+0x9b/0x280 [mlx5_core]
  net_rx_action+0x265/0x3b0
  __do_softirq+0xf5/0x2a8
  irq_exit+0xca/0xd0
  do_IRQ+0x57/0xe0
  common_interrupt+0x8c/0x8c
  

  In 4.15.0-56, a commit was added from upstream -stable that introduced
  an optimisation for checksumming packets which have had zero bytes
  padded to the end of the packet.

  commit 88078d98d1bb085d72af8437707279e203524fa5
  Author: Eric Dumazet 
  Date: Wed Apr 18 11:43:15 2018 -0700
  subject: net: pskb_trim_rcsum() and CHECKSUM_COMPLETE are friends

  You can read it here:
  
https://github.com/torvalds/linux/commit/88078d98d1bb085d72af8437707279e203524fa5

  It was discussed in this bugzilla link:
  https://bugzilla.kernel.org/show_bug.cgi?id=201849

  This commit causes problems with a number of NIC devices, including Mellanox.
  This is best described by the maintainer, Dimitris Michailidis:

  > > > MLNX devices have an issue with packets that are padded past the end of
  > > > the L3 payload with bytes that aren't all 0s. They use a mode of 
checksum
  > > > reporting which should be including the padding bytes but MLNX devices
  > > > leave those out. When the padding bytes aren't all 0 this omission 
causes
  > > > a checksum error. This device behavior has existed for a long time but 
it
  > > > has begun causing errors only this year. Before a padded packet had its
  > HW
  > > > checksum ignored so it wasn't material what HW had reported. More
  > recently
  > > > padded packet checksums started using the HW value and now it is
  > > > noticeable when that value isn't right.

  Now, some routers stick additional information in the zero padding
  section on occasion, which will change the hardware checksum. Since
  the hardware checksum was ignored until 4.15.0-56 with
  88078d98d1bb085d72af8437707279e203524fa5, this wasn't an issue. But
  with the optimisation, we start running into trouble since the
  hardware checksums no longer match what the kernel is expecting.

  [Fix]

  This was fixed for Mellanox 4 and 5 series drivers recently.

  Mellanox 4: 74abc07dee613086f9c0ded9e263ddc959a6de04
  
https://github.com/torvalds/linux/commit/74abc07dee613086f9c0ded9e263ddc959a6de04

  Mellanox 5: e8c8b53ccaff568fef4c13a6ccaf08bf241aa01a
  
https://github.com/torvalds/linux/commit/e8c8b53ccaff568fef4c13a6ccaf08bf241aa01a

  This customer hit the issue with mlx5_core driver, so the fix is:

  commit e8c8b53ccaff568fef4c13a6ccaf08bf241aa01a
  Author: Cong Wang 
  Date: Mon Dec 3 22:14:04 2018 -0800
  subject: net/mlx5e: Force CHECKSUM_UNNECESSARY for short ethernet frames

  This is actually present in 4.15.0-59, which is currently sitting in
  -proposed.

  The commits are a part of 4.9.156, 4.14.99, 4.19.21 upstream -stable
  releases, and have been pulled into bionic as a part of LP #1837664

  [Testcase]

  Simply try and bring an interface up on a machine with Mellanox series
  5 NICs.

  When a packet comes through which is smaller 

[Kernel-packages] [Bug 1614953] Re: hw csum failure when IPv6 interfaces configured in netdev_rx_csum_fault+0x38/0x40

[Jens Elkner]

Getting it all the time:

[Apr13 04:28] kino6_0: hw csum failure
[  +0.003777] CPU: 18 PID: 0 Comm: swapper/18 Tainted: P   OE
4.15.0-58-generic #64-Ubuntu
[  +0.03] Hardware name: GIGABYTE G291-281-00/MG51-G21-00, BIOS R06 
11/19/2019
[  +0.01] Call Trace:
[  +0.03]  
[  +0.10]  dump_stack+0x63/0x8b
[  +0.08]  netdev_rx_csum_fault+0x38/0x40
[  +0.03]  __skb_checksum_complete+0xbc/0xd0
[  +0.05]  nf_ip_checksum+0xc3/0xf0
[  +0.17]  tcp_error+0x162/0x1c0 [nf_conntrack]
[  +0.07]  ? kfree_skbmem+0x5f/0x70
[  +0.04]  ? consume_skb+0x34/0x90
[  +0.11]  nf_conntrack_in+0x14f/0x500 [nf_conntrack]
[  +0.09]  ? csum_partial_ext+0x9/0x10
[  +0.04]  ? __skb_checksum+0x6b/0x300
[  +0.06]  ipv4_conntrack_in+0x1c/0x20 [nf_conntrack_ipv4]
[  +0.05]  nf_hook_slow+0x48/0xc0
[  +0.04]  ? skb_send_sock+0x50/0x50
[  +0.05]  ip_rcv+0x2fa/0x360
[  +0.03]  ? inet_del_offload+0x40/0x40
[  +0.04]  __netif_receive_skb_core+0x432/0xb40
[  +0.04]  ? tcp4_gro_receive+0x137/0x1a0
[  +0.03]  __netif_receive_skb+0x18/0x60
[  +0.03]  ? __netif_receive_skb+0x18/0x60
[  +0.04]  netif_receive_skb_internal+0x45/0xe0
[  +0.03]  napi_gro_receive+0xc5/0xf0
[  +0.34]  mlx5e_handle_rx_cqe_mpwrq+0x465/0x860 [mlx5_core]
[  +0.29]  mlx5e_poll_rx_cq+0xd1/0x8b0 [mlx5_core]
[  +0.25]  mlx5e_napi_poll+0x9d/0x290 [mlx5_core]
[  +0.04]  net_rx_action+0x140/0x3a0
[  +0.06]  __do_softirq+0xe4/0x2d4
[  +0.06]  irq_exit+0xc5/0xd0
[  +0.04]  do_IRQ+0x8a/0xe0
[  +0.03]  common_interrupt+0x8c/0x8c
[  +0.02]  
[  +0.05] RIP: 0010:cpuidle_enter_state+0xa7/0x2f0
[  +0.05] RSP: 0018:a278002b3e68 EFLAGS: 0246 ORIG_RAX: 
ffdd
[  +0.04] RAX: 970ebeea2840 RBX: 0008672cdbad1064 RCX: 001f
[  +0.02] RDX: 0008672cdbad1064 RSI: f3a434de6285 RDI: 
[  +0.02] RBP: a278002b3ea8 R08: 0004 R09: 00022080
[  +0.02] R10: a278002b3e38 R11: 00137021632d21b0 R12: c277ff683298
[  +0.01] R13: 0003 R14: aa172e78 R15: 
[  +0.05]  ? cpuidle_enter_state+0x97/0x2f0
[  +0.03]  cpuidle_enter+0x17/0x20
[  +0.05]  call_cpuidle+0x23/0x40
[  +0.04]  do_idle+0x18c/0x1f0
[  +0.05]  cpu_startup_entry+0x73/0x80
[  +0.04]  start_secondary+0x1ab/0x200
[  +0.05]  secondary_startup_64+0xa5/0xb0

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

Title:
  hw csum failure when IPv6 interfaces configured in
  netdev_rx_csum_fault+0x38/0x40

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Xenial:
  Expired
Status in linux source package in Yakkety:
  Expired

Bug description:
  Since I started using IPv6 I noticed the following kernel error:

  Thu Aug 18 15:05:01 2016] : hw csum failure
  [Thu Aug 18 15:05:01 2016] CPU: 5 PID: 11086 Comm: Chrome_IOThread Tainted: P 
  OE   4.4.0-34-generic #53-Ubuntu
  [Thu Aug 18 15:05:01 2016] Hardware name: Gigabyte Technology Co., Ltd. To be 
filled by O.E.M./Z77-D3H, BIOS F22 11/14/2013
  [Thu Aug 18 15:05:01 2016]  0286 c05989f2 
8807573dfcd0 813f11b3
  [Thu Aug 18 15:05:01 2016]   0008 
8807573dfce8 8171f6e8
  [Thu Aug 18 15:05:01 2016]  0074 8807573dfd30 
8171639b fe091360
  [Thu Aug 18 15:05:01 2016] Call Trace:
  [Thu Aug 18 15:05:01 2016]  [] dump_stack+0x63/0x90
  [Thu Aug 18 15:05:01 2016]  [] 
netdev_rx_csum_fault+0x38/0x40
  [Thu Aug 18 15:05:01 2016]  [] 
skb_copy_and_csum_datagram_msg+0xeb/0x100
  [Thu Aug 18 15:05:01 2016]  [] udpv6_recvmsg+0x233/0x670
  [Thu Aug 18 15:05:01 2016]  [] inet_recvmsg+0x7e/0xb0
  [Thu Aug 18 15:05:01 2016]  [] sock_recvmsg+0x3b/0x50
  [Thu Aug 18 15:05:01 2016]  [] SYSC_recvfrom+0xe1/0x160
  [Thu Aug 18 15:05:01 2016]  [] ? wake_up_q+0x70/0x70
  [Thu Aug 18 15:05:01 2016]  [] SyS_recvfrom+0xe/0x10
  [Thu Aug 18 15:05:01 2016]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71

  It repeats periodically:

  $ dmesg -T | grep 'hw csum failure' | wc -l
  201

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 19 13:47:54 2016
  HibernationDevice: RESUME=UUID=066c8903-7f5e-43d5-b48f-76d33c4558f2
  InstallationDate: Installed on 2016-04-24 (116 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1743529] Re: Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic -not syncing: Out of memory message when crash is triggered.

[Jens Elkner]

kdump package is crap, because it is using a different image (initrd)
than update-initramfs creates, so /boot/initrd.img-* !=
/var/lib/kdump/initrd.img-* . Yes, they may have the same name, but not
the same content. What a hugh bullshit! So no wonder, why one has to
waste several hours to find out, why /etc/systemd/network/* get not
honored. Crap, crap, crap!

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

Title:
  Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic
  -not syncing: Out of memory message when crash is triggered.

Status in The Ubuntu-power-systems project:
  Fix Released
Status in kexec-tools package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Released
Status in kexec-tools source package in Artful:
  Fix Released
Status in kexec-tools source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Latest kexec-tools is needed to load/kexec recent kernels. For older 
releases, like xenial, it's needed to support linux-hwe kernels.

  [Regression Potential]
  It might fail to load the GA kernels, like a 4.4 kernel on xenial.

  [Test case]
  Different kernels on different architectures have been tested.

  
  == Comment: #0 - INDIRA P. JOGA
  Problem Description:
  ===
  System hung with kernel panic Kernel panic - not syncing: Out of memory 
message when crash is triggered

  Steps to re-create:
  ==
  > Installed ubuntu1804 daily build on Witherspoon test system
  root@whip:~# uname -a
  Linux whip 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
  root@whip:~# uname -r
  4.13.0-17-generic

  > root@whip:~# free -h
    totalusedfree  shared  buff/cache   
available
  Mem:   507G2.0G504G 19M728M
503G
  Swap:  2.0G  0B2.0G

  > Edited the grub /etc/default/grub.d/kexec-tools.cfg file and set the
  crash kernel parameter=4096M

  > Updated grub using update-grub command and reboot system.

  cat root@whip:~# cat /proc/cmdline
  root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet 
crashkernel=4096M

  > kdump status before triggering crash

  root@whip:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-17-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.13.0-17-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p 
--command-line="root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet 
irqpoll noirqdistrib nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img 
/var/lib/kdump/vmlinuz

  root@whip:~# kdump-config status
  current state   : ready to kdump

  >  Enabled sysrq
  root@whip:~# sysctl -w kernel.sysrq=1
  kernel.sysrq = 1

  > Triggered crash and it hangs with kernel panic- OOM message as below

  root@whip:~# echo c > /proc/sysrq-trigger
  [   85.731415] sysrq: SysRq : Trigger a crash
  [   85.731472] Unable to handle kernel paging request for data at address 
0x
  [   85.731584] Faulting instruction address: 0xc078f588
  [   85.731670] Oops: Kernel access of bad area, sig: 11 [#1]
  [   85.731744] SMP NR_CPUS=2048
  [   85.731745] NUMA
  [   85.731790] PowerNV
  [   85.731853] Modules linked in: rpcsec_gss_krb5 nfsv4 nfs fscache sctp_diag 
sctp dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag 
af_packet_diag netlink_diag binfmt_misc vmx_crypto crct10dif_vpmsum ofpart 
cmdlinepart idt_89hpesx powernv_flash ipmi_powernv opal_prd ibmpowernv mtd 
ipmi_devintf ipmi_msghandler at24 uio_pdrv_genirq uio dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua nfsd auth_rpcgss sch_fq_codel nfs_acl lockd grace 
sunrpc ip_tables x_tables autofs4 btrfs xor raid6_pq nouveau bnx2x ast 
i2c_algo_bit ttm drm_kms_helper mdio libcrc32c crc32c_vpmsum mlx5_core 
syscopyarea sysfillrect sysimgblt fb_sys_fops tg3 drm ahci mlxfw libahci nvme 
devlink nvme_core
  [   85.732704] CPU: 10 PID: 4316 Comm: bash Not tainted 4.13.0-17-generic 
#20-Ubuntu
  [   85.732764] task: c03fcb141700 task.stack: c03fc2374000
  [   85.732858] NIP: c078f588 LR: c07904b8 CTR: 
c078f560
  [   85.732977] REGS: c03fc23779f0 TRAP: 0300   Not tainted  
(4.13.0-17-generic)
  [   85.733066] MSR: 90009033 
  [   85.733075]   CR: 2842  XER: 2004
  [   85.733201] CFAR: c07904b4 DAR:  DSISR: 4200 
SOFTE: 1
  [   85.733201] GPR00: c07904b8 c03fc2377c70 c15f6000 
0063
  [   85.733201] GPR04: c03feedfade8 

[Kernel-packages] [Bug 1840854] Re: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs

[Jens Elkner]

We use 'Linux kino6 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux' (Ubuntu 18.04.3 LTS) and see
all the time 'hw csum failure's:

[ +28.297139] kino6_0: hw csum failure
[  +0.003607] CPU: 12 PID: 0 Comm: swapper/12 Tainted: P   O 
4.15.0-58-generic #64-Ubuntu
[  +0.03] Hardware name: GIGABYTE G291-281-00/MG51-G21-00, BIOS R06 
11/19/2019
[  +0.01] Call Trace:
[  +0.02]  
[  +0.11]  dump_stack+0x63/0x8b
[  +0.08]  netdev_rx_csum_fault+0x38/0x40
[  +0.03]  __skb_checksum_complete+0xbc/0xd0
[  +0.05]  nf_ip_checksum+0xc3/0xf0
[  +0.18]  tcp_error+0x162/0x1c0 [nf_conntrack]
[  +0.06]  ? ttwu_do_wakeup+0x1e/0x140
[  +0.11]  nf_conntrack_in+0x14f/0x500 [nf_conntrack]
[  +0.07]  ? csum_partial_ext+0x9/0x10
[  +0.07]  ? __skb_checksum+0x6b/0x300
[  +0.06]  ipv4_conntrack_in+0x1c/0x20 [nf_conntrack_ipv4]
[  +0.05]  nf_hook_slow+0x48/0xc0
[  +0.04]  ? skb_send_sock+0x50/0x50
[  +0.05]  ip_rcv+0x2fa/0x360
[  +0.03]  ? inet_del_offload+0x40/0x40
[  +0.04]  __netif_receive_skb_core+0x432/0xb40
[  +0.03]  ? update_curr+0xf2/0x1d0
[  +0.04]  ? tcp4_gro_receive+0x137/0x1a0
[  +0.03]  __netif_receive_skb+0x18/0x60
[  +0.03]  ? __netif_receive_skb+0x18/0x60
[  +0.03]  netif_receive_skb_internal+0x45/0xe0
[  +0.04]  napi_gro_receive+0xc5/0xf0
[  +0.36]  mlx5e_handle_rx_cqe_mpwrq+0x465/0x860 [mlx5_core]
[  +0.28]  mlx5e_poll_rx_cq+0xd1/0x8b0 [mlx5_core]
[  +0.25]  mlx5e_napi_poll+0x9d/0x290 [mlx5_core]
[  +0.04]  net_rx_action+0x140/0x3a0
[  +0.05]  __do_softirq+0xe4/0x2d4
[  +0.06]  irq_exit+0xc5/0xd0
[  +0.03]  do_IRQ+0x8a/0xe0
[  +0.03]  common_interrupt+0x8c/0x8c
[  +0.02]  
[  +0.05] RIP: 0010:cpuidle_enter_state+0xa7/0x2f0
[  +0.02] RSP: 0018:ad7a00283e68 EFLAGS: 0246 ORIG_RAX: 
ffdd
[  +0.04] RAX: 89f13fd22840 RBX: 02273da74e91 RCX: 001f
[  +0.02] RDX: 02273da74e91 RSI: feba65558937 RDI: 
[  +0.02] RBP: ad7a00283ea8 R08: 0004 R09: 00022080
[  +0.01] R10: ad7a00283e38 R11: 07e0dcda6658 R12: cd5a00503298
[  +0.02] R13: 0003 R14: b3f72e78 R15: 
[  +0.04]  ? cpuidle_enter_state+0x97/0x2f0
[  +0.03]  cpuidle_enter+0x17/0x20
[  +0.05]  call_cpuidle+0x23/0x40
[  +0.04]  do_idle+0x18c/0x1f0
[  +0.04]  cpu_startup_entry+0x73/0x80
[  +0.05]  start_secondary+0x1ab/0x200
[  +0.05]  secondary_startup_64+0xa5/0xb0

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

Title:
  mlx5_core reports hardware checksum error for padded packets on
  Mellanox NICs

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

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

  [Impact]

  On machines equipped with Mellanox NIC's, in this particular case,
  Mellanox 5 series NICs using the mlx5_core driver, after installing
  4.15.0-56 or later there is the following kernel splat:

  bond0: hw csum failure
  CPU: 63 PID: 2473 Comm: in:imklog Tainted: P OE 4.15.0-58-generic 
#64~16.04.1-Ubuntu
  Call Trace:
  
  dump_stack+0x63/0x8b
  netdev_rx_csum_fault+0x38/0x40
  __skb_checksum_complete+0xc0/0xd0
  nf_ip_checksum+0xca/0xf0
  tcp_error+0xe0/0x1a0 [nf_conntrack]
  ? tcp_v4_rcv+0x7c6/0xa70
  nf_conntrack_in+0xde/0x520 [nf_conntrack]
  ipv4_conntrack_in+0x1c/0x20 [nf_conntrack_ipv4]
  nf_hook_slow+0x48/0xd0
  ? skb_send_sock+0x50/0x50
  ip_rcv+0x30f/0x370
  ? inet_del_offload+0x40/0x40
  __netif_receive_skb_core+0x879/0xba0
  ? tcp4_gro_receive+0x117/0x1b0
  __netif_receive_skb+0x18/0x60
  ? __netif_receive_skb+0x18/0x60
  netif_receive_skb_internal+0x45/0xf0
  napi_gro_receive+0xd0/0xf0
  mlx5e_handle_rx_cqe_mpwrq+0x4a1/0x8a0 [mlx5_core]
  mlx5e_poll_rx_cq+0xc3/0x880 [mlx5_core]
  mlx5e_napi_poll+0x9b/0x280 [mlx5_core]
  net_rx_action+0x265/0x3b0
  __do_softirq+0xf5/0x2a8
  irq_exit+0xca/0xd0
  do_IRQ+0x57/0xe0
  common_interrupt+0x8c/0x8c
  

  In 4.15.0-56, a commit was added from upstream -stable that introduced
  an optimisation for checksumming packets which have had zero bytes
  padded to the end of the packet.

  commit 88078d98d1bb085d72af8437707279e203524fa5
  Author: Eric Dumazet 
  Date: Wed Apr 18 11:43:15 2018 -0700
  subject: net: pskb_trim_rcsum() and CHECKSUM_COMPLETE are friends

  You can read it here:
  
https://github.com/torvalds/linux/commit/88078d98d1bb085d72af8437707279e203524fa5

  It was discussed in this bugzilla link:
  https://bugzilla.kernel.org/show_bug.cgi?id=201849

  This commit causes problems with a number of NIC devices, including Mellanox.
  This is best described by the maintainer, Dimitris Michailidis:

  > > > MLNX devices have an issue with packets that 

[Kernel-packages] [Bug 1826332] Re: Something sends bad ACPI messages

[Jens Finkhäuser]

Original report: https://bugs.launchpad.net/ubuntu/+source/linux-
hwe/+bug/1744737

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

Title:
  Something sends bad ACPI messages

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Duplicate of #1744737

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-47-generic 4.15.0-47.50
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   jens   8470 F...m pulseaudio
   /dev/snd/controlC0:  jens   8470 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 25 09:18:07 2019
  HibernationDevice: RESUME=UUID=a79a66e4-84c7-4763-ac78-01a4e4919103
  InstallationDate: Installed on 2017-08-04 (628 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 20J6CTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-11-12 (163 days ago)
  dmi.bios.date: 02/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0FET48W (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20J6CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0FET48W(1.28):bd02/25/2019:svnLENOVO:pn20J6CTO1WW:pvrThinkPadT470p:rvnLENOVO:rn20J6CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470p
  dmi.product.name: 20J6CTO1WW
  dmi.product.version: ThinkPad T470p
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1826332] [NEW] Something sends bad ACPI messages

[Jens Finkhäuser]

Public bug reported:

Duplicate of #1744737

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-47-generic 4.15.0-47.50
ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
Uname: Linux 4.15.0-47-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   jens   8470 F...m pulseaudio
 /dev/snd/controlC0:  jens   8470 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 25 09:18:07 2019
HibernationDevice: RESUME=UUID=a79a66e4-84c7-4763-ac78-01a4e4919103
InstallationDate: Installed on 2017-08-04 (628 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: LENOVO 20J6CTO1WW
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-47-generic N/A
 linux-backports-modules-4.15.0-47-generic  N/A
 linux-firmware 1.173.3
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-11-12 (163 days ago)
dmi.bios.date: 02/25/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0FET48W (1.28 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20J6CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR0FET48W(1.28):bd02/25/2019:svnLENOVO:pn20J6CTO1WW:pvrThinkPadT470p:rvnLENOVO:rn20J6CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T470p
dmi.product.name: 20J6CTO1WW
dmi.product.version: ThinkPad T470p
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug bionic uec-images

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

Title:
  Something sends bad ACPI messages

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Duplicate of #1744737

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-47-generic 4.15.0-47.50
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   jens   8470 F...m pulseaudio
   /dev/snd/controlC0:  jens   8470 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 25 09:18:07 2019
  HibernationDevice: RESUME=UUID=a79a66e4-84c7-4763-ac78-01a4e4919103
  InstallationDate: Installed on 2017-08-04 (628 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 20J6CTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-11-12 (163 days ago)
  dmi.bios.date: 02/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0FET48W (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20J6CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0FET48W(1.28):bd02/25/2019:svnLENOVO:pn20J6CTO1WW:pvrThinkPadT470p:rvnLENOVO:rn20J6CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470p
  dmi.product.name: 20J6CTO1WW
  dmi.product.version: ThinkPad T470p
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1818690] Re: Touchpad not detected

[Jens]

Found a solution in this thread: https://askubuntu.com/questions/525629
/touchpad-is-not-recognized

Editing a line in /etc/default/grub to look like this:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.reset i8042.nomux
i8042.nopnp i8042.noloop"

did the trick.

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

Title:
  Touchpad not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Built-in touchpad is not detected/working. The output of cat
  /proc/bus/input/devices is attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-15-generic 4.18.0-15.16
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jens   2250 F pulseaudio
   /dev/snd/controlC1:  jens   2250 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  5 16:23:26 2019
  InstallationDate: Installed on 2019-03-01 (3 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Medion Akoya P6647
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=2f3d4c9a-9f90-41d6-bc89-9feb60802f5a ro quiet splash 
nouveau.modeset=0 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.175.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C15B.606
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Akoya P6647
  dmi.board.vendor: Medion
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Medion
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC15B.606:bd01/29/2015:svnMedion:pnAkoyaP6647:pvr1.0:rvnMedion:rnAkoyaP6647:rvr1.0:cvnMedion:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: MEDION Family
  dmi.product.name: Akoya P6647
  dmi.product.sku: 0
  dmi.product.version: 1.0
  dmi.sys.vendor: Medion

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

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

[Kernel-packages] [Bug 1818690] [NEW] Touchpad not detected

[Jens Welsing]

Public bug reported:

Built-in touchpad is not detected/working. The output of cat
/proc/bus/input/devices is attached.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-15-generic 4.18.0-15.16
ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jens   2250 F pulseaudio
 /dev/snd/controlC1:  jens   2250 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar  5 16:23:26 2019
InstallationDate: Installed on 2019-03-01 (3 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: Medion Akoya P6647
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=2f3d4c9a-9f90-41d6-bc89-9feb60802f5a ro quiet splash 
nouveau.modeset=0 vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-15-generic N/A
 linux-backports-modules-4.18.0-15-generic  N/A
 linux-firmware 1.175.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/29/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: C15B.606
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: Akoya P6647
dmi.board.vendor: Medion
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Medion
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC15B.606:bd01/29/2015:svnMedion:pnAkoyaP6647:pvr1.0:rvnMedion:rnAkoyaP6647:rvr1.0:cvnMedion:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: MEDION Family
dmi.product.name: Akoya P6647
dmi.product.sku: 0
dmi.product.version: 1.0
dmi.sys.vendor: Medion

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


** Tags: amd64 apport-bug cosmic

** Attachment added: "List of devices"
   https://bugs.launchpad.net/bugs/1818690/+attachment/5243707/+files/devices

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

Title:
  Touchpad not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Built-in touchpad is not detected/working. The output of cat
  /proc/bus/input/devices is attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-15-generic 4.18.0-15.16
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jens   2250 F pulseaudio
   /dev/snd/controlC1:  jens   2250 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  5 16:23:26 2019
  InstallationDate: Installed on 2019-03-01 (3 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Medion Akoya P6647
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=2f3d4c9a-9f90-41d6-bc89-9feb60802f5a ro quiet splash 
nouveau.modeset=0 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.175.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C15B.606
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Akoya P6647
  dmi.board.vendor: Medion
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Medion
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC15B.606:bd01/29/2015:svnMedion:pnAkoyaP6647:pvr1.0:rvnMedion:rnAkoyaP6647:rvr1.0:cvnMedion:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: MEDION Family
  dmi.product.name: Akoya P6647
  dmi.product.sku: 0
  dmi.product.version: 1.0
  dmi.sys.vendor: Medion

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

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

[Kernel-packages] [Bug 1800861] Re: DBI.pm is buggy and out of date

[Jens Elkner]

** Package changed: linux (Ubuntu) => libdbi-perl (Ubuntu)

** Changed in: libdbi-perl (Ubuntu)
   Status: Incomplete => In Progress

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

Title:
  DBI.pm is buggy and out of date

Status in libdbi-perl package in Ubuntu:
  In Progress

Bug description:
  /usr/lib/x86_64-linux-gnu/perl5/5.22/DBI.pm (xenial with latest updates) is 
buggy.
  To test, simply run:

  ---schnipp---
  #!/usr/bin/perl

  require DBI;

  my $dbfile = "/tmp/notifications_sqlite.dat";
  my $dbh = DBI->connect("dbi:SQLite:dbname=$dbfile",'','');
  my $qu_attr = "SELECT * FROM notifications_attr WHERE keyref = '21';";
  my $notifhr = $dbh->selectall_arrayref($qu, { Slice => {} });
  ---schnapp---

  It seems, that this bug got already fixed upstream ~ 2 years ago with
  DBI version 1.635 (however, most recent version is 1.542).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdbi-perl/+bug/1800861/+subscriptions

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

[Kernel-packages] [Bug 1800861] [NEW] DBI.pm is buggy and out of date

[Jens Elkner]

Public bug reported:

/usr/lib/x86_64-linux-gnu/perl5/5.22/DBI.pm (xenial with latest updates) is 
buggy.
To test, simply run:

---schnipp---
#!/usr/bin/perl

require DBI;

my $dbfile = "/tmp/notifications_sqlite.dat";
my $dbh = DBI->connect("dbi:SQLite:dbname=$dbfile",'','');
my $qu_attr = "SELECT * FROM notifications_attr WHERE keyref = '21';";
my $notifhr = $dbh->selectall_arrayref($qu, { Slice => {} });
---schnapp---

It seems, that this bug got already fixed upstream ~ 2 years ago with
DBI version 1.635 (however, most recent version is 1.542).

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

Title:
  DBI.pm is buggy and out of date

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  /usr/lib/x86_64-linux-gnu/perl5/5.22/DBI.pm (xenial with latest updates) is 
buggy.
  To test, simply run:

  ---schnipp---
  #!/usr/bin/perl

  require DBI;

  my $dbfile = "/tmp/notifications_sqlite.dat";
  my $dbh = DBI->connect("dbi:SQLite:dbname=$dbfile",'','');
  my $qu_attr = "SELECT * FROM notifications_attr WHERE keyref = '21';";
  my $notifhr = $dbh->selectall_arrayref($qu, { Slice => {} });
  ---schnapp---

  It seems, that this bug got already fixed upstream ~ 2 years ago with
  DBI version 1.635 (however, most recent version is 1.542).

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

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

[Kernel-packages] [Bug 1790181] Re: /proc/diskstats shows weird values

[Jens Peter]

On my laptop with a SATA ssd I also have higher reported times than
process real time, albeit not by such a huge margin. Only a factor of
2-4 too high.

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

Title:
  /proc/diskstats shows weird values

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  For one block device on one of my servers munin shows abnormally high
  latency.

  When querying /proc/diskstats manually, the device in question shows:
 8  32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 
1347171224 63 54302956 1357481880

  
  Sanity check:
  If I divide the 7th value by the 4th value I get a avg read latency of about 
10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms 
that munin reports.

  The problem:
  If I divide the 11th value by the 8th value I get an avg write latency of 
1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported 
by munin. Now this is an SD card and it is slow, but not THAT slow..

  
  To confirm unexpected values, I measured some activity:

  
  $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync;
  cat /proc/diskstats
  100+0 records in
  100+0 records out
  104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s
  
  real  0m8,132s
  user  0m0,000s
  sys   0m0,007s

  The reported time spent writing went from 1353896856 before the test to 
1356759112 after the test.
  The difference is 2862256 ms or about 2800 seconds that supposedly passed in 
just over 26 real time seconds.
  I repeated the test with count=1 and got 5780 ms IO write time reported in .7 
s realtime.

  
  #1297522 describes a similar error but I have no idea if the cause is related.


  System information:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018
  x86_64 x86_64 GNU/Linux

  /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 
cards.
  The system is a Dell R530.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug  11 22:30 seq
   crw-rw 1 root audio 116, 33 Aug  11 22:30 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=UUID=719079af-279c-46cd-9438-01086a2cb16e
  InstallationDate: Installed on 2016-03-29 (885 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  MachineType: Dell Inc. PowerEdge R530
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-30-generic N/A
   linux-backports-modules-4.15.0-30-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-30-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 10/05/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.4
  dmi.board.name: 0HFG24
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R530
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1790181] Re: /proc/diskstats shows weird values

[Jens Peter]

Testing with http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc2/
shows:

Writes on the sd card are still reported about a factor 1000 too high, e.g. 
2700ms = 27000s where I expect around 27s.
I tried on an nvme ssd with the same result, just smaller numbers and 
/dev/urandom was the bottleneck. 

I suspect that the kernel is actually reporting µs instead of ms
although that is wild speculation.

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

Title:
  /proc/diskstats shows weird values

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  For one block device on one of my servers munin shows abnormally high
  latency.

  When querying /proc/diskstats manually, the device in question shows:
 8  32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 
1347171224 63 54302956 1357481880

  
  Sanity check:
  If I divide the 7th value by the 4th value I get a avg read latency of about 
10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms 
that munin reports.

  The problem:
  If I divide the 11th value by the 8th value I get an avg write latency of 
1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported 
by munin. Now this is an SD card and it is slow, but not THAT slow..

  
  To confirm unexpected values, I measured some activity:

  
  $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync;
  cat /proc/diskstats
  100+0 records in
  100+0 records out
  104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s
  
  real  0m8,132s
  user  0m0,000s
  sys   0m0,007s

  The reported time spent writing went from 1353896856 before the test to 
1356759112 after the test.
  The difference is 2862256 ms or about 2800 seconds that supposedly passed in 
just over 26 real time seconds.
  I repeated the test with count=1 and got 5780 ms IO write time reported in .7 
s realtime.

  
  #1297522 describes a similar error but I have no idea if the cause is related.


  System information:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018
  x86_64 x86_64 GNU/Linux

  /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 
cards.
  The system is a Dell R530.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug  11 22:30 seq
   crw-rw 1 root audio 116, 33 Aug  11 22:30 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=UUID=719079af-279c-46cd-9438-01086a2cb16e
  InstallationDate: Installed on 2016-03-29 (885 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  MachineType: Dell Inc. PowerEdge R530
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-30-generic N/A
   linux-backports-modules-4.15.0-30-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-30-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 10/05/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.4
  dmi.board.name: 0HFG24
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R530
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1790181] Re: /proc/diskstats shows weird values

[Jens Peter]

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

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

Title:
  /proc/diskstats shows weird values

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  For one block device on one of my servers munin shows abnormally high
  latency.

  When querying /proc/diskstats manually, the device in question shows:
 8  32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 
1347171224 63 54302956 1357481880

  
  Sanity check:
  If I divide the 7th value by the 4th value I get a avg read latency of about 
10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms 
that munin reports.

  The problem:
  If I divide the 11th value by the 8th value I get an avg write latency of 
1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported 
by munin. Now this is an SD card and it is slow, but not THAT slow..

  
  To confirm unexpected values, I measured some activity:

  
  $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync;
  cat /proc/diskstats
  100+0 records in
  100+0 records out
  104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s
  
  real  0m8,132s
  user  0m0,000s
  sys   0m0,007s

  The reported time spent writing went from 1353896856 before the test to 
1356759112 after the test.
  The difference is 2862256 ms or about 2800 seconds that supposedly passed in 
just over 26 real time seconds.
  I repeated the test with count=1 and got 5780 ms IO write time reported in .7 
s realtime.

  
  #1297522 describes a similar error but I have no idea if the cause is related.


  System information:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018
  x86_64 x86_64 GNU/Linux

  /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 
cards.
  The system is a Dell R530.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug  11 22:30 seq
   crw-rw 1 root audio 116, 33 Aug  11 22:30 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=UUID=719079af-279c-46cd-9438-01086a2cb16e
  InstallationDate: Installed on 2016-03-29 (885 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  MachineType: Dell Inc. PowerEdge R530
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-30-generic N/A
   linux-backports-modules-4.15.0-30-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-30-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 10/05/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.4
  dmi.board.name: 0HFG24
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R530
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1790181] Re: /proc/diskstats shows weird values

[Jens Peter]

I noticed the bug only after I installed munin recently. I don't know
how long it may have existed before.

I will test the mainline kernel as soon as I can but since the machine
is used in production and can't be rebooted at will so testing probably
be 2 weeks out.

Thanks for your reply.

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

Title:
  /proc/diskstats shows weird values

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For one block device on one of my servers munin shows abnormally high
  latency.

  When querying /proc/diskstats manually, the device in question shows:
 8  32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 
1347171224 63 54302956 1357481880

  
  Sanity check:
  If I divide the 7th value by the 4th value I get a avg read latency of about 
10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms 
that munin reports.

  The problem:
  If I divide the 11th value by the 8th value I get an avg write latency of 
1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported 
by munin. Now this is an SD card and it is slow, but not THAT slow..

  
  To confirm unexpected values, I measured some activity:

  
  $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync;
  cat /proc/diskstats
  100+0 records in
  100+0 records out
  104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s
  
  real  0m8,132s
  user  0m0,000s
  sys   0m0,007s

  The reported time spent writing went from 1353896856 before the test to 
1356759112 after the test.
  The difference is 2862256 ms or about 2800 seconds that supposedly passed in 
just over 26 real time seconds.
  I repeated the test with count=1 and got 5780 ms IO write time reported in .7 
s realtime.

  
  #1297522 describes a similar error but I have no idea if the cause is related.


  System information:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018
  x86_64 x86_64 GNU/Linux

  /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 
cards.
  The system is a Dell R530.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug  11 22:30 seq
   crw-rw 1 root audio 116, 33 Aug  11 22:30 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=UUID=719079af-279c-46cd-9438-01086a2cb16e
  InstallationDate: Installed on 2016-03-29 (885 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  MachineType: Dell Inc. PowerEdge R530
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-30-generic N/A
   linux-backports-modules-4.15.0-30-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-30-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 10/05/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.4
  dmi.board.name: 0HFG24
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R530
  dmi.sys.vendor: Dell Inc.

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

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

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

[Jens Peter]

apport information

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

Title:
  /proc/diskstats shows weird values

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  For one block device on one of my servers munin shows abnormally high
  latency.

  When querying /proc/diskstats manually, the device in question shows:
 8  32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 
1347171224 63 54302956 1357481880

  
  Sanity check:
  If I divide the 7th value by the 4th value I get a avg read latency of about 
10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms 
that munin reports.

  The problem:
  If I divide the 11th value by the 8th value I get an avg write latency of 
1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported 
by munin. Now this is an SD card and it is slow, but not THAT slow..

  
  To confirm unexpected values, I measured some activity:

  
  $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync;
  cat /proc/diskstats
  100+0 records in
  100+0 records out
  104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s
  
  real  0m8,132s
  user  0m0,000s
  sys   0m0,007s

  The reported time spent writing went from 1353896856 before the test to 
1356759112 after the test.
  The difference is 2862256 ms or about 2800 seconds that supposedly passed in 
just over 26 real time seconds.
  I repeated the test with count=1 and got 5780 ms IO write time reported in .7 
s realtime.

  
  #1297522 describes a similar error but I have no idea if the cause is related.


  System information:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018
  x86_64 x86_64 GNU/Linux

  /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 
cards.
  The system is a Dell R530.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug  11 22:30 seq
   crw-rw 1 root audio 116, 33 Aug  11 22:30 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=UUID=719079af-279c-46cd-9438-01086a2cb16e
  InstallationDate: Installed on 2016-03-29 (885 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  MachineType: Dell Inc. PowerEdge R530
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-30-generic N/A
   linux-backports-modules-4.15.0-30-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-30-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 10/05/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.4
  dmi.board.name: 0HFG24
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R530
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1790181] Re: /proc/diskstats shows weird values

[Jens Peter]

apport information

** Tags added: apport-collected

** Description changed:

  For one block device on one of my servers munin shows abnormally high
  latency.
  
  When querying /proc/diskstats manually, the device in question shows:
 8  32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 
1347171224 63 54302956 1357481880
  
  
  Sanity check:
  If I divide the 7th value by the 4th value I get a avg read latency of about 
10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms 
that munin reports.
  
  The problem:
  If I divide the 11th value by the 8th value I get an avg write latency of 
1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported 
by munin. Now this is an SD card and it is slow, but not THAT slow..
  
  
  To confirm unexpected values, I measured some activity:
  
  
  $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync;
  cat /proc/diskstats
  100+0 records in
  100+0 records out
  104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s
  
  real  0m8,132s
  user  0m0,000s
  sys   0m0,007s
  
  The reported time spent writing went from 1353896856 before the test to 
1356759112 after the test.
  The difference is 2862256 ms or about 2800 seconds that supposedly passed in 
just over 26 real time seconds.
  I repeated the test with count=1 and got 5780 ms IO write time reported in .7 
s realtime.
  
  
  #1297522 describes a similar error but I have no idea if the cause is related.
  
  
  System information:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  
  Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018
  x86_64 x86_64 GNU/Linux
  
  /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 
cards.
  The system is a Dell R530.
+ --- 
+ ProblemType: Bug
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 Aug  11 22:30 seq
+  crw-rw 1 root audio 116, 33 Aug  11 22:30 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=UUID=719079af-279c-46cd-9438-01086a2cb16e
+ InstallationDate: Installed on 2016-03-29 (885 days ago)
+ InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
+ MachineType: Dell Inc. PowerEdge R530
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcFB: 0 mgadrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M
+ ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-30-generic N/A
+  linux-backports-modules-4.15.0-30-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-30-generic x86_64
+ UnreportableReason: This report is about a package that is not installed.
+ UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago)
+ UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
+ _MarkForUpload: False
+ dmi.bios.date: 10/05/2015
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.5.4
+ dmi.board.name: 0HFG24
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A01
+ dmi.chassis.type: 23
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr:
+ dmi.product.name: PowerEdge R530
+ dmi.sys.vendor: Dell Inc.

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

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

Title:
  /proc/diskstats shows weird values

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  For one block device on one of my servers munin shows abnormally high
  latency.

  When querying /proc/diskstats manually, the device in question shows:
 8  32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 
1347171224 63 54302956 1357481880

  
  Sanity check:
  If I divide the 7th value by the 4th value I get a avg read latency of about 
10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms 
that munin reports.

  The problem:
  If I divide the 11th 

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

[Jens Peter]

apport information

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

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

Title:
  /proc/diskstats shows weird values

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  For one block device on one of my servers munin shows abnormally high
  latency.

  When querying /proc/diskstats manually, the device in question shows:
 8  32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 
1347171224 63 54302956 1357481880

  
  Sanity check:
  If I divide the 7th value by the 4th value I get a avg read latency of about 
10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms 
that munin reports.

  The problem:
  If I divide the 11th value by the 8th value I get an avg write latency of 
1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported 
by munin. Now this is an SD card and it is slow, but not THAT slow..

  
  To confirm unexpected values, I measured some activity:

  
  $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync;
  cat /proc/diskstats
  100+0 records in
  100+0 records out
  104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s
  
  real  0m8,132s
  user  0m0,000s
  sys   0m0,007s

  The reported time spent writing went from 1353896856 before the test to 
1356759112 after the test.
  The difference is 2862256 ms or about 2800 seconds that supposedly passed in 
just over 26 real time seconds.
  I repeated the test with count=1 and got 5780 ms IO write time reported in .7 
s realtime.

  
  #1297522 describes a similar error but I have no idea if the cause is related.


  System information:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018
  x86_64 x86_64 GNU/Linux

  /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 
cards.
  The system is a Dell R530.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug  11 22:30 seq
   crw-rw 1 root audio 116, 33 Aug  11 22:30 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=UUID=719079af-279c-46cd-9438-01086a2cb16e
  InstallationDate: Installed on 2016-03-29 (885 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  MachineType: Dell Inc. PowerEdge R530
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-30-generic N/A
   linux-backports-modules-4.15.0-30-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-30-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 10/05/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.4
  dmi.board.name: 0HFG24
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R530
  dmi.sys.vendor: Dell Inc.

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

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

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

[Jens Peter]

apport information

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

Title:
  /proc/diskstats shows weird values

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  For one block device on one of my servers munin shows abnormally high
  latency.

  When querying /proc/diskstats manually, the device in question shows:
 8  32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 
1347171224 63 54302956 1357481880

  
  Sanity check:
  If I divide the 7th value by the 4th value I get a avg read latency of about 
10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms 
that munin reports.

  The problem:
  If I divide the 11th value by the 8th value I get an avg write latency of 
1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported 
by munin. Now this is an SD card and it is slow, but not THAT slow..

  
  To confirm unexpected values, I measured some activity:

  
  $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync;
  cat /proc/diskstats
  100+0 records in
  100+0 records out
  104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s
  
  real  0m8,132s
  user  0m0,000s
  sys   0m0,007s

  The reported time spent writing went from 1353896856 before the test to 
1356759112 after the test.
  The difference is 2862256 ms or about 2800 seconds that supposedly passed in 
just over 26 real time seconds.
  I repeated the test with count=1 and got 5780 ms IO write time reported in .7 
s realtime.

  
  #1297522 describes a similar error but I have no idea if the cause is related.


  System information:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018
  x86_64 x86_64 GNU/Linux

  /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 
cards.
  The system is a Dell R530.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug  11 22:30 seq
   crw-rw 1 root audio 116, 33 Aug  11 22:30 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=UUID=719079af-279c-46cd-9438-01086a2cb16e
  InstallationDate: Installed on 2016-03-29 (885 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  MachineType: Dell Inc. PowerEdge R530
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-30-generic N/A
   linux-backports-modules-4.15.0-30-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-30-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 10/05/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.4
  dmi.board.name: 0HFG24
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R530
  dmi.sys.vendor: Dell Inc.

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

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

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

[Jens Peter]

apport information

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

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

Title:
  /proc/diskstats shows weird values

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  For one block device on one of my servers munin shows abnormally high
  latency.

  When querying /proc/diskstats manually, the device in question shows:
 8  32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 
1347171224 63 54302956 1357481880

  
  Sanity check:
  If I divide the 7th value by the 4th value I get a avg read latency of about 
10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms 
that munin reports.

  The problem:
  If I divide the 11th value by the 8th value I get an avg write latency of 
1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported 
by munin. Now this is an SD card and it is slow, but not THAT slow..

  
  To confirm unexpected values, I measured some activity:

  
  $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync;
  cat /proc/diskstats
  100+0 records in
  100+0 records out
  104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s
  
  real  0m8,132s
  user  0m0,000s
  sys   0m0,007s

  The reported time spent writing went from 1353896856 before the test to 
1356759112 after the test.
  The difference is 2862256 ms or about 2800 seconds that supposedly passed in 
just over 26 real time seconds.
  I repeated the test with count=1 and got 5780 ms IO write time reported in .7 
s realtime.

  
  #1297522 describes a similar error but I have no idea if the cause is related.


  System information:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018
  x86_64 x86_64 GNU/Linux

  /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 
cards.
  The system is a Dell R530.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug  11 22:30 seq
   crw-rw 1 root audio 116, 33 Aug  11 22:30 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=UUID=719079af-279c-46cd-9438-01086a2cb16e
  InstallationDate: Installed on 2016-03-29 (885 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  MachineType: Dell Inc. PowerEdge R530
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-30-generic N/A
   linux-backports-modules-4.15.0-30-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-30-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 10/05/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.4
  dmi.board.name: 0HFG24
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R530
  dmi.sys.vendor: Dell Inc.

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

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

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

[Jens Peter]

apport information

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

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

Title:
  /proc/diskstats shows weird values

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  For one block device on one of my servers munin shows abnormally high
  latency.

  When querying /proc/diskstats manually, the device in question shows:
 8  32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 
1347171224 63 54302956 1357481880

  
  Sanity check:
  If I divide the 7th value by the 4th value I get a avg read latency of about 
10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms 
that munin reports.

  The problem:
  If I divide the 11th value by the 8th value I get an avg write latency of 
1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported 
by munin. Now this is an SD card and it is slow, but not THAT slow..

  
  To confirm unexpected values, I measured some activity:

  
  $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync;
  cat /proc/diskstats
  100+0 records in
  100+0 records out
  104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s
  
  real  0m8,132s
  user  0m0,000s
  sys   0m0,007s

  The reported time spent writing went from 1353896856 before the test to 
1356759112 after the test.
  The difference is 2862256 ms or about 2800 seconds that supposedly passed in 
just over 26 real time seconds.
  I repeated the test with count=1 and got 5780 ms IO write time reported in .7 
s realtime.

  
  #1297522 describes a similar error but I have no idea if the cause is related.


  System information:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018
  x86_64 x86_64 GNU/Linux

  /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 
cards.
  The system is a Dell R530.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug  11 22:30 seq
   crw-rw 1 root audio 116, 33 Aug  11 22:30 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=UUID=719079af-279c-46cd-9438-01086a2cb16e
  InstallationDate: Installed on 2016-03-29 (885 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  MachineType: Dell Inc. PowerEdge R530
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-30-generic N/A
   linux-backports-modules-4.15.0-30-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-30-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 10/05/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.4
  dmi.board.name: 0HFG24
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R530
  dmi.sys.vendor: Dell Inc.

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

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

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

[Jens Peter]

apport information

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

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

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

Title:
  /proc/diskstats shows weird values

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  For one block device on one of my servers munin shows abnormally high
  latency.

  When querying /proc/diskstats manually, the device in question shows:
 8  32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 
1347171224 63 54302956 1357481880

  
  Sanity check:
  If I divide the 7th value by the 4th value I get a avg read latency of about 
10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms 
that munin reports.

  The problem:
  If I divide the 11th value by the 8th value I get an avg write latency of 
1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported 
by munin. Now this is an SD card and it is slow, but not THAT slow..

  
  To confirm unexpected values, I measured some activity:

  
  $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync;
  cat /proc/diskstats
  100+0 records in
  100+0 records out
  104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s
  
  real  0m8,132s
  user  0m0,000s
  sys   0m0,007s

  The reported time spent writing went from 1353896856 before the test to 
1356759112 after the test.
  The difference is 2862256 ms or about 2800 seconds that supposedly passed in 
just over 26 real time seconds.
  I repeated the test with count=1 and got 5780 ms IO write time reported in .7 
s realtime.

  
  #1297522 describes a similar error but I have no idea if the cause is related.


  System information:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018
  x86_64 x86_64 GNU/Linux

  /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 
cards.
  The system is a Dell R530.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug  11 22:30 seq
   crw-rw 1 root audio 116, 33 Aug  11 22:30 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=UUID=719079af-279c-46cd-9438-01086a2cb16e
  InstallationDate: Installed on 2016-03-29 (885 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  MachineType: Dell Inc. PowerEdge R530
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-30-generic N/A
   linux-backports-modules-4.15.0-30-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-30-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 10/05/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.4
  dmi.board.name: 0HFG24
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R530
  dmi.sys.vendor: Dell Inc.

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

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

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

[Jens Peter]

apport information

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

Title:
  /proc/diskstats shows weird values

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  For one block device on one of my servers munin shows abnormally high
  latency.

  When querying /proc/diskstats manually, the device in question shows:
 8  32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 
1347171224 63 54302956 1357481880

  
  Sanity check:
  If I divide the 7th value by the 4th value I get a avg read latency of about 
10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms 
that munin reports.

  The problem:
  If I divide the 11th value by the 8th value I get an avg write latency of 
1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported 
by munin. Now this is an SD card and it is slow, but not THAT slow..

  
  To confirm unexpected values, I measured some activity:

  
  $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync;
  cat /proc/diskstats
  100+0 records in
  100+0 records out
  104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s
  
  real  0m8,132s
  user  0m0,000s
  sys   0m0,007s

  The reported time spent writing went from 1353896856 before the test to 
1356759112 after the test.
  The difference is 2862256 ms or about 2800 seconds that supposedly passed in 
just over 26 real time seconds.
  I repeated the test with count=1 and got 5780 ms IO write time reported in .7 
s realtime.

  
  #1297522 describes a similar error but I have no idea if the cause is related.


  System information:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018
  x86_64 x86_64 GNU/Linux

  /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 
cards.
  The system is a Dell R530.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug  11 22:30 seq
   crw-rw 1 root audio 116, 33 Aug  11 22:30 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=UUID=719079af-279c-46cd-9438-01086a2cb16e
  InstallationDate: Installed on 2016-03-29 (885 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  MachineType: Dell Inc. PowerEdge R530
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-30-generic N/A
   linux-backports-modules-4.15.0-30-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-30-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 10/05/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.4
  dmi.board.name: 0HFG24
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R530
  dmi.sys.vendor: Dell Inc.

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

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

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

[Jens Peter]

apport information

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

Title:
  /proc/diskstats shows weird values

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  For one block device on one of my servers munin shows abnormally high
  latency.

  When querying /proc/diskstats manually, the device in question shows:
 8  32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 
1347171224 63 54302956 1357481880

  
  Sanity check:
  If I divide the 7th value by the 4th value I get a avg read latency of about 
10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms 
that munin reports.

  The problem:
  If I divide the 11th value by the 8th value I get an avg write latency of 
1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported 
by munin. Now this is an SD card and it is slow, but not THAT slow..

  
  To confirm unexpected values, I measured some activity:

  
  $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync;
  cat /proc/diskstats
  100+0 records in
  100+0 records out
  104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s
  
  real  0m8,132s
  user  0m0,000s
  sys   0m0,007s

  The reported time spent writing went from 1353896856 before the test to 
1356759112 after the test.
  The difference is 2862256 ms or about 2800 seconds that supposedly passed in 
just over 26 real time seconds.
  I repeated the test with count=1 and got 5780 ms IO write time reported in .7 
s realtime.

  
  #1297522 describes a similar error but I have no idea if the cause is related.


  System information:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018
  x86_64 x86_64 GNU/Linux

  /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 
cards.
  The system is a Dell R530.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug  11 22:30 seq
   crw-rw 1 root audio 116, 33 Aug  11 22:30 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=UUID=719079af-279c-46cd-9438-01086a2cb16e
  InstallationDate: Installed on 2016-03-29 (885 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  MachineType: Dell Inc. PowerEdge R530
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-30-generic N/A
   linux-backports-modules-4.15.0-30-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-30-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 10/05/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.4
  dmi.board.name: 0HFG24
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R530
  dmi.sys.vendor: Dell Inc.

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

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

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

[Jens Peter]

apport information

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

Title:
  /proc/diskstats shows weird values

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  For one block device on one of my servers munin shows abnormally high
  latency.

  When querying /proc/diskstats manually, the device in question shows:
 8  32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 
1347171224 63 54302956 1357481880

  
  Sanity check:
  If I divide the 7th value by the 4th value I get a avg read latency of about 
10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms 
that munin reports.

  The problem:
  If I divide the 11th value by the 8th value I get an avg write latency of 
1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported 
by munin. Now this is an SD card and it is slow, but not THAT slow..

  
  To confirm unexpected values, I measured some activity:

  
  $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync;
  cat /proc/diskstats
  100+0 records in
  100+0 records out
  104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s
  
  real  0m8,132s
  user  0m0,000s
  sys   0m0,007s

  The reported time spent writing went from 1353896856 before the test to 
1356759112 after the test.
  The difference is 2862256 ms or about 2800 seconds that supposedly passed in 
just over 26 real time seconds.
  I repeated the test with count=1 and got 5780 ms IO write time reported in .7 
s realtime.

  
  #1297522 describes a similar error but I have no idea if the cause is related.


  System information:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018
  x86_64 x86_64 GNU/Linux

  /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 
cards.
  The system is a Dell R530.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug  11 22:30 seq
   crw-rw 1 root audio 116, 33 Aug  11 22:30 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=UUID=719079af-279c-46cd-9438-01086a2cb16e
  InstallationDate: Installed on 2016-03-29 (885 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  MachineType: Dell Inc. PowerEdge R530
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-30-generic N/A
   linux-backports-modules-4.15.0-30-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-30-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 10/05/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.4
  dmi.board.name: 0HFG24
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R530
  dmi.sys.vendor: Dell Inc.

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

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

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

[Jens Peter]

apport information

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

Title:
  /proc/diskstats shows weird values

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  For one block device on one of my servers munin shows abnormally high
  latency.

  When querying /proc/diskstats manually, the device in question shows:
 8  32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 
1347171224 63 54302956 1357481880

  
  Sanity check:
  If I divide the 7th value by the 4th value I get a avg read latency of about 
10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms 
that munin reports.

  The problem:
  If I divide the 11th value by the 8th value I get an avg write latency of 
1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported 
by munin. Now this is an SD card and it is slow, but not THAT slow..

  
  To confirm unexpected values, I measured some activity:

  
  $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync;
  cat /proc/diskstats
  100+0 records in
  100+0 records out
  104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s
  
  real  0m8,132s
  user  0m0,000s
  sys   0m0,007s

  The reported time spent writing went from 1353896856 before the test to 
1356759112 after the test.
  The difference is 2862256 ms or about 2800 seconds that supposedly passed in 
just over 26 real time seconds.
  I repeated the test with count=1 and got 5780 ms IO write time reported in .7 
s realtime.

  
  #1297522 describes a similar error but I have no idea if the cause is related.


  System information:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018
  x86_64 x86_64 GNU/Linux

  /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 
cards.
  The system is a Dell R530.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug  11 22:30 seq
   crw-rw 1 root audio 116, 33 Aug  11 22:30 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=UUID=719079af-279c-46cd-9438-01086a2cb16e
  InstallationDate: Installed on 2016-03-29 (885 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  MachineType: Dell Inc. PowerEdge R530
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-30-generic N/A
   linux-backports-modules-4.15.0-30-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-30-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 10/05/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.4
  dmi.board.name: 0HFG24
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R530
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1790181] Re: /proc/diskstats shows weird values

[Jens Peter]

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

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

Title:
  /proc/diskstats shows weird values

Status in linux package in Ubuntu:
  New

Bug description:
  For one block device on one of my servers munin shows abnormally high
  latency.

  When querying /proc/diskstats manually, the device in question shows:
 8  32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 
1347171224 63 54302956 1357481880

  
  Sanity check:
  If I divide the 7th value by the 4th value I get a avg read latency of about 
10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms 
that munin reports.

  The problem:
  If I divide the 11th value by the 8th value I get an avg write latency of 
1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported 
by munin. Now this is an SD card and it is slow, but not THAT slow..

  
  To confirm unexpected values, I measured some activity:

  
  $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync;
  cat /proc/diskstats
  100+0 records in
  100+0 records out
  104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s
  
  real  0m8,132s
  user  0m0,000s
  sys   0m0,007s

  The reported time spent writing went from 1353896856 before the test to 
1356759112 after the test.
  The difference is 2862256 ms or about 2800 seconds that supposedly passed in 
just over 26 real time seconds.
  I repeated the test with count=1 and got 5780 ms IO write time reported in .7 
s realtime.

  
  #1297522 describes a similar error but I have no idea if the cause is related.


  System information:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018
  x86_64 x86_64 GNU/Linux

  /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 
cards.
  The system is a Dell R530.

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

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

[Kernel-packages] [Bug 1773598] [NEW] package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess retur

[Jens ØStergaard]

Public bug reported:

wifi driver not installing

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Sun May 27 00:32:25 2018
ErrorMessage: installed bcmwl-kernel-source package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2018-05-26 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: bcmwl
Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 failed to 
install/upgrade: installed bcmwl-kernel-source package post-installation script 
subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 failed to
  install/upgrade: installed bcmwl-kernel-source package post-
  installation script subprocess returned error exit status 1

Status in bcmwl package in Ubuntu:
  New

Bug description:
  wifi driver not installing

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May 27 00:32:25 2018
  ErrorMessage: installed bcmwl-kernel-source package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-05-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: bcmwl
  Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 failed to 
install/upgrade: installed bcmwl-kernel-source package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13

[Dr. Jens Harbott]

Proposed kernels show the same improved behaviour as the earlier test
kernels.

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

Title:
  Servers going OOM after updating kernel from 4.10 to 4.13

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

Bug description:
  == SRU Justification ==
  We are seeing this on multiple servers after upgrading from previous 4.10 
series HWE kernels to the new 4.13 HWE series. With the new kernel, free memory 
is continously decreasing at a high rate and the servers start swapping and 
finally OOMing services within days. With the 4.10 kernel, decrease of free 
memory is slower and stabilizes after a while.

  Latest kernel tested is linux-image-4.13.0-32-generic but the issue
  also affects older kernels from that series, tested back to linux-
  image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic.

  The servers are running as OpenStack controller nodes using either
  Ocata or Pike UCA plus ceph. See attached graph for the memory
  behaviour.

  == Fix ==
  2b9478ffc550("i40e: Fix memory leak related filter programming status")
  62b4c6694dfd("i40e: Add programming descriptors to cleaned_count")

  == Regression Potential ==
  Low.  Limited to i40e and fix existing regression.

  == 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.


  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Feb  9 09:45:50 2018
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13

[Dr. Jens Harbott]

Running the -proposed kernel on two machines now, will provide the
results in a couple of days.

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

Title:
  Servers going OOM after updating kernel from 4.10 to 4.13

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

Bug description:
  == SRU Justification ==
  We are seeing this on multiple servers after upgrading from previous 4.10 
series HWE kernels to the new 4.13 HWE series. With the new kernel, free memory 
is continously decreasing at a high rate and the servers start swapping and 
finally OOMing services within days. With the 4.10 kernel, decrease of free 
memory is slower and stabilizes after a while.

  Latest kernel tested is linux-image-4.13.0-32-generic but the issue
  also affects older kernels from that series, tested back to linux-
  image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic.

  The servers are running as OpenStack controller nodes using either
  Ocata or Pike UCA plus ceph. See attached graph for the memory
  behaviour.

  == Fix ==
  2b9478ffc550("i40e: Fix memory leak related filter programming status")
  62b4c6694dfd("i40e: Add programming descriptors to cleaned_count")

  == Regression Potential ==
  Low.  Limited to i40e and fix existing regression.

  == 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.


  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Feb  9 09:45:50 2018
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13

[Dr. Jens Harbott]

@Stefan: I haven't reproduced the issue on Artful and I don't have an
environment to do so. The original issue is for the HWE kernel on Xenial
and only for that I can perform verification.

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

Title:
  Servers going OOM after updating kernel from 4.10 to 4.13

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Fix Committed

Bug description:
  == SRU Justification ==
  We are seeing this on multiple servers after upgrading from previous 4.10 
series HWE kernels to the new 4.13 HWE series. With the new kernel, free memory 
is continously decreasing at a high rate and the servers start swapping and 
finally OOMing services within days. With the 4.10 kernel, decrease of free 
memory is slower and stabilizes after a while.

  Latest kernel tested is linux-image-4.13.0-32-generic but the issue
  also affects older kernels from that series, tested back to linux-
  image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic.

  The servers are running as OpenStack controller nodes using either
  Ocata or Pike UCA plus ceph. See attached graph for the memory
  behaviour.

  == Fix ==
  2b9478ffc550("i40e: Fix memory leak related filter programming status")
  62b4c6694dfd("i40e: Add programming descriptors to cleaned_count")

  == Regression Potential ==
  Low.  Limited to i40e and fix existing regression.

  == 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.


  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Feb  9 09:45:50 2018
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13

[Dr. Jens Harbott]

The slow leak will probably be tolerable for the time being, having
those two patches added to the kernel would surely be a pretty valuable
step that I think should be done now. My target still is Xenial with the
hwe kernel, though. If you need to go via Artful to fix that, well, go
ahead.

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

Title:
  Servers going OOM after updating kernel from 4.10 to 4.13

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

Bug description:
  We are seeing this on multiple servers after upgrading from previous
  4.10 series HWE kernels to the new 4.13 HWE series. With the new
  kernel, free memory is continously decreasing at a high rate and the
  servers start swapping and finally OOMing services within days. With
  the 4.10 kernel, decrease of free memory is slower and stabilizes
  after a while.

  Latest kernel tested is linux-image-4.13.0-32-generic but the issue
  also affects older kernels from that series, tested back to linux-
  image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic.

  The servers are running as OpenStack controller nodes using either
  Ocata or Pike UCA plus ceph. See attached graph for the memory
  behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Feb  9 09:45:50 2018
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13

[Dr. Jens Harbott]

The test kernel solves the issue in the same way as my own kernel
earlier, i.e. we still seem to have a very slow running memory leak with
this kernel. I'm also seeing this slow leak when I replace the in-tree
i40e driver by an upstream version (2.3.4), so either it is unrelated or
contained in both.

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

Title:
  Servers going OOM after updating kernel from 4.10 to 4.13

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

Bug description:
  We are seeing this on multiple servers after upgrading from previous
  4.10 series HWE kernels to the new 4.13 HWE series. With the new
  kernel, free memory is continously decreasing at a high rate and the
  servers start swapping and finally OOMing services within days. With
  the 4.10 kernel, decrease of free memory is slower and stabilizes
  after a while.

  Latest kernel tested is linux-image-4.13.0-32-generic but the issue
  also affects older kernels from that series, tested back to linux-
  image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic.

  The servers are running as OpenStack controller nodes using either
  Ocata or Pike UCA plus ceph. See attached graph for the memory
  behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Feb  9 09:45:50 2018
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13

[Dr. Jens Harbott]

After running for a couple of days, it seems that we are still seeing
the slow memory leak similar to what was noticed in >= 4.14 earlier with
the patched kernel. But it won't be possible for me to bisect at that
rate.

@Joseph: Getting a patched current 4.13 still would be nice, getting
instructions for how to build such a kernel would be even nicer.

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

Title:
  Servers going OOM after updating kernel from 4.10 to 4.13

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

Bug description:
  We are seeing this on multiple servers after upgrading from previous
  4.10 series HWE kernels to the new 4.13 HWE series. With the new
  kernel, free memory is continously decreasing at a high rate and the
  servers start swapping and finally OOMing services within days. With
  the 4.10 kernel, decrease of free memory is slower and stabilizes
  after a while.

  Latest kernel tested is linux-image-4.13.0-32-generic but the issue
  also affects older kernels from that series, tested back to linux-
  image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic.

  The servers are running as OpenStack controller nodes using either
  Ocata or Pike UCA plus ceph. See attached graph for the memory
  behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Feb  9 09:45:50 2018
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13

[Dr. Jens Harbott]

O.k., confirming that this series of patches fixes the issue:

~/linux$ git log --oneline|head -3
bc6d6fd2f916 i40e: Add programming descriptors to cleaned_count
69949b3bd674 i40e: Fix memory leak related filter programming status
b32038eb34ee UBUNTU: Ubuntu-4.13.0-32.35

Can you build the same thing on top of the latest 4.13 set? Seems some
special gcc foo is needed to make the retpoline stuff working there

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

Title:
  Servers going OOM after updating kernel from 4.10 to 4.13

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

Bug description:
  We are seeing this on multiple servers after upgrading from previous
  4.10 series HWE kernels to the new 4.13 HWE series. With the new
  kernel, free memory is continously decreasing at a high rate and the
  servers start swapping and finally OOMing services within days. With
  the 4.10 kernel, decrease of free memory is slower and stabilizes
  after a while.

  Latest kernel tested is linux-image-4.13.0-32-generic but the issue
  also affects older kernels from that series, tested back to linux-
  image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic.

  The servers are running as OpenStack controller nodes using either
  Ocata or Pike UCA plus ceph. See attached graph for the memory
  behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Feb  9 09:45:50 2018
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13

[Dr. Jens Harbott]

Reading the thread further, we seem to need two patches, see 
https://www.spinics.net/lists/netdev/msg462051.html, so I'm going to add 
bc6d6fd2f916a0794ae4c44b28e14e2d172e05e0 into the build, too.
Will try that on top of b32038eb34ee42fd8056f99f88652270f6667996 (tag: 
Ubuntu-4.13.0-32.35).

I also tested the "ethtool --set-priv-flags  flow-director-atr
off" option and it seems to slow down the leak similar to >= 4.14
kernels. So either that fixes only part of the issue or we have a
different one that only got masked up to now.

Third option would be using the upstream i40e driver instead, testing
with 2.3.4 currently and that also seems to resolve the issue.

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

Title:
  Servers going OOM after updating kernel from 4.10 to 4.13

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

Bug description:
  We are seeing this on multiple servers after upgrading from previous
  4.10 series HWE kernels to the new 4.13 HWE series. With the new
  kernel, free memory is continously decreasing at a high rate and the
  servers start swapping and finally OOMing services within days. With
  the 4.10 kernel, decrease of free memory is slower and stabilizes
  after a while.

  Latest kernel tested is linux-image-4.13.0-32-generic but the issue
  also affects older kernels from that series, tested back to linux-
  image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic.

  The servers are running as OpenStack controller nodes using either
  Ocata or Pike UCA plus ceph. See attached graph for the memory
  behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Feb  9 09:45:50 2018
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13

[Dr. Jens Harbott]

A colleague found that this seems to be a known issue:

https://www.spinics.net/lists/netdev/msg458258.html

and the fix should be

https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/drivers/net/ethernet/intel/i40e/i40e_txrx.c?id=2b9478ffc550f17c6cd8c69057234e91150f5972

I will try cherry-picking this onto 4.13, not sure why it never seems to
have been pulled into the stable branch.

Also not sure why we are still seeing issues with >= 4.14, very likely a
completely different issue there, but I think we'll be fine if we get
4.13 fixed for now.

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

Title:
  Servers going OOM after updating kernel from 4.10 to 4.13

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

Bug description:
  We are seeing this on multiple servers after upgrading from previous
  4.10 series HWE kernels to the new 4.13 HWE series. With the new
  kernel, free memory is continously decreasing at a high rate and the
  servers start swapping and finally OOMing services within days. With
  the 4.10 kernel, decrease of free memory is slower and stabilizes
  after a while.

  Latest kernel tested is linux-image-4.13.0-32-generic but the issue
  also affects older kernels from that series, tested back to linux-
  image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic.

  The servers are running as OpenStack controller nodes using either
  Ocata or Pike UCA plus ceph. See attached graph for the memory
  behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Feb  9 09:45:50 2018
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13

[Dr. Jens Harbott]

Sorry for the delay, bisecting took longer than planned, but I now have
the result:

6964e53f55837b0c49ed60d36656d2e0ee4fc27b is the first bad commit
commit 6964e53f55837b0c49ed60d36656d2e0ee4fc27b
Author: Jacob Keller 
Date:   Mon Jun 12 15:38:36 2017 -0700

i40e: fix handling of HW ATR eviction

The bad news is that this patch pretty certainly isn't directly the
culprit, as it only fixes (and re-enables) features that seem to have
been messed up earlier. So not sure how to proceed now, probably need to
discuss this with upstream developers?

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

Title:
  Servers going OOM after updating kernel from 4.10 to 4.13

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

Bug description:
  We are seeing this on multiple servers after upgrading from previous
  4.10 series HWE kernels to the new 4.13 HWE series. With the new
  kernel, free memory is continously decreasing at a high rate and the
  servers start swapping and finally OOMing services within days. With
  the 4.10 kernel, decrease of free memory is slower and stabilizes
  after a while.

  Latest kernel tested is linux-image-4.13.0-32-generic but the issue
  also affects older kernels from that series, tested back to linux-
  image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic.

  The servers are running as OpenStack controller nodes using either
  Ocata or Pike UCA plus ceph. See attached graph for the memory
  behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Feb  9 09:45:50 2018
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13

[Dr. Jens Harbott]

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

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

Title:
  Servers going OOM after updating kernel from 4.10 to 4.13

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

Bug description:
  We are seeing this on multiple servers after upgrading from previous
  4.10 series HWE kernels to the new 4.13 HWE series. With the new
  kernel, free memory is continously decreasing at a high rate and the
  servers start swapping and finally OOMing services within days. With
  the 4.10 kernel, decrease of free memory is slower and stabilizes
  after a while.

  Latest kernel tested is linux-image-4.13.0-32-generic but the issue
  also affects older kernels from that series, tested back to linux-
  image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic.

  The servers are running as OpenStack controller nodes using either
  Ocata or Pike UCA plus ceph. See attached graph for the memory
  behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Feb  9 09:45:50 2018
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13

[Dr. Jens Harbott]

So here are the first results:

4.11.0-041100-generic #201705041534 - not affected
4.12.0-041200-generic #201707022031 - affected
4.13.0-041300-generic #201709031731 - affected
4.13.16-041316-generic #201711240901 - affected

Results for newer kernels are not so clear, they do not fail as fast as
previous ones, but they do still fill up memory and - later - swap
slowly. The rate is so slow however, that it will probably take weeks to
come to some definitive results here.

Thus my next step, unless there is a better proposal, will be starting
to bisect from 4.11 to 4.12, git expects 13 steps for that.

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

Title:
  Servers going OOM after updating kernel from 4.10 to 4.13

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

Bug description:
  We are seeing this on multiple servers after upgrading from previous
  4.10 series HWE kernels to the new 4.13 HWE series. With the new
  kernel, free memory is continously decreasing at a high rate and the
  servers start swapping and finally OOMing services within days. With
  the 4.10 kernel, decrease of free memory is slower and stabilizes
  after a while.

  Latest kernel tested is linux-image-4.13.0-32-generic but the issue
  also affects older kernels from that series, tested back to linux-
  image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic.

  The servers are running as OpenStack controller nodes using either
  Ocata or Pike UCA plus ceph. See attached graph for the memory
  behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Feb  9 09:45:50 2018
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13

[Dr. Jens Harbott]

Ok, nevermind the aufs issue, I got that resolved. Should have some
results with mainline kernels in a couple of days.

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

Title:
  Servers going OOM after updating kernel from 4.10 to 4.13

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

Bug description:
  We are seeing this on multiple servers after upgrading from previous
  4.10 series HWE kernels to the new 4.13 HWE series. With the new
  kernel, free memory is continously decreasing at a high rate and the
  servers start swapping and finally OOMing services within days. With
  the 4.10 kernel, decrease of free memory is slower and stabilizes
  after a while.

  Latest kernel tested is linux-image-4.13.0-32-generic but the issue
  also affects older kernels from that series, tested back to linux-
  image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic.

  The servers are running as OpenStack controller nodes using either
  Ocata or Pike UCA plus ceph. See attached graph for the memory
  behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Feb  9 09:45:50 2018
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13

[Dr. Jens Harbott]

@Joseph: I did test 4.15.2, but some things are failing, in particular
docker because of lacking AUFS support, so I need to build a kernel
myself I guess, which will take a bit.

Also note that I'm seeing this on Xenial machines, didn't test with
Artful. We used to run them with the 4.10 HWE kernels because they offer
improved performance in some areas compared to the stock 4.4. kernel.
Started seeing these issue after HWE switched to 4.13 a couple of 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/1748408

Title:
  Servers going OOM after updating kernel from 4.10 to 4.13

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

Bug description:
  We are seeing this on multiple servers after upgrading from previous
  4.10 series HWE kernels to the new 4.13 HWE series. With the new
  kernel, free memory is continously decreasing at a high rate and the
  servers start swapping and finally OOMing services within days. With
  the 4.10 kernel, decrease of free memory is slower and stabilizes
  after a while.

  Latest kernel tested is linux-image-4.13.0-32-generic but the issue
  also affects older kernels from that series, tested back to linux-
  image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic.

  The servers are running as OpenStack controller nodes using either
  Ocata or Pike UCA plus ceph. See attached graph for the memory
  behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Feb  9 09:45:50 2018
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Jens Elkner]

Since xenial we have this very annoying behavior (unregister_netdevice:
waiting for lo to become free. Usage count = 1) as well, which in turn
makes a container reboot taking several minutes instead of seconds e.g.
on vivid (lxc-ls -f also hangs for that time). E.g.:

 [ +10.244888] unregister_netdevice: waiting for lo to become free. Usage count 
= 1
[Oct 2 17:16] INFO: task lxc-autostart:5321 blocked for more than 120 seconds.
[  +0.007147]   Tainted: P   OE   4.4.0-96-generic #119-Ubuntu
[  +0.006796] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  +0.007913] lxc-autostart   D 883fb99fbcb8 0  5321  1 0x
[  +0.07]  883fb99fbcb8  883ff2a3aa00 
881fed2fe200
[  +0.04]  883fb99fc000 81ef79a4 881fed2fe200 

[  +0.04]  81ef79a8 883fb99fbcd0 8183f165 
81ef79a0
[  +0.04] Call Trace:
[  +0.14]  [] schedule+0x35/0x80
[  +0.05]  [] schedule_preempt_disabled+0xe/0x10
[  +0.16]  [] __mutex_lock_slowpath+0xb9/0x130
[  +0.14]  [] mutex_lock+0x1f/0x30
[  +0.09]  [] copy_net_ns+0x6e/0x120
[  +0.09]  [] create_new_namespaces+0x11b/0x1d0
[  +0.03]  [] copy_namespaces+0x6d/0xa0
[  +0.07]  [] copy_process+0x8e2/0x1b30
[  +0.11]  [] _do_fork+0x80/0x360
[  +0.15]  [] ? exit_to_usermode_loop+0xa6/0xd0
[  +0.04]  [] SyS_clone+0x19/0x20
[  +0.09]  [] entry_SYSCALL_64_fastpath+0x16/0x71
[  +4.882232] 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/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]

  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 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89

[Dr. Jens Harbott]

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

Title:
  Creating conntrack entry failure with kernel 4.4.0-89

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Released

Bug description:
  The functional job failure rate is at 100%. Every time some test gets
  stuck and job is killed after timeout.

  logstash query:
  
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
  %22gate-neutron-dsvm-functional-ubuntu-
  
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22

  2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
  dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
  15261 Killed  timeout -s 9 ${REMAINING_TIME}m bash -c
  "source $WORKSPACE/devstack-gate/functions.sh && $cmd"

  There are a few test executors left, which means there are more tests
  stuck:

  stack15468 15445 15468  0.0  0.0   328   796 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpDTLPoX
  stack15469 15468 15469  1.5  1.8 139332 150008 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
  stack15470 15445 15470  0.0  0.0   328   700 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpICNqRQ
  stack15471 15470 15471  1.6  2.0 152056 164812 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
  stack15474 15445 15474  0.0  0.0   328   792 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpe646Tl
  stack15475 15474 15475  1.6  1.9 149972 162516 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
  stack15476 15445 15476  0.0  0.0   328   804 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpv2ovhz
  stack15477 15476 15477  1.2  1.8 136760 149160 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
  stack15478 15445 15478  0.0  0.0   328   712 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpDqXE8S
  stack15479 15478 15479  1.5  1.9 148784 161004 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
  stack15480 15445 15480  0.0  0.0   328   804 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpTmmShS
  stack15482 15480 15482  1.6  1.9 148856 161516 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS

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

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

[Kernel-packages] [Bug 1694090] Re: ZoL: wrong import order prevents boot

[Jens Elkner]

It might be also a result of the bogus mount.zfs, which requires POSIX
incorrect arguments but honors POSIXLY_CORRECT env var!

Had a similar zfs mount order problem with a rpool/local/home/{A,B,C}
tree (was created using -p option) ...

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

Title:
  ZoL: wrong import order prevents boot

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  I've the following zfs:

  # zfs list -r rpool/VARSHARE
  NAME  USED  AVAIL  REFER  MOUNTPOINT
  rpool/VARSHARE   114K   165G30K  /var/share
  rpool/VARSHARE/lxc84K   165G19K  /var/share/lxc
  rpool/VARSHARE/lxc/xenial 65K   165G19K  
/var/share/lxc/xenial
  rpool/VARSHARE/lxc/xenial/pkg 19K   165G19K  
/var/share/lxc/xenial/pkg
  rpool/VARSHARE/lxc/xenial/rootfs-amd6427K   165G27K  
/var/share/lxc/xenial/rootfs-amd64

  On boot, we see

   Starting Mount ZFS filesystems...
  [FAILED] Failed to start Mount ZFS filesystems.
  See 'systemctl status zfs-mount.service' for details.
  Welcome to emergPress Enter for maintenance
  (or press Control-D to continue): 

  
  # df -h /var/share
  rpool/VARSHARE/lxc165G 0  165G   0% /var/share/lxc
  rpool/VARSHARE/lxc/xenial 165G 0  165G   0% 
/var/share/lxc/xenial
  rpool/VARSHARE/lxc/xenial/pkg 165G 0  165G   0% 
/var/share/lxc/xenial/pkg
  rpool/VARSHARE/lxc/xenial/rootfs-amd64165G 0  165G   0% 
/var/share/lxc/xenial/rootfs-amd64

  
  Obviously rpool/VARSHARE - the parent of rpool/VARSHARE/lxc - was not 
mounted, even so canmount property is for all set to on, rpool/VARSHARE's 
mountpoint to /var/share and rpool/VARSHARE/lxc children inherit their 
mountpoint.

  
  # systemctl status zfs-mount.service
  ● zfs-mount.service - Mount ZFS filesystems
 Loaded: loaded (/lib/systemd/system/zfs-mount.service; static; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Sun 2017-05-28 04:51:46 CEST; 
13min ago
Process: 6935 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE)
   Main PID: 6935 (code=exited, status=1/FAILURE)

  May 28 04:51:45 ares systemd[1]: Starting Mount ZFS filesystems...
  May 28 04:51:45 ares zfs[6935]: cannot mount '/var/share': directory is not 
empty
  May 28 04:51:46 ares systemd[1]: zfs-mount.service: Main process exited, 
code=exited, status=1/FAILURE
  May 28 04:51:46 ares systemd[1]: Failed to start Mount ZFS filesystems.
  May 28 04:51:46 ares systemd[1]: zfs-mount.service: Unit entered failed state.
  May 28 04:51:46 ares systemd[1]: zfs-mount.service: Failed with result 
'exit-code'.

  So 'zfs mount ...' seems to be severely buggy.

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

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

[Kernel-packages] [Bug 1694090] Re: ZoL: wrong import order prevents boot

[Jens Elkner]

Please read carefully before answering: As already said (and the given
output clearly shows the problem beside being mentioned in the subject):
zfs screwed up the mount order and mounted rpool/VARSHARE/lxc _before_
rpool/VARSHARE. And when /var/share/lxc gets mounted, obviously
/var/share is not empty and thus zfs,mount shot itself into the feet ...

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

Title:
  ZoL: wrong import order prevents boot

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  I've the following zfs:

  # zfs list -r rpool/VARSHARE
  NAME  USED  AVAIL  REFER  MOUNTPOINT
  rpool/VARSHARE   114K   165G30K  /var/share
  rpool/VARSHARE/lxc84K   165G19K  /var/share/lxc
  rpool/VARSHARE/lxc/xenial 65K   165G19K  
/var/share/lxc/xenial
  rpool/VARSHARE/lxc/xenial/pkg 19K   165G19K  
/var/share/lxc/xenial/pkg
  rpool/VARSHARE/lxc/xenial/rootfs-amd6427K   165G27K  
/var/share/lxc/xenial/rootfs-amd64

  On boot, we see

   Starting Mount ZFS filesystems...
  [FAILED] Failed to start Mount ZFS filesystems.
  See 'systemctl status zfs-mount.service' for details.
  Welcome to emergPress Enter for maintenance
  (or press Control-D to continue): 

  
  # df -h /var/share
  rpool/VARSHARE/lxc165G 0  165G   0% /var/share/lxc
  rpool/VARSHARE/lxc/xenial 165G 0  165G   0% 
/var/share/lxc/xenial
  rpool/VARSHARE/lxc/xenial/pkg 165G 0  165G   0% 
/var/share/lxc/xenial/pkg
  rpool/VARSHARE/lxc/xenial/rootfs-amd64165G 0  165G   0% 
/var/share/lxc/xenial/rootfs-amd64

  
  Obviously rpool/VARSHARE - the parent of rpool/VARSHARE/lxc - was not 
mounted, even so canmount property is for all set to on, rpool/VARSHARE's 
mountpoint to /var/share and rpool/VARSHARE/lxc children inherit their 
mountpoint.

  
  # systemctl status zfs-mount.service
  ● zfs-mount.service - Mount ZFS filesystems
 Loaded: loaded (/lib/systemd/system/zfs-mount.service; static; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Sun 2017-05-28 04:51:46 CEST; 
13min ago
Process: 6935 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE)
   Main PID: 6935 (code=exited, status=1/FAILURE)

  May 28 04:51:45 ares systemd[1]: Starting Mount ZFS filesystems...
  May 28 04:51:45 ares zfs[6935]: cannot mount '/var/share': directory is not 
empty
  May 28 04:51:46 ares systemd[1]: zfs-mount.service: Main process exited, 
code=exited, status=1/FAILURE
  May 28 04:51:46 ares systemd[1]: Failed to start Mount ZFS filesystems.
  May 28 04:51:46 ares systemd[1]: zfs-mount.service: Unit entered failed state.
  May 28 04:51:46 ares systemd[1]: zfs-mount.service: Failed with result 
'exit-code'.

  So 'zfs mount ...' seems to be severely buggy.

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

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

[Kernel-packages] [Bug 1694090] [NEW] ZoL: wrong import order prevents boot

[Jens Elkner]

Public bug reported:

I've the following zfs:

# zfs list -r rpool/VARSHARE
NAME  USED  AVAIL  REFER  MOUNTPOINT
rpool/VARSHARE   114K   165G30K  /var/share
rpool/VARSHARE/lxc84K   165G19K  /var/share/lxc
rpool/VARSHARE/lxc/xenial 65K   165G19K  
/var/share/lxc/xenial
rpool/VARSHARE/lxc/xenial/pkg 19K   165G19K  
/var/share/lxc/xenial/pkg
rpool/VARSHARE/lxc/xenial/rootfs-amd6427K   165G27K  
/var/share/lxc/xenial/rootfs-amd64

On boot, we see

 Starting Mount ZFS filesystems...
[FAILED] Failed to start Mount ZFS filesystems.
See 'systemctl status zfs-mount.service' for details.
Welcome to emergPress Enter for maintenance
(or press Control-D to continue): 


# df -h /var/share
rpool/VARSHARE/lxc165G 0  165G   0% /var/share/lxc
rpool/VARSHARE/lxc/xenial 165G 0  165G   0% 
/var/share/lxc/xenial
rpool/VARSHARE/lxc/xenial/pkg 165G 0  165G   0% 
/var/share/lxc/xenial/pkg
rpool/VARSHARE/lxc/xenial/rootfs-amd64165G 0  165G   0% 
/var/share/lxc/xenial/rootfs-amd64


Obviously rpool/VARSHARE - the parent of rpool/VARSHARE/lxc - was not mounted, 
even so canmount property is for all set to on, rpool/VARSHARE's mountpoint to 
/var/share and rpool/VARSHARE/lxc children inherit their mountpoint.


# systemctl status zfs-mount.service
● zfs-mount.service - Mount ZFS filesystems
   Loaded: loaded (/lib/systemd/system/zfs-mount.service; static; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Sun 2017-05-28 04:51:46 CEST; 13min 
ago
  Process: 6935 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE)
 Main PID: 6935 (code=exited, status=1/FAILURE)

May 28 04:51:45 ares systemd[1]: Starting Mount ZFS filesystems...
May 28 04:51:45 ares zfs[6935]: cannot mount '/var/share': directory is not 
empty
May 28 04:51:46 ares systemd[1]: zfs-mount.service: Main process exited, 
code=exited, status=1/FAILURE
May 28 04:51:46 ares systemd[1]: Failed to start Mount ZFS filesystems.
May 28 04:51:46 ares systemd[1]: zfs-mount.service: Unit entered failed state.
May 28 04:51:46 ares systemd[1]: zfs-mount.service: Failed with result 
'exit-code'.

So 'zfs mount ...' seems to be severely buggy.

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

Title:
  ZoL: wrong import order prevents boot

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  I've the following zfs:

  # zfs list -r rpool/VARSHARE
  NAME  USED  AVAIL  REFER  MOUNTPOINT
  rpool/VARSHARE   114K   165G30K  /var/share
  rpool/VARSHARE/lxc84K   165G19K  /var/share/lxc
  rpool/VARSHARE/lxc/xenial 65K   165G19K  
/var/share/lxc/xenial
  rpool/VARSHARE/lxc/xenial/pkg 19K   165G19K  
/var/share/lxc/xenial/pkg
  rpool/VARSHARE/lxc/xenial/rootfs-amd6427K   165G27K  
/var/share/lxc/xenial/rootfs-amd64

  On boot, we see

   Starting Mount ZFS filesystems...
  [FAILED] Failed to start Mount ZFS filesystems.
  See 'systemctl status zfs-mount.service' for details.
  Welcome to emergPress Enter for maintenance
  (or press Control-D to continue): 

  
  # df -h /var/share
  rpool/VARSHARE/lxc165G 0  165G   0% /var/share/lxc
  rpool/VARSHARE/lxc/xenial 165G 0  165G   0% 
/var/share/lxc/xenial
  rpool/VARSHARE/lxc/xenial/pkg 165G 0  165G   0% 
/var/share/lxc/xenial/pkg
  rpool/VARSHARE/lxc/xenial/rootfs-amd64165G 0  165G   0% 
/var/share/lxc/xenial/rootfs-amd64

  
  Obviously rpool/VARSHARE - the parent of rpool/VARSHARE/lxc - was not 
mounted, even so canmount property is for all set to on, rpool/VARSHARE's 
mountpoint to /var/share and rpool/VARSHARE/lxc children inherit their 
mountpoint.

  
  # systemctl status zfs-mount.service
  ● zfs-mount.service - Mount ZFS filesystems
 Loaded: loaded (/lib/systemd/system/zfs-mount.service; static; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Sun 2017-05-28 04:51:46 CEST; 
13min ago
Process: 6935 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE)
   Main PID: 6935 (code=exited, status=1/FAILURE)

  May 28 04:51:45 ares systemd[1]: Starting Mount ZFS filesystems...
  May 28 04:51:45 ares zfs[6935]: cannot mount '/var/share': directory is not 
empty
  May 28 04:51:46 ares systemd[1]: zfs-mount.service: Main process exited, 
code=exited, status=1/FAILURE
  May 28 04:51:46 ares systemd[1]: Failed to start Mount ZFS filesystems.
  May 28 04:51:46 ares systemd[1]: zfs-mount.service: Unit entered failed state.
  May 28 04:51:46 ares systemd[1]: zfs-mount.service: 

[Kernel-packages] [Bug 1687664] Re: grub-probe zfs bug: failed to get canonical path

[Jens Elkner]

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

No ETAs, when the backport is available for the LTS release?

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

Title:
  grub-probe zfs bug: failed to get canonical path

Status in grub2 package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  grub-probe /

  fails with grub-probe: error: failed to get canonical path of
  `/dev/HDD0p2'. This is simply because grub makes the wrong assumption,
  that "zpool status $pool" lists the vdevs in use only with the '/dev/'
  prefix stripped off. It probably assumes something like /dev/sda etc.,
  which is discouraged to use.

  Instead, grub should use "zpool status -P $pool" to get the full
  device path. This would probably result into a symlink, e.g. /dev
  /disk-by-id/$bla . If this is not sufficient, grub should use
  realpath() to get the final blockdev entry like /dev/sda1 .

  The current setup I use is:

  433 0 drwxr-xr-x 4 root root 80 Apr 28 20:22 /dev/chassis/SYS
  434 0 drwxr-xr-x 2 root root 200 Apr 28 23:06 /dev/chassis/SYS/HDD0
  435 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0 -> 
../../../sda
  417 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0p1 -> 
../../../sda1
  442 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0p2 -> 
../../../sda2
  423 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0p9 -> 
../../../sda9
  436 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD0/disk -> 
../../../sda
  418 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/p1 -> 
../../../sda1
  443 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/p2 -> 
../../../sda2
  424 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/p9 -> 
../../../sda9
  437 0 drwxr-xr-x 2 root root 80 Apr 28 20:22 /dev/chassis/SYS/HDD1
  438 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD1/HDD1 -> 
../../../sdb
  439 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD1/disk -> 
../../../sdb

  with 'zpool create ... rpool /dev/chassis/SYS/HDD0/HDD0p2'

  PS: The full version is 2.02~beta2-36ubuntu3.9 and ZoL
  0.6.5.6-0ubuntu15 (Ubuntu xenial 16.04).

  For simulation one may setup a VirtualBox VM, with Storage == Controller SAS 
(Type: LsiLogic SAS, Port Count: 8), and e.g. one VDI attached to it (/dev/sda) 
and e.g. netboot an install image. When it comes to the 'partitioning disks' 
dialog, start a shell and fetch/install ksh93 (i.e. ksh-udeb).
  Than the script http://iks.cs.ovgu.de/~elkner/tmp/ubuntu/bayLinks.sh can be 
used, to create the required dev symlinks (e.g. bayLinks.sh -mru). For 
convenience http://iks.cs.ovgu.de/~elkner/tmp/ubuntu/ubuntu-part.sh can be used 
to create the script for [re-]partitioning the drive[s] and setup zfs related 
stuff (whereby the 'zpool create' and consecutive stuff will fail because of 
the bug). E.g. /tmp/ubuntu-part.sh /dev/chassis/SYS/HDD0/HDD0 .

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

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

[Kernel-packages] [Bug 1687664] Re: grub-probe zfs bug: failed to get canonical path

[Jens Elkner]

Wondering, whether there is an official repository, where one may look
into the source of the shipped version of the package. I found
https://launchpad.net/ubuntu/+source/grub2/2.02~beta2-36ubuntu3.9, but
even the grub2_2.02~beta2.orig.tar.xz is != to what is tagged as
grub-2.02-beta2 in the official repo
(https://git.savannah.gnu.org/git/grub.git) ... g ...

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

Title:
  grub-probe zfs bug: failed to get canonical path

Status in grub2 package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  grub-probe /

  fails with grub-probe: error: failed to get canonical path of
  `/dev/HDD0p2'. This is simply because grub makes the wrong assumption,
  that "zpool status $pool" lists the vdevs in use only with the '/dev/'
  prefix stripped off. It probably assumes something like /dev/sda etc.,
  which is discouraged to use.

  Instead, grub should use "zpool status -P $pool" to get the full
  device path. This would probably result into a symlink, e.g. /dev
  /disk-by-id/$bla . If this is not sufficient, grub should use
  realpath() to get the final blockdev entry like /dev/sda1 .

  The current setup I use is:

  433 0 drwxr-xr-x 4 root root 80 Apr 28 20:22 /dev/chassis/SYS
  434 0 drwxr-xr-x 2 root root 200 Apr 28 23:06 /dev/chassis/SYS/HDD0
  435 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0 -> 
../../../sda
  417 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0p1 -> 
../../../sda1
  442 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0p2 -> 
../../../sda2
  423 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0p9 -> 
../../../sda9
  436 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD0/disk -> 
../../../sda
  418 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/p1 -> 
../../../sda1
  443 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/p2 -> 
../../../sda2
  424 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/p9 -> 
../../../sda9
  437 0 drwxr-xr-x 2 root root 80 Apr 28 20:22 /dev/chassis/SYS/HDD1
  438 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD1/HDD1 -> 
../../../sdb
  439 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD1/disk -> 
../../../sdb

  with 'zpool create ... rpool /dev/chassis/SYS/HDD0/HDD0p2'

  PS: The full version is 2.02~beta2-36ubuntu3.9 and ZoL
  0.6.5.6-0ubuntu15 (Ubuntu xenial 16.04).

  For simulation one may setup a VirtualBox VM, with Storage == Controller SAS 
(Type: LsiLogic SAS, Port Count: 8), and e.g. one VDI attached to it (/dev/sda) 
and e.g. netboot an install image. When it comes to the 'partitioning disks' 
dialog, start a shell and fetch/install ksh93 (i.e. ksh-udeb).
  Than the script http://iks.cs.ovgu.de/~elkner/tmp/ubuntu/bayLinks.sh can be 
used, to create the required dev symlinks (e.g. bayLinks.sh -mru). For 
convenience http://iks.cs.ovgu.de/~elkner/tmp/ubuntu/ubuntu-part.sh can be used 
to create the script for [re-]partitioning the drive[s] and setup zfs related 
stuff (whereby the 'zpool create' and consecutive stuff will fail because of 
the bug). E.g. /tmp/ubuntu-part.sh /dev/chassis/SYS/HDD0/HDD0 .

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

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

[Kernel-packages] [Bug 1687664] Re: grub-probe zfs bug: failed to get canonical path

[Jens Elkner]

BUG or not? At least I get mixed feelings, when I see, that the log
device gets passed to grub-probe! E.g.:

+ zpool status rpool
  pool: rpool
 state: ONLINE
  scan: resilvered 547M in 0h0m with 0 errors on Thu May 18 03:49:08 2017
config:

NAME STATE READ WRITE CKSUM
rpoolONLINE   0 0 0
  mirror-0   ONLINE   0 0 0
HDD0p2   ONLINE   0 0 0
HDD12p2  ONLINE   0 0 0
logs
  HDD2p3 ONLINE   0 0 0
spares
  HDD1p2 AVAIL   

errors: No known data errors


+ zpool status -P rpool
  pool: rpool
 state: ONLINE
  scan: resilvered 547M in 0h0m with 0 errors on Thu May 18 03:49:08 2017
config:

NAME  STATE READ WRITE CKSUM
rpool ONLINE   0 0 0
  mirror-0ONLINE   0 0 0
/dev/chassis/SYS/HDD0p2   ONLINE   0 0 0
/dev/chassis/SYS/HDD12p2  ONLINE   0 0 0
logs
  /dev/chassis/SYS/HDD2p3 ONLINE   0 0 0
spares
  /dev/chassis/SYS/HDD1p2 AVAIL   

errors: No known data errors


and than on update-grub I see:

...
prepare_grub_to_access_device /dev/sda2 /dev/sdf2 /dev/sdb3
+ old_ifs=  

+ IFS=

+ /usr/sbin/grub-probe --device /dev/sda2 /dev/sdf2 /dev/sdb3 --target=partmap
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda2.  Check 
your device.map.
...

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

Title:
  grub-probe zfs bug: failed to get canonical path

Status in grub2 package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  grub-probe /

  fails with grub-probe: error: failed to get canonical path of
  `/dev/HDD0p2'. This is simply because grub makes the wrong assumption,
  that "zpool status $pool" lists the vdevs in use only with the '/dev/'
  prefix stripped off. It probably assumes something like /dev/sda etc.,
  which is discouraged to use.

  Instead, grub should use "zpool status -P $pool" to get the full
  device path. This would probably result into a symlink, e.g. /dev
  /disk-by-id/$bla . If this is not sufficient, grub should use
  realpath() to get the final blockdev entry like /dev/sda1 .

  The current setup I use is:

  433 0 drwxr-xr-x 4 root root 80 Apr 28 20:22 /dev/chassis/SYS
  434 0 drwxr-xr-x 2 root root 200 Apr 28 23:06 /dev/chassis/SYS/HDD0
  435 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0 -> 
../../../sda
  417 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0p1 -> 
../../../sda1
  442 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0p2 -> 
../../../sda2
  423 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0p9 -> 
../../../sda9
  436 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD0/disk -> 
../../../sda
  418 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/p1 -> 
../../../sda1
  443 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/p2 -> 
../../../sda2
  424 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/p9 -> 
../../../sda9
  437 0 drwxr-xr-x 2 root root 80 Apr 28 20:22 /dev/chassis/SYS/HDD1
  438 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD1/HDD1 -> 
../../../sdb
  439 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD1/disk -> 
../../../sdb

  with 'zpool create ... rpool /dev/chassis/SYS/HDD0/HDD0p2'

  PS: The full version is 2.02~beta2-36ubuntu3.9 and ZoL
  0.6.5.6-0ubuntu15 (Ubuntu xenial 16.04).

  For simulation one may setup a VirtualBox VM, with Storage == Controller SAS 
(Type: LsiLogic SAS, Port Count: 8), and e.g. one VDI attached to it (/dev/sda) 
and e.g. netboot an install image. When it comes to the 'partitioning disks' 
dialog, start a shell and fetch/install ksh93 (i.e. ksh-udeb).
  Than the script http://iks.cs.ovgu.de/~elkner/tmp/ubuntu/bayLinks.sh can be 
used, to create the required dev symlinks (e.g. bayLinks.sh -mru). For 
convenience http://iks.cs.ovgu.de/~elkner/tmp/ubuntu/ubuntu-part.sh can be used 
to create the script for [re-]partitioning the drive[s] and setup zfs related 
stuff (whereby the 'zpool create' and consecutive stuff will fail because of 
the bug). E.g. /tmp/ubuntu-part.sh /dev/chassis/SYS/HDD0/HDD0 .

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

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

[Kernel-packages] [Bug 1687664] Re: grub-probe zfs bug: failed to get canonical path

[Jens Elkner]

BTW: Just encountered, that netinstall fails, when it tries to install
grub, because /sys seems not to be mounted to /target/sys:

# zpool status 
The ZFS modules are not loaded.
Try running '/sbin/modprobe zfs' as root to load them.

After a mount --rbind /sys /target/sys :
# zpool status 
  pool: rpool
 state: ONLINE
  scan: none requested
config:

NAMESTATE READ WRITE CKSUM
rpool   ONLINE   0 0 0
  HDD0p2ONLINE   0 0 0

errors: No known data errors

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

Title:
  grub-probe zfs bug: failed to get canonical path

Status in grub2 package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  grub-probe /

  fails with grub-probe: error: failed to get canonical path of
  `/dev/HDD0p2'. This is simply because grub makes the wrong assumption,
  that "zpool status $pool" lists the vdevs in use only with the '/dev/'
  prefix stripped off. It probably assumes something like /dev/sda etc.,
  which is discouraged to use.

  Instead, grub should use "zpool status -P $pool" to get the full
  device path. This would probably result into a symlink, e.g. /dev
  /disk-by-id/$bla . If this is not sufficient, grub should use
  realpath() to get the final blockdev entry like /dev/sda1 .

  The current setup I use is:

  433 0 drwxr-xr-x 4 root root 80 Apr 28 20:22 /dev/chassis/SYS
  434 0 drwxr-xr-x 2 root root 200 Apr 28 23:06 /dev/chassis/SYS/HDD0
  435 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0 -> 
../../../sda
  417 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0p1 -> 
../../../sda1
  442 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0p2 -> 
../../../sda2
  423 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0p9 -> 
../../../sda9
  436 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD0/disk -> 
../../../sda
  418 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/p1 -> 
../../../sda1
  443 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/p2 -> 
../../../sda2
  424 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/p9 -> 
../../../sda9
  437 0 drwxr-xr-x 2 root root 80 Apr 28 20:22 /dev/chassis/SYS/HDD1
  438 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD1/HDD1 -> 
../../../sdb
  439 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD1/disk -> 
../../../sdb

  with 'zpool create ... rpool /dev/chassis/SYS/HDD0/HDD0p2'

  PS: The full version is 2.02~beta2-36ubuntu3.9 and ZoL
  0.6.5.6-0ubuntu15 (Ubuntu xenial 16.04).

  For simulation one may setup a VirtualBox VM, with Storage == Controller SAS 
(Type: LsiLogic SAS, Port Count: 8), and e.g. one VDI attached to it (/dev/sda) 
and e.g. netboot an install image. When it comes to the 'partitioning disks' 
dialog, start a shell and fetch/install ksh93 (i.e. ksh-udeb).
  Than the script http://iks.cs.ovgu.de/~elkner/tmp/ubuntu/bayLinks.sh can be 
used, to create the required dev symlinks (e.g. bayLinks.sh -mru). For 
convenience http://iks.cs.ovgu.de/~elkner/tmp/ubuntu/ubuntu-part.sh can be used 
to create the script for [re-]partitioning the drive[s] and setup zfs related 
stuff (whereby the 'zpool create' and consecutive stuff will fail because of 
the bug). E.g. /tmp/ubuntu-part.sh /dev/chassis/SYS/HDD0/HDD0 .

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

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

[Kernel-packages] [Bug 1685528] Re: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail

[Jens Elkner]

It should not restrict import to hardcoded /dev and /dev/disk/by-id -
see https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1688890

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

Title:
  ZFS initramfs mounts dataset explicitly set not to be mounted, causing
  boot process to fail

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Per https://github.com/zfsonlinux/pkg-zfs/issues/221: the initramfs
  zfs script might overrule canmount and mountpoint options for a
  dataset, causing other mount operations and with them the boot process
  to fail.

  Experienced this with Ubuntu Zesty. Xenial seems to ship with a
  different zfs script for the initrd.

  Work around when it happens: unmount the dataset that should not be
  mounted, and exit the initramfs rescue prompt to resume booting.

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

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

[Kernel-packages] [Bug 1688890] Re: initramfs-zfs should support misc /dev dirs

[Jens Elkner]

** Patch added: "honor misc /dev dirs"
   
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1688890/+attachment/4872753/+files/initramfs-zfs.patch

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

Title:
  initramfs-zfs should support misc /dev dirs

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Right now 'zfs-initramfs', i.e. /usr/share/initramfs-tools/scripts/zfs
  does not support any other directory than /dev for "zpool import ...".
  Therefore even if a pool gets created from a different directory like
  /dev, say /dev/disk/by-id or /dev/chassis/SYS on next reboot /dev will
  be used and thus zpool status will show the /dev/sd* etc. on
  successful import. Beside that now a user does not see the original
  names used in "zpool create ..." the unstable names like "/dev/sd*"
  are shown, which is explicitly NOT recommended.

  The following patch introduces the "pseudo" kernel param named "zdirs"
  - a comma separated list of dev dirs to scan on import - which gets
  used by /usr/share/initramfs-tools/scripts/zfs to honor it.

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

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

[Kernel-packages] [Bug 1688890] [NEW] initramfs-zfs should support misc /dev dirs

[Jens Elkner]

Public bug reported:

Right now 'zfs-initramfs', i.e. /usr/share/initramfs-tools/scripts/zfs
does not support any other directory than /dev for "zpool import ...".
Therefore even if a pool gets created from a different directory like
/dev, say /dev/disk/by-id or /dev/chassis/SYS on next reboot /dev will
be used and thus zpool status will show the /dev/sd* etc. on successful
import. Beside that now a user does not see the original names used in
"zpool create ..." the unstable names like "/dev/sd*" are shown, which
is explicitly NOT recommended.

The following patch introduces the "pseudo" kernel param named "zdirs" -
a comma separated list of dev dirs to scan on import - which gets used
by /usr/share/initramfs-tools/scripts/zfs to honor it.

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

** Package changed: grub2 (Ubuntu) => zfs-linux (Ubuntu)

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

Title:
  initramfs-zfs should support misc /dev dirs

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Right now 'zfs-initramfs', i.e. /usr/share/initramfs-tools/scripts/zfs
  does not support any other directory than /dev for "zpool import ...".
  Therefore even if a pool gets created from a different directory like
  /dev, say /dev/disk/by-id or /dev/chassis/SYS on next reboot /dev will
  be used and thus zpool status will show the /dev/sd* etc. on
  successful import. Beside that now a user does not see the original
  names used in "zpool create ..." the unstable names like "/dev/sd*"
  are shown, which is explicitly NOT recommended.

  The following patch introduces the "pseudo" kernel param named "zdirs"
  - a comma separated list of dev dirs to scan on import - which gets
  used by /usr/share/initramfs-tools/scripts/zfs to honor it.

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

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

[Kernel-packages] [Bug 1687791] Re: Install of kdump-tools fails

[Jens Elkner]

Seems, that this package gets included via preseed:

tasksel tasksel/first multiselect minimal
d-i pkgsel/include string grub2 linux-crashdump openssh-server tcsh ksh gawk 
vim sysstat lxc debootstrap libcap-ng-utils acpid at bc ethtool libxslt1.1 
lxc-templates patch uidmap xz-utils acl iptables ulogd2 ntp nfs-common autofs 
ldap-utils gdisk zfsutils-linux zfs-initramfs dmidecode

Anyway, IMHO it doesn't matter what kind of install - it should not fail
to install.

BTW: The image used is
http://archive.ubuntu.com/ubuntu/dists/xenial/main/installer-
amd64/current/images/netboot/netboot.tar.gz

I've already added the 'set -x' as shown above. The 1st line of the
output shows, how it has been done (because there is no vi[m] available
in the install environment), and the remaining lines show the output
after resuming the install (I guess, the installer redirects everything
to /var/log/syslog, otherwise I wonder, where else the output gets
captured.). Anyway, I can see two lines prefixed with a '+', so I guess,
that 'set -x' does what it should, but there is simply not more than
this.

IIUC, it does not hurt, if it fails - can be done later/on demand as
well. So why not append a '|| true' or remove it completely from
postinstall ?

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

Title:
  Install of kdump-tools fails

Status in makedumpfile package in Ubuntu:
  New

Bug description:
  When installing Ubuntu xenial via netimage, installation fails because
  of an error, when configuring the kdump-tools. /var/log/syslog says:

  ...

  May  2 22:15:17 in-target: Setting up grub2 (2.02~beta2-36ubuntu3.9) ...^M
  May  2 22:15:17 in-target: Setting up lxc-common (2.0.7-0ubuntu1~16.04.2) 
...^M
  May  2 22:15:17 in-target: Running in chroot, ignoring request.^M
  May  2 22:15:17 in-target: invoke-rc.d: policy-rc.d denied execution of 
reload.^M
  May  2 22:15:17 in-target: Setting up grub-gfxpayload-lists (0.7) ...^M
  May  2 22:15:17 in-target: Processing triggers for libc-bin (2.23-0ubuntu7) 
...^M
  May  2 22:15:17 in-target: Processing triggers for systemd (229-4ubuntu17) 
...^M
  May  2 22:15:17 in-target: Processing triggers for ureadahead (0.100.0-19) 
...^M
  May  2 22:15:17 in-target: Processing triggers for dbus (1.10.6-1ubuntu3.3) 
...^M
  May  2 22:15:17 in-target: Errors were encountered while processing:^M
  May  2 22:15:17 in-target:  kdump-tools^M
  May  2 22:15:17 in-target:  linux-crashdump^M
  May  2 22:15:18 in-target: E: Sub-process /usr/bin/dpkg returned an error 
code (1)
  May  2 22:15:18 in-target: Setting up kdump-tools (1:1.5.9-5ubuntu0.4) ...
  May  2 22:15:18 in-target: dpkg: error processing package kdump-tools 
(--configure):
  May  2 22:15:18 in-target:  subprocess installed post-installation script 
returned error exit status 1
  May  2 22:15:18 in-target: dpkg: dependency problems prevent configuration of 
linux-crashdump:
  May  2 22:15:18 in-target:  linux-crashdump depends on kdump-tools; however:
  May  2 22:15:18 in-target:   Package kdump-tools is not configured yet.
  May  2 22:15:18 in-target: 
  May  2 22:15:18 in-target: dpkg: error processing package linux-crashdump 
(--configure):
  May  2 22:15:18 in-target:  dependency problems - leaving unconfigured
  May  2 22:15:18 in-target: Errors were encountered while processing:
  May  2 22:15:18 in-target:  kdump-tools
  May  2 22:15:18 in-target:  linux-crashdump
  May  2 22:15:18 main-menu[616]: WARNING **: Configuring 'pkgsel' failed with 
error code 100
  May  2 22:15:18 main-menu[616]: WARNING **: Menu item 'pkgsel' failed.

  
  After this the 'Select and install software' dialog pops up and says, that 
'Installation step failed'. If one presses '', one gets bombed back 
into the 'Ubuntu installer main menu'.
  Now you get into a loop, when choosing the 'Select and install software' item 
from the menu.

  Installer image is 'Linux foo 4.4.0-62-generic #83-Ubuntu SMP Wed Jan
  18 14:10:15 UTC 2017 x86_64 GNU/Linux'.

  The only workaround found so far is:
  cp -p /target/var/lib/dpkg/info/kdump-tools.postinst \
  /target/var/lib/dpkg/info/kdump-tools.postinst.suck
  printf '#!/bin/sh\nexit 0\n' \
  >/target/var/lib/dpkg/info/kdump-tools.postinst

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

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

[Kernel-packages] [Bug 1687791] Re: Install of kdump-tools fails

[Jens Elkner]

~ #  sed -i.orig -e '/^set/ a\set -x' 
/target/var/lib/dpkg/info/kdump-tools.postinst
~ # tail -f /var/log/syslog 
May  5 12:11:29 in-target:  linux-crashdump depends on kdump-tools; however:
May  5 12:11:29 in-target:   Package kdump-tools is not configured yet.
May  5 12:11:29 in-target: 
May  5 12:11:29 in-target: dpkg: error processing package linux-crashdump 
(--configure):
May  5 12:11:29 in-target:  dependency problems - leaving unconfigured
May  5 12:11:29 in-target: Errors were encountered while processing:
May  5 12:11:29 in-target:  kdump-tools
May  5 12:11:29 in-target:  linux-crashdump
May  5 12:11:29 main-menu[422]: WARNING **: Configuring 'pkgsel' failed with 
error code 100
May  5 12:11:29 main-menu[422]: WARNING **: Menu item 'pkgsel' failed.

May  5 12:13:15 main-menu[422]: INFO: Modifying debconf priority limit from 
'critical' to 'high'
May  5 12:13:15 debconf: Setting debconf/priority to high
May  5 12:13:15 main-menu[422]: INFO: Falling back to the package description 
for brltty-udeb
May  5 12:13:20 main-menu[422]: INFO: Falling back to the package description 
for brltty-udeb
May  5 12:13:20 main-menu[422]: INFO: Menu item 'pkgsel' selected
May  5 12:13:21 in-target: Reading package lists...
May  5 12:13:21 in-target: 
May  5 12:13:21 in-target: Building dependency tree...
May  5 12:13:21 in-target: 
May  5 12:13:21 in-target: Reading state information...
May  5 12:13:21 in-target: 
May  5 12:13:21 in-target: tasksel is already the newest version (3.34ubuntu3).
May  5 12:13:21 in-target: 0 upgraded, 0 newly installed, 0 to remove and 0 not 
upgraded.
May  5 12:13:21 in-target: 2 not fully installed or removed.
May  5 12:13:21 in-target: After this operation, 0 B of additional disk space 
will be used.
May  5 12:13:21 in-target: Setting up kdump-tools (1:1.5.9-5ubuntu0.4) ...^M
May  5 12:13:21 in-target: + uname -r^M
May  5 12:13:21 in-target: + /etc/kernel/postinst.d/kdump-tools 
4.4.0-62-generic^M
May  5 12:13:21 in-target: dpkg: error processing package kdump-tools 
(--configure):^M
May  5 12:13:21 in-target:  subprocess installed post-installation script 
returned error exit status 1^M
May  5 12:13:21 in-target: No apport report written because the error message 
indicates its a followup error from a previous failure.
May  5 12:13:21 in-target: dpkg: dependency problems prevent configuration of 
linux-crashdump:^M
May  5 12:13:21 in-target:  linux-crashdump depends on kdump-tools; however:^M
May  5 12:13:21 in-target:   Package kdump-tools is not configured yet.^M
May  5 12:13:21 in-target: ^M
May  5 12:13:21 in-target: dpkg: error processing package linux-crashdump 
(--configure):^M
May  5 12:13:21 in-target:  dependency problems - leaving unconfigured^M
May  5 12:13:21 in-target: Errors were encountered while processing:^M
May  5 12:13:21 in-target:  kdump-tools^M
May  5 12:13:21 in-target:  linux-crashdump^M
May  5 12:13:22 in-target: E: Sub-process /usr/bin/dpkg returned an error code 
(1)
May  5 12:13:22 in-target: Setting up kdump-tools (1:1.5.9-5ubuntu0.4) ...
May  5 12:13:22 in-target: + uname -r
May  5 12:13:22 in-target: + /etc/kernel/postinst.d/kdump-tools 4.4.0-62-generic
May  5 12:13:22 in-target: dpkg: error processing package kdump-tools 
(--configure):
May  5 12:13:22 in-target:  subprocess installed post-installation script 
returned error exit status 1
May  5 12:13:22 in-target: dpkg: dependency problems prevent configuration of 
linux-crashdump:
May  5 12:13:22 in-target:  linux-crashdump depends on kdump-tools; however:
May  5 12:13:22 in-target:   Package kdump-tools is not configured yet.
May  5 12:13:22 in-target: 
May  5 12:13:22 in-target: dpkg: error processing package linux-crashdump 
(--configure):
May  5 12:13:22 in-target:  dependency problems - leaving unconfigured
May  5 12:13:22 in-target: Errors were encountered while processing:
May  5 12:13:22 in-target:  kdump-tools
May  5 12:13:22 in-target:  linux-crashdump
May  5 12:13:24 pkgsel: checking for (security) updates to the base system
May  5 12:13:25 in-target: Reading package lists...
May  5 12:13:25 in-target: 
May  5 12:13:25 in-target: Building dependency tree...
May  5 12:13:25 in-target: 
May  5 12:13:25 in-target: Reading state information...
May  5 12:13:25 in-target: 
May  5 12:13:25 in-target: Calculating upgrade...
May  5 12:13:25 in-target: 
May  5 12:13:25 in-target: 0 upgraded, 0 newly installed, 0 to remove and 0 not 
upgraded.
May  5 12:13:25 in-target: 2 not fully installed or removed.
May  5 12:13:25 in-target: After this operation, 0 B of additional disk space 
will be used.
May  5 12:13:25 in-target: Setting up kdump-tools (1:1.5.9-5ubuntu0.4) ...^M
May  5 12:13:25 in-target: + uname -r^M
May  5 12:13:25 in-target: + /etc/kernel/postinst.d/kdump-tools 
4.4.0-62-generic^M
May  5 12:13:25 in-target: dpkg: error processing package kdump-tools 
(--configure):^M
May  5 12:13:25 in-target:  subprocess installed post-installation script 
returned error exit status 1^M
May  5 

[Kernel-packages] [Bug 1688424] [NEW] grub-mkrelpath returns invalid zfs dataset -> initramfs: mount /root fails

[Jens Elkner]

Public bug reported:

If zfs is used for boot, boot will fail because of bogus information returned by
/usr/bin/grub-mkrelpath.  E.g. if the zfs dataset for / is rpool/ROOT/linux:

# /usr/bin/grub-mkrelpath /
/ROOT/linux@


This leads to a bogus /boot/grub/grub.cfg because /etc/grub.d/10_linux 
generates a boot entry like this:
linux   /ROOT/linux@/boot/vmlinuz-4.4.0-77-generic root=ZFS=/ROOT/linux ro 
crashkernel=384M-2G:64M,2G-:128M bootdegraded=true debug=y console=ttyS1,115200 
 crashkernel=384M-:128M

This in turn causes that initramfs to fail on boot:
...
+ wait_for_udev
+ command -v udevadm
+ udevadm settle
+ modprobe zfs zfs_autoimport_disable=1
+ ZFS_BOOTFS=/ROOT/linux
+ echo /ROOT/linux
+ sed -e s,/.*,,
+ ZFS_RPOOL=
+ delay=0
+ [ 0 -gt 0 ]
+ unset delay
+ zpool import -N 
[   10.922149] SPL: The /etc/hostid file is not found.
[   10.927031] SPL: using hostid 0x
+ ZFS_STDERR=cannot import '': no such pool available
+ ZFS_ERROR=1
+ [ 1 -ne 0 ]
+ panic Command: zpool import -N 
Message: cannot import '': no such pool available
Error: 1

Manually import the root pool at the command prompt and then exit.
Hint: Try:  zpool import -f -R / -N 


Wrong hint BTW, but at least a hint: "zpool import; zpool import 
${poolID}|rpool" fixes it.
Anyway, when continuing after an 'exit' it fails with:

...
+ zpool status -L 
+ [ n != y ]
+ log_begin_msg Setting mountpoint=/ on ZFS filesystem /ROOT/linux
+ _log_msg Begin: Setting mountpoint=/ on ZFS filesystem /ROOT/linux ... 
+ [ n = y ]
+ printf Begin: Setting mountpoint=/ on ZFS filesystem /ROOT/linux ... 
Begin: Setting mountpoint=/ on ZFS filesystem /ROOT/linux ... + zfs set 
mountpoint=/ /ROOT/linux
+ ZFS_STDERR=cannot open '/ROOT/linux': invalid dataset name
+ [ n != y ]
+ log_end_msg
+ _log_msg done.\n
+ [ n = y ]
+ printf done.\n
done.
+ [ n != y ]
+ log_begin_msg Mounting ZFS filesystem /ROOT/linux
+ _log_msg Begin: Mounting ZFS filesystem /ROOT/linux ... 
+ [ n = y ]
+ printf Begin: Mounting ZFS filesystem /ROOT/linux ... 
Begin: Mounting ZFS filesystem /ROOT/linux ... + mount -t zfs -o zfsutil 
/ROOT/linux /root
+ ZFS_STDERR=filesystem 'ROOT/linux' cannot be mounted, unable to open the 
dataset
mount: mounting /ROOT/linux on /root failed: No such file or directory
+ ZFS_ERROR=1
+ [ n != y ]
+ log_end_msg
+ _log_msg done.\n
+ [ n = y ]
+ printf done.\n
done.
+ [ 1 -ne 0 ]
+ panic Command: mount -t zfs -o zfsutil /ROOT/linux /root
Message: filesystem 'ROOT/linux' cannot be mounted, unable to open the dataset
mount: mounting /ROOT/linux on /root failed: No such file or directory
Error: 1

Manually mount the root filesystem on /root and then exit.


A 'mount -t zfs -o zfsutil rpool/ROOT/linux /root' fixis it and after an 'exit' 
the system finally starts.

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

** Package changed: dmidecode (Ubuntu) => grub2 (Ubuntu)

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

Title:
  grub-mkrelpath returns invalid zfs dataset -> initramfs: mount /root
  fails

Status in grub2 package in Ubuntu:
  New

Bug description:
  If zfs is used for boot, boot will fail because of bogus information returned 
by
  /usr/bin/grub-mkrelpath.  E.g. if the zfs dataset for / is rpool/ROOT/linux:

  # /usr/bin/grub-mkrelpath /
  /ROOT/linux@

  
  This leads to a bogus /boot/grub/grub.cfg because /etc/grub.d/10_linux 
generates a boot entry like this:
  linux   /ROOT/linux@/boot/vmlinuz-4.4.0-77-generic root=ZFS=/ROOT/linux ro 
crashkernel=384M-2G:64M,2G-:128M bootdegraded=true debug=y console=ttyS1,115200 
 crashkernel=384M-:128M

  This in turn causes that initramfs to fail on boot:
  ...
  + wait_for_udev
  + command -v udevadm
  + udevadm settle
  + modprobe zfs zfs_autoimport_disable=1
  + ZFS_BOOTFS=/ROOT/linux
  + echo /ROOT/linux
  + sed -e s,/.*,,
  + ZFS_RPOOL=
  + delay=0
  + [ 0 -gt 0 ]
  + unset delay
  + zpool import -N 
  [   10.922149] SPL: The /etc/hostid file is not found.
  [   10.927031] SPL: using hostid 0x
  + ZFS_STDERR=cannot import '': no such pool available
  + ZFS_ERROR=1
  + [ 1 -ne 0 ]
  + panic Command: zpool import -N 
  Message: cannot import '': no such pool available
  Error: 1

  Manually import the root pool at the command prompt and then exit.
  Hint: Try:  zpool import -f -R / -N 

  
  Wrong hint BTW, but at least a hint: "zpool import; zpool import 
${poolID}|rpool" fixes it.
  Anyway, when continuing after an 'exit' it fails with:

  ...
  + zpool status -L 
  + [ n != y ]
  + log_begin_msg Setting mountpoint=/ on ZFS filesystem /ROOT/linux
  + _log_msg Begin: Setting mountpoint=/ on ZFS filesystem /ROOT/linux ... 
  + [ n = y ]
  + printf Begin: Setting mountpoint=/ on ZFS filesystem /ROOT/linux ... 
  Begin: Setting mountpoint=/ on ZFS filesystem /ROOT/linux ... + zfs set 
mountpoint=/ /ROOT/linux
  + ZFS_STDERR=cannot open '/ROOT/linux': 

[Kernel-packages] [Bug 1688162] Re: dmidecode should print diagnostic messages to stderr

[Jens Elkner]

Hi Christian,

Yepp, the patch looks good. Would be nice to get this integrated (or to
sync dmidecode with the current GNU version).

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

Title:
  dmidecode should print diagnostic messages to stderr

Status in dmidecode package in Ubuntu:
  Triaged

Bug description:
  Ubuntu version of dmidecode breaks several scripts because it prints
  diagnostics messages to stdout instead of stderr.

  E.g.: sudo /bin/ksh93
  # /usr/sbin/dmidecode -s baseboard-manufacturer 2>/dev/null
  Supermicro
  Invalid entry length (16). Fixed up to 11.

  
  The original version (https://git.savannah.nongnu.org/git/dmidecode.git) 
however, works as expected:
  # /tmp/dmidecode -s baseboard-manufacturer 2>/dev/null
  Supermicro

  
  $ /usr/bin/lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  Codename: xenial

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

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

[Kernel-packages] [Bug 1688162] [NEW] dmidecode should print diagnostic messages to stderr

[Jens Elkner]

Public bug reported:

Ubuntu version of dmidecode breaks several scripts because it prints
diagnostics messages to stdout instead of stderr.

E.g.: sudo /bin/ksh93
# /usr/sbin/dmidecode -s baseboard-manufacturer 2>/dev/null
Supermicro
Invalid entry length (16). Fixed up to 11.


The original version (https://git.savannah.nongnu.org/git/dmidecode.git) 
however, works as expected:
# /tmp/dmidecode -s baseboard-manufacturer 2>/dev/null
Supermicro


$ /usr/bin/lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.2 LTS
Release:16.04
Codename:   xenial

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


** Tags: dmidecode

** Package changed: qemu (Ubuntu) => dmidecode (Ubuntu)

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

Title:
  dmidecode should print diagnostic messages to stderr

Status in dmidecode package in Ubuntu:
  New

Bug description:
  Ubuntu version of dmidecode breaks several scripts because it prints
  diagnostics messages to stdout instead of stderr.

  E.g.: sudo /bin/ksh93
  # /usr/sbin/dmidecode -s baseboard-manufacturer 2>/dev/null
  Supermicro
  Invalid entry length (16). Fixed up to 11.

  
  The original version (https://git.savannah.nongnu.org/git/dmidecode.git) 
however, works as expected:
  # /tmp/dmidecode -s baseboard-manufacturer 2>/dev/null
  Supermicro

  
  $ /usr/bin/lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  Codename: xenial

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

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

[Kernel-packages] [Bug 1527727] Re: grub-probe for zfs assumes all devices prefix with /dev, ignoring /dev/disk/...

[Jens Elkner]

Done - see 1687664.

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

Title:
  grub-probe for zfs assumes all devices prefix with /dev, ignoring
  /dev/disk/...

Status in grub:
  Unknown
Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  In Progress
Status in grub2-signed source package in Xenial:
  In Progress
Status in zfs-linux source package in Xenial:
  Confirmed

Bug description:
  [Impact]
  Installs over ZFS where a ZFS disk is expected to be used as a root device.

  [Test case]
  - Run update-grub on a system with a ZFS root filesystem.

  [Regression Potential]
  Installs relying on the current broken behavior to avoid listing other 
operating systems in grub menu may find that new entries are added.

  ---

  update-grub runs /usr/sbin/grub-probe

  Without libzfslinux support compiled in, /usr/sbin/grub-probe runs
  ["zpool", "status", poolname] to find out ZFS info.

  zpool responds with device names as used at (I think!) pool creation
  time. Often, this is /dev/disk/by-id/... names, without the path.

  grub-probe then parses the output, and takes the names of devices, and
  if they do not start with a "/", it prepends "/dev/".

  It then tests the existence of the path name of the device. it fails.

  grub-probe then returns  something like

  /usr/sbin/grub-probe: error: failed to get canonical path of `/dev
  /ata-ST31000333AS_-part1'.

  The actual path is of course /dev/disk/by-
  id/ST31000333AS_-part1

  It can prepend smarter than "/dev" or it can understand ZFS natively,
  to fix the problem.

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

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

[Kernel-packages] [Bug 1527727] Re: grub-probe for zfs assumes all devices prefix with /dev, ignoring /dev/disk/...

[Jens Elkner]

Just encountered the same problem with xenial:

grub-probe: error: failed to get canonical path of `/dev/HDD0p2'
See also http://savannah.gnu.org/bugs/?50896

IMHO "zpool status -P $pool" should be used, everything else is a
kludge, which will fail sooner or later.

** Bug watch added: GNU Savannah Bug Tracker #50896
   http://savannah.gnu.org/bugs/?50896

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

Title:
  grub-probe for zfs assumes all devices prefix with /dev, ignoring
  /dev/disk/...

Status in grub:
  Unknown
Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  In Progress
Status in grub2-signed source package in Xenial:
  In Progress
Status in zfs-linux source package in Xenial:
  Confirmed

Bug description:
  [Impact]
  Installs over ZFS where a ZFS disk is expected to be used as a root device.

  [Test case]
  - Run update-grub on a system with a ZFS root filesystem.

  [Regression Potential]
  Installs relying on the current broken behavior to avoid listing other 
operating systems in grub menu may find that new entries are added.

  ---

  update-grub runs /usr/sbin/grub-probe

  Without libzfslinux support compiled in, /usr/sbin/grub-probe runs
  ["zpool", "status", poolname] to find out ZFS info.

  zpool responds with device names as used at (I think!) pool creation
  time. Often, this is /dev/disk/by-id/... names, without the path.

  grub-probe then parses the output, and takes the names of devices, and
  if they do not start with a "/", it prepends "/dev/".

  It then tests the existence of the path name of the device. it fails.

  grub-probe then returns  something like

  /usr/sbin/grub-probe: error: failed to get canonical path of `/dev
  /ata-ST31000333AS_-part1'.

  The actual path is of course /dev/disk/by-
  id/ST31000333AS_-part1

  It can prepend smarter than "/dev" or it can understand ZFS natively,
  to fix the problem.

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

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

[Kernel-packages] [Bug 1578141] Re: Predictable interface names partially broken with igb driver

[Dr. Jens Rosenboom]

@Martin: Fixing the installed system is easy, the bad case happens when
the installer sets up the system with "rename2" as the first interface,
making access via console necessary in order to recover.

root@compute-node37:~# SYSTEMD_LOG_LEVEL=debug udevadm test-builtin net_id 
/sys/class/net/eno1
calling: test-builtin
=== trie on-disk ===
tool version:  229
file size: 6841778 bytes
header size 80 bytes
strings1755242 bytes
nodes  5086456 bytes
Load module index
timestamp of '/etc/systemd/network' changed
timestamp of '/lib/systemd/network' changed
Parsed configuration file /lib/systemd/network/99-default.link
Parsed configuration file /lib/systemd/network/90-mac-for-usb.link
Created link configuration context.
ID_NET_NAME_MAC=enx002590d8975a
ID_OUI_FROM_DATABASE=Super Micro Computer, Inc.
ID_NET_NAME_ONBOARD=eno1
ID_NET_NAME_PATH=enp7s0f0
Unload module index
Unloaded link configuration context.
root@compute-node37:~# SYSTEMD_LOG_LEVEL=debug udevadm test-builtin net_id 
/sys/class/net/rename3  

  
calling: test-builtin
=== trie on-disk ===
tool version:  229
file size: 6841778 bytes
header size 80 bytes
strings1755242 bytes
nodes  5086456 bytes
Load module index
timestamp of '/etc/systemd/network' changed
timestamp of '/lib/systemd/network' changed
Parsed configuration file /lib/systemd/network/99-default.link
Parsed configuration file /lib/systemd/network/90-mac-for-usb.link
Created link configuration context.
ID_NET_NAME_MAC=enx002590d8975b
ID_OUI_FROM_DATABASE=Super Micro Computer, Inc.
ID_NET_NAME_ONBOARD=eno1
ID_NET_NAME_PATH=enp7s0f1
Unload module index
Unloaded link configuration context.

Also note that the whole renaming process seems to come from an Ubuntu
specific patch in Revert-udev-network-device-renaming-immediately-
give.patch, IIUC plain systemd would fail the renaming process and end
up with either (eno1, eth1) or (eth0, eno1) as interface tuples.

If there was a way to get rid of the race condition and make sure that
the system always ends up with the same tuple, that would already be a
large step forward.

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

Title:
  Predictable interface names partially broken with igb driver

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

Bug description:
  Note: I'm not sure whether this is really a kernel bug or something
  within systemd/udev, please advise how to further debug.

  On a system with two GE ports, instead of getting named eno1 and eno2,
  I am getting eno1 and renameN. Where N starts at 3 and increases by 2
  on every iteration of doing "rmmod igb;modprobe igb". The
  corresponding lines in dmesg look like this:

  [2.748429] igb :07:00.0: added PHC on eth0
  [2.748431] igb :07:00.0: Intel(R) Gigabit Ethernet Network Connection
  [2.748433] igb :07:00.0: eth0: (PCIe:5.0Gb/s:Width x4) 
00:25:90:d7:60:8e
  [2.748505] igb :07:00.0: eth0: PBA No: 106100-000
  [2.748506] igb :07:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx 
queue(s)
  [2.802555] igb :07:00.1: added PHC on eth1
  [2.802557] igb :07:00.1: Intel(R) Gigabit Ethernet Network Connection
  [2.802559] igb :07:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 
00:25:90:d7:60:8f
  [2.802631] igb :07:00.1: eth1: PBA No: 106100-000
  [2.802632] igb :07:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx 
queue(s)
  [2.803618] igb :07:00.0 eno1: renamed from eth0
  [2.833208] igb :07:00.1 rename3: renamed from eth1

  What is even worse: Sometimes the naming changes and the second
  interface ends up as eno1 while the first interface is named renameN
  with an even N. The bad thing about this version is that when it
  happens while the installer is running, the installer will setup
  "rename2" as the primary network interface, which works fine for the
  installation itself, but after installation is finished and the first
  boot of the installed system happens, that interface will be gone,
  leaving the system without network connectivity.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  4 09:48 seq
   crw-rw 1 root audio 116, 33 May  4 09:48 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  

[Kernel-packages] [Bug 1578141] Re: Predictable interface names partially broken with igb driver

[Dr. Jens Rosenboom]

Looking further, it seems that the BIOS is providing broken information,
see this snippet from dmidecode output:

Handle 0x007E, DMI type 41, 11 bytes
Onboard Device
Reference Designation:  Onboard Intel Ethernet 1
Type: Ethernet
Status: Enabled
Type Instance: 1
Bus Address: :07:00.0

Handle 0x007F, DMI type 41, 11 bytes
Onboard Device
Reference Designation:  Onboard Intel Ethernet 2
Type: Ethernet
Status: Enabled
Type Instance: 1
Bus Address: :07:00.1

and as a result we get ID_NET_NAME_ONBOARD=eno1 for both devices. So
udev tries to rename both interfaces to eno1, only one succeeds, the
other one fails due to a name collision. Would be nice to implement a
workaround for these broken BIOS data.

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

Title:
  Predictable interface names partially broken with igb driver

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

Bug description:
  Note: I'm not sure whether this is really a kernel bug or something
  within systemd/udev, please advise how to further debug.

  On a system with two GE ports, instead of getting named eno1 and eno2,
  I am getting eno1 and renameN. Where N starts at 3 and increases by 2
  on every iteration of doing "rmmod igb;modprobe igb". The
  corresponding lines in dmesg look like this:

  [2.748429] igb :07:00.0: added PHC on eth0
  [2.748431] igb :07:00.0: Intel(R) Gigabit Ethernet Network Connection
  [2.748433] igb :07:00.0: eth0: (PCIe:5.0Gb/s:Width x4) 
00:25:90:d7:60:8e
  [2.748505] igb :07:00.0: eth0: PBA No: 106100-000
  [2.748506] igb :07:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx 
queue(s)
  [2.802555] igb :07:00.1: added PHC on eth1
  [2.802557] igb :07:00.1: Intel(R) Gigabit Ethernet Network Connection
  [2.802559] igb :07:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 
00:25:90:d7:60:8f
  [2.802631] igb :07:00.1: eth1: PBA No: 106100-000
  [2.802632] igb :07:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx 
queue(s)
  [2.803618] igb :07:00.0 eno1: renamed from eth0
  [2.833208] igb :07:00.1 rename3: renamed from eth1

  What is even worse: Sometimes the naming changes and the second
  interface ends up as eno1 while the first interface is named renameN
  with an even N. The bad thing about this version is that when it
  happens while the installer is running, the installer will setup
  "rename2" as the primary network interface, which works fine for the
  installation itself, but after installation is finished and the first
  boot of the installed system happens, that interface will be gone,
  leaving the system without network connectivity.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  4 09:48 seq
   crw-rw 1 root audio 116, 33 May  4 09:48 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  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: Wed May  4 10:00:39 2016
  HibernationDevice: RESUME=/dev/mapper/compute--node37--vg-swap
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Supermicro X9DRT-HF+
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/compute--node37--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0c
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9DRT-HF+
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  dmi.chassis.asset.tag: To Be Filled 

[Kernel-packages] [Bug 1578141] Re: Predictable interface names partially broken with igb driver

[Dr. Jens Rosenboom]

We have seen the issue only when deploying Xenial, installations running
Precise or Trusty do not seem to be affected.

Running with 4.6.0-040600rc6-generic has shown the same behaviour.

After doing the rmmod/modprobe cycle, I have now found the attached set
of messages in the output of "journalctl -x", so this seems to confirm
my suspicion of some bad interaction between kernel and systemd going
on.

** Attachment added: "Output of "journalctl -x" when doing "rmmod igb;sleep 
3;modprobe igb""
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578141/+attachment/4657073/+files/journal.txt

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

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

** Also affects: systemd (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/1578141

Title:
  Predictable interface names partially broken with igb driver

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

Bug description:
  Note: I'm not sure whether this is really a kernel bug or something
  within systemd/udev, please advise how to further debug.

  On a system with two GE ports, instead of getting named eno1 and eno2,
  I am getting eno1 and renameN. Where N starts at 3 and increases by 2
  on every iteration of doing "rmmod igb;modprobe igb". The
  corresponding lines in dmesg look like this:

  [2.748429] igb :07:00.0: added PHC on eth0
  [2.748431] igb :07:00.0: Intel(R) Gigabit Ethernet Network Connection
  [2.748433] igb :07:00.0: eth0: (PCIe:5.0Gb/s:Width x4) 
00:25:90:d7:60:8e
  [2.748505] igb :07:00.0: eth0: PBA No: 106100-000
  [2.748506] igb :07:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx 
queue(s)
  [2.802555] igb :07:00.1: added PHC on eth1
  [2.802557] igb :07:00.1: Intel(R) Gigabit Ethernet Network Connection
  [2.802559] igb :07:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 
00:25:90:d7:60:8f
  [2.802631] igb :07:00.1: eth1: PBA No: 106100-000
  [2.802632] igb :07:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx 
queue(s)
  [2.803618] igb :07:00.0 eno1: renamed from eth0
  [2.833208] igb :07:00.1 rename3: renamed from eth1

  What is even worse: Sometimes the naming changes and the second
  interface ends up as eno1 while the first interface is named renameN
  with an even N. The bad thing about this version is that when it
  happens while the installer is running, the installer will setup
  "rename2" as the primary network interface, which works fine for the
  installation itself, but after installation is finished and the first
  boot of the installed system happens, that interface will be gone,
  leaving the system without network connectivity.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  4 09:48 seq
   crw-rw 1 root audio 116, 33 May  4 09:48 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  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: Wed May  4 10:00:39 2016
  HibernationDevice: RESUME=/dev/mapper/compute--node37--vg-swap
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Supermicro X9DRT-HF+
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/compute--node37--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0c
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9DRT-HF+
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  dmi.chassis.asset.tag: To Be 

[Kernel-packages] [Bug 1578141] [NEW] Predictable interface names partially broken with igb driver

[Dr. Jens Rosenboom]

Public bug reported:

Note: I'm not sure whether this is really a kernel bug or something
within systemd/udev, please advise how to further debug.

On a system with two GE ports, instead of getting named eno1 and eno2, I
am getting eno1 and renameN. Where N starts at 3 and increases by 2 on
every iteration of doing "rmmod igb;modprobe igb". The corresponding
lines in dmesg look like this:

[2.748429] igb :07:00.0: added PHC on eth0
[2.748431] igb :07:00.0: Intel(R) Gigabit Ethernet Network Connection
[2.748433] igb :07:00.0: eth0: (PCIe:5.0Gb/s:Width x4) 00:25:90:d7:60:8e
[2.748505] igb :07:00.0: eth0: PBA No: 106100-000
[2.748506] igb :07:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx 
queue(s)
[2.802555] igb :07:00.1: added PHC on eth1
[2.802557] igb :07:00.1: Intel(R) Gigabit Ethernet Network Connection
[2.802559] igb :07:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 00:25:90:d7:60:8f
[2.802631] igb :07:00.1: eth1: PBA No: 106100-000
[2.802632] igb :07:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx 
queue(s)
[2.803618] igb :07:00.0 eno1: renamed from eth0
[2.833208] igb :07:00.1 rename3: renamed from eth1

What is even worse: Sometimes the naming changes and the second
interface ends up as eno1 while the first interface is named renameN
with an even N. The bad thing about this version is that when it happens
while the installer is running, the installer will setup "rename2" as
the primary network interface, which works fine for the installation
itself, but after installation is finished and the first boot of the
installed system happens, that interface will be gone, leaving the
system without network connectivity.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-21-generic 4.4.0-21.37
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 May  4 09:48 seq
 crw-rw 1 root audio 116, 33 May  4 09:48 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2
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: Wed May  4 10:00:39 2016
HibernationDevice: RESUME=/dev/mapper/compute--node37--vg-swap
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Supermicro X9DRT-HF+
PciMultimedia:
 
ProcEnviron:
 LANGUAGE=en_US:
 TERM=screen
 PATH=(custom, no user)
 LANG=en_US
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/compute--node37--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-21-generic N/A
 linux-backports-modules-4.4.0-21-generic  N/A
 linux-firmware1.157
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/21/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3.0c
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X9DRT-HF+
dmi.board.vendor: Supermicro
dmi.board.version: 0123456789
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0c:bd05/21/2014:svnSupermicro:pnX9DRT-HF+:pvr0123456789:rvnSupermicro:rnX9DRT-HF+:rvr0123456789:cvnSupermicro:ct17:cvr0123456789:
dmi.product.name: X9DRT-HF+
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro

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


** Tags: amd64 apport-bug xenial

** Attachment added: "version.log"
   
https://bugs.launchpad.net/bugs/1578141/+attachment/4655387/+files/version.log

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

Title:
  Predictable interface names partially broken with igb driver

Status in linux package in Ubuntu:
  New

Bug description:
  Note: I'm not sure whether this is really a kernel bug or something
  within systemd/udev, please advise how to further debug.

  On a system with two GE ports, instead of getting named eno1 and eno2,
  I am getting eno1 and renameN. Where N starts at 3 and increases by 2
  on every iteration of doing "rmmod igb;modprobe igb". The
  corresponding lines in dmesg look like this:

[Kernel-packages] [Bug 1524069] Re: [Xenial] KVM trusty guest 3.13.0-68 raid6-pq panic in raid6_avx21_gen_syndrome() while probing grub devices [was: Xenial KVM: updating Trusty guest from 3.13.0-68 t

[Dr. Jens Rosenboom]

I am seeing the same issue on some of my OpenStack compute nodes,
interestingly those which seem to have a newer CPU than others.

Affected CPU: Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz
Mapped in guest to: Intel Core i7 9xx (Nehalem Class Core i7)

Unaffected Host CPU: Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz
Mapped in guest to: Intel Xeon E312xx (Sandy Bridge)

Booting a Xenial guest on the affected host crashes during boot, see
http://paste.ubuntu.com/15204908/. A Wily guest runs fine at first, but
generates a similar traceback as soon as I modprobe raid6_pq.

Both hosts are running nova-compute from Wily. Please let me know if you
need any further details.

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

Title:
  [Xenial] KVM trusty guest 3.13.0-68 raid6-pq panic in
  raid6_avx21_gen_syndrome() while probing grub devices [was: Xenial
  KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes kernel
  exception]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The symptom I saw was this (note the segfault, and apt-get upgrade
  hangs after this):

  Setting up linux-image-3.13.0-71-generic (3.13.0-71.114) ...
  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 
3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-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-3.13.0-71-generic
  Found initrd image: /boot/initrd.img-3.13.0-71-generic
  Found linux image: /boot/vmlinuz-3.13.0-68-generic
  Found initrd image: /boot/initrd.img-3.13.0-68-generic
  Segmentation fault
  done
  Setting up linux-firmware (1.127.19) ...
  Setting up linux-image-extra-3.13.0-71-generic (3.13.0-71.114) ...
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
3.13.0-71-generic /boot/vmlinuz-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-generic
  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-71-generic 
/boot/vmlinuz-3.13.0-71-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-3.13.0-71-generic
  Found initrd image: /boot/initrd.img-3.13.0-71-generic
  Found linux image: /boot/vmlinuz-3.13.0-68-generic
  Found initrd image: /boot/initrd.img-3.13.0-68-generic

  In dmesg, I saw a corresponding kernel stack trace:

  [  522.649091] SGI XFS with ACLs, security attributes, realtime, large 
block/inode numbers, no debug enabled
  [  522.654031] JFS: nTxBlock = 8192, nTxLock = 65536
  [  522.660515] NTFS driver 2.1.30 [Flags: R/O MODULE].
  [  522.672519] QNX4 filesystem 0.2.3 registered.
  [  522.677257] xor: measuring software checksum speed
  [  522.715613]prefetch64-sse: 17306.000 MB/sec
  [  522.755589]generic_sse: 16039.000 MB/sec
  [  522.755590] xor: using function: prefetch64-sse (17306.000 MB/sec)
  [  522.823619] raid6: sse2x1   10481 MB/s
  [  522.891614] raid6: sse2x2   13303 MB/s
  [  522.959616] raid6: sse2x4   15209 MB/s
  [  522.963634] invalid opcode:  [#1] SMP 
  [  522.963645] Modules linked in: raid6_pq(+) xor ufs qnx4 hfsplus hfs minix 
ntfs msdos jfs xfs libcrc32c ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT 
xt_CHECKSUM iptable_mangle xt_tcpudp bridge stp llc ip6table_filter ip6_tables 
iptable_filter ip_tables ebtable_nat ebtables x_tables snd_hda_intel 
snd_hda_codec snd_hwdep qxl snd_pcm kvm_intel ttm snd_page_alloc kvm 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_kms_helper snd_timer 
aesni_intel snd aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd drm 
soundcore lp parport serio_raw i2c_piix4 mac_hid pata_acpi floppy psmouse
  [  522.963746] CPU: 2 PID: 11288 Comm: modprobe Not tainted 3.13.0-68-generic 
#111-Ubuntu
  [  522.963751] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [  522.963755] task: 880059363000 ti: 88005dec6000 task.ti: 
88005dec6000

[Kernel-packages] [Bug 1437492] Re: boot stalls on USB detection errors

[Jens Ravesloot]

I have the same problem. I have the Asus Maximus VII Hero (Z97) and the same 
errors occur. On my PC I have elementary OS 0.3.2 (based on Ubuntu 14.04) 
installed. 
While booting with 'normal' bios setting and a USB3.0 HDD my keyboard and mouse 
(and basically all USB devices) stop working. When disabling the Intel xHCI 
Mode in the bios there is absolutely no problem. A friend of mine has an Asus 
Z97-A and he runs Arch and has exactly the same problem.

Update: I flashed my bios to the newest firmware (3003) and with xHCI
enabled in the bios my USB3.0 HDD still doesn't work, but all my other
devices  don't have any problems.

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

Title:
  boot stalls on USB detection errors

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

Bug description:
  My system boots slow. I investigated this and it seems 
systemd-udev-settle.service is the culprit.
  My system runs ext4 with GPT on UEFI.
  I do not use encryption or LVM.

  $ journalctl -u systemd-udev-settle
  -- Logs begin at fri 2015-03-27 19:03:06 CET, end at fri 2015-03-27 22:06:32 
CET. --
  mar 27 19:03:42 hostname systemd[1]: Started udev Wait for Complete Device 
Initialization.

  $ systemd-analyze
  Startup finished in 14.865s (firmware) + 11.133s (loader) + 6.127s (kernel) + 
42.079s (userspace) = 1min 14.206s

  $ systemd-analyze critical-chain
  http://paste.ubuntu.com/10691416/

  $ systemd-analyze blame
  36.013s systemd-udev-settle.service
  http://paste.ubuntu.com/10691314/

  $ systemctl show systemd-udev-settle.service -p RequiredBy
  RequiredBy=

  $ systemctl show systemd-udev-settle.service -p WantedBy
  WantedBy=friendly-recovery.service

  $ systemd-analyze plot > boot.svg
  http://imgh.us/boot_1.svg

  $ systemd-analyze dump
  http://paste.ubuntu.com/10691856/

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-5ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Mar 27 22:05:28 2015
  InstallationDate: Installed on 2013-12-26 (455 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic.efi.signed 
root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1491615] Re: Updating shim-signed freezes computer during postinstall

[Jens]

No, unfortunately not. :(

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

Title:
  Updating shim-signed freezes computer during postinstall

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When performing an update using ubuntu's default GUI tool, during the
  "configuring shim-signed" message, the computer freezes and needs to
  be reset. Unfortunately, there is nothing in the system log except for
  corruption (a lot of null bytes). But I experience these hard freezes
  regularly, whenever a GRUB or EFI related package is being updated,
  always during postinstall.

  [0.00] efi: EFI v2.31 by American Megatrends
  [0.00] efi:  ESRT=0xd9f7f998  ACPI=0xd8f97000  ACPI 2.0=0xd8f97000  
SMBIOS=0xf04d0  MPS=0xfd510 
  [0.00] esrt: Reserving ESRT space from 0xd9f7f998 to 
0xd9f7f9d0.
  [0.00] SMBIOS 2.8 present.
  [0.00] DMI: MSI MS-7817/CSM-B85M-E45 (MS-7817), BIOS V10.9 04/21/2015
  Linux kiste 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux

  This bug exists and keeps reappearing since I originally installed
  Ubuntu 14.04. However, for some reason it does not happen with a very
  similar second machine. This machine does not load the 'efi' kernel
  module on boot, can this be the reason?

  [0.00] SMBIOS 2.8 present.
  [0.00] DMI: MSI MS-7817/H81M-P33 (MS-7817), BIOS V1.5 05/30/2014
  Linux desktop 3.19.0+ #6 SMP Sat Feb 21 20:08:01 CET 2015 x86_64 x86_64 
x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: shim-signed 1.9+0.8-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep  2 09:33:16 2015
  SourcePackage: shim-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jens   2628 F pulseaudio
   /dev/snd/controlC0:  jens   2628 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/linuxkiste--vg-swap_1
  IwConfig:
   p2p1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic 
root=/dev/mapper/hostname--vg-root ro splash quiet 
netconsole=@192.168.178.59/p2p1,6665@192.168.178.62/ vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-28-generic N/A
   linux-backports-modules-3.19.0-28-generic  N/A
   linux-firmware 1.127.15
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.19.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CSM-B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnCSM-B85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7817
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1491615] Re: Updating shim-signed freezes computer during postinstall

[Jens]

I have installed the mainline kernel, but how do I provoke the series of
operations that caused this bug, ie. a kernel update with subsequent
'Oops' in (I suppose) the 'efi' module?

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

Title:
  Updating shim-signed freezes computer during postinstall

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When performing an update using ubuntu's default GUI tool, during the
  "configuring shim-signed" message, the computer freezes and needs to
  be reset. Unfortunately, there is nothing in the system log except for
  corruption (a lot of null bytes). But I experience these hard freezes
  regularly, whenever a GRUB or EFI related package is being updated,
  always during postinstall.

  [0.00] efi: EFI v2.31 by American Megatrends
  [0.00] efi:  ESRT=0xd9f7f998  ACPI=0xd8f97000  ACPI 2.0=0xd8f97000  
SMBIOS=0xf04d0  MPS=0xfd510 
  [0.00] esrt: Reserving ESRT space from 0xd9f7f998 to 
0xd9f7f9d0.
  [0.00] SMBIOS 2.8 present.
  [0.00] DMI: MSI MS-7817/CSM-B85M-E45 (MS-7817), BIOS V10.9 04/21/2015
  Linux kiste 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux

  This bug exists and keeps reappearing since I originally installed
  Ubuntu 14.04. However, for some reason it does not happen with a very
  similar second machine. This machine does not load the 'efi' kernel
  module on boot, can this be the reason?

  [0.00] SMBIOS 2.8 present.
  [0.00] DMI: MSI MS-7817/H81M-P33 (MS-7817), BIOS V1.5 05/30/2014
  Linux desktop 3.19.0+ #6 SMP Sat Feb 21 20:08:01 CET 2015 x86_64 x86_64 
x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: shim-signed 1.9+0.8-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep  2 09:33:16 2015
  SourcePackage: shim-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jens   2628 F pulseaudio
   /dev/snd/controlC0:  jens   2628 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/linuxkiste--vg-swap_1
  IwConfig:
   p2p1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic 
root=/dev/mapper/hostname--vg-root ro splash quiet 
netconsole=@192.168.178.59/p2p1,6665@192.168.178.62/ vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-28-generic N/A
   linux-backports-modules-3.19.0-28-generic  N/A
   linux-firmware 1.127.15
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.19.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CSM-B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnCSM-B85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7817
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1325667] Re: [MSI B85M-E45] resume oops after hibernation

[Jens]

Sorry, can't (and could not) - since 12.04 does not (yet) contain
Haswell graphics and mainboard drivers.

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

Title:
  [MSI B85M-E45] resume oops after hibernation

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With the above chipset, hibernation is unuseable because after
  resuming, the system sometimes freezes - after a couple minutes with a
  blank screen where only the mouse pointer is visible - and has to be
  hard reset.

  I tried booting the newest mainline kernel (3.15.0-031500rc2-generic)
  but this kernel does not boot on my system, it freezes after printing
  something about "big_key registered" on the console, and just sits
  there (no other output or activity).

  Here is the crash trace output.

  
  ProblemType: KernelOops
  Annotation: Your system might become unstable now and might need to be 
restarted.
  Date: Mon Jun  2 15:09:05 2014
  Failure: oops
  OopsText:
   BUG: Bad page map in process dbus-daemon  pte:88010100 pmd:2125d8067
   addr:7ff2862b5000 vm_flags:0870 anon_vma:  (null) 
mapping:8800d40ad538 index:18d
   vma->vm_ops->fault: filemap_fault+0x0/0x410
   vma->vm_file->f_op->mmap: ext4_file_mmap+0x0/0x60
   CPU: 3 PID: 27455 Comm: dbus-daemon Tainted: GF   B   W  O 3.13.0-27-generic 
#50-Ubuntu
   Hardware name: MSI MS-7817/B85M-E45 (MS-7817), BIOS V10.2 09/25/2013
88020f5a9600 88020ffa5c70 817199c4 7ff2862b5000
88020ffa5cb8 81174503 88010100 018d
8802125d85a8 88010100 7ff2862b5000 7ff286334000
   Call Trace:
[] dump_stack+0x45/0x56
[] print_bad_pte+0x1a3/0x250
[] unmap_page_range+0x58e/0x7f0
[] unmap_single_vma+0x81/0xf0
[] unmap_vmas+0x49/0x90
[] exit_mmap+0x9c/0x170
[] mmput+0x5c/0x120
[] do_exit+0x26c/0xa50
[] ? vtime_account_user+0x54/0x60
[] do_group_exit+0x3f/0xa0
[] SyS_exit_group+0x14/0x20
[] tracesys+0xe1/0xe6
   
  Package: linux-image-3.13.0-27-generic 3.13.0-27.50
  SourcePackage: linux
  Tags: kernel-oops
  Uname: Linux 3.13.0-27-generic x86_64

  
  ProblemType: KernelOops
  Annotation: Your system might become unstable now and might need to be 
restarted.
  Date: Mon Jun  2 15:09:06 2014
  Failure: oops
  OopsText:
   BUG: Bad page map in process dbus-daemon  pte:0100 pmd:2125d8067
   addr:7ff2862b4000 vm_flags:0870 anon_vma:  (null) 
mapping:8800d40ad538 index:18c
   vma->vm_ops->fault: filemap_fault+0x0/0x410
   vma->vm_file->f_op->mmap: ext4_file_mmap+0x0/0x60
   CPU: 3 PID: 27455 Comm: dbus-daemon Tainted: GF   W  O 3.13.0-27-generic 
#50-Ubuntu
   Hardware name: MSI MS-7817/B85M-E45 (MS-7817), BIOS V10.2 09/25/2013
88020f5a9600 88020ffa5c70 817199c4 7ff2862b4000
88020ffa5cb8 81174503 0100 018c
8802125d85a0 0100 7ff2862b4000 7ff286334000
   Call Trace:
[] dump_stack+0x45/0x56
[] print_bad_pte+0x1a3/0x250
[] unmap_page_range+0x58e/0x7f0
[] unmap_single_vma+0x81/0xf0
[] unmap_vmas+0x49/0x90
[] exit_mmap+0x9c/0x170
[] mmput+0x5c/0x120
[] do_exit+0x26c/0xa50
[] ? vtime_account_user+0x54/0x60
[] do_group_exit+0x3f/0xa0
[] SyS_exit_group+0x14/0x20
[] tracesys+0xe1/0xe6
   
  Package: linux-image-3.13.0-27-generic 3.13.0-27.50
  SourcePackage: linux
  Tags: kernel-oops
  Uname: Linux 3.13.0-27-generic x86_64

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-27-generic 3.13.0-27.50
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jens   3234 F.... pulseaudio
   /dev/snd/controlC0:  jens   3234 F pulseaudio
  CurrentDesktop: LXDE
  Date: Mon Jun  2 15:32:41 2014
  HibernationDevice: RESUME=UUID=8eef85a0-0281-49ce-9b60-e2a5aaf95c68
  InstallationDate: Installed on 2014-05-12 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac 
(20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7817
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-27-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-27-generic N/A
   linux-backports-modules-3.13.0-27-generic  N/A
   linux-firmware 1.127.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 

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

[Jens]

apport information

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

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

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

Title:
  Updating shim-signed freezes computer during postinstall

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When performing an update using ubuntu's default GUI tool, during the
  "configuring shim-signed" message, the computer freezes and needs to
  be reset. Unfortunately, there is nothing in the system log except for
  corruption (a lot of null bytes). But I experience these hard freezes
  regularly, whenever a GRUB or EFI related package is being updated,
  always during postinstall.

  [0.00] efi: EFI v2.31 by American Megatrends
  [0.00] efi:  ESRT=0xd9f7f998  ACPI=0xd8f97000  ACPI 2.0=0xd8f97000  
SMBIOS=0xf04d0  MPS=0xfd510 
  [0.00] esrt: Reserving ESRT space from 0xd9f7f998 to 
0xd9f7f9d0.
  [0.00] SMBIOS 2.8 present.
  [0.00] DMI: MSI MS-7817/CSM-B85M-E45 (MS-7817), BIOS V10.9 04/21/2015
  Linux kiste 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux

  This bug exists and keeps reappearing since I originally installed
  Ubuntu 14.04. However, for some reason it does not happen with a very
  similar second machine. This machine does not load the 'efi' kernel
  module on boot, can this be the reason?

  [0.00] SMBIOS 2.8 present.
  [0.00] DMI: MSI MS-7817/H81M-P33 (MS-7817), BIOS V1.5 05/30/2014
  Linux desktop 3.19.0+ #6 SMP Sat Feb 21 20:08:01 CET 2015 x86_64 x86_64 
x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: shim-signed 1.9+0.8-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep  2 09:33:16 2015
  SourcePackage: shim-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jens   2628 F pulseaudio
   /dev/snd/controlC0:  jens   2628 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/linuxkiste--vg-swap_1
  IwConfig:
   p2p1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic 
root=/dev/mapper/hostname--vg-root ro splash quiet 
netconsole=@192.168.178.59/p2p1,6665@192.168.178.62/ vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-28-generic N/A
   linux-backports-modules-3.19.0-28-generic  N/A
   linux-firmware 1.127.15
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.19.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CSM-B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnCSM-B85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7817
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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