[Kernel-packages] [Bug 1822633] Re: Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1a56:1535] Pairing failure with BLE 4.0
** Summary changed:
- Pairing failure with BLE 4.0
+ Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1a56:1535] Pairing failure
with BLE 4.0
--
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/1822633
Title:
Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1a56:1535] Pairing
failure with BLE 4.0
Status in bluez package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
When attempting to pair a BLE 4.0 pen using Bluez, we receive
authentication errors.
Here is the FW from Jason.
Details:
===
I added a few debug statements (patch attached) to the kernel's
net/bluetooth/smp.c:smp_sig_channel() function
(https://github.com/torvalds/linux/blob/v5.0/net/bluetooth/smp.c#L2883).
When I try to pair the PN579X, I get the following logs:
[ 5653.563048] DBG: Received code 2 (allowed = 0024) with 6 bytes
[ 5653.563053] DBG: Processing code...
[ 5653.709572] DBG: Received code 3 (allowed = 0028) with 16 bytes
[ 5653.709577] DBG: Processing code...
[ 5653.807085] DBG: Received code 4 (allowed = 0030) with 16 bytes
[ 5653.807089] DBG: Processing code...
[ 5654.148553] DBG: Received code 6 (allowed = 0060) with 16 bytes
[ 5654.148557] DBG: Processing code...
[ 5654.197024] DBG: Received code 7 (allowed = 00a0) with 10 bytes
[ 5654.197027] DBG: Processing code...
[ 5654.245824] DBG: Received code 8 (allowed = 0120) with 16 bytes
[ 5654.245828] DBG: Processing code...
[ 5654.246178] DBG: Received code 9 (allowed = 0220) with 7 bytes
[ 5654.246182] DBG: Processing code...
[ 5657.610656] input: Dell Active Pen PN579X Keyboard as
/devices/virtual/misc/uhid/0005:413C:81D5.0004/input/input23
[ 5657.610997] hid-generic 0005:413C:81D5.0004: input,hidraw0: BLUETOOTH HID
vf.08 Keyboard [Dell Active Pen PN579X] on 18:56:80:18:6A:E5
When I try to pair the PN557W, however, I only get the following:
[ 64.924901] DBG: Received code 11 (allowed = 0024) with 1 bytes
[ 64.924906] DBG: AuthReq = 00
[ 64.924907] ERR: Code not allowed on existing connection
[ 64.924943] Bluetooth: hci0: unexpected SMP command 0x0b from
bc:82:5d:fa:5e:b7
[ 64.940314] NET: Registered protocol family 38
[ 65.022326] DBG: Received code 5 (allowed = 0024) with 1 bytes
[ 65.022331] DBG: Processing code...
The "allowed" value is a bitmap, so 0024 means that only event
code 2 and 5 are allowed. The "smp_sig_channel()" function does allow
code 11 ("SMP_CMD_SECURITY_REQ") to be sent from the device at the
beginning of the connection but *only* if the "smp" variable hasn't
been set yet. It looks like the host starts the pairing process and
initializes the "smp" variable, which then prevents code 11 from being
allowed.
I did try to force the code to allow code 11 at any time, but this
didn't seem to help the situation any. The device still sent code 5
("SMP_CMD_PAIRING_FAIL") immediately afterwards, just like it does in
the trace above. Worse, the kernel logs a general protection fault
several seconds afterwards, so it clearly doesn't like the workaround.
I also find it odd that the "AuthReq = 00". I found a copy of the core
Bluetooth spec at https://www.bluetooth.com/specifications/bluetooth-
core-specification and Vol. 3 Part H Chapter 3.6.7 describes the
AuthReq flags. All zero would seem to indicate that no security is
requested, and I'm not sure if the kernel enforces a minimum security
level or something.
Finally, I also tried the suggestion at
https://www.raymondjdouglas.com/blog/2019/airpods-on-arch/ on the assumption
that maybe this is an issue caused by LE communication rather than classic
BR/EDR communication. Alas, my computer wasn't even able to start the pairing
process after making the change.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-01-21 (70 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
InterestingModules: bnep btusb bluetooth
MachineType: Dell Inc. XPS 13 9360
Package: linux
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic
root=UUID=c045330d-1b98-41ff-99cb-26bf69b59fd3 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Tags: third-party-packages bionic
Uname: Linux 4.15.0-46-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambash
[Kernel-packages] [Bug 1822633] Re: Pairing failure with BLE 4.0
** Tags added: hwe-networking-wifi
** Tags removed: hwe-networking-wifi
** Tags added: hwe-bluetooth
--
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/1822633
Title:
Pairing failure with BLE 4.0
Status in bluez package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
When attempting to pair a BLE 4.0 pen using Bluez, we receive
authentication errors.
Here is the FW from Jason.
Details:
===
I added a few debug statements (patch attached) to the kernel's
net/bluetooth/smp.c:smp_sig_channel() function
(https://github.com/torvalds/linux/blob/v5.0/net/bluetooth/smp.c#L2883).
When I try to pair the PN579X, I get the following logs:
[ 5653.563048] DBG: Received code 2 (allowed = 0024) with 6 bytes
[ 5653.563053] DBG: Processing code...
[ 5653.709572] DBG: Received code 3 (allowed = 0028) with 16 bytes
[ 5653.709577] DBG: Processing code...
[ 5653.807085] DBG: Received code 4 (allowed = 0030) with 16 bytes
[ 5653.807089] DBG: Processing code...
[ 5654.148553] DBG: Received code 6 (allowed = 0060) with 16 bytes
[ 5654.148557] DBG: Processing code...
[ 5654.197024] DBG: Received code 7 (allowed = 00a0) with 10 bytes
[ 5654.197027] DBG: Processing code...
[ 5654.245824] DBG: Received code 8 (allowed = 0120) with 16 bytes
[ 5654.245828] DBG: Processing code...
[ 5654.246178] DBG: Received code 9 (allowed = 0220) with 7 bytes
[ 5654.246182] DBG: Processing code...
[ 5657.610656] input: Dell Active Pen PN579X Keyboard as
/devices/virtual/misc/uhid/0005:413C:81D5.0004/input/input23
[ 5657.610997] hid-generic 0005:413C:81D5.0004: input,hidraw0: BLUETOOTH HID
vf.08 Keyboard [Dell Active Pen PN579X] on 18:56:80:18:6A:E5
When I try to pair the PN557W, however, I only get the following:
[ 64.924901] DBG: Received code 11 (allowed = 0024) with 1 bytes
[ 64.924906] DBG: AuthReq = 00
[ 64.924907] ERR: Code not allowed on existing connection
[ 64.924943] Bluetooth: hci0: unexpected SMP command 0x0b from
bc:82:5d:fa:5e:b7
[ 64.940314] NET: Registered protocol family 38
[ 65.022326] DBG: Received code 5 (allowed = 0024) with 1 bytes
[ 65.022331] DBG: Processing code...
The "allowed" value is a bitmap, so 0024 means that only event
code 2 and 5 are allowed. The "smp_sig_channel()" function does allow
code 11 ("SMP_CMD_SECURITY_REQ") to be sent from the device at the
beginning of the connection but *only* if the "smp" variable hasn't
been set yet. It looks like the host starts the pairing process and
initializes the "smp" variable, which then prevents code 11 from being
allowed.
I did try to force the code to allow code 11 at any time, but this
didn't seem to help the situation any. The device still sent code 5
("SMP_CMD_PAIRING_FAIL") immediately afterwards, just like it does in
the trace above. Worse, the kernel logs a general protection fault
several seconds afterwards, so it clearly doesn't like the workaround.
I also find it odd that the "AuthReq = 00". I found a copy of the core
Bluetooth spec at https://www.bluetooth.com/specifications/bluetooth-
core-specification and Vol. 3 Part H Chapter 3.6.7 describes the
AuthReq flags. All zero would seem to indicate that no security is
requested, and I'm not sure if the kernel enforces a minimum security
level or something.
Finally, I also tried the suggestion at
https://www.raymondjdouglas.com/blog/2019/airpods-on-arch/ on the assumption
that maybe this is an issue caused by LE communication rather than classic
BR/EDR communication. Alas, my computer wasn't even able to start the pairing
process after making the change.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-01-21 (70 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
InterestingModules: bnep btusb bluetooth
MachineType: Dell Inc. XPS 13 9360
Package: linux
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic
root=UUID=c045330d-1b98-41ff-99cb-26bf69b59fd3 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Tags: third-party-packages bionic
Uname: Linux 4.15.0-46-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/24/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.ve
[Kernel-packages] [Bug 1870994] Re: "*BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg
[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/1870994 Title: "*BAD*gran_size: 64Kchunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg Status in linux package in Ubuntu: Expired Bug description: While looking at the attached dmesg which comes from an up-to-date eoan, I found certain lines containing *BAD* and "can not find optimal value", "please specify...". For me, they are just intimidating printfs. Should I get worried? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867534] Re: Wifi requires interruption before timing out (and immediate reconnect attempt succeeds)
** Tags added: hwe-networking-wifi ** Summary changed: - Wifi requires interruption before timing out (and immediate reconnect attempt succeeds) + Intel Wireless 7260 [8086:08b2] Subsystem [8086:4262] Wifi requires interruption before timing out (and immediate reconnect attempt succeeds) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867534 Title: Intel Wireless 7260 [8086:08b2] Subsystem [8086:4262] Wifi requires interruption before timing out (and immediate reconnect attempt succeeds) Status in linux package in Ubuntu: Confirmed Bug description: ISO testing 20.04 Lubuntu daily (20200315). From the Live desktop, I click my nm-tray access point, supply the password. nm-tray will timeout. Trying again will timeout. What works is clicking the same access point a couple times before it times out. This causes an immediate failure and successful connection (two balloon msgs). This problem is not specific to Lubuntu. It happens with Kubuntu, Budgie, Mate, Xubuntu. The common theme is: it appears to be out of sync in some manner. The wifi connection needs to be interrupted before timing out. Then an immediate attempt (within 2-3 seconds? I haven't tested how long it can wait) succeeds. This problem also happens after install and reboot. For example, with yesterday's daily image (20200314), I had to reboot Lubuntu twice after install before the wifi worked. (I haven't reached that point yet today. I'm creating this bug report from the Live desktop. I will update with more info about post-install.). Note: I don't know if this is acceptable wifi behavior. Good enough? I figured I should report it and let someone decide. It seems to be specific to this laptop (Lenovo Thinkpad E440 20C5) or it's Intel 7260 wifi card. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lubuntu1857 F pulseaudio /dev/snd/controlC0: lubuntu1857 F pulseaudio CasperVersion: 1.441 Date: Sun Mar 15 17:17:43 2020 LiveMediaBuild: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: LENOVO 20C5004YUS ProcFB: 0 i915drmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 SourcePackage: linux-5.4 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: J9ETA2WW (2.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C5004YUS dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ9ETA2WW(2.28):bd06/20/2018:svnLENOVO:pn20C5004YUS:pvrThinkPadEdgeE440:rvnLENOVO:rn20C5004YUS:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Edge E440 dmi.product.name: 20C5004YUS dmi.product.sku: LENOVO_MT_20C5_BU_Think_FM_ThinkPad Edge E440 dmi.product.version: ThinkPad Edge E440 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
I've tried Ubuntu 20.04 (5.4.0-33-generic) hoping it will be better. But it's not the case; i've encoutered the problem quickly, even without using Kodi for stressing the GPU. Here the problem froze completly the system; hard reboot is the only way out. Will come back to Ubuntu 18.04 and 5.3.0-53 generic. For info, here is the syslog with the problem: Jun 5 18:28:41 hystKodi3 systemd-udevd[343]: Worker [2067] terminated by signal 11 (SEGV) Jun 5 18:28:44 hystKodi3 PackageKit: daemon quit Jun 5 18:28:44 hystKodi3 systemd[1]: packagekit.service: Succeeded. Jun 5 18:28:45 hystKodi3 kernel: [ 317.504521] i915 :00:10.0: GPU HANG: ecode 9:1:0x, hang on rcs0 Jun 5 18:28:45 hystKodi3 kernel: [ 317.505529] i915 :00:10.0: Resetting rcs0 for hang on rcs0 Jun 5 18:28:48 hystKodi3 systemd-udevd[2100]: free(): invalid next size (fast) Jun 5 18:28:48 hystKodi3 systemd-udevd[343]: Worker [2100] terminated by signal 6 (ABRT) Jun 5 18:28:53 hystKodi3 kernel: [ 325.505416] i915 :00:10.0: Resetting rcs0 for hang on rcs0 Jun 5 18:30:01 hystKodi3 CRON[2110]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Fix Released Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 Hibernation
[Kernel-packages] [Bug 1882312] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1882312/+attachment/5380830/+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/1882312 Title: RAID5 reshape stuck due to same badblock on multiple devices Status in linux package in Ubuntu: Confirmed Bug description: Linux [hostname removed] 5.3.0-55-generic #49-Ubuntu SMP Thu May 21 12:47:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Ubuntu release: 19.10 (although the same issue is present in 18.04 and 20.04 as well). A RAID5 reshape from 3 to 4 devices got stuck: md127 : active raid5 sde1[5] sdd1[4] sdc1[0] sdf1[3] 7813769216 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [] [>] reshape = 1.8% (72261116/3906884608) finish=1663133.7min speed=38K/sec bitmap: 0/30 pages [0KB], 65536KB chunk with the following stack trace: [54979.996871] INFO: task md127_reshape:7090 blocked for more than 1208 seconds. [54979.996922] Tainted: P OE 5.3.0-55-generic #49-Ubuntu [54979.996967] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [54979.997018] md127_reshape D0 7090 2 0x80004080 [54979.997019] Call Trace: [54979.997022] __schedule+0x2b9/0x6c0 [54979.997023] schedule+0x42/0xb0 [54979.997027] reshape_request+0x878/0x950 [raid456] [54979.997028] ? wait_woken+0x80/0x80 [54979.997030] raid5_sync_request+0x302/0x3b0 [raid456] [54979.997032] md_do_sync.cold+0x3ef/0x999 [54979.997034] ? ecryptfs_write_begin+0x70/0x280 [54979.997034] ? __switch_to_asm+0x40/0x70 [54979.997035] ? __switch_to_asm+0x34/0x70 [54979.997035] ? __switch_to_asm+0x40/0x70 [54979.997036] ? __switch_to_asm+0x34/0x70 [54979.997036] ? __switch_to_asm+0x40/0x70 [54979.997037] ? __switch_to_asm+0x34/0x70 [54979.997038] md_thread+0x97/0x160 [54979.997040] kthread+0x104/0x140 [54979.997040] ? md_start_sync+0x60/0x60 [54979.997041] ? kthread_park+0x80/0x80 [54979.997042] ret_from_fork+0x35/0x40 No other hardware errors were reported and the reshape got stuck at somewhat different blocks every time it was restarted (all within the same vicinity of each others). It turns out that md had injected the same exact sector into the badblock log of multiple devices at some point before the reshape was started. This could be seen with "mdadm --examine-badblocks /dev/sdXY". The original cause for the badblocks entries was probably a loose cable as the reported sectors were fully readable with the "dd" and "badblocks" command. The problem was eventually resolved by removing the badblock log on the RAID5 device using "mdadm --assemble /dev/md0 --update=force-no- bbl". Having removed the badblock log, reshape progressed beyond the previously troublesome area of blocks. I would have expected at least an error message in the kernel log rather than just a "hung task" message, probably before the reshape was allowed to be initiated (aka early termination). Furthermore, it would be beneficial if mdadm could allow the badblock log to be cleared for a device rather than removed on the array with "update=force-no-bbl". --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.3.0-55-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=/dev/mapper/vg0-swap IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-
[Kernel-packages] [Bug 1882312] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1882312/+attachment/5380831/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882312 Title: RAID5 reshape stuck due to same badblock on multiple devices Status in linux package in Ubuntu: Confirmed Bug description: Linux [hostname removed] 5.3.0-55-generic #49-Ubuntu SMP Thu May 21 12:47:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Ubuntu release: 19.10 (although the same issue is present in 18.04 and 20.04 as well). A RAID5 reshape from 3 to 4 devices got stuck: md127 : active raid5 sde1[5] sdd1[4] sdc1[0] sdf1[3] 7813769216 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [] [>] reshape = 1.8% (72261116/3906884608) finish=1663133.7min speed=38K/sec bitmap: 0/30 pages [0KB], 65536KB chunk with the following stack trace: [54979.996871] INFO: task md127_reshape:7090 blocked for more than 1208 seconds. [54979.996922] Tainted: P OE 5.3.0-55-generic #49-Ubuntu [54979.996967] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [54979.997018] md127_reshape D0 7090 2 0x80004080 [54979.997019] Call Trace: [54979.997022] __schedule+0x2b9/0x6c0 [54979.997023] schedule+0x42/0xb0 [54979.997027] reshape_request+0x878/0x950 [raid456] [54979.997028] ? wait_woken+0x80/0x80 [54979.997030] raid5_sync_request+0x302/0x3b0 [raid456] [54979.997032] md_do_sync.cold+0x3ef/0x999 [54979.997034] ? ecryptfs_write_begin+0x70/0x280 [54979.997034] ? __switch_to_asm+0x40/0x70 [54979.997035] ? __switch_to_asm+0x34/0x70 [54979.997035] ? __switch_to_asm+0x40/0x70 [54979.997036] ? __switch_to_asm+0x34/0x70 [54979.997036] ? __switch_to_asm+0x40/0x70 [54979.997037] ? __switch_to_asm+0x34/0x70 [54979.997038] md_thread+0x97/0x160 [54979.997040] kthread+0x104/0x140 [54979.997040] ? md_start_sync+0x60/0x60 [54979.997041] ? kthread_park+0x80/0x80 [54979.997042] ret_from_fork+0x35/0x40 No other hardware errors were reported and the reshape got stuck at somewhat different blocks every time it was restarted (all within the same vicinity of each others). It turns out that md had injected the same exact sector into the badblock log of multiple devices at some point before the reshape was started. This could be seen with "mdadm --examine-badblocks /dev/sdXY". The original cause for the badblocks entries was probably a loose cable as the reported sectors were fully readable with the "dd" and "badblocks" command. The problem was eventually resolved by removing the badblock log on the RAID5 device using "mdadm --assemble /dev/md0 --update=force-no- bbl". Having removed the badblock log, reshape progressed beyond the previously troublesome area of blocks. I would have expected at least an error message in the kernel log rather than just a "hung task" message, probably before the reshape was allowed to be initiated (aka early termination). Furthermore, it would be beneficial if mdadm could allow the badblock log to be cleared for a device rather than removed on the array with "update=force-no-bbl". --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.3.0-55-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=/dev/mapper/vg0-swap IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-55-gen
[Kernel-packages] [Bug 1882312] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1882312/+attachment/5380833/+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/1882312 Title: RAID5 reshape stuck due to same badblock on multiple devices Status in linux package in Ubuntu: Confirmed Bug description: Linux [hostname removed] 5.3.0-55-generic #49-Ubuntu SMP Thu May 21 12:47:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Ubuntu release: 19.10 (although the same issue is present in 18.04 and 20.04 as well). A RAID5 reshape from 3 to 4 devices got stuck: md127 : active raid5 sde1[5] sdd1[4] sdc1[0] sdf1[3] 7813769216 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [] [>] reshape = 1.8% (72261116/3906884608) finish=1663133.7min speed=38K/sec bitmap: 0/30 pages [0KB], 65536KB chunk with the following stack trace: [54979.996871] INFO: task md127_reshape:7090 blocked for more than 1208 seconds. [54979.996922] Tainted: P OE 5.3.0-55-generic #49-Ubuntu [54979.996967] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [54979.997018] md127_reshape D0 7090 2 0x80004080 [54979.997019] Call Trace: [54979.997022] __schedule+0x2b9/0x6c0 [54979.997023] schedule+0x42/0xb0 [54979.997027] reshape_request+0x878/0x950 [raid456] [54979.997028] ? wait_woken+0x80/0x80 [54979.997030] raid5_sync_request+0x302/0x3b0 [raid456] [54979.997032] md_do_sync.cold+0x3ef/0x999 [54979.997034] ? ecryptfs_write_begin+0x70/0x280 [54979.997034] ? __switch_to_asm+0x40/0x70 [54979.997035] ? __switch_to_asm+0x34/0x70 [54979.997035] ? __switch_to_asm+0x40/0x70 [54979.997036] ? __switch_to_asm+0x34/0x70 [54979.997036] ? __switch_to_asm+0x40/0x70 [54979.997037] ? __switch_to_asm+0x34/0x70 [54979.997038] md_thread+0x97/0x160 [54979.997040] kthread+0x104/0x140 [54979.997040] ? md_start_sync+0x60/0x60 [54979.997041] ? kthread_park+0x80/0x80 [54979.997042] ret_from_fork+0x35/0x40 No other hardware errors were reported and the reshape got stuck at somewhat different blocks every time it was restarted (all within the same vicinity of each others). It turns out that md had injected the same exact sector into the badblock log of multiple devices at some point before the reshape was started. This could be seen with "mdadm --examine-badblocks /dev/sdXY". The original cause for the badblocks entries was probably a loose cable as the reported sectors were fully readable with the "dd" and "badblocks" command. The problem was eventually resolved by removing the badblock log on the RAID5 device using "mdadm --assemble /dev/md0 --update=force-no- bbl". Having removed the badblock log, reshape progressed beyond the previously troublesome area of blocks. I would have expected at least an error message in the kernel log rather than just a "hung task" message, probably before the reshape was allowed to be initiated (aka early termination). Furthermore, it would be beneficial if mdadm could allow the badblock log to be cleared for a device rather than removed on the array with "update=force-no-bbl". --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.3.0-55-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=/dev/mapper/vg0-swap IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-55-gener
[Kernel-packages] [Bug 1882312] Card0.Codecs.codec.2.txt
apport information ** Attachment added: "Card0.Codecs.codec.2.txt" https://bugs.launchpad.net/bugs/1882312/+attachment/5380825/+files/Card0.Codecs.codec.2.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/1882312 Title: RAID5 reshape stuck due to same badblock on multiple devices Status in linux package in Ubuntu: Confirmed Bug description: Linux [hostname removed] 5.3.0-55-generic #49-Ubuntu SMP Thu May 21 12:47:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Ubuntu release: 19.10 (although the same issue is present in 18.04 and 20.04 as well). A RAID5 reshape from 3 to 4 devices got stuck: md127 : active raid5 sde1[5] sdd1[4] sdc1[0] sdf1[3] 7813769216 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [] [>] reshape = 1.8% (72261116/3906884608) finish=1663133.7min speed=38K/sec bitmap: 0/30 pages [0KB], 65536KB chunk with the following stack trace: [54979.996871] INFO: task md127_reshape:7090 blocked for more than 1208 seconds. [54979.996922] Tainted: P OE 5.3.0-55-generic #49-Ubuntu [54979.996967] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [54979.997018] md127_reshape D0 7090 2 0x80004080 [54979.997019] Call Trace: [54979.997022] __schedule+0x2b9/0x6c0 [54979.997023] schedule+0x42/0xb0 [54979.997027] reshape_request+0x878/0x950 [raid456] [54979.997028] ? wait_woken+0x80/0x80 [54979.997030] raid5_sync_request+0x302/0x3b0 [raid456] [54979.997032] md_do_sync.cold+0x3ef/0x999 [54979.997034] ? ecryptfs_write_begin+0x70/0x280 [54979.997034] ? __switch_to_asm+0x40/0x70 [54979.997035] ? __switch_to_asm+0x34/0x70 [54979.997035] ? __switch_to_asm+0x40/0x70 [54979.997036] ? __switch_to_asm+0x34/0x70 [54979.997036] ? __switch_to_asm+0x40/0x70 [54979.997037] ? __switch_to_asm+0x34/0x70 [54979.997038] md_thread+0x97/0x160 [54979.997040] kthread+0x104/0x140 [54979.997040] ? md_start_sync+0x60/0x60 [54979.997041] ? kthread_park+0x80/0x80 [54979.997042] ret_from_fork+0x35/0x40 No other hardware errors were reported and the reshape got stuck at somewhat different blocks every time it was restarted (all within the same vicinity of each others). It turns out that md had injected the same exact sector into the badblock log of multiple devices at some point before the reshape was started. This could be seen with "mdadm --examine-badblocks /dev/sdXY". The original cause for the badblocks entries was probably a loose cable as the reported sectors were fully readable with the "dd" and "badblocks" command. The problem was eventually resolved by removing the badblock log on the RAID5 device using "mdadm --assemble /dev/md0 --update=force-no- bbl". Having removed the badblock log, reshape progressed beyond the previously troublesome area of blocks. I would have expected at least an error message in the kernel log rather than just a "hung task" message, probably before the reshape was allowed to be initiated (aka early termination). Furthermore, it would be beneficial if mdadm could allow the badblock log to be cleared for a device rather than removed on the array with "update=force-no-bbl". --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.3.0-55-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=/dev/mapper/vg0-swap IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vm
[Kernel-packages] [Bug 1882312] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1882312/+attachment/5380826/+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/1882312 Title: RAID5 reshape stuck due to same badblock on multiple devices Status in linux package in Ubuntu: Confirmed Bug description: Linux [hostname removed] 5.3.0-55-generic #49-Ubuntu SMP Thu May 21 12:47:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Ubuntu release: 19.10 (although the same issue is present in 18.04 and 20.04 as well). A RAID5 reshape from 3 to 4 devices got stuck: md127 : active raid5 sde1[5] sdd1[4] sdc1[0] sdf1[3] 7813769216 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [] [>] reshape = 1.8% (72261116/3906884608) finish=1663133.7min speed=38K/sec bitmap: 0/30 pages [0KB], 65536KB chunk with the following stack trace: [54979.996871] INFO: task md127_reshape:7090 blocked for more than 1208 seconds. [54979.996922] Tainted: P OE 5.3.0-55-generic #49-Ubuntu [54979.996967] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [54979.997018] md127_reshape D0 7090 2 0x80004080 [54979.997019] Call Trace: [54979.997022] __schedule+0x2b9/0x6c0 [54979.997023] schedule+0x42/0xb0 [54979.997027] reshape_request+0x878/0x950 [raid456] [54979.997028] ? wait_woken+0x80/0x80 [54979.997030] raid5_sync_request+0x302/0x3b0 [raid456] [54979.997032] md_do_sync.cold+0x3ef/0x999 [54979.997034] ? ecryptfs_write_begin+0x70/0x280 [54979.997034] ? __switch_to_asm+0x40/0x70 [54979.997035] ? __switch_to_asm+0x34/0x70 [54979.997035] ? __switch_to_asm+0x40/0x70 [54979.997036] ? __switch_to_asm+0x34/0x70 [54979.997036] ? __switch_to_asm+0x40/0x70 [54979.997037] ? __switch_to_asm+0x34/0x70 [54979.997038] md_thread+0x97/0x160 [54979.997040] kthread+0x104/0x140 [54979.997040] ? md_start_sync+0x60/0x60 [54979.997041] ? kthread_park+0x80/0x80 [54979.997042] ret_from_fork+0x35/0x40 No other hardware errors were reported and the reshape got stuck at somewhat different blocks every time it was restarted (all within the same vicinity of each others). It turns out that md had injected the same exact sector into the badblock log of multiple devices at some point before the reshape was started. This could be seen with "mdadm --examine-badblocks /dev/sdXY". The original cause for the badblocks entries was probably a loose cable as the reported sectors were fully readable with the "dd" and "badblocks" command. The problem was eventually resolved by removing the badblock log on the RAID5 device using "mdadm --assemble /dev/md0 --update=force-no- bbl". Having removed the badblock log, reshape progressed beyond the previously troublesome area of blocks. I would have expected at least an error message in the kernel log rather than just a "hung task" message, probably before the reshape was allowed to be initiated (aka early termination). Furthermore, it would be beneficial if mdadm could allow the badblock log to be cleared for a device rather than removed on the array with "update=force-no-bbl". --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.3.0-55-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=/dev/mapper/vg0-swap IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-55-g
[Kernel-packages] [Bug 1882312] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1882312/+attachment/5380827/+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/1882312 Title: RAID5 reshape stuck due to same badblock on multiple devices Status in linux package in Ubuntu: Confirmed Bug description: Linux [hostname removed] 5.3.0-55-generic #49-Ubuntu SMP Thu May 21 12:47:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Ubuntu release: 19.10 (although the same issue is present in 18.04 and 20.04 as well). A RAID5 reshape from 3 to 4 devices got stuck: md127 : active raid5 sde1[5] sdd1[4] sdc1[0] sdf1[3] 7813769216 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [] [>] reshape = 1.8% (72261116/3906884608) finish=1663133.7min speed=38K/sec bitmap: 0/30 pages [0KB], 65536KB chunk with the following stack trace: [54979.996871] INFO: task md127_reshape:7090 blocked for more than 1208 seconds. [54979.996922] Tainted: P OE 5.3.0-55-generic #49-Ubuntu [54979.996967] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [54979.997018] md127_reshape D0 7090 2 0x80004080 [54979.997019] Call Trace: [54979.997022] __schedule+0x2b9/0x6c0 [54979.997023] schedule+0x42/0xb0 [54979.997027] reshape_request+0x878/0x950 [raid456] [54979.997028] ? wait_woken+0x80/0x80 [54979.997030] raid5_sync_request+0x302/0x3b0 [raid456] [54979.997032] md_do_sync.cold+0x3ef/0x999 [54979.997034] ? ecryptfs_write_begin+0x70/0x280 [54979.997034] ? __switch_to_asm+0x40/0x70 [54979.997035] ? __switch_to_asm+0x34/0x70 [54979.997035] ? __switch_to_asm+0x40/0x70 [54979.997036] ? __switch_to_asm+0x34/0x70 [54979.997036] ? __switch_to_asm+0x40/0x70 [54979.997037] ? __switch_to_asm+0x34/0x70 [54979.997038] md_thread+0x97/0x160 [54979.997040] kthread+0x104/0x140 [54979.997040] ? md_start_sync+0x60/0x60 [54979.997041] ? kthread_park+0x80/0x80 [54979.997042] ret_from_fork+0x35/0x40 No other hardware errors were reported and the reshape got stuck at somewhat different blocks every time it was restarted (all within the same vicinity of each others). It turns out that md had injected the same exact sector into the badblock log of multiple devices at some point before the reshape was started. This could be seen with "mdadm --examine-badblocks /dev/sdXY". The original cause for the badblocks entries was probably a loose cable as the reported sectors were fully readable with the "dd" and "badblocks" command. The problem was eventually resolved by removing the badblock log on the RAID5 device using "mdadm --assemble /dev/md0 --update=force-no- bbl". Having removed the badblock log, reshape progressed beyond the previously troublesome area of blocks. I would have expected at least an error message in the kernel log rather than just a "hung task" message, probably before the reshape was allowed to be initiated (aka early termination). Furthermore, it would be beneficial if mdadm could allow the badblock log to be cleared for a device rather than removed on the array with "update=force-no-bbl". --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.3.0-55-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=/dev/mapper/vg0-swap IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-55-generic root=/d
[Kernel-packages] [Bug 1882312] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1882312/+attachment/5380828/+files/PciMultimedia.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/1882312 Title: RAID5 reshape stuck due to same badblock on multiple devices Status in linux package in Ubuntu: Confirmed Bug description: Linux [hostname removed] 5.3.0-55-generic #49-Ubuntu SMP Thu May 21 12:47:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Ubuntu release: 19.10 (although the same issue is present in 18.04 and 20.04 as well). A RAID5 reshape from 3 to 4 devices got stuck: md127 : active raid5 sde1[5] sdd1[4] sdc1[0] sdf1[3] 7813769216 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [] [>] reshape = 1.8% (72261116/3906884608) finish=1663133.7min speed=38K/sec bitmap: 0/30 pages [0KB], 65536KB chunk with the following stack trace: [54979.996871] INFO: task md127_reshape:7090 blocked for more than 1208 seconds. [54979.996922] Tainted: P OE 5.3.0-55-generic #49-Ubuntu [54979.996967] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [54979.997018] md127_reshape D0 7090 2 0x80004080 [54979.997019] Call Trace: [54979.997022] __schedule+0x2b9/0x6c0 [54979.997023] schedule+0x42/0xb0 [54979.997027] reshape_request+0x878/0x950 [raid456] [54979.997028] ? wait_woken+0x80/0x80 [54979.997030] raid5_sync_request+0x302/0x3b0 [raid456] [54979.997032] md_do_sync.cold+0x3ef/0x999 [54979.997034] ? ecryptfs_write_begin+0x70/0x280 [54979.997034] ? __switch_to_asm+0x40/0x70 [54979.997035] ? __switch_to_asm+0x34/0x70 [54979.997035] ? __switch_to_asm+0x40/0x70 [54979.997036] ? __switch_to_asm+0x34/0x70 [54979.997036] ? __switch_to_asm+0x40/0x70 [54979.997037] ? __switch_to_asm+0x34/0x70 [54979.997038] md_thread+0x97/0x160 [54979.997040] kthread+0x104/0x140 [54979.997040] ? md_start_sync+0x60/0x60 [54979.997041] ? kthread_park+0x80/0x80 [54979.997042] ret_from_fork+0x35/0x40 No other hardware errors were reported and the reshape got stuck at somewhat different blocks every time it was restarted (all within the same vicinity of each others). It turns out that md had injected the same exact sector into the badblock log of multiple devices at some point before the reshape was started. This could be seen with "mdadm --examine-badblocks /dev/sdXY". The original cause for the badblocks entries was probably a loose cable as the reported sectors were fully readable with the "dd" and "badblocks" command. The problem was eventually resolved by removing the badblock log on the RAID5 device using "mdadm --assemble /dev/md0 --update=force-no- bbl". Having removed the badblock log, reshape progressed beyond the previously troublesome area of blocks. I would have expected at least an error message in the kernel log rather than just a "hung task" message, probably before the reshape was allowed to be initiated (aka early termination). Furthermore, it would be beneficial if mdadm could allow the badblock log to be cleared for a device rather than removed on the array with "update=force-no-bbl". --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.3.0-55-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=/dev/mapper/vg0-swap IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-55
[Kernel-packages] [Bug 1882312] Re: RAID5 reshape stuck due to same badblock on multiple devices
Please note that the apport report is collected AFTER the issue was resolved. ** 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/1882312 Title: RAID5 reshape stuck due to same badblock on multiple devices Status in linux package in Ubuntu: Confirmed Bug description: Linux [hostname removed] 5.3.0-55-generic #49-Ubuntu SMP Thu May 21 12:47:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Ubuntu release: 19.10 (although the same issue is present in 18.04 and 20.04 as well). A RAID5 reshape from 3 to 4 devices got stuck: md127 : active raid5 sde1[5] sdd1[4] sdc1[0] sdf1[3] 7813769216 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [] [>] reshape = 1.8% (72261116/3906884608) finish=1663133.7min speed=38K/sec bitmap: 0/30 pages [0KB], 65536KB chunk with the following stack trace: [54979.996871] INFO: task md127_reshape:7090 blocked for more than 1208 seconds. [54979.996922] Tainted: P OE 5.3.0-55-generic #49-Ubuntu [54979.996967] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [54979.997018] md127_reshape D0 7090 2 0x80004080 [54979.997019] Call Trace: [54979.997022] __schedule+0x2b9/0x6c0 [54979.997023] schedule+0x42/0xb0 [54979.997027] reshape_request+0x878/0x950 [raid456] [54979.997028] ? wait_woken+0x80/0x80 [54979.997030] raid5_sync_request+0x302/0x3b0 [raid456] [54979.997032] md_do_sync.cold+0x3ef/0x999 [54979.997034] ? ecryptfs_write_begin+0x70/0x280 [54979.997034] ? __switch_to_asm+0x40/0x70 [54979.997035] ? __switch_to_asm+0x34/0x70 [54979.997035] ? __switch_to_asm+0x40/0x70 [54979.997036] ? __switch_to_asm+0x34/0x70 [54979.997036] ? __switch_to_asm+0x40/0x70 [54979.997037] ? __switch_to_asm+0x34/0x70 [54979.997038] md_thread+0x97/0x160 [54979.997040] kthread+0x104/0x140 [54979.997040] ? md_start_sync+0x60/0x60 [54979.997041] ? kthread_park+0x80/0x80 [54979.997042] ret_from_fork+0x35/0x40 No other hardware errors were reported and the reshape got stuck at somewhat different blocks every time it was restarted (all within the same vicinity of each others). It turns out that md had injected the same exact sector into the badblock log of multiple devices at some point before the reshape was started. This could be seen with "mdadm --examine-badblocks /dev/sdXY". The original cause for the badblocks entries was probably a loose cable as the reported sectors were fully readable with the "dd" and "badblocks" command. The problem was eventually resolved by removing the badblock log on the RAID5 device using "mdadm --assemble /dev/md0 --update=force-no- bbl". Having removed the badblock log, reshape progressed beyond the previously troublesome area of blocks. I would have expected at least an error message in the kernel log rather than just a "hung task" message, probably before the reshape was allowed to be initiated (aka early termination). Furthermore, it would be beneficial if mdadm could allow the badblock log to be cleared for a device rather than removed on the array with "update=force-no-bbl". --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.3.0-55-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=/dev/mapper/vg0-swap IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-55-g
[Kernel-packages] [Bug 1882312] Re: RAID5 reshape stuck due to same badblock on multiple devices
apport information ** Tags added: apport-collected ** Description changed: Linux [hostname removed] 5.3.0-55-generic #49-Ubuntu SMP Thu May 21 12:47:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Ubuntu release: 19.10 (although the same issue is present in 18.04 and 20.04 as well). A RAID5 reshape from 3 to 4 devices got stuck: md127 : active raid5 sde1[5] sdd1[4] sdc1[0] sdf1[3] 7813769216 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [] [>] reshape = 1.8% (72261116/3906884608) finish=1663133.7min speed=38K/sec bitmap: 0/30 pages [0KB], 65536KB chunk with the following stack trace: [54979.996871] INFO: task md127_reshape:7090 blocked for more than 1208 seconds. [54979.996922] Tainted: P OE 5.3.0-55-generic #49-Ubuntu [54979.996967] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [54979.997018] md127_reshape D0 7090 2 0x80004080 [54979.997019] Call Trace: [54979.997022] __schedule+0x2b9/0x6c0 [54979.997023] schedule+0x42/0xb0 [54979.997027] reshape_request+0x878/0x950 [raid456] [54979.997028] ? wait_woken+0x80/0x80 [54979.997030] raid5_sync_request+0x302/0x3b0 [raid456] [54979.997032] md_do_sync.cold+0x3ef/0x999 [54979.997034] ? ecryptfs_write_begin+0x70/0x280 [54979.997034] ? __switch_to_asm+0x40/0x70 [54979.997035] ? __switch_to_asm+0x34/0x70 [54979.997035] ? __switch_to_asm+0x40/0x70 [54979.997036] ? __switch_to_asm+0x34/0x70 [54979.997036] ? __switch_to_asm+0x40/0x70 [54979.997037] ? __switch_to_asm+0x34/0x70 [54979.997038] md_thread+0x97/0x160 [54979.997040] kthread+0x104/0x140 [54979.997040] ? md_start_sync+0x60/0x60 [54979.997041] ? kthread_park+0x80/0x80 [54979.997042] ret_from_fork+0x35/0x40 No other hardware errors were reported and the reshape got stuck at somewhat different blocks every time it was restarted (all within the same vicinity of each others). It turns out that md had injected the same exact sector into the badblock log of multiple devices at some point before the reshape was started. This could be seen with "mdadm --examine-badblocks /dev/sdXY". The original cause for the badblocks entries was probably a loose cable as the reported sectors were fully readable with the "dd" and "badblocks" command. The problem was eventually resolved by removing the badblock log on the RAID5 device using "mdadm --assemble /dev/md0 --update=force-no-bbl". Having removed the badblock log, reshape progressed beyond the previously troublesome area of blocks. - I would have expected at least an error message in the kernel log rather - than just a "hung task" message, probably before the reshape was allowed - to be initiated (aka early termination). Furthermore, it would be - beneficial if mdadm could allow the badblock log to be cleared for a - device rather than removed on the array with "update=force-no-bbl". + I would have expected at least an error message in the kernel log rather than just a "hung task" message, probably before the reshape was allowed to be initiated (aka early termination). Furthermore, it would be beneficial if mdadm could allow the badblock log to be cleared for a device rather than removed on the array with "update=force-no-bbl". + --- + ProblemType: Bug + AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.3.0-55-generic. + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.11-0ubuntu8.9 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' + Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' + DistroRelease: Ubuntu 19.10 + HibernationDevice: RESUME=/dev/mapper/vg0-swap + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' + Lsusb: + Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: System manufacturer System Product Name + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: linux (not installed) + ProcEnviron: + LC_CTYPE=en_US.UTF-8 + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-55
[Kernel-packages] [Bug 1882312] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1882312/+attachment/5380832/+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/1882312 Title: RAID5 reshape stuck due to same badblock on multiple devices Status in linux package in Ubuntu: Confirmed Bug description: Linux [hostname removed] 5.3.0-55-generic #49-Ubuntu SMP Thu May 21 12:47:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Ubuntu release: 19.10 (although the same issue is present in 18.04 and 20.04 as well). A RAID5 reshape from 3 to 4 devices got stuck: md127 : active raid5 sde1[5] sdd1[4] sdc1[0] sdf1[3] 7813769216 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [] [>] reshape = 1.8% (72261116/3906884608) finish=1663133.7min speed=38K/sec bitmap: 0/30 pages [0KB], 65536KB chunk with the following stack trace: [54979.996871] INFO: task md127_reshape:7090 blocked for more than 1208 seconds. [54979.996922] Tainted: P OE 5.3.0-55-generic #49-Ubuntu [54979.996967] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [54979.997018] md127_reshape D0 7090 2 0x80004080 [54979.997019] Call Trace: [54979.997022] __schedule+0x2b9/0x6c0 [54979.997023] schedule+0x42/0xb0 [54979.997027] reshape_request+0x878/0x950 [raid456] [54979.997028] ? wait_woken+0x80/0x80 [54979.997030] raid5_sync_request+0x302/0x3b0 [raid456] [54979.997032] md_do_sync.cold+0x3ef/0x999 [54979.997034] ? ecryptfs_write_begin+0x70/0x280 [54979.997034] ? __switch_to_asm+0x40/0x70 [54979.997035] ? __switch_to_asm+0x34/0x70 [54979.997035] ? __switch_to_asm+0x40/0x70 [54979.997036] ? __switch_to_asm+0x34/0x70 [54979.997036] ? __switch_to_asm+0x40/0x70 [54979.997037] ? __switch_to_asm+0x34/0x70 [54979.997038] md_thread+0x97/0x160 [54979.997040] kthread+0x104/0x140 [54979.997040] ? md_start_sync+0x60/0x60 [54979.997041] ? kthread_park+0x80/0x80 [54979.997042] ret_from_fork+0x35/0x40 No other hardware errors were reported and the reshape got stuck at somewhat different blocks every time it was restarted (all within the same vicinity of each others). It turns out that md had injected the same exact sector into the badblock log of multiple devices at some point before the reshape was started. This could be seen with "mdadm --examine-badblocks /dev/sdXY". The original cause for the badblocks entries was probably a loose cable as the reported sectors were fully readable with the "dd" and "badblocks" command. The problem was eventually resolved by removing the badblock log on the RAID5 device using "mdadm --assemble /dev/md0 --update=force-no- bbl". Having removed the badblock log, reshape progressed beyond the previously troublesome area of blocks. I would have expected at least an error message in the kernel log rather than just a "hung task" message, probably before the reshape was allowed to be initiated (aka early termination). Furthermore, it would be beneficial if mdadm could allow the badblock log to be cleared for a device rather than removed on the array with "update=force-no-bbl". --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.3.0-55-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=/dev/mapper/vg0-swap IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-55-generic root=
[Kernel-packages] [Bug 1882312] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1882312/+attachment/5380829/+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/1882312 Title: RAID5 reshape stuck due to same badblock on multiple devices Status in linux package in Ubuntu: Confirmed Bug description: Linux [hostname removed] 5.3.0-55-generic #49-Ubuntu SMP Thu May 21 12:47:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Ubuntu release: 19.10 (although the same issue is present in 18.04 and 20.04 as well). A RAID5 reshape from 3 to 4 devices got stuck: md127 : active raid5 sde1[5] sdd1[4] sdc1[0] sdf1[3] 7813769216 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [] [>] reshape = 1.8% (72261116/3906884608) finish=1663133.7min speed=38K/sec bitmap: 0/30 pages [0KB], 65536KB chunk with the following stack trace: [54979.996871] INFO: task md127_reshape:7090 blocked for more than 1208 seconds. [54979.996922] Tainted: P OE 5.3.0-55-generic #49-Ubuntu [54979.996967] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [54979.997018] md127_reshape D0 7090 2 0x80004080 [54979.997019] Call Trace: [54979.997022] __schedule+0x2b9/0x6c0 [54979.997023] schedule+0x42/0xb0 [54979.997027] reshape_request+0x878/0x950 [raid456] [54979.997028] ? wait_woken+0x80/0x80 [54979.997030] raid5_sync_request+0x302/0x3b0 [raid456] [54979.997032] md_do_sync.cold+0x3ef/0x999 [54979.997034] ? ecryptfs_write_begin+0x70/0x280 [54979.997034] ? __switch_to_asm+0x40/0x70 [54979.997035] ? __switch_to_asm+0x34/0x70 [54979.997035] ? __switch_to_asm+0x40/0x70 [54979.997036] ? __switch_to_asm+0x34/0x70 [54979.997036] ? __switch_to_asm+0x40/0x70 [54979.997037] ? __switch_to_asm+0x34/0x70 [54979.997038] md_thread+0x97/0x160 [54979.997040] kthread+0x104/0x140 [54979.997040] ? md_start_sync+0x60/0x60 [54979.997041] ? kthread_park+0x80/0x80 [54979.997042] ret_from_fork+0x35/0x40 No other hardware errors were reported and the reshape got stuck at somewhat different blocks every time it was restarted (all within the same vicinity of each others). It turns out that md had injected the same exact sector into the badblock log of multiple devices at some point before the reshape was started. This could be seen with "mdadm --examine-badblocks /dev/sdXY". The original cause for the badblocks entries was probably a loose cable as the reported sectors were fully readable with the "dd" and "badblocks" command. The problem was eventually resolved by removing the badblock log on the RAID5 device using "mdadm --assemble /dev/md0 --update=force-no- bbl". Having removed the badblock log, reshape progressed beyond the previously troublesome area of blocks. I would have expected at least an error message in the kernel log rather than just a "hung task" message, probably before the reshape was allowed to be initiated (aka early termination). Furthermore, it would be beneficial if mdadm could allow the badblock log to be cleared for a device rather than removed on the array with "update=force-no-bbl". --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.3.0-55-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=/dev/mapper/vg0-swap IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinu
[Kernel-packages] [Bug 1882312] Card0.Codecs.codec.0.txt
apport information ** Attachment added: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1882312/+attachment/5380824/+files/Card0.Codecs.codec.0.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/1882312 Title: RAID5 reshape stuck due to same badblock on multiple devices Status in linux package in Ubuntu: Confirmed Bug description: Linux [hostname removed] 5.3.0-55-generic #49-Ubuntu SMP Thu May 21 12:47:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Ubuntu release: 19.10 (although the same issue is present in 18.04 and 20.04 as well). A RAID5 reshape from 3 to 4 devices got stuck: md127 : active raid5 sde1[5] sdd1[4] sdc1[0] sdf1[3] 7813769216 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [] [>] reshape = 1.8% (72261116/3906884608) finish=1663133.7min speed=38K/sec bitmap: 0/30 pages [0KB], 65536KB chunk with the following stack trace: [54979.996871] INFO: task md127_reshape:7090 blocked for more than 1208 seconds. [54979.996922] Tainted: P OE 5.3.0-55-generic #49-Ubuntu [54979.996967] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [54979.997018] md127_reshape D0 7090 2 0x80004080 [54979.997019] Call Trace: [54979.997022] __schedule+0x2b9/0x6c0 [54979.997023] schedule+0x42/0xb0 [54979.997027] reshape_request+0x878/0x950 [raid456] [54979.997028] ? wait_woken+0x80/0x80 [54979.997030] raid5_sync_request+0x302/0x3b0 [raid456] [54979.997032] md_do_sync.cold+0x3ef/0x999 [54979.997034] ? ecryptfs_write_begin+0x70/0x280 [54979.997034] ? __switch_to_asm+0x40/0x70 [54979.997035] ? __switch_to_asm+0x34/0x70 [54979.997035] ? __switch_to_asm+0x40/0x70 [54979.997036] ? __switch_to_asm+0x34/0x70 [54979.997036] ? __switch_to_asm+0x40/0x70 [54979.997037] ? __switch_to_asm+0x34/0x70 [54979.997038] md_thread+0x97/0x160 [54979.997040] kthread+0x104/0x140 [54979.997040] ? md_start_sync+0x60/0x60 [54979.997041] ? kthread_park+0x80/0x80 [54979.997042] ret_from_fork+0x35/0x40 No other hardware errors were reported and the reshape got stuck at somewhat different blocks every time it was restarted (all within the same vicinity of each others). It turns out that md had injected the same exact sector into the badblock log of multiple devices at some point before the reshape was started. This could be seen with "mdadm --examine-badblocks /dev/sdXY". The original cause for the badblocks entries was probably a loose cable as the reported sectors were fully readable with the "dd" and "badblocks" command. The problem was eventually resolved by removing the badblock log on the RAID5 device using "mdadm --assemble /dev/md0 --update=force-no- bbl". Having removed the badblock log, reshape progressed beyond the previously troublesome area of blocks. I would have expected at least an error message in the kernel log rather than just a "hung task" message, probably before the reshape was allowed to be initiated (aka early termination). Furthermore, it would be beneficial if mdadm could allow the badblock log to be cleared for a device rather than removed on the array with "update=force-no-bbl". --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.3.0-55-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=/dev/mapper/vg0-swap IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vm
[Kernel-packages] [Bug 1882312] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1882312/+attachment/5380823/+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/1882312 Title: RAID5 reshape stuck due to same badblock on multiple devices Status in linux package in Ubuntu: Confirmed Bug description: Linux [hostname removed] 5.3.0-55-generic #49-Ubuntu SMP Thu May 21 12:47:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Ubuntu release: 19.10 (although the same issue is present in 18.04 and 20.04 as well). A RAID5 reshape from 3 to 4 devices got stuck: md127 : active raid5 sde1[5] sdd1[4] sdc1[0] sdf1[3] 7813769216 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [] [>] reshape = 1.8% (72261116/3906884608) finish=1663133.7min speed=38K/sec bitmap: 0/30 pages [0KB], 65536KB chunk with the following stack trace: [54979.996871] INFO: task md127_reshape:7090 blocked for more than 1208 seconds. [54979.996922] Tainted: P OE 5.3.0-55-generic #49-Ubuntu [54979.996967] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [54979.997018] md127_reshape D0 7090 2 0x80004080 [54979.997019] Call Trace: [54979.997022] __schedule+0x2b9/0x6c0 [54979.997023] schedule+0x42/0xb0 [54979.997027] reshape_request+0x878/0x950 [raid456] [54979.997028] ? wait_woken+0x80/0x80 [54979.997030] raid5_sync_request+0x302/0x3b0 [raid456] [54979.997032] md_do_sync.cold+0x3ef/0x999 [54979.997034] ? ecryptfs_write_begin+0x70/0x280 [54979.997034] ? __switch_to_asm+0x40/0x70 [54979.997035] ? __switch_to_asm+0x34/0x70 [54979.997035] ? __switch_to_asm+0x40/0x70 [54979.997036] ? __switch_to_asm+0x34/0x70 [54979.997036] ? __switch_to_asm+0x40/0x70 [54979.997037] ? __switch_to_asm+0x34/0x70 [54979.997038] md_thread+0x97/0x160 [54979.997040] kthread+0x104/0x140 [54979.997040] ? md_start_sync+0x60/0x60 [54979.997041] ? kthread_park+0x80/0x80 [54979.997042] ret_from_fork+0x35/0x40 No other hardware errors were reported and the reshape got stuck at somewhat different blocks every time it was restarted (all within the same vicinity of each others). It turns out that md had injected the same exact sector into the badblock log of multiple devices at some point before the reshape was started. This could be seen with "mdadm --examine-badblocks /dev/sdXY". The original cause for the badblocks entries was probably a loose cable as the reported sectors were fully readable with the "dd" and "badblocks" command. The problem was eventually resolved by removing the badblock log on the RAID5 device using "mdadm --assemble /dev/md0 --update=force-no- bbl". Having removed the badblock log, reshape progressed beyond the previously troublesome area of blocks. I would have expected at least an error message in the kernel log rather than just a "hung task" message, probably before the reshape was allowed to be initiated (aka early termination). Furthermore, it would be beneficial if mdadm could allow the badblock log to be cleared for a device rather than removed on the array with "update=force-no-bbl". --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.3.0-55-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=/dev/mapper/vg0-swap IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-55-generic root=/dev
[Kernel-packages] [Bug 1882312] Missing required logs.
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 1882312 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 ** Tags added: eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882312 Title: RAID5 reshape stuck due to same badblock on multiple devices Status in linux package in Ubuntu: Incomplete Bug description: Linux [hostname removed] 5.3.0-55-generic #49-Ubuntu SMP Thu May 21 12:47:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Ubuntu release: 19.10 (although the same issue is present in 18.04 and 20.04 as well). A RAID5 reshape from 3 to 4 devices got stuck: md127 : active raid5 sde1[5] sdd1[4] sdc1[0] sdf1[3] 7813769216 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [] [>] reshape = 1.8% (72261116/3906884608) finish=1663133.7min speed=38K/sec bitmap: 0/30 pages [0KB], 65536KB chunk with the following stack trace: [54979.996871] INFO: task md127_reshape:7090 blocked for more than 1208 seconds. [54979.996922] Tainted: P OE 5.3.0-55-generic #49-Ubuntu [54979.996967] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [54979.997018] md127_reshape D0 7090 2 0x80004080 [54979.997019] Call Trace: [54979.997022] __schedule+0x2b9/0x6c0 [54979.997023] schedule+0x42/0xb0 [54979.997027] reshape_request+0x878/0x950 [raid456] [54979.997028] ? wait_woken+0x80/0x80 [54979.997030] raid5_sync_request+0x302/0x3b0 [raid456] [54979.997032] md_do_sync.cold+0x3ef/0x999 [54979.997034] ? ecryptfs_write_begin+0x70/0x280 [54979.997034] ? __switch_to_asm+0x40/0x70 [54979.997035] ? __switch_to_asm+0x34/0x70 [54979.997035] ? __switch_to_asm+0x40/0x70 [54979.997036] ? __switch_to_asm+0x34/0x70 [54979.997036] ? __switch_to_asm+0x40/0x70 [54979.997037] ? __switch_to_asm+0x34/0x70 [54979.997038] md_thread+0x97/0x160 [54979.997040] kthread+0x104/0x140 [54979.997040] ? md_start_sync+0x60/0x60 [54979.997041] ? kthread_park+0x80/0x80 [54979.997042] ret_from_fork+0x35/0x40 No other hardware errors were reported and the reshape got stuck at somewhat different blocks every time it was restarted (all within the same vicinity of each others). It turns out that md had injected the same exact sector into the badblock log of multiple devices at some point before the reshape was started. This could be seen with "mdadm --examine-badblocks /dev/sdXY". The original cause for the badblocks entries was probably a loose cable as the reported sectors were fully readable with the "dd" and "badblocks" command. The problem was eventually resolved by removing the badblock log on the RAID5 device using "mdadm --assemble /dev/md0 --update=force-no- bbl". Having removed the badblock log, reshape progressed beyond the previously troublesome area of blocks. I would have expected at least an error message in the kernel log rather than just a "hung task" message, probably before the reshape was allowed to be initiated (aka early termination). Furthermore, it would be beneficial if mdadm could allow the badblock log to be cleared for a device rather than removed on the array with "update =force-no-bbl". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882312] [NEW] RAID5 reshape stuck due to same badblock on multiple devices
Public bug reported: Linux [hostname removed] 5.3.0-55-generic #49-Ubuntu SMP Thu May 21 12:47:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Ubuntu release: 19.10 (although the same issue is present in 18.04 and 20.04 as well). A RAID5 reshape from 3 to 4 devices got stuck: md127 : active raid5 sde1[5] sdd1[4] sdc1[0] sdf1[3] 7813769216 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [] [>] reshape = 1.8% (72261116/3906884608) finish=1663133.7min speed=38K/sec bitmap: 0/30 pages [0KB], 65536KB chunk with the following stack trace: [54979.996871] INFO: task md127_reshape:7090 blocked for more than 1208 seconds. [54979.996922] Tainted: P OE 5.3.0-55-generic #49-Ubuntu [54979.996967] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [54979.997018] md127_reshape D0 7090 2 0x80004080 [54979.997019] Call Trace: [54979.997022] __schedule+0x2b9/0x6c0 [54979.997023] schedule+0x42/0xb0 [54979.997027] reshape_request+0x878/0x950 [raid456] [54979.997028] ? wait_woken+0x80/0x80 [54979.997030] raid5_sync_request+0x302/0x3b0 [raid456] [54979.997032] md_do_sync.cold+0x3ef/0x999 [54979.997034] ? ecryptfs_write_begin+0x70/0x280 [54979.997034] ? __switch_to_asm+0x40/0x70 [54979.997035] ? __switch_to_asm+0x34/0x70 [54979.997035] ? __switch_to_asm+0x40/0x70 [54979.997036] ? __switch_to_asm+0x34/0x70 [54979.997036] ? __switch_to_asm+0x40/0x70 [54979.997037] ? __switch_to_asm+0x34/0x70 [54979.997038] md_thread+0x97/0x160 [54979.997040] kthread+0x104/0x140 [54979.997040] ? md_start_sync+0x60/0x60 [54979.997041] ? kthread_park+0x80/0x80 [54979.997042] ret_from_fork+0x35/0x40 No other hardware errors were reported and the reshape got stuck at somewhat different blocks every time it was restarted (all within the same vicinity of each others). It turns out that md had injected the same exact sector into the badblock log of multiple devices at some point before the reshape was started. This could be seen with "mdadm --examine-badblocks /dev/sdXY". The original cause for the badblocks entries was probably a loose cable as the reported sectors were fully readable with the "dd" and "badblocks" command. The problem was eventually resolved by removing the badblock log on the RAID5 device using "mdadm --assemble /dev/md0 --update=force-no-bbl". Having removed the badblock log, reshape progressed beyond the previously troublesome area of blocks. I would have expected at least an error message in the kernel log rather than just a "hung task" message, probably before the reshape was allowed to be initiated (aka early termination). Furthermore, it would be beneficial if mdadm could allow the badblock log to be cleared for a device rather than removed on the array with "update=force-no-bbl". ** 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/1882312 Title: RAID5 reshape stuck due to same badblock on multiple devices Status in linux package in Ubuntu: New Bug description: Linux [hostname removed] 5.3.0-55-generic #49-Ubuntu SMP Thu May 21 12:47:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Ubuntu release: 19.10 (although the same issue is present in 18.04 and 20.04 as well). A RAID5 reshape from 3 to 4 devices got stuck: md127 : active raid5 sde1[5] sdd1[4] sdc1[0] sdf1[3] 7813769216 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [] [>] reshape = 1.8% (72261116/3906884608) finish=1663133.7min speed=38K/sec bitmap: 0/30 pages [0KB], 65536KB chunk with the following stack trace: [54979.996871] INFO: task md127_reshape:7090 blocked for more than 1208 seconds. [54979.996922] Tainted: P OE 5.3.0-55-generic #49-Ubuntu [54979.996967] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [54979.997018] md127_reshape D0 7090 2 0x80004080 [54979.997019] Call Trace: [54979.997022] __schedule+0x2b9/0x6c0 [54979.997023] schedule+0x42/0xb0 [54979.997027] reshape_request+0x878/0x950 [raid456] [54979.997028] ? wait_woken+0x80/0x80 [54979.997030] raid5_sync_request+0x302/0x3b0 [raid456] [54979.997032] md_do_sync.cold+0x3ef/0x999 [54979.997034] ? ecryptfs_write_begin+0x70/0x280 [54979.997034] ? __switch_to_asm+0x40/0x70 [54979.997035] ? __switch_to_asm+0x34/0x70 [54979.997035] ? __switch_to_asm+0x40/0x70 [54979.997036] ? __switch_to_asm+0x34/0x70 [54979.997036] ? __switch_to_asm+0x40/0x70 [54979.997037] ? __switch_to_asm+0x34/0x70 [54979.997038] md_thread+0x97/0x160 [54979.997040] kthread+0x104/0x140 [54979.997040] ? md_start_sync+0x60/0x60 [54979.997041] ? kthread_park+0x80/0x80 [54979.997042] ret_from_fork+0x35/0x40 No other hardware errors were repor
[Kernel-packages] [Bug 1881319] Re: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel)
I also have a Lenovo IdeaPad 5 15ARE05 with no touchpad working, but xinput list shows "GTCH7503:00 2A94:D64D" with no mention of Elan at all. I installed Linux Mint. I tried 15 different solutions and none of them worked. Please advised. Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881319 Title: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel) Status in linux package in Ubuntu: Confirmed Bug description: Touchpad isn't reacting at all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andreas1223 F pulseaudio /dev/snd/controlC0: andreas1223 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri May 29 18:05:01 2020 InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YQ ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=4197e5c6-f903-46c3-bc16-3013c5650810 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN24WW 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 5 15ARE05 dmi.modalias: dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882308] Status changed to Confirmed
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/1882308 Title: Intel GVT-g Bug With Windows Guests Status in linux package in Ubuntu: Confirmed Bug description: Looks like this bug is fixed by Intel here... just need the patch applied to the Ubuntu kernel. https://github.com/intel/gvt- linux/commit/dbafc67307ec06036b25b223a251af03fe07969a Ubuntu 5.4.0-33.37-generic 5.4.34 Kernel command line arguments: i915.enable_gvt=1 kvm.ignore_msrs=1 intel_iommu=on 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:191f] (rev 07) Subsystem: Dell Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [1028:06bb] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) [8086:1901] (rev 07) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [88] Subsystem: Dell Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) [1028:06bb] Capabilities: [80] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00218 Data: Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 256 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <1us, L1 <8us ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s (downgraded), Width x0 (downgraded) TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #1, PowerLimit 75.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- Interlock- Changed: MRL- PresDet- LinkState- RootCap: CRSVisible- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, NROPrPrP-, LTR+ 10BitTagComp-, 10BitTagReq-, OBFF Via WAKE#, ExtFmt-, EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS-, LN System CLS Not Supported, TPHComp-, ExtTPHComp-, ARIFwd- AtomicOpsCap: Routing- 32bit+ 64bit+ 128bitCAS+ DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- AtomicOpsCtl: ReqEn- EgressBlck- LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect
[Kernel-packages] [Bug 1882308] [NEW] Intel GVT-g Bug With Windows Guests
Public bug reported: Looks like this bug is fixed by Intel here... just need the patch applied to the Ubuntu kernel. https://github.com/intel/gvt- linux/commit/dbafc67307ec06036b25b223a251af03fe07969a Ubuntu 5.4.0-33.37-generic 5.4.34 Kernel command line arguments: i915.enable_gvt=1 kvm.ignore_msrs=1 intel_iommu=on 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:191f] (rev 07) Subsystem: Dell Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [1028:06bb] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) [8086:1901] (rev 07) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [88] Subsystem: Dell Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) [1028:06bb] Capabilities: [80] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00218 Data: Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 256 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <1us, L1 <8us ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s (downgraded), Width x0 (downgraded) TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #1, PowerLimit 75.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- Interlock- Changed: MRL- PresDet- LinkState- RootCap: CRSVisible- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, NROPrPrP-, LTR+ 10BitTagComp-, 10BitTagReq-, OBFF Via WAKE#, ExtFmt-, EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS-, LN System CLS Not Supported, TPHComp-, ExtTPHComp-, ARIFwd- AtomicOpsCap: Routing- 32bit+ 64bit+ 128bitCAS+ DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- AtomicOpsCtl: ReqEn- EgressBlck- LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb:Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff Status: NegoPending+ InProgress- Capabilities: [140 v1] Root Complex Link Desc: PortNumber=02 ComponentID=01 EltType=Config Link0: Desc:
[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
I ran all 4 commands posted by Erikas in #150. I am not sure what fixed it as I did not stop to test between commands. But I made it an sh script as Viktor suggested. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882303] [NEW] Eoan update: upstream stable patchset 2020-06-05
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 2020-06-05 Ported from the following upstream stable releases: v4.19.125, v5.4.43 from git://git.kernel.org/ i2c: dev: Fix the race between the release of i2c_dev and cdev KVM: SVM: Fix potential memory leak in svm_cpu_init() ima: Set file->f_mode instead of file->f_flags in ima_calc_file_hash() evm: Check also if *tfm is an error pointer in init_desc() ima: Fix return value of ima_write_policy() mtd: spinand: Propagate ECC information to the MTD structure fix multiplication overflow in copy_fdtable() ubifs: remove broken lazytime support iommu/amd: Fix over-read of ACPI UID from IVRS table i2c: mux: demux-pinctrl: Fix an error handling path in 'i2c_demux_pinctrl_probe()' ubi: Fix seq_file usage in detailed_erase_block_info debugfs file gcc-common.h: Update for GCC 10 HID: multitouch: add eGalaxTouch P80H84 support HID: alps: Add AUI1657 device ID HID: alps: ALPS_1657 is too specific; use U1_UNICORN_LEGACY instead scsi: qla2xxx: Fix hang when issuing nvme disconnect-all in NPIV scsi: qla2xxx: Delete all sessions before unregister local nvme port configfs: fix config_item refcnt leak in configfs_rmdir() vhost/vsock: fix packet delivery order to monitoring devices aquantia: Fix the media type of AQC100 ethernet controller in the driver component: Silence bind error on -EPROBE_DEFER scsi: ibmvscsi: Fix WARN_ON during event pool release HID: i2c-hid: reset Synaptics SYNA2393 on resume x86/apic: Move TSC deadline timer debug printk gtp: set NLM_F_MULTI flag in gtp_genl_dump_pdp() HID: quirks: Add HID_QUIRK_NO_INIT_REPORTS quirk for Dell K12A keyboard-dock ceph: fix double unlock in handle_cap_export() stmmac: fix pointer check after utilization in stmmac_interrupt USB: core: Fix misleading driver bug report platform/x86: asus-nb-wmi: Do not load on Asus T100TA and T200TA ARM: futex: Address build warning padata: Replace delayed timer with immediate workqueue in padata_reorder padata: initialize pd->cpu with effective cpumask padata: purge get_cpu and reorder_via_wq from padata_do_serial ALSA: iec1712: Initialize STDSP24 properly when using the model=staudio option ALSA: pcm: fix incorrect hw_base increase ALSA: hda/realtek - Fix silent output on Gigabyte X570 Aorus Xtreme ALSA: hda/realtek - Add more fixup entries for Clevo machines drm/etnaviv: fix perfmon domain interation apparmor: fix potential label refcnt leak in aa_change_profile apparmor: Fix aa_label refcnt leak in policy_update dmaengine: tegra210-adma: Fix an error handling path in 'tegra_adma_probe()' dmaengine: owl: Use correct lock in owl_dma_get_pchan() drm/i915/gvt: Init DPLL/DDI vreg for virtual display instead of inheritance. powerpc: Remove STRICT_KERNEL_RWX incompatibility with RELOCATABLE powerpc/64s: Disable STRICT_KERNEL_RWX media: fdp1: Fix R-Car M3-N naming in debug message Revert "net/ibmvnic: Fix EOI when running in XIVE mode" Revert "gfs2: Don't demote a glock until its revokes are written" staging: iio: ad2s1210: Fix SPI reading staging: greybus: Fix uninitialized scalar variable iio: sca3000: Remove an erroneous 'get_device()' iio: dac: vf610: Fix an error handling path in 'vf610_dac_probe()' misc: rtsx: Add short delay after exit from ASPM mei: release me_cl object reference ipack: tpci200: fix error return code in tpci200_register() rapidio: fix an error in get_user_pages_fast() error handling rxrpc: Fix a memory leak in rxkad_verify_response() x86/unwind/orc: Fix unwind_get_return_address_ptr() for inactive tasks iio: adc: stm32-adc: Use dma_request_chan() instead dma_request_slave_channel() iio: adc: stm32-adc: fix device used to request dma iio: adc: stm32-dfsdm: Use dma_request_chan() instead dma_request_slave_channel() iio: adc: stm32-dfsdm: fix device used to request dma rxrpc: Trace discarded ACKs rxrpc: Fix ack discard ubifs: fix wrong use of crypto_shash_descsize() i2c: fix missing pm_runtime_put_sync in i2c_device_probe evm: Fix a small race in init_desc() afs: Don't unlock fetched data pages until the op completes successfully mtd: Fix mtd not registered due to nvmem name collision net/ena: Fix build warning in ena_xdp_set() x86/mm/cpa: Flush direct map alias during cpa ibmvnic: Skip fatal error reset after passive init iommu/amd: Call domain_flush_complete() in update_domain() drm/amd/display: Prevent dpcd reads with passive dongles KVM: selftests: Fix build for evmcs.h scripts/gdb: repair rb_first() and rb_last() ALSA: hda - constify and cleanup static NodeID tables ALSA: hd
[Kernel-packages] [Bug 1822633] Re: Pairing failure with BLE 4.0
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
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/1822633
Title:
Pairing failure with BLE 4.0
Status in bluez package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
When attempting to pair a BLE 4.0 pen using Bluez, we receive
authentication errors.
Here is the FW from Jason.
Details:
===
I added a few debug statements (patch attached) to the kernel's
net/bluetooth/smp.c:smp_sig_channel() function
(https://github.com/torvalds/linux/blob/v5.0/net/bluetooth/smp.c#L2883).
When I try to pair the PN579X, I get the following logs:
[ 5653.563048] DBG: Received code 2 (allowed = 0024) with 6 bytes
[ 5653.563053] DBG: Processing code...
[ 5653.709572] DBG: Received code 3 (allowed = 0028) with 16 bytes
[ 5653.709577] DBG: Processing code...
[ 5653.807085] DBG: Received code 4 (allowed = 0030) with 16 bytes
[ 5653.807089] DBG: Processing code...
[ 5654.148553] DBG: Received code 6 (allowed = 0060) with 16 bytes
[ 5654.148557] DBG: Processing code...
[ 5654.197024] DBG: Received code 7 (allowed = 00a0) with 10 bytes
[ 5654.197027] DBG: Processing code...
[ 5654.245824] DBG: Received code 8 (allowed = 0120) with 16 bytes
[ 5654.245828] DBG: Processing code...
[ 5654.246178] DBG: Received code 9 (allowed = 0220) with 7 bytes
[ 5654.246182] DBG: Processing code...
[ 5657.610656] input: Dell Active Pen PN579X Keyboard as
/devices/virtual/misc/uhid/0005:413C:81D5.0004/input/input23
[ 5657.610997] hid-generic 0005:413C:81D5.0004: input,hidraw0: BLUETOOTH HID
vf.08 Keyboard [Dell Active Pen PN579X] on 18:56:80:18:6A:E5
When I try to pair the PN557W, however, I only get the following:
[ 64.924901] DBG: Received code 11 (allowed = 0024) with 1 bytes
[ 64.924906] DBG: AuthReq = 00
[ 64.924907] ERR: Code not allowed on existing connection
[ 64.924943] Bluetooth: hci0: unexpected SMP command 0x0b from
bc:82:5d:fa:5e:b7
[ 64.940314] NET: Registered protocol family 38
[ 65.022326] DBG: Received code 5 (allowed = 0024) with 1 bytes
[ 65.022331] DBG: Processing code...
The "allowed" value is a bitmap, so 0024 means that only event
code 2 and 5 are allowed. The "smp_sig_channel()" function does allow
code 11 ("SMP_CMD_SECURITY_REQ") to be sent from the device at the
beginning of the connection but *only* if the "smp" variable hasn't
been set yet. It looks like the host starts the pairing process and
initializes the "smp" variable, which then prevents code 11 from being
allowed.
I did try to force the code to allow code 11 at any time, but this
didn't seem to help the situation any. The device still sent code 5
("SMP_CMD_PAIRING_FAIL") immediately afterwards, just like it does in
the trace above. Worse, the kernel logs a general protection fault
several seconds afterwards, so it clearly doesn't like the workaround.
I also find it odd that the "AuthReq = 00". I found a copy of the core
Bluetooth spec at https://www.bluetooth.com/specifications/bluetooth-
core-specification and Vol. 3 Part H Chapter 3.6.7 describes the
AuthReq flags. All zero would seem to indicate that no security is
requested, and I'm not sure if the kernel enforces a minimum security
level or something.
Finally, I also tried the suggestion at
https://www.raymondjdouglas.com/blog/2019/airpods-on-arch/ on the assumption
that maybe this is an issue caused by LE communication rather than classic
BR/EDR communication. Alas, my computer wasn't even able to start the pairing
process after making the change.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-01-21 (70 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
InterestingModules: bnep btusb bluetooth
MachineType: Dell Inc. XPS 13 9360
Package: linux
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic
root=UUID=c045330d-1b98-41ff-99cb-26bf69b59fd3 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Tags: third-party-packages bionic
Uname: Linux 4.15.0-46-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/24/2017
dmi.bios.
[Kernel-packages] [Bug 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
Disregard my last comment (#15) ... I was confused for a second between : #define PHYS_MASK ((1UL << PHYS_MASK_SHIFT) - 1) #define PMD_SECTION_MASK((1UL << 40) - 1) so PMD_SECTION_MASK fix is not found in debian yet. I'll sponsor the debdiff over the weekend. - Eric -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux package in Debian: New Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881821] Re: MAAS does not properly detect max interface speed for interfaces which use multiple phyiscal ports(Cisco UCS B200 M5 blade)
Setting to invalid for the kernel.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1881821
Title:
MAAS does not properly detect max interface speed for interfaces which
use multiple phyiscal ports(Cisco UCS B200 M5 blade)
Status in MAAS:
Triaged
Status in MAAS 2.7 series:
Triaged
Status in MAAS 2.8 series:
Triaged
Status in linux package in Ubuntu:
Invalid
Bug description:
MAAS 2.7.1
Ubuntu 18.04.4
When attempting to commission a Cisco UCS B200 M5 blade, the
commissioning finishes (if smartctl-validate is disabled), however on
the machine in question in the Networking tab, it only shows 2 nics,
eth0 and eth1. and shows no storage.
Going to SSH in the middle of commissioning, running lshw shows all 10
NICs, and the disk of the proper size.
This is causing the buckets.yaml for FCE to be inaccurate, and thus
cannot write a bucketsconfig.yaml since the actual devices don't show
up.
This was tried with bionic {ga,hwe,hwe-edge} and focal ga kernels for
commissioning, all have the same behavior.
I was previously hitting this bug
https://bugs.launchpad.net/maas/+bug/1878643 but applied the fix from
comment #10, and am no longer getting any commissioning errors.
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1881821/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
[Groovy sponsoring] At first glance, It seems to be a good candidate for a 'sync' from debian here. https://wiki.ubuntu.com/UbuntuDevelopment/Merging#Check_if_its_a_merge_or_a_sync https://wiki.ubuntu.com/SyncRequestProcess The fix seems to be found in makedumpfile 'unstable' makedumpfile (1:1.6.7-2) # arch/arm64.c 84 #define PMD_SECTION_MASK((1UL << 40) - 1) - Eric -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux package in Debian: New Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
** Patch added: "lp1869465_eoan_v2.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+attachment/5380771/+files/lp1869465_eoan_v2.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux package in Debian: New Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
** Patch added: "lp1869465_groovy_v2.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+attachment/5380769/+files/lp1869465_groovy_v2.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux package in Debian: New Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
** Tags removed: sts-sponsor-mfo ** Tags added: sts-sponsor-mfo-and-slashd -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux package in Debian: New Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
** Patch added: "lp1869465_bionic_v2.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+attachment/5380772/+files/lp1869465_bionic_v2.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux package in Debian: New Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
** Patch added: "lp1869465_xenial_v2.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+attachment/5380773/+files/lp1869465_xenial_v2.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux package in Debian: New Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
** Patch added: "lp1869465_focal_v2.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+attachment/5380770/+files/lp1869465_focal_v2.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux package in Debian: New Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
Hi Jo, Thanks for the debdiffs! The contents look good to me (versioning, dep3 headers) except that the patch sequence number is missing, and the changelog lacks a brief description of it. I just fixed those minor things up, and verified all debdiffs apply cleanly, quilt push -a applies cleanly, and quilt series show the sequence numbers correctly. Attaching the new 'v2' debdiffs. The current status of upload queues, pending SRUs/ -proposed pockets, block-proposed- tags, is all good -- no makedumpfile uploads in progress. This should be good to go. I'll ask a coredev for sponsorship to groovy, and once it's there, I can sponsor for the stable releases. cheers, Mauricio -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux package in Debian: New Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881810] Re: ZFS import cause panic
Added dmesg output ** Attachment added: "dmesg log" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1881810/+attachment/5380764/+files/dm.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1881810 Title: ZFS import cause panic Status in zfs-linux package in Ubuntu: Triaged Bug description: 1) Ubuntu 20.04 LTS 2) apt policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12 Candidate:0.8.3-1ubuntu12 3) ZFS pool not possible to import, unless using read only. If trying to import normal way as write/read, casing panic message Expected to be able to import zpool without panic. Expected that scrub should not be able to run in read only. Expected that somehow be able to restore the zpool somehow. 4) # zpool status no pools available # zpool import pool: datastore id: 3190464655986727485 state: ONLINE status: Some supported features are not enabled on the pool. action: The pool can be imported using its name or numeric identifier, though some features will not be available without an explicit 'zpool upgrade'. config: datastore ONLINE raidz2-0 ONLINE sdb ONLINE sdc ONLINE sdd ONLINE sde ONLINE sdf ONLINE sdg ONLINE # zpool import -o readonly=on datastore # zpool status pool: datastore state: ONLINE status: Some supported features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(5) for details. scan: scrub in progress since Sun May 10 00:24:01 2020 15,1T scanned at 0B/s, 15,1T issued at 0B/s, 15,1T total 1,44M repaired, 100,01% done, no estimated completion time config: NAMESTATE READ WRITE CKSUM datastore ONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 sdb ONLINE 0 0 0 sdc ONLINE 0 0 0 sdd ONLINE 0 0 0 sde ONLINE 0 0 0 sdf ONLINE 0 0 0 sdg ONLINE 0 0 0 errors: No known data errors Running zdb it always stops ad 2,23T and then aborts. # zdb -e -bcsvL datastore Traversing all blocks to verify checksums ... 2.23T completed ( 149MB/s) estimated time remaining: 25hr 06min 25sec free(): invalid pointer Abort (SIGABRT) #zpool import datastore VERIFY3(c < SPA_MAXBLOCKSIZE >> SPA_MINBLOCKSHIFT) failed (36028797018963967 < 32768) PANIC at zio.c:293:zio_buf_alloc() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1881810/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882287] Re: RM signed linux-oem
Separate bug filed for osp1, see full list at https://bugs.launchpad.net/bugs/+bugs?field.tag=rm-signed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1882287 Title: RM signed linux-oem Status in linux-oem package in Ubuntu: Triaged Bug description: linux-oem is remove from the archive please remove http://archive.ubuntu.com/ubuntu/dists/groovy/main/uefi/linux-oem-amd64/ http://archive.ubuntu.com/ubuntu/dists/groovy/main/signed/linux-oem-amd64/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1882287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882287] Re: RM signed linux-oem
same for osp1? or is it gone already -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1882287 Title: RM signed linux-oem Status in linux-oem package in Ubuntu: Triaged Bug description: linux-oem is remove from the archive please remove http://archive.ubuntu.com/ubuntu/dists/groovy/main/uefi/linux-oem-amd64/ http://archive.ubuntu.com/ubuntu/dists/groovy/main/signed/linux-oem-amd64/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1882287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882287] Re: RM signed linux-oem
ack -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1882287 Title: RM signed linux-oem Status in linux-oem package in Ubuntu: Triaged Bug description: linux-oem is remove from the archive please remove http://archive.ubuntu.com/ubuntu/dists/groovy/main/uefi/linux-oem-amd64/ http://archive.ubuntu.com/ubuntu/dists/groovy/main/signed/linux-oem-amd64/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1882287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865149] Status changed to Confirmed
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/1865149 Title: The speakers of the notebook do not sound, but the headphones work Status in linux package in Ubuntu: Confirmed Bug description: Update ubuntu and BIOS. After this, the notebook's speakers do not work, but if I connect the headphones, they sound. == Solution == 1. Start with usb xubuntu 19.10 2. Open mp3 3. Then this mp3 is heard through the headphones and speakers of the notebook 4. Reboot 5. Start with ubuntu 20.04(development) on hard drive 6. Try listening to an mp3 again 7. Now everything works correctly == Others == Now that I remember, this is not the first time that happens to me. It is when the BIOS is updated, then the problem of no sound appears in the speakers of the notebook. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1815 F pulseaudio /dev/snd/pcmC0D0p: caravena 1815 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:06:14 2020 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (452 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-14-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 SourcePackage: linux-5.4 UpgradeStatus: Upgraded to focal on 2018-12-02 (452 days ago) dmi.bios.date: 11/18/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.35:bd11/18/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865149/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867534] Status changed to Confirmed
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/1867534 Title: Wifi requires interruption before timing out (and immediate reconnect attempt succeeds) Status in linux package in Ubuntu: Confirmed Bug description: ISO testing 20.04 Lubuntu daily (20200315). From the Live desktop, I click my nm-tray access point, supply the password. nm-tray will timeout. Trying again will timeout. What works is clicking the same access point a couple times before it times out. This causes an immediate failure and successful connection (two balloon msgs). This problem is not specific to Lubuntu. It happens with Kubuntu, Budgie, Mate, Xubuntu. The common theme is: it appears to be out of sync in some manner. The wifi connection needs to be interrupted before timing out. Then an immediate attempt (within 2-3 seconds? I haven't tested how long it can wait) succeeds. This problem also happens after install and reboot. For example, with yesterday's daily image (20200314), I had to reboot Lubuntu twice after install before the wifi worked. (I haven't reached that point yet today. I'm creating this bug report from the Live desktop. I will update with more info about post-install.). Note: I don't know if this is acceptable wifi behavior. Good enough? I figured I should report it and let someone decide. It seems to be specific to this laptop (Lenovo Thinkpad E440 20C5) or it's Intel 7260 wifi card. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lubuntu1857 F pulseaudio /dev/snd/controlC0: lubuntu1857 F pulseaudio CasperVersion: 1.441 Date: Sun Mar 15 17:17:43 2020 LiveMediaBuild: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: LENOVO 20C5004YUS ProcFB: 0 i915drmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 SourcePackage: linux-5.4 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: J9ETA2WW (2.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C5004YUS dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ9ETA2WW(2.28):bd06/20/2018:svnLENOVO:pn20C5004YUS:pvrThinkPadEdgeE440:rvnLENOVO:rn20C5004YUS:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Edge E440 dmi.product.name: 20C5004YUS dmi.product.sku: LENOVO_MT_20C5_BU_Think_FM_ThinkPad Edge E440 dmi.product.version: ThinkPad Edge E440 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866744] Status changed to Confirmed
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/1866744 Title: package linux-5.4-tools-common (not installed) failed to install/upgrade: tentata sovrascrittura di "/usr/bin/acpidbg" presente anche nel pacchetto linux-tools-common 5.4.0-18.22 Status in linux package in Ubuntu: Confirmed Bug description: non ci sono dettagli. Segna errore di sistema ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-5.4-tools-common (not installed) ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: valerio2636 F pulseaudio Date: Tue Mar 10 09:53:08 2020 ErrorMessage: tentata sovrascrittura di "/usr/bin/acpidbg" presente anche nel pacchetto linux-tools-common 5.4.0-18.22 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200308) IwConfig: enp1s0no wireless extensions. enp3s2no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=ada6a835-d362-43fd-b1e0-0fd23cf528b3 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: linux-5.4 Title: package linux-5.4-tools-common (not installed) failed to install/upgrade: tentata sovrascrittura di "/usr/bin/acpidbg" presente anche nel pacchetto linux-tools-common 5.4.0-18.22 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: G41M-VS3. dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd05/18/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnG41M-VS3.:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882285] [NEW] package linux-image-4.4.0-171-generic 4.4.0-171.200 failed to install/upgrade: package linux-image-4.4.0-171-generic is not ready for configuration cannot configu
Public bug reported: Bug ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-171-generic 4.4.0-171.200 ProcVersionSignature: Ubuntu 4.4.0-176.206-generic 4.4.211 Uname: Linux 4.4.0-176-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Fri Jun 5 14:50:15 2020 DuplicateSignature: package:linux-image-4.4.0-171-generic:4.4.0-171.200 Setting up linux-modules-4.4.0-154-generic (4.4.0-154.181) ... dpkg: error processing package linux-image-4.4.0-154-generic (--configure): package linux-image-4.4.0-154-generic is not ready for configuration ErrorMessage: package linux-image-4.4.0-171-generic is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2019-05-12 (390 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.1 SourcePackage: linux-signed Title: package linux-image-4.4.0-171-generic 4.4.0-171.200 failed to install/upgrade: package linux-image-4.4.0-171-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1882285 Title: package linux-image-4.4.0-171-generic 4.4.0-171.200 failed to install/upgrade: package linux-image-4.4.0-171-generic is not ready for configuration cannot configure (current status 'half-installed') Status in linux-signed package in Ubuntu: New Bug description: Bug ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-171-generic 4.4.0-171.200 ProcVersionSignature: Ubuntu 4.4.0-176.206-generic 4.4.211 Uname: Linux 4.4.0-176-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Fri Jun 5 14:50:15 2020 DuplicateSignature: package:linux-image-4.4.0-171-generic:4.4.0-171.200 Setting up linux-modules-4.4.0-154-generic (4.4.0-154.181) ... dpkg: error processing package linux-image-4.4.0-154-generic (--configure): package linux-image-4.4.0-154-generic is not ready for configuration ErrorMessage: package linux-image-4.4.0-171-generic is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2019-05-12 (390 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.1 SourcePackage: linux-signed Title: package linux-image-4.4.0-171-generic 4.4.0-171.200 failed to install/upgrade: package linux-image-4.4.0-171-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1882285/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867455] Status changed to Confirmed
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/1867455 Title: Having more than one AMD Radeon RX 580 installed will trigger a PCIe bus fatal error during boot. Status in linux package in Ubuntu: Confirmed Bug description: I have a Dell R920 with three MSI Radeon RX 580 8G V1 cards, if more than one of these cards is installed in the system, a bus fatal error will be generated causing the system to reset itself when the amdgpu module is loaded and it tries to initialize the device. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-14-lowlatency 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18 Uname: Linux 5.4.0-14-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Mar 14 12:20:47 2020 Dependencies: MachineType: Dell Inc. PowerEdge R920 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-14-lowlatency root=ZFS=rpool/ROOT/ubuntu ro intel_iommu=on iommu=pt root=ZFS=rpool/ROOT/ubuntu intremap=no_x2apic_optout ipv6.disable=1 mitigations=off PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-14-lowlatency N/A linux-backports-modules-5.4.0-14-lowlatency N/A linux-firmware 1.186 RfKill: SourcePackage: linux-5.4 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.0 dmi.board.name: 0V7HD0 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.0:bd06/26/2019:svnDellInc.:pnPowerEdgeR920:pvr:rvnDellInc.:rn0V7HD0:rvrA06:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R920 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866749] Status changed to Confirmed
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/1866749 Title: package linux-image-5.4.0-14-generic 5.4.0-14.17 failed to install/upgrade: il sottoprocesso installato pacchetto linux- image-5.4.0-14-generic script pre-removal ha restituito lo stato di errore 1 Status in linux package in Ubuntu: Confirmed Bug description: in realta e il 5.4.0-18 che crea probemi e non va prorio ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: valerio3524 F pulseaudio Date: Tue Mar 10 11:53:46 2020 ErrorMessage: il sottoprocesso installato pacchetto linux-image-5.4.0-14-generic script pre-removal ha restituito lo stato di errore 1 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200308) IwConfig: enp3s2no wireless extensions. enp1s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=ada6a835-d362-43fd-b1e0-0fd23cf528b3 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: linux-5.4 Title: package linux-image-5.4.0-14-generic 5.4.0-14.17 failed to install/upgrade: il sottoprocesso installato pacchetto linux-image-5.4.0-14-generic script pre-removal ha restituito lo stato di errore 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: G41M-VS3. dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd05/18/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnG41M-VS3.:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882283] [NEW] RM signed linux-azure-amd64
Public bug reported: RM signed linux-azure-amd64 linux-azure-amd64 switched from uefi to signed layout please remove obsolete http://archive.ubuntu.com/ubuntu/dists/groovy/main/uefi/linux-azure- amd64/ ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Triaged ** Tags: rm-signed -- 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/1882283 Title: RM signed linux-azure-amd64 Status in linux-azure package in Ubuntu: Triaged Bug description: RM signed linux-azure-amd64 linux-azure-amd64 switched from uefi to signed layout please remove obsolete http://archive.ubuntu.com/ubuntu/dists/groovy/main/uefi/linux-azure- amd64/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1882283/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867141] Status changed to Confirmed
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/1867141 Title: BUG: Bad rss-counter state mm:f676147b type:MM_SWAPENTS val:-1 Status in linux package in Ubuntu: Confirmed Bug description: 1. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. linux-generic: Installed: 5.4.0.14.17 Candidate: 5.4.0.14.17 Version table: *** 5.4.0.14.17 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. I expected my desktop computer to log in without an error message. 4. An error message popped up That happened after I installed 71 upgraded packages, then logged out of my Ubuntu session, then logged back in. Perhaps I should have rebooted? ProblemType: KernelOops DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nick 139333 F pulseaudio /dev/snd/controlC0: nick 139333 F pulseaudio Date: Tue Mar 10 21:05:30 2020 Failure: oops IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: ASUSTeK Computer INC. CM1630 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-14-generic root=UUID=d0f01318-e4c8-4bc1-a9e9-63574bcc9718 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux-5.4 Title: BUG: Bad rss-counter state mm:f676147b type:MM_SWAPENTS val:-1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: CM1630 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd05/20/2010:svnASUSTeKComputerINC.:pnCM1630:pvrSystemVersion:rvnASUSTeKComputerINC.:rnCM1630:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: CM1630 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867141/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866172] Status changed to Confirmed
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/1866172 Title: xubuntu 20.04 'live' qa-test; suspend, resume but system froze on waking Status in linux package in Ubuntu: Confirmed Bug description: Xubuntu daily test (20.04) on dell vostro 430 (i7-870, 8gb, nvidia geforce gt 6600 gt) test went well, then I suspended system, waited, on resume (keystroke) system appeared to stop with mucked-up but mostly-recognizable display (https://photos.app.goo.gl/2kSU5SubdbkdpFUcA) I was unable to use any keyboard input to switch to terminal, or gain any clues (sorry keyboard didn't have sysrq key to see if kernel was up). I rebooted the system which is when `ubuntu-bug linux` was ran. After this bug was submitted I suspended system, waited & it resumed correctly. I suspended it again, waited & it resumed normally; so the issue doesn't occur all the time. Because CTRL+ALT+T wasn't working (different issue; https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1827459), nor menu items having icons etc, I `xfsettingsd --replace` to fix that issue & suspended again.. This time the system didn't resume reliably. This time however it was not as I'm describing above, as the screen was correctly drawn. The mouse-pointer was visible but static, then appeared to move (following my movements) before disappearing, redrawn but static again .. IF the system was 'up', it'd become super slow; and I eventually turned box off. I'll retest on requests (too tried now) photo of screen on resume : https://photos.app.goo.gl/2kSU5SubdbkdpFUcA ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4057 F pulseaudio CasperVersion: 1.441 CurrentDesktop: XFCE Date: Thu Mar 5 10:35:57 2020 IwConfig: enp2s0no wireless extensions. lono wireless extensions. LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200305) MachineType: Dell Inc. Vostro 430 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 RfKill: SourcePackage: linux-5.4 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 054KM3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd01/13/2011:svnDellInc.:pnVostro430:pvr00:rvnDellInc.:rn054KM3:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: 0 dmi.product.name: Vostro 430 dmi.product.sku: 0 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866172/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882284] [NEW] RM signed linux-amd64
Public bug reported: RM signed linux-amd64 linux-amd64 switched from uefi to signed layout please remove obsolete http://archive.ubuntu.com/ubuntu/dists/groovy/main/uefi/linux-amd64/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Triaged ** Tags: rm-signed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882284 Title: RM signed linux-amd64 Status in linux package in Ubuntu: Triaged Bug description: RM signed linux-amd64 linux-amd64 switched from uefi to signed layout please remove obsolete http://archive.ubuntu.com/ubuntu/dists/groovy/main/uefi/linux-amd64/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882285] Re: package linux-image-4.4.0-171-generic 4.4.0-171.200 failed to install/upgrade: package linux-image-4.4.0-171-generic is not ready for configuration cannot configure
** Tags removed: need-duplicate-check -- 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/1882285 Title: package linux-image-4.4.0-171-generic 4.4.0-171.200 failed to install/upgrade: package linux-image-4.4.0-171-generic is not ready for configuration cannot configure (current status 'half-installed') Status in linux-signed package in Ubuntu: New Bug description: Bug ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-171-generic 4.4.0-171.200 ProcVersionSignature: Ubuntu 4.4.0-176.206-generic 4.4.211 Uname: Linux 4.4.0-176-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Fri Jun 5 14:50:15 2020 DuplicateSignature: package:linux-image-4.4.0-171-generic:4.4.0-171.200 Setting up linux-modules-4.4.0-154-generic (4.4.0-154.181) ... dpkg: error processing package linux-image-4.4.0-154-generic (--configure): package linux-image-4.4.0-154-generic is not ready for configuration ErrorMessage: package linux-image-4.4.0-171-generic is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2019-05-12 (390 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.1 SourcePackage: linux-signed Title: package linux-image-4.4.0-171-generic 4.4.0-171.200 failed to install/upgrade: package linux-image-4.4.0-171-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1882285/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882287] [NEW] RM signed linux-oem
Public bug reported: linux-oem is remove from the archive please remove http://archive.ubuntu.com/ubuntu/dists/groovy/main/uefi/linux-oem-amd64/ http://archive.ubuntu.com/ubuntu/dists/groovy/main/signed/linux-oem-amd64/ ** Affects: linux-oem (Ubuntu) Importance: Undecided Status: Triaged ** Tags: rm-signed ** Tags added: rm-signed ** Changed in: linux-oem (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1882287 Title: RM signed linux-oem Status in linux-oem package in Ubuntu: Triaged Bug description: linux-oem is remove from the archive please remove http://archive.ubuntu.com/ubuntu/dists/groovy/main/uefi/linux-oem-amd64/ http://archive.ubuntu.com/ubuntu/dists/groovy/main/signed/linux-oem-amd64/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1882287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882194] Re: Intel Wireless 7265 [8086:095a] Subsystem [8086:5010] not probed after kernel packages upgrade failures
There's now a dependencies issue. ** Attachment added: "Screenshot from 2020-06-05 13-48-29.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882194/+attachment/5380753/+files/Screenshot%20from%202020-06-05%2013-48-29.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882194 Title: Intel Wireless 7265 [8086:095a] Subsystem [8086:5010] not probed after kernel packages upgrade failures Status in linux package in Ubuntu: Incomplete Bug description: Hello. I previously tried to manually update the kernel via Terminal and ran into a series of errors from the apt which refused to fully install the kernet update. After several unsuccessful attempt through various other Terminal means, the update seemed to be accepted; but after rebooting my machine; the Intel WiFi drivers collapsed and I no longer could connect to the internet. After reinstalling previously saved Intel drivers from my Trash bin, I managed to get the Bluetooth to work, and then I used the UBS tethering feature of my startphone to connect this machine to the Internet, which till this moment; is my only method of going online. I consulted with a professioanl web-developer from Europe, whom confirmed this bug and suggested I report it; which I am now doing. Thanks to the kernel developers for all your hard work. You're such appreciated! ;-) PS: Here's additional info --- frederick@frederickpina:~$ cat/proc/version_signature>version.log bash: cat/proc/version_signature: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: frederick 1983 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 5 02:13:54 2020 InstallationDate: Installed on 2020-01-30 (126 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. usb0 no wireless extensions. MachineType: HP HP Spectre x360 Convertible 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=/boot/vmlinuz-5.4.0-33-generic root=UUID=3ad1fd87-8287-4943-af05-e0fcb04a210d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-24 (41 days ago) dmi.bios.date: 05/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8174 dmi.board.vendor: HP dmi.board.version: 38.41 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.21:bd05/16/2019:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn8174:rvr38.41:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible dmi.product.sku: T6T09UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882194] Re: Intel Wireless 7265 [8086:095a] Subsystem [8086:5010] not probed after kernel packages upgrade failures
## frederick@frederickpina:~$ dkms status I had to install the dkms in a prior window, so after putting this command; it did nothing on the command prompt. ## frederick@frederickpina:~$ sudo apt install linux-generic [sudo] password for frederick: Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: amd64-microcode intel-microcode iucode-tool linux-image-generic linux-modules-extra-5.4.0-33-generic thermald The following NEW packages will be installed: amd64-microcode intel-microcode iucode-tool linux-generic linux-image-generic linux-modules-extra-5.4.0-33-generic thermald 0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded. Need to get 2,686 kB/41.2 MB of archives. After this operation, 193 MB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://archive.ubuntu.com/ubuntu focal/main amd64 iucode-tool amd64 2.3.1-1 [45.6 kB] Get:2 http://archive.ubuntu.com/ubuntu focal/main amd64 intel-microcode amd64 3.20191115.1ubuntu3 [2,408 kB] Get:3 http://archive.ubuntu.com/ubuntu focal/main amd64 amd64-microcode amd64 3.20191218.1ubuntu1 [31.8 kB] Get:4 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-image-generic amd64 5.4.0.33.38 [2,708 B] Get:5 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-generic amd64 5.4.0.33.38 [1,900 B] Get:6 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 thermald amd64 1.9.1-1ubuntu0.1 [197 kB] Fetched 2,686 kB in 10s (278 kB/s) Selecting previously unselected package iucode-tool. (Reading database ... 236167 files and directories currently installed.) Preparing to unpack .../0-iucode-tool_2.3.1-1_amd64.deb ... Unpacking iucode-tool (2.3.1-1) ... Preparing to unpack .../1-linux-modules-extra-5.4.0-33-generic_5.4.0-33.37_amd64 .deb ... Unpacking linux-modules-extra-5.4.0-33-generic (5.4.0-33.37) ... dpkg: error processing archive /tmp/apt-dpkg-install-inlA7E/1-linux-modules-extr a-5.4.0-33-generic_5.4.0-33.37_amd64.deb (--unpack): unable to open '/lib/modules/5.4.0-33-generic/kernel/drivers/scsi/pcmcia/qlogic _cs.ko.dpkg-new': Operation not permitted Selecting previously unselected package intel-microcode. Preparing to unpack .../2-intel-microcode_3.20191115.1ubuntu3_amd64.deb ... Unpacking intel-microcode (3.20191115.1ubuntu3) ... Selecting previously unselected package amd64-microcode. Preparing to unpack .../3-amd64-microcode_3.20191218.1ubuntu1_amd64.deb ... Unpacking amd64-microcode (3.20191218.1ubuntu1) ... Selecting previously unselected package linux-image-generic. Preparing to unpack .../4-linux-image-generic_5.4.0.33.38_amd64.deb ... Unpacking linux-image-generic (5.4.0.33.38) ... Selecting previously unselected package linux-generic. Preparing to unpack .../5-linux-generic_5.4.0.33.38_amd64.deb ... Unpacking linux-generic (5.4.0.33.38) ... Selecting previously unselected package thermald. Preparing to unpack .../6-thermald_1.9.1-1ubuntu0.1_amd64.deb ... Unpacking thermald (1.9.1-1ubuntu0.1) ... Errors were encountered while processing: /tmp/apt-dpkg-install-inlA7E/1-linux-modules-extra-5.4.0-33-generic_5.4.0-33.37 _amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) frederick@frederickpina:~$ I'm not sure what this error is or means... ??? ## -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882194 Title: Intel Wireless 7265 [8086:095a] Subsystem [8086:5010] not probed after kernel packages upgrade failures Status in linux package in Ubuntu: Incomplete Bug description: Hello. I previously tried to manually update the kernel via Terminal and ran into a series of errors from the apt which refused to fully install the kernet update. After several unsuccessful attempt through various other Terminal means, the update seemed to be accepted; but after rebooting my machine; the Intel WiFi drivers collapsed and I no longer could connect to the internet. After reinstalling previously saved Intel drivers from my Trash bin, I managed to get the Bluetooth to work, and then I used the UBS tethering feature of my startphone to connect this machine to the Internet, which till this moment; is my only method of going online. I consulted with a professioanl web-developer from Europe, whom confirmed this bug and suggested I report it; which I am now doing. Thanks to the kernel developers for all your hard work. You're such appreciated! ;-) PS: Here's additional info --- frederick@frederickpina:~$ cat/pr
[Kernel-packages] [Bug 1867455] Re: Having more than one AMD Radeon RX 580 installed will trigger a PCIe bus fatal error during boot.
** Package changed: linux-5.4 (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867455 Title: Having more than one AMD Radeon RX 580 installed will trigger a PCIe bus fatal error during boot. Status in linux package in Ubuntu: Confirmed Bug description: I have a Dell R920 with three MSI Radeon RX 580 8G V1 cards, if more than one of these cards is installed in the system, a bus fatal error will be generated causing the system to reset itself when the amdgpu module is loaded and it tries to initialize the device. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-14-lowlatency 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18 Uname: Linux 5.4.0-14-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Mar 14 12:20:47 2020 Dependencies: MachineType: Dell Inc. PowerEdge R920 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-14-lowlatency root=ZFS=rpool/ROOT/ubuntu ro intel_iommu=on iommu=pt root=ZFS=rpool/ROOT/ubuntu intremap=no_x2apic_optout ipv6.disable=1 mitigations=off PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-14-lowlatency N/A linux-backports-modules-5.4.0-14-lowlatency N/A linux-firmware 1.186 RfKill: SourcePackage: linux-5.4 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.0 dmi.board.name: 0V7HD0 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.0:bd06/26/2019:svnDellInc.:pnPowerEdgeR920:pvr:rvnDellInc.:rn0V7HD0:rvrA06:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R920 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867534] Re: Wifi requires interruption before timing out (and immediate reconnect attempt succeeds)
** Package changed: linux-5.4 (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867534 Title: Wifi requires interruption before timing out (and immediate reconnect attempt succeeds) Status in linux package in Ubuntu: Confirmed Bug description: ISO testing 20.04 Lubuntu daily (20200315). From the Live desktop, I click my nm-tray access point, supply the password. nm-tray will timeout. Trying again will timeout. What works is clicking the same access point a couple times before it times out. This causes an immediate failure and successful connection (two balloon msgs). This problem is not specific to Lubuntu. It happens with Kubuntu, Budgie, Mate, Xubuntu. The common theme is: it appears to be out of sync in some manner. The wifi connection needs to be interrupted before timing out. Then an immediate attempt (within 2-3 seconds? I haven't tested how long it can wait) succeeds. This problem also happens after install and reboot. For example, with yesterday's daily image (20200314), I had to reboot Lubuntu twice after install before the wifi worked. (I haven't reached that point yet today. I'm creating this bug report from the Live desktop. I will update with more info about post-install.). Note: I don't know if this is acceptable wifi behavior. Good enough? I figured I should report it and let someone decide. It seems to be specific to this laptop (Lenovo Thinkpad E440 20C5) or it's Intel 7260 wifi card. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lubuntu1857 F pulseaudio /dev/snd/controlC0: lubuntu1857 F pulseaudio CasperVersion: 1.441 Date: Sun Mar 15 17:17:43 2020 LiveMediaBuild: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: LENOVO 20C5004YUS ProcFB: 0 i915drmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 SourcePackage: linux-5.4 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: J9ETA2WW (2.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C5004YUS dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ9ETA2WW(2.28):bd06/20/2018:svnLENOVO:pn20C5004YUS:pvrThinkPadEdgeE440:rvnLENOVO:rn20C5004YUS:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Edge E440 dmi.product.name: 20C5004YUS dmi.product.sku: LENOVO_MT_20C5_BU_Think_FM_ThinkPad Edge E440 dmi.product.version: ThinkPad Edge E440 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882194] Re: Intel Wireless 7265 [8086:095a] Subsystem [8086:5010] not probed after kernel packages upgrade failures
This looks very familiar, this operation not permitted error: frederick@frederickpina:~$ sudo apt-get install -f Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-modules-extra-5.4.0-33-generic The following NEW packages will be installed: linux-modules-extra-5.4.0-33-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 6 not fully installed or removed. Need to get 0 B/38.5 MB of archives. After this operation, 189 MB of additional disk space will be used. Do you want to continue? [Y/n] Y (Reading database ... 236296 files and directories currently installed.) Preparing to unpack .../linux-modules-extra-5.4.0-33-generic_5.4.0-33.37_amd64.deb ... Unpacking linux-modules-extra-5.4.0-33-generic (5.4.0-33.37) ... dpkg: error processing archive /var/cache/apt/archives/linux-modules-extra-5.4.0-33-generic_5.4.0-33.37_amd64.deb (--unpack): unable to open '/lib/modules/5.4.0-33-generic/kernel/drivers/media/dvb-frontends/cx22700.ko.dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-modules-extra-5.4.0-33-generic_5.4.0-33.37_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) frederick@frederickpina:~$ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882194 Title: Intel Wireless 7265 [8086:095a] Subsystem [8086:5010] not probed after kernel packages upgrade failures Status in linux package in Ubuntu: Incomplete Bug description: Hello. I previously tried to manually update the kernel via Terminal and ran into a series of errors from the apt which refused to fully install the kernet update. After several unsuccessful attempt through various other Terminal means, the update seemed to be accepted; but after rebooting my machine; the Intel WiFi drivers collapsed and I no longer could connect to the internet. After reinstalling previously saved Intel drivers from my Trash bin, I managed to get the Bluetooth to work, and then I used the UBS tethering feature of my startphone to connect this machine to the Internet, which till this moment; is my only method of going online. I consulted with a professioanl web-developer from Europe, whom confirmed this bug and suggested I report it; which I am now doing. Thanks to the kernel developers for all your hard work. You're such appreciated! ;-) PS: Here's additional info --- frederick@frederickpina:~$ cat/proc/version_signature>version.log bash: cat/proc/version_signature: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: frederick 1983 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 5 02:13:54 2020 InstallationDate: Installed on 2020-01-30 (126 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. usb0 no wireless extensions. MachineType: HP HP Spectre x360 Convertible 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=/boot/vmlinuz-5.4.0-33-generic root=UUID=3ad1fd87-8287-4943-af05-e0fcb04a210d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-24 (41 days ago) dmi.bios.date: 05/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8174 dmi.board.vendor: HP dmi.board.version: 38.41 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.21:bd05/16/2019:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn8174:rvr38.41:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible dmi.product.sku: T6T09UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-p
[Kernel-packages] [Bug 1866984] Re: linux-5.4 regression: hibernate-disk resumes instantly
** Package changed: linux-5.4 (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866984 Title: linux-5.4 regression: hibernate-disk resumes instantly Status in hibernate package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading from 19.10 (eoan) to 20.04 (focal), hibernate-disk fails to properly hibernate and shutdown the system; instead, Ubuntu resumes instantly. $ sudo hibernate-disk [sudo] password for xyz: hibernate-disk:Warning: Tuxonice binary signature file not found. $ (Note that this warning has been there earlier and is presumably not associated with this bug.) Expected: Switch to console, memory-page writeout progress indication, poweroff Observed: Switch to console, very quickly switch back to X11 Excerpt from dmesg: [ 418.377514] usbcore: deregistering interface driver uvcvideo [ 419.227465] Filesystems sync: 0.006 seconds [ 419.227468] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 419.229889] OOM killer disabled. [ 419.230429] PM: Marking nosave pages: [mem 0x-0x0fff] [ 419.230432] PM: Marking nosave pages: [mem 0x0009d000-0x000f] [ 419.230440] PM: Marking nosave pages: [mem 0x99438000-0x] [ 419.233760] PM: Basic memory bitmaps created [ 419.234176] PM: Preallocating image memory... done (allocated 1188843 pages) [ 420.040021] PM: Allocated 4755372 kbytes in 0.80 seconds (5944.21 MB/s) [ 420.040021] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 420.041324] printk: Suspending console(s) (use no_console_suspend to debug) [ 420.041755] wlp3s0: deauthenticating from cc:ce:1e:61:2e:d0 by local choice (Reason: 3=DEAUTH_LEAVING) [ 421.278599] ACPI: EC: interrupt blocked [ 421.297107] ACPI: Preparing to enter system sleep state S4 [ 421.301832] ACPI: EC: event blocked [ 421.301833] ACPI: EC: EC stopped [ 421.301834] PM: Saving platform NVS memory [ 421.302557] Disabling non-boot CPUs ... [ 421.303996] smpboot: CPU 1 is now offline [ 421.307624] smpboot: CPU 2 is now offline [ 421.309904] IRQ 129: no longer affine to CPU3 [ 421.310921] smpboot: CPU 3 is now offline [ 421.314818] smpboot: CPU 4 is now offline [ 421.317033] IRQ 16: no longer affine to CPU5 [ 421.317040] IRQ 132: no longer affine to CPU5 [ 421.318049] smpboot: CPU 5 is now offline [ 421.320365] IRQ 126: no longer affine to CPU6 [ 421.320373] IRQ 130: no longer affine to CPU6 [ 421.321405] smpboot: CPU 6 is now offline [ 421.325743] smpboot: CPU 7 is now offline [ 421.330059] PM: Creating hibernation image: [ 422.045974] PM: Need to copy 1182218 pages [ 422.045977] PM: Normal pages needed: 1182218 + 1024, available pages: 7053219 [ 423.427947] PM: Hibernation image created (1182218 pages copied) [ 421.330504] PM: Restoring platform NVS memory [ 421.330638] ACPI: EC: EC started [ 421.331412] Enabling non-boot CPUs ... [ 421.331453] x86: Booting SMP configuration: [ 421.331454] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 421.332297] CPU1 is up [ 421.332327] smpboot: Booting Node 0 Processor 2 APIC 0x4 [ 421.333137] CPU2 is up [ 421.333164] smpboot: Booting Node 0 Processor 3 APIC 0x6 [ 421.333987] CPU3 is up [ 421.334013] smpboot: Booting Node 0 Processor 4 APIC 0x1 [ 421.334926] CPU4 is up [ 421.334956] smpboot: Booting Node 0 Processor 5 APIC 0x3 [ 421.335640] CPU5 is up [ 421.335666] smpboot: Booting Node 0 Processor 6 APIC 0x5 [ 421.336447] CPU6 is up [ 421.336469] smpboot: Booting Node 0 Processor 7 APIC 0x7 [ 421.337232] CPU7 is up [ 421.340095] ACPI: Waking up from system sleep state S4 [ 421.347884] ACPI: EC: interrupt unblocked [ 421.390488] ACPI: EC: event unblocked [ 421.391425] tpm tpm0: tpm_try_transmit: send(): error -5 [ 421.403775] iwlwifi :03:00.0: Applying debug destination EXTERNAL_DRAM [ 421.553049] iwlwifi :03:00.0: Applying debug destination EXTERNAL_DRAM [ 421.603306] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [ 421.634367] iwlwifi :03:00.0: FW already configured (0) - re-configuring [ 421.714565] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 421.715010] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [ 421.715012] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 421.715083] ata1.00: ACPI cmd ef/10:09:00:00:00:a0 (SET FEATURES) succeeded [ 421.715396] ata1.00: supports DRM functions and may not be fully accessible [ 421.716087] ata1.00: disabling queued TRIM support [ 421.718110] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES)
[Kernel-packages] [Bug 1867141] Re: BUG: Bad rss-counter state mm:00000000f676147b type:MM_SWAPENTS val:-1
** Package changed: linux-5.4 (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867141 Title: BUG: Bad rss-counter state mm:f676147b type:MM_SWAPENTS val:-1 Status in linux package in Ubuntu: Confirmed Bug description: 1. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. linux-generic: Installed: 5.4.0.14.17 Candidate: 5.4.0.14.17 Version table: *** 5.4.0.14.17 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. I expected my desktop computer to log in without an error message. 4. An error message popped up That happened after I installed 71 upgraded packages, then logged out of my Ubuntu session, then logged back in. Perhaps I should have rebooted? ProblemType: KernelOops DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nick 139333 F pulseaudio /dev/snd/controlC0: nick 139333 F pulseaudio Date: Tue Mar 10 21:05:30 2020 Failure: oops IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: ASUSTeK Computer INC. CM1630 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-14-generic root=UUID=d0f01318-e4c8-4bc1-a9e9-63574bcc9718 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux-5.4 Title: BUG: Bad rss-counter state mm:f676147b type:MM_SWAPENTS val:-1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: CM1630 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd05/20/2010:svnASUSTeKComputerINC.:pnCM1630:pvrSystemVersion:rvnASUSTeKComputerINC.:rnCM1630:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: CM1630 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867141/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879807] Re: 5.3.0-53 Kernel system falis to reboot after install
*** This bug is a duplicate of bug 1880041 *** https://bugs.launchpad.net/bugs/1880041 I'm algo having this issue. AMD 3200G with its onboard Vega 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/1879807 Title: 5.3.0-53 Kernel system falis to reboot after install Status in linux package in Ubuntu: Confirmed Bug description: I cant post the requested terminal outputs because I can't install the kernel, but here is the system information: System:Host: LM Kernel: 5.3.0-51-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin dm: LightDM Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic Machine: Type: Desktop Mobo: ASRock model: A300M-STX serial: UEFI: American Megatrends v: P3.60 date: 10/28/2019 Battery: Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: charge: 55% status: Discharging CPU: Topology: Quad Core model: AMD Ryzen 3 3200G with Radeon Vega Graphics bits: 64 type: MCP arch: Zen rev: 1 L2 cache: 2048 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 28803 Speed: 1600 MHz min/max: 1400/3600 MHz Core speeds (MHz): 1: 1600 2: 1600 3: 4000 4: 1600 Graphics: Device-1: AMD Picasso driver: amdgpu v: kernel bus ID: 04:00.0 chip ID: 1002:15d8 Display: x11 server: X.Org 1.20.5 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz OpenGL: renderer: AMD RAVEN (DRM 3.33.0 5.3.0-51-generic LLVM 9.0.0) v: 4.5 Mesa 19.2.8 direct render: Yes Audio: Device-1: AMD driver: snd_hda_intel v: kernel bus ID: 04:00.1 chip ID: 1002:15de Device-2: AMD vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 04:00.6 chip ID: 1022:15e3 Sound Server: ALSA v: k5.3.0-51-generic Network: Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi v: kernel bus ID: 02:00.0 chip ID: 8086:24fb IF: wlp2s0 state: down mac: Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock driver: r8169 v: kernel port: f000 bus ID: 03:00.0 chip ID: 10ec:8168 IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: Drives:Local Storage: total: 350.27 GiB used: 18.08 GiB (5.2%) ID-1: /dev/nvme0n1 vendor: Toshiba model: RD400 size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: ID-2: /dev/sda vendor: Crucial model: CT120BX500SSD1 size: 111.79 GiB speed: 6.0 Gb/s serial: temp: 39 C Partition: ID-1: / size: 233.26 GiB used: 10.51 GiB (4.5%) fs: ext4 dev: /dev/nvme0n1p2 USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip ID: 1d6b:0002 Hub: 1-3:2 info: Genesys Logic Hub ports: 4 rev: 2.0 chip ID: 05e3:0608 Device-1: 1-3.1:3 info: Intel type: Bluetooth driver: btusb rev: 2.0 chip ID: 8087:0aa7 Hub: 1-3.2:4 info: Genesys Logic Hub ports: 4 rev: 2.0 chip ID: 05e3:0608 Device-2: 1-3.2.2:5 info: Logitech Illuminated Keyboard type: Keyboard,Mouse driver: hid-generic,usbhid rev: 2.0 chip ID: 046d:c318 Device-3: 1-3.2.3:6 info: Logitech Unifying Receiver type: Mouse,HID driver: logitech-djreceiver,usbhid rev: 2.0 chip ID: 046d:c52f Hub: 2-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.1 chip ID: 1d6b:0003 Hub: 3-0:1 info: Full speed (or root) Hub ports: 1 rev: 2.0 chip ID: 1d6b:0002 Hub: 4-0:1 info: Full speed (or root) Hub ports: 1 rev: 3.1 chip ID: 1d6b:0003 Sensors: System Temperatures: cpu: 38.5 C mobo: N/A Fan Speeds (RPM): N/A Repos: No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 1: deb [arch=amd64] http: //dl.google.com/linux/chrome/deb/ stable main Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list 1: deb [arch=amd64] http: //dl.google.com/linux/earth/deb/ stable main Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 1: deb http: //mirror.clarkson.edu/linuxmint/packages tricia main upstream import backport 2: deb http: //archive.linux.duke.edu/ubuntu bionic main restricted universe multiverse 3: deb http: //archive.linux.duke.edu/ubuntu bionic-updates main restricted universe multiverse 4: deb http: //archive.linux.duke.edu/ubuntu bionic-backports main restricted universe multiverse 5: deb http: //security.ubuntu.com/ubuntu/ bionic-security m
[Kernel-packages] [Bug 1863116] Re: debian/rules editconfigs does not work on s390x to change s390x only configs
** Changed in: linux-5.4 (Ubuntu) Status: New => Invalid ** No longer affects: linux-5.4 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1863116 Title: debian/rules editconfigs does not work on s390x to change s390x only configs Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: On s390x pull-lp-source linux-5.4 cd linux-* fakeroot ./debian/rules clean ./debian/rules editconfig dh_testdir; /bin/bash -e debian/scripts/misc/kernelconfig editconfigs Do you want to edit config: amd64/config.flavour.generic? [Y/n] n ... scripts/Kconfig.include:35: compiler 'x86_64-linux-gnu-gcc' not found make[3]: *** [../scripts/kconfig/Makefile:73: syncconfig] Error 1 make[2]: *** [/home/ubuntu/linux-5.4-5.4.0/Makefile:594: syncconfig] Error 2 make[2]: Leaving directory '/home/ubuntu/linux-5.4-5.4.0/build' make[1]: *** [Makefile:179: sub-make] Error 2 make[1]: Leaving directory '/home/ubuntu/linux-5.4-5.4.0' make: *** [debian/rules.d/1-maintainer.mk:44: editconfigs] Error 2 And indeed i do not have x86_64-linux-gnu-gcc crosscompiler available to build on s390x for amd64, and also I don't want to touch amd64 configs. Only s390x ones. As a user, I should be able to rebuild ports architecture kernel with tweaked config for testing, self-hosted without cross-compilers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1863116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860126] Re: Focal update: v5.4.9 upstream stable release
** Package changed: linux-5.4 (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860126 Title: Focal update: v5.4.9 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed 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.9 upstream stable release from git://git.kernel.org/ Linux 5.4.9 mm/hugetlb: defer freeing of huge pages if in non-task context hsr: fix a race condition in node list insertion and deletion hsr: fix error handling routine in hsr_dev_finalize() hsr: avoid debugfs warning message when module is remove net: annotate lockless accesses to sk->sk_pacing_shift perf/x86/intel/bts: Fix the use of page_private() efi: Don't attempt to map RCI2 config table if it doesn't exist lib/ubsan: don't serialize UBSAN report xen/blkback: Avoid unmapping unmapped grant pages mm/sparse.c: mark populate_section_memmap as __meminit s390/smp: fix physical to logical CPU map for SMT Btrfs: only associate the locked page with one async_chunk struct btrfs: get rid of unique workqueue helper functions ubifs: ubifs_tnc_start_commit: Fix OOB in layout_in_gaps net: add annotations on hh->hh_len lockless accesses xfs: periodically yield scrub threads to the scheduler drm/i915/execlists: Fix annotation for decoupling virtual request ath9k_htc: Discard undersized packets ath9k_htc: Modify byte order for an error message fix compat handling of FICLONERANGE, FIDEDUPERANGE and FS_IOC_FIEMAP fs: cifs: Fix atime update check vs mtime cifs: Fix lookup of root ses in DFS referral cache tty: serial: msm_serial: Fix lockup for sysrq and oops phy: renesas: rcar-gen3-usb2: Use platform_get_irq_optional() for optional irq arm64: dts: meson: odroid-c2: Disable usb_otg bus to avoid power failed warning dt-bindings: clock: renesas: rcar-usb2-clock-sel: Fix typo in example media: usb: fix memory leak in af9005_identify_state regulator: ab8500: Remove AB8505 USB regulator media: flexcop-usb: ensure -EIO is returned on error condition arm64: dts: meson-gxm-khadas-vim2: fix uart_A bluetooth node arm64: dts: meson-gxl-s905x-khadas-vim: fix uart_A bluetooth node Bluetooth: Fix memory leak in hci_connect_le_scan Bluetooth: delete a stray unlock Bluetooth: btusb: fix PM leak in error case of setup powerpc/mm: Mark get_slice_psize() & slice_addr_is_low() as notrace regulator: axp20x: Fix AXP22x ELDO2 regulator enable bitmask spi: uniphier: Fix FIFO threshold regulator: bd70528: Remove .set_ramp_delay for bd70528_ldo_ops regulator: axp20x: Fix axp20x_set_ramp_delay watchdog: tqmx86_wdt: Fix build error net, sysctl: Fix compiler warning when only cBPF is present netfilter: nf_queue: enqueue skbs with NULL dst platform/x86: pmc_atom: Add Siemens CONNECT X300 to critclk_systems DMI table xfs: don't check for AG deadlock for realtime files in bunmapi firmware: arm_scmi: Avoid double free in error flow cifs: Fix potential softlockups while refreshing DFS cache of: overlay: add_changeset_property() memory leak iommu/vt-d: Remove incorrect PSI capability check perf callchain: Fix segfault in thread__resolve_callchain_sample() ACPI: sysfs: Change ACPI_MASKABLE_GPE_MAX to 0x100 kernel/module.c: wakeup processes in module_wq on module unload net/sched: annotate lockless accesses to qdisc->empty HID: i2c-hid: Reset ALPS touchpads on resume powerpc: Chunk calls to flush_dcache_range in arch_*_memory nfsd4: fix up replay_matches_cache() arm64: dts: qcom: msm8998-clamshell: Remove retention idle state sunrpc: fix crash when cache_head become valid before update PM / devfreq: Check NULL governor in available_governors_show drm/msm: include linux/sched/task.h spi: spi-fsl-dspi: Fix 16-bit word order in 32-bit XSPI mode ftrace: Avoid potential division by zero in function profiler arm64: Revert support for execute-only user mappings exit: panic before exit_mm() on global init exit scsi: lpfc: Fix rpi release when deleting vport ALSA: firewire-motu: Correct a typo in the clock proc string ALSA: pcm: Yet another missing check of non-cached buffer type ALSA: cs4236: fix error return comparison of an unsigned integer gen_initramfs_list.sh: fix 'bad variable name' error dmaengine: virt-dma: Fix access after free in vchan_complete() apparmor: fix aa_xattrs_matc
[Kernel-packages] [Bug 1863588] Re: Focal update: v5.4.19 upstream stable release
** Package changed: linux-5.4 (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1863588
Title:
Focal update: v5.4.19 upstream stable release
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
Confirmed
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.19 upstream stable release
from git://git.kernel.org/
Linux 5.4.19
powerpc/kuap: Fix set direction in allow/prevent_user_access()
regulator fix for "regulator: core: Add regulator_is_equal() helper"
rxrpc: Fix service call disconnection
perf/core: Fix mlock accounting in perf_mmap()
clocksource: Prevent double add_timer_on() for watchdog_timer
x86/apic/msi: Plug non-maskable MSI affinity race
cifs: fail i/o on soft mounts if sessionsetup errors out
KVM: Play nice with read-only memslots when querying host page size
KVM: Use vcpu-specific gva->hva translation when querying host page size
KVM: nVMX: vmread should not set rflags to specify success in case of #PF
KVM: x86: fix overlap between SPTE_MMIO_MASK and generation
KVM: x86: Use gpa_t for cr2/gpa to fix TDP support on 32-bit KVM
KVM: x86: use CPUID to locate host page table reserved bits
KVM: x86/mmu: Apply max PA check for MMIO sptes to 32-bit KVM
drm/dp_mst: Remove VCPI while disabling topology mgr
btrfs: free block groups after free'ing fs trees
btrfs: use bool argument in free_root_pointers()
x86/timer: Don't skip PIT setup when APIC is disabled or in legacy mode
mfd: bd70528: Fix hour register mask
mfd: rn5t618: Mark ADC control register volatile
mfd: da9062: Fix watchdog compatible string
ASoC: Intel: skl_hda_dsp_common: Fix global-out-of-bounds bug
net/mlx5: Deprecate usage of generic TLS HW capability bit
net/mlx5: Fix deadlock in fs_core
drop_monitor: Do not cancel uninitialized work item
qed: Fix timestamping issue for L2 unicast ptp packets.
ipv6/addrconf: fix potential NULL deref in inet6_set_link_af()
taprio: Fix dropping packets when using taprio + ETF offloading
taprio: Use taprio_reset_tc() to reset Traffic Classes configuration
taprio: Add missing policy validation for flags
taprio: Fix still allowing changing the flags during runtime
taprio: Fix enabling offload with wrong number of traffic classes
net: macb: Limit maximum GEM TX length in TSO
net: macb: Remove unnecessary alignment check for TSO
net/mlx5: IPsec, fix memory leak at mlx5_fpga_ipsec_delete_sa_ctx
net/mlx5: IPsec, Fix esp modify function attribute
net: systemport: Avoid RBUF stuck in Wake-on-LAN mode
net: stmmac: fix a possible endless loop
net_sched: fix a resource leak in tcindex_set_parms()
net: mvneta: move rx_dropped and rx_errors in per-cpu stats
net: dsa: microchip: enable module autoprobe
net: dsa: bcm_sf2: Only 7278 supports 2Gb/sec IMP port
net: dsa: b53: Always use dev->vlan_enabled in b53_configure_vlan()
dpaa_eth: support all modes with rate adapting PHYs
devlink: report 0 after hitting end in region read
bonding/alb: properly access headers in bond_alb_xmit()
ASoC: sgtl5000: Fix VDDA and VDDIO comparison
regulator: core: Add regulator_is_equal() helper
ubifs: Fix memory leak from c->sup_node
ubi: Fix an error pointer dereference in error handling code
ubi: fastmap: Fix inverted logic in seen selfcheck
virtio_balloon: Fix memory leaks on errors in virtballoon_probe()
virtio-balloon: Fix memory leak when unloading while hinting is in progress
nfsd: Return the correct number of bytes written to the file
nfsd: fix jiffies/time_t mixup in LRU list
nfsd: fix delay timer on 32-bit architectures
IB/core: Fix ODP get user pages flow
IB/mlx5: Fix outstanding_pi index for GSI qps
net: tulip: Adjust indentation in {dmfe, uli526x}_init_module
net: smc911x: Adjust indentation in smc911x_phy_configure
ppp: Adjust indentation into ppp_async_input
NFC: pn544: Adjust indentation in pn544_hci_check_presence
drm: msm: mdp4: Adjust indentation in mdp4_dsi_encoder_enable
powerpc/44x: Adjust indentation in ibm4xx_denali_fixup_memsize
ext2: Adjust indentation in ext2_fill_super
phy: qualcomm: Adjust indentation in read_poll_timeout
mtd: spi-nor: Split mt25qu512a (n25q512a) entry into two
scsi: ufs: Recheck bkops level if bkops is disabled
scsi: qla4xxx: Adjust indentation in qla4xxx_mem_free
scsi: csiostor: Adjust indentation in csio_device_reset
scsi:
[Kernel-packages] [Bug 1865149] Re: The speakers of the notebook do not sound, but the headphones work
** Package changed: linux-5.4 (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865149 Title: The speakers of the notebook do not sound, but the headphones work Status in linux package in Ubuntu: New Bug description: Update ubuntu and BIOS. After this, the notebook's speakers do not work, but if I connect the headphones, they sound. == Solution == 1. Start with usb xubuntu 19.10 2. Open mp3 3. Then this mp3 is heard through the headphones and speakers of the notebook 4. Reboot 5. Start with ubuntu 20.04(development) on hard drive 6. Try listening to an mp3 again 7. Now everything works correctly == Others == Now that I remember, this is not the first time that happens to me. It is when the BIOS is updated, then the problem of no sound appears in the speakers of the notebook. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1815 F pulseaudio /dev/snd/pcmC0D0p: caravena 1815 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:06:14 2020 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (452 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-14-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 SourcePackage: linux-5.4 UpgradeStatus: Upgraded to focal on 2018-12-02 (452 days ago) dmi.bios.date: 11/18/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.35:bd11/18/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865149/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863589] Re: Focal update: v5.4.20 upstream stable release
** Package changed: linux-5.4 (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863589 Title: Focal update: v5.4.20 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed 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.20 upstream stable release from git://git.kernel.org/ Linux 5.4.20 selinux: fall back to ref-walk if audit is required libertas: make lbs_ibss_join_existing() return error code on rates overflow libertas: don't exit from lbs_ibss_join_existing() with RCU read lock held mwifiex: Fix possible buffer overflows in mwifiex_cmd_append_vsie_tlv() mwifiex: Fix possible buffer overflows in mwifiex_ret_wmm_get_status() dmaengine: axi-dmac: add a check for devm_regmap_init_mmio clk: meson: g12a: fix missing uart2 in regmap table mfd: max77650: Select REGMAP_IRQ in Kconfig regmap: fix writes to non incrementing registers pinctrl: sh-pfc: r8a7778: Fix duplicate SDSELF_B and SD1_CLK_B pinctrl: sh-pfc: r8a77965: Fix DU_DOTCLKIN3 drive/bias control selinux: fix regression introduced by move_mount(2) syscall selinux: revert "stop passing MAY_NOT_BLOCK to the AVC upon follow_link" bcache: avoid unnecessary btree nodes flushing in btree_flush_write() dt-bindings: iio: adc: ad7606: Fix wrong maxItems value media: i2c: adv748x: Fix unsafe macros drivers: watchdog: stm32_iwdg: set WDOG_HW_RUNNING at probe crypto: caam/qi2 - fix typo in algorithm's driver name crypto: atmel-sha - fix error handling when setting hmac key crypto: artpec6 - return correct error code for failed setkey() crypto: testmgr - don't try to decrypt uninitialized buffers mtd: sharpslpart: Fix unsigned comparison to zero mtd: onenand_base: Adjust indentation in onenand_read_ops_nolock arm64: nofpsmid: Handle TIF_FOREIGN_FPSTATE flag cleanly KVM: arm64: Treat emulated TVAL TimerValue as a signed 32-bit integer KVM: arm64: pmu: Fix chained SW_INCR counters KVM: arm64: pmu: Don't increment SW_INCR if PMCR.E is unset KVM: arm: Make inject_abt32() inject an external abort instead KVM: arm: Fix DFSR setting for non-LPAE aarch32 guests KVM: arm/arm64: Fix young bit from mmu notifier arm64: ptrace: nofpsimd: Fail FP/SIMD regset operations arm64: cpufeature: Set the FP/SIMD compat HWCAP bits properly arm64: cpufeature: Fix the type of no FP/SIMD capability sched/uclamp: Fix a bug in propagating uclamp value in new cgroups ARM: 8949/1: mm: mark free_memmap as __init KVM: arm/arm64: vgic-its: Fix restoration of unmapped collections ARM: at91: pm: use of_device_id array to find the proper shdwc node ARM: at91: pm: use SAM9X60 PMC's compatible iommu/arm-smmu-v3: Populate VMID field for CMDQ_OP_TLBI_NH_VA powerpc/pseries: Allow not having ibm, hypertas-functions::hcall-multi-tce for DDW powerpc/pseries/vio: Fix iommu_table use-after-free refcount warning powerpc/papr_scm: Fix leaking 'bus_desc.provider_name' in some paths powerpc/ptdump: Only enable PPC_CHECK_WX with STRICT_KERNEL_RWX powerpc/ptdump: Fix W+X verification call in mark_rodata_ro() Revert "powerpc/pseries/iommu: Don't use dma_iommu_ops on secure guests" soc: qcom: rpmhpd: Set 'active_only' for active only power domains tools/power/acpi: fix compilation error ARM: dts: at91: sama5d3: define clock rate range for tcb1 ARM: dts: at91: sama5d3: fix maximum peripheral clock rates ARM: dts: meson8b: use the actual frequency for the GPU's 364MHz OPP ARM: dts: meson8: use the actual frequency for the GPU's 182.1MHz OPP arm64: dts: marvell: clearfog-gt-8k: fix switch cpu port node arm64: dts: renesas: r8a77990: ebisu: Remove clkout-lr-synchronous from sound ARM: dts: am43xx: add support for clkout1 clock ARM: dts: at91: Reenable UART TX pull-ups arm64: dts: uDPU: fix broken ethernet arm64: dts: qcom: msm8998: Fix tcsr syscon size platform/x86: intel_mid_powerbtn: Take a copy of ddata ARC: [plat-axs10x]: Add missing multicast filter number to GMAC node watchdog: qcom: Use platform_get_irq_optional() for bark irq rtc: cmos: Stop using shared IRQ rtc: hym8563: Return -EINVAL if the time is known to be invalid x86/boot: Handle malformed SRAT tables during early ACPI parsing NFSv4.0: nfs4_do_fsinfo() should not do implicit lease renewals NFSv4: try lease recovery on NFS4ERR_EXPIRED NFSv4: pnfs_roc() mu
[Kernel-packages] [Bug 1864930] Re: brightness setting and sleep/suspend (echo mem > /sys/power/state) , s2ram and s2disk fail for 5.4.0 and s2disk fail for 5.4.22
** Package changed: linux-5.4 (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864930 Title: brightness setting and sleep/suspend (echo mem > /sys/power/state) , s2ram and s2disk fail for 5.4.0 and s2disk fail for 5.4.22 Status in linux package in Ubuntu: Confirmed Bug description: 1) After resuming from suspend (uswsusp/s2ram) and/or after resuming from "echo mem > /sys/power/state" there is a black screen on laptop after resume with 5.4.0-14-generic kernel only. Kernel seems to be working as CTRL+ALT+F2 and CTRL+ALT+DEL restarts laptop. A) 3 Different combinations of this distro with other kernels work well: kubunut20.04 + linux-image-5.3.0-40-generic (copied from kubuntu 19.10 from /lib/modules/5.3.0-40-generic and /boot/vmlinuz-5.3.0-40-generic) Installed from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6-rc3/ kubuntu20.04 + linux-image-unsigned-5.5.6-050506-generic is working. kubuntu20.04 + linux-image-unsigned-5.6.0-050600rc3-generic is working. B) This kernel 5.4.0-14-generic when copied manually into kubuntu 19.10 behaves the same as in 20.04 (NOT WORKING for suspend to ram) 2) setting brightness with keys on laptop keyboard does not work for this kernel 5.4.0-14-generic only Neither using this command line method marian@kubuntu2004:~/Downloads$ cat /sys/class/backlight/intel_backlight/max_brightness 255 marian@kubuntu2004:~/Downloads$ cat /sys/class/backlight/intel_backlight/max_brightness 255 marian@kubuntu2004:~/Downloads$ cat /sys/class/backlight/intel_backlight/actual_brightness 255 marian@kubuntu2004:~/Downloads$ cat /sys/class/backlight/intel_backlight/brightness 242 marian@kubuntu2004:~/Downloads$ echo 200 | sudo tee /sys/class/backlight/intel_backlight/brightness 200 marian@kubuntu2004:~/Downloads$ cat /sys/class/backlight/intel_backlight/brightness Again kernel 5.3 copied into kubuntu20.04 got working brigthness keys. However this works for all tested kernels above (including 5.4.0-14-generic) xrandr --output eDP-1 --brightness 0.8 3) after uswsusp/hibernate (s2disk) and "echo disk > /sys/power/state" do not seem to resume/thaw for those kernels: linux-image-5.4.0-14-generic, linux-image-unsigned-5.5.6-050506-generic , linux-image-unsigned-5.6.0-050600rc3-generic, on the other hand kernel linux-image-5.3.0-40-generic manually copied from kubuntu 19.10 into kubuntu 20.04 seems to be working fine when thawing/resuming from hibernation. Again I tested different combination of kernels and distros for this issue. This kernel (5.4.0-14-generic) also does not work for hibernate/resume even when copied from kubuntu20.04 into kubuntu19.10 4) Starting kubuntu without installation from daily build from 25th Feb 2020 shows the same problem for brightness setting and for black screen after resuming from sleep. http://cdimage.ubuntu.com/kubuntu/daily-live/current/ Note I always recreated imagerd in target place when copied kernels manually: update-initramfs -u -k 5.3.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marian 1214 F pulseaudio CurrentDesktop: KDE Date: Wed Feb 26 22:20:29 2020 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 05c8:0815 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision FHD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=/dev/mapper/sysvg-ub2004deboot ro resume=/dev/nvme0n1p8 quiet splash resume=/dev/nvme0n1p8 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 SourcePackage: linux-5.4 UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 01/07/2019 dmi.bios.vendor: AMI dmi.bios.version: F.24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.24:bd01/07/2019:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:r
[Kernel-packages] [Bug 1865182] Re: lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'
** Package changed: linux-5.4 (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865182 Title: lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' Status in linux package in Ubuntu: Confirmed Bug description: This error did not take place on my laptop (where I ran apport, for convenience), but on a server being deployed to Focal with MAAS. The initial deployment boot worked fine, and that was lucky as it meant I could ssh in and tail /var/log/syslog while it went through the upgrades and cloud-init steps. But after this it reboots without network configuration. I've attached the logs mentioned above. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nick 1445 F pulseaudio /dev/snd/controlC0: nick 1445 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 16:17:47 2020 Dependencies: InstallationDate: Installed on 2020-02-24 (4 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20ALCT01WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-14-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 SourcePackage: linux-5.4 UpgradeStatus: Upgraded to focal on 2020-02-24 (4 days ago) dmi.bios.date: 12/15/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GIET84WW (2.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ALCT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGIET84WW(2.34):bd12/15/2015:svnLENOVO:pn20ALCT01WW:pvrThinkPadX240:rvnLENOVO:rn20ALCT01WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X240 dmi.product.name: 20ALCT01WW dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240 dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866744] Re: package linux-5.4-tools-common (not installed) failed to install/upgrade: tentata sovrascrittura di "/usr/bin/acpidbg" presente anche nel pacchetto linux-tools-comm
** Package changed: linux-5.4 (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866744 Title: package linux-5.4-tools-common (not installed) failed to install/upgrade: tentata sovrascrittura di "/usr/bin/acpidbg" presente anche nel pacchetto linux-tools-common 5.4.0-18.22 Status in linux package in Ubuntu: New Bug description: non ci sono dettagli. Segna errore di sistema ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-5.4-tools-common (not installed) ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: valerio2636 F pulseaudio Date: Tue Mar 10 09:53:08 2020 ErrorMessage: tentata sovrascrittura di "/usr/bin/acpidbg" presente anche nel pacchetto linux-tools-common 5.4.0-18.22 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200308) IwConfig: enp1s0no wireless extensions. enp3s2no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=ada6a835-d362-43fd-b1e0-0fd23cf528b3 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: linux-5.4 Title: package linux-5.4-tools-common (not installed) failed to install/upgrade: tentata sovrascrittura di "/usr/bin/acpidbg" presente anche nel pacchetto linux-tools-common 5.4.0-18.22 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: G41M-VS3. dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd05/18/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnG41M-VS3.:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866172] Re: xubuntu 20.04 'live' qa-test; suspend, resume but system froze on waking
** Package changed: linux-5.4 (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866172 Title: xubuntu 20.04 'live' qa-test; suspend, resume but system froze on waking Status in linux package in Ubuntu: New Bug description: Xubuntu daily test (20.04) on dell vostro 430 (i7-870, 8gb, nvidia geforce gt 6600 gt) test went well, then I suspended system, waited, on resume (keystroke) system appeared to stop with mucked-up but mostly-recognizable display (https://photos.app.goo.gl/2kSU5SubdbkdpFUcA) I was unable to use any keyboard input to switch to terminal, or gain any clues (sorry keyboard didn't have sysrq key to see if kernel was up). I rebooted the system which is when `ubuntu-bug linux` was ran. After this bug was submitted I suspended system, waited & it resumed correctly. I suspended it again, waited & it resumed normally; so the issue doesn't occur all the time. Because CTRL+ALT+T wasn't working (different issue; https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1827459), nor menu items having icons etc, I `xfsettingsd --replace` to fix that issue & suspended again.. This time the system didn't resume reliably. This time however it was not as I'm describing above, as the screen was correctly drawn. The mouse-pointer was visible but static, then appeared to move (following my movements) before disappearing, redrawn but static again .. IF the system was 'up', it'd become super slow; and I eventually turned box off. I'll retest on requests (too tried now) photo of screen on resume : https://photos.app.goo.gl/2kSU5SubdbkdpFUcA ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4057 F pulseaudio CasperVersion: 1.441 CurrentDesktop: XFCE Date: Thu Mar 5 10:35:57 2020 IwConfig: enp2s0no wireless extensions. lono wireless extensions. LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200305) MachineType: Dell Inc. Vostro 430 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 RfKill: SourcePackage: linux-5.4 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 054KM3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd01/13/2011:svnDellInc.:pnVostro430:pvr00:rvnDellInc.:rn054KM3:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: 0 dmi.product.name: Vostro 430 dmi.product.sku: 0 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866172/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876875] Re: Improve download-signed script to support current & grub2
Did source copy of grub2-signed 1.142.1 into private PPA and it successfully rebuilt signed packages on amd64 and arm64 against a copy of grub2 from the matching private PPA. If sru team wants to look at the build-log, i can private build-logs privately. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1876875 Title: Improve download-signed script to support current & grub2 Status in grub2-signed package in Ubuntu: Fix Released Status in linux-signed package in Ubuntu: Fix Committed Status in s390-tools-signed package in Ubuntu: Won't Fix Status in grub2-signed source package in Focal: Fix Committed Bug description: [Impact] * Improve and generalise download-signed script to allow using it with any signed binaries we care about * Add support to download simply the most current version * Add support to download /uefi/ signed binaries * Clean up arg parsing, add help, drop unused statements & imports. [Test Case] * Test downloading signed kernel works with public & private archives * Test that rebuilt signed .debs are the same [Regression Potential] * This is a built time script, as long the binaries are downloaded & packaged up the same, there is no end-user facing impact. [Other Info] * With these changes, download-signed script can be used by s390-tools-signed & grub2-signed, as well as all the kernels. * This is needed to support resigning with different keys for different ubuntu products. For example, UC20 uses the same grub binaries, but wants an additional trustpath to UC20 CA for grade:secured core images. At the moment creating such a signature is only possible via a round-trip in a PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1876875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865346] Re: Changing backlight no longer works with Linux 5.4
** Package changed: linux-5.4 (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865346 Title: Changing backlight no longer works with Linux 5.4 Status in linux package in Ubuntu: Confirmed Bug description: As of upgrading to Ubuntu 20.04 (and with it Linux 5.4), adjusting brightness no longer works. `/sys/class/backlight/intel_backlight/` exists, but writing to `/sys/class/backlight/intel_backlight/brightness` doesn't have any effect. If I boot into Linux 5.3 instead, changing brightness works again. Complete dmesg output is attached, but I don't see anything interesting in it. My hardware is a Dell Inc. XPS 15 9575, with an Intel Core i7-8705G. More info: `lsb_release -rd`: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 `apt-cache policy linux-generic`: linux-generic: Installed: 5.4.0.14.17 Candidate: 5.4.0.14.17 Version table: *** 5.4.0.14.17 500 500 http://no.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865346/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866749] Re: package linux-image-5.4.0-14-generic 5.4.0-14.17 failed to install/upgrade: il sottoprocesso installato pacchetto linux-image-5.4.0-14-generic script pre-removal ha
** Package changed: linux-5.4 (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866749 Title: package linux-image-5.4.0-14-generic 5.4.0-14.17 failed to install/upgrade: il sottoprocesso installato pacchetto linux- image-5.4.0-14-generic script pre-removal ha restituito lo stato di errore 1 Status in linux package in Ubuntu: New Bug description: in realta e il 5.4.0-18 che crea probemi e non va prorio ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: valerio3524 F pulseaudio Date: Tue Mar 10 11:53:46 2020 ErrorMessage: il sottoprocesso installato pacchetto linux-image-5.4.0-14-generic script pre-removal ha restituito lo stato di errore 1 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200308) IwConfig: enp3s2no wireless extensions. enp1s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=ada6a835-d362-43fd-b1e0-0fd23cf528b3 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: linux-5.4 Title: package linux-image-5.4.0-14-generic 5.4.0-14.17 failed to install/upgrade: il sottoprocesso installato pacchetto linux-image-5.4.0-14-generic script pre-removal ha restituito lo stato di errore 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: G41M-VS3. dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd05/18/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnG41M-VS3.:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882273] Status changed to Confirmed
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/1882273 Title: ALPS Touchpad' incorrectly detected as PS/2 mouse in 'Lenovo IdeaPad S145' after installing Ubuntu 20 Status in linux package in Ubuntu: Confirmed Bug description: 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=0003 Vendor=04b3 Product=310b Version=0100 N: Name="HID 04b3:310b" P: Phys=usb-:00:14.0-2/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:04B3:310B.0001/input/input4 U: Uniq= H: Handlers=mouse0 event4 B: PROP=0 B: EV=17 B: KEY=7 0 0 0 0 B: REL=903 B: MSC=10 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/input5 U: Uniq= H: Handlers=rfkill kbd event5 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 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 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37
[Kernel-packages] [Bug 1882159] Re: 10s delay after grub, before kernel messages start
> Please clarify the origin of the delay first. I've done that, why is this still 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/1882159 Title: 10s delay after grub, before kernel messages start Status in linux package in Ubuntu: Incomplete Bug description: - fresh install of 20.04 X64 in a vmware vm - "quiet splash" kernel args have been removed - the kernel messages should start immediately after grub menu selection - but there's a 10s delay grub config ``` GRUB_DEFAULT=0 GRUB_TIMEOUT_STYLE=menu GRUB_TIMEOUT=3 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` #GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" GRUB_CMDLINE_LINUX="" ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: me 912 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 4 20:34:38 2020 InstallationDate: Installed on 2020-06-03 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. ens32 no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=606fed4f-11b6-4349-803e-69c555177718 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882273] [NEW] ALPS Touchpad' incorrectly detected as PS/2 mouse in 'Lenovo IdeaPad S145' after installing Ubuntu 20
Public bug reported: 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=0003 Vendor=04b3 Product=310b Version=0100 N: Name="HID 04b3:310b" P: Phys=usb-:00:14.0-2/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:04B3:310B.0001/input/input4 U: Uniq= H: Handlers=mouse0 event4 B: PROP=0 B: EV=17 B: KEY=7 0 0 0 0 B: REL=903 B: MSC=10 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/input5 U: Uniq= H: Handlers=rfkill kbd event5 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 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 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jordi 1546 F pulseaudio /dev/snd/pcmC0D0c: jordi 1546 F...m pulseaudio /dev/snd/pcmC0D0p: jordi 1546 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 5 19:08:18 2020 InstallationDate: Installed on 2020-04-23 (43 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enx503eaa9f9b96 no wireless extensions. MachineType: LENOVO 81W8 ProcEnviron: TERM=xterm-256color PATH=(cu
[Kernel-packages] [Bug 1874194] Re: Ubuntu 20.04 HDMI connected, no boot
I can confirm that booting without "quiet splash" in the grub config eliminates the problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882153] Re: linux-modules-kvm does not include net/netfilter/ipvs/*.ko modules
Apport info is irrelevant, it's a packaging issue : D ** 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/1882153 Title: linux-modules-kvm does not include net/netfilter/ipvs/*.ko modules Status in cloud-images: Invalid Status in linux package in Ubuntu: Confirmed Bug description: How to reproduce: 1. Boot from an Ubuntu Focal kvm cloud image # uname -r 5.4.0-1011-kvm # apt-get update # apt-get install linux-modules-5.4.0-1011-gcp [...] # dpkg -l linux-modules\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--== ii linux-modules-5.4.0-1011-gcp 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP ii linux-modules-5.4.0-1011-kvm 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP # ls -1 /lib/modules/5.4.0-1011-*/kernel/net/netfilter/ipvs/*ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_dh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_fo.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ftp.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblcr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_mh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_nq.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ovf.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_pe_sip.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_rr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sed.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wlc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wrr.ko There's no ipvs in linux-modules-5.4.0-1011-kvm version. Please include them. Tested on Ubuntu Focal from here: https://cloud-images.ubuntu.com/minimal/releases/focal/ https://cloud-images.ubuntu.com/focal/ https://cloud-images.ubuntu.com/releases/focal/ --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: RDO OpenStack Compute Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1011-kvm root=PARTUUID=815e35f9-92e6-44ee-9ea5-7f5a68f9c5d6 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: User Name 5.4.0-1011.11-kvm 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-1011-kvm N/A linux-backports-modules-5.4.0-1011-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1011-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.11.0-2.el7 dmi.chassis.type: 1 dmi.chassis.vendor: Red Hat dmi.chassis.version: RHEL 7.6.0 PC (i440FX + PIIX, 1996) dmi.modalias: dmi:bvnSeaBIOS:bvr1.11.0-2.el7:bd04/01/2014:svnRDO:pnOpenStackCompute:pvr17.0.5-1.el7:cvnRedHat:ct1:cvrRHEL7.6.0PC(i440FX+PIIX,1996): dmi.product.family: Virtual Machine dmi.product.name: OpenStack Compute dmi.product.version: 17.0.5-1.el7
[Kernel-packages] [Bug 1882153] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1882153/+attachment/5380723/+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/1882153 Title: linux-modules-kvm does not include net/netfilter/ipvs/*.ko modules Status in cloud-images: Invalid Status in linux package in Ubuntu: Confirmed Bug description: How to reproduce: 1. Boot from an Ubuntu Focal kvm cloud image # uname -r 5.4.0-1011-kvm # apt-get update # apt-get install linux-modules-5.4.0-1011-gcp [...] # dpkg -l linux-modules\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--== ii linux-modules-5.4.0-1011-gcp 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP ii linux-modules-5.4.0-1011-kvm 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP # ls -1 /lib/modules/5.4.0-1011-*/kernel/net/netfilter/ipvs/*ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_dh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_fo.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ftp.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblcr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_mh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_nq.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ovf.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_pe_sip.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_rr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sed.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wlc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wrr.ko There's no ipvs in linux-modules-5.4.0-1011-kvm version. Please include them. Tested on Ubuntu Focal from here: https://cloud-images.ubuntu.com/minimal/releases/focal/ https://cloud-images.ubuntu.com/focal/ https://cloud-images.ubuntu.com/releases/focal/ --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: RDO OpenStack Compute Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1011-kvm root=PARTUUID=815e35f9-92e6-44ee-9ea5-7f5a68f9c5d6 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: User Name 5.4.0-1011.11-kvm 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-1011-kvm N/A linux-backports-modules-5.4.0-1011-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1011-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.11.0-2.el7 dmi.chassis.type: 1 dmi.chassis.vendor: Red Hat dmi.chassis.version: RHEL 7.6.0 PC (i440FX + PIIX, 1996) dmi.modalias: dmi:bvnSeaBIOS:bvr1.11.0-2.el7:bd04/01/2014:svnRDO:pnOpenStackCompute:pvr17.0.5-1.el7:cvnRedHat:ct1:cvrRHEL7.6.0PC(i440FX+PIIX,1996): dmi.product.family: Virtual Machine dmi.product.name: OpenStack Compute dmi.product.
[Kernel-packages] [Bug 1882153] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1882153/+attachment/5380727/+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/1882153 Title: linux-modules-kvm does not include net/netfilter/ipvs/*.ko modules Status in cloud-images: Invalid Status in linux package in Ubuntu: Confirmed Bug description: How to reproduce: 1. Boot from an Ubuntu Focal kvm cloud image # uname -r 5.4.0-1011-kvm # apt-get update # apt-get install linux-modules-5.4.0-1011-gcp [...] # dpkg -l linux-modules\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--== ii linux-modules-5.4.0-1011-gcp 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP ii linux-modules-5.4.0-1011-kvm 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP # ls -1 /lib/modules/5.4.0-1011-*/kernel/net/netfilter/ipvs/*ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_dh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_fo.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ftp.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblcr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_mh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_nq.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ovf.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_pe_sip.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_rr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sed.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wlc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wrr.ko There's no ipvs in linux-modules-5.4.0-1011-kvm version. Please include them. Tested on Ubuntu Focal from here: https://cloud-images.ubuntu.com/minimal/releases/focal/ https://cloud-images.ubuntu.com/focal/ https://cloud-images.ubuntu.com/releases/focal/ --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: RDO OpenStack Compute Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1011-kvm root=PARTUUID=815e35f9-92e6-44ee-9ea5-7f5a68f9c5d6 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: User Name 5.4.0-1011.11-kvm 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-1011-kvm N/A linux-backports-modules-5.4.0-1011-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1011-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.11.0-2.el7 dmi.chassis.type: 1 dmi.chassis.vendor: Red Hat dmi.chassis.version: RHEL 7.6.0 PC (i440FX + PIIX, 1996) dmi.modalias: dmi:bvnSeaBIOS:bvr1.11.0-2.el7:bd04/01/2014:svnRDO:pnOpenStackCompute:pvr17.0.5-1.el7:cvnRedHat:ct1:cvrRHEL7.6.0PC(i440FX+PIIX,1996): dmi.product.family: Virtual Machine dmi.product.name: OpenStack Compute
[Kernel-packages] [Bug 1882153] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1882153/+attachment/5380729/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882153 Title: linux-modules-kvm does not include net/netfilter/ipvs/*.ko modules Status in cloud-images: Invalid Status in linux package in Ubuntu: Confirmed Bug description: How to reproduce: 1. Boot from an Ubuntu Focal kvm cloud image # uname -r 5.4.0-1011-kvm # apt-get update # apt-get install linux-modules-5.4.0-1011-gcp [...] # dpkg -l linux-modules\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--== ii linux-modules-5.4.0-1011-gcp 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP ii linux-modules-5.4.0-1011-kvm 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP # ls -1 /lib/modules/5.4.0-1011-*/kernel/net/netfilter/ipvs/*ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_dh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_fo.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ftp.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblcr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_mh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_nq.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ovf.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_pe_sip.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_rr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sed.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wlc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wrr.ko There's no ipvs in linux-modules-5.4.0-1011-kvm version. Please include them. Tested on Ubuntu Focal from here: https://cloud-images.ubuntu.com/minimal/releases/focal/ https://cloud-images.ubuntu.com/focal/ https://cloud-images.ubuntu.com/releases/focal/ --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: RDO OpenStack Compute Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1011-kvm root=PARTUUID=815e35f9-92e6-44ee-9ea5-7f5a68f9c5d6 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: User Name 5.4.0-1011.11-kvm 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-1011-kvm N/A linux-backports-modules-5.4.0-1011-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1011-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.11.0-2.el7 dmi.chassis.type: 1 dmi.chassis.vendor: Red Hat dmi.chassis.version: RHEL 7.6.0 PC (i440FX + PIIX, 1996) dmi.modalias: dmi:bvnSeaBIOS:bvr1.11.0-2.el7:bd04/01/2014:svnRDO:pnOpenStackCompute:pvr17.0.5-1.el7:cvnRedHat:ct1:cvrRHEL7.6.0PC(i440FX+PIIX,1996): dmi.product.family: Virtual Machine dmi.product.name: OpenStack Compute dmi.product.ve
[Kernel-packages] [Bug 1882153] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1882153/+attachment/5380730/+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/1882153 Title: linux-modules-kvm does not include net/netfilter/ipvs/*.ko modules Status in cloud-images: Invalid Status in linux package in Ubuntu: Confirmed Bug description: How to reproduce: 1. Boot from an Ubuntu Focal kvm cloud image # uname -r 5.4.0-1011-kvm # apt-get update # apt-get install linux-modules-5.4.0-1011-gcp [...] # dpkg -l linux-modules\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--== ii linux-modules-5.4.0-1011-gcp 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP ii linux-modules-5.4.0-1011-kvm 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP # ls -1 /lib/modules/5.4.0-1011-*/kernel/net/netfilter/ipvs/*ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_dh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_fo.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ftp.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblcr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_mh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_nq.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ovf.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_pe_sip.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_rr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sed.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wlc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wrr.ko There's no ipvs in linux-modules-5.4.0-1011-kvm version. Please include them. Tested on Ubuntu Focal from here: https://cloud-images.ubuntu.com/minimal/releases/focal/ https://cloud-images.ubuntu.com/focal/ https://cloud-images.ubuntu.com/releases/focal/ --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: RDO OpenStack Compute Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1011-kvm root=PARTUUID=815e35f9-92e6-44ee-9ea5-7f5a68f9c5d6 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: User Name 5.4.0-1011.11-kvm 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-1011-kvm N/A linux-backports-modules-5.4.0-1011-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1011-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.11.0-2.el7 dmi.chassis.type: 1 dmi.chassis.vendor: Red Hat dmi.chassis.version: RHEL 7.6.0 PC (i440FX + PIIX, 1996) dmi.modalias: dmi:bvnSeaBIOS:bvr1.11.0-2.el7:bd04/01/2014:svnRDO:pnOpenStackCompute:pvr17.0.5-1.el7:cvnRedHat:ct1:cvrRHEL7.6.0PC(i440FX+PIIX,1996): dmi.product.family: Virtual Machine dmi.product.name: OpenStack Compute dmi.product.version: 17.0
[Kernel-packages] [Bug 1882153] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1882153/+attachment/5380725/+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/1882153 Title: linux-modules-kvm does not include net/netfilter/ipvs/*.ko modules Status in cloud-images: Invalid Status in linux package in Ubuntu: Confirmed Bug description: How to reproduce: 1. Boot from an Ubuntu Focal kvm cloud image # uname -r 5.4.0-1011-kvm # apt-get update # apt-get install linux-modules-5.4.0-1011-gcp [...] # dpkg -l linux-modules\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--== ii linux-modules-5.4.0-1011-gcp 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP ii linux-modules-5.4.0-1011-kvm 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP # ls -1 /lib/modules/5.4.0-1011-*/kernel/net/netfilter/ipvs/*ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_dh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_fo.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ftp.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblcr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_mh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_nq.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ovf.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_pe_sip.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_rr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sed.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wlc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wrr.ko There's no ipvs in linux-modules-5.4.0-1011-kvm version. Please include them. Tested on Ubuntu Focal from here: https://cloud-images.ubuntu.com/minimal/releases/focal/ https://cloud-images.ubuntu.com/focal/ https://cloud-images.ubuntu.com/releases/focal/ --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: RDO OpenStack Compute Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1011-kvm root=PARTUUID=815e35f9-92e6-44ee-9ea5-7f5a68f9c5d6 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: User Name 5.4.0-1011.11-kvm 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-1011-kvm N/A linux-backports-modules-5.4.0-1011-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1011-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.11.0-2.el7 dmi.chassis.type: 1 dmi.chassis.vendor: Red Hat dmi.chassis.version: RHEL 7.6.0 PC (i440FX + PIIX, 1996) dmi.modalias: dmi:bvnSeaBIOS:bvr1.11.0-2.el7:bd04/01/2014:svnRDO:pnOpenStackCompute:pvr17.0.5-1.el7:cvnRedHat:ct1:cvrRHEL7.6.0PC(i440FX+PIIX,1996): dmi.product.family: Virtual Machine dmi.product.name: OpenStack Compute dmi.product.version:
[Kernel-packages] [Bug 1882153] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1882153/+attachment/5380728/+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/1882153 Title: linux-modules-kvm does not include net/netfilter/ipvs/*.ko modules Status in cloud-images: Invalid Status in linux package in Ubuntu: Confirmed Bug description: How to reproduce: 1. Boot from an Ubuntu Focal kvm cloud image # uname -r 5.4.0-1011-kvm # apt-get update # apt-get install linux-modules-5.4.0-1011-gcp [...] # dpkg -l linux-modules\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--== ii linux-modules-5.4.0-1011-gcp 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP ii linux-modules-5.4.0-1011-kvm 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP # ls -1 /lib/modules/5.4.0-1011-*/kernel/net/netfilter/ipvs/*ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_dh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_fo.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ftp.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblcr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_mh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_nq.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ovf.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_pe_sip.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_rr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sed.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wlc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wrr.ko There's no ipvs in linux-modules-5.4.0-1011-kvm version. Please include them. Tested on Ubuntu Focal from here: https://cloud-images.ubuntu.com/minimal/releases/focal/ https://cloud-images.ubuntu.com/focal/ https://cloud-images.ubuntu.com/releases/focal/ --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: RDO OpenStack Compute Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1011-kvm root=PARTUUID=815e35f9-92e6-44ee-9ea5-7f5a68f9c5d6 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: User Name 5.4.0-1011.11-kvm 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-1011-kvm N/A linux-backports-modules-5.4.0-1011-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1011-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.11.0-2.el7 dmi.chassis.type: 1 dmi.chassis.vendor: Red Hat dmi.chassis.version: RHEL 7.6.0 PC (i440FX + PIIX, 1996) dmi.modalias: dmi:bvnSeaBIOS:bvr1.11.0-2.el7:bd04/01/2014:svnRDO:pnOpenStackCompute:pvr17.0.5-1.el7:cvnRedHat:ct1:cvrRHEL7.6.0PC(i440FX+PIIX,1996): dmi.product.family: Virtual Machine dmi.product.name: OpenStack Compute dmi.prod
[Kernel-packages] [Bug 1882153] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1882153/+attachment/5380726/+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/1882153 Title: linux-modules-kvm does not include net/netfilter/ipvs/*.ko modules Status in cloud-images: Invalid Status in linux package in Ubuntu: Confirmed Bug description: How to reproduce: 1. Boot from an Ubuntu Focal kvm cloud image # uname -r 5.4.0-1011-kvm # apt-get update # apt-get install linux-modules-5.4.0-1011-gcp [...] # dpkg -l linux-modules\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--== ii linux-modules-5.4.0-1011-gcp 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP ii linux-modules-5.4.0-1011-kvm 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP # ls -1 /lib/modules/5.4.0-1011-*/kernel/net/netfilter/ipvs/*ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_dh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_fo.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ftp.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblcr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_mh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_nq.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ovf.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_pe_sip.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_rr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sed.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wlc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wrr.ko There's no ipvs in linux-modules-5.4.0-1011-kvm version. Please include them. Tested on Ubuntu Focal from here: https://cloud-images.ubuntu.com/minimal/releases/focal/ https://cloud-images.ubuntu.com/focal/ https://cloud-images.ubuntu.com/releases/focal/ --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: RDO OpenStack Compute Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1011-kvm root=PARTUUID=815e35f9-92e6-44ee-9ea5-7f5a68f9c5d6 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: User Name 5.4.0-1011.11-kvm 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-1011-kvm N/A linux-backports-modules-5.4.0-1011-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1011-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.11.0-2.el7 dmi.chassis.type: 1 dmi.chassis.vendor: Red Hat dmi.chassis.version: RHEL 7.6.0 PC (i440FX + PIIX, 1996) dmi.modalias: dmi:bvnSeaBIOS:bvr1.11.0-2.el7:bd04/01/2014:svnRDO:pnOpenStackCompute:pvr17.0.5-1.el7:cvnRedHat:ct1:cvrRHEL7.6.0PC(i440FX+PIIX,1996): dmi.product.family: Virtual Machine dmi.product.name: OpenStack Compute dmi.product.ve
[Kernel-packages] [Bug 1882153] Re: linux-modules-kvm does not include net/netfilter/ipvs/*.ko modules
apport information ** Tags added: apport-collected uec-images ** Description changed: How to reproduce: 1. Boot from an Ubuntu Focal kvm cloud image # uname -r 5.4.0-1011-kvm # apt-get update # apt-get install linux-modules-5.4.0-1011-gcp [...] # dpkg -l linux-modules\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--== ii linux-modules-5.4.0-1011-gcp 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP ii linux-modules-5.4.0-1011-kvm 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP # ls -1 /lib/modules/5.4.0-1011-*/kernel/net/netfilter/ipvs/*ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_dh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_fo.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ftp.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblcr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_mh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_nq.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ovf.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_pe_sip.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_rr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sed.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wlc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wrr.ko There's no ipvs in linux-modules-5.4.0-1011-kvm version. Please include them. Tested on Ubuntu Focal from here: https://cloud-images.ubuntu.com/minimal/releases/focal/ https://cloud-images.ubuntu.com/focal/ https://cloud-images.ubuntu.com/releases/focal/ + --- + ProblemType: Bug + AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu27.2 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lsusb: Error: command ['lsusb'] failed with exit code 1: + Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory + Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: + MachineType: RDO OpenStack Compute + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash + ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1011-kvm root=PARTUUID=815e35f9-92e6-44ee-9ea5-7f5a68f9c5d6 ro console=tty1 console=ttyS0 panic=-1 + ProcVersionSignature: User Name 5.4.0-1011.11-kvm 5.4.34 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-1011-kvm N/A + linux-backports-modules-5.4.0-1011-kvm N/A + linux-firmware N/A + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: focal uec-images + Uname: Linux 5.4.0-1011-kvm x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video + _MarkForUpload: True + dmi.bios.date: 04/01/2014 + dmi.bios.vendor: SeaBIOS + dmi.bios.version: 1.11.0-2.el7 + dmi.chassis.type: 1 + dmi.chassis.vendor: Red Hat + dmi.chassis.version: RHEL 7.6.0 PC (i440FX + PIIX, 1996) + dmi.modalias: dmi:bvnSeaBIOS:bvr1.11.0-2.el7:bd04/01/2014:svnRDO:pnOpenStackCompute:pvr17.0.5-1.el7:cvnRedHat:ct1:cvrRHEL7.6.0PC(i440FX+PIIX,1996): + dmi.product.family: Virtual Machine + dmi.product.name: OpenStack Compute + dmi.product.version: 17.0.5-1.el7 + dmi.sys.vendor: RDO ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1882153/+attachment/5380722/+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/1882153 Title: linux-modules-kvm does not include
[Kernel-packages] [Bug 1882153] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1882153/+attachment/5380724/+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/1882153 Title: linux-modules-kvm does not include net/netfilter/ipvs/*.ko modules Status in cloud-images: Invalid Status in linux package in Ubuntu: Confirmed Bug description: How to reproduce: 1. Boot from an Ubuntu Focal kvm cloud image # uname -r 5.4.0-1011-kvm # apt-get update # apt-get install linux-modules-5.4.0-1011-gcp [...] # dpkg -l linux-modules\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--== ii linux-modules-5.4.0-1011-gcp 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP ii linux-modules-5.4.0-1011-kvm 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP # ls -1 /lib/modules/5.4.0-1011-*/kernel/net/netfilter/ipvs/*ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_dh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_fo.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ftp.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblcr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_mh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_nq.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ovf.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_pe_sip.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_rr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sed.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wlc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wrr.ko There's no ipvs in linux-modules-5.4.0-1011-kvm version. Please include them. Tested on Ubuntu Focal from here: https://cloud-images.ubuntu.com/minimal/releases/focal/ https://cloud-images.ubuntu.com/focal/ https://cloud-images.ubuntu.com/releases/focal/ --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: RDO OpenStack Compute Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1011-kvm root=PARTUUID=815e35f9-92e6-44ee-9ea5-7f5a68f9c5d6 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: User Name 5.4.0-1011.11-kvm 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-1011-kvm N/A linux-backports-modules-5.4.0-1011-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1011-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.11.0-2.el7 dmi.chassis.type: 1 dmi.chassis.vendor: Red Hat dmi.chassis.version: RHEL 7.6.0 PC (i440FX + PIIX, 1996) dmi.modalias: dmi:bvnSeaBIOS:bvr1.11.0-2.el7:bd04/01/2014:svnRDO:pnOpenStackCompute:pvr17.0.5-1.el7:cvnRedHat:ct1:cvrRHEL7.6.0PC(i440FX+PIIX,1996): dmi.product.family: Virtual Machine dmi.product.name: OpenStack Compute dmi.product.version: 17.0.5
[Kernel-packages] [Bug 1882153] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1882153/+attachment/5380731/+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/1882153 Title: linux-modules-kvm does not include net/netfilter/ipvs/*.ko modules Status in cloud-images: Invalid Status in linux package in Ubuntu: Confirmed Bug description: How to reproduce: 1. Boot from an Ubuntu Focal kvm cloud image # uname -r 5.4.0-1011-kvm # apt-get update # apt-get install linux-modules-5.4.0-1011-gcp [...] # dpkg -l linux-modules\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--== ii linux-modules-5.4.0-1011-gcp 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP ii linux-modules-5.4.0-1011-kvm 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP # ls -1 /lib/modules/5.4.0-1011-*/kernel/net/netfilter/ipvs/*ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_dh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_fo.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ftp.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblcr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_mh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_nq.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ovf.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_pe_sip.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_rr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sed.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wlc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wrr.ko There's no ipvs in linux-modules-5.4.0-1011-kvm version. Please include them. Tested on Ubuntu Focal from here: https://cloud-images.ubuntu.com/minimal/releases/focal/ https://cloud-images.ubuntu.com/focal/ https://cloud-images.ubuntu.com/releases/focal/ --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: RDO OpenStack Compute Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1011-kvm root=PARTUUID=815e35f9-92e6-44ee-9ea5-7f5a68f9c5d6 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: User Name 5.4.0-1011.11-kvm 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-1011-kvm N/A linux-backports-modules-5.4.0-1011-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1011-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.11.0-2.el7 dmi.chassis.type: 1 dmi.chassis.vendor: Red Hat dmi.chassis.version: RHEL 7.6.0 PC (i440FX + PIIX, 1996) dmi.modalias: dmi:bvnSeaBIOS:bvr1.11.0-2.el7:bd04/01/2014:svnRDO:pnOpenStackCompute:pvr17.0.5-1.el7:cvnRedHat:ct1:cvrRHEL7.6.0PC(i440FX+PIIX,1996): dmi.product.family: Virtual Machine dmi.product.name: OpenStack Compute dmi.product.vers
[Kernel-packages] [Bug 1881631] Re: arm64 Ubuntu kernel builds missing CONFIG_NLS_ASCII
So is it now changed to 'y'? Last night I confirmed that the module is missing in initrd.img and that is what was causing the mount error, so this is great news. -- 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/1881631 Title: arm64 Ubuntu kernel builds missing CONFIG_NLS_ASCII Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Eoan: Fix Committed Bug description: The CONFIG_NLS_ASCII was already set to Y in the raspi-5.4 kernel and bionic kernel by Juerg, now do the same change in the raspi2-5.3 kernel. [Impact] users reported that the raspi ubuntu core has some problem to mount filessytem, need to enable the NLS_ASCII and make it built-in. [Fix] change it from m to y just as the focal and bionic raspi kernel. [Test Case] building the kernel and boot the kernel, it could mount the filesystem successfully. [Regression Risk] Low, just changing a kconfig to y from m. Remounting log mounts in Ubuntu core are failing on arm64 builds due to missing CONFIG_NLS_ASCII in the arm64 kernel build options. This option is enabled on the other kernel builds but somehow was overlooked on arm64 appears to affect our ability to access logs via journalctl with data from prior to restart because certain mounts are failing. Other Raspberry Pi kernel builds, such as the armhf build, have the option enabled and so do not encounter the mount error. The kernel option that needs to be turned on to resolve this is CONFIG_NLS_ASCII. It needs to be set to either 'm' or 'y'. Most of the other chips have it set to 'y', keeping it built-in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1881631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882153] Missing required logs.
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 1882153 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 ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882153 Title: linux-modules-kvm does not include net/netfilter/ipvs/*.ko modules Status in cloud-images: Invalid Status in linux package in Ubuntu: Incomplete Bug description: How to reproduce: 1. Boot from an Ubuntu Focal kvm cloud image # uname -r 5.4.0-1011-kvm # apt-get update # apt-get install linux-modules-5.4.0-1011-gcp [...] # dpkg -l linux-modules\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--== ii linux-modules-5.4.0-1011-gcp 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP ii linux-modules-5.4.0-1011-kvm 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP # ls -1 /lib/modules/5.4.0-1011-*/kernel/net/netfilter/ipvs/*ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_dh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_fo.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ftp.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblcr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_mh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_nq.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ovf.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_pe_sip.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_rr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sed.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wlc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wrr.ko There's no ipvs in linux-modules-5.4.0-1011-kvm version. Please include them. Tested on Ubuntu Focal from here: https://cloud-images.ubuntu.com/minimal/releases/focal/ https://cloud-images.ubuntu.com/focal/ https://cloud-images.ubuntu.com/releases/focal/ To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1882153/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882153] Re: linux-modules-kvm does not include net/netfilter/ipvs/*.ko modules
Hi Éric, Would you mind saying why it's invalid? Thank you, Simon -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882153 Title: linux-modules-kvm does not include net/netfilter/ipvs/*.ko modules Status in cloud-images: Invalid Status in linux package in Ubuntu: Incomplete Bug description: How to reproduce: 1. Boot from an Ubuntu Focal kvm cloud image # uname -r 5.4.0-1011-kvm # apt-get update # apt-get install linux-modules-5.4.0-1011-gcp [...] # dpkg -l linux-modules\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--== ii linux-modules-5.4.0-1011-gcp 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP ii linux-modules-5.4.0-1011-kvm 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP # ls -1 /lib/modules/5.4.0-1011-*/kernel/net/netfilter/ipvs/*ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_dh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_fo.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ftp.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblcr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_mh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_nq.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ovf.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_pe_sip.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_rr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sed.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wlc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wrr.ko There's no ipvs in linux-modules-5.4.0-1011-kvm version. Please include them. Tested on Ubuntu Focal from here: https://cloud-images.ubuntu.com/minimal/releases/focal/ https://cloud-images.ubuntu.com/focal/ https://cloud-images.ubuntu.com/releases/focal/ To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1882153/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882268] [NEW] [linux-azure] Request for two CIFS commits in 16.04
Public bug reported:
There was a previous bug requesting the following two commits in 18.04:
84a1f5b1cc6f ("cifs: Fix potential softlockups while refreshing DFS cache")
2084ed57167c ("CIFS: Only send SMB2_NEGOTIATE command on new TCP connections")
There is an issue now, which requires these commits in the 4.15 based
16.04 kernel.
Can these two commits be applied to 16.04?
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
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/1882268
Title:
[linux-azure] Request for two CIFS commits in 16.04
Status in linux-azure package in Ubuntu:
New
Bug description:
There was a previous bug requesting the following two commits in
18.04:
84a1f5b1cc6f ("cifs: Fix potential softlockups while refreshing DFS cache")
2084ed57167c ("CIFS: Only send SMB2_NEGOTIATE command on new TCP connections")
There is an issue now, which requires these commits in the 4.15 based
16.04 kernel.
Can these two commits be applied to 16.04?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1882268/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
Kailiang suggested trying these: hda-verb /dev/snd/hwC0D0 0x20 0x500 0xf hda-verb /dev/snd/hwC0D0 0x20 0x400 0x7774 hda-verb /dev/snd/hwC0D0 0x20 0x500 0x45 hda-verb /dev/snd/hwC0D0 0x20 0x400 0x5289 Unfortunately, on my Asus Zenbook UX533FTC those commands did not fix microphone, even when setting it's boost/volume to 0% (both via alsamixer and pavucontrol). In fact, those commands did not seem to change anything. - Someone, using UX533FTC model, confirm that audio sounds exactly the same when using these commands: hda-verb /dev/snd/hwC0D0 0x20 0x500 0xf hda-verb /dev/snd/hwC0D0 0x20 0x477 0x74 versus these: hda-verb /dev/snd/hwC0D0 0x20 0x500 0x1b hda-verb /dev/snd/hwC0D0 0x20 0x477 0x4a4b hda-verb /dev/snd/hwC0D0 0x20 0x500 0xf hda-verb /dev/snd/hwC0D0 0x20 0x477 0x74 Thing is - try to hear any difference, especially in higher frequencies. I still think that we only need these 2 commands on this particular model. Note that I am using BIOS version "300" from date "2020/02/26" from Asus website https://www.asus.com/Laptops/ASUS- ZenBook-15-UX533FTC/HelpDesk_BIOS/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882153] Re: linux-modules-kvm does not include net/netfilter/ipvs/*.ko modules
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-images Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882153 Title: linux-modules-kvm does not include net/netfilter/ipvs/*.ko modules Status in cloud-images: Invalid Status in linux package in Ubuntu: New Bug description: How to reproduce: 1. Boot from an Ubuntu Focal kvm cloud image # uname -r 5.4.0-1011-kvm # apt-get update # apt-get install linux-modules-5.4.0-1011-gcp [...] # dpkg -l linux-modules\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--== ii linux-modules-5.4.0-1011-gcp 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP ii linux-modules-5.4.0-1011-kvm 5.4.0-1011.11 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP # ls -1 /lib/modules/5.4.0-1011-*/kernel/net/netfilter/ipvs/*ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_dh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_fo.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ftp.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lblcr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_lc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_mh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_nq.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_ovf.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_pe_sip.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_rr.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sed.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_sh.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wlc.ko /lib/modules/5.4.0-1011-gcp/kernel/net/netfilter/ipvs/ip_vs_wrr.ko There's no ipvs in linux-modules-5.4.0-1011-kvm version. Please include them. Tested on Ubuntu Focal from here: https://cloud-images.ubuntu.com/minimal/releases/focal/ https://cloud-images.ubuntu.com/focal/ https://cloud-images.ubuntu.com/releases/focal/ To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1882153/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
Hi Sergey, I just write the script with that four commands: hda-verb /dev/snd/hwC0D0 0x20 0x500 0x1b hda-verb /dev/snd/hwC0D0 0x20 0x477 0x4a4b hda-verb /dev/snd/hwC0D0 0x20 0x500 0xf hda-verb /dev/snd/hwC0D0 0x20 0x477 0x74 and just in case check that the volume values on alsamixer were ok. I check that both external speaker and jack works properly. My laptop is the ZenBook UX534FTC. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877270] Re: Devlink - add RoCE disable kernel support
** Description changed:
[Impact]
RoCE disable feature was added to the kernel v5.5.
This feature was requested by Mellanox customers that use Ubuntu 20.04,
and it's a very high important to deliver this feature to the customers
in one of ubuntu 20.04 SRU.
[SHORT DESCRIPTION]
RoCE enablement state controls driver support for RoCE traffic.
When RoCE is disabled, there is no gid table, only raw ethernet QPs are
supported and traffic on the well known UDP RoCE port is handled as raw
ethernet traffic.
-
[Test Case]
To change RoCE enablement state a user must change the driverinit cmode
value and run devlink reload.
User command examples:
- Disable RoCE::
- $ devlink dev param set pci/:06:00.0 name enable_roce value false
cmode driverinit
- $ devlink dev reload pci/:06:00.0
+ $ devlink dev param set pci/:06:00.0 name enable_roce value false
cmode driverinit
+ $ devlink dev reload pci/:06:00.0
- Read RoCE enablement state::
- $ devlink dev param show pci/:06:00.0 name enable_roce
- pci/:06:00.0:
- name enable_roce type generic
- values:
- cmode driverinit value true
+ $ devlink dev param show pci/:06:00.0 name enable_roce
+ pci/:06:00.0:
+ name enable_roce type generic
+ values:
+ cmode driverinit value true
[Regression Potential]
This feature shouldn't affect the regression because it's only adding support
for
RoCE enable/disable.
Also,
This feature was tested internally by Mellanox QA teams
those tests logs/results are private unfortunately i can't share it here
[Other Info]
Feature patchset:
+ 4383cfcc65e7 net/mlx5: Add devlink reload
+ 32680da71034 net/mlx5: Remove unneeded variable in mlx5_unload_one
94de879c28d8 IB/mlx5: Load profile according to RoCE enablement state
b5a498baf929 IB/mlx5: Rename profile and init methods
cc9defcbb8fa net/mlx5: Handle "enable_roce" devlink param
e90cde0d76f0 net/mlx5: Document flow_steering_mode devlink param
6c7295e13ffd devlink: Add new "enable_roce" generic device param
- patctwork:
- https://patchwork.ozlabs.org/cover/1192314/
+ 070c63f20f6c ("net: devlink: allow to change namespaces during
+ reload")## This one does not apply cleanly
+
+ All are in upstream in 5.5, so no pick into Groovy necessary
userspace:
- No userspace dependency on this. the feature uses the devlink
+ No userspace dependency on this. the feature uses the devlink
param functionality which already exists in UB20.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/1877270
Title:
Devlink - add RoCE disable kernel support
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Groovy:
In Progress
Bug description:
[Impact]
RoCE disable feature was added to the kernel v5.5.
This feature was requested by Mellanox customers that use Ubuntu 20.04,
and it's a very high important to deliver this feature to the customers
in one of ubuntu 20.04 SRU.
[SHORT DESCRIPTION]
RoCE enablement state controls driver support for RoCE traffic.
When RoCE is disabled, there is no gid table, only raw ethernet QPs are
supported and traffic on the well known UDP RoCE port is handled as raw
ethernet traffic.
[Test Case]
To change RoCE enablement state a user must change the driverinit
cmode value and run devlink reload.
User command examples:
- Disable RoCE::
$ devlink dev param set pci/:06:00.0 name enable_roce value false
cmode driverinit
$ devlink dev reload pci/:06:00.0
- Read RoCE enablement state::
$ devlink dev param show pci/:06:00.0 name enable_roce
pci/:06:00.0:
name enable_roce type generic
values:
cmode driverinit value true
[Regression Potential]
This feature shouldn't affect the regression because it's only adding support
for
RoCE enable/disable.
Also,
This feature was tested internally by Mellanox QA teams
those tests logs/results are private unfortunately i can't share it here
[Other Info]
Feature patchset:
4383cfcc65e7 net/mlx5: Add devlink reload
32680da71034 net/mlx5: Remove unneeded variable in mlx5_unload_one
94de879c28d8 IB/mlx5: Load profile according to RoCE enablement state
b5a498baf929 IB/mlx5: Rename profile and init methods
cc9defcbb8fa net/mlx5: Handle "enable_roce" devlink param
e90cde0d76f0 net/mlx5: Document flow_steering_mode devlink param
6c7295e13ffd devlink: Add new "enable_roce" generic device param
070c63f20f6c ("net: devlink: allow to change namespaces during
reload")## This one does not apply cleanly
All are in upstream in 5.5, so no pick into Groovy necessary
userspace:
No userspace dependency on this. the
[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
Hello Taha and Alac, Please clarify which exactly set of commands helped you. Is it the following set of commands? hda-verb /dev/snd/hwC0D0 0x20 0x500 0x1b hda-verb /dev/snd/hwC0D0 0x20 0x477 0x4a4b hda-verb /dev/snd/hwC0D0 0x20 0x500 0xf hda-verb /dev/snd/hwC0D0 0x20 0x477 0x74 Because on Thursday I received a notification about comment #160 from Kailiang. But can't find it anymore on the UI. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882195] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1882195/+attachment/5380707/+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/1882195 Title: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue Status in linux package in Ubuntu: Confirmed Bug description: Issue:- Getting blank screen after the initial install grub prompt. Tried acpi=off, nomodeset parameters added in grub still no luck Note:- Ubuntu 20.04 LTS worked without any issues. Env:- UEFI - Dual boot, secure boot disabled, SATA to AHCI Bios vers - 1.0.7 $find /sys/devices -name "edid" /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1/edid /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid $lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) === nomodeset:- defined to instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded. Surprisingly this desktop comes with single HDMI slot. And there is no any DP port. We need to rely on this one. Apart from the nomodeset/acpi=off, is there any grub parameter can I try here? Please suggest. Please note:- we need to rely on 18.04 LTS due to application compatibility. Please suggest Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/controlC2', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Alienware Alienware Aurora R9 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.7 dmi.board.name: 0T76PD dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.7:bd12/23/2019:svnAlienware:pnAlienwareAuroraR9:pvr1.0.7:rvnAlienware:rn0T76PD:rvrA01:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R9 dmi.product.sku: 0961 dmi.product.version: 1.0.7 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882195] Re: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue
Provided apport info from 20.04 LTS from the same model. Issue is with unable to install 18.04 LTS on this model. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882195 Title: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue Status in linux package in Ubuntu: Confirmed Bug description: Issue:- Getting blank screen after the initial install grub prompt. Tried acpi=off, nomodeset parameters added in grub still no luck Note:- Ubuntu 20.04 LTS worked without any issues. Env:- UEFI - Dual boot, secure boot disabled, SATA to AHCI Bios vers - 1.0.7 $find /sys/devices -name "edid" /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1/edid /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid $lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) === nomodeset:- defined to instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded. Surprisingly this desktop comes with single HDMI slot. And there is no any DP port. We need to rely on this one. Apart from the nomodeset/acpi=off, is there any grub parameter can I try here? Please suggest. Please note:- we need to rely on 18.04 LTS due to application compatibility. Please suggest Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/controlC2', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Alienware Alienware Aurora R9 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.7 dmi.board.name: 0T76PD dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.7:bd12/23/2019:svnAlienware:pnAlienwareAuroraR9:pvr1.0.7:rvnAlienware:rn0T76PD:rvrA01:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R9 dmi.product.sku: 0961 dmi.product.version: 1.0.7 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882195] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1882195/+attachment/5380699/+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/1882195 Title: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue Status in linux package in Ubuntu: Confirmed Bug description: Issue:- Getting blank screen after the initial install grub prompt. Tried acpi=off, nomodeset parameters added in grub still no luck Note:- Ubuntu 20.04 LTS worked without any issues. Env:- UEFI - Dual boot, secure boot disabled, SATA to AHCI Bios vers - 1.0.7 $find /sys/devices -name "edid" /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1/edid /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid $lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) === nomodeset:- defined to instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded. Surprisingly this desktop comes with single HDMI slot. And there is no any DP port. We need to rely on this one. Apart from the nomodeset/acpi=off, is there any grub parameter can I try here? Please suggest. Please note:- we need to rely on 18.04 LTS due to application compatibility. Please suggest Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/controlC2', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Alienware Alienware Aurora R9 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.7 dmi.board.name: 0T76PD dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.7:bd12/23/2019:svnAlienware:pnAlienwareAuroraR9:pvr1.0.7:rvnAlienware:rn0T76PD:rvrA01:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R9 dmi.product.sku: 0961 dmi.product.version: 1.0.7 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882195] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1882195/+attachment/5380706/+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/1882195 Title: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue Status in linux package in Ubuntu: Confirmed Bug description: Issue:- Getting blank screen after the initial install grub prompt. Tried acpi=off, nomodeset parameters added in grub still no luck Note:- Ubuntu 20.04 LTS worked without any issues. Env:- UEFI - Dual boot, secure boot disabled, SATA to AHCI Bios vers - 1.0.7 $find /sys/devices -name "edid" /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1/edid /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid $lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) === nomodeset:- defined to instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded. Surprisingly this desktop comes with single HDMI slot. And there is no any DP port. We need to rely on this one. Apart from the nomodeset/acpi=off, is there any grub parameter can I try here? Please suggest. Please note:- we need to rely on 18.04 LTS due to application compatibility. Please suggest Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/controlC2', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Alienware Alienware Aurora R9 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.7 dmi.board.name: 0T76PD dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.7:bd12/23/2019:svnAlienware:pnAlienwareAuroraR9:pvr1.0.7:rvnAlienware:rn0T76PD:rvrA01:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R9 dmi.product.sku: 0961 dmi.product.version: 1.0.7 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
