[Kernel-packages] [Bug 1942684] Re: Kernel 5.14.X / 5.13.14 fails to boot

[DanglingPointer]

Tried building 5.14.14 from vanilla upstream 
https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.14.14.tar.xz
using the config from ubuntu mainline config-5.14.14-051414-generic
but removing the debian "pem" for a custom kernel build; and...
It fails to boot after grub for ivybridge and haswell machines.

I will try disabling "CONFIG_UBSAN_TRAP" to see if that works.

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

Title:
  Kernel 5.14.X / 5.13.14 fails to boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have been testing kernels 5.14.0 and 5.14.1 since their release on
  https://kernel.ubuntu.com/~kernel-ppa/mainline/ and my machine fails
  to boot with either one.

  However, I am able to boot just fine with 5.14.0-rc7.

  
  journalctl -b output attached with 5.14.1

  Motherboard: MSI X570 Tomahawk
  CPU: AMD 5900X
  GPU: AsusTek 6800XT
  OS: Hirsute 21.04
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-07-04 (62 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  wayland-session hirsute
  Uname: Linux 5.14.0-051400rc6-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Kernel-packages] [Bug 1947623] Re: Kernel Panic for Ubuntu 21.10, kernel 5.13.0.19.30 and Thinkpad E14 AMD

[Andreas Struller]

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

** This bug has been marked a duplicate of bug 1945590
   Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Title:
  Kernel Panic for Ubuntu 21.10, kernel 5.13.0.19.30 and Thinkpad E14
  AMD

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Can't boot computer after upgrade to Ubuntu 21.10, with kernel
  5.13.0.19.30, because of Kernel Panic Error.

  It seems to be a problem with:
   ETPS/2 Elantech TrackPoint
   ETPS/2 Elantech Touchpad

  Kernel 5.11.0-38 seems to work ok.

  Erorr:

  -
  [ 1.722420] psmouse serio1: elantech: assuming hardware version 4 (with 
firmware version 0x5f3001)
1.738396] psmouse serio1: elantech: Synaptics capabilities query result 
0x90, 0x18, 0xOd. 
  [ 1.753308] psmouse serio1: elantech: Elan sample query result 00, Od, a7
1.768372] psmouse serio1: elantech: Elan is body: 0x11, current fw 
version: 0x4
  [ 1.770839] usb 3-3: New USB device found, idVendor=27c6, idProduct=55a4, 
bcdDevice= 1.00
  [ 1.773016] usb 3-3: Neu USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 1.775165] usb 3-3: Product: Goodix FingerPrint Device
  [ 1.777283] usb 3-3: Manufacturer: Generic
  [ 1.783924] usb 1-3: New USB device found, idVendor=13d3, idProduct=56fb, 
bcdDevice=20.01
  [ 1.786078] usb 1-3: New USB device strings: Mfr=3, Product=1, 
SerialNumber=2
  [ 1.788191] usb 1-3: Product: Integrated Camera
  [ 1.790293] usb 1-3: Manufacturer: Azuremaue
  [ 1.792379] usb 1-3: SerialNuMber:
  [ 1.824961] Kernel panic - not syncing: stack-protector: Kernel stack is 
corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse]
  [ 1.827125] CPU: 5 PID: 150 Comm: kworker/5:2 Not tainted 
5.13.0-19-generic #19 -Ubuntu
1.828936] Hardware name: LENOVO 20T6000TPB/20T6000TPB, BIOS R1AET4OW 
(1.16 ) 09/06/2021
  [ 1.828936] Workqueue: events long serio handle_event
  [ 1.828936] Call Trace:
  [ 1.828936]  show stack+0x52/0x58
  [ 1.828936]  dump stack+0x7d/0x9c
  [ 1.828936]  panic+0x101/0x2e3
  [ 1.828936]  ? elantech change repurt id+0x1bf/0x1c4 [psmouse]
  [ 1.828936]  __stack_chk_fail+0x14/0x20
  [ 1.828936]  elantech change report id+0x1bf/0x1c4 [psmouse]
  [ 1.828936]  elantech_query_info.cold+0X316/0x594 [psmouse]
  [ 1.828936]  elantech_init*0x34/0x160 [psmouse]
  [ 1.828936]  ? synaptics send cmd*0x60/0x60 Ipsmousel
  [ 1.828936]  psmouse_extensions+0x4b6/0x520 kpsmouse]
  [ 1.828936]  psmouse switch_protocol+0x144/0x190 [psmouse]
  [ 1.828936]  psmouse_connect+0xI85/0x3a0 [psmouse]
  [ 1.828936]  seriodriver_probe+0x86/0x50
  [ 1.828936]  really_probe+0x245/0x4c0
  [ 1.828936]  driver_probe device+0xf0/0x160
  [ 1.828936]  device_driver attach+0xab/0xbO
  [ 1.828936]  __driver_attach+0xbZ/0x140
  [ 1.828936]  ? device_driver_attach+0xbO/0xbO
  [ 1.828936]  bus_foreachdeu+0x7e/0xc0
  [ 1.828936]  driver_attach+0xle/0x20
  [ 1.828936]  serio_handle_event+0xl0f/0x290
  [ 1.828936]  process_one_work+0x220/0x3c0
  [ 1.828936]  worker_thread+0x53/0x420
  [ 1.828936]  kthread+0xl1f/0x140
  [ 1.828936]  ? process_one_work+0x3c0/0x3c0
  [ 1.828936]  ? set_kthread_struct+0x50/0x50
  [ 1.828936]  ret_from_fork+0x22/0x30
  [ 1.828936] Kernel Offset: 0x2d00 from 0x8100 (relocation 
range: 0x000-0xbfff)
  [ 1.828936] - - -[ end Kernel panic - not syncing: stack-protector: 
Kernel stack is corrupted in: elantech_change_report_id+0x1bf/0x1c4 [psmouse] 
]---
  ---


  Computer:
  -
  Computer
  

  
  Summary
  ---

  -Computer-
  Processor : AMD Ryzen 5 4500U with Radeon Graphics
  Memory: 23817MB (6094MB used)
  Machine Type  : Notebook
  Operating System  : Ubuntu 21.10
  Date/Time : pon, 18 Oct 2021, 20:41:12
  -Display-
  Resolution: 2560x1440 pixels
  OpenGL Renderer   : AMD RENOIR (DRM 3.40.0, 5.11.0-38-generic, 
LLVM 12.0.1)
  X11 Vendor: The X.Org Foundation
  -Audio Devices-
  Audio Adapter : HDA-Intel - HD-Audio Generic
  Audio Adapter : HDA-Intel - HD-Audio Generic
  Audio Adapter : USB-Audio - ThinkPad USB-C Dock Gen2 USB Au
  -Input Devices-
   Power Button
   Lid Switch
   Sleep Button
   Power Button
   AT Translated Set 2 keyboard
   Video Bus
   ETPS/2 Elantech TrackPoint
   ETPS/2 Elantech Touchpad
   HD-Audio Generic HDMI/DP,pcm:3
   HD-Audio Generic HDMI/DP,pcm:7
   HD-Audio Generic HDMI/DP,pcm:8
   ThinkPad Extra Buttons
   HD-Audio Generic 

[Kernel-packages] [Bug 1930460] Re: HP Probook 470 G5 does not wake from sleep (just a black screen)

[Launchpad Bug Tracker]

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

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

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

Title:
  HP Probook 470 G5 does not wake from sleep (just a black screen)

Status in linux package in Ubuntu:
  Expired

Bug description:
  I have HP Probook 470 G5, first I installed Ubuntu 18.04 and then upgraded to 
20.04, in both cases the same problem arrived. 
  I have disabled sleep mode, but also, if I intensionally put laptop in sleep 
mode the same thing happened. 
  Sometimes when I try to wake him up, its just black screen and I cant do 
anything, I have to do hard restart (on button) 
  Or when I try to wake him from sleep, i can do that, but i see that laptop 
has been restarted. 

  Please exuce my bad English, I hope you understand me.
  I am beginner with Linux , and I dont have any idea how to solve this problem 
on my own 

  Thank you very much on your help

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  1 21:25:03 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-09-03 (271 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-15 (229 days ago)

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp/5.11.0.1022.22)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-gcp (5.11.0.1022.22) for 
hirsute have finished running.
The following regressions have been reported in tests triggered by the package:

glibc/2.33-0ubuntu5 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/hirsute/update_excuses.html#linux-meta-gcp

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws/5.4.0.1059.62)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-aws (5.4.0.1059.62) for 
focal have finished running.
The following regressions have been reported in tests triggered by the package:

backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (arm64, amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-aws

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1941798] Re: Focal update: v5.4.140 upstream stable release

[rojer]

this update caused a regression in ch341 driver:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947780

already fixed upstream, just needs to apply the upstream patch (which is
a revert of the original change).

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

Title:
  Focal update: v5.4.140 upstream stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     v5.4.140 upstream stable release
     from git://git.kernel.org/

  Revert "ACPICA: Fix memory leak caused by _CID repair function"
  ALSA: seq: Fix racy deletion of subscriber
  arm64: dts: ls1028a: fix node name for the sysclk
  ARM: imx: add missing iounmap()
  ARM: imx: add missing clk_disable_unprepare()
  ARM: dts: imx6qdl-sr-som: Increase the PHY reset duration to 10ms
  ARM: dts: colibri-imx6ull: limit SDIO clock to 25MHz
  ARM: imx: fix missing 3rd argument in macro imx_mmdc_perf_init
  ARM: dts: imx: Swap M53Menlo pinctrl_power_button/pinctrl_power_out pins
  arm64: dts: armada-3720-turris-mox: remove mrvl,i2c-fast-mode
  ALSA: usb-audio: fix incorrect clock source setting
  clk: stm32f4: fix post divisor setup for I2S/SAI PLLs
  ARM: dts: am437x-l4: fix typo in can@0 node
  omap5-board-common: remove not physically existing vdds_1v8_main 
fixed-regulator
  spi: imx: mx51-ecspi: Reinstate low-speed CONFIGREG delay
  spi: imx: mx51-ecspi: Fix low-speed CONFIGREG delay calculation
  scsi: sr: Return correct event when media event code is 3
  media: videobuf2-core: dequeue if start_streaming fails
  dmaengine: imx-dma: configure the generic DMA type to make it work
  net, gro: Set inner transport header offset in tcp/udp GRO hook
  net: dsa: sja1105: overwrite dynamic FDB entries with static ones in 
.port_fdb_add
  net: dsa: sja1105: invalidate dynamic FDB entries learned concurrently with 
statically added ones
  net: phy: micrel: Fix detection of ksz87xx switch
  net: natsemi: Fix missing pci_disable_device() in probe and remove
  gpio: tqmx86: really make IRQ optional
  sctp: move the active_key update after sh_keys is added
  nfp: update ethtool reporting of pauseframe control
  net: ipv6: fix returned variable type in ip6_skb_dst_mtu
  mips: Fix non-POSIX regexp
  bnx2x: fix an error code in bnx2x_nic_load()
  net: pegasus: fix uninit-value in get_interrupt_interval
  net: fec: fix use-after-free in fec_drv_remove
  net: vxge: fix use-after-free in vxge_device_unregister
  blk-iolatency: error out if blk_get_queue() failed in iolatency_set_limit()
  Bluetooth: defer cleanup of resources in hci_unregister_dev()
  USB: usbtmc: Fix RCU stall warning
  USB: serial: option: add Telit FD980 composition 0x1056
  USB: serial: ch341: fix character loss at high transfer rates
  USB: serial: ftdi_sio: add device ID for Auto-M3 OP-COM v2
  firmware_loader: use -ETIMEDOUT instead of -EAGAIN in fw_load_sysfs_fallback
  firmware_loader: fix use-after-free in firmware_fallback_sysfs
  ALSA: hda/realtek: add mic quirk for Acer SF314-42
  ALSA: usb-audio: Add registration quirk for JBL Quantum 600
  usb: cdns3: Fixed incorrect gadget state
  usb: gadget: f_hid: added GET_IDLE and SET_IDLE handlers
  usb: gadget: f_hid: fixed NULL pointer dereference
  usb: gadget: f_hid: idle uses the highest byte for duration
  usb: otg-fsm: Fix hrtimer list corruption
  clk: fix leak on devm_clk_bulk_get_all() unwind
  scripts/tracing: fix the bug that can't parse raw_trace_func
  tracing / histogram: Give calculation hist_fields a size
  optee: Clear stale cache entries during initialization
  tee: add tee_shm_alloc_kernel_buf()
  optee: Fix memory leak when failing to register shm pages
  tpm_ftpm_tee: Free and unregister TEE shared memory during kexec
  staging: rtl8723bs: Fix a resource leak in sd_int_dpc
  staging: rtl8712: get rid of flush_scheduled_work
  media: rtl28xxu: fix zero-length control request
  pipe: increase minimum default pipe size to 2 pages
  ext4: fix potential htree corruption when growing large_dir directories
  serial: tegra: Only print FIFO error message when an error occurs
  serial: 8250_mtk: fix uart corruption issue when rx power off
  serial: 8250: Mask out floating 16/32-bit bus bits
  MIPS: Malta: Do not byte-swap accesses to the CBUS UART
  serial: 8250_pci: Enumerate Elkhart Lake UARTs via dedicated driver
  serial: 8250_pci: Avoid irq sharing for MSI(-X) interrupts.
  time

[Kernel-packages] [Bug 1947780] Re: Kernel module ch341 bug

[rojer]

this update caused a regression:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941798

commit in question is https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal/commit/drivers/usb/serial/ch341.c?id=5e940f519a0d7ef1857b51b6ce3eb2a6731d9b26

the issue was reported upstream
https://bugzilla.kernel.org/show_bug.cgi?id=214131 and reverted in
https://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-
serial.git/commit/?h=usb-
linus&id=df7b16d1c00ecb3da3a30c999cdb39f273c99a2f

this commit needs to be brought in

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

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

Title:
  Kernel module ch341 bug

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 20.04.3 LTS

  Kernel module ch341 in Ubuntu kernels 5.4.0-88-generic  and 5.4.0-89-generic 
cannot program any esp8266 modules like Wemos D1 mini which contain ch340 chip 
uart controller. In kernel 5.4.0-86-generic everything is working good.
  Communication over serial connection is working in both cases only 
programming using esptool is broken, kernel module do not react properly to 
response fom ch340 chip I suppose

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-89-generic 5.4.0-89.100
  ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143
  Uname: Linux 5.4.0-89-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  boguslaw   1801 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Oct 19 21:14:32 2021
  HibernationDevice: RESUME=UUID=924612b1-306e-46c9-bd1f-7324041efb4a
  MachineType: Dell Inc. Latitude E6400
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic 
root=UUID=e7494ee9-8c5d-4133-bc4b-57986641b724 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-89-generic N/A
   linux-backports-modules-5.4.0-89-generic  N/A
   linux-firmware1.187.19
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A34
  dmi.board.name: 0RX493
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA34:bd06/04/2013:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0RX493:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude E6400
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.11/5.11.0.40.44~20.04.18)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-hwe-5.11 
(5.11.0.40.44~20.04.18) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (amd64, arm64, ppc64el)
systemd/245.4-4ubuntu3.13 (amd64, s390x, ppc64el)
glibc/2.31-0ubuntu9.2 (amd64)
nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-hwe-5.11

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Screen Brightness keys do not work on Lenovo IdeaPad 3

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've installed Ubuntu 21.10 with recent updates from scratch, and screen 
brightness control hot keys do not work. I can adjust brightness with slide bar 
in settings, and also with
  $ echo 2000 | sudo tee /sys/class/backlight/intel_backlight/brightness
  Both acpi_listen and 'sudo showkey' commands show no events, not even in a 
console.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-20-generic 5.13.0-20.20
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lex1476 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 22 19:24:38 2021
  InstallationDate: Installed on 2021-10-21 (1 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 82H7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/13/2021
  dmi.bios.release: 1.20
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GGCN20WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 3 14ITL6
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrGGCN20WW:bd01/13/2021:br1.20:efr1.20:svnLENOVO:pn82H7:pvrIdeaPad314ITL6:skuLENOVO_MT_82H7_BU_idea_FM_IdeaPad314ITL6:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad314ITL6:
  dmi.product.family: IdeaPad 3 14ITL6
  dmi.product.name: 82H7
  dmi.product.sku: LENOVO_MT_82H7_BU_idea_FM_IdeaPad 3 14ITL6
  dmi.product.version: IdeaPad 3 14ITL6
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1948505] [NEW] Screen Brightness keys do not work on Lenovo IdeaPad 3

[Lex Ross]

Public bug reported:

I've installed Ubuntu 21.10 with recent updates from scratch, and screen 
brightness control hot keys do not work. I can adjust brightness with slide bar 
in settings, and also with
$ echo 2000 | sudo tee /sys/class/backlight/intel_backlight/brightness
Both acpi_listen and 'sudo showkey' commands show no events, not even in a 
console.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-20-generic 5.13.0-20.20
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  lex1476 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 22 19:24:38 2021
InstallationDate: Installed on 2021-10-21 (1 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 82H7
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-20-generic N/A
 linux-backports-modules-5.13.0-20-generic  N/A
 linux-firmware 1.201
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/13/2021
dmi.bios.release: 1.20
dmi.bios.vendor: LENOVO
dmi.bios.version: GGCN20WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad 3 14ITL6
dmi.ec.firmware.release: 1.20
dmi.modalias: 
dmi:bvnLENOVO:bvrGGCN20WW:bd01/13/2021:br1.20:efr1.20:svnLENOVO:pn82H7:pvrIdeaPad314ITL6:skuLENOVO_MT_82H7_BU_idea_FM_IdeaPad314ITL6:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad314ITL6:
dmi.product.family: IdeaPad 3 14ITL6
dmi.product.name: 82H7
dmi.product.sku: LENOVO_MT_82H7_BU_idea_FM_IdeaPad 3 14ITL6
dmi.product.version: IdeaPad 3 14ITL6
dmi.sys.vendor: LENOVO

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


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

** Description changed:

  I've installed Ubuntu 21.10 with recent updates from scratch, and screen 
brightness control hot keys do not work. I can adjust brightness with slide bar 
in settings, and also with
- $ echo 2000 | sudo tee 
/sys/class/backlight/intel_backlight/brightness
+ $ echo 2000 | sudo tee /sys/class/backlight/intel_backlight/brightness
  Both acpi_listen and 'sudo showkey' commands show no events, not even in a 
console.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-20-generic 5.13.0-20.20
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  lex1476 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  lex1476 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 22 19:24:38 2021
  InstallationDate: Installed on 2021-10-21 (1 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 82H7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-5.13.0-20-generic N/A
-  linux-backports-modules-5.13.0-20-generic  N/A
-  linux-firmware 1.201
+  linux-restricted-modules-5.13.0-20-generic N/A
+  linux-backports-modules-5.13.0-20-generic  N/A
+  linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/13/2021
  dmi.bios.release: 1.20
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GGCN20WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 3 14ITL6
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrGGCN20WW:bd01/13/2021:br1.20:efr1.20:svnLENOVO:pn82H7:pvrIdeaPad314ITL6:skuLENOVO_MT_82H7_BU_idea_FM_IdeaPad314ITL6:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad314ITL6:
  dmi.product.family: IdeaPad 3 14ITL6
  dmi.product.name: 82H7
  dmi.product.sku: LENOVO_MT_82H7_BU_idea_FM_IdeaPad 3 14ITL6
  dmi.product.version: IdeaPad 3 14ITL6
  dmi.sys.vendor: LENOVO

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

Title:
  Screen Brightness keys do not work on Lenovo IdeaPad 3

Status in li

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-bluefield/5.4.0.1021.22)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-bluefield (5.4.0.1021.22) 
for focal have finished running.
The following regressions have been reported in tests triggered by the package:

fwts/unknown (arm64)
backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (arm64)
mali-midgard/unknown (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-bluefield

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1946304] Re: amdgpu: Add initial firmware for navi24 Beige Goby

[Steve Langasek]

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.187.20 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: linux-firmware (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  amdgpu: Add initial firmware for navi24 Beige Goby

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]

  New AMD Beige Goby/Navi24 GPU takes new firmware blobs.

  [Fix]

  Upstream commit 62fd279be67c ("amdgpu: Add initial firmware for Beige
  Goby").

  [Test Case]

  Apply firmware patch and boot with kernel >= v5.14, amdgpu should probe
  successfully.

  [Where problems could occur]

  New hardware. Expecting issues for external monitor hotplug, power
  consumption, etc.

  [Other Info]

  This change is already applied in upstream linux-firmware repo, and since
  it depends on kernel >= v5.14, only Focal is nominated for oem-5.14 here.

  == original bug report ==

  - This GPU is needed for AMD R21M-P50-50
  - amdgpu upstream driver already landed kernel v5.14.

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c?h=v5.14#n1216
 [git.kernel.org]
  /* BEIGE_GOBY */
  {0x1002, 0x7420, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
  {0x1002, 0x7421, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
  {0x1002, 0x7422, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
  {0x1002, 0x7423, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
  {0x1002, 0x743F, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},

  - linux-firmware is being under reviewed in
  https://lore.kernel.org/linux-
  
firmware/cadnq5_nnubczwd66tcutevyajrw5x2q2+kurtqws4ahzopw...@mail.gmail.com/T/#u

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1946304/+subscriptions


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

[Kernel-packages] [Bug 1947829] Re: Cannot identified WLAN card MT7921 in Ubunut OS with Install OS complete first OOBE Boot OS

[Steve Langasek]

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.187.20 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: linux-firmware (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  Cannot identified WLAN card MT7921 in Ubunut OS with Install OS
  complete first OOBE Boot OS

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Committed
Status in linux-firmware source package in Impish:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]

  Sometimes MT7921 may not be probed due to an endless mcu reset:

[ 5.789548] mt7921 mcu reset 0
[ 5.790625] mt7921 rx type 0x7
[ 5.790625] mt7921 eid 0x1 ext_eid 0x0
[ 5.790626] mt76_rx_event eid 0x1 ext_eid 0x0

  [Fix]

  WiFi and Bluetooth firmware updates from mainline:
  * e5a80ef8 linux-firmware: update frimware for mediatek bluetooth chip 
(MT7921)
  * d34196f5 linux-firmware: update firmware for MT7921 WiFi device

  [Test Case]

  This should fix the mcu reset and wireless/bluetooh devices should be
  probed successfully.

  [Where problems could occur]

  While there is explicit FW API for kernel version compatibility checking,
  this might introduce some hidden glitches that we don't know yet.

  [Other Info]

  MT7921 is supported since Impish 5.13 kernel, and Impish already has the
  latest Bluetooth firmware, so only the WiFi one is proposed. For oem-5.13
  and oem-5.14 in Focal, both firmware updates for Bluetooth and WiFi are
  required.

  == original bug report ==

  [Reproduce Steps]
  1.Add the wireless card MT7921 to SUT,Install the Ubuntu OS.
  2.During OOBE, Open the settings, there is no wireless settings in the 
panel,and the wifi cannot be used,issue occurred.

  [Results]
  Expected Result:The wireless settings should be exists and wifi can be used
  Actual Result:The wireless settings not exists and wifi can not be used

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1947829/+subscriptions


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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  [Lenovo P52s] Unable to  WiFi connect to Inseego Wavemaker 5G FX2000

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 21.10
  Release:  21.10

  2) uname -a
  Linux worldpeacepc 5.13.0-21-generic #21-Ubuntu SMP Tue Oct 19 08:59:28 UTC 
2021 x86_64 x86_64 x86_64 GNU/Linux

  3) What is expected to happen is when I click the top right hand side
  of the GUI, choose the SSID associated with the Inseego Wavemaker 5G
  FX2000, put in the known good password, it connects.

  4) What happens instead is it fails to connect. Same problem in Ubuntu
  21.04.

  However, I'm able to connect to other SSIDs from other non-Inseego
  devices. An iPhone 12 Mini and Windows 10 devices have no problems
  connecting.

  What I tried but it didn't change anything:
  1) Disable ipv6 in Ubuntu.
  2) In the Inseego GUI, change from:
  5GHz 802.11acn/ax

  to:
  5GHz 802.11ac

  WORKAROUND: In the Inseego GUI changing the WiFi security from:
  WPA3/WPA2 Transition

  to:
  WPA2 Personal PSK (AES)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-21-generic 5.13.0-21.21
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  moniker1825 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 22 16:07:37 2021
  InstallationDate: Installed on 2021-08-25 (58 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 20LB001FUS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-21-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-21-generic N/A
   linux-backports-modules-5.13.0-21-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2021
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N27ET43W (1.29 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LB001FUS
  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.ec.firmware.release: 1.15
  dmi.modalias: 
dmi:bvnLENOVO:bvrN27ET43W(1.29):bd08/13/2021:br1.29:efr1.15:svnLENOVO:pn20LB001FUS:pvrThinkPadP52s:rvnLENOVO:rn20LB001FUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20LB_BU_Think_FM_ThinkPadP52s:
  dmi.product.family: ThinkPad P52s
  dmi.product.name: 20LB001FUS
  dmi.product.sku: LENOVO_MT_20LB_BU_Think_FM_ThinkPad P52s
  dmi.product.version: ThinkPad P52s
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws/5.11.0.1021.22)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-aws (5.11.0.1021.22) for 
hirsute have finished running.
The following regressions have been reported in tests triggered by the package:

glibc/2.33-0ubuntu5 (arm64)
systemd/247.3-3ubuntu3.6 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/hirsute/update_excuses.html#linux-meta-aws

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1948504] [NEW] [Lenovo P52s] Unable to WiFi connect to Inseego Wavemaker 5G FX2000

[Christopher M . Peñalver]

Public bug reported:

1) lsb_release -rd
Description:Ubuntu 21.10
Release:21.10

