[Kernel-packages] [Bug 1854059] Re: [UBUNTU] kernel: cpu idle time calculation
I'm changing the status of the "linux (Ubuntu)" entry - which represents 'focal' the current release in development - to Fix Released, since patch "s390/idle: fix cpu idle time calculation" with commit ID "3d7efa4" landed in focal with the update of focal's kernel to 5.4 (5.4.0.9.11 as of today). This patch is in: Ubuntu-5.4-5.4.0-10.13 Ubuntu-5.4-5.4.0-11.14 Ubuntu-5.4.0-8.11 Ubuntu-5.4.0-9.12 ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854059 Title: [UBUNTU] kernel: cpu idle time calculation Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: Description: kernel: cpu idle time calculation Symptom: The cpu idle time reported within /proc/stat as well as in /sys/devices/system/cpu/cpuX/idle_time_us sometimes may show incorrect values. Problem: The kernel tries to figure out when a cpu entered idle by accessing its per-cpu data structure. There is an ordering problem: if a remote cpu has an idle_enter value which is not zero, and an idle_exit value which is zero, it is assumed it is idle since "now". The "now" timestamp however is taken before the idle_enter value is read. This in turn means that "now" can be smaller than idle_enter of the remote cpu. Unconditionally subtracting idle_enter from "now" can thus lead to a negative value (aka large unsigned value). Solution: Move the get_tod_clock() invocation. Upstream-ID: https://github.com/torvalds/linux/commit/3d7efa4edd07be5c5c3ffa95ba63e97e070e1f3f Patch tagged as "stable". Tracking the integration of this patch in the relevant distros.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1854059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854059] Re: [UBUNTU] kernel: cpu idle time calculation
Updating bionic entry to Fix Released, since patch "s390/idle: fix cpu idle time calculation" with commit "44ef7df" is in bionic master. It's available with the kernels: Ubuntu-4.15.0-71.80 Ubuntu-4.15.0-72.81 Ubuntu-4.15.0-73.82 Ubuntu-4.15.0-74.84 and we are at "linux-generic | 4.15.0.74.76 | bionic-updates | s390x" as of today. ** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854059 Title: [UBUNTU] kernel: cpu idle time calculation Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Bug description: Description: kernel: cpu idle time calculation Symptom: The cpu idle time reported within /proc/stat as well as in /sys/devices/system/cpu/cpuX/idle_time_us sometimes may show incorrect values. Problem: The kernel tries to figure out when a cpu entered idle by accessing its per-cpu data structure. There is an ordering problem: if a remote cpu has an idle_enter value which is not zero, and an idle_exit value which is zero, it is assumed it is idle since "now". The "now" timestamp however is taken before the idle_enter value is read. This in turn means that "now" can be smaller than idle_enter of the remote cpu. Unconditionally subtracting idle_enter from "now" can thus lead to a negative value (aka large unsigned value). Solution: Move the get_tod_clock() invocation. Upstream-ID: https://github.com/torvalds/linux/commit/3d7efa4edd07be5c5c3ffa95ba63e97e070e1f3f Patch tagged as "stable". Tracking the integration of this patch in the relevant distros.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1854059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854059] Re: [UBUNTU] kernel: cpu idle time calculation
Updating eoan entry to Fix Released, since patch "s390/idle: fix cpu idle time calculation" with commit "a700d7b0" is in eoan master. It's available with the kernels: Ubuntu-5.3.0-24.26 Ubuntu-5.3.0-25.27 Ubuntu-5.3.0-26.28 Ubuntu-5.3.0-27.29 and we are at "linux-generic | 5.3.0.26.30 | eoan-updates| s390x" as of today. ** Changed in: linux (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854059 Title: [UBUNTU] kernel: cpu idle time calculation Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Bug description: Description: kernel: cpu idle time calculation Symptom: The cpu idle time reported within /proc/stat as well as in /sys/devices/system/cpu/cpuX/idle_time_us sometimes may show incorrect values. Problem: The kernel tries to figure out when a cpu entered idle by accessing its per-cpu data structure. There is an ordering problem: if a remote cpu has an idle_enter value which is not zero, and an idle_exit value which is zero, it is assumed it is idle since "now". The "now" timestamp however is taken before the idle_enter value is read. This in turn means that "now" can be smaller than idle_enter of the remote cpu. Unconditionally subtracting idle_enter from "now" can thus lead to a negative value (aka large unsigned value). Solution: Move the get_tod_clock() invocation. Upstream-ID: https://github.com/torvalds/linux/commit/3d7efa4edd07be5c5c3ffa95ba63e97e070e1f3f Patch tagged as "stable". Tracking the integration of this patch in the relevant distros.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1854059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854059] Re: [UBUNTU] kernel: cpu idle time calculation
Updating disco entry to Fix Released, since patch "s390/idle: fix cpu idle time calculation" with commit "b3ff8122" is in disco master. It's available with the kernels: Ubuntu-5.0.0-38.41 Ubuntu-5.0.0-39.43 and we are at "linux-generic | 5.0.0.38.40 | disco-updates | s390x" as of today. ** Changed in: linux (Ubuntu Disco) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854059 Title: [UBUNTU] kernel: cpu idle time calculation Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Bug description: Description: kernel: cpu idle time calculation Symptom: The cpu idle time reported within /proc/stat as well as in /sys/devices/system/cpu/cpuX/idle_time_us sometimes may show incorrect values. Problem: The kernel tries to figure out when a cpu entered idle by accessing its per-cpu data structure. There is an ordering problem: if a remote cpu has an idle_enter value which is not zero, and an idle_exit value which is zero, it is assumed it is idle since "now". The "now" timestamp however is taken before the idle_enter value is read. This in turn means that "now" can be smaller than idle_enter of the remote cpu. Unconditionally subtracting idle_enter from "now" can thus lead to a negative value (aka large unsigned value). Solution: Move the get_tod_clock() invocation. Upstream-ID: https://github.com/torvalds/linux/commit/3d7efa4edd07be5c5c3ffa95ba63e97e070e1f3f Patch tagged as "stable". Tracking the integration of this patch in the relevant distros.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1854059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850099] Re: Kernel 5.3.0-19 panic after upgrade to eoan ermine from disco dingo
If it's fixed then there's no need to test further. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850099 Title: Kernel 5.3.0-19 panic after upgrade to eoan ermine from disco dingo Status in linux package in Ubuntu: Fix Released Bug description: After upgrading to eoan ermine, my laptop (Dell Precision 5510) got an error message stating "Error: out of memory Press any key to continue..." After pressing a key, nothing changed. I left the room and came back to see that there was a kernel panic. I'll attach picture as I couldn't copy/paste the console output. Description: Ubuntu 19.10 Release: 19.10 linux-image-5.3.0-19-generic I expect the kernel to load without a panic. The kernel panicked. After rebooting and selecting an older kernel, I was able to boot and load the old kernel without issue (5.0.0-32-generic) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-19-generic 5.3.0-19.20 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lost 1947 F pulseaudio CurrentDesktop: XFCE Date: Mon Oct 28 00:52:26 2019 HibernationDevice: RESUME=UUID=0dba346e-043c-4e62-95a4-911a6a65e626 InstallationDate: Installed on 2016-06-17 (1227 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Touchscreen Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5510 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-32-generic N/A linux-backports-modules-5.0.0-32-generic N/A linux-firmware1.183.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0WVDX2 dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd10/03/2019:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0WVDX2:rvrA07:cvnDellInc.:ct9:cvr: dmi.product.family: Precision dmi.product.name: Precision 5510 dmi.product.sku: 06E5 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)
Excellent news! The bluetooth dock battery status started working properly a couple of weeks ago. I can't be sure which update fixed the bug, but here is the latest system status:- ubuntu 19.10 eoan Desktop 5.3.0-26-generic x86_64 kernel Bluez-* 5.50-0ubuntu4 gnome-bluetooth 3.34.0-1 udev 242-7ubuntu3.2 libudev-1.0.0"amd64 1.233-1 The bug can finally be closed as fixed. Thanks very much everyone who contributed. Brian -- 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/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later) Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858832] [NEW] invalid opcode xdr_buf_read_netobj on nfs4+krb5i directory
You have been subscribed to a public bug: RELEASE=19.3 CODENAME=tricia EDITION="Cinnamon" DESCRIPTION="Linux Mint 19.3 Tricia" DESKTOP=Gnome TOOLKIT=GTK NEW_FEATURES_URL=https://www.linuxmint.com/rel_tricia_cinnamon_whatsnew.php RELEASE_NOTES_URL=https://www.linuxmint.com/rel_tricia_cinnamon.php USER_GUIDE_URL=https://www.linuxmint.com/documentation.php GRUB_TITLE=Linux Mint 19.3 Cinnamon My home dir is mounted through nfs on a local server via nfs4 and krb5i. When stressing the mounted directory or its sub-directories (sometimes starting firefox, sometimes starting thunderbird, nearly guaranteed when compiling, sometimes the login itself), it will eventually lead to the following stack-trace. The corresponding process is then stuck and accessing the mounted directory (like calling ls) easily yields further and similar stack trace and causing the process to also stuck. Currently I am running an AMD 3950x on a ASUS Crosshair VII Hero Wifi (chipset x470), but I had the same issues with an Intel 6700K on a ASUS Crosshair VIII Hero in fall of 2019. I couldn't be bother back then to report the bug so I just kept running a working kernel (~5.0.0-15 I think) without updating it. After Christmas I updated said Intel machine with the AMD machine, re-installed Linux Mint, installed all updates and therefore ran into this issue again. [ 49.420081] [ cut here ] [ 49.420084] kernel BUG at /build/linux-hwe-FLYqTt/linux-hwe-5.0.0/net/sunrpc/xdr.c:434! [ 49.420092] invalid opcode: [#1] SMP NOPTI [ 49.420095] CPU: 16 PID: 469 Comm: kworker/u64:13 Tainted: P OE 5.0.0-37-generic #40~18.04.1-Ubuntu [ 49.420096] Hardware name: System manufacturer System Product Name/ROG CROSSHAIR VII HERO (WI-FI), BIOS 3004 12/16/2019 [ 49.420109] Workqueue: rpciod rpc_async_schedule [sunrpc] [ 49.420123] RIP: 0010:xdr_shrink_pagelen+0x9e/0xa0 [sunrpc] [ 49.420124] Code: 29 ea e8 85 f4 ff ff 44 8b 63 34 8b 43 3c 45 29 ec 44 29 e8 3b 43 40 44 89 63 34 89 43 3c 73 03 89 43 40 5b 41 5c 41 5d 5d c3 <0f> 0b 0f 1f 44 00 00 4c 8d 54 24 08 48 83 e4 f0 b9 04 00 00 00 41 [ 49.420126] RSP: 0018:b93787be7b38 EFLAGS: 00010287 [ 49.420128] RAX: 000c RBX: 006c RCX: 001c [ 49.420129] RDX: 005c RSI: 0010 RDI: 8e1a87c56e50 [ 49.420130] RBP: b93787be7b50 R08: 8e1b06999700 R09: [ 49.420131] R10: R11: 8e1b0ecd1cd0 R12: 8e1a87c56e50 [ 49.420132] R13: b93787be7c00 R14: 0058 R15: c228e8c0 [ 49.420134] FS: () GS:8e1b1ea0() knlGS: [ 49.420135] CS: 0010 DS: ES: CR0: 80050033 [ 49.420136] CR2: 7ffa1faeb000 CR3: 000f19abe000 CR4: 00340ee0 [ 49.420137] Call Trace: [ 49.420150] xdr_buf_read_netobj+0x122/0x180 [sunrpc] [ 49.420154] ? kzfree+0x2d/0x40 [ 49.420158] ? crypto_destroy_tfm+0x73/0xb0 [ 49.420162] gss_unwrap_resp_integ.isra.11+0x9c/0x100 [auth_rpcgss] [ 49.420164] ? gss_unwrap_resp_integ.isra.11+0x9c/0x100 [auth_rpcgss] [ 49.420167] gss_unwrap_resp+0x13c/0x280 [auth_rpcgss] [ 49.420170] ? gss_unwrap_resp+0x13c/0x280 [auth_rpcgss] [ 49.420172] ? gss_validate+0x242/0x300 [auth_rpcgss] [ 49.420184] ? nfs4_xdr_dec_readdir+0x100/0x100 [nfsv4] [ 49.420194] rpcauth_unwrap_resp+0x67/0xe0 [sunrpc] [ 49.420204] ? nfs4_xdr_dec_readdir+0x100/0x100 [nfsv4] [ 49.420213] call_decode+0x1c4/0x880 [sunrpc] [ 49.420216] ? __switch_to_asm+0x35/0x70 [ 49.420224] ? rpc_check_timeout+0x130/0x130 [sunrpc] [ 49.420233] __rpc_execute+0x7a/0x3f0 [sunrpc] [ 49.420242] rpc_async_schedule+0x12/0x20 [sunrpc] [ 49.420245] process_one_work+0x1fd/0x400 [ 49.420247] worker_thread+0x34/0x410 [ 49.420249] kthread+0x121/0x140 [ 49.420250] ? process_one_work+0x400/0x400 [ 49.420252] ? kthread_park+0xb0/0xb0 [ 49.420254] ret_from_fork+0x22/0x40 [ 49.420255] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache edac_mce_amd snd_hda_codec_hdmi joydev kvm hid_roccat_koneplus hid_roccat irqbypass hid_roccat_common nvidia_uvm(OE) nvidia_drm(POE) nvidia_modeset(POE) snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_ca0132 snd_hda_intel snd_usb_audio snd_hda_codec snd_usbmidi_lib snd_hda_core crct10dif_pclmul snd_hwdep crc32_pclmul snd_seq_midi snd_pcm nvidia(POE) ghash_clmulni_intel snd_seq_midi_event eeepc_wmi aesni_intel snd_rawmidi asus_wmi sparse_keymap aes_x86_64 crypto_simd cryptd video glue_helper snd_seq drm_kms_helper snd_seq_device mxm_wmi wmi_bmof input_leds drm snd_timer ipmi_devintf snd serio_raw ccp ipmi_msghandler fb_sys_fops syscopyarea sysfillrect sysimgblt soundcore k10temp mac_hid sch_fq_codel asus_wmi_sensors(OE) parport_pc sunrpc ppdev lp parport ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_mirror dm_region_hash dm_log hid_pla
[Kernel-packages] [Bug 1858832] Re: invalid opcode xdr_buf_read_netobj on nfs4+krb5i directory
Thanks for testing! I will SRU this to our Disco kernel. https://lists.ubuntu.com/archives/kernel-team/2020-January/106822.html ** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu) ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Tags added: disco ** Description changed: + == SRU Justification == + The xdr_shrink_pagelen() added in commit 5f1bc39 (SUNRPC: Fix buffer + handling of GSS MIC without slack), which applied in the Disco tree via + stable update process, sometimes will raise the following kernel trace + when the bytes to remove from buf->pages is larger than buf->page_len: + + [ 49.420081] [ cut here ] + [ 49.420084] kernel BUG at /build/linux-hwe-FLYqTt/linux-hwe-5.0.0/net/sunrpc/xdr.c:434! + [ 49.420092] invalid opcode: [#1] SMP NOPTI + [ 49.420095] CPU: 16 PID: 469 Comm: kworker/u64:13 Tainted: P OE 5.0.0-37-generic #40~18.04.1-Ubuntu + [ 49.420096] Hardware name: System manufacturer System Product Name/ROG CROSSHAIR VII HERO (WI-FI), BIOS 3004 12/16/2019 + [ 49.420109] Workqueue: rpciod rpc_async_schedule [sunrpc] + [ 49.420123] RIP: 0010:xdr_shrink_pagelen+0x9e/0xa0 [sunrpc] + [ 49.420124] Code: 29 ea e8 85 f4 ff ff 44 8b 63 34 8b 43 3c 45 29 ec 44 29 e8 3b 43 40 44 89 63 34 89 43 3c 73 03 89 43 40 5b 41 5c 41 5d 5d c3 <0f> 0b 0f 1f 44 00 00 4c 8d 54 24 08 48 83 e4 f0 b9 04 00 00 00 41 + [ 49.420126] RSP: 0018:b93787be7b38 EFLAGS: 00010287 + [ 49.420128] RAX: 000c RBX: 006c RCX: 001c + [ 49.420129] RDX: 005c RSI: 0010 RDI: 8e1a87c56e50 + [ 49.420130] RBP: b93787be7b50 R08: 8e1b06999700 R09: + [ 49.420131] R10: R11: 8e1b0ecd1cd0 R12: 8e1a87c56e50 + [ 49.420132] R13: b93787be7c00 R14: 0058 R15: c228e8c0 + [ 49.420134] FS: () GS:8e1b1ea0() knlGS: + [ 49.420135] CS: 0010 DS: ES: CR0: 80050033 + [ 49.420136] CR2: 7ffa1faeb000 CR3: 000f19abe000 CR4: 00340ee0 + [ 49.420137] Call Trace: + [ 49.420150] xdr_buf_read_netobj+0x122/0x180 [sunrpc] + [ 49.420154] ? kzfree+0x2d/0x40 + [ 49.420158] ? crypto_destroy_tfm+0x73/0xb0 + [ 49.420162] gss_unwrap_resp_integ.isra.11+0x9c/0x100 [auth_rpcgss] + [ 49.420164] ? gss_unwrap_resp_integ.isra.11+0x9c/0x100 [auth_rpcgss] + [ 49.420167] gss_unwrap_resp+0x13c/0x280 [auth_rpcgss] + [ 49.420170] ? gss_unwrap_resp+0x13c/0x280 [auth_rpcgss] + [ 49.420172] ? gss_validate+0x242/0x300 [auth_rpcgss] + [ 49.420184] ? nfs4_xdr_dec_readdir+0x100/0x100 [nfsv4] + [ 49.420194] rpcauth_unwrap_resp+0x67/0xe0 [sunrpc] + [ 49.420204] ? nfs4_xdr_dec_readdir+0x100/0x100 [nfsv4] + [ 49.420213] call_decode+0x1c4/0x880 [sunrpc] + [ 49.420216] ? __switch_to_asm+0x35/0x70 + [ 49.420224] ? rpc_check_timeout+0x130/0x130 [sunrpc] + [ 49.420233] __rpc_execute+0x7a/0x3f0 [sunrpc] + [ 49.420242] rpc_async_schedule+0x12/0x20 [sunrpc] + [ 49.420245] process_one_work+0x1fd/0x400 + [ 49.420247] worker_thread+0x34/0x410 + [ 49.420249] kthread+0x121/0x140 + [ 49.420250] ? process_one_work+0x400/0x400 + [ 49.420252] ? kthread_park+0xb0/0xb0 + [ 49.420254] ret_from_fork+0x22/0x40 + + == Fixes == + * e8d70b32 (SUNRPC: Fix another issue with MIC buffer space) + Instead of calling BUG_ON, this patch will just cap the number of bytes + that xdr_shrink_pagelen() will move. + + Only Disco kernel needs this patch, for Bionic and earlier they don't + have 5f1bc39, and this fix has been applied to Eoan and onward. + + == Test == + Test kernel can be found here: + https://people.canonical.com/~phlin/kernel/lp-1858832-sunrpc-bufferhandling/ + + And it's been stress-tested by the bug reporter, Michael, this issue + can no longer be reproduced. + + == Regression Potential == + Low. It's just changing the length of bytes to shrink, change limited + to a single driver with positive test result. + + + == Original Bug Report == RELEASE=19.3 CODENAME=tricia EDITION="Cinnamon" DESCRIPTION="Linux Mint 19.3 Tricia" DESKTOP=Gnome TOOLKIT=GTK NEW_FEATURES_URL=https://www.linuxmint.com/rel_tricia_cinnamon_whatsnew.php RELEASE_NOTES_URL=https://www.linuxmint.com/rel_tricia_cinnamon.php USER_GUIDE_URL=https://www.linuxmint.com/documentation.php GRUB_TITLE=Linux Mint 19.3 Cinnamon My home dir is mounted through nfs on a local server via nfs4 and krb5i. When stressing the mounted directory or its sub-directories (sometimes starting firefox, sometimes starting thunderbird, nearly guaranteed when compiling, sometimes the login itself), it will eventually lead to the following stack-trace. The corresponding process is then stuck and accessing the mounted director
[Kernel-packages] [Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- 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/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later) Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854059] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-01-13 03:43 EDT--- IBM Bugzilla status -> closed Fix Released with all requested distros -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854059 Title: [UBUNTU] kernel: cpu idle time calculation Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Bug description: Description: kernel: cpu idle time calculation Symptom: The cpu idle time reported within /proc/stat as well as in /sys/devices/system/cpu/cpuX/idle_time_us sometimes may show incorrect values. Problem: The kernel tries to figure out when a cpu entered idle by accessing its per-cpu data structure. There is an ordering problem: if a remote cpu has an idle_enter value which is not zero, and an idle_exit value which is zero, it is assumed it is idle since "now". The "now" timestamp however is taken before the idle_enter value is read. This in turn means that "now" can be smaller than idle_enter of the remote cpu. Unconditionally subtracting idle_enter from "now" can thus lead to a negative value (aka large unsigned value). Solution: Move the get_tod_clock() invocation. Upstream-ID: https://github.com/torvalds/linux/commit/3d7efa4edd07be5c5c3ffa95ba63e97e070e1f3f Patch tagged as "stable". Tracking the integration of this patch in the relevant distros.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1854059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859407] [NEW] peripheral devices on Dell WD19TB cannot be detected after suspend resume
Public bug reported: [Summary] If user un-plugs and then re-plugs the thunderbolt 3 cable of Dell WD19TB into the laptop during suspend state, peripheral devices on the docking station cannot be re-probed after the system resumes. [Steps to reproduce] 1. Please make sure that the WD19 (TBT 3 cable) connects to the laptop 2. Suspend the system 3. Un-plug the TBT 3 cable of WD19 docking station from laptop 4. Re-plug the TBT 3 cable of WD19 docking station into the laptop 5. Press the Enter key or power button to wake up the system 6. Connect an Ethernet cable to a Ethernet port of WD19 docking station 7. Check if the Ethernet interface is available and networking connection is up. [Expected result] The Ethernet interface can be detected [Actual result] The Ethernet cannot be detected ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-osp1 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-osp1 (Ubuntu Bionic) Importance: Undecided Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux (Ubuntu Disco) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-osp1 (Ubuntu Disco) Importance: Undecided Status: Won't Fix ** Affects: linux (Ubuntu Eoan) Importance: Undecided Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux-oem-osp1 (Ubuntu Eoan) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1852989 somerville ** Tags added: oem-priority originate-from-1852989 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859407 Title: peripheral devices on Dell WD19TB cannot be detected after suspend resume Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: In Progress Status in linux source package in Disco: Won't Fix Status in linux-oem-osp1 source package in Disco: Won't Fix Status in linux source package in Eoan: In Progress Status in linux-oem-osp1 source package in Eoan: New Bug description: [Summary] If user un-plugs and then re-plugs the thunderbolt 3 cable of Dell WD19TB into the laptop during suspend state, peripheral devices on the docking station cannot be re-probed after the system resumes. [Steps to reproduce] 1. Please make sure that the WD19 (TBT 3 cable) connects to the laptop 2. Suspend the system 3. Un-plug the TBT 3 cable of WD19 docking station from laptop 4. Re-plug the TBT 3 cable of WD19 docking station into the laptop 5. Press the Enter key or power button to wake up the system 6. Connect an Ethernet cable to a Ethernet port of WD19 docking station 7. Check if the Ethernet interface is available and networking connection is up. [Expected result] The Ethernet interface can be detected [Actual result] The Ethernet cannot be detected To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859407] Re: peripheral devices on Dell WD19TB cannot be detected after suspend resume
$ git bisect log git bisect start # new: [54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c] Linux 5.4-rc1 git bisect new 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c # old: [4d856f72c10ecb060868ed10ff1b1453943fc6c8] Linux 5.3 git bisect old 4d856f72c10ecb060868ed10ff1b1453943fc6c8 # new: [81160dda9a7aad13c04e78bb2cfd3c4630e3afab] Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next git bisect new 81160dda9a7aad13c04e78bb2cfd3c4630e3afab # old: [04cbfba6208592999d7bfe6609ec01dc3fde73f5] Merge tag 'dmaengine-5.4-rc1' of git://git.infradead.org/users/vkoul/slave-dma git bisect old 04cbfba6208592999d7bfe6609ec01dc3fde73f5 # old: [e69e9db9031b2ef4897cfafb9a496f8eb6724e14] nfp: nsp: add support for hwinfo set operation git bisect old e69e9db9031b2ef4897cfafb9a496f8eb6724e14 # new: [e6874fc29410fabfdbc8c12b467f41a16cbcfd2b] Merge tag 'staging-5.4-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging git bisect new e6874fc29410fabfdbc8c12b467f41a16cbcfd2b # new: [c6b48dad92aedaa9bdc013ee495cb5b1bbdf1f11] Merge tag 'usb-5.4-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb git bisect new c6b48dad92aedaa9bdc013ee495cb5b1bbdf1f11 # new: [fe38bd6862074c0a2b9be7f31f043aaa70b2af5f] Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm git bisect new fe38bd6862074c0a2b9be7f31f043aaa70b2af5f # new: [031f469ecf7c85d2d43a04abd256b6f3a1ef5794] Merge branch 'pm-devfreq' git bisect new 031f469ecf7c85d2d43a04abd256b6f3a1ef5794 # new: [2cdd5cc7032636d5f17822c6ba30ac08bfd2cb6d] Merge branch 'pm-cpuidle' git bisect new 2cdd5cc7032636d5f17822c6ba30ac08bfd2cb6d # new: [b90ff3554aa3e123bb7e6d08789f6fd92d86ddde] ACPI: PM: s2idle: Always set up EC GPE for system wakeup git bisect new b90ff3554aa3e123bb7e6d08789f6fd92d86ddde # new: [2e2c2fdc53437beffd2cf26aaf6187e602d565bc] ACPI: PM: s2idle: Rearrange lps0_device_attach() git bisect new 2e2c2fdc53437beffd2cf26aaf6187e602d565bc # old: [41275eb5c7181febdfaa63c3a0ad9b7acdadcd52] ACPI: PM: Set s2idle_wakeup earlier and clear it later git bisect old 41275eb5c7181febdfaa63c3a0ad9b7acdadcd52 # new: [8eb0fd3b55f084320ae511cd5a64d356cf497c83] PM: sleep: Integrate suspend-to-idle with generig suspend flow git bisect new 8eb0fd3b55f084320ae511cd5a64d356cf497c83 # new: [56b991849009f5def0443bfb2f48c8321d888e15] PM: sleep: Simplify suspend-to-idle control flow git bisect new 56b991849009f5def0443bfb2f48c8321d888e15 # first new commit: [56b991849009f5def0443bfb2f48c8321d888e15] PM: sleep: Simplify suspend-to-idle control flow -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859407 Title: peripheral devices on Dell WD19TB cannot be detected after suspend resume Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: In Progress Status in linux source package in Disco: Won't Fix Status in linux-oem-osp1 source package in Disco: Won't Fix Status in linux source package in Eoan: In Progress Status in linux-oem-osp1 source package in Eoan: New Bug description: [Summary] If user un-plugs and then re-plugs the thunderbolt 3 cable of Dell WD19TB into the laptop during suspend state, peripheral devices on the docking station cannot be re-probed after the system resumes. [Steps to reproduce] 1. Please make sure that the WD19 (TBT 3 cable) connects to the laptop 2. Suspend the system 3. Un-plug the TBT 3 cable of WD19 docking station from laptop 4. Re-plug the TBT 3 cable of WD19 docking station into the laptop 5. Press the Enter key or power button to wake up the system 6. Connect an Ethernet cable to a Ethernet port of WD19 docking station 7. Check if the Ethernet interface is available and networking connection is up. [Expected result] The Ethernet interface can be detected [Actual result] The Ethernet cannot be detected To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859407] 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 1859407 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859407 Title: peripheral devices on Dell WD19TB cannot be detected after suspend resume Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: In Progress Status in linux source package in Disco: Won't Fix Status in linux-oem-osp1 source package in Disco: Won't Fix Status in linux source package in Eoan: In Progress Status in linux-oem-osp1 source package in Eoan: New Bug description: [Summary] If user un-plugs and then re-plugs the thunderbolt 3 cable of Dell WD19TB into the laptop during suspend state, peripheral devices on the docking station cannot be re-probed after the system resumes. [Steps to reproduce] 1. Please make sure that the WD19 (TBT 3 cable) connects to the laptop 2. Suspend the system 3. Un-plug the TBT 3 cable of WD19 docking station from laptop 4. Re-plug the TBT 3 cable of WD19 docking station into the laptop 5. Press the Enter key or power button to wake up the system 6. Connect an Ethernet cable to a Ethernet port of WD19 docking station 7. Check if the Ethernet interface is available and networking connection is up. [Expected result] The Ethernet interface can be detected [Actual result] The Ethernet cannot be detected To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859407] Re: peripheral devices on Dell WD19TB cannot be detected after suspend resume
Would focus on linux-oem-osp1 for Bionic and linux-generic for Eoan. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-osp1 (Ubuntu Bionic) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859407 Title: peripheral devices on Dell WD19TB cannot be detected after suspend resume Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: In Progress Status in linux source package in Disco: Won't Fix Status in linux-oem-osp1 source package in Disco: Won't Fix Status in linux source package in Eoan: In Progress Status in linux-oem-osp1 source package in Eoan: New Bug description: [Summary] If user un-plugs and then re-plugs the thunderbolt 3 cable of Dell WD19TB into the laptop during suspend state, peripheral devices on the docking station cannot be re-probed after the system resumes. [Steps to reproduce] 1. Please make sure that the WD19 (TBT 3 cable) connects to the laptop 2. Suspend the system 3. Un-plug the TBT 3 cable of WD19 docking station from laptop 4. Re-plug the TBT 3 cable of WD19 docking station into the laptop 5. Press the Enter key or power button to wake up the system 6. Connect an Ethernet cable to a Ethernet port of WD19 docking station 7. Check if the Ethernet interface is available and networking connection is up. [Expected result] The Ethernet interface can be detected [Actual result] The Ethernet cannot be detected To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859407] Re: peripheral devices on Dell WD19TB cannot be detected after suspend resume
So this pulls following commits: * 56b991849009f PM: sleep: Simplify suspend-to-idle control flow * 41275eb5c7181 ACPI: PM: Set s2idle_wakeup earlier and clear it later * 9089f16e053af ACPI: EC: Return bool from acpi_ec_dispatch_gpe() * 6921de898ba8f ACPICA: Return u32 from acpi_dispatch_gpe() * 3a79bc63d9075 PCI: irq: Introduce rearm_wake_irq() And 56b991849009f takes an additional fix as we've done for bug 1858424: * 016b87ca5c8c6 ACPI: EC: Rework flushing of pending work ** Also affects: linux-oem-osp1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Status: New => Won't Fix ** Changed in: linux-oem-osp1 (Ubuntu Disco) Status: New => Won't Fix ** Changed in: linux-oem-osp1 (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => Won't Fix ** Changed in: linux (Ubuntu Eoan) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859407 Title: peripheral devices on Dell WD19TB cannot be detected after suspend resume Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: In Progress Status in linux source package in Disco: Won't Fix Status in linux-oem-osp1 source package in Disco: Won't Fix Status in linux source package in Eoan: In Progress Status in linux-oem-osp1 source package in Eoan: New Bug description: [Summary] If user un-plugs and then re-plugs the thunderbolt 3 cable of Dell WD19TB into the laptop during suspend state, peripheral devices on the docking station cannot be re-probed after the system resumes. [Steps to reproduce] 1. Please make sure that the WD19 (TBT 3 cable) connects to the laptop 2. Suspend the system 3. Un-plug the TBT 3 cable of WD19 docking station from laptop 4. Re-plug the TBT 3 cable of WD19 docking station into the laptop 5. Press the Enter key or power button to wake up the system 6. Connect an Ethernet cable to a Ethernet port of WD19 docking station 7. Check if the Ethernet interface is available and networking connection is up. [Expected result] The Ethernet interface can be detected [Actual result] The Ethernet cannot be detected To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809704] Re: efivarfs test in ubuntu_kernel_selftest failed on the second run
** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809704 Title: efivarfs test in ubuntu_kernel_selftest failed on the second run Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Committed Bug description: == SRU Justification == If you run the test selftest/efivarfs test suite twice, it will fail on the second run. This is because the test file created in the first run will obtain the immutable property, and it will make the second attempt failed with premission denied error. == Fix == * 1f0ea958 (selftests: efivarfs: return Kselftest Skip code for skipped tests) * dff6d2ae (selftests/efivarfs: clean up test files from test_create*()) This issue exists in X/B/D, fixed in newer releases. For Xenial it lacks the crucial commit which allows the selftest framework to handle KSFT_SKIP return code (3f4435b5), so the first commit has to be backported to keep using 0 as its return value. The second commit is a backport with fuzzy adjustments. For Bionic, the first commit is a clean cherry-pick, the second is a backport with fuzzy adjustments. For Disco, it just needs the second commit, which is also a backport with fuzzy adjustments as well. == Test == Patch tested against the affected kernels, and it works as expected. == Regression Potential == Low, changes limited to testing tools. == Original Bug Report == This seems to be an issue to the test case, if you run the test suite twice, it will fail on the second run. The first run will create the test file: $ ll /sys/firmware/efi/efivars/test_create_read-210be57c-9849-4fc7-a635-e6382d1aec27 -rw--- 1 root root 0 Dec 24 07:16 /sys/firmware/efi/efivars/test_create_read-210be57c-9849-4fc7-a635-e6382d1aec27 This is cause the open(O_WRONLY) test in test_create_read failed with premission denied on the second run. This issue can be reproduced with upstream kernel tree on Xenial as well. $ sudo make -C linux/tools/testing/selftests TARGETS=efivarfs run_tests make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' for TARGET in efivarfs; do \ make -C $TARGET; \ done; make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs' for TARGET in efivarfs; do \ make -C $TARGET run_tests; \ done; make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs' running test_create ./efivarfs.sh: line 48: /sys/firmware/efi/efivars/test_create-210be57c-9849-4fc7-a635-e6382d1aec27: Permission denied [PASS] running test_create_empty ./efivarfs.sh: line 65: /sys/firmware/efi/efivars/test_create_empty-210be57c-9849-4fc7-a635-e6382d1aec27: Permission denied [PASS] running test_create_read open(O_WRONLY): Permission denied [FAIL] running test_delete [PASS] running test_zero_size_delete [PASS] running test_open_unlink [PASS] running test_valid_filenames [PASS] running test_invalid_filenames [PASS] selftests: efivarfs.sh [FAIL] make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-141-generic 4.4.0-141.167 ProcVersionSignature: User Name 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 24 05:10 seq crw-rw 1 root audio 116, 33 Dec 24 05:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/
[Kernel-packages] [Bug 1858536] Re: bionic/linux-gcp: 5.0.0-1029.30~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1858539 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Holding before Promote to Proposed - phase-changed: Monday, 13. January 2020 05:46 UTC + phase: Ready for Promote to Proposed + phase-changed: Monday, 13. January 2020 09:36 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,signed:depwait + promote-to-proposed: Pending -- ready for review trackers: bionic/linux-gcp/gcp-kernel: bug 1858535 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1858536 Title: bionic/linux-gcp: 5.0.0-1029.30~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858539 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Promote to Proposed phase-changed: Monday, 13. January 2020 09:36 UTC reason: promote-to-proposed: Pending -- ready for review trackers: bionic/linux-gcp/gcp-kernel: bug 1858535 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859415] [NEW] "pstore: crypto_comp_decompress failed" found in Power9 boot dmesg with Eoan kernel
Public bug reported: Issue found on PowerPC P9 node "baltar" [4.775420] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) [5.547096] systemd[1]: Inserted module 'autofs4' [5.627326] pstore: crypto_comp_decompress failed, ret = -22! [5.664716] systemd[1]: systemd 242 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid) Looks like this is the fix: https://github.com/torvalds/linux/commit/89d328f637b9904b6d4c9af73c8a608b8dd4d6f8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: User Name 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic ppc64le .sys.firmware.opal.msglog: Error: [Errno 13] Permission denied: '/sys/firmware/opal/msglog' AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 13 06:51 seq crw-rw 1 root audio 116, 33 Jan 13 06:51 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jan 13 08:07:01 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc. Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro console=hvc0 ProcLoadAvg: 0.02 0.01 0.00 1/1401 5112 ProcLocks: 1: POSIX ADVISORY WRITE 3283 00:18:493 0 EOF 2: POSIX ADVISORY WRITE 3542 00:18:594 0 EOF 3: FLOCK ADVISORY WRITE 3534 00:18:578 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 5.3.0-26-generic (buildd@bos02-ppc64el-018) (gcc version 9.2.1 20191008 (User Name 9.2.1-9ubuntu2)) #28-User Name SMP Wed Dec 18 05:34:53 UTC 2019 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 40 cpu_coreson: Number of cores online = 39 cpu_smt: SMT=4 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Eoan) Importance: Undecided Status: Confirmed ** Tags: apport-bug eoan ppc64el uec-images ** Also affects: linux (Ubuntu Eoan) 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/1859415 Title: "pstore: crypto_comp_decompress failed" found in Power9 boot dmesg with Eoan kernel Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Bug description: Issue found on PowerPC P9 node "baltar" [4.775420] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) [5.547096] systemd[1]: Inserted module 'autofs4' [5.627326] pstore: crypto_comp_decompress failed, ret = -22! [5.664716] systemd[1]: systemd 242 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid) Looks like this is the fix: https://github.com/torvalds/linux/commit/89d328f637b9904b6d4c9af73c8a608b8dd4d6f8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: User Name 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic ppc64le .sys.firmware.opal.msglog: Error: [Errno 13] Permission denied: '/sys/firmware/opal/msglog' AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 13 06:51 seq crw-rw 1 root audio 116, 33 Jan 13 06:51 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jan 13 08:07:01 2020 IwConfig: Err
[Kernel-packages] [Bug 1859407] Re: peripheral devices on Dell WD19TB cannot be detected after suspend resume
PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1859407
SRU: https://lists.ubuntu.com/archives/kernel-team/2020-January/106824.html
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+ If user un-plugs and then re-plugs the thunderbolt 3 cable of Dell
+ WD19TB into the laptop during suspend state, peripheral devices on the
+ docking station cannot be re-probed after the system resumes.
+
+ [Fix]
+ Upstream commit 56b991849009f ("PM: sleep: Simplify suspend-to-idle control
+ flow") along with its dependencies are required to fix this issue:
+
+ * 56b991849009f PM: sleep: Simplify suspend-to-idle control flow
+ * 41275eb5c7181 ACPI: PM: Set s2idle_wakeup earlier and clear it later
+ * 9089f16e053af ACPI: EC: Return bool from acpi_ec_dispatch_gpe()
+ * 6921de898ba8f ACPICA: Return u32 from acpi_dispatch_gpe()
+ * 3a79bc63d9075 PCI: irq: Introduce rearm_wake_irq()
+
+ And 56b991849009f takes an additional fix as we've done for bug 1858424:
+
+ * 016b87ca5c8c6 ACPI: EC: Rework flushing of pending work
+
+ [Test Case]
+ 1. Please make sure that the WD19 (TBT 3 cable) connects to the laptop
+ 2. Suspend the system
+ 3. Un-plug the TBT 3 cable of WD19 docking station from laptop
+ 4. Re-plug the TBT 3 cable of WD19 docking station into the laptop
+ 5. Press the Enter key or power button to wake up the system
+ 6. Connect an Ethernet cable to a Ethernet port of WD19 docking station
+ 7. Check if the Ethernet interface is available and networking connection is
up.
+
+ [Regression Potential]
+ Medium. The first four patches should not affect original functionalities. The
+ last two mostly simplify the process and resolve a regression.
+
+ == original bug description ==
+
[Summary]
If user un-plugs and then re-plugs the thunderbolt 3 cable of Dell WD19TB
into the laptop during suspend state, peripheral devices on the docking station
cannot be re-probed after the system resumes.
[Steps to reproduce]
1. Please make sure that the WD19 (TBT 3 cable) connects to the laptop
2. Suspend the system
3. Un-plug the TBT 3 cable of WD19 docking station from laptop
4. Re-plug the TBT 3 cable of WD19 docking station into the laptop
5. Press the Enter key or power button to wake up the system
6. Connect an Ethernet cable to a Ethernet port of WD19 docking station
7. Check if the Ethernet interface is available and networking connection is
up.
[Expected result]
The Ethernet interface can be detected
[Actual result]
The Ethernet cannot be detected
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1859407
Title:
peripheral devices on Dell WD19TB cannot be detected after suspend
resume
Status in HWE Next:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-osp1 package in Ubuntu:
New
Status in linux source package in Bionic:
Won't Fix
Status in linux-oem-osp1 source package in Bionic:
In Progress
Status in linux source package in Disco:
Won't Fix
Status in linux-oem-osp1 source package in Disco:
Won't Fix
Status in linux source package in Eoan:
In Progress
Status in linux-oem-osp1 source package in Eoan:
New
Bug description:
[SRU Justification]
[Impact]
If user un-plugs and then re-plugs the thunderbolt 3 cable of Dell
WD19TB into the laptop during suspend state, peripheral devices on the
docking station cannot be re-probed after the system resumes.
[Fix]
Upstream commit 56b991849009f ("PM: sleep: Simplify suspend-to-idle control
flow") along with its dependencies are required to fix this issue:
* 56b991849009f PM: sleep: Simplify suspend-to-idle control flow
* 41275eb5c7181 ACPI: PM: Set s2idle_wakeup earlier and clear it later
* 9089f16e053af ACPI: EC: Return bool from acpi_ec_dispatch_gpe()
* 6921de898ba8f ACPICA: Return u32 from acpi_dispatch_gpe()
* 3a79bc63d9075 PCI: irq: Introduce rearm_wake_irq()
And 56b991849009f takes an additional fix as we've done for bug
1858424:
* 016b87ca5c8c6 ACPI: EC: Rework flushing of pending work
[Test Case]
1. Please make sure that the WD19 (TBT 3 cable) connects to the laptop
2. Suspend the system
3. Un-plug the TBT 3 cable of WD19 docking station from laptop
4. Re-plug the TBT 3 cable of WD19 docking station into the laptop
5. Press the Enter key or power button to wake up the system
6. Connect an Ethernet cable to a Ethernet port of WD19 docking station
7. Check if the Ethernet interface is available and networking connection is
up.
[Regression Potential]
Medium. The first four patches should not affect original functionalities. The
last two mostly simplify the process and resolve a regression.
== original bug description ==
[Summary]
If user un-plugs and then re-plugs the thunderbolt 3 cable of Dell WD19TB
into the laptop during suspend state, peripheral devices
[Kernel-packages] [Bug 1859415] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu Eoan) 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/1859415 Title: "pstore: crypto_comp_decompress failed" found in Power9 boot dmesg with Eoan kernel Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Bug description: Issue found on PowerPC P9 node "baltar" [4.775420] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) [5.547096] systemd[1]: Inserted module 'autofs4' [5.627326] pstore: crypto_comp_decompress failed, ret = -22! [5.664716] systemd[1]: systemd 242 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid) Looks like this is the fix: https://github.com/torvalds/linux/commit/89d328f637b9904b6d4c9af73c8a608b8dd4d6f8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: User Name 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic ppc64le .sys.firmware.opal.msglog: Error: [Errno 13] Permission denied: '/sys/firmware/opal/msglog' AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 13 06:51 seq crw-rw 1 root audio 116, 33 Jan 13 06:51 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jan 13 08:07:01 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc. Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro console=hvc0 ProcLoadAvg: 0.02 0.01 0.00 1/1401 5112 ProcLocks: 1: POSIX ADVISORY WRITE 3283 00:18:493 0 EOF 2: POSIX ADVISORY WRITE 3542 00:18:594 0 EOF 3: FLOCK ADVISORY WRITE 3534 00:18:578 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 5.3.0-26-generic (buildd@bos02-ppc64el-018) (gcc version 9.2.1 20191008 (User Name 9.2.1-9ubuntu2)) #28-User Name SMP Wed Dec 18 05:34:53 UTC 2019 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 40 cpu_coreson: Number of cores online = 39 cpu_smt: SMT=4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859415/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858536] Re: bionic/linux-gcp: 5.0.0-1029.30~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1858536 Title: bionic/linux-gcp: 5.0.0-1029.30~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858539 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Monday, 13. January 2020 10:36 UTC reason: promote-to-proposed: Ongoing -- review in progress trackers: bionic/linux-gcp/gcp-kernel: bug 1858535 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858536] Re: bionic/linux-gcp: 5.0.0-1029.30~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858539 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Ready for Promote to Proposed - phase-changed: Monday, 13. January 2020 09:36 UTC + phase: Promote to Proposed + phase-changed: Monday, 13. January 2020 10:36 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress trackers: bionic/linux-gcp/gcp-kernel: bug 1858535 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1858536 Title: bionic/linux-gcp: 5.0.0-1029.30~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858539 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Monday, 13. January 2020 10:36 UTC reason: promote-to-proposed: Ongoing -- review in progress trackers: bionic/linux-gcp/gcp-kernel: bug 1858535 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853375] Re: net selftest psock_fanout fails on xenial s390x due to incorrect queue lengths
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu) Assignee: Po-Hsu Lin (cypressyew) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853375 Title: net selftest psock_fanout fails on xenial s390x due to incorrect queue lengths Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Bug description: s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-xenial/xenial/s390x/l/linux/20191114_180123_738a0@/log.gz Here's the relevant excerpt: 17:34:26 DEBUG| [stdout] 17:34:26 DEBUG| [stdout] running psock_fanout test 17:34:26 DEBUG| [stdout] 17:34:26 ERROR| [stderr] test: control single socket 17:34:27 ERROR| [stderr] test: control multiple sockets 17:34:27 ERROR| [stderr] test: datapath 0x0 17:34:27 ERROR| [stderr] info: count=0,0, expect=0,0 17:34:27 ERROR| [stderr] info: count=20,0, expect=15,5 17:34:27 ERROR| [stderr] ERROR: incorrect queue lengths 17:34:27 ERROR| [stderr] info: count=20,0, expect=20,5 17:34:27 ERROR| [stderr] ERROR: incorrect queue lengths 17:34:27 ERROR| [stderr] info: trying alternate ports (4) 17:34:27 ERROR| [stderr] test: datapath 0x0 17:34:27 ERROR| [stderr] info: count=0,0, expect=0,0 17:34:27 ERROR| [stderr] info: count=20,0, expect=15,5 17:34:27 ERROR| [stderr] ERROR: incorrect queue lengths 17:34:27 ERROR| [stderr] info: count=20,0, expect=20,5 17:34:27 ERROR| [stderr] ERROR: incorrect queue lengths 17:34:27 ERROR| [stderr] info: trying alternate ports (3) 17:34:27 ERROR| [stderr] test: datapath 0x0 17:34:27 ERROR| [stderr] info: count=0,0, expect=0,0 17:34:27 ERROR| [stderr] info: count=20,0, expect=15,5 17:34:27 ERROR| [stderr] ERROR: incorrect queue lengths 17:34:27 ERROR| [stderr] info: count=20,0, expect=20,5 17:34:27 ERROR| [stderr] ERROR: incorrect queue lengths 17:34:27 ERROR| [stderr] info: trying alternate ports (2) 17:34:27 ERROR| [stderr] test: datapath 0x0 17:34:27 ERROR| [stderr] info: count=0,0, expect=0,0 17:34:27 ERROR| [stderr] info: count=20,0, expect=15,5 17:34:27 ERROR| [stderr] ERROR: incorrect queue lengths 17:34:27 ERROR| [stderr] info: count=20,0, expect=20,5 17:34:27 ERROR| [stderr] ERROR: incorrect queue lengths 17:34:27 ERROR| [stderr] info: trying alternate ports (1) 17:34:27 ERROR| [stderr] test: datapath 0x0 17:34:28 ERROR| [stderr] info: count=0,0, expect=0,0 17:34:28 ERROR| [stderr] info: count=20,0, expect=15,5 17:34:28 ERROR| [stderr] ERROR: incorrect queue lengths 17:34:28 ERROR| [stderr] info: count=20,0, expect=20,5 17:34:28 ERROR| [stderr] ERROR: incorrect queue lengths 17:34:28 ERROR| [stderr] info: trying alternate ports (0) 17:34:28 ERROR| [stderr] test: datapath 0x0 17:34:28 ERROR| [stderr] info: count=0,0, expect=0,0 17:34:28 ERROR| [stderr] info: count=20,0, expect=15,5 17:34:28 ERROR| [stderr] ERROR: incorrect queue lengths 17:34:28 ERROR| [stderr] info: count=20,0, expect=20,5 17:34:28 ERROR| [stderr] ERROR: incorrect queue lengths 17:34:28 ERROR| [stderr] test: datapath 0x1000 17:34:28 ERROR| [stderr] info: count=0,0, expect=0,0 17:34:28 ERROR| [stderr] info: count=20,0, expect=15,5 17:34:28 ERROR| [stderr] ERROR: incorrect queue lengths 17:34:28 ERROR| [stderr] info: count=20,0, expect=15,5 17:34:28 ERROR| [stderr] ERROR: incorrect queue lengths 17:34:28 ERROR| [stderr] info: count=20,0, expect=20,5 17:34:28 ERROR| [stderr] ERROR: incorrect queue lengths 17:34:28 ERROR| [stderr] info: trying alternate ports (0) 17:34:28 ERROR| [stderr] test: datapath 0x0 17:34:28 ERROR| [stderr] info: count=0,0, expect=0,0 17:34:28 ERROR| [stderr] info: count=20,0, expect=15,5 17:34:28 ERROR| [stderr] ERROR: incorrect queue lengths 17:34:28 ERROR| [stderr] info: count=20,0, expect=20,5 17:34:28 ERROR| [stderr] ERROR: incorrect queue lengths 17:34:28 ERROR| [stderr] test: datapath 0x1000 17:34:28 ERROR| [stderr] info: count=0,0, expect=0,0 17:34:28 ERROR| [stderr] info: count=20,0, expect=15,5 17:34:28 ERROR| [stderr] ERROR: incorrect queue lengths 17:34:28 ERROR| [stderr] info: count=20,15, expect=20,15 17:34:28 ERROR| [stderr] test: datapath 0x1 17:34:28 ERROR| [stderr] info: count=0,0, expect=0,0 17:34:28 ERROR| [stderr] info: count=10,10, expect=10,10 17:34:28 ERROR| [stderr] info: count=18,17, expect=18,17 17:34:28 ERROR| [stderr] test: datapath 0x3 17:34:28 ERROR| [stderr] info: count=0,0, expect=0,0 17:34:28 ERROR| [stderr] info: count=15,5, expect=15,5 17:34:28 ERROR| [stderr] info: count=20,15, expect=20,15 17:34:28 ERROR| [stderr] test: datapath 0x6 1
[Kernel-packages] [Bug 1859429] [NEW] Boot took much longer with repeated error message PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Public bug reported: Hi, I saw this message in several other bugs but I am using the newest kernel. Right after upgrade the kernel the boot took several minutes and a message was being repeated several times in screen: [ 340.489762] pcieport :00:1c.5: AER: Corrected error received: :00:1c.5 [ 340.489775] pcieport :00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [ 340.489780] pcieport :00:1c.5: AER: device [8086:9d15] error status/mask=1000/2000 [ 340.489784] pcieport :00:1c.5: AER:[12] Timeout The notebook didn't had an issue so far and uptime is 35 minutes. I don't see any issue on performance as of now. All partitions are present. Before this event of slow down in boot (and notebook frozen for a few seconds duing boot) I was having this same message once or twice and then it was normal boot. root@dell-ubuntu:~# cat /proc/version Linux version 5.3.0-26-generic (buildd@lgw01-amd64-013) (gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)) #28-Ubuntu SMP Wed Dec 18 05:37:46 UTC 2019 root@dell-ubuntu:~# cat /proc/version_signature Ubuntu 5.3.0-26.28-generic 5.3.13 root@dell-ubuntu:/home/billmask/bug_report/PCIe# lsb_release -rd Description:Ubuntu 19.10 Release:19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm3886 F pulseaudio billmask 4450 F pulseaudio Date: Mon Jan 13 08:00:06 2020 InstallationDate: Installed on 2019-07-28 (169 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 7572 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-26-generic root=/dev/mapper/vg_root-lv_root 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: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-25 (80 days ago) dmi.bios.date: 05/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 082HPJ dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd05/31/2019:svnDellInc.:pnInspiron7572:pvr:rvnDellInc.:rn082HPJ:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7572 dmi.product.sku: 0829 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Dmesg output" https://bugs.launchpad.net/bugs/1859429/+attachment/5319749/+files/dmesg_output.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859429 Title: Boot took much longer with repeated error message PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Status in linux package in Ubuntu: New Bug description: Hi, I saw this message in several other bugs but I am using the newest kernel. Right after upgrade the kernel the boot took several minutes and a message was being repeated several times in screen: [ 340.489762] pcieport :00:1c.5: AER: Corrected error received: :00:1c.5 [ 340.489775] pcieport :00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [ 340.489780] pcieport :00:1c.5: AER: device [8086:9d15] error status/mask=1000/2000 [ 340.489784] pcieport :00:1c.5: AER:[12] Timeout The notebook didn't had an issue so far and uptime is 35 minutes. I don't see any issue on performance as of now. All partitions are present. Before this event of slow down in boot (and notebook frozen for a few seconds duing boot) I was having this same message once or twice and then it was normal boot. root@dell-ubuntu:~# cat /proc/version Linux version 5.3.0-26-generic (buildd@lgw01-amd64-013) (gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)) #28-Ubuntu SMP Wed Dec 18 05:37:46 UTC 2019 root@dell-ubuntu:~# cat /proc/version_signature Ubuntu 5.3.0-26.28-generic 5.3.13 root@dell-ubuntu:/home/billmask/bug_report/PCIe# lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Arch
[Kernel-packages] [Bug 1859429] Re: Boot took much longer with repeated error message PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Adding: lspci -vnvn ** Attachment added: "lspci -vnvn" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859429/+attachment/5319765/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859429 Title: Boot took much longer with repeated error message PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Status in linux package in Ubuntu: New Bug description: Hi, I saw this message in several other bugs but I am using the newest kernel. Right after upgrade the kernel the boot took several minutes and a message was being repeated several times in screen: [ 340.489762] pcieport :00:1c.5: AER: Corrected error received: :00:1c.5 [ 340.489775] pcieport :00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [ 340.489780] pcieport :00:1c.5: AER: device [8086:9d15] error status/mask=1000/2000 [ 340.489784] pcieport :00:1c.5: AER:[12] Timeout The notebook didn't had an issue so far and uptime is 35 minutes. I don't see any issue on performance as of now. All partitions are present. Before this event of slow down in boot (and notebook frozen for a few seconds duing boot) I was having this same message once or twice and then it was normal boot. root@dell-ubuntu:~# cat /proc/version Linux version 5.3.0-26-generic (buildd@lgw01-amd64-013) (gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)) #28-Ubuntu SMP Wed Dec 18 05:37:46 UTC 2019 root@dell-ubuntu:~# cat /proc/version_signature Ubuntu 5.3.0-26.28-generic 5.3.13 root@dell-ubuntu:/home/billmask/bug_report/PCIe# lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm3886 F pulseaudio billmask 4450 F pulseaudio Date: Mon Jan 13 08:00:06 2020 InstallationDate: Installed on 2019-07-28 (169 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 7572 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-26-generic root=/dev/mapper/vg_root-lv_root 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: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-25 (80 days ago) dmi.bios.date: 05/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 082HPJ dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd05/31/2019:svnDellInc.:pnInspiron7572:pvr:rvnDellInc.:rn082HPJ:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7572 dmi.product.sku: 0829 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859429/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852077] Re: Backport: bonding: fix state transition issue in link monitoring
Hello Fabio,
yes you're right!
The patch has been applied via the stable update process. So my patchset
was superseded.
B/D - https://lists.ubuntu.com/archives/kernel-team/2019-November/105911.html
E/F - https://lists.ubuntu.com/archives/kernel-team/2019-December/106055.html
I will mark this one as Fix-released.
Thanks for the follow-up.
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu Disco)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu Eoan)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1852077
Title:
Backport: bonding: fix state transition issue in link monitoring
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Disco:
Fix Released
Status in linux source package in Eoan:
Fix Released
Status in linux source package in Focal:
Fix Released
Bug description:
== Justification ==
From the well explained commit message:
Since de77ecd4ef02 ("bonding: improve link-status update in
mii-monitoring"), the bonding driver has utilized two separate variables
to indicate the next link state a particular slave should transition to.
Each is used to communicate to a different portion of the link state
change commit logic; one to the bond_miimon_commit function itself, and
another to the state transition logic.
Unfortunately, the two variables can become unsynchronized,
resulting in incorrect link state transitions within bonding. This can
cause slaves to become stuck in an incorrect link state until a
subsequent carrier state transition.
The issue occurs when a special case in bond_slave_netdev_event
sets slave->link directly to BOND_LINK_FAIL. On the next pass through
bond_miimon_inspect after the slave goes carrier up, the BOND_LINK_FAIL
case will set the proposed next state (link_new_state) to BOND_LINK_UP,
but the new_link to BOND_LINK_DOWN. The setting of the final link state
from new_link comes after that from link_new_state, and so the slave
will end up incorrectly in _DOWN state.
Resolve this by combining the two variables into one.
== Fixes ==
* 1899bb32 (bonding: fix state transition issue in link monitoring)
This patch can be cherry-picked into E/F
For older releases like B/D, it will needs to be backported as they are
missing the slave_err() printk marco added in 5237ff79 (bonding: add
slave_foo printk macros) as well as the commit to replace netdev_err()
with slave_err() in e2a7420d (bonding/main: convert to using slave
printk macros)
For Xenial, the commit that causes this issue, de77ecd4, does not
exist.
== Test ==
Test kernels can be found here:
https://people.canonical.com/~phlin/kernel/lp-1852077-bonding/
The X-hwe and Disco kernel were tested by the bug reporter, Aleksei,
the patched kernel works as expected.
== Regression Potential ==
Low.
This patch just unify the variable used in link state change commit
logic to prevent the occurrence of an incorrect state. And the changes
are limited to the bonding driver itself.
(Although the include/net/bonding.h will be used in other drivers, but
the changes to that file is only affecting this bond_main.c driver)
== Original Bug Report ==
There's an issue with bonding driver in the current ubuntu kernels.
Sometimes one link stuck in a weird state.
It was fixed with patch https://www.spinics.net/lists/netdev/msg609506.html
in upstream.
Commit 1899bb325149e481de31a4f32b59ea6f24e176ea.
We see this bug with linux 4.15 (ubuntu xenial, hwe kernel), but it
should be reproducible with other current kernel versions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852077/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859287] Re: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04
Please have mainline kernel build a try: https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.5-rc6/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859287 Title: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi there, Laptop: Dell XPS 13 7390 2-in-1 Built-in wireless: Killer Wi-Fi 6 AX1650i 160MHz iwlwifi worked fine with 19.10 but breaks when upgrading to 20.04. Firmware crashes after loading and interface doesn't show up. This is with: linux-image-5.4.0-9-generic 5.4.0-9.12 linux-firmware 1.184 I've noticed the driver was trying to load a more recent firmware: Direct firmware load for iwlwifi-Qu-b0-hr-b0-50.ucode failed with error -2 I've downloaded this file from upstream iwlwifi firmware git and tried unloading/reloading iwlwifi. Driver crashes as well, but with a different error code. Best, - LM ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lool 1579 F pulseaudio /dev/snd/pcmC0D0p: lool 1579 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jan 11 15:02:08 2020 InstallationDate: Installed on 2019-12-02 (39 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 2-in-1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic root=UUID=854f3bc2-da3a-4a3c-82a1-6b04a932bb29 ro pcie_aspm=off plymouth.force-scale=3 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-11 (0 days ago) dmi.bios.date: 11/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 06CDVY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd11/10/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859429] Re: Boot took much longer with repeated error message PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
AER, advanced error reporting[1], is generated by hardware and corrected AERs usually doesn't mean any harm because they're just notifications to upper OS that some minor errors like CRC has been corrected automatically by hardware. There is little you can do but to turn off such reporting by append kernel boot parameter "noaer". [1]: https://www.kernel.org/doc/html/latest/PCI/pcieaer-howto.html ** Changed in: linux (Ubuntu) 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/1859429 Title: Boot took much longer with repeated error message PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Status in linux package in Ubuntu: Invalid Bug description: Hi, I saw this message in several other bugs but I am using the newest kernel. Right after upgrade the kernel the boot took several minutes and a message was being repeated several times in screen: [ 340.489762] pcieport :00:1c.5: AER: Corrected error received: :00:1c.5 [ 340.489775] pcieport :00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [ 340.489780] pcieport :00:1c.5: AER: device [8086:9d15] error status/mask=1000/2000 [ 340.489784] pcieport :00:1c.5: AER:[12] Timeout The notebook didn't had an issue so far and uptime is 35 minutes. I don't see any issue on performance as of now. All partitions are present. Before this event of slow down in boot (and notebook frozen for a few seconds duing boot) I was having this same message once or twice and then it was normal boot. root@dell-ubuntu:~# cat /proc/version Linux version 5.3.0-26-generic (buildd@lgw01-amd64-013) (gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)) #28-Ubuntu SMP Wed Dec 18 05:37:46 UTC 2019 root@dell-ubuntu:~# cat /proc/version_signature Ubuntu 5.3.0-26.28-generic 5.3.13 root@dell-ubuntu:/home/billmask/bug_report/PCIe# lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm3886 F pulseaudio billmask 4450 F pulseaudio Date: Mon Jan 13 08:00:06 2020 InstallationDate: Installed on 2019-07-28 (169 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 7572 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-26-generic root=/dev/mapper/vg_root-lv_root 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: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-25 (80 days ago) dmi.bios.date: 05/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 082HPJ dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd05/31/2019:svnDellInc.:pnInspiron7572:pvr:rvnDellInc.:rn082HPJ:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7572 dmi.product.sku: 0829 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859429/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858536] Re: bionic/linux-gcp: 5.0.0-1029.30~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858539 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Monday, 13. January 2020 10:36 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait trackers: bionic/linux-gcp/gcp-kernel: bug 1858535 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1858536 Title: bionic/linux-gcp: 5.0.0-1029.30~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858539 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Monday, 13. January 2020 10:36 UTC reason: promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait trackers: bionic/linux-gcp/gcp-kernel: bug 1858535 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858588] Re: xenial/linux-snapdragon: 4.4.0-1132.140 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858594 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Ready for Promote to Proposed phase-changed: Sunday, 12. January 2020 23:17 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- ready for review trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1858587 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1858588 Title: xenial/linux-snapdragon: 4.4.0-1132.140 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858594 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Ready for Promote to Proposed phase-changed: Sunday, 12. January 2020 23:17 UTC reason: promote-to-proposed: Stalled -- ready for review trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1858587 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809704] Re: efivarfs test in ubuntu_kernel_selftest failed on the second run
Verified with Disco in proposed. ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809704 Title: efivarfs test in ubuntu_kernel_selftest failed on the second run Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Committed Bug description: == SRU Justification == If you run the test selftest/efivarfs test suite twice, it will fail on the second run. This is because the test file created in the first run will obtain the immutable property, and it will make the second attempt failed with premission denied error. == Fix == * 1f0ea958 (selftests: efivarfs: return Kselftest Skip code for skipped tests) * dff6d2ae (selftests/efivarfs: clean up test files from test_create*()) This issue exists in X/B/D, fixed in newer releases. For Xenial it lacks the crucial commit which allows the selftest framework to handle KSFT_SKIP return code (3f4435b5), so the first commit has to be backported to keep using 0 as its return value. The second commit is a backport with fuzzy adjustments. For Bionic, the first commit is a clean cherry-pick, the second is a backport with fuzzy adjustments. For Disco, it just needs the second commit, which is also a backport with fuzzy adjustments as well. == Test == Patch tested against the affected kernels, and it works as expected. == Regression Potential == Low, changes limited to testing tools. == Original Bug Report == This seems to be an issue to the test case, if you run the test suite twice, it will fail on the second run. The first run will create the test file: $ ll /sys/firmware/efi/efivars/test_create_read-210be57c-9849-4fc7-a635-e6382d1aec27 -rw--- 1 root root 0 Dec 24 07:16 /sys/firmware/efi/efivars/test_create_read-210be57c-9849-4fc7-a635-e6382d1aec27 This is cause the open(O_WRONLY) test in test_create_read failed with premission denied on the second run. This issue can be reproduced with upstream kernel tree on Xenial as well. $ sudo make -C linux/tools/testing/selftests TARGETS=efivarfs run_tests make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' for TARGET in efivarfs; do \ make -C $TARGET; \ done; make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs' for TARGET in efivarfs; do \ make -C $TARGET run_tests; \ done; make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs' running test_create ./efivarfs.sh: line 48: /sys/firmware/efi/efivars/test_create-210be57c-9849-4fc7-a635-e6382d1aec27: Permission denied [PASS] running test_create_empty ./efivarfs.sh: line 65: /sys/firmware/efi/efivars/test_create_empty-210be57c-9849-4fc7-a635-e6382d1aec27: Permission denied [PASS] running test_create_read open(O_WRONLY): Permission denied [FAIL] running test_delete [PASS] running test_zero_size_delete [PASS] running test_open_unlink [PASS] running test_valid_filenames [PASS] running test_invalid_filenames [PASS] selftests: efivarfs.sh [FAIL] make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-141-generic 4.4.0-141.167 ProcVersionSignature: User Name 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 24 05:10 seq crw-rw 1 root audio 116, 33 Dec 24 05:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse:
[Kernel-packages] [Bug 1852122] Re: ocfs2-tools is causing kernel panics in Ubuntu Focal (Ubuntu-5.4.0-9.12)
Thanks for checking this Andreas! Looks like upstream got a fix for the issue and Debian has confirmed it worked. With that, I'll check if it fixes the issue indeed and suggest the SRU to the kernel-team so we can unblock ocfs2-tools. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852122 Title: ocfs2-tools is causing kernel panics in Ubuntu Focal (Ubuntu-5.4.0-9.12) Status in OCFS2 Tools: Fix Released Status in linux package in Ubuntu: In Progress Status in ocfs2-tools package in Ubuntu: In Progress Status in linux source package in Eoan: In Progress Status in ocfs2-tools source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in ocfs2-tools source package in Focal: In Progress Bug description: I noticed the tests for ocfs2-tools/1.8.6-1ubuntu1 were constantly retrying themselves. It's a feature we have so that transient / occasional failures are auto-retried, but it's misfiring here because we're not detecting that it's a consistent failure. That particular bug is fixed, but it means that ocfs2-tools is failing on ppc64el. Here's the important part of the log, full output attached. [ 85.605738] BUG: Unable to handle kernel data access at 0x01744098 [ 85.605850] Faulting instruction address: 0xc0e81168 [ 85.605901] Oops: Kernel access of bad area, sig: 11 [#1] [ 85.605970] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries [ 85.606029] Modules linked in: ocfs2 quota_tree ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue iptable_mangle xt_TCPMSS xt_tcpudp bpfilter dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vmx_crypto crct10dif_vpmsum sch_fq_codel ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c crc32c_vpmsum virtio_net virtio_blk net_failover failover [ 85.606291] CPU: 0 PID: 1 Comm: systemd Not tainted 5.3.0-18-generic #19-Ubuntu [ 85.606350] NIP: c0e81168 LR: c054f240 CTR: [ 85.606410] REGS: c0005a3e3700 TRAP: 0300 Not tainted (5.3.0-18-generic) [ 85.606469] MSR: 80009033 CR: 28024448 XER: [ 85.606531] CFAR: 701f9806f638 DAR: 01744098 DSISR: 4000 IRQMASK: 0 [ 85.606531] GPR00: 7374 c0005a3e3990 c19c9100 c0004fe462a8 [ 85.606531] GPR04: c0005856d840 000e 74656772 c0004fe4a568 [ 85.606531] GPR08: c00058568004 01744090 [ 85.606531] GPR12: e8086002 c1d6 7fffddd522d0 [ 85.606531] GPR16: c755e07c [ 85.606531] GPR20: c000598caca8 c0005a3e3a58 c00058292f00 [ 85.606531] GPR24: c0eea710 c0005856d840 c755e074 [ 85.606531] GPR28:
[Kernel-packages] [Bug 1859429] Re: Boot took much longer with repeated error message PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
I appreciate the quick answer and will investigate more the boot time. It might be something hidden. Thank you very much. This can be closed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859429 Title: Boot took much longer with repeated error message PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Status in linux package in Ubuntu: Invalid Bug description: Hi, I saw this message in several other bugs but I am using the newest kernel. Right after upgrade the kernel the boot took several minutes and a message was being repeated several times in screen: [ 340.489762] pcieport :00:1c.5: AER: Corrected error received: :00:1c.5 [ 340.489775] pcieport :00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [ 340.489780] pcieport :00:1c.5: AER: device [8086:9d15] error status/mask=1000/2000 [ 340.489784] pcieport :00:1c.5: AER:[12] Timeout The notebook didn't had an issue so far and uptime is 35 minutes. I don't see any issue on performance as of now. All partitions are present. Before this event of slow down in boot (and notebook frozen for a few seconds duing boot) I was having this same message once or twice and then it was normal boot. root@dell-ubuntu:~# cat /proc/version Linux version 5.3.0-26-generic (buildd@lgw01-amd64-013) (gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)) #28-Ubuntu SMP Wed Dec 18 05:37:46 UTC 2019 root@dell-ubuntu:~# cat /proc/version_signature Ubuntu 5.3.0-26.28-generic 5.3.13 root@dell-ubuntu:/home/billmask/bug_report/PCIe# lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm3886 F pulseaudio billmask 4450 F pulseaudio Date: Mon Jan 13 08:00:06 2020 InstallationDate: Installed on 2019-07-28 (169 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 7572 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-26-generic root=/dev/mapper/vg_root-lv_root 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: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-25 (80 days ago) dmi.bios.date: 05/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 082HPJ dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd05/31/2019:svnDellInc.:pnInspiron7572:pvr:rvnDellInc.:rn082HPJ:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7572 dmi.product.sku: 0829 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859429/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855668] Re: lockdown on power
Changing back to Triaged - after test done and info provided my Daniel. Btw. in between kernel 5.4 landed in the focal (20.04) release pocket as well: linux-generic | 5.4.0.9.11 | focal | ppc64el So any lock-down tests can now be done based on the normal kernel from focal's release pocket. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855668 Title: lockdown on power Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Michael Ranweiler - 2019-11-11 08:50:51 == For 20.04 testing/inclusion. The ubuntu kernel team has a ppa here for testing: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable Test results will follow... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1855668/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858531] Re: disco/linux-aws: 5.0.0-1024.27 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1858531 Title: disco/linux-aws: 5.0.0-1024.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-aws meta: linux-meta-aws phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:11 UTC reason: promote-to-proposed: Stalled -- review in progress trackers: bionic/linux-aws-5.0: bug 1858530 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858531] Re: disco/linux-aws: 5.0.0-1024.27 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-aws meta: linux-meta-aws - phase: Ready for Promote to Proposed - phase-changed: Monday, 13. January 2020 05:36 UTC + phase: Promote to Proposed + phase-changed: Monday, 13. January 2020 12:11 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- review in progress trackers: bionic/linux-aws-5.0: bug 1858530 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1858531 Title: disco/linux-aws: 5.0.0-1024.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-aws meta: linux-meta-aws phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:11 UTC reason: promote-to-proposed: Stalled -- review in progress trackers: bionic/linux-aws-5.0: bug 1858530 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858539] Re: disco/linux-gcp: 5.0.0-1029.30 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1858539 Title: disco/linux-gcp: 5.0.0-1029.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:21 UTC reason: promote-to-proposed: Stalled -- review in progress trackers: bionic/linux-gcp: bug 1858536 bionic/linux-gke-5.0: bug 1858538 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852122] Re: ocfs2-tools is causing kernel panics in Ubuntu Focal (Ubuntu-5.4.0-9.12)
awesome, thanks for following up! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852122 Title: ocfs2-tools is causing kernel panics in Ubuntu Focal (Ubuntu-5.4.0-9.12) Status in OCFS2 Tools: Fix Released Status in linux package in Ubuntu: In Progress Status in ocfs2-tools package in Ubuntu: In Progress Status in linux source package in Eoan: In Progress Status in ocfs2-tools source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in ocfs2-tools source package in Focal: In Progress Bug description: I noticed the tests for ocfs2-tools/1.8.6-1ubuntu1 were constantly retrying themselves. It's a feature we have so that transient / occasional failures are auto-retried, but it's misfiring here because we're not detecting that it's a consistent failure. That particular bug is fixed, but it means that ocfs2-tools is failing on ppc64el. Here's the important part of the log, full output attached. [ 85.605738] BUG: Unable to handle kernel data access at 0x01744098 [ 85.605850] Faulting instruction address: 0xc0e81168 [ 85.605901] Oops: Kernel access of bad area, sig: 11 [#1] [ 85.605970] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries [ 85.606029] Modules linked in: ocfs2 quota_tree ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue iptable_mangle xt_TCPMSS xt_tcpudp bpfilter dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vmx_crypto crct10dif_vpmsum sch_fq_codel ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c crc32c_vpmsum virtio_net virtio_blk net_failover failover [ 85.606291] CPU: 0 PID: 1 Comm: systemd Not tainted 5.3.0-18-generic #19-Ubuntu [ 85.606350] NIP: c0e81168 LR: c054f240 CTR: [ 85.606410] REGS: c0005a3e3700 TRAP: 0300 Not tainted (5.3.0-18-generic) [ 85.606469] MSR: 80009033 CR: 28024448 XER: [ 85.606531] CFAR: 701f9806f638 DAR: 01744098 DSISR: 4000 IRQMASK: 0 [ 85.606531] GPR00: 7374 c0005a3e3990 c19c9100 c0004fe462a8 [ 85.606531] GPR04: c0005856d840 000e 74656772 c0004fe4a568 [ 85.606531] GPR08: c00058568004 01744090 [ 85.606531] GPR12: e8086002 c1d6 7fffddd522d0 [ 85.606531] GPR16: c755e07c [ 85.606531] GPR20: c000598caca8 c0005a3e3a58 c00058292f00 [ 85.606531] GPR24: c0eea710 c0005856d840 c755e074 [ 85.606531] GPR28: 6518907d c0005a3e3a68 c0004fe4b160 027c47b6 [ 85.607079] NIP
[Kernel-packages] [Bug 1858531] Re: disco/linux-aws: 5.0.0-1024.27 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-aws meta: linux-meta-aws phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:11 UTC reason: - promote-to-proposed: Stalled -- review in progress + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-aws-5.0: bug 1858530 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1858531 Title: disco/linux-aws: 5.0.0-1024.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-aws meta: linux-meta-aws phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:11 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-aws-5.0: bug 1858530 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858543] Re: disco/linux-oracle: 5.0.0-1010.15 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1858543 Title: disco/linux-oracle: 5.0.0-1010.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:26 UTC reason: promote-to-proposed: Stalled -- review in progress trackers: bionic/linux-oracle-5.0: bug 1858542 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858539] Re: disco/linux-gcp: 5.0.0-1029.30 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Ready for Promote to Proposed - phase-changed: Monday, 13. January 2020 03:32 UTC + phase: Promote to Proposed + phase-changed: Monday, 13. January 2020 12:21 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- review in progress trackers: bionic/linux-gcp: bug 1858536 bionic/linux-gke-5.0: bug 1858538 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1858539 Title: disco/linux-gcp: 5.0.0-1029.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:21 UTC reason: promote-to-proposed: Stalled -- review in progress trackers: bionic/linux-gcp: bug 1858536 bionic/linux-gke-5.0: bug 1858538 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858543] Re: disco/linux-oracle: 5.0.0-1010.15 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Ready for Promote to Proposed - phase-changed: Monday, 13. January 2020 03:32 UTC + phase: Promote to Proposed + phase-changed: Monday, 13. January 2020 12:26 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- review in progress trackers: bionic/linux-oracle-5.0: bug 1858542 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1858543 Title: disco/linux-oracle: 5.0.0-1010.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:26 UTC reason: promote-to-proposed: Stalled -- review in progress trackers: bionic/linux-oracle-5.0: bug 1858542 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858539] Re: disco/linux-gcp: 5.0.0-1029.30 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:21 UTC reason: - promote-to-proposed: Stalled -- review in progress + promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait trackers: bionic/linux-gcp: bug 1858536 bionic/linux-gke-5.0: bug 1858538 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1858539 Title: disco/linux-gcp: 5.0.0-1029.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:21 UTC reason: promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait trackers: bionic/linux-gcp: bug 1858536 bionic/linux-gke-5.0: bug 1858538 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858544] Re: disco/linux-snapdragon: 5.0.0-1029.31 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1858544 Title: disco/linux-snapdragon: 5.0.0-1029.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:51 UTC reason: promote-to-proposed: Stalled -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858544/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858586] Re: xenial/linux-raspi2: 4.4.0-1128.137 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- 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/1858586 Title: xenial/linux-raspi2: 4.4.0-1128.137 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858594 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:56 UTC reason: promote-to-proposed: Stalled -- review in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1858585 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858543] Re: disco/linux-oracle: 5.0.0-1010.15 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:26 UTC reason: - promote-to-proposed: Stalled -- review in progress + promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait trackers: bionic/linux-oracle-5.0: bug 1858542 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1858543 Title: disco/linux-oracle: 5.0.0-1010.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:26 UTC reason: promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait trackers: bionic/linux-oracle-5.0: bug 1858542 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858544] Re: disco/linux-snapdragon: 5.0.0-1029.31 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-snapdragon meta: linux-meta-snapdragon - phase: Ready for Promote to Proposed - phase-changed: Monday, 13. January 2020 03:32 UTC + phase: Promote to Proposed + phase-changed: Monday, 13. January 2020 12:51 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- review in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1858544 Title: disco/linux-snapdragon: 5.0.0-1029.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:51 UTC reason: promote-to-proposed: Stalled -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858544/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858588] Re: xenial/linux-snapdragon: 4.4.0-1132.140 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1858588 Title: xenial/linux-snapdragon: 4.4.0-1132.140 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858594 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Promote to Proposed phase-changed: Monday, 13. January 2020 13:01 UTC reason: promote-to-proposed: Stalled -- review in progress trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1858587 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858586] Re: xenial/linux-raspi2: 4.4.0-1128.137 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858594 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Ready for Promote to Proposed - phase-changed: Monday, 13. January 2020 03:41 UTC + phase: Promote to Proposed + phase-changed: Monday, 13. January 2020 12:56 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- review in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1858585 variant: debs -- 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/1858586 Title: xenial/linux-raspi2: 4.4.0-1128.137 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858594 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:56 UTC reason: promote-to-proposed: Stalled -- review in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1858585 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858588] Re: xenial/linux-snapdragon: 4.4.0-1132.140 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858594 packages: main: linux-snapdragon meta: linux-meta-snapdragon - phase: Ready for Promote to Proposed - phase-changed: Sunday, 12. January 2020 23:17 UTC + phase: Promote to Proposed + phase-changed: Monday, 13. January 2020 13:01 UTC reason: - promote-to-proposed: Stalled -- ready for review + promote-to-proposed: Stalled -- review in progress trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1858587 variant: debs ** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858594 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Promote to Proposed phase-changed: Monday, 13. January 2020 13:01 UTC reason: - promote-to-proposed: Stalled -- review in progress + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1858587 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1858588 Title: xenial/linux-snapdragon: 4.4.0-1132.140 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858594 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Promote to Proposed phase-changed: Monday, 13. January 2020 13:01 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1858587 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858544] Re: disco/linux-snapdragon: 5.0.0-1029.31 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:51 UTC reason: - promote-to-proposed: Stalled -- review in progress + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1858544 Title: disco/linux-snapdragon: 5.0.0-1029.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:51 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858544/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858586] Re: xenial/linux-raspi2: 4.4.0-1128.137 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858594 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:56 UTC reason: - promote-to-proposed: Stalled -- review in progress + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: xenial/linux-raspi2/pi2-kernel: bug 1858585 variant: debs -- 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/1858586 Title: xenial/linux-raspi2: 4.4.0-1128.137 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858594 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:56 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: xenial/linux-raspi2/pi2-kernel: bug 1858585 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858543] Re: disco/linux-oracle: 5.0.0-1010.15 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:26 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait + promote-to-proposed: Pending -- package copied to Proposed signed:queued trackers: bionic/linux-oracle-5.0: bug 1858542 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1858543 Title: disco/linux-oracle: 5.0.0-1010.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:26 UTC reason: promote-to-proposed: Pending -- package copied to Proposed signed:queued trackers: bionic/linux-oracle-5.0: bug 1858542 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858539] Re: disco/linux-gcp: 5.0.0-1029.30 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:21 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait + promote-to-proposed: Pending -- package copied to Proposed signed:queued trackers: bionic/linux-gcp: bug 1858536 bionic/linux-gke-5.0: bug 1858538 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1858539 Title: disco/linux-gcp: 5.0.0-1029.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:21 UTC reason: promote-to-proposed: Pending -- package copied to Proposed signed:queued trackers: bionic/linux-gcp: bug 1858536 bionic/linux-gke-5.0: bug 1858538 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858536] Re: bionic/linux-gcp: 5.0.0-1029.30~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858539 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Monday, 13. January 2020 10:36 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait + promote-to-proposed: Pending -- package copied to Proposed signed:queued trackers: bionic/linux-gcp/gcp-kernel: bug 1858535 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1858536 Title: bionic/linux-gcp: 5.0.0-1029.30~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858539 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Monday, 13. January 2020 10:36 UTC reason: promote-to-proposed: Pending -- package copied to Proposed signed:queued trackers: bionic/linux-gcp/gcp-kernel: bug 1858535 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859223] Re: Firmware missing for Thinkpad X-series Bluetooth adapters, leads to headset HSP/HFP profiles not working
Those files are from upstream linux-firmware and are covered by a couple of different licenses, depending on the file. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/LICENCE.broadcom_bcm43xx https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/LICENCE.cypress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1859223 Title: Firmware missing for Thinkpad X-series Bluetooth adapters, leads to headset HSP/HFP profiles not working Status in linux-firmware package in Ubuntu: New Bug description: Hello there, it's my third or fourth session spending hours trying to debug why a Bluetooth headset would not work in HSP/HFP mode on my x230. The failure more is super obscure because at the time of error the only thing you notice is that no audio comes through in either direction. Using the a2dp_sink profile works fine. The root cause for the problem is simply missing firmware, which dmesg hints at during bootup: Jan 7 04:11:12.809444 barbudinho kernel: [490029.978724] Bluetooth: hci0: BCM: chip id 63 Jan 7 04:11:12.809460 barbudinho kernel: [490029.979639] Bluetooth: hci0: BCM: features 0x07 Jan 7 04:11:12.825406 barbudinho kernel: [490029.995655] Bluetooth: hci0: BCM20702A Jan 7 04:11:12.829543 barbudinho kernel: [490029.996649] Bluetooth: hci0: BCM20702A1 (001.002.014) build Jan 7 04:11:12.829560 barbudinho kernel: [490029.996671] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0a5c-21e6.hcd failed with error -2 Jan 7 04:11:12.829566 barbudinho kernel: [490029.996673] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0a5c-21e6.hcd not found There are at least two firmware packages missing for different common X-series adapters; this is referred to from https://plugable.com/2014/06/23/plugable-usb-bluetooth-adapter-solving-hfphsp-profile-issues-on-linux and also https://wiki.gentoo.org/wiki/Lenovo_Thinkpad_T430. The actual firmware locations from those are: - 0a5c:21e8 https://s3.amazonaws.com/plugable/bin/fw-0a5c_21e8.hcd - 0a5c:21e6 http://dlcdnet.asus.com/pub/ASUS/misc/BT/Bluetooth_V1201650_WHQL_Win10.zip (see Bluetooth_V1201650_WHQL_Win10.zip) There is a lot of firmware collected here which may not be available on Ubuntu: https://github.com/winterheart/broadcom-bt- firmware/tree/master/brcm Related Debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=801084 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1859223/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858531] Re: disco/linux-aws: 5.0.0-1024.27 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-aws meta: linux-meta-aws - phase: Promote to Proposed - phase-changed: Monday, 13. January 2020 12:11 UTC + phase: Testing + phase-changed: Monday, 13. January 2020 13:51 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.0: bug 1858530 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1858531 Title: disco/linux-aws: 5.0.0-1024.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Monday, 13. January 2020 13:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.0: bug 1858530 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859352] [NEW] Graphic driver (radeon) screen problem in kernels released after 2019-06-09
You have been subscribed to a public bug: I've got a problem with some kernel modules (probably radeon) which cause screen problems. It occurs only on internal laptop screen. I found that problem is present in all kernels released after 2019-06-09 18:25. Last kernel which works corectly is v4.19.49 2019-06-09 10:04. v5.2-rc4 2019-06-09 18:25 has this bug and also v4.19.50 2019-06-11 13:06. So I think there are some changes in all kernel packages between hour 10:04 and 18:25 that day (2019-06-09) casue future problems. This may be problem with radeon modules cause screen goes strange when console shows "fb: switching to radeondrmfb from VESA VGA" (I remove "quiet splash" from GRUB menu). In this video I show described problem -> https://player.vimeo.com/video/382017028 I've tested those kernels: *Works correctly: v4.19/ 2018-10-22 23:50 v4.19.49/ 2019-06-09 10:04 v5.0.1/ 2019-03-10 08:30 v5.0.7/ 2019-04-05 22:40 v5.0.21/ 2019-06-04 08:28 v5.1.6/ 2019-05-31 15:32 v5.1.8/ 2019-06-09 09:29 *Not working correctly v4.14.163/ 2020-01-09 12:29 v4.19.50/ 2019-06-11 13:06 v4.19.94/ 2020-01-09 12:42 v5.0.0-37/ 2019-11-14 12:06 v5.1.9/ 2019-06-11 12:29 v5.1.10/ 2019-06-15 11:30 v5.1.11/ 2019-06-17 19:36 v5.2-rc4/ 2019-06-09 18:25 v5.2-rc5/ 2019-06-16 20:26 Quick Hardware info: * Compal FL90 * CPU: Intel Core 2 Duo T7500 * GPU: AMD Rv620 * System Description: Ubuntu 18.04.3 LTS x64 (xubuntu) * Kernel (works OK): 5.1.8-050108-generic #201906090832 SMP Sun Jun 9 08:35:40 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Graphic driver (radeon) screen problem in kernels released after 2019-06-09 https://bugs.launchpad.net/bugs/1859352 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859472] [NEW] Connect Wifi on oem.1066 kernel locks up
Public bug reported: If I attempt to connect to a wifi location on the Lenovo P53 or Lenovo P73 when using the 1066 oem kernel the system locks up. If I reboot back to the 1059 kernel all is working fine ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "system info" https://bugs.launchpad.net/bugs/1859472/+attachment/5319811/+files/bug.tar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859472 Title: Connect Wifi on oem.1066 kernel locks up Status in linux package in Ubuntu: New Bug description: If I attempt to connect to a wifi location on the Lenovo P53 or Lenovo P73 when using the 1066 oem kernel the system locks up. If I reboot back to the 1059 kernel all is working fine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859352] Re: Graphic driver (radeon) screen problem in kernels released after 2019-06-09
add package |linux" because problem is in kernel modules (i think) ** Package changed: 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/1859352 Title: Graphic driver (radeon) screen problem in kernels released after 2019-06-09 Status in linux package in Ubuntu: New Bug description: I've got a problem with some kernel modules (probably radeon) which cause screen problems. It occurs only on internal laptop screen. I found that problem is present in all kernels released after 2019-06-09 18:25. Last kernel which works corectly is v4.19.49 2019-06-09 10:04. v5.2-rc4 2019-06-09 18:25 has this bug and also v4.19.50 2019-06-11 13:06. So I think there are some changes in all kernel packages between hour 10:04 and 18:25 that day (2019-06-09) casue future problems. This may be problem with radeon modules cause screen goes strange when console shows "fb: switching to radeondrmfb from VESA VGA" (I remove "quiet splash" from GRUB menu). In this video I show described problem -> https://player.vimeo.com/video/382017028 I've tested those kernels: *Works correctly: v4.19/ 2018-10-22 23:50 v4.19.49/ 2019-06-09 10:04 v5.0.1/ 2019-03-10 08:30 v5.0.7/ 2019-04-05 22:40 v5.0.21/ 2019-06-04 08:28 v5.1.6/ 2019-05-31 15:32 v5.1.8/ 2019-06-09 09:29 *Not working correctly v4.14.163/ 2020-01-09 12:29 v4.19.50/ 2019-06-11 13:06 v4.19.94/ 2020-01-09 12:42 v5.0.0-37/ 2019-11-14 12:06 v5.1.9/ 2019-06-11 12:29 v5.1.10/ 2019-06-15 11:30 v5.1.11/ 2019-06-17 19:36 v5.2-rc4/ 2019-06-09 18:25 v5.2-rc5/ 2019-06-16 20:26 Quick Hardware info: * Compal FL90 * CPU: Intel Core 2 Duo T7500 * GPU: AMD Rv620 * System Description: Ubuntu 18.04.3 LTS x64 (xubuntu) * Kernel (works OK): 5.1.8-050108-generic #201906090832 SMP Sun Jun 9 08:35:40 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859472] 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 1859472 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859472 Title: Connect Wifi on oem.1066 kernel locks up Status in linux package in Ubuntu: Incomplete Bug description: If I attempt to connect to a wifi location on the Lenovo P53 or Lenovo P73 when using the 1066 oem kernel the system locks up. If I reboot back to the 1059 kernel all is working fine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859352] 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 1859352 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859352 Title: Graphic driver (radeon) screen problem in kernels released after 2019-06-09 Status in linux package in Ubuntu: Incomplete Bug description: I've got a problem with some kernel modules (probably radeon) which cause screen problems. It occurs only on internal laptop screen. I found that problem is present in all kernels released after 2019-06-09 18:25. Last kernel which works corectly is v4.19.49 2019-06-09 10:04. v5.2-rc4 2019-06-09 18:25 has this bug and also v4.19.50 2019-06-11 13:06. So I think there are some changes in all kernel packages between hour 10:04 and 18:25 that day (2019-06-09) casue future problems. This may be problem with radeon modules cause screen goes strange when console shows "fb: switching to radeondrmfb from VESA VGA" (I remove "quiet splash" from GRUB menu). In this video I show described problem -> https://player.vimeo.com/video/382017028 I've tested those kernels: *Works correctly: v4.19/ 2018-10-22 23:50 v4.19.49/ 2019-06-09 10:04 v5.0.1/ 2019-03-10 08:30 v5.0.7/ 2019-04-05 22:40 v5.0.21/ 2019-06-04 08:28 v5.1.6/ 2019-05-31 15:32 v5.1.8/ 2019-06-09 09:29 *Not working correctly v4.14.163/ 2020-01-09 12:29 v4.19.50/ 2019-06-11 13:06 v4.19.94/ 2020-01-09 12:42 v5.0.0-37/ 2019-11-14 12:06 v5.1.9/ 2019-06-11 12:29 v5.1.10/ 2019-06-15 11:30 v5.1.11/ 2019-06-17 19:36 v5.2-rc4/ 2019-06-09 18:25 v5.2-rc5/ 2019-06-16 20:26 Quick Hardware info: * Compal FL90 * CPU: Intel Core 2 Duo T7500 * GPU: AMD Rv620 * System Description: Ubuntu 18.04.3 LTS x64 (xubuntu) * Kernel (works OK): 5.1.8-050108-generic #201906090832 SMP Sun Jun 9 08:35:40 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858544] Re: disco/linux-snapdragon: 5.0.0-1029.31 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-snapdragon meta: linux-meta-snapdragon - phase: Promote to Proposed - phase-changed: Monday, 13. January 2020 12:51 UTC + phase: Testing + phase-changed: Monday, 13. January 2020 14:36 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + certification-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1858544 Title: disco/linux-snapdragon: 5.0.0-1029.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Monday, 13. January 2020 14:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858544/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1857398] Re: ubiquity should support encryption by default with zfsroot, with users able to opt in to running change-key after install
> It is not appropriate to require the user to type a password on every > boot by default; this must be opt-in. My suggestion was not to make EVERYONE use encrypted ZFS with a passphrase, only those who selected an encryption option within Ubiquity. (Perhaps my code was misunderstood as a implementation suggestion instead of a proof of concept for developers.) Having users opt for encryption and password would leave ZFS in parity with other filesystems installed within Ubiquity. I understand the original idea is to transparently force encryption on everyone but not bother them. Not only is there a performance issue, but you could have some really annoyed people if they ever needed to livecd/mount that filesystem and discover the hidden encryption they have to figure out how to work around. -- 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/1857398 Title: ubiquity should support encryption by default with zfsroot, with users able to opt in to running change-key after install Status in ubiquity package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Bug description: zfs supports built-in encryption support, but the decision of whether a pool is encrypted or not must be made at pool creation time; it is possible to add encrypted datasets on top of an unencrypted pool but it is not possible to do an online change of a dataset (or a whole pool) to toggle encryption. We should therefore always install with encryption enabled on zfs systems, with a non-secret key by default, and allow the user to use 'zfs change-key -o keylocation=prompt' after install to take ownership of the encryption and upgrade the security. This is also the simplest way to allow users to avoid having to choose between the security of full-disk encryption, and the advanced filesystem features of zfs since it requires no additional UX work in ubiquity. We should make sure that https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857040 is fixed first in the kernel so that enabling zfs encryption does not impose an unreasonable performance penalty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1857398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858588] Re: xenial/linux-snapdragon: 4.4.0-1132.140 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858594 packages: main: linux-snapdragon meta: linux-meta-snapdragon - phase: Promote to Proposed - phase-changed: Monday, 13. January 2020 13:01 UTC + phase: Testing + phase-changed: Monday, 13. January 2020 14:41 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + certification-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1858587 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1858588 Title: xenial/linux-snapdragon: 4.4.0-1132.140 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858594 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Monday, 13. January 2020 14:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1858587 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858586] Re: xenial/linux-raspi2: 4.4.0-1128.137 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858594 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Promote to Proposed - phase-changed: Monday, 13. January 2020 12:56 UTC + phase: Testing + phase-changed: Monday, 13. January 2020 14:41 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + certification-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1858585 variant: debs -- 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/1858586 Title: xenial/linux-raspi2: 4.4.0-1128.137 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858594 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Monday, 13. January 2020 14:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1858585 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858531] Re: disco/linux-aws: 5.0.0-1024.27 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Monday, 13. January 2020 13:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.0: bug 1858530 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1858531 Title: disco/linux-aws: 5.0.0-1024.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Monday, 13. January 2020 13:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.0: bug 1858530 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828596] Re: kdump fails when crash is triggered after DLPAR cpu add operation
Hello bugproxy, or anyone else affected, Accepted makedumpfile into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.6-2ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: makedumpfile (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags removed: verification-failed ** Tags added: verification-needed verification-needed-eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1828596 Title: kdump fails when crash is triggered after DLPAR cpu add operation Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: In Progress Status in makedumpfile source package in Bionic: In Progress Status in makedumpfile source package in Cosmic: Won't Fix Status in makedumpfile source package in Disco: Won't Fix Status in makedumpfile source package in Eoan: Fix Committed Status in makedumpfile source package in Focal: Fix Released Bug description: [Impact] After a CPU add/hotplug operation on Power systems, kdump will fail after a crash. The kdump kernel needs to be reloaded after a CPU add/hotplug. [Test case] Do CPU add/hotplug, trigger a crash, and check for a successful kdump. [Regression potential] Multiple reloads caused by multiple sequential CPU adds may cause spurious log results, and systemd may fail to properly reload the kdump kernel. This has been handled by resetting the failure counter when doing such reloads. == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 == ---Problem Description--- kdump fails when crash is triggered after CPU add operation. Machine Type = na ---System Hang--- Crashed in early boot process of kdump kernel after crash Had to issue system reset from HMC to reclaim ---Steps to Reproduce--- 1. Configure kdump. 2. Add cpu from HMC. 3. Trigger crash. 4. Machine hangs after crash as below: --- [169250.213166] IPI complete [169250.234331] kexec: Starting switchover sequence. I'm in purgatory --- STRUCK HERE --- ---uname output--- na ---Debugger--- A debugger is not configured == Comment: #1 - Hari Krishna Bathini - 2019-05-10 05:56:46 == The problem is, kexec udev rule to restart kdump-tools service - when a core is added, is not being triggered. The old DT created by kexec (before the core is added) is being used by KDump Kernel. So, when system crashes on a thread from the added core(s), KDump kernel is failing to get the 'boot_cpuid' and eventually failing to boot.. == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 == The udev rule when CPU is added is not triggered because ppc64 does not eject add/remove event when a CPU is hot added/removed. It only ejects online/offline event to user space when CPU is hot added/removed. So, the below udev rules are never triggered when needed: SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart kdump-tools.service" SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart kdump-tools.service" Also, with how CPU hot add & remove are handled in ppc64, a udev trigger to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU hot add case by updating the udev rule and drop the udev rule meant for CPU hot remove in the kdump udev rules file: SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try- restart kdump-tools.service" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1857616] Re: Cannot collect dump due to "Can't get a valid pmd_pte" error
Hello Guilherme, or anyone else affected,
Accepted makedumpfile into eoan-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.6-2ubuntu2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-eoan to verification-done-eoan. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-eoan. In either case, without details of your
testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: makedumpfile (Ubuntu Eoan)
Status: Confirmed => Fix Committed
** Tags added: verification-needed verification-needed-eoan
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1857616
Title:
Cannot collect dump due to "Can't get a valid pmd_pte" error
Status in makedumpfile package in Ubuntu:
Fix Released
Status in makedumpfile source package in Xenial:
Opinion
Status in makedumpfile source package in Bionic:
Confirmed
Status in makedumpfile source package in Disco:
Invalid
Status in makedumpfile source package in Eoan:
Fix Committed
Status in makedumpfile source package in Focal:
Fix Released
Bug description:
[Impact]
* Currently makedumpfile has 2 flaws due to: (a) out of
synchronization with kernel code and, (b) kaslr handling. The first is
related to a definition of a memory flag bit, whereas the second is
about kaslr offset calculation - both cause similar failures when
collecting the vmcore in kdump environment:
Excluding unnecessary pages : [ 46.3 %] / __vtop4_x86_64[ 39.341233]: Can't
get a valid pmd_pte.
readmem: Can't convert a virtual address(e05cb400) to physical
address.
readmem: type_addr: 0, addr:e05cb400, size:32768
__exclude_unnecessary_pages: Can't read the buffer of struct page.
create_2nd_bitmap: Can't exclude unnecessary pages.
* The report is mainly related to the first issue, which started to
happen after the merge of kernel commit 326e1b8f83a4 ("mm/sparsemem:
introduce a SECTION_IS_EARLY flag"), introduced in kernel 5.3. After
this commit, a memory flag was changed and induced the error in dump
collection. The fix is available in makedumpfile, as commit 7bdb468c2c
("Increase SECTION_MAP_LAST_BIT to 4"). This is hereby SRUed to Bionic
(due to HWE kernel 5.3), Eoan and Focal.
* The other issue is fixed in both Eoan and Focal, on makedumpfile
1.6.6-based version. It is related with the kaslr offset: if the
offset is small enough, we may return 0 wrongly in
get_kaslr_offset_x86_64(), causing the vmcore collection to fail or
even worse, to erase unintended data from the memory dump. This is
fixed by makedumpfile commit 3222d4ad04 ("x86_64: fix
get_kaslr_offset_x86_64() to return kaslr_offset correctly"), which
isn't present in versions before 1.6.6. We hereby SRU this fix for
Bionic.
* Notice this modification is being worked concurrently with other
kdump-tools' changes in LP #1828596.
[Test Case]
1) Deploy an Eoan VM e.g. with uvt-kvm;
2) Set-up console output in the guest;
3) Install the kdump-tools package;
4) Configure and collect a dump (with sysrq to panic the system) - the error
aforementioned is observed given Eoan kernel is 5.3-based.
[Regression Potential]
* The modifications hereby proposed are minimal and scope-constrained
to makedumpfile in x86_64; both are merged in makedumpfile upstream,
one of them being already released in E/F. An unlikely regression
would potentially fails vmcore collection in kdump environment.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1857616/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856323] Re: kdump-tools is unable to resolve DNS when systemd-resolved is used
Hello Guilherme, or anyone else affected,
Accepted makedumpfile into eoan-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.6-2ubuntu2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-eoan to verification-done-eoan. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-eoan. In either case, without details of your
testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: makedumpfile (Ubuntu Eoan)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-eoan
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1856323
Title:
kdump-tools is unable to resolve DNS when systemd-resolved is used
Status in makedumpfile package in Ubuntu:
Fix Released
Status in makedumpfile source package in Bionic:
In Progress
Status in makedumpfile source package in Disco:
Won't Fix
Status in makedumpfile source package in Eoan:
Fix Committed
Status in makedumpfile source package in Focal:
Fix Released
Bug description:
[Impact]
* Currently kdump is unable to handle domain name resolution due to
the lack of "resolved" service in the kdump environment; this happens
given the nature of reduced service load required in the kdump
scenario.
* Kdump currently relies on a systemd service approach - there are 2
services, one being a configuration/load entity (kdump-tools.service)
whereas the other is the crash dump service itself (kdump-tools-
dump.service). Due to the complexity and risk in booting a machine
after a kernel crash to collect kernel dump, it's expected kdump-
tools-dump to load the minimal possible amount of services. In order
to achieve that, kdump-tools-dump relies only in the sysinit and
network-online targets.
* The systemd DNS tool ("resolved") is not ready in the moment kdump-
tools-dump service is up to collect the kernel dump; also, "resolved"
depends on dbus.socket to work, so to have a fully functional DNS
resolution we are hereby adding both services as dependencies for
kdump-tools-dump, so the network dump functionality works with
hostnames (not requiring anymore that users set IP raw addresses).
* The attached SVG files (kdump.svg and regular_boot.svg) contains
"systemd-analyze plot" outputs from a kdump-tools-dump and regular
boot perspective. To collect the kdump data we manage to change the
kdump-tools-dump service to load SSHd and also that required disabling
the OneShot property of such service. With that data, one can check
the services started/completed in each environment - it's possible to
notice the absence of systemd-resolved when in kdump environment.
* Notice this modification is being worked concurrently with other
kdump-tools' changes in LP #1828596.
[Test Case]
1) Deploy a Bionic VM e.g. with uvt-kvm;
2) Set-up console output in the guest;
3) Install the kdump-tools package;
4) Configure a network dump (SSH or NFS) using hostnames for the target
machine;
5) Perform the test dump (with 'echo c> /proc/sysrq-trigger') and watch the
failure in name resolution,
[Regression Potential]
* The modifications hereby proposed are minimal and scope-constrained to
kdump-tools package; it'll only affect the services loaded before
kdump-tools-dump collecting service.
A regression would then potentially fails kdump completion if one of the new
services added to the kdump environment load (resolved and dbus.socket) fails
to load and stalls/prevents the kdump service complete load.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1856323/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800566] Re: Make reset_devices parameter default for kdump
Hello Guilherme, or anyone else affected, Accepted makedumpfile into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.6-2ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: makedumpfile (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1800566 Title: Make reset_devices parameter default for kdump Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Trusty: Won't Fix Status in makedumpfile source package in Xenial: In Progress Status in makedumpfile source package in Bionic: In Progress Status in makedumpfile source package in Cosmic: Won't Fix Status in makedumpfile source package in Disco: Won't Fix Status in makedumpfile source package in Eoan: Fix Committed Status in makedumpfile source package in Focal: Fix Released Bug description: [Impact] * Kdump does not configure by default the crash kernel to perform a device reset by default, by passing the "reset_devices" parameter. * Kernel has the "reset_devices" parameter that drivers can opt-in, and perform special activity in case this parameter is parsed from command-line. For example, in kdump kernels it hints the drivers that they are booting from a non-healthy condition and needs to issue some form of reset to the adapter, like clearing DMA mapping in their firmware for example. Users currently (kernel v5.5-rc2) are: aacraid, hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, xenbus. This should be enabled by default in the kdump config file to be added in the kdump kernel command-line for all versions. [Test Case] 1) Deploy a Bionic VM e.g. with uvt-kvm 2) Install the kdump-tools package 3) Run `kdump-config test`and check for the 'reset_devices' parameter: $ kdump-config test ... kexec command to be used: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz [Regression Potential] The regression potential is low, since it doesn't need any changes in makedumpfile code and we're only adding a parameter on the crash kernel command-line. The risks are related with bad behavior with the kernel when using "reset_devices", like if the driver has bugs in this path. It's considered safer to have the option (and this way prevent problems for booting a unhealthy kernel with potential stuck DMAs in the devices) than not having it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858543] Re: disco/linux-oracle: 5.0.0-1010.15 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:26 UTC reason: - promote-to-proposed: Pending -- package copied to Proposed signed:queued + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-oracle-5.0: bug 1858542 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1858543 Title: disco/linux-oracle: 5.0.0-1010.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:26 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-oracle-5.0: bug 1858542 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858536] Re: bionic/linux-gcp: 5.0.0-1029.30~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858539 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Monday, 13. January 2020 10:36 UTC reason: - promote-to-proposed: Pending -- package copied to Proposed signed:queued + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-gcp/gcp-kernel: bug 1858535 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1858536 Title: bionic/linux-gcp: 5.0.0-1029.30~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858539 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Monday, 13. January 2020 10:36 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-gcp/gcp-kernel: bug 1858535 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858539] Re: disco/linux-gcp: 5.0.0-1029.30 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:21 UTC reason: - promote-to-proposed: Pending -- package copied to Proposed signed:queued + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-gcp: bug 1858536 bionic/linux-gke-5.0: bug 1858538 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1858539 Title: disco/linux-gcp: 5.0.0-1029.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858547 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Monday, 13. January 2020 12:21 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-gcp: bug 1858536 bionic/linux-gke-5.0: bug 1858538 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859472] Re: Connect Wifi on oem.1066 kernel locks up
apport information ** Tags added: apport-collected bionic ** Description changed: - If I attempt to connect to a wifi location on the Lenovo P53 or Lenovo - P73 when using the 1066 oem kernel the system locks up. If I reboot - back to the 1059 kernel all is working fine + If I attempt to connect to a wifi location on the Lenovo P53 or Lenovo P73 when using the 1066 oem kernel the system locks up. If I reboot back to the 1059 kernel all is working fine + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.9 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: z 2338 F pulseaudio + /dev/snd/controlC0: z 2338 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistributionChannelDescriptor: + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-sutton-bionic-amd64-20191017-183+sutton-mccarthy-bionic-amd64+iso + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2020-01-13 (0 days ago) + InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20191017-14:35 + IwConfig: + lono wireless extensions. + + wlp82s0 no wireless extensions. + + enp0s31f6 no wireless extensions. + MachineType: LENOVO 20QNZ4RCUS + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1066-oem root=UUID=8634c580-655e-4b92-93f7-93a3a39face2 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-1066-oem N/A + linux-backports-modules-4.15.0-1066-oem N/A + linux-firmware 1.173.14 + Tags: bionic + Uname: Linux 4.15.0-1066-oem x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 08/02/2019 + dmi.bios.vendor: LENOVO + dmi.bios.version: N2NET26W (1.11 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20QNZ4RCUS + dmi.board.vendor: LENOVO + dmi.board.version: SDK0Q40104 WIN + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.modalias: dmi:bvnLENOVO:bvrN2NET26W(1.11):bd08/02/2019:svnLENOVO:pn20QNZ4RCUS:pvrThinkPadP53:rvnLENOVO:rn20QNZ4RCUS:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad P53 + dmi.product.name: 20QNZ4RCUS + dmi.product.version: ThinkPad P53 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1859472/+attachment/5319814/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859472 Title: Connect Wifi on oem.1066 kernel locks up Status in linux package in Ubuntu: Confirmed Bug description: If I attempt to connect to a wifi location on the Lenovo P53 or Lenovo P73 when using the 1066 oem kernel the system locks up. If I reboot back to the 1059 kernel all is working fine --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: z 2338 F pulseaudio /dev/snd/controlC0: z 2338 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20191017-183+sutton-mccarthy-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-13 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20191017-14:35 IwConfig: lono wireless extensions. wlp82s0 no wireless extensions. enp0s31f6 no wireless extensions. MachineType: LENOVO 20QNZ4RCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1066-oem root=UUID=8634c580-655e-4b92-93f7-93a3a39face2 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1066-oem N/A linux-backports-modules-4.15.0-1066-oem N/A linux-firmware 1.173.14 Tags: bionic Uname: Linux 4.15.0-1066-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm
[Kernel-packages] [Bug 1859472] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1859472/+attachment/5319820/+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/1859472 Title: Connect Wifi on oem.1066 kernel locks up Status in linux package in Ubuntu: Confirmed Bug description: If I attempt to connect to a wifi location on the Lenovo P53 or Lenovo P73 when using the 1066 oem kernel the system locks up. If I reboot back to the 1059 kernel all is working fine --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: z 2338 F pulseaudio /dev/snd/controlC0: z 2338 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20191017-183+sutton-mccarthy-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-13 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20191017-14:35 IwConfig: lono wireless extensions. wlp82s0 no wireless extensions. enp0s31f6 no wireless extensions. MachineType: LENOVO 20QNZ4RCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1066-oem root=UUID=8634c580-655e-4b92-93f7-93a3a39face2 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1066-oem N/A linux-backports-modules-4.15.0-1066-oem N/A linux-firmware 1.173.14 Tags: bionic Uname: Linux 4.15.0-1066-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET26W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QNZ4RCUS dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET26W(1.11):bd08/02/2019:svnLENOVO:pn20QNZ4RCUS:pvrThinkPadP53:rvnLENOVO:rn20QNZ4RCUS:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53 dmi.product.name: 20QNZ4RCUS dmi.product.version: ThinkPad P53 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859472] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1859472/+attachment/5319816/+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/1859472 Title: Connect Wifi on oem.1066 kernel locks up Status in linux package in Ubuntu: Confirmed Bug description: If I attempt to connect to a wifi location on the Lenovo P53 or Lenovo P73 when using the 1066 oem kernel the system locks up. If I reboot back to the 1059 kernel all is working fine --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: z 2338 F pulseaudio /dev/snd/controlC0: z 2338 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20191017-183+sutton-mccarthy-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-13 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20191017-14:35 IwConfig: lono wireless extensions. wlp82s0 no wireless extensions. enp0s31f6 no wireless extensions. MachineType: LENOVO 20QNZ4RCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1066-oem root=UUID=8634c580-655e-4b92-93f7-93a3a39face2 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1066-oem N/A linux-backports-modules-4.15.0-1066-oem N/A linux-firmware 1.173.14 Tags: bionic Uname: Linux 4.15.0-1066-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET26W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QNZ4RCUS dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET26W(1.11):bd08/02/2019:svnLENOVO:pn20QNZ4RCUS:pvrThinkPadP53:rvnLENOVO:rn20QNZ4RCUS:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53 dmi.product.name: 20QNZ4RCUS dmi.product.version: ThinkPad P53 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859472] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1859472/+attachment/5319815/+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/1859472 Title: Connect Wifi on oem.1066 kernel locks up Status in linux package in Ubuntu: Confirmed Bug description: If I attempt to connect to a wifi location on the Lenovo P53 or Lenovo P73 when using the 1066 oem kernel the system locks up. If I reboot back to the 1059 kernel all is working fine --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: z 2338 F pulseaudio /dev/snd/controlC0: z 2338 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20191017-183+sutton-mccarthy-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-13 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20191017-14:35 IwConfig: lono wireless extensions. wlp82s0 no wireless extensions. enp0s31f6 no wireless extensions. MachineType: LENOVO 20QNZ4RCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1066-oem root=UUID=8634c580-655e-4b92-93f7-93a3a39face2 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1066-oem N/A linux-backports-modules-4.15.0-1066-oem N/A linux-firmware 1.173.14 Tags: bionic Uname: Linux 4.15.0-1066-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET26W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QNZ4RCUS dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET26W(1.11):bd08/02/2019:svnLENOVO:pn20QNZ4RCUS:pvrThinkPadP53:rvnLENOVO:rn20QNZ4RCUS:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53 dmi.product.name: 20QNZ4RCUS dmi.product.version: ThinkPad P53 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859472] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1859472/+attachment/5319818/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859472 Title: Connect Wifi on oem.1066 kernel locks up Status in linux package in Ubuntu: Confirmed Bug description: If I attempt to connect to a wifi location on the Lenovo P53 or Lenovo P73 when using the 1066 oem kernel the system locks up. If I reboot back to the 1059 kernel all is working fine --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: z 2338 F pulseaudio /dev/snd/controlC0: z 2338 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20191017-183+sutton-mccarthy-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-13 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20191017-14:35 IwConfig: lono wireless extensions. wlp82s0 no wireless extensions. enp0s31f6 no wireless extensions. MachineType: LENOVO 20QNZ4RCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1066-oem root=UUID=8634c580-655e-4b92-93f7-93a3a39face2 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1066-oem N/A linux-backports-modules-4.15.0-1066-oem N/A linux-firmware 1.173.14 Tags: bionic Uname: Linux 4.15.0-1066-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET26W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QNZ4RCUS dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET26W(1.11):bd08/02/2019:svnLENOVO:pn20QNZ4RCUS:pvrThinkPadP53:rvnLENOVO:rn20QNZ4RCUS:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53 dmi.product.name: 20QNZ4RCUS dmi.product.version: ThinkPad P53 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859472] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1859472/+attachment/5319819/+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/1859472 Title: Connect Wifi on oem.1066 kernel locks up Status in linux package in Ubuntu: Confirmed Bug description: If I attempt to connect to a wifi location on the Lenovo P53 or Lenovo P73 when using the 1066 oem kernel the system locks up. If I reboot back to the 1059 kernel all is working fine --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: z 2338 F pulseaudio /dev/snd/controlC0: z 2338 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20191017-183+sutton-mccarthy-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-13 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20191017-14:35 IwConfig: lono wireless extensions. wlp82s0 no wireless extensions. enp0s31f6 no wireless extensions. MachineType: LENOVO 20QNZ4RCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1066-oem root=UUID=8634c580-655e-4b92-93f7-93a3a39face2 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1066-oem N/A linux-backports-modules-4.15.0-1066-oem N/A linux-firmware 1.173.14 Tags: bionic Uname: Linux 4.15.0-1066-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET26W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QNZ4RCUS dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET26W(1.11):bd08/02/2019:svnLENOVO:pn20QNZ4RCUS:pvrThinkPadP53:rvnLENOVO:rn20QNZ4RCUS:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53 dmi.product.name: 20QNZ4RCUS dmi.product.version: ThinkPad P53 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859472] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1859472/+attachment/5319825/+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/1859472 Title: Connect Wifi on oem.1066 kernel locks up Status in linux package in Ubuntu: Confirmed Bug description: If I attempt to connect to a wifi location on the Lenovo P53 or Lenovo P73 when using the 1066 oem kernel the system locks up. If I reboot back to the 1059 kernel all is working fine --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: z 2338 F pulseaudio /dev/snd/controlC0: z 2338 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20191017-183+sutton-mccarthy-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-13 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20191017-14:35 IwConfig: lono wireless extensions. wlp82s0 no wireless extensions. enp0s31f6 no wireless extensions. MachineType: LENOVO 20QNZ4RCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1066-oem root=UUID=8634c580-655e-4b92-93f7-93a3a39face2 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1066-oem N/A linux-backports-modules-4.15.0-1066-oem N/A linux-firmware 1.173.14 Tags: bionic Uname: Linux 4.15.0-1066-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET26W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QNZ4RCUS dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET26W(1.11):bd08/02/2019:svnLENOVO:pn20QNZ4RCUS:pvrThinkPadP53:rvnLENOVO:rn20QNZ4RCUS:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53 dmi.product.name: 20QNZ4RCUS dmi.product.version: ThinkPad P53 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859472] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1859472/+attachment/5319826/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859472 Title: Connect Wifi on oem.1066 kernel locks up Status in linux package in Ubuntu: Confirmed Bug description: If I attempt to connect to a wifi location on the Lenovo P53 or Lenovo P73 when using the 1066 oem kernel the system locks up. If I reboot back to the 1059 kernel all is working fine --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: z 2338 F pulseaudio /dev/snd/controlC0: z 2338 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20191017-183+sutton-mccarthy-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-13 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20191017-14:35 IwConfig: lono wireless extensions. wlp82s0 no wireless extensions. enp0s31f6 no wireless extensions. MachineType: LENOVO 20QNZ4RCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1066-oem root=UUID=8634c580-655e-4b92-93f7-93a3a39face2 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1066-oem N/A linux-backports-modules-4.15.0-1066-oem N/A linux-firmware 1.173.14 Tags: bionic Uname: Linux 4.15.0-1066-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET26W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QNZ4RCUS dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET26W(1.11):bd08/02/2019:svnLENOVO:pn20QNZ4RCUS:pvrThinkPadP53:rvnLENOVO:rn20QNZ4RCUS:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53 dmi.product.name: 20QNZ4RCUS dmi.product.version: ThinkPad P53 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859472] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1859472/+attachment/5319821/+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/1859472 Title: Connect Wifi on oem.1066 kernel locks up Status in linux package in Ubuntu: Confirmed Bug description: If I attempt to connect to a wifi location on the Lenovo P53 or Lenovo P73 when using the 1066 oem kernel the system locks up. If I reboot back to the 1059 kernel all is working fine --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: z 2338 F pulseaudio /dev/snd/controlC0: z 2338 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20191017-183+sutton-mccarthy-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-13 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20191017-14:35 IwConfig: lono wireless extensions. wlp82s0 no wireless extensions. enp0s31f6 no wireless extensions. MachineType: LENOVO 20QNZ4RCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1066-oem root=UUID=8634c580-655e-4b92-93f7-93a3a39face2 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1066-oem N/A linux-backports-modules-4.15.0-1066-oem N/A linux-firmware 1.173.14 Tags: bionic Uname: Linux 4.15.0-1066-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET26W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QNZ4RCUS dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET26W(1.11):bd08/02/2019:svnLENOVO:pn20QNZ4RCUS:pvrThinkPadP53:rvnLENOVO:rn20QNZ4RCUS:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53 dmi.product.name: 20QNZ4RCUS dmi.product.version: ThinkPad P53 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859472] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1859472/+attachment/5319817/+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/1859472 Title: Connect Wifi on oem.1066 kernel locks up Status in linux package in Ubuntu: Confirmed Bug description: If I attempt to connect to a wifi location on the Lenovo P53 or Lenovo P73 when using the 1066 oem kernel the system locks up. If I reboot back to the 1059 kernel all is working fine --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: z 2338 F pulseaudio /dev/snd/controlC0: z 2338 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20191017-183+sutton-mccarthy-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-13 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20191017-14:35 IwConfig: lono wireless extensions. wlp82s0 no wireless extensions. enp0s31f6 no wireless extensions. MachineType: LENOVO 20QNZ4RCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1066-oem root=UUID=8634c580-655e-4b92-93f7-93a3a39face2 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1066-oem N/A linux-backports-modules-4.15.0-1066-oem N/A linux-firmware 1.173.14 Tags: bionic Uname: Linux 4.15.0-1066-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET26W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QNZ4RCUS dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET26W(1.11):bd08/02/2019:svnLENOVO:pn20QNZ4RCUS:pvrThinkPadP53:rvnLENOVO:rn20QNZ4RCUS:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53 dmi.product.name: 20QNZ4RCUS dmi.product.version: ThinkPad P53 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859472] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1859472/+attachment/5319824/+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/1859472 Title: Connect Wifi on oem.1066 kernel locks up Status in linux package in Ubuntu: Confirmed Bug description: If I attempt to connect to a wifi location on the Lenovo P53 or Lenovo P73 when using the 1066 oem kernel the system locks up. If I reboot back to the 1059 kernel all is working fine --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: z 2338 F pulseaudio /dev/snd/controlC0: z 2338 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20191017-183+sutton-mccarthy-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-13 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20191017-14:35 IwConfig: lono wireless extensions. wlp82s0 no wireless extensions. enp0s31f6 no wireless extensions. MachineType: LENOVO 20QNZ4RCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1066-oem root=UUID=8634c580-655e-4b92-93f7-93a3a39face2 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1066-oem N/A linux-backports-modules-4.15.0-1066-oem N/A linux-firmware 1.173.14 Tags: bionic Uname: Linux 4.15.0-1066-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET26W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QNZ4RCUS dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET26W(1.11):bd08/02/2019:svnLENOVO:pn20QNZ4RCUS:pvrThinkPadP53:rvnLENOVO:rn20QNZ4RCUS:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53 dmi.product.name: 20QNZ4RCUS dmi.product.version: ThinkPad P53 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859472] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1859472/+attachment/5319823/+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/1859472 Title: Connect Wifi on oem.1066 kernel locks up Status in linux package in Ubuntu: Confirmed Bug description: If I attempt to connect to a wifi location on the Lenovo P53 or Lenovo P73 when using the 1066 oem kernel the system locks up. If I reboot back to the 1059 kernel all is working fine --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: z 2338 F pulseaudio /dev/snd/controlC0: z 2338 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20191017-183+sutton-mccarthy-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-13 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20191017-14:35 IwConfig: lono wireless extensions. wlp82s0 no wireless extensions. enp0s31f6 no wireless extensions. MachineType: LENOVO 20QNZ4RCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1066-oem root=UUID=8634c580-655e-4b92-93f7-93a3a39face2 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1066-oem N/A linux-backports-modules-4.15.0-1066-oem N/A linux-firmware 1.173.14 Tags: bionic Uname: Linux 4.15.0-1066-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET26W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QNZ4RCUS dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET26W(1.11):bd08/02/2019:svnLENOVO:pn20QNZ4RCUS:pvrThinkPadP53:rvnLENOVO:rn20QNZ4RCUS:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53 dmi.product.name: 20QNZ4RCUS dmi.product.version: ThinkPad P53 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859472] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1859472/+attachment/5319822/+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/1859472 Title: Connect Wifi on oem.1066 kernel locks up Status in linux package in Ubuntu: Confirmed Bug description: If I attempt to connect to a wifi location on the Lenovo P53 or Lenovo P73 when using the 1066 oem kernel the system locks up. If I reboot back to the 1059 kernel all is working fine --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: z 2338 F pulseaudio /dev/snd/controlC0: z 2338 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20191017-183+sutton-mccarthy-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-13 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20191017-14:35 IwConfig: lono wireless extensions. wlp82s0 no wireless extensions. enp0s31f6 no wireless extensions. MachineType: LENOVO 20QNZ4RCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1066-oem root=UUID=8634c580-655e-4b92-93f7-93a3a39face2 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1066-oem N/A linux-backports-modules-4.15.0-1066-oem N/A linux-firmware 1.173.14 Tags: bionic Uname: Linux 4.15.0-1066-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET26W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QNZ4RCUS dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET26W(1.11):bd08/02/2019:svnLENOVO:pn20QNZ4RCUS:pvrThinkPadP53:rvnLENOVO:rn20QNZ4RCUS:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53 dmi.product.name: 20QNZ4RCUS dmi.product.version: ThinkPad P53 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777398] Re: dm thin block allocation failure
Patch posted at https://www.redhat.com/archives/dm-devel/2020-January/msg00021.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777398 Title: dm thin block allocation failure Status in linux package in Ubuntu: Confirmed Bug description: When using the bionic kernel (hwe-edge) on xenial we randomly trigger a kernel bug when creating a thin provisioned lvm volume. kernel: [146487.421278] [ cut here ] kernel: [146487.421281] kernel BUG at /build/linux-hwe-edge-eBL7So/linux-hwe-edge-4.15.0/drivers/md/persistent-data/dm-space-map-disk.c:178! kernel: [146487.421435] invalid opcode: [#1] SMP PTI kernel: [146487.421528] Modules linked in: dm_snapshot cmac arc4 md4 nls_utf8 cifs ccm fscache dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag af_packet_diag netlink_diag xt_CHECKSUM xt_nat iptable_nat nf_nat_ipv4 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack iptable_filter veth dummy bridge iptable_mangle xt_CT iptable_raw ip_tables x_tables vhost_net vhost tap ipmi_ssif dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio intel_rapl skx_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf lpc_ich ioatdma shpchp dca acpi_power_meter acpi_pad mac_hid ipmi_si ipmi_devintf ipmi_msghandler kernel: [146487.421859] nf_nat_ftp nf_conntrack_ftp nf_nat_sip nf_conntrack_sip nf_nat_pptp nf_conntrack_pptp nf_nat_proto_gre nf_nat nf_conntrack_proto_gre nf_conntrack tcp_htcp 8021q garp mrp stp llc bonding autofs4 btrfs zstd_compress raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid10 raid1 i2c_algo_bit ttm i40e drm_kms_helper syscopyarea ptp sysfillrect pps_core sysimgblt fb_sys_fops nvme ahci drm nvme_core libahci wmi kernel: [146487.422080] CPU: 13 PID: 2274450 Comm: kworker/u576:1 Not tainted 4.15.0-22-generic #24~16.04.1-Ubuntu kernel: [146487.422211] Hardware name: Quanta Cloud Technology Inc. QuantaGrid D52B-1U/S5B-MB (LBG-4), BIOS 3A10.03 11/17/2017 kernel: [146487.422349] Workqueue: dm-thin do_worker [dm_thin_pool] kernel: [146487.422443] RIP: 0010:sm_disk_new_block+0xa1/0xb0 [dm_persistent_data] kernel: [146487.422536] RSP: 0018:9efc5e4d3c68 EFLAGS: 00010297 kernel: [146487.422626] RAX: RBX: 88b122d34000 RCX: kernel: [146487.422749] RDX: 8868d8631e00 RSI: 0282 RDI: 88b137691200 kernel: [146487.422872] RBP: 9efc5e4d3c90 R08: R09: 9efc5e4d39f0 kernel: [146487.422994] R10: 9efc5e4d38f8 R11: 9efc5e4d3b48 R12: kernel: [146487.423117] R13: 9efc5e4d3d40 R14: 9efc5e4d3d40 R15: 882de1769fa0 kernel: [146487.423240] FS: () GS:8868ee54() knlGS: kernel: [146487.423366] CS: 0010 DS: ES: CR0: 80050033 kernel: [146487.423457] CR2: 7f0f30b083c0 CR3: 002ab260a004 CR4: 007626e0 kernel: [146487.423580] DR0: DR1: DR2: kernel: [146487.423703] DR3: DR6: fffe0ff0 DR7: 0400 kernel: [146487.423826] PKRU: 5554 kernel: [146487.423906] Call Trace: kernel: [146487.423989] dm_pool_alloc_data_block+0x44/0x60 [dm_thin_pool] kernel: [146487.424082] alloc_data_block.isra.53+0x6f/0x180 [dm_thin_pool] kernel: [146487.424175] process_cell+0x2cf/0x4d0 [dm_thin_pool] kernel: [146487.424267] ? mempool_alloc_slab+0x15/0x20 kernel: [146487.424354] ? mempool_alloc+0x73/0x180 kernel: [146487.424440] ? process_prepared+0x8d/0xc0 [dm_thin_pool] kernel: [146487.424531] do_worker+0x25c/0x8b0 [dm_thin_pool] kernel: [146487.424621] process_one_work+0x14d/0x410 kernel: [146487.424708] ? process_discard_cell_passdown+0x1e0/0x1e0 [dm_thin_pool] kernel: [146487.424802] ? process_one_work+0x14d/0x410 kernel: [146487.424888] worker_thread+0x4b/0x460 kernel: [146487.424973] kthread+0x105/0x140 kernel: [146487.425055] ? process_one_work+0x410/0x410 kernel: [146487.425142] ? kthread_associate_blkcg+0xa0/0xa0 kernel: [146487.425230] ? do_syscall_64+0x73/0x130 kernel: [146487.425315] ? SyS_exit_group+0x14/0x20 kernel: [146487.425401] ret_from_fork+0x35/0x40 kernel: [146487.425485] Code: c0 01 48 89 83 20 22 00 00 49 8b 75 00 e8 68 f7 ff ff 85 c0 75 10 83 7d dc 01 75 0f 48 83 83 28 22 00 00 01 eb af 41 89 c4 eb aa <0f> 0b e8 e8 1b cf d2 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 kernel: [146487.425703] RIP: sm_disk_new_block+0xa1/0xb0 [dm_persistent_data] RSP: 9efc5e4d3c68 kernel: [146487.425869] ---[ end
[Kernel-packages] [Bug 1806232] Re: Graphical artifacts/glitches on Intel Atom x5 - Screen Tearing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (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/1806232 Title: Graphical artifacts/glitches on Intel Atom x5 - Screen Tearing Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: There is screen tearing on the left side of the screen, and it's especially apparent when there's motion on the entire screen. This is happening on Ubuntu 18.10 on an Asus T102HA with an Atom x5 Cherry Trail. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Dec 2 00:59:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1400] InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: ASUSTeK COMPUTER INC. T102HA 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.18.0-11-generic root=UUID=6d4342e4-1f2b-42ea-850e-63e34c955cd3 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T102HA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T102HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT102HA.204:bd07/18/2016:svnASUSTeKCOMPUTERINC.:pnT102HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT102HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T102HA dmi.product.sku: ASUS-TabletSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1857616] Autopkgtest regression report (makedumpfile/1:1.6.6-2ubuntu2)
All autopkgtests for the newly accepted makedumpfile (1:1.6.6-2ubuntu2) for
eoan have finished running.
The following regressions have been reported in tests triggered by the package:
makedumpfile/1:1.6.6-2ubuntu2 (i386, ppc64el)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#makedumpfile
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1857616
Title:
Cannot collect dump due to "Can't get a valid pmd_pte" error
Status in makedumpfile package in Ubuntu:
Fix Released
Status in makedumpfile source package in Xenial:
Opinion
Status in makedumpfile source package in Bionic:
Confirmed
Status in makedumpfile source package in Disco:
Invalid
Status in makedumpfile source package in Eoan:
Fix Committed
Status in makedumpfile source package in Focal:
Fix Released
Bug description:
[Impact]
* Currently makedumpfile has 2 flaws due to: (a) out of
synchronization with kernel code and, (b) kaslr handling. The first is
related to a definition of a memory flag bit, whereas the second is
about kaslr offset calculation - both cause similar failures when
collecting the vmcore in kdump environment:
Excluding unnecessary pages : [ 46.3 %] / __vtop4_x86_64[ 39.341233]: Can't
get a valid pmd_pte.
readmem: Can't convert a virtual address(e05cb400) to physical
address.
readmem: type_addr: 0, addr:e05cb400, size:32768
__exclude_unnecessary_pages: Can't read the buffer of struct page.
create_2nd_bitmap: Can't exclude unnecessary pages.
* The report is mainly related to the first issue, which started to
happen after the merge of kernel commit 326e1b8f83a4 ("mm/sparsemem:
introduce a SECTION_IS_EARLY flag"), introduced in kernel 5.3. After
this commit, a memory flag was changed and induced the error in dump
collection. The fix is available in makedumpfile, as commit 7bdb468c2c
("Increase SECTION_MAP_LAST_BIT to 4"). This is hereby SRUed to Bionic
(due to HWE kernel 5.3), Eoan and Focal.
* The other issue is fixed in both Eoan and Focal, on makedumpfile
1.6.6-based version. It is related with the kaslr offset: if the
offset is small enough, we may return 0 wrongly in
get_kaslr_offset_x86_64(), causing the vmcore collection to fail or
even worse, to erase unintended data from the memory dump. This is
fixed by makedumpfile commit 3222d4ad04 ("x86_64: fix
get_kaslr_offset_x86_64() to return kaslr_offset correctly"), which
isn't present in versions before 1.6.6. We hereby SRU this fix for
Bionic.
* Notice this modification is being worked concurrently with other
kdump-tools' changes in LP #1828596.
[Test Case]
1) Deploy an Eoan VM e.g. with uvt-kvm;
2) Set-up console output in the guest;
3) Install the kdump-tools package;
4) Configure and collect a dump (with sysrq to panic the system) - the error
aforementioned is observed given Eoan kernel is 5.3-based.
[Regression Potential]
* The modifications hereby proposed are minimal and scope-constrained
to makedumpfile in x86_64; both are merged in makedumpfile upstream,
one of them being already released in E/F. An unlikely regression
would potentially fails vmcore collection in kdump environment.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1857616/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800566] Autopkgtest regression report (makedumpfile/1:1.6.6-2ubuntu2)
All autopkgtests for the newly accepted makedumpfile (1:1.6.6-2ubuntu2) for eoan have finished running. The following regressions have been reported in tests triggered by the package: makedumpfile/1:1.6.6-2ubuntu2 (i386, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#makedumpfile [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1800566 Title: Make reset_devices parameter default for kdump Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Trusty: Won't Fix Status in makedumpfile source package in Xenial: In Progress Status in makedumpfile source package in Bionic: In Progress Status in makedumpfile source package in Cosmic: Won't Fix Status in makedumpfile source package in Disco: Won't Fix Status in makedumpfile source package in Eoan: Fix Committed Status in makedumpfile source package in Focal: Fix Released Bug description: [Impact] * Kdump does not configure by default the crash kernel to perform a device reset by default, by passing the "reset_devices" parameter. * Kernel has the "reset_devices" parameter that drivers can opt-in, and perform special activity in case this parameter is parsed from command-line. For example, in kdump kernels it hints the drivers that they are booting from a non-healthy condition and needs to issue some form of reset to the adapter, like clearing DMA mapping in their firmware for example. Users currently (kernel v5.5-rc2) are: aacraid, hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, xenbus. This should be enabled by default in the kdump config file to be added in the kdump kernel command-line for all versions. [Test Case] 1) Deploy a Bionic VM e.g. with uvt-kvm 2) Install the kdump-tools package 3) Run `kdump-config test`and check for the 'reset_devices' parameter: $ kdump-config test ... kexec command to be used: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz [Regression Potential] The regression potential is low, since it doesn't need any changes in makedumpfile code and we're only adding a parameter on the crash kernel command-line. The risks are related with bad behavior with the kernel when using "reset_devices", like if the driver has bugs in this path. It's considered safer to have the option (and this way prevent problems for booting a unhealthy kernel with potential stuck DMAs in the devices) than not having it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828596] Autopkgtest regression report (makedumpfile/1:1.6.6-2ubuntu2)
All autopkgtests for the newly accepted makedumpfile (1:1.6.6-2ubuntu2) for eoan have finished running. The following regressions have been reported in tests triggered by the package: makedumpfile/1:1.6.6-2ubuntu2 (i386, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#makedumpfile [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1828596 Title: kdump fails when crash is triggered after DLPAR cpu add operation Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: In Progress Status in makedumpfile source package in Bionic: In Progress Status in makedumpfile source package in Cosmic: Won't Fix Status in makedumpfile source package in Disco: Won't Fix Status in makedumpfile source package in Eoan: Fix Committed Status in makedumpfile source package in Focal: Fix Released Bug description: [Impact] After a CPU add/hotplug operation on Power systems, kdump will fail after a crash. The kdump kernel needs to be reloaded after a CPU add/hotplug. [Test case] Do CPU add/hotplug, trigger a crash, and check for a successful kdump. [Regression potential] Multiple reloads caused by multiple sequential CPU adds may cause spurious log results, and systemd may fail to properly reload the kdump kernel. This has been handled by resetting the failure counter when doing such reloads. == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 == ---Problem Description--- kdump fails when crash is triggered after CPU add operation. Machine Type = na ---System Hang--- Crashed in early boot process of kdump kernel after crash Had to issue system reset from HMC to reclaim ---Steps to Reproduce--- 1. Configure kdump. 2. Add cpu from HMC. 3. Trigger crash. 4. Machine hangs after crash as below: --- [169250.213166] IPI complete [169250.234331] kexec: Starting switchover sequence. I'm in purgatory --- STRUCK HERE --- ---uname output--- na ---Debugger--- A debugger is not configured == Comment: #1 - Hari Krishna Bathini - 2019-05-10 05:56:46 == The problem is, kexec udev rule to restart kdump-tools service - when a core is added, is not being triggered. The old DT created by kexec (before the core is added) is being used by KDump Kernel. So, when system crashes on a thread from the added core(s), KDump kernel is failing to get the 'boot_cpuid' and eventually failing to boot.. == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 == The udev rule when CPU is added is not triggered because ppc64 does not eject add/remove event when a CPU is hot added/removed. It only ejects online/offline event to user space when CPU is hot added/removed. So, the below udev rules are never triggered when needed: SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart kdump-tools.service" SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart kdump-tools.service" Also, with how CPU hot add & remove are handled in ppc64, a udev trigger to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU hot add case by updating the udev rule and drop the udev rule meant for CPU hot remove in the kdump udev rules file: SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try- restart kdump-tools.service" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856323] Autopkgtest regression report (makedumpfile/1:1.6.6-2ubuntu2)
All autopkgtests for the newly accepted makedumpfile (1:1.6.6-2ubuntu2) for
eoan have finished running.
The following regressions have been reported in tests triggered by the package:
makedumpfile/1:1.6.6-2ubuntu2 (i386, ppc64el)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#makedumpfile
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1856323
Title:
kdump-tools is unable to resolve DNS when systemd-resolved is used
Status in makedumpfile package in Ubuntu:
Fix Released
Status in makedumpfile source package in Bionic:
In Progress
Status in makedumpfile source package in Disco:
Won't Fix
Status in makedumpfile source package in Eoan:
Fix Committed
Status in makedumpfile source package in Focal:
Fix Released
Bug description:
[Impact]
* Currently kdump is unable to handle domain name resolution due to
the lack of "resolved" service in the kdump environment; this happens
given the nature of reduced service load required in the kdump
scenario.
* Kdump currently relies on a systemd service approach - there are 2
services, one being a configuration/load entity (kdump-tools.service)
whereas the other is the crash dump service itself (kdump-tools-
dump.service). Due to the complexity and risk in booting a machine
after a kernel crash to collect kernel dump, it's expected kdump-
tools-dump to load the minimal possible amount of services. In order
to achieve that, kdump-tools-dump relies only in the sysinit and
network-online targets.
* The systemd DNS tool ("resolved") is not ready in the moment kdump-
tools-dump service is up to collect the kernel dump; also, "resolved"
depends on dbus.socket to work, so to have a fully functional DNS
resolution we are hereby adding both services as dependencies for
kdump-tools-dump, so the network dump functionality works with
hostnames (not requiring anymore that users set IP raw addresses).
* The attached SVG files (kdump.svg and regular_boot.svg) contains
"systemd-analyze plot" outputs from a kdump-tools-dump and regular
boot perspective. To collect the kdump data we manage to change the
kdump-tools-dump service to load SSHd and also that required disabling
the OneShot property of such service. With that data, one can check
the services started/completed in each environment - it's possible to
notice the absence of systemd-resolved when in kdump environment.
* Notice this modification is being worked concurrently with other
kdump-tools' changes in LP #1828596.
[Test Case]
1) Deploy a Bionic VM e.g. with uvt-kvm;
2) Set-up console output in the guest;
3) Install the kdump-tools package;
4) Configure a network dump (SSH or NFS) using hostnames for the target
machine;
5) Perform the test dump (with 'echo c> /proc/sysrq-trigger') and watch the
failure in name resolution,
[Regression Potential]
* The modifications hereby proposed are minimal and scope-constrained to
kdump-tools package; it'll only affect the services loaded before
kdump-tools-dump collecting service.
A regression would then potentially fails kdump completion if one of the new
services added to the kdump environment load (resolved and dbus.socket) fails
to load and stalls/prevents the kdump service complete load.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1856323/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859472] Re: Connect Wifi on oem.1066 kernel locks up
David, do you have any iwlwifi dkms installed? Please open a terminal and run 'dkms status', then post the output in this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859472 Title: Connect Wifi on oem.1066 kernel locks up Status in linux package in Ubuntu: Confirmed Bug description: If I attempt to connect to a wifi location on the Lenovo P53 or Lenovo P73 when using the 1066 oem kernel the system locks up. If I reboot back to the 1059 kernel all is working fine --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: z 2338 F pulseaudio /dev/snd/controlC0: z 2338 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20191017-183+sutton-mccarthy-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-13 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20191017-14:35 IwConfig: lono wireless extensions. wlp82s0 no wireless extensions. enp0s31f6 no wireless extensions. MachineType: LENOVO 20QNZ4RCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1066-oem root=UUID=8634c580-655e-4b92-93f7-93a3a39face2 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1066-oem N/A linux-backports-modules-4.15.0-1066-oem N/A linux-firmware 1.173.14 Tags: bionic Uname: Linux 4.15.0-1066-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET26W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QNZ4RCUS dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET26W(1.11):bd08/02/2019:svnLENOVO:pn20QNZ4RCUS:pvrThinkPadP53:rvnLENOVO:rn20QNZ4RCUS:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53 dmi.product.name: 20QNZ4RCUS dmi.product.version: ThinkPad P53 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859472] Re: Connect Wifi on oem.1066 kernel locks up
Hi David: Please update the backports-iwlwifi package to the newer one: https://launchpad.net/ubuntu/bionic/+upload/22621360/+files/backport-iwlwifi-dkms_7906-0ubuntu3~18.04.1_all.deb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859472 Title: Connect Wifi on oem.1066 kernel locks up Status in linux package in Ubuntu: Confirmed Bug description: If I attempt to connect to a wifi location on the Lenovo P53 or Lenovo P73 when using the 1066 oem kernel the system locks up. If I reboot back to the 1059 kernel all is working fine --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: z 2338 F pulseaudio /dev/snd/controlC0: z 2338 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20191017-183+sutton-mccarthy-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-13 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20191017-14:35 IwConfig: lono wireless extensions. wlp82s0 no wireless extensions. enp0s31f6 no wireless extensions. MachineType: LENOVO 20QNZ4RCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1066-oem root=UUID=8634c580-655e-4b92-93f7-93a3a39face2 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1066-oem N/A linux-backports-modules-4.15.0-1066-oem N/A linux-firmware 1.173.14 Tags: bionic Uname: Linux 4.15.0-1066-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET26W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QNZ4RCUS dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET26W(1.11):bd08/02/2019:svnLENOVO:pn20QNZ4RCUS:pvrThinkPadP53:rvnLENOVO:rn20QNZ4RCUS:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53 dmi.product.name: 20QNZ4RCUS dmi.product.version: ThinkPad P53 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858526] Re: eoan/linux-oracle: -proposed tracker
** Tags removed: kernel-sru-derivative-of-1858528 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- - kernel-stable-master-bug: 1858528 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Holding before Packaging phase-changed: Tuesday, 07. January 2020 01:39 UTC reason: prepare-package: Holding -- waiting for master bug trackers: bionic/linux-oracle-5.3: bug 1858525 variant: debs ** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux-oracle (Ubuntu Eoan) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1858526 Title: eoan/linux-oracle: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-lrm series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Eoan: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Holding before Packaging phase-changed: Tuesday, 07. January 2020 01:39 UTC reason: prepare-package: Holding -- waiting for master bug trackers: bionic/linux-oracle-5.3: bug 1858525 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858524] Re: eoan/linux-kvm: -proposed tracker
** Tags removed: kernel-sru-derivative-of-1858528 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- - kernel-stable-master-bug: 1858528 packages: main: linux-kvm meta: linux-meta-kvm phase: Holding before Packaging phase-changed: Tuesday, 07. January 2020 01:39 UTC reason: prepare-package: Holding -- waiting for master bug variant: debs ** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux-kvm (Ubuntu Eoan) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1858524 Title: eoan/linux-kvm: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Eoan: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: main: linux-kvm meta: linux-meta-kvm phase: Holding before Packaging phase-changed: Tuesday, 07. January 2020 01:39 UTC reason: prepare-package: Holding -- waiting for master bug variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858524/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858523] Re: eoan/linux-gcp: -proposed tracker
** Tags removed: kernel-sru-derivative-of-1858528 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- - kernel-stable-master-bug: 1858528 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Packaging phase-changed: Tuesday, 07. January 2020 01:39 UTC reason: prepare-package: Holding -- waiting for master bug trackers: bionic/linux-gcp-5.3: bug 1858522 variant: debs ** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux-gcp (Ubuntu Eoan) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1858523 Title: eoan/linux-gcp: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-lrm series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Eoan: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Packaging phase-changed: Tuesday, 07. January 2020 01:39 UTC reason: prepare-package: Holding -- waiting for master bug trackers: bionic/linux-gcp-5.3: bug 1858522 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858523/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858521] Re: eoan/linux-azure: -proposed tracker
** Tags removed: kernel-sru-derivative-of-1858528 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- - kernel-stable-master-bug: 1858528 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Packaging phase-changed: Tuesday, 07. January 2020 01:38 UTC reason: prepare-package: Holding -- waiting for master bug trackers: bionic/linux-azure-5.3: bug 1858520 variant: debs ** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux-azure (Ubuntu Eoan) Status: Confirmed => Invalid -- 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/1858521 Title: eoan/linux-azure: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-lrm series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Eoan: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Packaging phase-changed: Tuesday, 07. January 2020 01:38 UTC reason: prepare-package: Holding -- waiting for master bug trackers: bionic/linux-azure-5.3: bug 1858520 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858572] Re: xenial/linux-gcp: -proposed tracker
** Tags removed: kernel-sru-backport-of-1858576 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- - kernel-stable-master-bug: 1858576 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Packaging phase-changed: Tuesday, 07. January 2020 03:22 UTC reason: prepare-package: Holding -- waiting for master bug trackers: xenial/linux-gcp/gcp-kernel: bug 1858570 xenial/linux-gcp/gke-kernel: bug 1858571 variant: debs ** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux-gcp (Ubuntu Xenial) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1858572 Title: xenial/linux-gcp: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Packaging phase-changed: Tuesday, 07. January 2020 03:22 UTC reason: prepare-package: Holding -- waiting for master bug trackers: xenial/linux-gcp/gcp-kernel: bug 1858570 xenial/linux-gcp/gke-kernel: bug 1858571 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