2) uname -a
Linux worldpeacepc 5.13.0-21-generic #21-Ubuntu SMP Tue Oct 19 08:59:28 UTC 
2021 x86_64 x86_64 x86_64 GNU/Linux

3) What is expected to happen is when I click the top right hand side of
the GUI, choose the SSID associated with the Inseego Wavemaker 5G
FX2000, put in the known good password, it connects.

4) What happens instead is it fails to connect. Same problem in Ubuntu
21.04.

However, I'm able to connect to other SSIDs from other non-Inseego
devices. An iPhone 12 Mini and Windows 10 devices have no problems
connecting.

What I tried but it didn't change anything:
1) Disable ipv6 in Ubuntu.
2) In the Inseego GUI, change from:
5GHz 802.11acn/ax

to:
5GHz 802.11ac

WORKAROUND: In the Inseego GUI changing the WiFi security from:
WPA3/WPA2 Transition

to:
WPA2 Personal PSK (AES)

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-21-generic 5.13.0-21.21
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  moniker1825 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 22 16:07:37 2021
InstallationDate: Installed on 2021-08-25 (58 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: LENOVO 20LB001FUS
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-21-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-21-generic N/A
 linux-backports-modules-5.13.0-21-generic  N/A
 linux-firmware 1.201
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/13/2021
dmi.bios.release: 1.29
dmi.bios.vendor: LENOVO
dmi.bios.version: N27ET43W (1.29 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LB001FUS
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.ec.firmware.release: 1.15
dmi.modalias: 
dmi:bvnLENOVO:bvrN27ET43W(1.29):bd08/13/2021:br1.29:efr1.15:svnLENOVO:pn20LB001FUS:pvrThinkPadP52s:rvnLENOVO:rn20LB001FUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20LB_BU_Think_FM_ThinkPadP52s:
dmi.product.family: ThinkPad P52s
dmi.product.name: 20LB001FUS
dmi.product.sku: LENOVO_MT_20LB_BU_Think_FM_ThinkPad P52s
dmi.product.version: ThinkPad P52s
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug impish package-from-proposed

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

Title:
  [Lenovo P52s] Unable to  WiFi connect to Inseego Wavemaker 5G FX2000

Status in linux package in Ubuntu:
  New

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 21.10
  Release:  21.10

  2) uname -a
  Linux worldpeacepc 5.13.0-21-generic #21-Ubuntu SMP Tue Oct 19 08:59:28 UTC 
2021 x86_64 x86_64 x86_64 GNU/Linux

  3) What is expected to happen is when I click the top right hand side
  of the GUI, choose the SSID associated with the Inseego Wavemaker 5G
  FX2000, put in the known good password, it connects.

  4) What happens instead is it fails to connect. Same problem in Ubuntu
  21.04.

  However, I'm able to connect to other SSIDs from other non-Inseego
  devices. An iPhone 12 Mini and Windows 10 devices have no problems
  connecting.

  What I tried but it didn't change anything:
  1) Disable ipv6 in Ubuntu.
  2) In the Inseego GUI, change from:
  5GHz 802.11acn/ax

  to:
  5GHz 802.11ac

  WORKAROUND: In the Inseego GUI changing the WiFi security from:
  WPA3/WPA2 Transition

  to:
  WPA2 Personal PSK (AES)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-21-generic 5.13.0-21.21
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  moniker1825 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 22 16:07:37 2021
  InstallationDate: Installed on 2021-08-25 (58 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 20LB001FUS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

[Stefan Glorch]

I can also confirm that possibly the same bug occurs on my Lenovo ThinkPad L13 
Yoga (Intel i5-1135G7, Iris Xe), with kernel versions
5.13.0-20,
5.13.0-19 and
5.14.11 (mainline).
Starting the system using 5.11.0-37 or the patched 5.13.0-15 from earlier does 
not lead to said kernel panic.

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  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.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  TP-Link UB500 Bluetooth USB adapter not working properly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have just bought a Tp-link bluetooth 5.0 usb adapter (UB500). According to 
this website https://usb-ids.gowdy.us/read/UD/2357/0604 the chip is Realtek 
RTL8761B. 
  It works just fine on Windows 10, but I'm having problems on Ubuntu. 

  I'm running Ubuntu 21.10 with the 5.14.14-051414-generic kernel

  The adapter seems to be correctly installed and properly working,
  however scanning does not pick up any bluetooth device. I've tried two
  headsets (that I know are properly working) and my phone, with no
  success. When performing a scan on my phone, the computer doesn't show
  up, even if I've set it to visible.

  (I'm sorry if the information is not complete, but ubuntu-bug is not
  working for me)

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-kvm/5.4.0.1049.48)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-kvm (5.4.0.1049.48) for 
focal have finished running.
The following regressions have been reported in tests triggered by the package:

rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.3 (amd64)
v4l2loopback/0.12.3-1ubuntu0.4 (amd64)
oss4/4.2-build2010-5ubuntu6~20.04.3 (amd64)
evdi/1.9.1-1ubuntu4~20.04.1 (amd64)
sl-modem/2.9.11~20110321-16ubuntu1 (amd64)
glibc/2.31-0ubuntu9.2 (amd64)
dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64)
virtualbox/6.1.26-dfsg-3~ubuntu1.20.04.2 (amd64)
backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (amd64)
lttng-modules/2.12.5-1ubuntu2~20.04.1 (amd64)
rtl8821ce/5.5.2.1-0ubuntu4~20.04.4 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-kvm

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1948502] Re: TP-Link UB500 Bluetooth USB adapter not working properly

[gwendydd]

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

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

Title:
  TP-Link UB500 Bluetooth USB adapter not working properly

Status in linux package in Ubuntu:
  New

Bug description:
  I have just bought a Tp-link bluetooth 5.0 usb adapter (UB500). According to 
this website https://usb-ids.gowdy.us/read/UD/2357/0604 the chip is Realtek 
RTL8761B. 
  It works just fine on Windows 10, but I'm having problems on Ubuntu. 

  I'm running Ubuntu 21.10 with the 5.14.14-051414-generic kernel

  The adapter seems to be correctly installed and properly working,
  however scanning does not pick up any bluetooth device. I've tried two
  headsets (that I know are properly working) and my phone, with no
  success. When performing a scan on my phone, the computer doesn't show
  up, even if I've set it to visible.

  (I'm sorry if the information is not complete, but ubuntu-bug is not
  working for me)

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


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

[Kernel-packages] [Bug 1948502] [NEW] TP-Link UB500 Bluetooth USB adapter not working properly

[gwendydd]

Public bug reported:

I have just bought a Tp-link bluetooth 5.0 usb adapter (UB500). According to 
this website https://usb-ids.gowdy.us/read/UD/2357/0604 the chip is Realtek 
RTL8761B. 
It works just fine on Windows 10, but I'm having problems on Ubuntu. 

I'm running Ubuntu 21.10 with the 5.14.14-051414-generic kernel

The adapter seems to be correctly installed and properly working,
however scanning does not pick up any bluetooth device. I've tried two
headsets (that I know are properly working) and my phone, with no
success. When performing a scan on my phone, the computer doesn't show
up, even if I've set it to visible.

(I'm sorry if the information is not complete, but ubuntu-bug is not
working for me)

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

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/bugs/1948502/+attachment/5535315/+files/lspci-vnvn.log

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

Title:
  TP-Link UB500 Bluetooth USB adapter not working properly

Status in linux package in Ubuntu:
  New

Bug description:
  I have just bought a Tp-link bluetooth 5.0 usb adapter (UB500). According to 
this website https://usb-ids.gowdy.us/read/UD/2357/0604 the chip is Realtek 
RTL8761B. 
  It works just fine on Windows 10, but I'm having problems on Ubuntu. 

  I'm running Ubuntu 21.10 with the 5.14.14-051414-generic kernel

  The adapter seems to be correctly installed and properly working,
  however scanning does not pick up any bluetooth device. I've tried two
  headsets (that I know are properly working) and my phone, with no
  success. When performing a scan on my phone, the computer doesn't show
  up, even if I've set it to visible.

  (I'm sorry if the information is not complete, but ubuntu-bug is not
  working for me)

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-kvm/5.11.0.1019.20)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-kvm (5.11.0.1019.20) for 
hirsute have finished running.
The following regressions have been reported in tests triggered by the package:

rtl8821ce/5.5.2.1-0ubuntu6 (amd64)
dahdi-linux/1:2.11.1~dfsg-1ubuntu8 (amd64)
sl-modem/2.9.11~20110321-16ubuntu1 (amd64)
v4l2loopback/0.12.5-1ubuntu1 (amd64)
rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu14 (amd64)
lttng-modules/2.12.5-1ubuntu2~21.04.1 (amd64)
backport-iwlwifi-dkms/8613-0ubuntu2 (amd64)
oss4/4.2-build2010-5ubuntu8 (amd64)
systemd/247.3-3ubuntu3.6 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/hirsute/update_excuses.html#linux-meta-kvm

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1947829] Re: Cannot identified WLAN card MT7921 in Ubunut OS with Install OS complete first OOBE Boot OS

[Steve Langasek]

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into impish-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.201.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: linux-firmware (Ubuntu Impish)
   Status: In Progress => Fix Committed

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

Title:
  Cannot identified WLAN card MT7921 in Ubunut OS with Install OS
  complete first OOBE Boot OS

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  In Progress
Status in linux-firmware source package in Impish:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]

  Sometimes MT7921 may not be probed due to an endless mcu reset:

[ 5.789548] mt7921 mcu reset 0
[ 5.790625] mt7921 rx type 0x7
[ 5.790625] mt7921 eid 0x1 ext_eid 0x0
[ 5.790626] mt76_rx_event eid 0x1 ext_eid 0x0

  [Fix]

  WiFi and Bluetooth firmware updates from mainline:
  * e5a80ef8 linux-firmware: update frimware for mediatek bluetooth chip 
(MT7921)
  * d34196f5 linux-firmware: update firmware for MT7921 WiFi device

  [Test Case]

  This should fix the mcu reset and wireless/bluetooh devices should be
  probed successfully.

  [Where problems could occur]

  While there is explicit FW API for kernel version compatibility checking,
  this might introduce some hidden glitches that we don't know yet.

  [Other Info]

  MT7921 is supported since Impish 5.13 kernel, and Impish already has the
  latest Bluetooth firmware, so only the WiFi one is proposed. For oem-5.13
  and oem-5.14 in Focal, both firmware updates for Bluetooth and WiFi are
  required.

  == original bug report ==

  [Reproduce Steps]
  1.Add the wireless card MT7921 to SUT,Install the Ubuntu OS.
  2.During OOBE, Open the settings, there is no wireless settings in the 
panel,and the wifi cannot be used,issue occurred.

  [Results]
  Expected Result:The wireless settings should be exists and wifi can be used
  Actual Result:The wireless settings not exists and wifi can not be used

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1947829/+subscriptions


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oracle/5.11.0.1021.22)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-oracle (5.11.0.1021.22) for 
hirsute have finished running.
The following regressions have been reported in tests triggered by the package:

glibc/2.33-0ubuntu5 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/hirsute/update_excuses.html#linux-meta-oracle

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/5.4.0.1063.61)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-azure (5.4.0.1063.61) for 
focal have finished running.
The following regressions have been reported in tests triggered by the package:

lxc/1:4.0.6-0ubuntu1~20.04.1 (amd64)
dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64)
v4l2loopback/0.12.3-1ubuntu0.4 (amd64)
backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-azure

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1948351] Re: ppc64 BPF JIT mod by 1 will not return 0

[Thadeu Lima de Souza Cascardo]

** Description changed:

+ [Impact]
+ When doing MOD by 1 with a immediate/constant divisor on PPC, the JIT will 
produce code that returns the dividend, just like a division, instead of 0.
+ 
+ Both eBPF and cBPF will fail as well when doing such operations.
+ 
+ [Test case]
+ $ cat bpf-mod1.c
+ #include 
+ #include 
+ #include 
+ #include 
+ #include 
+ #include 
+ #include 
+ #include 
+ #include 
+ #include 
+ #include 
+ #include 
+ 
+ #define ARRAY_SIZE(array) (sizeof(array)/sizeof(array[0]))
+ 
+ static int pair[2];
+ 
+ static int attach()
+ {
+ int r;
+ 
+ struct sock_filter insn[] = {
+ { BPF_LD | BPF_W | BPF_ABS, 0, 0, 0 },
+ { BPF_ALU | BPF_MOD, 0, 0, 1 },
+ { BPF_RET | BPF_A, 0, 0, 0 },
+ };
+ 
+ struct sock_fprog prog = {};
+ prog.filter = insn;
+ prog.len = ARRAY_SIZE(insn);
+ 
+ socketpair(AF_UNIX, SOCK_DGRAM, 0, pair);
+ setsockopt(pair[1], SOL_SOCKET, SO_ATTACH_FILTER, &prog, 
sizeof(prog));
+ return 0;
+ }
+ 
+ int main(int argc, char **argv)
+ {
+ int buf[5];
+ int r;
+ r = attach();
+ if (r < 0) {
+ err(1, "function will error out already");
+ }
+ write(pair[0], "hello", 5);
+ r = recv(pair[1], buf, 5, MSG_DONTWAIT);
+ if (r != -1 || errno != EAGAIN) {
+ err(1, "program failed");
+ }
+ return 0;
+ }
+ $ gcc -o bpf-mod1 bpf-mod1.c
+ $ ./bpf-mod1
+ cbpf-mod1: program failed: Success
+ 
+ After fix:
+ $ ./bpf-mod1
+ $ echo $?
+ 0
+ 
+ [Potential regression]
+ BPF programs might be misbehave on ppc64el.
+ 
+ 
+ 
  This is a scripted bug report about ADT failures while running linux
  tests for linux/5.4.0-90.101 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be determined.
- 
  
  Consistently failing on Focal/linux 5.4.0-90.101
  
  13:15:26 DEBUG| [stdout] # selftests: net: test_bpf.sh
  13:15:27 DEBUG| [stdout] # test_bpf: [FAIL]
  13:15:27 DEBUG| [stdout] not ok 9 selftests: net: test_bpf.sh # exit=1
  
- 
  Testing failed on:
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20211021_141544_eda49@/log.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/1948351

Title:
  ppc64 BPF JIT mod by 1 will not return 0

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  New

Bug description:
  [Impact]
  When doing MOD by 1 with a immediate/constant divisor on PPC, the JIT will 
produce code that returns the dividend, just like a division, instead of 0.

  Both eBPF and cBPF will fail as well when doing such operations.

  [Test case]
  $ cat bpf-mod1.c
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  #define ARRAY_SIZE(array) (sizeof(array)/sizeof(array[0]))

  static int pair[2];

  static int attach()
  {
  int r;

  struct sock_filter insn[] = {
  { BPF_LD | BPF_W | BPF_ABS, 0, 0, 0 },
  { BPF_ALU | BPF_MOD, 0, 0, 1 },
  { BPF_RET | BPF_A, 0, 0, 0 },
  };

  struct sock_fprog prog = {};
  prog.filter = insn;
  prog.len = ARRAY_SIZE(insn);

  socketpair(AF_UNIX, SOCK_DGRAM, 0, pair);
  setsockopt(pair[1], SOL_SOCKET, SO_ATTACH_FILTER, &prog, 
sizeof(prog));
  return 0;
  }

  int main(int argc, char **argv)
  {
  int buf[5];
  int r;
  r = attach();
  if (r < 0) {
  err(1, "function will error out already");
  }
  write(pair[0], "hello", 5);
  r = recv(pair[1], buf, 5, MSG_DONTWAIT);
  if (r != -1 || errno != EAGAIN) {
  err(1, "program failed");
  }
  return 0;
  }
  $ gcc -o bpf-mod1 bpf-mod1.c
  $ ./bpf-mod1
  cbpf-mod1: program failed: Success

  After fix:
  $ ./bpf-mod1
  $ echo $?
  0

  [Potential regression]
  BPF programs might be misbehave on ppc64el.

  

  This is a scripted bug report about ADT failures while running linux
  tests for linux/5.4.0-90.101 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Consistently failing on Focal/linux 5.4.0-90.101

  13:15:26 DEBUG| [stdout] # selftests: net: test_bpf.sh
  13:15:27 DEBUG| [stdout] # test_bpf: [FAIL]
  13:15:27 DEBUG| [stdout] not ok 9 selftests: net: test_bpf.sh # exit=1

  Testing failed on:
  ppc64el: 
https://autopkgtest.ubuntu.com/resul

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure-5.4/5.4.0.1063.43)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-azure-5.4 (5.4.0.1063.43) 
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

v4l2loopback/0.10.0-1ubuntu1.2 (amd64)
lxc/3.0.3-0ubuntu1~18.04.1 (amd64)
kpatch/0.5.0-0ubuntu1.1 (amd64)
dahdi-linux/1:2.11.1~dfsg-1ubuntu4.2 (amd64)
asic0x/1.0.1-1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-meta-azure-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure-5.11/5.11.0.1020.21~20.04.20)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-azure-5.11 
(5.11.0.1020.21~20.04.20) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

glibc/2.31-0ubuntu9.2 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-azure-5.11

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1929923] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From boris.m...@de.ibm.com 2021-10-22 14:34 EDT---
Problem doesn't occur on the latest supported Ubuntu level, hence closing the 
bug.
BZ status change:->REJECTED / UNREPRODUCIBLE

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

Title:
  [UBUNTU 20.04] LPAR becomes unresponsive after the Kernel panic -
  rq_qos_wake_function

Status in Ubuntu on IBM z Systems:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  ---Problem Description---
  kernel panic rq_qos_wake_function
   
  ---uname output---
  Linux version 5.4.0-71-generic
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  Stack trace output:
   May 15 20:21:04 data1 kernel: Call Trace:
  May 15 20:21:04 data1 kernel: ([<00234091e670>] 0x234091e670)
  May 15 20:21:04 data1 kernel:  [<003e10047e3a>] 
rq_qos_wake_function+0x8a/0xa0 
  May 15 20:21:04 data1 kernel:  [<003e0fbec482>] 
__wake_up_common+0xa2/0x1b0 
  May 15 20:21:04 data1 kernel:  [<003e0fbec984>] 
__wake_up_common_lock+0x94/0xe0 
  May 15 20:21:04 data1 kernel:  [<003e0fbec9fa>] __wake_up+0x2a/0x40 
  May 15 20:21:04 data1 kernel:  [<003e1005ee70>] wbt_done+0x90/0xe0 
  May 15 20:21:04 data1 kernel:  [<003e10047f42>] __rq_qos_done+0x42/0x60 
  May 15 20:21:04 data1 kernel:  [<003e10033cb0>] 
blk_mq_free_request+0xe0/0x140 
  May 15 20:21:04 data1 kernel:  [<003e101d46f0>] 
dm_softirq_done+0x140/0x230 
  May 15 20:21:04 data1 kernel:  [<003e100326c0>] 
blk_done_softirq+0xc0/0xe0 
  May 15 20:21:04 data1 kernel:  [<003e103fc084>] __do_softirq+0x104/0x360 
  May 15 20:21:04 data1 kernel:  [<003e0fb9da1e>] irq_exit+0x9e/0xc0 
  May 15 20:21:04 data1 kernel:  [<003e0fb28ae8>] do_IRQ+0x78/0xb0 
  May 15 20:21:04 data1 kernel:  [<003e103fb588>] 
ext_int_handler+0x130/0x134 
  May 15 20:21:04 data1 kernel:  [<003e101d4416>] dm_mq_queue_rq+0x36/0x1d0 
  May 15 20:21:04 data1 kernel: Last Breaking-Event-Address:
  May 15 20:21:04 data1 kernel:  [<003e0fbce75e>] wake_up_process+0xe/0x20
  May 15 20:21:04 data1 kernel: Kernel panic - not syncing: Fatal exception in 
interrupt
   
  Oops output:
   no
   
  System Dump Info:
The system was configured to capture a dump, however a dump was not 
produced.

  -Attach sysctl -a output output to the bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929923/+subscriptions


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/5.11.0.40.41)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta (5.11.0.40.41) for hirsute 
have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/247.3-3ubuntu3.6 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/hirsute/update_excuses.html#linux-meta

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1948485] [NEW] Impish update: upstream stable patchset 2021-10-22

[Kamal Mostafa]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   upstream stable patchset 2021-10-22

Ported from the following upstream stable releases:
v5.10.68, v5.14.7

   from git://git.kernel.org/

xen: reset legacy rtc flag for PV domU
arm64/sve: Use correct size when reinitialising SVE state
PM: base: power: don't try to use non-existing RTC for storing data
PCI: Add AMD GPU multi-function power dependencies
drm/amd/amdgpu: Increase HWIP_MAX_INSTANCE to 10
drm/etnaviv: return context from etnaviv_iommu_context_get
drm/etnaviv: put submit prev MMU context when it exists
drm/etnaviv: stop abusing mmu_context as FE running marker
drm/etnaviv: keep MMU context across runtime suspend/resume
drm/etnaviv: exec and MMU state is lost when resetting the GPU
drm/etnaviv: fix MMU context leak on GPU reset
drm/etnaviv: reference MMU context when setting up hardware state
drm/etnaviv: add missing MMU context put when reaping MMU mapping
s390/sclp: fix Secure-IPL facility detection
x86/pat: Pass valid address to sanitize_phys()
x86/mm: Fix kern_addr_valid() to cope with existing but not present entries
tipc: fix an use-after-free issue in tipc_recvmsg
ethtool: Fix rxnfc copy to user buffer overflow
net/{mlx5|nfp|bnxt}: Remove unnecessary RTNL lock assert
net-caif: avoid user-triggerable WARN_ON(1)
ptp: dp83640: don't define PAGE0
net/l2tp: Fix reference count leak in l2tp_udp_recv_core
r6040: Restore MDIO clock frequency after MAC reset
tipc: increase timeout in tipc_sk_enqueue()
drm/rockchip: cdn-dp-core: Make cdn_dp_core_resume __maybe_unused
perf machine: Initialize srcline string member in add_location struct
net/mlx5: FWTrace, cancel work on alloc pd error flow
net/mlx5: Fix potential sleeping in atomic context
nvme-tcp: fix io_work priority inversion
events: Reuse value read using READ_ONCE instead of re-reading it
net: ipa: initialize all filter table slots
gen_compile_commands: fix missing 'sys' package
vhost_net: fix OoB on sendmsg() failure.
net/af_unix: fix a data-race in unix_dgram_poll
net: dsa: destroy the phylink instance on any error in dsa_slave_phy_setup
x86/uaccess: Fix 32-bit __get_user_asm_u64() when CC_HAS_ASM_GOTO_OUTPUT=y
tcp: fix tp->undo_retrans accounting in tcp_sacktag_one()
selftest: net: fix typo in altname test
qed: Handle management FW error
udp_tunnel: Fix udp_tunnel_nic work-queue type
dt-bindings: arm: Fix Toradex compatible typo
ibmvnic: check failover_pending in login response
KVM: PPC: Book3S HV: Tolerate treclaim. in fake-suspend mode changing registers
bnxt_en: make bnxt_free_skbs() safe to call after bnxt_free_mem()
net: hns3: pad the short tunnel frame before sending to hardware
net: hns3: change affinity_mask to numa node range
net: hns3: disable mac in flr process
net: hns3: fix the timing issue of VF clearing interrupt sources
dt-bindings: mtd: gpmc: Fix the ECC bytes vs. OOB bytes equation
mfd: db8500-prcmu: Adjust map to reality
PCI: Add ACS quirks for NXP LX2xx0 and LX2xx2 platforms
fuse: fix use after free in fuse_read_interrupt()
PCI: tegra194: Fix handling BME_CHGED event
PCI: tegra194: Fix MSI-X programming
PCI: tegra: Fix OF node reference leak
mfd: Don't use irq_create_mapping() to resolve a mapping
PCI: rcar: Fix runtime PM imbalance in rcar_pcie_ep_probe()
tracing/probes: Reject events which have the same name of existing one
PCI: cadence: Use bitfield for *quirk_retrain_flag* instead of bool
PCI: cadence: Add quirk flag to set minimum delay in LTSSM Detect.Quiet state
PCI: j721e: Add PCIe support for J7200
PCI: j721e: Add PCIe support for AM64
PCI: Add ACS quirks for Cavium multi-function devices
watchdog: Start watchdog in watchdog_set_last_hw_keepalive only if appropriate
octeontx2-af: Add additional register check to rvu_poll_reg()
Set fc_nlinfo in nh_create_ipv4, nh_create_ipv6
net: usb: cdc_mbim: avoid altsetting toggling for Telit LN920
PCI: ibmphp: Fix double unmap of io_mem
ethtool: Fix an error code in cxgb2.c
NTB: Fix an error code in ntb_msit_probe()
NTB: perf: Fix an error code in perf_setup_inbuf()
mfd: axp20x: Update AXP288 volatile ranges
backlight: ktd253: Stabilize backlight
PCI: of: Don't fail devm_pci_alloc_host_bridge() on missing 'ranges'
PCI: iproc: Fix BCMA probe resource handling
netfilter: nft_ct: protect nft_ct_pcpu_template_refcnt with mutex
KVM: arm64: Restrict IPA size to maximum 48 bits on 4K and 16K page size
PCI: Fix pci_dev_str_match_path() alloc while atomic bug
mfd: tqmx86: Clear GPIO IRQ resource when no IRQ is set
tracing/boot: Fix a hist trigger dependency for boot time tra

[Kernel-packages] [Bug 1942784] Re: makedumpfile not properly working on focal with 5.11 kernel

[Ioanna Alifieraki]

New debdiff for focal.

** Patch added: "lp1942784_focal.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+attachment/5535296/+files/lp1942784_focal.debdiff

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

Title:
  makedumpfile not properly working on focal with 5.11 kernel

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Focal:
  In Progress
Status in makedumpfile source package in Hirsute:
  In Progress

Bug description:
  [IMPACT]

  When running Focal with the hwe 5.11 kernel makedumpfile is not working as it 
should.
  Instead of compressing the dump makedumpfile falls back to cp.
  This can create problems on systems with very large RAM and result into 
exhausting all storage on the host.
  This can be resolved with upstream commit f1197543d1c4 ([PATCH] Retrieve 
MAX_PHYSMEM_BITS from vmcoreinfo).
  The reason for falling back to cp is that without this patch makedumpfile 
calculates wrongly the memory layout.
  This happens after the kernel commit 1d50e5d0c505 ("crash_core, vmcoreinfo: 
Append 'MAX_PHYSMEM_BITS'to vmcoreinfo").
  With this commit applied, reading MAX_PHYSMEM_BITS from vmcoreinfo instead of 
inferring lead to correctly detecting the memory layout and creating the dump 
file properly. 

  In addition the dmesg. is not created.
  This can be resolved with the following two commits  :
  - commit c617ec633392([PATCH 1/2] printk: add support for lockless ringbuffer)
  - commit 44b073b7ec46([PATCH 2/2] printk: use committed/finalized state 
values)

  [TEST CASE]

  For testing a machine running focal with the 5.11 kernel is required.
  Then trigger a crash.
  On the console we can see that makedumpfile fails and `falls back to cp`.
  In /var/crash we can see that no dmesg file is created and instead of the 
dump file
  the uncompressed vmcoreinfo is created.

  [WHERE PROBLEMS COULD OCCUR]

  The 3 commits pulled into focal make makedumpfile compatible with the 5.11 
kernel.
  Any regression potential would involve the crash dump not being created after 
a crash in case kdump is configured.

  [OTHER]

  Only Focal with 5.11 kernel is affected.

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


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

[Kernel-packages] [Bug 1948351] Re: ppc64 BPF JIT mod by 1 will not return 0

[Thadeu Lima de Souza Cascardo]

** Also affects: linux (Ubuntu Hirsute)
   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/1948351

Title:
  ppc64 BPF JIT mod by 1 will not return 0

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  New

Bug description:
  This is a scripted bug report about ADT failures while running linux
  tests for linux/5.4.0-90.101 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  
  Consistently failing on Focal/linux 5.4.0-90.101

  13:15:26 DEBUG| [stdout] # selftests: net: test_bpf.sh
  13:15:27 DEBUG| [stdout] # test_bpf: [FAIL]
  13:15:27 DEBUG| [stdout] not ok 9 selftests: net: test_bpf.sh # exit=1

  
  Testing failed on:
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20211021_141544_eda49@/log.gz

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


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

[Kernel-packages] [Bug 1948044] Re: charon-systemd fails on raspberry pi systems under ubuntu 21.10

[Paride Legovini]

Indeed xfrm_user.ko is missing from the Impish image
(ubuntu-21.10-preinstalled-server-arm64+raspi.img), while it's present
in the Focal one (ubuntu-20.04.3-preinstalled-server-arm64+raspi.img).
I'm adding a kernel task to this bug report.

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

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

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

Title:
  charon-systemd fails on raspberry pi systems under ubuntu 21.10

Status in linux-raspi package in Ubuntu:
  New
Status in strongswan package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 21.10 from Ubuntu 21.04 my Strongswan
  installation fails. It seems that charon-systemd can´t be started. The
  problem occurs also when using a fresh install of the offical Ubuntu
  Server 21.10 image (from ).

  The problem doesn't exist on a VM running on an AMD64 system.

  I attach the output of journalctl -xeu strongswan.service (after
  increasing charons loglevel to 2).

  Kind regards
  Sven

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: charon-systemd 5.9.1-1ubuntu3.1
  ProcVersionSignature: Ubuntu 5.13.0-1008.9-raspi 5.13.14
  Uname: Linux 5.13.0-1008-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Thu Oct 21 11:54:32 2021
  ProcEnviron:
   SHELL=/bin/bash
   LANG=C.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: strongswan
  UpgradeStatus: Upgraded to impish on 2021-10-19 (2 days ago)

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


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

[Kernel-packages] [Bug 1946266] Re: Add psample tunnel support and also two fixes for psample issues.

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-focal

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

Title:
  Add psample tunnel support and also two fixes for psample issues.

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Focal:
  Fix Committed

Bug description:
  * Explain the bug(s)
  Fix psample compilation issue and add tunnel support

  * brief explanation of fixes
  Enhance psample

  * How to test
  Add tc rule with tunnel and sample actions and run traffic. Verify sample 
traffic on the sample interface.

  * What it could break.
  psample could be broke as new function is enabled

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


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

[Kernel-packages] [Bug 1944390] Re: Fix ignoring ct state match of OVS offload to TC/HW

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-focal

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

Title:
  Fix ignoring ct state match of OVS offload to TC/HW

Status in linux-bluefield package in Ubuntu:
  New
Status in linux-bluefield source package in Focal:
  Fix Committed

Bug description:
  * Explain the bug
   
  When using OVS with tc to offload connection tracking flows, if user matches 
on ct_state other then trk and est, such as ct_state +rpl, it will be silently 
ignored by TC/HW and might result in wrong actions being executed.
   
  * How to test
   
  Create OVS bridge with 2 devices $dev1, $dev2 (can be any devices)
  Enable HW offload and configure connection tracking OpenFlow rules which match
  on ct_state +rpl and do different actions based on that match.

  e.g:
  ovs-ofctl del-flows br-ovs
  ovs-ofctl add-flow br-ovs arp,actions=normal
  ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)"
  ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new 
actions=ct(commit),normal"
  ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est-rpl, 
actions=$dev1"
  ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est+rpl, 
actions=$dev2"

  With commits, ovs dump-flows (or tc show on devs) will have ct_state +rpl 
match, and without they don't have,
  meaning the match is ignored.
   
  * What it could break.

  NA

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


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

[Kernel-packages] [Bug 1946393] Re: Fix byte count on fragmented packets in tc ct action

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-focal

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

Title:
  Fix byte count on fragmented packets in tc ct action

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Focal:
  Fix Committed

Bug description:
  * Explain the bug
   
  First fragmented packets (frag offset = 0) byte len is zeroed 
  when stolen by ip_defrag(). And since act_ct update the stats
  only afterwards (at end of execute), bytes aren't correctly
  accounted for such packets. 
   
  * How to test
   
  Create OVS bridge with 2 devices $dev1, $dev2 (can be any devices)
  Enable HW offload and configure connection tracking OpenFlow rules as below
  e.g:
  ovs-ofctl del-flows br-ovs
  ovs-ofctl add-flow br-ovs arp,actions=normal
  ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)"
  ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new 
actions=ct(commit),normal"
  ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal"

  Run fragmented icmp ping traffic (e.g ping -s 2000)

  dump ovs rules (ovs-appctl dpctl/dump-flows), observe byte count on 
frag=first rule:
  
ct_state(-trk),recirc_id(0),in_port(2),eth_type(0x0800),ipv4(proto=1,frag=first),
 packets:10, bytes:13960, used:1.370s, actions:ct(zone=1),recirc(0x1)

  bytes would be zero if bug occurs.

  * What it could break.
   
  NA

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


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

[Kernel-packages] [Bug 1948470] Re: aufs: kernel bug with apparmor and fuseblk

[Mauricio Faria de Oliveira]

[H/F/B][PATCH 0/1] aufs: fix kernel bug with apparmor and fuseblk
https://lists.ubuntu.com/archives/kernel-team/2021-October/125163.html

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

Title:
  aufs: kernel bug with apparmor and fuseblk

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  In Progress
Status in linux source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Invalid

Bug description:
  [Impact]

   * AppArmor-enabled applications on the aufs filesystem
     might hit a kernel bug when getting file attributes.

   * The aufs filesystem explicitly assigns a NULL pointer
     to `struct path.mnt` for `vfs_getattr()`, which calls
     into AppArmor that checks `struct path.mnt->mnt_flags`,
     triggering a kernel NULL pointer dereference.

   * This is almost 10 years old [1,2], reproducible w/ the
     Linux v3.2 kernel, but it's rare as apparently it needs
     a fuseblk mount as an aufs branch, and file creation/
     open (O_CREAT), with a filename that exists only in a
     lower aufs branch. On Linux v5.15-rc* it doesn't need
     AppArmor anymore.

  [Fix]

   * The patch fixing this issue does set `struct path.mnt`
     properly, by taking `struct path` as parameter instead
     of just `struct dentry` (and making up an incomplete
     `struct path` w/ that `dentry` and `mnt = NULL`.)

   * Since it changes the signature of a key, leaf function
     with several callers, the patch is a bit long/refactor,
     but it has been tested by the upstream aufs maintainer
     with a private test-suite.

  [Test Plan]

   * Synthetic reproducer available in [1] and comment #1.

  [Regression Potential]

   * Regressions would probably manifest as kernel errors
     mostly in the lookup and open paths, but more subtle
     manifestations would be possible as well.

   * The patch modifies a fair number of functions, even if
     doing so in simple ways. The synthetic reproducer only
     covers one of those functions.

   * The other code paths have been tested by the maintainer
     w/ the mainline kernel, and should be equivalent to our
     kernel as none of such changed for cherry-pick/backport.

   * The upstream aufs maintainer runs a private test suite
     that covers several features and use cases of aufs, so
     hopefully that provides some relief to take this patch.

  [Other Info]

   * Impish no longer ships aufs; no fix needed.
   * Hirsute/Focal/Bionic do/need it. (H only for backports)
   * Hirsute/Focal are clean cherry-picks.
   * Bionic is a trivial backport.

  [1] https://sourceforge.net/p/aufs/mailman/message/37363599/
  [2] 
https://unix.stackexchange.com/questions/324571/docker-run-causing-kernel-panic

  [Kernel Traces]

  BUG: kernel NULL pointer dereference, address: 0010
  ...
  CPU: 23 PID: 17623 Comm: drone-agent Not tainted 5.4.0-1058-azure 
#60~18.04.1-Ubuntu
  Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 
090008 12/07/2018
  RIP: 0010:aa_path_name+0x55/0x370
  ...
  Call Trace:
  ? request_wait_answer+0xc4/0x200
  path_name+0x60/0xe0
  profile_path_perm.part.9+0x57/0xa0
  aa_path_perm+0xe2/0x130
  common_perm+0x59/0x130
  common_perm_cond+0x4c/0x70
  apparmor_inode_getattr+0x1d/0x20
  security_inode_getattr+0x35/0x50
  vfs_getattr+0x21/0x40
  vfsub_update_h_iattr+0x95/0xb0 [aufs]
  ? lookup_dcache+0x44/0x70
  ? lookup_one_len+0x66/0x90
  vfsub_lookup_one_len+0x50/0x70 [aufs]
  au_sio_lkup_one+0x8e/0xa0 [aufs]
  au_lkup_dentry+0x3fa/0x660 [aufs]
  aufs_lookup.part.35+0x11c/0x210 [aufs]
  aufs_atomic_open+0xec/0x3c0 [aufs]
  path_openat+0xe30/0x16a0
  ? aufs_lookup+0x30/0x30 [aufs]
  ? path_openat+0xe30/0x16a0
  ? unlock_page_memcg+0x12/0x20
  ? filemap_map_pages+0x17d/0x3b0
  do_filp_open+0x9b/0x110
  ? __check_object_size+0xdb/0x1b0
  ? __alloc_fd+0xb2/0x170
  do_sys_open+0x1ba/0x2e0
  ? do_sys_open+0x1ba/0x2e0
  __x64_sys_openat+0x20/0x30
  do_syscall_64+0x5e/0x200
  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  RIP: 0033:0x4a06fa

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


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

[Kernel-packages] [Bug 1947453] Re: [amdgpu] wayland black screen with white flashes, display corruption, kernel 5.13

[Bug Watch Updater]

Launchpad has imported 5 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=213779.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2021-07-18T23:18:34+00:00 alex14641 wrote:

If I close my laptop lid and reopen it, the screen stays blank.
Reverting the following commit fixes the issue:

commit 9127daa0a8d88a6e6452eb8b7c9be4c3f42a867e
Author: Stylon Wang 
Date:   Tue Mar 2 19:25:56 2021 +0800

drm/amd/display: Guard ASSR with internal display flag

[Why]
ASSR enabling only considers capability declared in DPCD.
We also need to check whether the connector is internal.

[How]
ASSR enabling need to check both DPCD capability and internal display
flag.

Signed-off-by: Stylon Wang 
Reviewed-by: Harry Wentland 
Acked-by: Anson Jacob 
Tested-by: Dan Wheeler 
Signed-off-by: Alex Deucher 

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947453/comments/0


On 2021-07-18T23:20:03+00:00 alex14641 wrote:

The graphics card is a RX580.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947453/comments/1


On 2021-07-19T14:53:43+00:00 alexdeucher wrote:

Can you try the patch here:
https://gitlab.freedesktop.org/drm/amd/-/issues/1620

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947453/comments/2


On 2021-07-20T12:27:31+00:00 alex14641 wrote:

That patch works.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947453/comments/3


On 2021-07-28T04:49:50+00:00 alexdeucher wrote:

Fix is in 5.14 and should land in stable shortly:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6be50f5d83adc9541de3d5be26e968182b5ac150

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947453/comments/4


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => High

** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1620
   https://gitlab.freedesktop.org/drm/amd/-/issues/1620

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

Title:
  [amdgpu] wayland black screen with white flashes, display corruption,
  kernel 5.13

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

Bug description:
  After upgrade from ubuntu 21.04 to ubuntu 21.10 I am seeing black
  screen in wayland session and screen corruption in Xorg session

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 16 15:49:45 2021
  DistUpgraded: 2021-10-16 08:19:20,349 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev da) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1043:1b70]
  InstallationDate: Installed on 2020-11-20 (329 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: ASUSTeK COMPUTER INC. X505BA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro iommu=soft quiet splash 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago)
  dmi.bios.date: 04/02/2020
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X505BA.317
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X505BA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.

[Kernel-packages] [Bug 1948470] Re: aufs: kernel bug with apparmor and fuseblk

[Mauricio Faria de Oliveira]

Test with bionic-proposed (4.15.0-162.170)
---

Original:

# ../openat
Killed

[  442.526300] BUG: unable to handle kernel NULL pointer dereference at 
0010
...
[  442.539854] CPU: 1 PID: 5644 Comm: openat Not tainted 4.15.0-162-generic 
#170-Ubuntu
[  442.540733] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.13.0-1ubuntu1.1 04/01/2014
[  442.541755] RIP: 0010:aa_path_name+0x55/0x370
...
[  442.549808] Call Trace:
[  442.550211]  path_name+0x60/0xe0
[  442.550687]  profile_path_perm.part.7+0x57/0xa0
[  442.551293]  aa_path_perm+0xe2/0x130
[  442.551819]  common_perm+0x59/0x130
[  442.552323]  common_perm_cond+0x4c/0x70
[  442.552856]  apparmor_inode_getattr+0x1d/0x20
[  442.553444]  security_inode_getattr+0x47/0x60
[  442.554038]  vfs_getattr+0x21/0x40
[  442.554538]  vfsub_update_h_iattr+0x95/0xb0 [aufs]
[  442.555172]  ? __lookup_hash+0x22/0xa0
[  442.555697]  ? lookup_one_len+0x113/0x120
[  442.556323]  vfsub_lookup_one_len+0x50/0x70 [aufs]
[  442.557065]  au_wh_test+0x25/0xe0 [aufs]
[  442.557615]  au_lkup_dentry+0x484/0x620 [aufs]
[  442.558225]  aufs_lookup.part.33+0x11c/0x210 [aufs]
[  442.562787]  aufs_atomic_open+0x102/0x3b0 [aufs]
[  442.563427]  ? aufs_permission+0x190/0x2d0 [aufs]
[  442.564098]  ? __inode_permission+0x5b/0x160
[  442.564689]  path_openat+0xde1/0x18b0
[  442.565214]  ? path_openat+0xde1/0x18b0
[  442.565756]  do_filp_open+0x9b/0x110
[  442.566266]  ? __check_object_size+0xc8/0x1b0
[  442.566862]  ? __alloc_fd+0xb2/0x170
[  442.567376]  do_sys_open+0x1ba/0x2c0
[  442.567908]  ? do_sys_open+0x1ba/0x2c0
[  442.568453]  SyS_openat+0x14/0x20
[  442.568939]  do_syscall_64+0x73/0x130
[  442.569458]  entry_SYSCALL_64_after_hwframe+0x41/0xa6
[  442.570117] RIP: 0033:0x7f079564af83


Patched:

# ../openat
# echo $?
0

# uname -rv
4.15.0-162-generic #170+test20211022b1 SMP Fri Oct 22 10:59:39 -03 2021

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

Title:
  aufs: kernel bug with apparmor and fuseblk

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  In Progress
Status in linux source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Invalid

Bug description:
  [Impact]

   * AppArmor-enabled applications on the aufs filesystem
     might hit a kernel bug when getting file attributes.

   * The aufs filesystem explicitly assigns a NULL pointer
     to `struct path.mnt` for `vfs_getattr()`, which calls
     into AppArmor that checks `struct path.mnt->mnt_flags`,
     triggering a kernel NULL pointer dereference.

   * This is almost 10 years old [1,2], reproducible w/ the
     Linux v3.2 kernel, but it's rare as apparently it needs
     a fuseblk mount as an aufs branch, and file creation/
     open (O_CREAT), with a filename that exists only in a
     lower aufs branch. On Linux v5.15-rc* it doesn't need
     AppArmor anymore.

  [Fix]

   * The patch fixing this issue does set `struct path.mnt`
     properly, by taking `struct path` as parameter instead
     of just `struct dentry` (and making up an incomplete
     `struct path` w/ that `dentry` and `mnt = NULL`.)

   * Since it changes the signature of a key, leaf function
     with several callers, the patch is a bit long/refactor,
     but it has been tested by the upstream aufs maintainer
     with a private test-suite.

  [Test Plan]

   * Synthetic reproducer available in [1] and comment #1.

  [Regression Potential]

   * Regressions would probably manifest as kernel errors
     mostly in the lookup and open paths, but more subtle
     manifestations would be possible as well.

   * The patch modifies a fair number of functions, even if
     doing so in simple ways. The synthetic reproducer only
     covers one of those functions.

   * The other code paths have been tested by the maintainer
     w/ the mainline kernel, and should be equivalent to our
     kernel as none of such changed for cherry-pick/backport.

   * The upstream aufs maintainer runs a private test suite
     that covers several features and use cases of aufs, so
     hopefully that provides some relief to take this patch.

  [Other Info]

   * Impish no longer ships aufs; no fix needed.
   * Hirsute/Focal/Bionic do/need it. (H only for backports)
   * Hirsute/Focal are clean cherry-picks.
   * Bionic is a trivial backport.

  [1] https://sourceforge.net/p/aufs/mailman/message/37363599/
  [2] 
https://unix.stackexchange.com/questions/324571/docker-run-causing-kernel-panic

  [Kernel Traces]

  BUG: kernel NULL pointer dereference, address: 0010
  ...
  CPU: 23 PID: 17623 Comm: drone-agent Not tainted 5.4.0-1058-azure 
#60~18.04.1-Ubuntu
  Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 
090008 12/07/2018
  RIP: 

[Kernel-packages] [Bug 1948470] Re: aufs: kernel bug with apparmor and fuseblk

[Mauricio Faria de Oliveira]

Hirsute doesn't ship aufs anymore; no testing needed, just patching.

commit 4fb9ce7538c89f81e3fa5bfae881c9b49e7137e0
Author: Seth Forshee 
Date:   Fri Feb 19 14:46:24 2021 -0600

UBUNTU: [Config] CONFIG_AUFS_FS=n

We're keeping aufs in the source tree for backports but disabling
it starting in hirsute. Update the configs and annotations
accordingly.

Signed-off-by: Seth Forshee 

** Tags added: sts

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

Title:
  aufs: kernel bug with apparmor and fuseblk

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  In Progress
Status in linux source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Invalid

Bug description:
  [Impact]

   * AppArmor-enabled applications on the aufs filesystem
     might hit a kernel bug when getting file attributes.

   * The aufs filesystem explicitly assigns a NULL pointer
     to `struct path.mnt` for `vfs_getattr()`, which calls
     into AppArmor that checks `struct path.mnt->mnt_flags`,
     triggering a kernel NULL pointer dereference.

   * This is almost 10 years old [1,2], reproducible w/ the
     Linux v3.2 kernel, but it's rare as apparently it needs
     a fuseblk mount as an aufs branch, and file creation/
     open (O_CREAT), with a filename that exists only in a
     lower aufs branch. On Linux v5.15-rc* it doesn't need
     AppArmor anymore.

  [Fix]

   * The patch fixing this issue does set `struct path.mnt`
     properly, by taking `struct path` as parameter instead
     of just `struct dentry` (and making up an incomplete
     `struct path` w/ that `dentry` and `mnt = NULL`.)

   * Since it changes the signature of a key, leaf function
     with several callers, the patch is a bit long/refactor,
     but it has been tested by the upstream aufs maintainer
     with a private test-suite.

  [Test Plan]

   * Synthetic reproducer available in [1] and comment #1.

  [Regression Potential]

   * Regressions would probably manifest as kernel errors
     mostly in the lookup and open paths, but more subtle
     manifestations would be possible as well.

   * The patch modifies a fair number of functions, even if
     doing so in simple ways. The synthetic reproducer only
     covers one of those functions.

   * The other code paths have been tested by the maintainer
     w/ the mainline kernel, and should be equivalent to our
     kernel as none of such changed for cherry-pick/backport.

   * The upstream aufs maintainer runs a private test suite
     that covers several features and use cases of aufs, so
     hopefully that provides some relief to take this patch.

  [Other Info]

   * Impish no longer ships aufs; no fix needed.
   * Hirsute/Focal/Bionic do/need it. (H only for backports)
   * Hirsute/Focal are clean cherry-picks.
   * Bionic is a trivial backport.

  [1] https://sourceforge.net/p/aufs/mailman/message/37363599/
  [2] 
https://unix.stackexchange.com/questions/324571/docker-run-causing-kernel-panic

  [Kernel Traces]

  BUG: kernel NULL pointer dereference, address: 0010
  ...
  CPU: 23 PID: 17623 Comm: drone-agent Not tainted 5.4.0-1058-azure 
#60~18.04.1-Ubuntu
  Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 
090008 12/07/2018
  RIP: 0010:aa_path_name+0x55/0x370
  ...
  Call Trace:
  ? request_wait_answer+0xc4/0x200
  path_name+0x60/0xe0
  profile_path_perm.part.9+0x57/0xa0
  aa_path_perm+0xe2/0x130
  common_perm+0x59/0x130
  common_perm_cond+0x4c/0x70
  apparmor_inode_getattr+0x1d/0x20
  security_inode_getattr+0x35/0x50
  vfs_getattr+0x21/0x40
  vfsub_update_h_iattr+0x95/0xb0 [aufs]
  ? lookup_dcache+0x44/0x70
  ? lookup_one_len+0x66/0x90
  vfsub_lookup_one_len+0x50/0x70 [aufs]
  au_sio_lkup_one+0x8e/0xa0 [aufs]
  au_lkup_dentry+0x3fa/0x660 [aufs]
  aufs_lookup.part.35+0x11c/0x210 [aufs]
  aufs_atomic_open+0xec/0x3c0 [aufs]
  path_openat+0xe30/0x16a0
  ? aufs_lookup+0x30/0x30 [aufs]
  ? path_openat+0xe30/0x16a0
  ? unlock_page_memcg+0x12/0x20
  ? filemap_map_pages+0x17d/0x3b0
  do_filp_open+0x9b/0x110
  ? __check_object_size+0xdb/0x1b0
  ? __alloc_fd+0xb2/0x170
  do_sys_open+0x1ba/0x2e0
  ? do_sys_open+0x1ba/0x2e0
  __x64_sys_openat+0x20/0x30
  do_syscall_64+0x5e/0x200
  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  RIP: 0033:0x4a06fa

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


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

[Kernel-packages] [Bug 1948470] Re: aufs: kernel bug with apparmor and fuseblk

[Mauricio Faria de Oliveira]

Test with focal-proposed (5.4.0-90.101)
---

Original:

# ../openat
Killed

[  286.989830] BUG: kernel NULL pointer dereference, address: 0010
...
[  286.996507] CPU: 2 PID: 5529 Comm: openat Not tainted 5.4.0-90-generic 
#101-Ubuntu
[  286.997358] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.13.0-1ubuntu1.1 04/01/2014
[  286.998397] RIP: 0010:d_namespace_path.constprop.0+0x48/0x300
...
[  287.008418] Call Trace:
[  287.016112]  aa_path_name+0x42/0xb0
[  287.016616]  path_name.isra.0+0x5f/0xe0
[  287.017153]  profile_path_perm.part.0+0x58/0xa0
[  287.017768]  aa_path_perm+0xdd/0x130
[  287.018293]  common_perm+0x96/0x110
[  287.018795]  common_perm_cond+0x4c/0x70
[  287.019353]  apparmor_inode_getattr+0x1d/0x20
[  287.019948]  security_inode_getattr+0x35/0x50
[  287.020542]  vfs_getattr+0x22/0x50
[  287.021042]  vfsub_update_h_iattr+0x95/0xb0 [aufs]
[  287.021687]  ? lookup_dcache+0x46/0x70
[  287.022216]  ? lookup_one_len+0x68/0x90
[  287.022755]  vfsub_lookup_one_len+0x61/0x70 [aufs]
[  287.023413]  au_wh_test+0x26/0xa0 [aufs]
[  287.023978]  au_lkup_dentry+0x1ba/0x670 [aufs]
[  287.024598]  aufs_lookup.part.0+0x119/0x200 [aufs]
[  287.025250]  aufs_atomic_open+0x19d/0x400 [aufs]
[  287.025881]  ? aufs_permission+0x1a9/0x2f0 [aufs]
[  287.026536]  ? security_path_mknod+0x4c/0x70
[  287.027130]  lookup_open+0x364/0x6e0
[  287.027658]  do_last+0x2cb/0x900
[  287.028141]  ? __alloc_file+0x94/0x110
[  287.028678]  path_openat+0x8d/0x290
[  287.029184]  ? do_async_page_fault+0x39/0x70
[  287.029773]  do_filp_open+0x91/0x100
[  287.030292]  ? strncpy_from_user+0xbd/0x150
[  287.030879]  ? __alloc_fd+0xb8/0x150
[  287.031402]  do_sys_open+0x17e/0x290
[  287.031920]  __x64_sys_openat+0x20/0x30
[  287.032469]  do_syscall_64+0x57/0x190
[  287.032997]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  287.033682] RIP: 0033:0x7f299dccf026


Patched:

# ../openat
# echo $?
0

# uname -rv
5.4.0-90-generic #101+test20211022b2 SMP Fri Oct 22 10:34:51 -03 2021

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

Title:
  aufs: kernel bug with apparmor and fuseblk

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  In Progress
Status in linux source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Invalid

Bug description:
  [Impact]

   * AppArmor-enabled applications on the aufs filesystem
     might hit a kernel bug when getting file attributes.

   * The aufs filesystem explicitly assigns a NULL pointer
     to `struct path.mnt` for `vfs_getattr()`, which calls
     into AppArmor that checks `struct path.mnt->mnt_flags`,
     triggering a kernel NULL pointer dereference.

   * This is almost 10 years old [1,2], reproducible w/ the
     Linux v3.2 kernel, but it's rare as apparently it needs
     a fuseblk mount as an aufs branch, and file creation/
     open (O_CREAT), with a filename that exists only in a
     lower aufs branch. On Linux v5.15-rc* it doesn't need
     AppArmor anymore.

  [Fix]

   * The patch fixing this issue does set `struct path.mnt`
     properly, by taking `struct path` as parameter instead
     of just `struct dentry` (and making up an incomplete
     `struct path` w/ that `dentry` and `mnt = NULL`.)

   * Since it changes the signature of a key, leaf function
     with several callers, the patch is a bit long/refactor,
     but it has been tested by the upstream aufs maintainer
     with a private test-suite.

  [Test Plan]

   * Synthetic reproducer available in [1] and comment #1.

  [Regression Potential]

   * Regressions would probably manifest as kernel errors
     mostly in the lookup and open paths, but more subtle
     manifestations would be possible as well.

   * The patch modifies a fair number of functions, even if
     doing so in simple ways. The synthetic reproducer only
     covers one of those functions.

   * The other code paths have been tested by the maintainer
     w/ the mainline kernel, and should be equivalent to our
     kernel as none of such changed for cherry-pick/backport.

   * The upstream aufs maintainer runs a private test suite
     that covers several features and use cases of aufs, so
     hopefully that provides some relief to take this patch.

  [Other Info]

   * Impish no longer ships aufs; no fix needed.
   * Hirsute/Focal/Bionic do/need it. (H only for backports)
   * Hirsute/Focal are clean cherry-picks.
   * Bionic is a trivial backport.

  [1] https://sourceforge.net/p/aufs/mailman/message/37363599/
  [2] 
https://unix.stackexchange.com/questions/324571/docker-run-causing-kernel-panic

  [Kernel Traces]

  BUG: kernel NULL pointer dereference, address: 0010
  ...
  CPU: 23 PID: 17623 Comm: drone-agent Not tainted 5.4.0-1058-azure

[Kernel-packages] [Bug 1947453] Re: [amdgpu] wayland black screen with white flashes, display corruption, kernel 5.13

[Eugene Savelov]

still reproduced with latest proposed kernel (5.13.0-21-generic)
test case:
turn secure boot on
cold boot ubuntu
authenticate and launch wayland session
result - display goes black


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

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=213779
   Importance: Unknown
   Status: Unknown

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

Title:
  [amdgpu] wayland black screen with white flashes, display corruption,
  kernel 5.13

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

Bug description:
  After upgrade from ubuntu 21.04 to ubuntu 21.10 I am seeing black
  screen in wayland session and screen corruption in Xorg session

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 16 15:49:45 2021
  DistUpgraded: 2021-10-16 08:19:20,349 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev da) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1043:1b70]
  InstallationDate: Installed on 2020-11-20 (329 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: ASUSTeK COMPUTER INC. X505BA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro iommu=soft quiet splash 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago)
  dmi.bios.date: 04/02/2020
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X505BA.317
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X505BA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: X505BA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  eugene 2026 F pulseaudio
   /dev/snd/controlC0:  eugene 2026 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-11-20 (329 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: ASUSTeK COMPUTER INC. X505BA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios

[Kernel-packages] [Bug 1948343] Re: Docking Station crash ramdomly after october 19 updates

[Ignacio Nicolas Beber]

UPDATE:

3 hours running windows 10 -> no problem.
2 hours running Ubuntu 20.04.2 -> No problem

40 minutes running Ubuntu 20.04.3 -> Start crashing.

Id think is not a Hardware problem. All it show its something in 20.04.3
updates/upgrades.

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

Title:
  Docking Station crash ramdomly after october 19 updates

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My dell D6000 dockingstation start crashing after installation of
  updates on october 19.

  Now, randomly the external HDMI monitor goes blank for 5 second until
  dock restart. But this fails make external webcam (connected to
  dockstation), and bluetooth headphones (mic at external web cam) got
  unconfigured, sending audio to the dock port and getting mic from it
  not regarding is not used, putting in a meeting without any sound.

  And because internet is also used via D6000 wired ethernet port, I got
  disconnected from VPN and RDP connections too.

  Release info:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.36
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  Uname: Linux 5.10.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 21 18:00:54 2021
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Vostro 3401
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem 
root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1050-oem N/A
   linux-backports-modules-5.10.0-1050-oem  N/A
   linux-firmware   1.187.19
  Tags:  focal
  Uname: Linux 5.10.0-1050-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2021
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0790WT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3401
  dmi.product.sku: 0A29
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1948351] Re: ppc64 BPF JIT mod by 1 will not return 0

[Thadeu Lima de Souza Cascardo]

** Summary changed:

- linux ADT test_bpf failure with linux/5.4.0-90.101
+ ppc64 BPF JIT mod by 1 will not return 0

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

Title:
  ppc64 BPF JIT mod by 1 will not return 0

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress

Bug description:
  This is a scripted bug report about ADT failures while running linux
  tests for linux/5.4.0-90.101 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  
  Consistently failing on Focal/linux 5.4.0-90.101

  13:15:26 DEBUG| [stdout] # selftests: net: test_bpf.sh
  13:15:27 DEBUG| [stdout] # test_bpf: [FAIL]
  13:15:27 DEBUG| [stdout] not ok 9 selftests: net: test_bpf.sh # exit=1

  
  Testing failed on:
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20211021_141544_eda49@/log.gz

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


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

[Kernel-packages] [Bug 1689461] Re: bluetoothd crashed with SIGSEGV from g_io_channel_shutdown from attio_cleanup from browse_request_cancel from device_remove from btd_adapter_remove_device

[ALinuxUser]

I experience what might be a similar crash, albeit on Linux Mint.

I have put a crash dump here: https://termbin.com/b726b. Also, I
reported the issue against Mint, here:
https://github.com/linuxmint/cinnamon/issues/10412#issuecomment-949710193.

I am unsure whether this the current page is the right place to report
this problem (even if it _is_ closely related to the problem that this
page mentions).

** Bug watch added: github.com/linuxmint/cinnamon/issues #10412
   https://github.com/linuxmint/cinnamon/issues/10412

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

Title:
  bluetoothd crashed with SIGSEGV from g_io_channel_shutdown from
  attio_cleanup from browse_request_cancel from device_remove from
  btd_adapter_remove_device

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bluez.  This problem was most recently seen with package version 5.37-0ubuntu5, 
the problem page at 
https://errors.ubuntu.com/problem/732cce930e4db100b0ec943638e1029f4655fbf9 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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


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

[Kernel-packages] [Bug 1948470] Re: aufs: kernel bug with apparmor and fuseblk

[Mauricio Faria de Oliveira]

** Description changed:

  [Impact]
  
   * AppArmor-enabled applications on the aufs filesystem
     might hit a kernel bug when getting file attributes.
  
   * The aufs filesystem explicitly assigns a NULL pointer
     to `struct path.mnt` for `vfs_getattr()`, which calls
     into AppArmor that checks `struct path.mnt->mnt_flags`,
     triggering a kernel NULL pointer dereference.
  
   * This is almost 10 years old [1,2], reproducible w/ the
     Linux v3.2 kernel, but it's rare as apparently it needs
     a fuseblk mount as an aufs branch, and file creation/
     open (O_CREAT), with a filename that exists only in a
     lower aufs branch. On Linux v5.15-rc* it doesn't need
     AppArmor anymore.
  
  [Fix]
  
   * The patch fixing this issue does set `struct path.mnt`
     properly, by taking `struct path` as parameter instead
     of just `struct dentry` (and making up an incomplete
     `struct path` w/ that `dentry` and `mnt = NULL`.)
  
   * Since it changes the signature of a key, leaf function
     with several callers, the patch is a bit long/refactor,
     but it has been tested by the upstream aufs maintainer
     with a private test-suite.
  
  [Test Plan]
  
   * Synthetic reproducer available in [1] and comment #1.
  
  [Regression Potential]
  
   * Regressions would probably manifest as kernel errors
     mostly in the lookup and open paths, but more subtle
     manifestations would be possible as well.
  
   * The patch modifies a fair number of functions, even if
     doing so in simple ways. The synthetic reproducer only
     covers one of those functions.
  
   * The other code paths have been tested by the maintainer
     w/ the mainline kernel, and should be equivalent to our
     kernel as none of such changed for cherry-pick/backport.
  
   * The upstream aufs maintainer runs a private test suite
     that covers several features and use cases of aufs, so
     hopefully that provides some relief to take this patch.
  
  [Other Info]
  
   * Impish no longer ships aufs; no fix needed.
-  * Hirsute/Focal/Bionic do/need it.
+  * Hirsute/Focal/Bionic do/need it. (H only for backports)
   * Hirsute/Focal are clean cherry-picks.
   * Bionic is a trivial backport.
  
  [1] https://sourceforge.net/p/aufs/mailman/message/37363599/
  [2] 
https://unix.stackexchange.com/questions/324571/docker-run-causing-kernel-panic
  
  [Kernel Traces]
  
  BUG: kernel NULL pointer dereference, address: 0010
  ...
  CPU: 23 PID: 17623 Comm: drone-agent Not tainted 5.4.0-1058-azure 
#60~18.04.1-Ubuntu
  Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 
090008 12/07/2018
  RIP: 0010:aa_path_name+0x55/0x370
  ...
  Call Trace:
  ? request_wait_answer+0xc4/0x200
  path_name+0x60/0xe0
  profile_path_perm.part.9+0x57/0xa0
  aa_path_perm+0xe2/0x130
  common_perm+0x59/0x130
  common_perm_cond+0x4c/0x70
  apparmor_inode_getattr+0x1d/0x20
  security_inode_getattr+0x35/0x50
  vfs_getattr+0x21/0x40
  vfsub_update_h_iattr+0x95/0xb0 [aufs]
  ? lookup_dcache+0x44/0x70
  ? lookup_one_len+0x66/0x90
  vfsub_lookup_one_len+0x50/0x70 [aufs]
  au_sio_lkup_one+0x8e/0xa0 [aufs]
  au_lkup_dentry+0x3fa/0x660 [aufs]
  aufs_lookup.part.35+0x11c/0x210 [aufs]
  aufs_atomic_open+0xec/0x3c0 [aufs]
  path_openat+0xe30/0x16a0
  ? aufs_lookup+0x30/0x30 [aufs]
  ? path_openat+0xe30/0x16a0
  ? unlock_page_memcg+0x12/0x20
  ? filemap_map_pages+0x17d/0x3b0
  do_filp_open+0x9b/0x110
  ? __check_object_size+0xdb/0x1b0
  ? __alloc_fd+0xb2/0x170
  do_sys_open+0x1ba/0x2e0
  ? do_sys_open+0x1ba/0x2e0
  __x64_sys_openat+0x20/0x30
  do_syscall_64+0x5e/0x200
  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  RIP: 0033:0x4a06fa

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

Title:
  aufs: kernel bug with apparmor and fuseblk

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  In Progress
Status in linux source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Invalid

Bug description:
  [Impact]

   * AppArmor-enabled applications on the aufs filesystem
     might hit a kernel bug when getting file attributes.

   * The aufs filesystem explicitly assigns a NULL pointer
     to `struct path.mnt` for `vfs_getattr()`, which calls
     into AppArmor that checks `struct path.mnt->mnt_flags`,
     triggering a kernel NULL pointer dereference.

   * This is almost 10 years old [1,2], reproducible w/ the
     Linux v3.2 kernel, but it's rare as apparently it needs
     a fuseblk mount as an aufs branch, and file creation/
     open (O_CREAT), with a filename that exists only in a
     lower aufs branch. On Linux v5.15-rc* it doesn't need
     AppArmor anymore.

  [Fix]

   * The patch fixing this issue does set `struct path.mnt`
     proper

[Kernel-packages] [Bug 1948471] Re: Kernel panic - kernel NULL pointer dereference; RIP is at blk_mq_put_rq_ref+0xa/0x60

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux-meta-gcp-5.11 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Kernel panic - kernel NULL pointer dereference; RIP is at
  blk_mq_put_rq_ref+0xa/0x60

Status in linux-meta-gcp-5.11 package in Ubuntu:
  Confirmed

Bug description:
  We have recently seen seemingly random kernel panics on one of our
  instances in Google Compute Engine, running the `linux-gcp-5.11`
  kernel on Ubuntu 20.04.

  The crashes happened weeks apart and seem to occur randomly, we have
  not found a way to consistently trigger the crashes.

  We've captured the crash logs of the two crashes we've seen so far:

  ## Crash 1

  [731972.720559] BUG: kernel NULL pointer dereference, address: 

  [731972.727963] #PF: supervisor instruction fetch in kernel mode
  [731972.733844] #PF: error_code(0x0010) - not-present page
  [731972.739243] PGD 147111067 P4D 147111067 PUD 10fd90067 PMD 0 
  [731972.745117] Oops: 0010 [#1] SMP NOPTI
  [731972.748989] CPU: 6 PID: 146349 Comm: node_exporter Not tainted 
5.11.0-1018-gcp #20~20.04.2-Ubuntu
  [731972.758078] Hardware name: Google Google Compute Engine/Google Compute 
Engine, BIOS Google 01/01/2011
  [731972.767508] RIP: 0010:0x0
  [731972.770345] Code: Unable to access opcode bytes at RIP 0xffd6.
  [731972.777862] RSP: 0018:b971c105fb00 EFLAGS: 00010246
  [731972.783298] RAX:  RBX: b971c105fb90 RCX: 
0002
  [731972.790643] RDX: 0001 RSI:  RDI: 
9e4a8305dc00
  [731972.797984] RBP: b971c105fb08 R08:  R09: 
003b
  [731972.805328] R10: 9e4aa8ac2000 R11: 9e4aa8ac13b2 R12: 
9e4a8305dc00
  [731972.812672] R13: 9e4a8305d000 R14:  R15: 
0001
  [731972.820016] FS:  7fb07dffb700() GS:9e693fb8() 
knlGS:
  [731972.829050] CS:  0010 DS:  ES:  CR0: 80050033
  [731972.835006] CR2: ffd6 CR3: 0001115a8000 CR4: 
00350ee0
  [731972.843919] Call Trace:
  [731972.846571]  blk_mq_put_rq_ref+0x47/0x60
  [731972.850710]  bt_iter+0x54/0x90
  [731972.854002]  blk_mq_queue_tag_busy_iter+0x18b/0x2d0
  [731972.859104]  ? blk_mq_hctx_mark_pending+0x70/0x70
  [731972.864026]  ? blk_mq_hctx_mark_pending+0x70/0x70
  [731972.868952]  blk_mq_in_flight+0x38/0x60
  [731972.873355]  diskstats_show+0x75/0x2b0
  [731972.877322]  seq_read_iter+0x2a3/0x450
  [731972.881288]  proc_reg_read_iter+0x5e/0x80
  [731972.885499]  new_sync_read+0x110/0x1a0
  [731972.890119]  vfs_read+0x154/0x1b0
  [731972.893647]  ksys_read+0x67/0xe0
  [731972.897092]  __x64_sys_read+0x1a/0x20
  [731972.900969]  do_syscall_64+0x38/0x90
  [731972.904870]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [731972.910124] RIP: 0033:0x4bd01b
  [731972.913381] Code: fb ff eb bd e8 e6 22 fb ff e9 61 ff ff ff cc e8 5b f1 
fa ff 48 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 48 8b 44 24 08 0f 05 <48> 3d 
01 f0 ff ff 76 20 48 c7 44 24 28 ff ff ff ff 48 c7 44 24 30
  [731972.933139] RSP: 002b:00c0005797f0 EFLAGS: 0206 ORIG_RAX: 

  [731972.940915] RAX: ffda RBX: 00c45800 RCX: 
004bd01b
  [731972.948249] RDX: 1000 RSI: 00c00087a000 RDI: 
0008
  [731972.955586] RBP: 00c000579840 R08: 0001 R09: 
0002
  [731972.963040] R10:  R11: 0206 R12: 

  [731972.970378] R13: 0002 R14: 0002 R15: 
0002
  [731972.978074] Modules linked in: nls_iso8859_1 dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
aesni_intel crypto_simd cryptd virtio_net glue_helper net_failover input_leds 
failover psmouse serio_raw efi_pstore sch_fq_codel msr drm virtio_rng ip_tables 
x_tables autofs4
  [731973.006538] CR2: 
  [731973.010064] ---[ end trace a489911d719de581 ]---
  [731973.135811] RIP: 0010:0x0
  [731973.138658] Code: Unable to access opcode bytes at RIP 0xffd6.
  [731973.145731] RSP: 0018:b971c105fb00 EFLAGS: 00010246
  [731973.151331] RAX:  RBX: b971c105fb90 RCX: 
0002
  [731973.158961] RDX: 0001 RSI:  RDI: 
9e4a8305dc00
  [731973.166296] RBP: b971c105fb08 R08:  R09: 
003b
  [731973.173718] R10: 9e4aa8ac2000 R11: 9e4aa8ac13b2 R12: 
9e4a8305dc00
  [731973.181228] R13: 9e4a8305d000 R14:  R15: 
0001
  [731973.189008] FS:  7fb07dffb700() GS:9e693fb8() 
knlGS:
  [731973.197297] CS:  0010 DS:  ES:  CR0: 80050033
  [731973.203242] CR2: 

[Kernel-packages] [Bug 1948470] Re: aufs: kernel bug with apparmor and fuseblk

[Mauricio Faria de Oliveira]

Steps to Reproduce:

1) test app

# cat openat.c
#include 
#include 

int main() {
int rc;
rc = openat(AT_FDCWD, "test", O_RDWR | O_CREAT | S_IRWXU);
if (rc < 0) {
perror("openat");
return 1;
}
return 0;
}

# gcc -o openat openat.c

2) ntfs-3g mount (fuseblk)

# truncate -s 1g ntfs.img
# DEV=$(losetup -f --show ntfs.img)
# mkfs.ntfs --fast $DEV

# mkdir ntfs
# mount -t ntfs-3g $DEV ntfs

# mount | grep ntfs | grep fuseblk
/dev/loop6 on /home/ubuntu/ntfs type fuseblk 
(rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096)

3) aufs mount (with 'test' file in the read-only branch)

# mkdir ro aufs
# touch ro/test
# mount -t aufs -o br=ntfs:ro none aufs

4) enable apparmor for the test app (even in complain mode with aa-
genprof)

# aa-genprof ./openat &
...
Please start the application to be profiled in
another window and exercise its functionality now.
...

[1]+  Stopped aa-genprof ./openat

5) remove 'test' file from read-write branch (still exists in read-only
branch)

# cd aufs
# rm test

6) run the test app

# ../openat
Killed

7) check kernel logs

# dmesg

** Description changed:

- aufs: kernel bug with apparmor and fuseblk
- 
  [Impact]
  
-  * AppArmor-enabled applications on the aufs filesystem
-might hit a kernel bug when getting file attributes.
-  
-  * The aufs filesystem explicitly assigns a NULL pointer
-to `struct path.mnt` for `vfs_getattr()`, which calls
-into AppArmor that checks `struct path.mnt->mnt_flags`,
-triggering a kernel NULL pointer dereference.
-
-  * This is almost 10 years old [1,2], reproducible w/ the
-Linux v3.2 kernel, but it's rare as apparently it needs
-a fuseblk mount as an aufs branch, and file creation/
-open (O_CREAT), with a filename that exists only in a
-lower aufs branch. On Linux v5.15-rc* it doesn't need
-AppArmor anymore.
+  * AppArmor-enabled applications on the aufs filesystem
+    might hit a kernel bug when getting file attributes.
+ 
+  * The aufs filesystem explicitly assigns a NULL pointer
+    to `struct path.mnt` for `vfs_getattr()`, which calls
+    into AppArmor that checks `struct path.mnt->mnt_flags`,
+    triggering a kernel NULL pointer dereference.
+ 
+  * This is almost 10 years old [1,2], reproducible w/ the
+    Linux v3.2 kernel, but it's rare as apparently it needs
+    a fuseblk mount as an aufs branch, and file creation/
+    open (O_CREAT), with a filename that exists only in a
+    lower aufs branch. On Linux v5.15-rc* it doesn't need
+    AppArmor anymore.
  
  [Fix]
  
-  * The patch fixing this issue does set `struct path.mnt`
-properly, by taking `struct path` as parameter instead
-of just `struct dentry` (and making up an incomplete
-`struct path` w/ that `dentry` and `mnt = NULL`.)
-  
-  * Since it changes the signature of a key, leaf function
-with several callers, the patch is a bit long/refactor,
-but it has been tested by the upstream aufs maintainer
-with a private test-suite.
-
+  * The patch fixing this issue does set `struct path.mnt`
+    properly, by taking `struct path` as parameter instead
+    of just `struct dentry` (and making up an incomplete
+    `struct path` w/ that `dentry` and `mnt = NULL`.)
+ 
+  * Since it changes the signature of a key, leaf function
+    with several callers, the patch is a bit long/refactor,
+    but it has been tested by the upstream aufs maintainer
+    with a private test-suite.
+ 
  [Test Plan]
  
-  * Synthetic reproducer available in [1] and comment #1.
+  * Synthetic reproducer available in [1] and comment #1.
  
  [Regression Potential]
  
-  * Regressions would probably manifest as kernel errors
-mostly in the lookup and open paths, but more subtle
-manifestations would be possible as well.
-  
-  * The patch modifies a fair number of functions, even if
-doing so in simple ways. The synthetic reproducer only
-covers one of those functions. 
-   
-  * The other code paths have been tested by the maintainer
-w/ the mainline kernel, and should be equivalent to our
-kernel as none of such changed for cherry-pick/backport.
-
-  * The upstream aufs maintainer runs a private test suite
-that covers several features and use cases of aufs, so
-hopefully that provides some relief to take this patch.
-
+  * Regressions would probably manifest as kernel errors
+    mostly in the lookup and open paths, but more subtle
+    manifestations would be possible as well.
+ 
+  * The patch modifies a fair number of functions, even if
+    doing so in simple ways. The synthetic reproducer only
+    covers one of those functio

[Kernel-packages] [Bug 1948470] [NEW] aufs: kernel bug with apparmor and fuseblk

[Mauricio Faria de Oliveira]

Public bug reported:

[Impact]

 * AppArmor-enabled applications on the aufs filesystem
   might hit a kernel bug when getting file attributes.

 * The aufs filesystem explicitly assigns a NULL pointer
   to `struct path.mnt` for `vfs_getattr()`, which calls
   into AppArmor that checks `struct path.mnt->mnt_flags`,
   triggering a kernel NULL pointer dereference.

 * This is almost 10 years old [1,2], reproducible w/ the
   Linux v3.2 kernel, but it's rare as apparently it needs
   a fuseblk mount as an aufs branch, and file creation/
   open (O_CREAT), with a filename that exists only in a
   lower aufs branch. On Linux v5.15-rc* it doesn't need
   AppArmor anymore.

[Fix]

 * The patch fixing this issue does set `struct path.mnt`
   properly, by taking `struct path` as parameter instead
   of just `struct dentry` (and making up an incomplete
   `struct path` w/ that `dentry` and `mnt = NULL`.)

 * Since it changes the signature of a key, leaf function
   with several callers, the patch is a bit long/refactor,
   but it has been tested by the upstream aufs maintainer
   with a private test-suite.

[Test Plan]

 * Synthetic reproducer available in [1] and comment #1.

[Regression Potential]

 * Regressions would probably manifest as kernel errors
   mostly in the lookup and open paths, but more subtle
   manifestations would be possible as well.

 * The patch modifies a fair number of functions, even if
   doing so in simple ways. The synthetic reproducer only
   covers one of those functions.

 * The other code paths have been tested by the maintainer
   w/ the mainline kernel, and should be equivalent to our
   kernel as none of such changed for cherry-pick/backport.

 * The upstream aufs maintainer runs a private test suite
   that covers several features and use cases of aufs, so
   hopefully that provides some relief to take this patch.

[Other Info]

 * Impish no longer ships aufs; no fix needed.
 * Hirsute/Focal/Bionic do/need it.
 * Hirsute/Focal are clean cherry-picks.
 * Bionic is a trivial backport.

[1] https://sourceforge.net/p/aufs/mailman/message/37363599/
[2] 
https://unix.stackexchange.com/questions/324571/docker-run-causing-kernel-panic

[Kernel Traces]

BUG: kernel NULL pointer dereference, address: 0010
...
CPU: 23 PID: 17623 Comm: drone-agent Not tainted 5.4.0-1058-azure 
#60~18.04.1-Ubuntu
Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 
090008 12/07/2018
RIP: 0010:aa_path_name+0x55/0x370
...
Call Trace:
? request_wait_answer+0xc4/0x200
path_name+0x60/0xe0
profile_path_perm.part.9+0x57/0xa0
aa_path_perm+0xe2/0x130
common_perm+0x59/0x130
common_perm_cond+0x4c/0x70
apparmor_inode_getattr+0x1d/0x20
security_inode_getattr+0x35/0x50
vfs_getattr+0x21/0x40
vfsub_update_h_iattr+0x95/0xb0 [aufs]
? lookup_dcache+0x44/0x70
? lookup_one_len+0x66/0x90
vfsub_lookup_one_len+0x50/0x70 [aufs]
au_sio_lkup_one+0x8e/0xa0 [aufs]
au_lkup_dentry+0x3fa/0x660 [aufs]
aufs_lookup.part.35+0x11c/0x210 [aufs]
aufs_atomic_open+0xec/0x3c0 [aufs]
path_openat+0xe30/0x16a0
? aufs_lookup+0x30/0x30 [aufs]
? path_openat+0xe30/0x16a0
? unlock_page_memcg+0x12/0x20
? filemap_map_pages+0x17d/0x3b0
do_filp_open+0x9b/0x110
? __check_object_size+0xdb/0x1b0
? __alloc_fd+0xb2/0x170
do_sys_open+0x1ba/0x2e0
? do_sys_open+0x1ba/0x2e0
__x64_sys_openat+0x20/0x30
do_syscall_64+0x5e/0x200
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x4a06fa

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

** Affects: linux (Ubuntu Bionic)
 Importance: Low
 Assignee: Mauricio Faria de Oliveira (mfo)
 Status: In Progress

** Affects: linux (Ubuntu Focal)
 Importance: Low
 Assignee: Mauricio Faria de Oliveira (mfo)
 Status: In Progress

** Affects: linux (Ubuntu Hirsute)
 Importance: Low
 Assignee: Mauricio Faria de Oliveira (mfo)
 Status: In Progress

** Affects: linux (Ubuntu Impish)
 Importance: Undecided
 Status: Invalid

** Affects: linux (Ubuntu Jammy)
 Importance: Undecided
 Status: Invalid

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

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

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

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

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

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

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

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

** Changed in: linux (Ubuntu Hirsute)
   Importance: Undecided => Low

** Changed in: linux (Ubuntu Hirsute)
 Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)

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

** Changed in: linux (Ubuntu Focal)
   Importance: Undec

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Touchpad not detected Fujitsu Lifebook U9311X

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No response from the touch pad. This laptop also has a touch screen,
  that works fine. The cursor is floating on the screen but I cannot
  control it. When I use the touch screen with fingers or with the
  provided pen I can control a second cursor, but the original one
  remains in place.

  xinput:

  WARNING: running xinput against an Xwayland server. See the xinput man page 
for details.
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ xwayland-touch:17   id=7[slave  pointer 
 (2)]
  ⎜   ↳ xwayland-tablet stylus:17   id=8[slave  pointer 
 (2)]
  ⎜   ↳ xwayland-tablet eraser:17   id=9[slave  pointer 
 (2)]
  ⎜   ↳ xwayland-tablet cursor:17   id=10   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ xwayland-keyboard:17id=6[slave  
keyboard (3)]

  The touchpad appears to not be there at all. See also attached cat of
  /proc/bus/input/devices. No touchpad there either.

  This is a fresh install(origally came with Windows). I updated all
  packages. I am on 21.04. I originally was on 20.04 but upgraded
  because I thought it would help for the touchscreen using do-release-
  upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-38-generic 5.11.0-38.42
  ProcVersionSignature: Ubuntu 5.11.0-38.42-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aart   1629 F pulseaudio
   /dev/snd/pcmC0D0p:   aart   1629 F...m pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 22 17:26:46 2021
  InstallationDate: Installed on 2021-10-22 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U9311X
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-38-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-38-generic N/A
   linux-backports-modules-5.11.0-38-generic  N/A
   linux-firmware 1.197.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-10-22 (0 days ago)
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 2.16
  dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.bios.version: Version 2.16
  dmi.board.name: FJNB2E4
  dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.board.version: A4
  dmi.chassis.type: 31
  dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.chassis.version: LIFEBOOK U9311X
  dmi.modalias: 
dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.16:bd04/20/2021:br2.16:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU9311X:pvr10601736746:skuSK01:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2E4:rvrA4:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvrLIFEBOOKU9311X:
  dmi.product.family: LIFEBOOK-FTS
  dmi.product.name: LIFEBOOK U9311X
  dmi.product.sku: SK01
  dmi.product.version: 10601736746
  dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED

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


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

[Kernel-packages] [Bug 1948471] [NEW] Kernel panic - kernel NULL pointer dereference; RIP is at blk_mq_put_rq_ref+0xa/0x60

[Maarten van den Berg]

Public bug reported:

We have recently seen seemingly random kernel panics on one of our
instances in Google Compute Engine, running the `linux-gcp-5.11` kernel
on Ubuntu 20.04.

The crashes happened weeks apart and seem to occur randomly, we have not
found a way to consistently trigger the crashes.

We've captured the crash logs of the two crashes we've seen so far:

## Crash 1

[731972.720559] BUG: kernel NULL pointer dereference, address: 
[731972.727963] #PF: supervisor instruction fetch in kernel mode
[731972.733844] #PF: error_code(0x0010) - not-present page
[731972.739243] PGD 147111067 P4D 147111067 PUD 10fd90067 PMD 0 
[731972.745117] Oops: 0010 [#1] SMP NOPTI
[731972.748989] CPU: 6 PID: 146349 Comm: node_exporter Not tainted 
5.11.0-1018-gcp #20~20.04.2-Ubuntu
[731972.758078] Hardware name: Google Google Compute Engine/Google Compute 
Engine, BIOS Google 01/01/2011
[731972.767508] RIP: 0010:0x0
[731972.770345] Code: Unable to access opcode bytes at RIP 0xffd6.
[731972.777862] RSP: 0018:b971c105fb00 EFLAGS: 00010246
[731972.783298] RAX:  RBX: b971c105fb90 RCX: 
0002
[731972.790643] RDX: 0001 RSI:  RDI: 
9e4a8305dc00
[731972.797984] RBP: b971c105fb08 R08:  R09: 
003b
[731972.805328] R10: 9e4aa8ac2000 R11: 9e4aa8ac13b2 R12: 
9e4a8305dc00
[731972.812672] R13: 9e4a8305d000 R14:  R15: 
0001
[731972.820016] FS:  7fb07dffb700() GS:9e693fb8() 
knlGS:
[731972.829050] CS:  0010 DS:  ES:  CR0: 80050033
[731972.835006] CR2: ffd6 CR3: 0001115a8000 CR4: 
00350ee0
[731972.843919] Call Trace:
[731972.846571]  blk_mq_put_rq_ref+0x47/0x60
[731972.850710]  bt_iter+0x54/0x90
[731972.854002]  blk_mq_queue_tag_busy_iter+0x18b/0x2d0
[731972.859104]  ? blk_mq_hctx_mark_pending+0x70/0x70
[731972.864026]  ? blk_mq_hctx_mark_pending+0x70/0x70
[731972.868952]  blk_mq_in_flight+0x38/0x60
[731972.873355]  diskstats_show+0x75/0x2b0
[731972.877322]  seq_read_iter+0x2a3/0x450
[731972.881288]  proc_reg_read_iter+0x5e/0x80
[731972.885499]  new_sync_read+0x110/0x1a0
[731972.890119]  vfs_read+0x154/0x1b0
[731972.893647]  ksys_read+0x67/0xe0
[731972.897092]  __x64_sys_read+0x1a/0x20
[731972.900969]  do_syscall_64+0x38/0x90
[731972.904870]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[731972.910124] RIP: 0033:0x4bd01b
[731972.913381] Code: fb ff eb bd e8 e6 22 fb ff e9 61 ff ff ff cc e8 5b f1 fa 
ff 48 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 48 8b 44 24 08 0f 05 <48> 3d 01 
f0 ff ff 76 20 48 c7 44 24 28 ff ff ff ff 48 c7 44 24 30
[731972.933139] RSP: 002b:00c0005797f0 EFLAGS: 0206 ORIG_RAX: 

[731972.940915] RAX: ffda RBX: 00c45800 RCX: 
004bd01b
[731972.948249] RDX: 1000 RSI: 00c00087a000 RDI: 
0008
[731972.955586] RBP: 00c000579840 R08: 0001 R09: 
0002
[731972.963040] R10:  R11: 0206 R12: 

[731972.970378] R13: 0002 R14: 0002 R15: 
0002
[731972.978074] Modules linked in: nls_iso8859_1 dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
aesni_intel crypto_simd cryptd virtio_net glue_helper net_failover input_leds 
failover psmouse serio_raw efi_pstore sch_fq_codel msr drm virtio_rng ip_tables 
x_tables autofs4
[731973.006538] CR2: 
[731973.010064] ---[ end trace a489911d719de581 ]---
[731973.135811] RIP: 0010:0x0
[731973.138658] Code: Unable to access opcode bytes at RIP 0xffd6.
[731973.145731] RSP: 0018:b971c105fb00 EFLAGS: 00010246
[731973.151331] RAX:  RBX: b971c105fb90 RCX: 
0002
[731973.158961] RDX: 0001 RSI:  RDI: 
9e4a8305dc00
[731973.166296] RBP: b971c105fb08 R08:  R09: 
003b
[731973.173718] R10: 9e4aa8ac2000 R11: 9e4aa8ac13b2 R12: 
9e4a8305dc00
[731973.181228] R13: 9e4a8305d000 R14:  R15: 
0001
[731973.189008] FS:  7fb07dffb700() GS:9e693fb8() 
knlGS:
[731973.197297] CS:  0010 DS:  ES:  CR0: 80050033
[731973.203242] CR2: ffd6 CR3: 0001115a8000 CR4: 
00350ee0
[731973.210841] Kernel panic - not syncing: Fatal exception
[731973.222020] Kernel Offset: 0x1a20 from 0x8100 (relocation 
range: 0x8000-0xbfff)
[731973.361494] Rebooting in 10 seconds..

## Crash 2

[1785249.917228] BUG: kernel NULL pointer dereference, address: 00c0
[1785249.924620] #PF: supervisor read access in kernel mode
[1785249.930041] #PF: error_code(0x) - not-present page
[1785249.935458] PGD 109bb2067 P4D 109bb2067 PUD 106a5d067 PMD 0 
[1785249.941399] Oops:  [#1] SMP NOPTI
[1785249

[Kernel-packages] [Bug 1947453] Re: [amdgpu] wayland black screen with white flashes, display corruption, kernel 5.13

[Eugene Savelov]

https://launchpadlibrarian.net/564434654/linux_5.13.0-21.21_source.changes

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

Title:
  [amdgpu] wayland black screen with white flashes, display corruption,
  kernel 5.13

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade from ubuntu 21.04 to ubuntu 21.10 I am seeing black
  screen in wayland session and screen corruption in Xorg session

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 16 15:49:45 2021
  DistUpgraded: 2021-10-16 08:19:20,349 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev da) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1043:1b70]
  InstallationDate: Installed on 2020-11-20 (329 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: ASUSTeK COMPUTER INC. X505BA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro iommu=soft quiet splash 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago)
  dmi.bios.date: 04/02/2020
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X505BA.317
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X505BA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: X505BA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  eugene 2026 F pulseaudio
   /dev/snd/controlC0:  eugene 2026 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-11-20 (329 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: ASUSTeK COMPUTER INC. X505BA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/02/2020
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X505BA.317
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X505BA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chass

[Kernel-packages] [Bug 1947453] Re: [amdgpu] wayland black screen with white flashes, display corruption, kernel 5.13

[Eugene Savelov]

issue resolved with proposed kernel updated 5.13.0-21-generic
Linux eugene-X505BA 5.13.0-21-generic #21-Ubuntu SMP Tue Oct 19 08:59:28 UTC 
2021 x86_64 x86_64 x86_64 GNU/Linux
test case - cold boot laptop, authenticate and enter wayland session
result - works correctly

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

Title:
  [amdgpu] wayland black screen with white flashes, display corruption,
  kernel 5.13

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade from ubuntu 21.04 to ubuntu 21.10 I am seeing black
  screen in wayland session and screen corruption in Xorg session

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 16 15:49:45 2021
  DistUpgraded: 2021-10-16 08:19:20,349 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev da) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1043:1b70]
  InstallationDate: Installed on 2020-11-20 (329 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: ASUSTeK COMPUTER INC. X505BA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro iommu=soft quiet splash 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago)
  dmi.bios.date: 04/02/2020
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X505BA.317
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X505BA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: X505BA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  eugene 2026 F pulseaudio
   /dev/snd/controlC0:  eugene 2026 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-11-20 (329 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: ASUSTeK COMPUTER INC. X505BA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/02/2020
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X505BA.317
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.n

[Kernel-packages] [Bug 1948468] [NEW] Touchpad not detected Fujitsu Lifebook U9311X

[Aart Stuurman]

Public bug reported:

No response from the touch pad. This laptop also has a touch screen,
that works fine. The cursor is floating on the screen but I cannot
control it. When I use the touch screen with fingers or with the
provided pen I can control a second cursor, but the original one remains
in place.

xinput:

WARNING: running xinput against an Xwayland server. See the xinput man page for 
details.
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ xwayland-touch:17 id=7[slave  pointer  (2)]
⎜   ↳ xwayland-tablet stylus:17 id=8[slave  pointer  (2)]
⎜   ↳ xwayland-tablet eraser:17 id=9[slave  pointer  (2)]
⎜   ↳ xwayland-tablet cursor:17 id=10   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ xwayland-keyboard:17  id=6[slave  keyboard (3)]

The touchpad appears to not be there at all. See also attached cat of
/proc/bus/input/devices. No touchpad there either.

This is a fresh install(origally came with Windows). I updated all
packages. I am on 21.04. I originally was on 20.04 but upgraded because
I thought it would help for the touchscreen using do-release-upgrade.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: linux-image-5.11.0-38-generic 5.11.0-38.42
ProcVersionSignature: Ubuntu 5.11.0-38.42-generic 5.11.22
Uname: Linux 5.11.0-38-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  aart   1629 F pulseaudio
 /dev/snd/pcmC0D0p:   aart   1629 F...m pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 22 17:26:46 2021
InstallationDate: Installed on 2021-10-22 (0 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U9311X
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-38-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.11.0-38-generic N/A
 linux-backports-modules-5.11.0-38-generic  N/A
 linux-firmware 1.197.3
SourcePackage: linux
UpgradeStatus: Upgraded to hirsute on 2021-10-22 (0 days ago)
dmi.bios.date: 04/20/2021
dmi.bios.release: 2.16
dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
dmi.bios.version: Version 2.16
dmi.board.name: FJNB2E4
dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
dmi.board.version: A4
dmi.chassis.type: 31
dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
dmi.chassis.version: LIFEBOOK U9311X
dmi.modalias: 
dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.16:bd04/20/2021:br2.16:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU9311X:pvr10601736746:skuSK01:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2E4:rvrA4:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvrLIFEBOOKU9311X:
dmi.product.family: LIFEBOOK-FTS
dmi.product.name: LIFEBOOK U9311X
dmi.product.sku: SK01
dmi.product.version: 10601736746
dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED

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


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

** Attachment added: "devices"
   https://bugs.launchpad.net/bugs/1948468/+attachment/5535254/+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/1948468

Title:
  Touchpad not detected Fujitsu Lifebook U9311X

Status in linux package in Ubuntu:
  New

Bug description:
  No response from the touch pad. This laptop also has a touch screen,
  that works fine. The cursor is floating on the screen but I cannot
  control it. When I use the touch screen with fingers or with the
  provided pen I can control a second cursor, but the original one
  remains in place.

  xinput:

  WARNING: running xinput against an Xwayland server. See the xinput man page 
for details.
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ xwayland-touch:17   id=7[slave  pointer 
 (2)]
  ⎜   ↳ xwayland-tablet stylus:17   id=8[slave  pointer 
 (2)]
  ⎜   ↳ xwayland-tablet eraser:17   id=9[slave  pointer 
 (2)]
  ⎜   ↳ xwayland-tablet cursor:17   id=10   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ xwayland-keyboard:17id=6[slave  
keyboard (3)]

  The touchp

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

[Ignacio Nicolas Beber]

apport information

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

Title:
  Docking Station crash ramdomly after october 19 updates

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My dell D6000 dockingstation start crashing after installation of
  updates on october 19.

  Now, randomly the external HDMI monitor goes blank for 5 second until
  dock restart. But this fails make external webcam (connected to
  dockstation), and bluetooth headphones (mic at external web cam) got
  unconfigured, sending audio to the dock port and getting mic from it
  not regarding is not used, putting in a meeting without any sound.

  And because internet is also used via D6000 wired ethernet port, I got
  disconnected from VPN and RDP connections too.

  Release info:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.36
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  Uname: Linux 5.10.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 21 18:00:54 2021
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Vostro 3401
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem 
root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1050-oem N/A
   linux-backports-modules-5.10.0-1050-oem  N/A
   linux-firmware   1.187.19
  Tags:  focal
  Uname: Linux 5.10.0-1050-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2021
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0790WT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3401
  dmi.product.sku: 0A29
  dmi.sys.vendor: Dell Inc.

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


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

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

[Ignacio Nicolas Beber]

apport information

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

Title:
  Docking Station crash ramdomly after october 19 updates

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My dell D6000 dockingstation start crashing after installation of
  updates on october 19.

  Now, randomly the external HDMI monitor goes blank for 5 second until
  dock restart. But this fails make external webcam (connected to
  dockstation), and bluetooth headphones (mic at external web cam) got
  unconfigured, sending audio to the dock port and getting mic from it
  not regarding is not used, putting in a meeting without any sound.

  And because internet is also used via D6000 wired ethernet port, I got
  disconnected from VPN and RDP connections too.

  Release info:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.36
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  Uname: Linux 5.10.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 21 18:00:54 2021
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Vostro 3401
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem 
root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1050-oem N/A
   linux-backports-modules-5.10.0-1050-oem  N/A
   linux-firmware   1.187.19
  Tags:  focal
  Uname: Linux 5.10.0-1050-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2021
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0790WT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3401
  dmi.product.sku: 0A29
  dmi.sys.vendor: Dell Inc.

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


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

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

[Ignacio Nicolas Beber]

apport information

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

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

Title:
  Docking Station crash ramdomly after october 19 updates

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My dell D6000 dockingstation start crashing after installation of
  updates on october 19.

  Now, randomly the external HDMI monitor goes blank for 5 second until
  dock restart. But this fails make external webcam (connected to
  dockstation), and bluetooth headphones (mic at external web cam) got
  unconfigured, sending audio to the dock port and getting mic from it
  not regarding is not used, putting in a meeting without any sound.

  And because internet is also used via D6000 wired ethernet port, I got
  disconnected from VPN and RDP connections too.

  Release info:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.36
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  Uname: Linux 5.10.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 21 18:00:54 2021
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Vostro 3401
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem 
root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1050-oem N/A
   linux-backports-modules-5.10.0-1050-oem  N/A
   linux-firmware   1.187.19
  Tags:  focal
  Uname: Linux 5.10.0-1050-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2021
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0790WT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3401
  dmi.product.sku: 0A29
  dmi.sys.vendor: Dell Inc.

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


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

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

[Ignacio Nicolas Beber]

apport information

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

Title:
  Docking Station crash ramdomly after october 19 updates

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My dell D6000 dockingstation start crashing after installation of
  updates on october 19.

  Now, randomly the external HDMI monitor goes blank for 5 second until
  dock restart. But this fails make external webcam (connected to
  dockstation), and bluetooth headphones (mic at external web cam) got
  unconfigured, sending audio to the dock port and getting mic from it
  not regarding is not used, putting in a meeting without any sound.

  And because internet is also used via D6000 wired ethernet port, I got
  disconnected from VPN and RDP connections too.

  Release info:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.36
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  Uname: Linux 5.10.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 21 18:00:54 2021
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Vostro 3401
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem 
root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1050-oem N/A
   linux-backports-modules-5.10.0-1050-oem  N/A
   linux-firmware   1.187.19
  Tags:  focal
  Uname: Linux 5.10.0-1050-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2021
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0790WT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3401
  dmi.product.sku: 0A29
  dmi.sys.vendor: Dell Inc.

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


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

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

[Ignacio Nicolas Beber]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1948343/+attachment/5535241/+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/1948343

Title:
  Docking Station crash ramdomly after october 19 updates

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My dell D6000 dockingstation start crashing after installation of
  updates on october 19.

  Now, randomly the external HDMI monitor goes blank for 5 second until
  dock restart. But this fails make external webcam (connected to
  dockstation), and bluetooth headphones (mic at external web cam) got
  unconfigured, sending audio to the dock port and getting mic from it
  not regarding is not used, putting in a meeting without any sound.

  And because internet is also used via D6000 wired ethernet port, I got
  disconnected from VPN and RDP connections too.

  Release info:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.36
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  Uname: Linux 5.10.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 21 18:00:54 2021
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Vostro 3401
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem 
root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1050-oem N/A
   linux-backports-modules-5.10.0-1050-oem  N/A
   linux-firmware   1.187.19
  Tags:  focal
  Uname: Linux 5.10.0-1050-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2021
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0790WT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3401
  dmi.product.sku: 0A29
  dmi.sys.vendor: Dell Inc.

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


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

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

[Ignacio Nicolas Beber]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1948343/+attachment/5535236/+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/1948343

Title:
  Docking Station crash ramdomly after october 19 updates

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My dell D6000 dockingstation start crashing after installation of
  updates on october 19.

  Now, randomly the external HDMI monitor goes blank for 5 second until
  dock restart. But this fails make external webcam (connected to
  dockstation), and bluetooth headphones (mic at external web cam) got
  unconfigured, sending audio to the dock port and getting mic from it
  not regarding is not used, putting in a meeting without any sound.

  And because internet is also used via D6000 wired ethernet port, I got
  disconnected from VPN and RDP connections too.

  Release info:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.36
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  Uname: Linux 5.10.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 21 18:00:54 2021
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Vostro 3401
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem 
root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1050-oem N/A
   linux-backports-modules-5.10.0-1050-oem  N/A
   linux-firmware   1.187.19
  Tags:  focal
  Uname: Linux 5.10.0-1050-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2021
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0790WT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3401
  dmi.product.sku: 0A29
  dmi.sys.vendor: Dell Inc.

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


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

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

[Ignacio Nicolas Beber]

apport information

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

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

Title:
  Docking Station crash ramdomly after october 19 updates

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My dell D6000 dockingstation start crashing after installation of
  updates on october 19.

  Now, randomly the external HDMI monitor goes blank for 5 second until
  dock restart. But this fails make external webcam (connected to
  dockstation), and bluetooth headphones (mic at external web cam) got
  unconfigured, sending audio to the dock port and getting mic from it
  not regarding is not used, putting in a meeting without any sound.

  And because internet is also used via D6000 wired ethernet port, I got
  disconnected from VPN and RDP connections too.

  Release info:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.36
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  Uname: Linux 5.10.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 21 18:00:54 2021
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Vostro 3401
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem 
root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1050-oem N/A
   linux-backports-modules-5.10.0-1050-oem  N/A
   linux-firmware   1.187.19
  Tags:  focal
  Uname: Linux 5.10.0-1050-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2021
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0790WT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3401
  dmi.product.sku: 0A29
  dmi.sys.vendor: Dell Inc.

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


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

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

[Ignacio Nicolas Beber]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1948343/+attachment/5535246/+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/1948343

Title:
  Docking Station crash ramdomly after october 19 updates

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My dell D6000 dockingstation start crashing after installation of
  updates on october 19.

  Now, randomly the external HDMI monitor goes blank for 5 second until
  dock restart. But this fails make external webcam (connected to
  dockstation), and bluetooth headphones (mic at external web cam) got
  unconfigured, sending audio to the dock port and getting mic from it
  not regarding is not used, putting in a meeting without any sound.

  And because internet is also used via D6000 wired ethernet port, I got
  disconnected from VPN and RDP connections too.

  Release info:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.36
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  Uname: Linux 5.10.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 21 18:00:54 2021
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Vostro 3401
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem 
root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1050-oem N/A
   linux-backports-modules-5.10.0-1050-oem  N/A
   linux-firmware   1.187.19
  Tags:  focal
  Uname: Linux 5.10.0-1050-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2021
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0790WT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3401
  dmi.product.sku: 0A29
  dmi.sys.vendor: Dell Inc.

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


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

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

[Ignacio Nicolas Beber]

apport information

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

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

Title:
  Docking Station crash ramdomly after october 19 updates

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My dell D6000 dockingstation start crashing after installation of
  updates on october 19.

  Now, randomly the external HDMI monitor goes blank for 5 second until
  dock restart. But this fails make external webcam (connected to
  dockstation), and bluetooth headphones (mic at external web cam) got
  unconfigured, sending audio to the dock port and getting mic from it
  not regarding is not used, putting in a meeting without any sound.

  And because internet is also used via D6000 wired ethernet port, I got
  disconnected from VPN and RDP connections too.

  Release info:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.36
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  Uname: Linux 5.10.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 21 18:00:54 2021
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Vostro 3401
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem 
root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1050-oem N/A
   linux-backports-modules-5.10.0-1050-oem  N/A
   linux-firmware   1.187.19
  Tags:  focal
  Uname: Linux 5.10.0-1050-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2021
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0790WT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3401
  dmi.product.sku: 0A29
  dmi.sys.vendor: Dell Inc.

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


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

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

[Ignacio Nicolas Beber]

apport information

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

Title:
  Docking Station crash ramdomly after october 19 updates

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My dell D6000 dockingstation start crashing after installation of
  updates on october 19.

  Now, randomly the external HDMI monitor goes blank for 5 second until
  dock restart. But this fails make external webcam (connected to
  dockstation), and bluetooth headphones (mic at external web cam) got
  unconfigured, sending audio to the dock port and getting mic from it
  not regarding is not used, putting in a meeting without any sound.

  And because internet is also used via D6000 wired ethernet port, I got
  disconnected from VPN and RDP connections too.

  Release info:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.36
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  Uname: Linux 5.10.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 21 18:00:54 2021
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Vostro 3401
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem 
root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1050-oem N/A
   linux-backports-modules-5.10.0-1050-oem  N/A
   linux-firmware   1.187.19
  Tags:  focal
  Uname: Linux 5.10.0-1050-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2021
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0790WT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3401
  dmi.product.sku: 0A29
  dmi.sys.vendor: Dell Inc.

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


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

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

[Ignacio Nicolas Beber]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1948343/+attachment/5535238/+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/1948343

Title:
  Docking Station crash ramdomly after october 19 updates

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My dell D6000 dockingstation start crashing after installation of
  updates on october 19.

  Now, randomly the external HDMI monitor goes blank for 5 second until
  dock restart. But this fails make external webcam (connected to
  dockstation), and bluetooth headphones (mic at external web cam) got
  unconfigured, sending audio to the dock port and getting mic from it
  not regarding is not used, putting in a meeting without any sound.

  And because internet is also used via D6000 wired ethernet port, I got
  disconnected from VPN and RDP connections too.

  Release info:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.36
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  Uname: Linux 5.10.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 21 18:00:54 2021
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Vostro 3401
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem 
root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1050-oem N/A
   linux-backports-modules-5.10.0-1050-oem  N/A
   linux-firmware   1.187.19
  Tags:  focal
  Uname: Linux 5.10.0-1050-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2021
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0790WT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3401
  dmi.product.sku: 0A29
  dmi.sys.vendor: Dell Inc.

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


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

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

[Ignacio Nicolas Beber]

apport information

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

Title:
  Docking Station crash ramdomly after october 19 updates

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My dell D6000 dockingstation start crashing after installation of
  updates on october 19.

  Now, randomly the external HDMI monitor goes blank for 5 second until
  dock restart. But this fails make external webcam (connected to
  dockstation), and bluetooth headphones (mic at external web cam) got
  unconfigured, sending audio to the dock port and getting mic from it
  not regarding is not used, putting in a meeting without any sound.

  And because internet is also used via D6000 wired ethernet port, I got
  disconnected from VPN and RDP connections too.

  Release info:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.36
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  Uname: Linux 5.10.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 21 18:00:54 2021
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Vostro 3401
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem 
root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1050-oem N/A
   linux-backports-modules-5.10.0-1050-oem  N/A
   linux-firmware   1.187.19
  Tags:  focal
  Uname: Linux 5.10.0-1050-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2021
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0790WT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3401
  dmi.product.sku: 0A29
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1948343] acpidump.txt

[Ignacio Nicolas Beber]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1948343/+attachment/5535253/+files/acpidump.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/1948343

Title:
  Docking Station crash ramdomly after october 19 updates

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My dell D6000 dockingstation start crashing after installation of
  updates on october 19.

  Now, randomly the external HDMI monitor goes blank for 5 second until
  dock restart. But this fails make external webcam (connected to
  dockstation), and bluetooth headphones (mic at external web cam) got
  unconfigured, sending audio to the dock port and getting mic from it
  not regarding is not used, putting in a meeting without any sound.

  And because internet is also used via D6000 wired ethernet port, I got
  disconnected from VPN and RDP connections too.

  Release info:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.36
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  Uname: Linux 5.10.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 21 18:00:54 2021
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Vostro 3401
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem 
root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1050-oem N/A
   linux-backports-modules-5.10.0-1050-oem  N/A
   linux-firmware   1.187.19
  Tags:  focal
  Uname: Linux 5.10.0-1050-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2021
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0790WT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3401
  dmi.product.sku: 0A29
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1948343] AudioDevicesInUse.txt

[Ignacio Nicolas Beber]

apport information

** Attachment added: "AudioDevicesInUse.txt"
   
https://bugs.launchpad.net/bugs/1948343/+attachment/5535235/+files/AudioDevicesInUse.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/1948343

Title:
  Docking Station crash ramdomly after october 19 updates

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My dell D6000 dockingstation start crashing after installation of
  updates on october 19.

  Now, randomly the external HDMI monitor goes blank for 5 second until
  dock restart. But this fails make external webcam (connected to
  dockstation), and bluetooth headphones (mic at external web cam) got
  unconfigured, sending audio to the dock port and getting mic from it
  not regarding is not used, putting in a meeting without any sound.

  And because internet is also used via D6000 wired ethernet port, I got
  disconnected from VPN and RDP connections too.

  Release info:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.36
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  Uname: Linux 5.10.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 21 18:00:54 2021
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Vostro 3401
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem 
root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1050-oem N/A
   linux-backports-modules-5.10.0-1050-oem  N/A
   linux-firmware   1.187.19
  Tags:  focal
  Uname: Linux 5.10.0-1050-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2021
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0790WT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3401
  dmi.product.sku: 0A29
  dmi.sys.vendor: Dell Inc.

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


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

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

[Ignacio Nicolas Beber]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1948343/+attachment/5535240/+files/Lspci-vt.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/1948343

Title:
  Docking Station crash ramdomly after october 19 updates

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My dell D6000 dockingstation start crashing after installation of
  updates on october 19.

  Now, randomly the external HDMI monitor goes blank for 5 second until
  dock restart. But this fails make external webcam (connected to
  dockstation), and bluetooth headphones (mic at external web cam) got
  unconfigured, sending audio to the dock port and getting mic from it
  not regarding is not used, putting in a meeting without any sound.

  And because internet is also used via D6000 wired ethernet port, I got
  disconnected from VPN and RDP connections too.

  Release info:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.36
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  Uname: Linux 5.10.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 21 18:00:54 2021
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Vostro 3401
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem 
root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1050-oem N/A
   linux-backports-modules-5.10.0-1050-oem  N/A
   linux-firmware   1.187.19
  Tags:  focal
  Uname: Linux 5.10.0-1050-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2021
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0790WT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3401
  dmi.product.sku: 0A29
  dmi.sys.vendor: Dell Inc.

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


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

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

[Ignacio Nicolas Beber]

apport information

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

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

Title:
  Docking Station crash ramdomly after october 19 updates

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My dell D6000 dockingstation start crashing after installation of
  updates on october 19.

  Now, randomly the external HDMI monitor goes blank for 5 second until
  dock restart. But this fails make external webcam (connected to
  dockstation), and bluetooth headphones (mic at external web cam) got
  unconfigured, sending audio to the dock port and getting mic from it
  not regarding is not used, putting in a meeting without any sound.

  And because internet is also used via D6000 wired ethernet port, I got
  disconnected from VPN and RDP connections too.

  Release info:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.36
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  Uname: Linux 5.10.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 21 18:00:54 2021
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Vostro 3401
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem 
root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1050-oem N/A
   linux-backports-modules-5.10.0-1050-oem  N/A
   linux-firmware   1.187.19
  Tags:  focal
  Uname: Linux 5.10.0-1050-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2021
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0790WT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3401
  dmi.product.sku: 0A29
  dmi.sys.vendor: Dell Inc.

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


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

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

[Ignacio Nicolas Beber]

apport information

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

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

Title:
  Docking Station crash ramdomly after october 19 updates

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My dell D6000 dockingstation start crashing after installation of
  updates on october 19.

  Now, randomly the external HDMI monitor goes blank for 5 second until
  dock restart. But this fails make external webcam (connected to
  dockstation), and bluetooth headphones (mic at external web cam) got
  unconfigured, sending audio to the dock port and getting mic from it
  not regarding is not used, putting in a meeting without any sound.

  And because internet is also used via D6000 wired ethernet port, I got
  disconnected from VPN and RDP connections too.

  Release info:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.36
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  Uname: Linux 5.10.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 21 18:00:54 2021
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Vostro 3401
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem 
root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1050-oem N/A
   linux-backports-modules-5.10.0-1050-oem  N/A
   linux-firmware   1.187.19
  Tags:  focal
  Uname: Linux 5.10.0-1050-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2021
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0790WT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3401
  dmi.product.sku: 0A29
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1948343] RfKill.txt

[Ignacio Nicolas Beber]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1948343/+attachment/5535250/+files/RfKill.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/1948343

Title:
  Docking Station crash ramdomly after october 19 updates

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My dell D6000 dockingstation start crashing after installation of
  updates on october 19.

  Now, randomly the external HDMI monitor goes blank for 5 second until
  dock restart. But this fails make external webcam (connected to
  dockstation), and bluetooth headphones (mic at external web cam) got
  unconfigured, sending audio to the dock port and getting mic from it
  not regarding is not used, putting in a meeting without any sound.

  And because internet is also used via D6000 wired ethernet port, I got
  disconnected from VPN and RDP connections too.

  Release info:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.36
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  Uname: Linux 5.10.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 21 18:00:54 2021
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Vostro 3401
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem 
root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1050-oem N/A
   linux-backports-modules-5.10.0-1050-oem  N/A
   linux-firmware   1.187.19
  Tags:  focal
  Uname: Linux 5.10.0-1050-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2021
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0790WT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3401
  dmi.product.sku: 0A29
  dmi.sys.vendor: Dell Inc.

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


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

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

[Ignacio Nicolas Beber]

apport information

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

Title:
  Docking Station crash ramdomly after october 19 updates

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My dell D6000 dockingstation start crashing after installation of
  updates on october 19.

  Now, randomly the external HDMI monitor goes blank for 5 second until
  dock restart. But this fails make external webcam (connected to
  dockstation), and bluetooth headphones (mic at external web cam) got
  unconfigured, sending audio to the dock port and getting mic from it
  not regarding is not used, putting in a meeting without any sound.

  And because internet is also used via D6000 wired ethernet port, I got
  disconnected from VPN and RDP connections too.

  Release info:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.36
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  Uname: Linux 5.10.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 21 18:00:54 2021
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Vostro 3401
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem 
root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1050-oem N/A
   linux-backports-modules-5.10.0-1050-oem  N/A
   linux-firmware   1.187.19
  Tags:  focal
  Uname: Linux 5.10.0-1050-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2021
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0790WT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3401
  dmi.product.sku: 0A29
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1948343] Re: Docking Station crash ramdomly after october 19 updates

[Ignacio Nicolas Beber]

apport information

** Tags added: apport-collected

** Description changed:

  My dell D6000 dockingstation start crashing after installation of
  updates on october 19.
  
  Now, randomly the external HDMI monitor goes blank for 5 second until
  dock restart. But this fails make external webcam (connected to
  dockstation), and bluetooth headphones (mic at external web cam) got
  unconfigured, sending audio to the dock port and getting mic from it not
  regarding is not used, putting in a meeting without any sound.
  
  And because internet is also used via D6000 wired ethernet port, I got
  disconnected from VPN and RDP connections too.
  
  Release info:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.36
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  Uname: Linux 5.10.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 21 18:00:54 2021
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.20
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2021-08-18 (64 days ago)
+ InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
+ MachineType: Dell Inc. Vostro 3401
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem 
root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
+ RelatedPackageVersions:
+  linux-restricted-modules-5.10.0-1050-oem N/A
+  linux-backports-modules-5.10.0-1050-oem  N/A
+  linux-firmware   1.187.19
+ Tags:  focal
+ Uname: Linux 5.10.0-1050-oem x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 07/19/2021
+ dmi.bios.release: 1.8
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.8.0
+ dmi.board.name: 0790WT
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr:
+ dmi.product.family: Vostro
+ dmi.product.name: Vostro 3401
+ dmi.product.sku: 0A29
+ dmi.sys.vendor: Dell Inc.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1948343/+attachment/5535234/+files/AlsaInfo.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/1948343

Title:
  Docking Station crash ramdomly after october 19 updates

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My dell D6000 dockingstation start crashing after installation of
  updates on october 19.

  Now, randomly the external HDMI monitor goes blank for 5 second until
  dock restart. But this fails make external webcam (connected to
  dockstation), and bluetooth headphones (mic at external web cam) got
  unconfigured, sending audio to the dock port and getting mic from it
  not regarding is not used, putting in a meeting without any sound.

  And because internet is also used via D6000 wired ethernet port, I got
  disconnected from VPN and RDP connections too.

  Release info:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.36
  ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68
  Uname: Linux 5.10.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 21 18:00:54 2021
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (64 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Vostro 3401
  Package: lin

[Kernel-packages] [Bug 1948351] Re: linux ADT test_bpf failure with linux/5.4.0-90.101

[Thadeu Lima de Souza Cascardo]

Reading bionic commit 6e096fe0027f723f746f8179503784cb3579294a
("bpf/tests: Do not PASS tests without actually testing the result"),
and looking at the specific failing tests, it looks to be the case that
the test change has shown these failures starting now. Also included in
focal.

There is a JIT bug on ppc64, fixed by upstream commit 
8bbc9d822421d9ac8ff9ed26a3713c9afc69d6c8 ("powerpc/bpf: Fix BPF_MOD when imm == 
1").

Testing with userspace, eBPF works fine, possibly because the verifier
changes the code before giving it to JIT. However, cBPF fails. Both on
4.15.0-160 and 4.15.0-162, so not a regression.

Cascardo.

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

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Bionic)
   Importance: Undecided => Medium

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

Title:
  linux ADT test_bpf failure with linux/5.4.0-90.101

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress

Bug description:
  This is a scripted bug report about ADT failures while running linux
  tests for linux/5.4.0-90.101 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  
  Consistently failing on Focal/linux 5.4.0-90.101

  13:15:26 DEBUG| [stdout] # selftests: net: test_bpf.sh
  13:15:27 DEBUG| [stdout] # test_bpf: [FAIL]
  13:15:27 DEBUG| [stdout] not ok 9 selftests: net: test_bpf.sh # exit=1

  
  Testing failed on:
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20211021_141544_eda49@/log.gz

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

[Diana]

I don't know if this helps anyone, but I have the same issue with Lenovo 
ThinkPad T15 AMD Gen 2(AMD Ryzen 5 4500U with Radeon Graphics). This laptop is 
mine, and brand new, with no OS installed.
- I created a bootable flash drive with Kubuntu 2021.10, and tried to boot the 
new laptop
- It never moved from the Lenovo splashscreen after selecting Kubuntu.
- Tried a different port, didn't work either.
- I try my company Lenovo ThinkPad T580, which is an Intel setup, and it 
booted, I was able to enter and "Try Kubuntu" from the pendrive.

- So, changed the image of the flash drive for Kubuntu 2021.04, was able to 
boot in the T15 and install Kubuntu. 
- Once in Kubuntu, after updating due updates, I upgrade the OS to 2021.10: 
same error that when trying to but 2021.10: kernel panic, never leaves the 
Lenovo splash screen.

So it might be something related to the trackpad, but in the AMD setup
(Ryzen 5 4500 and Radeon Graphics), it's not happening in the Intel
Setup (i5 with intel graphics).

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  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.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1903848] Re: Latest kernel update to "5.4.0-53-generic" = Internal audio, USB webcam no longer working

[Durga madhaba Rath]

7446.610760] USB Video Class driver (1.1.1)
[ 7461.313217] usb 1-1: 3:1: cannot get freq at ep 0x82
[ 7463.017338] usb 1-1: 3:1: cannot get freq at ep 0x82
[ 7469.563231] usb 1-1: timeout: still 10 active urbs on EP #82



unable to access my usb webcam.

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

Title:
  Latest kernel update to "5.4.0-53-generic" = Internal audio, USB
  webcam no longer working

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  This seems to be a persistent problem that has been around a few
  kernel versions earlier (see i.e.:
  https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1881757 ).

  After yesterday's apt update to 5.4.0-53-generic (amd64), my USB
  webcam (Logitech c930) as well as my internal audio (Intel HDA)
  stopped working altogether. All I get is a dummy audio output from the
  list of devices, and the webcam is not working either.

  I can still see my pre-existing audio devices with

  
  'lspci | grep Audio':
  
  00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High 
Definition Audio (rev 05)
  01:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio 
Controller (rev a1)
  

  
  
  'inxi -SA' reports this:
  
  Audio:
    Device-1: Intel 5 Series/3400 Series High Definition Audio driver: N/A
    Device-2: NVIDIA GP104 High Definition Audio driver: N/A
  
  (The #2 NVIDIA one being the video card's audio option, which I don't use, 
but it's not listed as being available either.)

  
  However, i.e. 'pacmd -list-cards' says:
  
  0 card(s) available.
  

  There's been plenty of similar instances of this error in 20.04.x and
  it has been tried to have been solved in threads such as:

  #1 https://askubuntu.com/questions/1258510/only-dummy-output-sound-in-
  ubuntu-20-04-after-reboot-broken-driver-modul

  #2 https://www.linuxuprising.com/2018/06/fix-no-sound-dummy-output-
  issue-in.html

  
  From #2, if I try:
  
  'lsmod | grep snd_hda_intel'

  (That displays no results at all.)
  

  
  However, this one does bring results:

  'lspci -nnk | grep -A2 Audio'
  
  00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset 
High Definition Audio [8086:3b56] (rev 05)
DeviceName: Intel(R) High Definition Audio Device
Subsystem: Intel Corporation 5 Series/3400 Series Chipset High 
Definition Audio [8086:0034]
Kernel modules: snd_hda_intel
  00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI 
Express Root Port 1 [8086:3b42] (rev 05)
  --
  01:00.1 Audio device [0403]: NVIDIA Corporation GP104 High Definition Audio 
Controller [10de:10f0] (rev a1)
Subsystem: NVIDIA Corporation GP104 High Definition Audio Controller 
[10de:11a3]
Kernel modules: snd_hda_intel
  

  I've been trying all the available fixes at the forementioned url #2
  to no avail, and also been trying to revert them, to no avail.

  I've been trying to run ALSA's configuration and it seems that the
  ALSA modules are not loading.

  Also been trying out various fix proposals from people who've had the
  same issue, but no luck on that frontier. Anyway, now I'm stuck with
  no webcam, no audio. Any suggestions?

  Thanks.

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


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

[Kernel-packages] [Bug 1947818] Re: The fans are constantly whirring on ThinkPad P14S Gen 2

[Bin Li]

Installed the 21.10 on P14s Gen 2i, the kernel is 5.13.0-19-generic,
BIOS is N34ET44W(1.44), and EC is N34HT35W, I could not reproduce this
issue.

coretemp-isa-
Adapter: ISA adapter
Package id 0:  +29.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:+28.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:+25.0°C  (high = +100.0°C, crit = +100.0°C)
Core 2:+24.0°C  (high = +100.0°C, crit = +100.0°C)
Core 3:+24.0°C  (high = +100.0°C, crit = +100.0°C)

thinkpad-isa-
Adapter: ISA adapter
fan1:   0 RPM
CPU:  +29.0°C
GPU:  N/A
temp3:+26.0°C
temp4: +0.0°C
temp5:+28.0°C
temp6:+29.0°C
temp7:+29.0°C
temp8:N/A

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

Title:
  The fans are constantly whirring on ThinkPad P14S Gen 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The fans are constantly whirring despite next to no CPU usage, it's
  quite loud, on versions 20.04, 21.04 and 21.10 it has the same issues.

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


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

[Kernel-packages] [Bug 1948449] [NEW] package linux-image-5.11.0-37-generic (not installed) failed to install/upgrade: installed linux-image-5.11.0-37-generic package pre-removal script subprocess ret

[John Pfaff]

Public bug reported:

I'm not sure what happened - I just got a notice that something
happened.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.11.0-37-generic (not installed)
ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-38-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Oct 19 14:45:11 2021
ErrorMessage: installed linux-image-5.11.0-37-generic package pre-removal 
script subprocess returned error exit status 1
InstallationDate: Installed on 2020-07-04 (475 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: linux-signed-hwe-5.11
Title: package linux-image-5.11.0-37-generic (not installed) failed to 
install/upgrade: installed linux-image-5.11.0-37-generic package pre-removal 
script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.11 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package linux-image-5.11.0-37-generic (not installed) failed to
  install/upgrade: installed linux-image-5.11.0-37-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux-signed-hwe-5.11 package in Ubuntu:
  New

Bug description:
  I'm not sure what happened - I just got a notice that something
  happened.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-37-generic (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Oct 19 14:45:11 2021
  ErrorMessage: installed linux-image-5.11.0-37-generic package pre-removal 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2020-07-04 (475 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: linux-signed-hwe-5.11
  Title: package linux-image-5.11.0-37-generic (not installed) failed to 
install/upgrade: installed linux-image-5.11.0-37-generic package pre-removal 
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/linux-signed-hwe-5.11/+bug/1948449/+subscriptions


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

[Kernel-packages] [Bug 1947925] Re: Seagate IronWolf 125 support

[Juerg Haefliger]

Is this a problem specific to the Pi platform or ARM in general? Is the
SSD self-powered via USB or externally powered?

Also, you logged this against linux-raspi2 which seems wrong since it
doesn't support the Pi 4. Which release and kernel are you running
(lsb_release -a, uname -a)?

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

Title:
  Seagate IronWolf 125 support

Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  This is not a severe bug. (Lack of Firmware for linux on arm)

  Seagate's SSD IronWolf 125 (1TB) doesn't work reliable on the raspberry pi 4 
(connected via SATA3 to USB, (Tried out multiple SATA3 to USB Cables)).
  After the internal ssds cache is filled the ssd will be locked and is not 
accessible anymore.
  FDISK will no longer list the SSD anymore.

  The SSD is brand new and is working fine on Mac and Windows. It also works 
fine on Linux (x86).
  But Linux on arm will fail on this ssd.
  I looked up on their official site to download the firmware but there is 
actually no firmware to download.

  I once downloaded the ssd support program on windows to check its
  integrity => no hardware errors.

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


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

[Kernel-packages] [Bug 1948351] Re: linux ADT test_bpf failure with linux/5.4.0-90.101

[Po-Hsu Lin]

Tested on P8 node entei with 4.15.0-162-generic

Kernel 4.15.0-162-generic + Source 4.15.0-162-generic
[12008.662733] test_bpf: #145 ALU_MOD_K: 3 % 1 = 0 jited:1 ret 3 != 0 FAIL (1 
times)
[12008.663071] test_bpf: #148 ALU64_MOD_K: 3 % 1 = 0 jited:1 ret 3 != 0 FAIL (1 
times)
[12012.150242] test_bpf: Summary: 340 PASSED, 2 FAILED, [334/334 JIT'ed]

Note that the test environment is not clean as I don't have any
available P8 node at hand (gulpin cannot be deployed with Bionic for
some reason) so I am re-using the ubuntu_qrt_apparmor job, which is
hanging for the moment.

Also, this test output needs to be improved, I have filed bug 1948448
for this.

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

Title:
  linux ADT test_bpf failure with linux/5.4.0-90.101

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  New

Bug description:
  This is a scripted bug report about ADT failures while running linux
  tests for linux/5.4.0-90.101 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  
  Consistently failing on Focal/linux 5.4.0-90.101

  13:15:26 DEBUG| [stdout] # selftests: net: test_bpf.sh
  13:15:27 DEBUG| [stdout] # test_bpf: [FAIL]
  13:15:27 DEBUG| [stdout] not ok 9 selftests: net: test_bpf.sh # exit=1

  
  Testing failed on:
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20211021_141544_eda49@/log.gz

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


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

[Kernel-packages] [Bug 1947723] Re: /dev/ttyUSB? port lost on upgrading to 21.10

[Juerg Haefliger]

It's a new package in Impish and going forward, it doesn't exist in
older series. The reason being that we enabled a whole bunch of new
drivers in Impish and don't want to blow up the size of linux-modules.
As a result, some other non-essential drivers moved to the new package.

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

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

Title:
  /dev/ttyUSB? port lost on upgrading to 21.10

Status in linux-raspi package in Ubuntu:
  Invalid

Bug description:
  No more /dev/ttyUSB? device for RS485 USB dongle after upgrading

  lsusb -t #after upgrading
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M
  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
  |__ Port 2: Dev 3, If 0, Class=Mass Storage, Driver=uas, 5000M
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
  |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
  |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
  |__ Port 3: Dev 5, If 0, Class=Communications, Driver=, 12M
  |__ Port 3: Dev 5, If 1, Class=CDC Data, Driver=, 12M
  |__ Port 4: Dev 6, If 0, Class=Vendor Specific Class, Driver=, 12M
should see something like 
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
  |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
  |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=ch341, 
12M

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-1008-raspi 5.13.0-1008.9
  ProcVersionSignature: Ubuntu 5.13.0-1008.9-raspi 5.13.14
  Uname: Linux 5.13.0-1008-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Tue Oct 19 07:13:27 2021
  ImageMediaBuild: 20210421
  SourcePackage: linux-raspi
  UpgradeStatus: Upgraded to impish on 2021-10-19 (0 days ago)

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


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

[Kernel-packages] [Bug 1929923] Re: [UBUNTU 20.04] LPAR becomes unresponsive after the Kernel panic - rq_qos_wake_function

[Frank Heimes]

Okay, thanks Aleksandra for having a look at an env. with the latest level
and for providing feedback on this!
(so this bug is closed)

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

Title:
  [UBUNTU 20.04] LPAR becomes unresponsive after the Kernel panic -
  rq_qos_wake_function

Status in Ubuntu on IBM z Systems:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  ---Problem Description---
  kernel panic rq_qos_wake_function
   
  ---uname output---
  Linux version 5.4.0-71-generic
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  Stack trace output:
   May 15 20:21:04 data1 kernel: Call Trace:
  May 15 20:21:04 data1 kernel: ([<00234091e670>] 0x234091e670)
  May 15 20:21:04 data1 kernel:  [<003e10047e3a>] 
rq_qos_wake_function+0x8a/0xa0 
  May 15 20:21:04 data1 kernel:  [<003e0fbec482>] 
__wake_up_common+0xa2/0x1b0 
  May 15 20:21:04 data1 kernel:  [<003e0fbec984>] 
__wake_up_common_lock+0x94/0xe0 
  May 15 20:21:04 data1 kernel:  [<003e0fbec9fa>] __wake_up+0x2a/0x40 
  May 15 20:21:04 data1 kernel:  [<003e1005ee70>] wbt_done+0x90/0xe0 
  May 15 20:21:04 data1 kernel:  [<003e10047f42>] __rq_qos_done+0x42/0x60 
  May 15 20:21:04 data1 kernel:  [<003e10033cb0>] 
blk_mq_free_request+0xe0/0x140 
  May 15 20:21:04 data1 kernel:  [<003e101d46f0>] 
dm_softirq_done+0x140/0x230 
  May 15 20:21:04 data1 kernel:  [<003e100326c0>] 
blk_done_softirq+0xc0/0xe0 
  May 15 20:21:04 data1 kernel:  [<003e103fc084>] __do_softirq+0x104/0x360 
  May 15 20:21:04 data1 kernel:  [<003e0fb9da1e>] irq_exit+0x9e/0xc0 
  May 15 20:21:04 data1 kernel:  [<003e0fb28ae8>] do_IRQ+0x78/0xb0 
  May 15 20:21:04 data1 kernel:  [<003e103fb588>] 
ext_int_handler+0x130/0x134 
  May 15 20:21:04 data1 kernel:  [<003e101d4416>] dm_mq_queue_rq+0x36/0x1d0 
  May 15 20:21:04 data1 kernel: Last Breaking-Event-Address:
  May 15 20:21:04 data1 kernel:  [<003e0fbce75e>] wake_up_process+0xe/0x20
  May 15 20:21:04 data1 kernel: Kernel panic - not syncing: Fatal exception in 
interrupt
   
  Oops output:
   no
   
  System Dump Info:
The system was configured to capture a dump, however a dump was not 
produced.

  -Attach sysctl -a output output to the bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929923/+subscriptions


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

[Kernel-packages] [Bug 1929923] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From aleksandra.pa...@de.ibm.com 2021-10-22 06:55 EDT---
I have talked with our team and we have not seen the problem on the last 
supported Ubuntu level yet. So you, from our perspective, can cancel the Bug.

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

Title:
  [UBUNTU 20.04] LPAR becomes unresponsive after the Kernel panic -
  rq_qos_wake_function

Status in Ubuntu on IBM z Systems:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  ---Problem Description---
  kernel panic rq_qos_wake_function
   
  ---uname output---
  Linux version 5.4.0-71-generic
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  Stack trace output:
   May 15 20:21:04 data1 kernel: Call Trace:
  May 15 20:21:04 data1 kernel: ([<00234091e670>] 0x234091e670)
  May 15 20:21:04 data1 kernel:  [<003e10047e3a>] 
rq_qos_wake_function+0x8a/0xa0 
  May 15 20:21:04 data1 kernel:  [<003e0fbec482>] 
__wake_up_common+0xa2/0x1b0 
  May 15 20:21:04 data1 kernel:  [<003e0fbec984>] 
__wake_up_common_lock+0x94/0xe0 
  May 15 20:21:04 data1 kernel:  [<003e0fbec9fa>] __wake_up+0x2a/0x40 
  May 15 20:21:04 data1 kernel:  [<003e1005ee70>] wbt_done+0x90/0xe0 
  May 15 20:21:04 data1 kernel:  [<003e10047f42>] __rq_qos_done+0x42/0x60 
  May 15 20:21:04 data1 kernel:  [<003e10033cb0>] 
blk_mq_free_request+0xe0/0x140 
  May 15 20:21:04 data1 kernel:  [<003e101d46f0>] 
dm_softirq_done+0x140/0x230 
  May 15 20:21:04 data1 kernel:  [<003e100326c0>] 
blk_done_softirq+0xc0/0xe0 
  May 15 20:21:04 data1 kernel:  [<003e103fc084>] __do_softirq+0x104/0x360 
  May 15 20:21:04 data1 kernel:  [<003e0fb9da1e>] irq_exit+0x9e/0xc0 
  May 15 20:21:04 data1 kernel:  [<003e0fb28ae8>] do_IRQ+0x78/0xb0 
  May 15 20:21:04 data1 kernel:  [<003e103fb588>] 
ext_int_handler+0x130/0x134 
  May 15 20:21:04 data1 kernel:  [<003e101d4416>] dm_mq_queue_rq+0x36/0x1d0 
  May 15 20:21:04 data1 kernel: Last Breaking-Event-Address:
  May 15 20:21:04 data1 kernel:  [<003e0fbce75e>] wake_up_process+0xe/0x20
  May 15 20:21:04 data1 kernel: Kernel panic - not syncing: Fatal exception in 
interrupt
   
  Oops output:
   no
   
  System Dump Info:
The system was configured to capture a dump, however a dump was not 
produced.

  -Attach sysctl -a output output to the bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929923/+subscriptions


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

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

[Ubuntu Kernel Bot]

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

apport-collect 1948446

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

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

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

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

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

Title:
   failure is observed in remapping BARs 20.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu, CONFIG_PCI_REALLOC_ENABLE_AUTO config option is enabled by
  default. As a result, OS tries to remap BAR addresses and a failure is
  observed in remapping BARs.

  The issue is observed only when the SRIOV flag is disabled in BIOS.

  The issue can be worked by disabling BAR remapping bypassing
  “pci=realloc=off” kernel parameter.  It has been tested with positive
  results.

  Dmesg also shows the following messages indicating that the setting up
  of standard BAR registers for the GPGPUs has failed.

  Jun 21 06:14:47 R750XAS kernel: [   70.384361] pci :17:00.0: BAR 1: no 
space for [mem size 0x20 64bit pref]
  Jun 21 06:14:47 R750XAS kernel: [   70.476810] pci :17:00.0: BAR 1: 
failed to assign [mem size 0x20 64bit pref]
  Jun 21 06:14:47 R750XAS kernel: [   71.041877] pci :17:00.0: BAR 0: no 
space for [mem size 0x0100]
  Jun 21 06:14:47 R750XAS kernel: [   71.120838] pci :17:00.0: BAR 0: 
failed to assign [mem size 0x0100]

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


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

[Kernel-packages] [Bug 1948446] [NEW] failure is observed in remapping BARs 20.04

[prabhakar pujeri]

Public bug reported:

In Ubuntu, CONFIG_PCI_REALLOC_ENABLE_AUTO config option is enabled by
default. As a result, OS tries to remap BAR addresses and a failure is
observed in remapping BARs.

The issue is observed only when the SRIOV flag is disabled in BIOS.

The issue can be worked by disabling BAR remapping bypassing
“pci=realloc=off” kernel parameter.  It has been tested with positive
results.

Dmesg also shows the following messages indicating that the setting up
of standard BAR registers for the GPGPUs has failed.

Jun 21 06:14:47 R750XAS kernel: [   70.384361] pci :17:00.0: BAR 1: no 
space for [mem size 0x20 64bit pref]
Jun 21 06:14:47 R750XAS kernel: [   70.476810] pci :17:00.0: BAR 1: failed 
to assign [mem size 0x20 64bit pref]
Jun 21 06:14:47 R750XAS kernel: [   71.041877] pci :17:00.0: BAR 0: no 
space for [mem size 0x0100]
Jun 21 06:14:47 R750XAS kernel: [   71.120838] pci :17:00.0: BAR 0: failed 
to assign [mem size 0x0100]

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

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

Title:
   failure is observed in remapping BARs 20.04

Status in linux package in Ubuntu:
  New

Bug description:
  In Ubuntu, CONFIG_PCI_REALLOC_ENABLE_AUTO config option is enabled by
  default. As a result, OS tries to remap BAR addresses and a failure is
  observed in remapping BARs.

  The issue is observed only when the SRIOV flag is disabled in BIOS.

  The issue can be worked by disabling BAR remapping bypassing
  “pci=realloc=off” kernel parameter.  It has been tested with positive
  results.

  Dmesg also shows the following messages indicating that the setting up
  of standard BAR registers for the GPGPUs has failed.

  Jun 21 06:14:47 R750XAS kernel: [   70.384361] pci :17:00.0: BAR 1: no 
space for [mem size 0x20 64bit pref]
  Jun 21 06:14:47 R750XAS kernel: [   70.476810] pci :17:00.0: BAR 1: 
failed to assign [mem size 0x20 64bit pref]
  Jun 21 06:14:47 R750XAS kernel: [   71.041877] pci :17:00.0: BAR 0: no 
space for [mem size 0x0100]
  Jun 21 06:14:47 R750XAS kernel: [   71.120838] pci :17:00.0: BAR 0: 
failed to assign [mem size 0x0100]

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


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

[Kernel-packages] [Bug 1945632] Re: Re-enable DEBUG_INFO_BTF where it was dissabled

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
hwe-5.11/5.11.0-40.44~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.

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

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


** Tags added: verification-needed-focal

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

Title:
  Re-enable DEBUG_INFO_BTF where it was dissabled

Status in linux package in Ubuntu:
  Incomplete
Status in linux-hwe-5.11 package in Ubuntu:
  Invalid
Status in linux-hwe-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  New
Status in linux-hwe-5.11 source package in Focal:
  Fix Committed
Status in linux-hwe-5.13 source package in Focal:
  Fix Committed

Bug description:
  [Impact]

   * pahole used to segfault on 32-bit platforms, which has now been
  fixed

   * pahole used to be too old in focal, which is now being SRUed

   * renable DEBUG_INFO_BTF in all the kernels/arches that had it
  disabled, as otherwise one cannot compile/use advanced BTF features on
  newer kernels.

  
  [Test Plan]

   * Check the built kernel's config that it has CONFIG_DEBUG_INFO_BTF=y
   * Check build log that it contains
  ```
BTF .btf.vmlinux.bin.o
  ```

  [Where problems could occur]

   * In the future, kernel may require even newer version of pahole from
  dwarves, making the builds fail to build again, as building BTF debug
  information will now be required. Until either BTF is disabled again
  or pahole is upgraded again.

  [Other Info]
   
   * Latest pahole is available from focal-proposed, hirsute-proposed, impish 
release, builders-extra PPA

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


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

[Kernel-packages] [Bug 1948444] [NEW] package linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 failed to install/upgrade: installed linux-image-5.11.0-38-generic package pre-removal script subproces

[Keerthan]

Public bug reported:

I am facing open afs problem

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1
ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-38-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Oct 22 15:28:00 2021
ErrorMessage: installed linux-image-5.11.0-38-generic package pre-removal 
script subprocess returned error exit status 255
InstallationDate: Installed on 2021-05-10 (164 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: linux-signed-hwe-5.11
Title: package linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 failed to 
install/upgrade: installed linux-image-5.11.0-38-generic package pre-removal 
script subprocess returned error exit status 255
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.11 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 failed to
  install/upgrade: installed linux-image-5.11.0-38-generic package pre-
  removal script subprocess returned error exit status 255

Status in linux-signed-hwe-5.11 package in Ubuntu:
  New

Bug description:
  I am facing open afs problem

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Oct 22 15:28:00 2021
  ErrorMessage: installed linux-image-5.11.0-38-generic package pre-removal 
script subprocess returned error exit status 255
  InstallationDate: Installed on 2021-05-10 (164 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: linux-signed-hwe-5.11
  Title: package linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 failed to 
install/upgrade: installed linux-image-5.11.0-38-generic package pre-removal 
script subprocess returned error exit status 255
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1948440] [NEW] "synaptics touchpad" not detected after system update october 20th

[Aislinn Evans]

Public bug reported:

after an update the touchpad stopped working and isnt detected in
devices in the command line. laptop is lenovo V15.

i think the linux wiki told me to send you this, but i dont really
understand what im doing so that may be incorrect:

fomorii@marvin:~$ cat /proc/bus/input/devices
I: Bus=0019 Vendor= Product=0005 Version=
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
U: Uniq=
H: Handlers=event0 
B: PROP=0
B: EV=21
B: SW=1

I: Bus=0019 Vendor= Product=0001 Version=
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
U: Uniq=
H: Handlers=kbd event1 
B: PROP=0
B: EV=3
B: KEY=10 0

I: Bus=0019 Vendor= Product=0001 Version=
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
U: Uniq=
H: Handlers=kbd event2 
B: PROP=0
B: EV=3
B: KEY=10 0

I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input3
U: Uniq=
H: Handlers=sysrq kbd event3 leds 
B: PROP=0
B: EV=120013
B: KEY=40200 3803078f800d001 fedfffef fffe
B: MSC=10
B: LED=7

I: Bus=0019 Vendor= Product= Version=
N: Name="Ideapad extra buttons"
P: Phys=ideapad/input0
S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input4
U: Uniq=
H: Handlers=rfkill kbd event4 
B: PROP=0
B: EV=13
B: KEY=81000800100c03 4430 0 2
B: MSC=10

I: Bus=0003 Vendor=413c Product=3010 Version=0110
N: Name="HID 413c:3010"
P: Phys=usb-:00:14.0-1/input0
S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:413C:3010.0001/input/input5
U: Uniq=
H: Handlers=mouse0 event5 
B: PROP=0
B: EV=17
B: KEY=7 0 0 0 0
B: REL=903
B: MSC=10

I: Bus=0003 Vendor=04f2 Product=b624 Version=1428
N: Name="Integrated Camera: Integrated C"
P: Phys=usb-:00:14.0-5/button
S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input6
U: Uniq=
H: Handlers=kbd event6 
B: PROP=0
B: EV=3
B: KEY=10 0 0 0

I: Bus=0019 Vendor= Product=0006 Version=
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7
U: Uniq=
H: Handlers=kbd event7 
B: PROP=0
B: EV=3
B: KEY=3e000b 0 0 0

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8
U: Uniq=
H: Handlers=event8 
B: PROP=0
B: EV=21
B: SW=10

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input9
U: Uniq=
H: Handlers=event9 
B: PROP=0
B: EV=21
B: SW=4

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input10
U: Uniq=
H: Handlers=event10 
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH HDMI/DP,pcm=7"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11
U: Uniq=
H: Handlers=event11 
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH HDMI/DP,pcm=8"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12
U: Uniq=
H: Handlers=event12 
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH HDMI/DP,pcm=9"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13
U: Uniq=
H: Handlers=event13 
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH HDMI/DP,pcm=10"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input14
U: Uniq=
H: Handlers=event14 
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH HDMI/DP,pcm=11"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input15
U: Uniq=
H: Handlers=event15 
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH HDMI/DP,pcm=12"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input16
U: Uniq=
H: Handlers=event16 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0003 Vendor=0d8c Product=0014 Version=0100
N: Name="C-Media Electronics Inc. USB Headset"
P: Phys=usb-:00:14.0-2/input3
S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.3/0003:0D8C:0014.0002/input/input17
U: Uniq=
H: Handlers=kbd event17 
B: PROP=0
B: EV=13
B: KEY=e 0
B: MSC=10

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.11.0-38-lowlatency 5.11.0-38.42~20.04.1
ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-lowlatency 5.11.22
Uname: Linux 5.11.0-38-lowlatency x86_64
ApportVersion: 2.20.11-

[Kernel-packages] [Bug 1948436] [NEW] Add RevID field to VPD info in EEPROM

[Shravan Kumar Ramani]

Public bug reported:

SRU Justification:

[Impact]
Currently, the VPD info stored in the EEPROM does not include a Rev ID. This 
field is incremented when a PN goes through minor HW changes. Sometimes, SW 
needs to differentiate the two versions of the card. Hence, this field should 
be supported in the EEPROM MFG partition.

[Fix]
EC (Engineering Changes) field is used to denote the HW Revision of a PN. Add 
it to the EEPROM MFG and provide a sysfs entry to access the same via 
mlx-bootctl.

[Test Case]
This field is typically programmed at the manufacturing step using the bfcfg 
tool which uses the write mechanism in the driver and then the MFG partition is 
locked. Reading the "rev" sysfs will show the current value.

[Regression Potential]
Can be considered minimum.

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

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

Title:
  Add RevID field to VPD info in EEPROM

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact]
  Currently, the VPD info stored in the EEPROM does not include a Rev ID. This 
field is incremented when a PN goes through minor HW changes. Sometimes, SW 
needs to differentiate the two versions of the card. Hence, this field should 
be supported in the EEPROM MFG partition.

  [Fix]
  EC (Engineering Changes) field is used to denote the HW Revision of a PN. Add 
it to the EEPROM MFG and provide a sysfs entry to access the same via 
mlx-bootctl.

  [Test Case]
  This field is typically programmed at the manufacturing step using the bfcfg 
tool which uses the write mechanism in the driver and then the MFG partition is 
locked. Reading the "rev" sysfs will show the current value.

  [Regression Potential]
  Can be considered minimum.

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


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

[Kernel-packages] [Bug 1948351] Re: linux ADT test_bpf failure with linux/5.4.0-90.101

[Stefan Bader]

These are the BPF related changes between 5.4.0-89 and 5.4.0-90. Nothing
where I would immediately think of causing division to go wrong...

git log Ubuntu-5.4.0-89.100..origin/master-prep --grep="bpf" --oneline
760480fda833 selftests/bpf: Enlarge select() timeout for test_maps
5c85b4d0b051 selftests/bpf: Fix xdp_tx.c prog section name
0f84b7521f50 samples: bpf: Fix tracex7 error raised on the missing argument
8bc1bccb0744 bpf/tests: Do not PASS tests without actually testing the result
0885ac9bc408 bpf/tests: Fix copy-and-paste error in double word test
3801d5662248 netlink: Deal with ESRCH error in nlmsg_notify()
ed5c6f4c1b06 bpf: Fix pointer arithmetic mask tightening under state pruning
884ec8412e0d bpf: verifier: Allocate idmap scratch in verifier env
dd5342c1a35a bpf: Fix leakage due to insufficient speculative store bypass 
mitigation
5362e01b39f6 bpf: Introduce BPF nospec instruction for mitigating Spectre v4
329efcf517b2 bpf: Fix possible out of bound write in narrow load handling
9c56c222fb51 tcp: seq_file: Avoid skipping sk during tcp_seek_last_pos
481ad73a440e drm/amdgpu/acp: Make PM domain really work
42341fc22763 bpf: Fix potential memleak and UAF in the verifier.
53ace18dddea bpf: Fix a typo of reuseport map in bpf.h.
6f143214953f bpf: Fix cast to pointer from integer of different size warning
b8e3620c71b7 bpf: Track contents of read-only maps as scalars

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

Title:
  linux ADT test_bpf failure with linux/5.4.0-90.101

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  New

Bug description:
  This is a scripted bug report about ADT failures while running linux
  tests for linux/5.4.0-90.101 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  
  Consistently failing on Focal/linux 5.4.0-90.101

  13:15:26 DEBUG| [stdout] # selftests: net: test_bpf.sh
  13:15:27 DEBUG| [stdout] # test_bpf: [FAIL]
  13:15:27 DEBUG| [stdout] not ok 9 selftests: net: test_bpf.sh # exit=1

  
  Testing failed on:
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20211021_141544_eda49@/log.gz

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


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

[Kernel-packages] [Bug 1948434] [NEW] Check if secure boot is enabled with development keys

[Shravan Kumar Ramani]

Public bug reported:

SRU Justification:

[Impact]
Currently, there is no indication from mlx-bootctl when the user reads the 
lifecycle_state sysfs as to whether secure boot is enabled with development 
keys or production keys. In order to make this clear to the user, add a check 
in the driver.

[Fix]
Check the secure boot development mode status bit. If secure boot is enabled 
with the development key, then print it to the output buffer when 
lifecycle_state_show() is invoked.

[Test Case]
On a system in secure state, if it has been programmed with development keys, 
then reading the lifecycle_state sysfs entry in the mlx-bootctl driver should 
print a message that indicates the same.
Similarly, a secure system which has been programmed with production keys must 
print the appropriate message when the lifecycle_state sysfs is read.

[Regression Potential]
Can be considered minimum.

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

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

Title:
  Check if secure boot is enabled with development keys

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact]
  Currently, there is no indication from mlx-bootctl when the user reads the 
lifecycle_state sysfs as to whether secure boot is enabled with development 
keys or production keys. In order to make this clear to the user, add a check 
in the driver.

  [Fix]
  Check the secure boot development mode status bit. If secure boot is enabled 
with the development key, then print it to the output buffer when 
lifecycle_state_show() is invoked.

  [Test Case]
  On a system in secure state, if it has been programmed with development keys, 
then reading the lifecycle_state sysfs entry in the mlx-bootctl driver should 
print a message that indicates the same.
  Similarly, a secure system which has been programmed with production keys 
must print the appropriate message when the lifecycle_state sysfs is read.

  [Regression Potential]
  Can be considered minimum.

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


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

[Kernel-packages] [Bug 1947311] Re: Cloud init ignores growpart off on impish for raspberry pi

[Noah]

Thanks, that's a good suggestion, but it didn't work.

Can I just reassign this ticket to the linux-raspi project?

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

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

Title:
  Cloud init ignores growpart off on impish for raspberry pi

Status in cloud-init package in Ubuntu:
  Incomplete
Status in linux-raspi package in Ubuntu:
  New

Bug description:
  Hi,

  On Raspberry Pi since Impish, the partition always grows even if I set
  the following in user-data of cloud-init.

  growpart:
mode: off
devices: ['/']

  I have tested this on 21.04, and it works, but is broken on 21.10.
  (partition always grows)

  I've also tested this in KVM on amd64, and it works (partition does
  NOT grow).

  This is a problem for me because I am using runcmd in cloud init to
  migrate my drive to LVM/LUKS, and the partitioning step fails because
  the drive is already full.

  Cheers,
  Noah

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+subscriptions


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

[Kernel-packages] [Bug 1948351] Re: linux ADT test_bpf failure with linux/5.4.0-90.101

[Po-Hsu Lin]

BTW here is the test summary, it looks like we have 2 cases removed in
5.4.0-90. (in lib/test

Test results:
* Kernel: 5.4.0-89 + Source: 5.4.0-89 = Summary: 378 PASSED, 0 FAILED, [366/366 
JIT'ed]
* Kernel: 5.4.0-89 + Source: 5.4.0-90 = Summary: 378 PASSED, 0 FAILED, [366/366 
JIT'ed]
* Kernel: 5.4.0-90 + Source: 5.4.0-90 = Summary: 376 PASSED, 2 FAILED, [366/366 
JIT'ed]
* Kernel: 5.4.0-90 + Source: 5.4.0-89 = Summary: 376 PASSED, 2 FAILED, [366/366 
JIT'ed]


** Also affects: linux (Ubuntu Focal)
   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/1948351

Title:
  linux ADT test_bpf failure with linux/5.4.0-90.101

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  New

Bug description:
  This is a scripted bug report about ADT failures while running linux
  tests for linux/5.4.0-90.101 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  
  Consistently failing on Focal/linux 5.4.0-90.101

  13:15:26 DEBUG| [stdout] # selftests: net: test_bpf.sh
  13:15:27 DEBUG| [stdout] # test_bpf: [FAIL]
  13:15:27 DEBUG| [stdout] not ok 9 selftests: net: test_bpf.sh # exit=1

  
  Testing failed on:
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20211021_141544_eda49@/log.gz

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


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

[Kernel-packages] [Bug 1948377] Re: [linux-iot][F] USB: serial: pl2303: add support for PL2303HXN

[AaronMa]

** Description changed:

  [Impact]
  PL2303HXN is not supported by 5.4 kernel.
- 5.5 kernel starts to support it.
+ 5.5 kernel starts to support it. so only SRU for focal 5.4 kernel.
  
  [Fix]
  Add support for PL2303HXN.
  
  [Test]
  Verified on hardware, use minicom to test serial port, it works fine.
  
  [Where problems could occur]
  It may break the pl2303 ttyUSBx.

** Changed in: linux (Ubuntu Focal)
 Assignee: Jesse Sung (wenchien) => (unassigned)

** Summary changed:

- [linux-iot][F] USB: serial: pl2303: add support for PL2303HXN
+ [SRU][F] USB: serial: pl2303: add support for PL2303HXN

** Description changed:

  [Impact]
  PL2303HXN is not supported by 5.4 kernel.
  5.5 kernel starts to support it. so only SRU for focal 5.4 kernel.
  
  [Fix]
+ Clean cherry-pick upstream commits.
  Add support for PL2303HXN.
  
  [Test]
  Verified on hardware, use minicom to test serial port, it works fine.
  
  [Where problems could occur]
  It may break the pl2303 ttyUSBx.

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

Title:
  [SRU][F] USB: serial: pl2303: add support for PL2303HXN

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress

Bug description:
  [Impact]
  PL2303HXN is not supported by 5.4 kernel.
  5.5 kernel starts to support it. so only SRU for focal 5.4 kernel.

  [Fix]
  Clean cherry-pick upstream commits.
  Add support for PL2303HXN.

  [Test]
  Verified on hardware, use minicom to test serial port, it works fine.

  [Where problems could occur]
  It may break the pl2303 ttyUSBx.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1948377/+subscriptions


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

[Kernel-packages] [Bug 1835340] Re: [HMEM] kmem: clear poison reported via mce or ACPI patrol scrub notifications

[Gongjun Song]

** Description changed:

  Description:
  
  During run-time, the kernel can be notified of new/latent errors in two
  different ways:
  
  If an application trips over a latent/unknown error, and if the system has 
machine check recovery, then we will be notified via the mce handler, and the 
app will be killed. In this case, the kernel should take the chance to go 
clear-errors for that page, and re-online it so it can be used again in the 
future.
  If the 'patrol scrubber' discovers an error on a yet-to-be-accessed location, 
it can send an ACPI notification to the nfit driver. In this case, the kernel 
should go clear the error if the page is not in use. If it is in use, the 
application that has it mapped may need to killed as in case 1 above.
  This additional run-time handling of errors will augment (and be 
complimentary to) the init-time handling in userspace, and having both will 
give us the best possible coverage for media errors.
  
- Target Release: 21.10
+ Target Release: 22.04
  Target Kernel: TBD

** Tags removed: intel-kernel-21.10
** Tags added: intel-kernel-22.04

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

Title:
  [HMEM] kmem: clear poison reported via mce or ACPI patrol scrub
  notifications

Status in intel:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:

  During run-time, the kernel can be notified of new/latent errors in
  two different ways:

  If an application trips over a latent/unknown error, and if the system has 
machine check recovery, then we will be notified via the mce handler, and the 
app will be killed. In this case, the kernel should take the chance to go 
clear-errors for that page, and re-online it so it can be used again in the 
future.
  If the 'patrol scrubber' discovers an error on a yet-to-be-accessed location, 
it can send an ACPI notification to the nfit driver. In this case, the kernel 
should go clear the error if the page is not in use. If it is in use, the 
application that has it mapped may need to killed as in case 1 above.
  This additional run-time handling of errors will augment (and be 
complimentary to) the init-time handling in userspace, and having both will 
give us the best possible coverage for media errors.

  Target Release: 22.04
  Target Kernel: TBD

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


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