[Kernel-packages] [Bug 1845797]

[jon.reeve]

This issue persists even after the latest (March 2020) BIOS update from
Lenovo. I posted about this here on the Lenovo forums:

https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/After-latest-
BIOS-update-audio-not-working-on-Yoga-C930/m-p/5009564

Is our only hope getting the Lenovo BIOS devs to release a fix? Can we
fix this in the BIOS ourselves?

I rate the probability of ever hearing from Lenovo about this at around
0%.

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

Title:
  Microphone not detected Lenovo Yoga S940

Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo
  Yoga S940

  Attached the screen of gnome sound control panel.

  Inxi output:

  System:Host:  Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: 
Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) 
  Machine:   Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga 
S940-14IWL serial:  
 Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial:  UEFI: LENOVO v: AKCN34WW date: 06/12/2019 
  CPU:   Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT 
MCP L2 cache: 8192 KiB 
 Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 
2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 
 8: 2229 
  Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: 
snd_hda_intel 
 Sound Server: ALSA v: k5.3.0-13-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniele2239 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-12 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q7
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-13-generic N/A
   linux-backports-modules-5.3.0-13-generic  N/A
   linux-firmware1.182
  Tags:  eoan
  Uname: Linux 5.3.0-13-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago)
  UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AKCN34WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S940-14IWL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL:
  dmi.product.family: Yoga S940-14IWL
  dmi.product.name: 81Q7
  dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL
  dmi.product.version: Lenovo Yoga S940-14IWL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1855954] Re: [TGL] VMD support in TGL

[You-Sheng Yang]

PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1855954

** Tags added: oem-priority originate-from-1872769 somerville

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1855954

Title:
  [TGL] VMD support in TGL

Status in HWE Next:
  New
Status in intel:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Description:
  VMD support in Tiger Lake Platform

  Target Kernel: TBD
  Target Release: 20.04

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

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

[Kernel-packages] [Bug 1873123] Re: Missing support for Intel VMD device 8086:9A0B

[You-Sheng Yang]

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

** This bug has been marked a duplicate of bug 1855954
   [TGL] VMD support in TGL

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

Title:
  Missing support for Intel VMD device 8086:9A0B

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Intel VMD device 8086:9A0B is not recognized in Focal Fossa.

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

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

[Kernel-packages] [Bug 1872984] Re: RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

[Kai-Heng Feng]

Please test kernel here:
https://people.canonical.com/~khfeng/lp1872984/

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1872984

Title:
  RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04
  - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  RTL8822BE crashes after rtw_pci starts on boot after kernel update to
  5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is
  still present on latest mainline kernel version
  5.7.0-050700rc1-generic .

  [   10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0
  [   10.714544] [ cut here ]
  [   10.714545] failed to read DBI register, addr=0x0719
  [   10.714577] WARNING: CPU: 0 PID: 939 at 
drivers/net/wireless/realtek/rtw88/pci.c:1156 
rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714577] Modules linked in: (see attached dmesg)
  [   10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 
5.7.0-050700rc1-generic #202004122032
  [   10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 
01/23/2018
  [   10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 
31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 
fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00
  [   10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282
  [   10.714618] RAX:  RBX:  RCX: 
0007
  [   10.714619] RDX: 0007 RSI: 0092 RDI: 
933cc9e19c80
  [   10.714619] RBP: b466007e7898 R08: 03d2 R09: 
0004
  [   10.714620] R10:  R11: 0001 R12: 
933cbdf31ea0
  [   10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: 

  [   10.714622] FS:  7fbcedc6efc0() GS:933cc9e0() 
knlGS:
  [   10.714622] CS:  0010 DS:  ES:  CR0: 80050033
  [   10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 
003606f0
  [   10.714623] Call Trace:
  [   10.714627]  rtw_pci_link_ps+0x4e/0x90 [rtwpci]
  [   10.714630]  ? _raw_spin_unlock_bh+0x1e/0x20
  [   10.714637]  rtw_leave_ips+0x1f/0x80 [rtw88]
  [   10.714640]  rtw_ops_config+0xa3/0xe0 [rtw88]
  [   10.714658]  ieee80211_hw_config+0x95/0x390 [mac80211]
  [   10.714669]  ieee80211_recalc_idle+0x27/0x30 [mac80211]
  [   10.714679]  __ieee80211_start_scan+0x334/0x750 [mac80211]
  [   10.714688]  ieee80211_request_scan+0x30/0x50 [mac80211]
  [   10.714699]  ieee80211_scan+0x5c/0xa0 [mac80211]
  [   10.714719]  nl80211_trigger_scan+0x59a/0x6c0 [cfg80211]
  [   10.714722]  genl_rcv_msg+0x1a8/0x470
  [   10.714724]  ? ep_poll_callback+0x2a0/0x2c0
  [   10.714725]  ? genl_family_rcv_msg_attrs_parse+0x100/0x100
  [   10.714726]  netlink_rcv_skb+0x50/0x120
  [   10.714728]  genl_rcv+0x29/0x40
  [   10.714729]  netlink_unicast+0x1a8/0x250
  [   10.714730]  netlink_sendmsg+0x233/0x460
  [   10.714739]  ? _copy_from_user+0x31/0x60
  [   10.714750]  sock_sendmsg+0x65/0x70
  [   10.714751]  sys_sendmsg+0x212/0x280
  [   10.714752]  ? copy_msghdr_from_user+0x5c/0x90
  [   10.714755]  ? __check_object_size+0x4d/0x150
  [   10.714756]  ___sys_sendmsg+0x81/0xc0
  [   10.714757]  ? __check_object_size+0x4d/0x150
  [   10.714759]  ? unix_ioctl+0x99/0x180
  [   10.714760]  ? sock_getsockopt+0x198/0xc04
  [   10.714761]  ? sock_do_ioctl+0x47/0x140
  [   10.714763]  ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0
  [   10.714765]  ? _cond_resched+0x19/0x30
  [   10.714767]  ? aa_sk_perm+0x43/0x1b0
  [   10.714768]  __sys_sendmsg+0x5c/0xa0
  [   10.714770]  __x64_sys_sendmsg+0x1f/0x30
  [   10.714772]  do_syscall_64+0x57/0x1b0
  [   10.714773]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   10.714774] RIP: 0033:0x7fbcedffb5b7
  [   10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 
f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10
  [   10.714776] RSP: 002b:7fff88e22288 EFLAGS: 0246 ORIG_RAX: 
002e
  [   10.714777] RAX: ffda RBX: 5632787355d0 RCX: 
7fbcedffb5b7
  [   10.714777] RDX:  RSI: 7fff88e222c0 RDI: 
0006
  [   10.714778] RBP: 563278761380 R08: 0004 R09: 
563278761380
  [   10.714778] R10: 7fff88e22394 R11: 0246 R12: 
5632787354e0
  [   10.714779] R13: 7fff88e222c0 R14: 7fff88e22394 R15: 
563278766710
  [   10.714780] ---[ end trace f00c16109236af6f ]---
  [   10.714782] rtw_pci :3a:00.0: failed to read ASPM, ret=-5

  
  Device is unable to scan for 

[Kernel-packages] [Bug 1869672] Re: kdump kernel can't be loaded using kernel 4.15.0-76

[yamato]

Guilherme,

I'm so glad to hear it. Thanks a lot for your effort!

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

Title:
  kdump kernel can't be loaded using kernel 4.15.0-76

Status in makedumpfile package in Ubuntu:
  New

Bug description:
  Thank you for reading this report.
  This may caused by bugs in kernel, not in kdump. If so, I will report this to 
kernel team.
  I need your comment to solve this.

  [Impact]
  * Kdump kernel can't be loaded using linux kernel 4.15.0-76.

  [Environment]
  Description:Ubuntu 18.04.4 LTS
  Release:18.04

  uname:
  Linux ubuntu 4.15.0-76-generic #86-Ubuntu SMP Fri Jan 17 17:24:28 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  Secure boot is enabled.

  Versions:
  * kexec-tools/bionic-updates,now 1:2.0.16-1ubuntu1.1
  * kdump-tools/bionic-updates,now 1:1.6.5-1ubuntu1~18.04.4

  [Test case]
  1)After OS booted, run systemctl status kdump-tools shows these messages 
below:

  
  ● kdump-tools.service - Kernel crash dump capture service
     Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
preset: enabled)
     Active: active (exited) since Fri 2020-03-27 16:40:31 JST; 5min ago
    Process: 895 ExecStart=/etc/init.d/kdump-tools start (code=exited, 
status=0/SUCCESS)
   Main PID: 895 (code=exited, status=0/SUCCESS)

  Mar 27 16:40:31 ubuntu systemd[1]: Starting Kernel crash dump capture 
service...
  Mar 27 16:40:31 ubuntu kdump-tools[895]: Starting kdump-tools:  * Creating 
symlink /var/lib/kdump/vmlinuz
  Mar 27 16:40:31 ubuntu kdump-tools[895]:  * Creating symlink 
/var/lib/kdump/initrd.img
  Mar 27 16:40:31 ubuntu kdump-tools[895]: kexec_file_load failed: Exec format 
error
  Mar 27 16:40:31 ubuntu kdump-tools[895]:  * failed to load kdump kernel
  Mar 27 16:40:31 ubuntu systemd[1]: Started Kernel crash dump capture service.
  

  2)Run kexec directly:
  $ sudo /sbin/kexec -p --command-line="/boot/vmlinuz-4.15.0-76-generic 
root=UUID=29a89ad8-8923-435e-a88c-aaf5cb379568 ro mce=ignore_ce reset_devices 
systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb 
ata_piix.prefer_ms_hyperv=0" --initrd=/boot/initrd.img-4.15.0-76-generic 
/boot/vmlinuz-4.15.0-64-generic

  Then,these messages are shown:
  Cannot open /proc/kcore: Operation not permitted
  Cannot read /proc/kcore: Operation not permitted
  Cannot load /boot/vmlinuz-4.15.0-76-generic

  On dmesg, these messages are shown:
  
  [  538.524718] Lockdown: /proc/kcore is restricted; see man kernel_lockdown.7
  

  3) Changing OS kernel to older one(I used 4.15.0-64), kdump kernel can
  be loaded.

  $ sudo systemctl status kdump-tools
  ● kdump-tools.service - Kernel crash dump capture service
     Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
preset: enabled)
     Active: active (exited) since Wed 2020-03-25 13:39:03 JST; 5 days ago
   Main PID: 832 (code=exited, status=0/SUCCESS)
  Tasks: 0 (limit: 4915)
     CGroup: /system.slice/kdump-tools.service

  Mar 25 13:39:02 ubuntu systemd[1]: Starting Kernel crash dump capture 
service...
  Mar 25 13:39:02 ubuntu kdump-tools[832]: Starting kdump-tools:  * Creating 
symlink /var/lib/kdump/vmlinuz
  Mar 25 13:39:02 ubuntu kdump-tools[832]:  * Creating symlink 
/var/lib/kdump/initrd.img
  Mar 25 13:39:03 ubuntu kdump-tools[832]:  * loaded kdump kernel
  Mar 25 13:39:03 ubuntu kdump-tools[938]: loaded kdump kernel
  Mar 25 13:39:03 ubuntu systemd[1]: Started Kernel crash dump capture service.

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

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

[Kernel-packages] [Bug 1855954] Re: [TGL] VMD support in TGL

[Anthony Wong]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

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

Title:
  [TGL] VMD support in TGL

Status in intel:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:
  VMD support in Tiger Lake Platform

  Target Kernel: TBD
  Target Release: 20.04

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

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

[Kernel-packages] [Bug 1873054] Re: Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests

[Po-Hsu Lin]

** Tags added: ubuntu-kernel-selftests

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

Title:
  Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete

Bug description:
  In Focal,

  The following tests fail on baremetal/amd64:

  04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer  
[FAIL]
  04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer   
[FAIL]
  04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test 
inter-event histogram trigger expected fail actions[XFAIL]

  Full output below.

  04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests ===
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check   
[PASS]
  04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing 
check[PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer 
size   [PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing 
setting [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and 
trace_marker  [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - 
add/remove kprobe events [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - 
add/remove synthetic events  [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - 
selective clear (compatibility) [PASS]
  04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - 
generic clear event [PASS]
  04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - 
enable/disable with event level files   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - 
restricts events based on pid   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - 
enable/disable with subsystem level files   [PASS]
  04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - 
enable/disable with top level files [PASS]
  04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from 
module   [PASS]
  04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph 
filters with stack tracer   [PASS]
  04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph 
filters [PASS]
  04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid 
filters   [PASS]
  04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace 
filter command  [PASS]
  04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace 
with cpumask[PASS]
  04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for 
function event triggers   [PASS]
  04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace 
on module   [PASS]
  04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function 
profiling [PASS]
  04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function 
profiler with function tracing[PASS]
  04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading 
of set_ftrace_filter  [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for 
function traceon/off triggers [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing 
error log support [PASS]
  04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and 
deletion of trace instances while setting an event[PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and 
deletion of trace instances   [PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - 
adding and removing  [PASS]
  04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32] Kprobe dynamic event - 
busy event check [PASS]
  04/12 03:26:14 DEBUG| utils:0153| [stdout] # [33] Kprobe dynamic event 
with arguments [PASS]
  04/12 03:26:15 DEBUG| utils:0153| [stdout] # [34] Kprobe event with comm 
arguments[PASS]
  04/12 03:26:15 DEBUG| utils:0153| [stdout] # [35] Kprobe event string 
type argument   [PASS]
  04/12 03:26:16 DEBUG| utils:0153| [stdout] # [36] Kprobe event symbol 
argument[PASS]
  04/12 03:26:18 DEBUG| utils:0153| [stdout] # [37] Kprobe event argument 
syntax[PASS]
  04/12 03:26:20 DEBUG| utils:0153| [stdout] # [38] 

[Kernel-packages] [Bug 1873123] Re: Missing support for Intel VMD device 8086:9A0B

[You-Sheng Yang]

PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1873123

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

Title:
  Missing support for Intel VMD device 8086:9A0B

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Intel VMD device 8086:9A0B is not recognized in Focal Fossa.

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

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

[Kernel-packages] [Bug 1872383] Re: blk_update_request error when mount nvme partition

[Anthony Wong]

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

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

Title:
  blk_update_request error when mount nvme partition

Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Can't install on this nvme with a focal server installer.

  As mount a nvme partition with kernel with focal 5.4.0-21-generic kernel
  endless blk_update_request error will exists in kernel dmesg.
  the nvme module: PC400 NVMe SK hynix 512GB

  While mount nvme module: PC SN720 NVMe WDC 256GB, there is no such issue.
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-21-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-01 (11 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200330)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 06c4:c401 Bizlink International Corp. DisplayPort ALT 
mode device
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
   |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 3: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
  MachineType: Dell Inc. Precision 3930 Rack
  Package: linux-generic 5.4.0.21.25
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=2b73a661-f0a8-453a-ac0d-b93c5eb97f8d ro
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 02/05/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.0:bd02/05/2020:svnDellInc.:pnPrecision3930Rack:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3930 Rack
  dmi.product.sku: 0873
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1872383/+subscriptions

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

[Kernel-packages] [Bug 1873123] Re: Missing support for Intel VMD device 8086:9A0B

[You-Sheng Yang]

** Tags added: oem-priority originate-from-1872769 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/1873123

Title:
  Missing support for Intel VMD device 8086:9A0B

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Intel VMD device 8086:9A0B is not recognized in Focal Fossa.

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

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

[Kernel-packages] [Bug 1873123] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1873123

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

Title:
  Missing support for Intel VMD device 8086:9A0B

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Intel VMD device 8086:9A0B is not recognized in Focal Fossa.

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

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

[Kernel-packages] [Bug 1873123] [NEW] Missing support for Intel VMD device 8086:9A0B

[You-Sheng Yang]

Public bug reported:

Intel VMD device 8086:9A0B is not recognized in Focal Fossa.

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

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

Title:
  Missing support for Intel VMD device 8086:9A0B

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Intel VMD device 8086:9A0B is not recognized in Focal Fossa.

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

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

[Kernel-packages] [Bug 1846305] Re: generic/397 from ubuntu_xfstests_ext4 failed

[Po-Hsu Lin]

** Summary changed:

- generic/397 from ubuntu_xfstests_ext4 failed on D
+ generic/397 from ubuntu_xfstests_ext4 failed

** Tags added: 5.4

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

Title:
  generic/397 from ubuntu_xfstests_ext4 failed

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Issue found on node amd64 node "gonzo"

   generic/397- output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/397.out.bad)
   --- tests/generic/397.out  2019-10-01 07:38:07.080386390 +
   +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/397.out.bad
   2019-10-01 13:01:22.850581563 +
   @@ -1,4 +1,5 @@
QA output created by 397
   +keyctl_session_to_parent: Operation not permitted
stat: cannot stat 'SCRATCH_MNT/edir/empty': No such file or directory 
stat: cannot stat 'SCRATCH_MNT/edir/symlink': No such file or directory
8
   ...
   (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/tests/generic/397.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/397.out.bad'
  to see the entire diff) 

  
  $ cat 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/397.out.bad
  QA output created by 397
  keyctl_session_to_parent: Operation not permitted
  stat: cannot stat 'SCRATCH_MNT/edir/empty': No such file or directory
  stat: cannot stat 'SCRATCH_MNT/edir/symlink': No such file or directory
  8
  1
  Required key not available
  SCRATCH_MNT/edir/newfile: Required key not available
  SCRATCH_MNT/edir/0123456789abcdef: Required key not available
  mkdir: cannot create directory 'SCRATCH_MNT/edir/newdir': Required key not 
available
  mkdir: cannot create directory 'SCRATCH_MNT/edir/0123456789abcdef': Required 
key not available
  ln: failed to create symbolic link 'SCRATCH_MNT/edir/newlink': Required key 
not available
  ln: failed to create symbolic link 'SCRATCH_MNT/edir/0123456789abcdef': 
Required key not available
  stat: cannot stat 'SCRATCH_MNT/edir': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-29-generic 5.0.0-29.31
  ProcVersionSignature: User Name 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct  1 11:07 seq
   crw-rw 1 root audio 116, 33 Oct  1 11:07 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [68184.314209] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [68184.315939] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed Oct  2 07:32:58 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R415
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=3e0e190e-d425-4d00-a9a9-deb0c452399b ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.178.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.3
  dmi.board.name: 08WNM9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.3:bd04/26/2012:svnDellInc.:pnPowerEdgeR415:pvr:rvnDellInc.:rn08WNM9:rvrA02:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R415
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1846305/+subscriptions

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

[Kernel-packages] [Bug 1867587] Re: [sas-0316]sync mainline kernel 5.6rc1 sas patchset into ubuntu HWE kernel branch

[Fred Kimmy]

** Summary changed:

- [sas-0316]sync mainline kernel 5.6rc1 roce patchset into ubuntu HWE kernel 
branch
+ [sas-0316]sync mainline kernel 5.6rc1 sas patchset into ubuntu HWE kernel 
branch

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

Title:
  [sas-0316]sync mainline kernel 5.6rc1 sas patchset into ubuntu HWE
  kernel branch

Status in kunpeng920:
  Fix Committed
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Committed
Status in kunpeng920 ubuntu-20.04 series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  [Bug Description]
  SAS patchset have merged into mainline 5.6rc1 kernel.

  [Steps to Reproduce]
1)
2)
3)

  [Actual Results]

  [Expected Results]

  [Reproducibility]

  [Additional information]
(Firmware version, kernel version, affected hardware, etc. if required):

  [Resolution]
  scsi: hisi_sas: Rename hisi_sas_cq.pci_irq_mask
  scsi: hisi_sas: Add prints for v3 hw interrupt converge and automatic affinity
  scsi: hisi_sas: Modify the file permissions of trigger_dump to write only
  scsi: hisi_sas: Replace magic number when handle channel interrupt
  scsi: hisi_sas: replace spin_lock_irqsave/spin_unlock_restore with 
spin_lock/spin_unlock
  scsi: hisi_sas: use threaded irq to process CQ interrupts

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

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

[Kernel-packages] [Bug 1872383] Re: blk_update_request error when mount nvme partition

[Yuan-Chen Cheng]

** Description changed:

+ Can't install on this nvme with a focal server installer.
+ 
  As mount a nvme partition with kernel with focal 5.4.0-21-generic kernel
  endless blk_update_request error will exists in kernel dmesg.
  the nvme module: PC400 NVMe SK hynix 512GB
  
  While mount nvme module: PC SN720 NVMe WDC 256GB, there is no such issue.
- --- 
+ ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-21-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-01 (11 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200330)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 06c4:c401 Bizlink International Corp. DisplayPort ALT 
mode device
-  Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 06c4:c401 Bizlink International Corp. DisplayPort ALT 
mode device
+  Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
-  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M
-  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
-  |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
-  |__ Port 3: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
-  |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
+  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M
+  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
+  |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
+  |__ Port 3: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
+  |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
  MachineType: Dell Inc. Precision 3930 Rack
  Package: linux-generic 5.4.0.21.25
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=2b73a661-f0a8-453a-ac0d-b93c5eb97f8d ro
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
-  linux-restricted-modules-5.4.0-21-generic N/A
-  linux-backports-modules-5.4.0-21-generic  N/A
-  linux-firmware1.187
+  linux-restricted-modules-5.4.0-21-generic N/A
+  linux-backports-modules-5.4.0-21-generic  N/A
+  linux-firmware1.187
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
-  
+ 
  _MarkForUpload: True
  dmi.bios.date: 02/05/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.0:bd02/05/2020:svnDellInc.:pnPrecision3930Rack:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3930 Rack
  dmi.product.sku: 0873
  dmi.sys.vendor: Dell Inc.

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

Title:
  blk_update_request error when mount nvme partition

Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Can't install on this nvme with a focal server installer.

  As mount a nvme partition with kernel with focal 5.4.0-21-generic kernel
  endless blk_update_request error will exists in kernel dmesg.
  the nvme module: PC400 NVMe SK hynix 512GB

  While mount nvme module: PC SN720 NVMe WDC 256GB, there is no such issue.
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-21-generic.
 

[Kernel-packages] [Bug 1837035] Re: memcg_stat_rss from controllers in ubuntu_ltp failed

[Po-Hsu Lin]

** No longer affects: linux-aws (Ubuntu Disco)

** No longer affects: linux (Ubuntu Disco)

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

Title:
  memcg_stat_rss from controllers in ubuntu_ltp failed

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New

Bug description:
  This issue was spotted on an i386 node "pepe" with Disco kernel,
  it failed with:

  memcg_process: shmget() failed: Invalid argument
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process

  memcg_stat_rss 4 TFAIL: Process 1845 exited with 1 after warm up

  
  <<>>
  tag=memcg_stat_rss stime=1563448062
  cmdline="memcg_stat_rss.sh"
  contacts=""
  analysis=exit
  <<>>
  memcg_stat_rss 1 TINFO: Starting test 1
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 1 TINFO: Running memcg_process --mmap-anon -s 135168
  memcg_stat_rss 1 TINFO: Warming up pid: 1784
  memcg_stat_rss 1 TINFO: Process is still here after warm up: 1784
  memcg_stat_rss 1 TPASS: rss is 135168 as expected
  memcg_stat_rss 2 TINFO: Starting test 2
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 2 TINFO: Running memcg_process --mmap-file -s 4096
  memcg_stat_rss 2 TINFO: Warming up pid: 1804
  memcg_stat_rss 2 TINFO: Process is still here after warm up: 1804
  memcg_stat_rss 2 TPASS: rss is 0 as expected
  memcg_stat_rss 3 TINFO: Starting test 3
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 3 TINFO: Running memcg_process --shm -k 3 -s 4096
  memcg_stat_rss 3 TINFO: Warming up pid: 1825
  memcg_stat_rss 3 TINFO: Process is still here after warm up: 1825
  memcg_stat_rss 3 TPASS: rss is 0 as expected
  memcg_stat_rss 4 TINFO: Starting test 4
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 4 TINFO: Running memcg_process --mmap-anon --mmap-file --shm 
-s 135168
  memcg_stat_rss 4 TINFO: Warming up pid: 1845
  memcg_process: shmget() failed: Invalid argument
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process

  memcg_stat_rss 4 TFAIL: Process 1845 exited with 1 after warm up
  memcg_stat_rss 5 TINFO: Starting test 5
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 5 TINFO: Running memcg_process --mmap-lock1 -s 135168
  memcg_stat_rss 5 TINFO: Warming up pid: 1858
  memcg_stat_rss 5 TINFO: Process is still here after warm up: 1858
  memcg_stat_rss 5 TPASS: rss is 135168 as expected
  memcg_stat_rss 6 TINFO: Starting test 6
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 6 TINFO: Running memcg_process --mmap-anon -s 135168
  memcg_stat_rss 6 TINFO: Warming up pid: 1878
  memcg_stat_rss 6 TINFO: Process is still here after warm up: 1878
  memcg_stat_rss 6 TPASS: rss is 135168 as expected
  memcg_stat_rss 7 TPASS: rss is 0 as expected
  memcg_stat_rss 8 TINFO: Starting test 7
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 8 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 8 TINFO: Running memcg_process --mmap-file -s 4096
  memcg_stat_rss 8 TINFO: Warming up pid: 1901
  memcg_stat_rss 8 TINFO: Process is still here after warm up: 1901
  memcg_stat_rss 8 TPASS: rss is 0 as expected
  memcg_stat_rss 9 TPASS: rss is 0 as expected
  memcg_stat_rss 10 TINFO: Starting test 8
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 10 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 10 TINFO: Running memcg_process --shm -k 8 -s 4096
  memcg_stat_rss 10 TINFO: Warming up pid: 1925
  memcg_stat_rss 10 TINFO: Process is still here after warm up: 1925
  memcg_stat_rss 10 TPASS: rss is 0 as expected
  memcg_stat_rss 11 TPASS: rss is 0 as expected
  memcg_stat_rss 12 TINFO: Starting test 9
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 12 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 12 TINFO: Running memcg_process --mmap-anon --mmap-file --shm 
-s 135168
  memcg_stat_rss 12 TINFO: Warming up pid: 1948
  memcg_process: shmget() failed: Invalid argument
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process

  memcg_stat_rss 12 TFAIL: Process 1948 exited with 1 after warm up
  memcg_stat_rss 

[Kernel-packages] [Bug 1837035] Re: memcg_stat_rss from controllers in ubuntu_ltp failed with D i386 (timeout with D s390x zVM)

[Po-Hsu Lin]

This failure can be found on B-AWS-FIPS 4.15.0-2015.15-aws-fips with
instance c5.large as well.

** Summary changed:

- memcg_stat_rss from controllers in ubuntu_ltp failed with D i386 (timeout 
with D s390x zVM)
+ memcg_stat_rss from controllers in ubuntu_ltp failed

** Tags added: 4.15 aws bionic

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

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

Title:
  memcg_stat_rss from controllers in ubuntu_ltp failed

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Disco:
  Confirmed
Status in linux-aws source package in Disco:
  New

Bug description:
  This issue was spotted on an i386 node "pepe" with Disco kernel,
  it failed with:

  memcg_process: shmget() failed: Invalid argument
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process

  memcg_stat_rss 4 TFAIL: Process 1845 exited with 1 after warm up

  
  <<>>
  tag=memcg_stat_rss stime=1563448062
  cmdline="memcg_stat_rss.sh"
  contacts=""
  analysis=exit
  <<>>
  memcg_stat_rss 1 TINFO: Starting test 1
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 1 TINFO: Running memcg_process --mmap-anon -s 135168
  memcg_stat_rss 1 TINFO: Warming up pid: 1784
  memcg_stat_rss 1 TINFO: Process is still here after warm up: 1784
  memcg_stat_rss 1 TPASS: rss is 135168 as expected
  memcg_stat_rss 2 TINFO: Starting test 2
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 2 TINFO: Running memcg_process --mmap-file -s 4096
  memcg_stat_rss 2 TINFO: Warming up pid: 1804
  memcg_stat_rss 2 TINFO: Process is still here after warm up: 1804
  memcg_stat_rss 2 TPASS: rss is 0 as expected
  memcg_stat_rss 3 TINFO: Starting test 3
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 3 TINFO: Running memcg_process --shm -k 3 -s 4096
  memcg_stat_rss 3 TINFO: Warming up pid: 1825
  memcg_stat_rss 3 TINFO: Process is still here after warm up: 1825
  memcg_stat_rss 3 TPASS: rss is 0 as expected
  memcg_stat_rss 4 TINFO: Starting test 4
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 4 TINFO: Running memcg_process --mmap-anon --mmap-file --shm 
-s 135168
  memcg_stat_rss 4 TINFO: Warming up pid: 1845
  memcg_process: shmget() failed: Invalid argument
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process

  memcg_stat_rss 4 TFAIL: Process 1845 exited with 1 after warm up
  memcg_stat_rss 5 TINFO: Starting test 5
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 5 TINFO: Running memcg_process --mmap-lock1 -s 135168
  memcg_stat_rss 5 TINFO: Warming up pid: 1858
  memcg_stat_rss 5 TINFO: Process is still here after warm up: 1858
  memcg_stat_rss 5 TPASS: rss is 135168 as expected
  memcg_stat_rss 6 TINFO: Starting test 6
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 6 TINFO: Running memcg_process --mmap-anon -s 135168
  memcg_stat_rss 6 TINFO: Warming up pid: 1878
  memcg_stat_rss 6 TINFO: Process is still here after warm up: 1878
  memcg_stat_rss 6 TPASS: rss is 135168 as expected
  memcg_stat_rss 7 TPASS: rss is 0 as expected
  memcg_stat_rss 8 TINFO: Starting test 7
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 8 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 8 TINFO: Running memcg_process --mmap-file -s 4096
  memcg_stat_rss 8 TINFO: Warming up pid: 1901
  memcg_stat_rss 8 TINFO: Process is still here after warm up: 1901
  memcg_stat_rss 8 TPASS: rss is 0 as expected
  memcg_stat_rss 9 TPASS: rss is 0 as expected
  memcg_stat_rss 10 TINFO: Starting test 8
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 10 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 10 TINFO: Running memcg_process --shm -k 8 -s 4096
  memcg_stat_rss 10 TINFO: Warming up pid: 1925
  memcg_stat_rss 10 TINFO: Process is still here after warm up: 1925
  memcg_stat_rss 10 TPASS: rss is 0 as expected
  memcg_stat_rss 11 TPASS: rss is 0 as expected
  memcg_stat_rss 12 TINFO: Starting test 9
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 12 TINFO: set 

[Kernel-packages] [Bug 1872311] Re: Brightness hotkeys not working on Lenovo S740

[Alex Hung]

If ACPI approach is used, there are also two different approaches used -
ACPI standard or OEM-specific .

ACPI defines events from brightness up and down, and it is
video/brightnessdown BRTDN 0087 & video/brightnessup BRTUP 0086.
The can be checked by running "acpi_listen" and pressing brightness
hotkeys.

If OEM-specific events are used, it should be handled by platform driver
like "ideapad_laptop".

Would you mind sharing acpidump log (sudo acpidump > acpi.log) so more
analysis can be performed?

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

Title:
  Brightness hotkeys not working on Lenovo S740

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Brightness hotkeys (Fn + F11 for decrease and Fn + F12 for increase)
  do not work on Ubuntu 20.04 and Lenovo S740 laptop. The brightness
  hotkeys did not work on 19.10 either.

  I followed the guide here:
  https://wiki.ubuntu.com/Hotkeys/Troubleshooting

  In "Step-by-step Troubleshooting", none of the steps (1-7) did produce
  any reaction to brightness change key combinations. However, I am able
  to change the laptop screen brightness through the brightness applet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  elias  1447 F pulseaudio
   /dev/snd/controlC0:  elias  1447 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 16:12:01 2020
  InstallationDate: Installed on 2019-11-19 (144 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 81RS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=101c7da4-860d-4496-ae06-d98699795f9a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-04 (7 days ago)
  dmi.bios.date: 03/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BYCN33WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S740-14IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrBYCN33WW:bd03/10/2020:svnLENOVO:pn81RS:pvrLenovoYogaS740-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS740-14IIL:
  dmi.product.family: Yoga S740-14IIL
  dmi.product.name: 81RS
  dmi.product.sku: LENOVO_MT_81RS_BU_idea_FM_Yoga S740-14IIL
  dmi.product.version: Lenovo Yoga S740-14IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1872311] Re: Brightness hotkeys not working on Lenovo S740

[Alex Hung]

The brightness interface (/sys/class/backlight/intel_backlight) is
working, so it must be the missing events that cause your problem.

Ubuntu needs keycodes (KEY_BRIGHTNESSDOWN 224 & KEY_BRIGHTNESSUP 225),
and this can be from either scancode or ACPI events. Laptops usually use
ACPI for brightness, and this can be confirmed by pressing hotkeys while
running

   $ watch -n1 cat /proc/interrupts

Note: ACPI usually is on IRQ 9. Check whether interrupts increase with
brightness up/down presses.

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

Title:
  Brightness hotkeys not working on Lenovo S740

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Brightness hotkeys (Fn + F11 for decrease and Fn + F12 for increase)
  do not work on Ubuntu 20.04 and Lenovo S740 laptop. The brightness
  hotkeys did not work on 19.10 either.

  I followed the guide here:
  https://wiki.ubuntu.com/Hotkeys/Troubleshooting

  In "Step-by-step Troubleshooting", none of the steps (1-7) did produce
  any reaction to brightness change key combinations. However, I am able
  to change the laptop screen brightness through the brightness applet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  elias  1447 F pulseaudio
   /dev/snd/controlC0:  elias  1447 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 16:12:01 2020
  InstallationDate: Installed on 2019-11-19 (144 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 81RS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=101c7da4-860d-4496-ae06-d98699795f9a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-04 (7 days ago)
  dmi.bios.date: 03/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BYCN33WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S740-14IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrBYCN33WW:bd03/10/2020:svnLENOVO:pn81RS:pvrLenovoYogaS740-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS740-14IIL:
  dmi.product.family: Yoga S740-14IIL
  dmi.product.name: 81RS
  dmi.product.sku: LENOVO_MT_81RS_BU_idea_FM_Yoga S740-14IIL
  dmi.product.version: Lenovo Yoga S740-14IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1872351] Re: Qualcomm Atheros QCA6174 Killer 1435 Wireless-AC: Disabling wifi causes kernel warning in __sta_info_destroy_part2

[Alex Hung]

The same wifi used on one of the system I have, and I was able to
reproduce the same error once a while. When this warning message
occurred, the system wouldn't connect to my router, either.

I was able to workaround this by "sudo modprobe -r ath10k_pci ; sudo
modprobe ath10k_pci"

I compared kernel 5.4 (used in Ubuntu 20.04) and 5.7-rc1, and there
aren't fixes for this problem. The only patch that touches
"__sta_info_destroy_part2" is commit b16798f5b907733 (see
https://lore.kernel.org/linux-
wireless/20200326155133.ccb4fb0bb356.If48f0f0504efdcf16b8921f48c6d3bb2cb763c99@changeid/)

This patch has cc'ed stable, and it will eventually be included in 5.4.
A test kernel (Ubuntu-5.4.0-21.25 + b16798f5b907733) was built and is
available @ https://people.canonical.com/~alexhung/LP1872351/

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

Title:
  Qualcomm Atheros QCA6174 Killer 1435 Wireless-AC: Disabling wifi
  causes kernel warning in __sta_info_destroy_part2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have multiple issues with wifi on my Dell XPS 9380.
  This error was triggered when I tried to disable my wifi.

  [ 3634.322471] [ cut here ]
  [ 3634.322524] WARNING: CPU: 3 PID: 1188 at net/mac80211/sta_info.c:1057 
__sta_info_destroy_part2+0x14e/0x160 [mac80211]
  [ 3634.322525] Modules linked in: rfcomm vboxnetadp(OE) vboxnetflt(OE) 
vboxdrv(OE) ccm typec_displayport cmac algif_hash algif_skcipher af_alg bnep 
binfmt_misc nls_iso8859_1 mei_hdcp intel_rapl_msr snd_hda_codec_hdmi 
dell_laptop snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio 
snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core snd_usb_audio 
ath10k_pci x86_pkg_temp_thermal snd_usbmidi_lib snd_seq_midi snd_hwdep 
snd_seq_midi_event ath10k_core intel_powerclamp coretemp cdc_ether snd_rawmidi 
usbnet btusb kvm_intel r8152 ath btrtl mii btbcm kvm snd_seq uvcvideo 
videobuf2_vmalloc btintel videobuf2_memops intel_cstate videobuf2_v4l2 joydev 
snd_seq_device snd_pcm dell_wmi intel_rapl_perf videobuf2_common bluetooth 
mac80211 dell_smbios videodev snd_timer dcdbas mc input_leds ecdh_generic ecc 
wmi_bmof snd dell_wmi_descriptor serio_raw intel_wmi_thunderbolt cfg80211 
soundcore rtsx_pci_ms libarc4 memstick hid_multitouch processor_thermal_device 
ucsi_acpi typec_ucsi mei_me intel_rapl_common
  [ 3634.322564]  intel_xhci_usb_role_switch mei typec intel_soc_dts_iosf 
intel_pch_thermal roles int3403_thermal int340x_thermal_zone int3400_thermal 
mac_hid acpi_pad intel_hid acpi_thermal_rel sparse_keymap sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 mmc_block dm_crypt 
usbhid hid_generic crct10dif_pclmul crc32_pclmul rtsx_pci_sdmmc i915 
ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_algo_bit glue_helper 
drm_kms_helper psmouse syscopyarea sysfillrect nvme sysimgblt i2c_i801 
fb_sys_fops nvme_core drm intel_lpss_pci rtsx_pci intel_lpss idma64 i2c_hid 
virt_dma wmi hid pinctrl_sunrisepoint video pinctrl_intel
  [ 3634.322599] CPU: 3 PID: 1188 Comm: NetworkManager Tainted: G   OE  
   5.4.0-21-generic #25-Ubuntu
  [ 3634.322600] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.12.1 
12/11/2019
  [ 3634.322633] RIP: 0010:__sta_info_destroy_part2+0x14e/0x160 [mac80211]
  [ 3634.322635] Code: 24 0c 01 00 00 00 0f 84 52 ff ff ff 45 31 c0 b9 01 00 00 
00 4c 89 e2 48 89 de 4c 89 ef e8 0a a6 ff ff 85 c0 0f 84 34 ff ff ff <0f> 0b e9 
2d ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00
  [ 3634.322636] RSP: 0018:a70c009c3918 EFLAGS: 00010282
  [ 3634.322638] RAX: ff94 RBX: 9006104cc8c0 RCX: 

  [ 3634.322640] RDX: 90061ba3c740 RSI:  RDI: 
900613a62f48
  [ 3634.322641] RBP: a70c009c3938 R08: 90061e4d78c8 R09: 
0004
  [ 3634.322642] R10:  R11:  R12: 
900613f28000
  [ 3634.322643] R13: 900613a607a0 R14: 9006104cc8c0 R15: 
900613a60d68
  [ 3634.322644] FS:  7f596b396240() GS:90061e4c() 
knlGS:
  [ 3634.322645] CS:  0010 DS:  ES:  CR0: 80050033
  [ 3634.322646] CR2: 0db00945f000 CR3: 000494824005 CR4: 
003606e0
  [ 3634.322647] Call Trace:
  [ 3634.322670]  __sta_info_flush+0x128/0x180 [mac80211]
  [ 3634.322696]  ieee80211_set_disassoc+0xc0/0x5f0 [mac80211]
  [ 3634.322719]  ieee80211_mgd_deauth+0x104/0x490 [mac80211]
  [ 3634.322743]  ieee80211_deauth+0x18/0x20 [mac80211]
  [ 3634.322782]  cfg80211_mlme_deauth+0xb6/0x1e0 [cfg80211]
  [ 3634.322804]  cfg80211_mlme_down+0x66/0x80 [cfg80211]
  [ 3634.322823]  cfg80211_disconnect+0x127/0x1e0 [cfg80211]
  [ 3634.322827]  ? _raw_spin_unlock_bh+0x1e/0x20
  [ 3634.322845]  __cfg80211_leave+0x133/0x1b0 [cfg80211]
  [ 3634.322862]  cfg80211_leave+0x2c/0x40 [cfg80211]
  [ 3634.322879]  

[Kernel-packages] [Bug 1864061] Re: PCI/internal sound card not detected

[Peter Albrecht]

Adding "options snd-hda-intel dmic_detect=0" to the end of
/etc/modprobe.d/alsa-base.conf fixes the sound issue, but added some
internal errors that appear to have been resolved by a simple apt update
&& apt upgrade.

Thanks much!

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

Title:
  PCI/internal sound card not detected

Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux-oem-osp1 source package in Eoan:
  Fix Released

Bug description:
  The sof-pci-dev and snd-soc-skl all contains the same pciid, if
  the soc-skl is loaded ahead of sof-pci-dev, the sof driver will
  not work anymore, in the oem project, we manually put the soc-skl
  in the blacklist.

  From kernel-5.4 (focal kernel), the driver soc-skl is disabled by
  default, and there is no users report any issues on it. So let us
  disable soc-skl in the eoan and osp1 kernel too.

  The patch for eoan kernel doesn't remove the modules because looks
  like the abi folder are not controlled by git. This will break the
  modulecheck, so if this patch could be merged, please help remove
  those modules:
  snd-soc-skl
  snd-soc-skl-ipc
  snd-soc-skl-ssp-clk

  [Impact]
  If soc-skl driver is loaded ahead of sof driver, the sof could
  not work anymore, we need to blacklist the soc-skl manually

  [Fix]
  Like the focal kernel, we disable the soc_skl driver in the kernel
  config

  [Test Case]
  Tested on Lenovo and Dell machines which has dmic, the sof driver
  could be loaded successfully.

  Tested on the machinces without the dmic, the legacy hda driver
  worked well as before.

  [Regression Risk]
  Low, Focal kernel and mainine-5.5, 5.6-rc kernel all disabled this
  dirver; and We have not met a machine need the soc_skl driver yet;
  and Intel claim that the sof could replace the soc_skl driver.


  In the -41 kernel, we introduced a patch from stable kernel, that
  make the sof driver crash, and there is a fix patch in the 5.6-rc1,
  and this fix patch is already in the stable and is merged to focal
  kernel, now we backport this patch to Eoan kernel if -42 doesn't
  introduce this fix patch from stable.

  The patch introduced the crash:
  commit 063821115e02229d5fd3de31bad270d5e30aeb41
  Author: Dragos Tarcatu 
  Date: Mon Dec 9 18:39:38 2019 -0600

  ASoC: topology: Check return value for snd_soc_add_dai_link()

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

  [ Upstream commit 76d2703649321c296df7ec0dafd50add96215de4 ]

  snd_soc_add_dai_link() might fail. This situation occurs for
  instance in a very specific use case where a PCM device and a
  Back End DAI link are given identical names in the topology.
  When this happens, soc_new_pcm_runtime() fails and then
  snd_soc_add_dai_link() returns -ENOMEM when called from
  soc_tplg_fe_link_create(). Because of that, the link will not
  get added into the card list, so any attempt to remove it later
  ends up in a panic.

  Fix that by checking the return status and free the memory in case
  of an error.

  Reviewed-by: Ranjani Sridharan 
  Signed-off-by: Dragos Tarcatu 
  Signed-off-by: Pierre-Louis Bossart 
  Link: 
https://lore.kernel.org/r/20191210003939.15752-2-pierre-louis.boss...@linux.intel.com
  Signed-off-by: Mark Brown 
  Signed-off-by: Sasha Levin 
  Signed-off-by: Kamal Mostafa 
  Signed-off-by: Khalid Elmously 

  
  [Impact]
  During the boot, the sof driver crash because the hdmi_pcm_list
  is not initialized before it is used.

  [Fix]
  This bug is fixed in the mainline kernel v5.6-rc1, now backport
  this patch to ubuntu kernel

  [Test Case]
  Boot the -41 kernel with this patch added.
  blacklist the snd_soc_skl
  the kernel can boot successfully, and sof driver worked well

  [Regression Risk]
  Low, the patches are backported from upstream kernel, and I tested
  this patch on Lenovo and Dell dmic machines. Focal kernel already
  has this patch and works well.



  Probably a kernel bug.

  The sound card isn't detected in 5.3.0-41-generic
  Booting 5.3.0-40-generic does work.

  The relevant dmesg message is:

  [9.845441] skl_hda_dsp_generic skl_hda_dsp_generic: Unsupported 
HDAudio/iDisp configuration found
  [9.845447] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with 
error -22

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18
  Uname: Linux 5.3.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] 

[Kernel-packages] [Bug 1864061] Re: PCI/internal sound card not detected

[braincoke]

I have an Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, with 5.3.0-46-generic 
#38~18.04.1-Ubuntu.
My HDMI and Display Port audio were not working. Putting "options snd-hda-intel 
dmic_detect=0" in the /etc/modprobe.d/alsa-base.conf and rebooting solved the 
problem.

Thanks Hui Wang !

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

Title:
  PCI/internal sound card not detected

Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux-oem-osp1 source package in Eoan:
  Fix Released

Bug description:
  The sof-pci-dev and snd-soc-skl all contains the same pciid, if
  the soc-skl is loaded ahead of sof-pci-dev, the sof driver will
  not work anymore, in the oem project, we manually put the soc-skl
  in the blacklist.

  From kernel-5.4 (focal kernel), the driver soc-skl is disabled by
  default, and there is no users report any issues on it. So let us
  disable soc-skl in the eoan and osp1 kernel too.

  The patch for eoan kernel doesn't remove the modules because looks
  like the abi folder are not controlled by git. This will break the
  modulecheck, so if this patch could be merged, please help remove
  those modules:
  snd-soc-skl
  snd-soc-skl-ipc
  snd-soc-skl-ssp-clk

  [Impact]
  If soc-skl driver is loaded ahead of sof driver, the sof could
  not work anymore, we need to blacklist the soc-skl manually

  [Fix]
  Like the focal kernel, we disable the soc_skl driver in the kernel
  config

  [Test Case]
  Tested on Lenovo and Dell machines which has dmic, the sof driver
  could be loaded successfully.

  Tested on the machinces without the dmic, the legacy hda driver
  worked well as before.

  [Regression Risk]
  Low, Focal kernel and mainine-5.5, 5.6-rc kernel all disabled this
  dirver; and We have not met a machine need the soc_skl driver yet;
  and Intel claim that the sof could replace the soc_skl driver.


  In the -41 kernel, we introduced a patch from stable kernel, that
  make the sof driver crash, and there is a fix patch in the 5.6-rc1,
  and this fix patch is already in the stable and is merged to focal
  kernel, now we backport this patch to Eoan kernel if -42 doesn't
  introduce this fix patch from stable.

  The patch introduced the crash:
  commit 063821115e02229d5fd3de31bad270d5e30aeb41
  Author: Dragos Tarcatu 
  Date: Mon Dec 9 18:39:38 2019 -0600

  ASoC: topology: Check return value for snd_soc_add_dai_link()

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

  [ Upstream commit 76d2703649321c296df7ec0dafd50add96215de4 ]

  snd_soc_add_dai_link() might fail. This situation occurs for
  instance in a very specific use case where a PCM device and a
  Back End DAI link are given identical names in the topology.
  When this happens, soc_new_pcm_runtime() fails and then
  snd_soc_add_dai_link() returns -ENOMEM when called from
  soc_tplg_fe_link_create(). Because of that, the link will not
  get added into the card list, so any attempt to remove it later
  ends up in a panic.

  Fix that by checking the return status and free the memory in case
  of an error.

  Reviewed-by: Ranjani Sridharan 
  Signed-off-by: Dragos Tarcatu 
  Signed-off-by: Pierre-Louis Bossart 
  Link: 
https://lore.kernel.org/r/20191210003939.15752-2-pierre-louis.boss...@linux.intel.com
  Signed-off-by: Mark Brown 
  Signed-off-by: Sasha Levin 
  Signed-off-by: Kamal Mostafa 
  Signed-off-by: Khalid Elmously 

  
  [Impact]
  During the boot, the sof driver crash because the hdmi_pcm_list
  is not initialized before it is used.

  [Fix]
  This bug is fixed in the mainline kernel v5.6-rc1, now backport
  this patch to ubuntu kernel

  [Test Case]
  Boot the -41 kernel with this patch added.
  blacklist the snd_soc_skl
  the kernel can boot successfully, and sof driver worked well

  [Regression Risk]
  Low, the patches are backported from upstream kernel, and I tested
  this patch on Lenovo and Dell dmic machines. Focal kernel already
  has this patch and works well.



  Probably a kernel bug.

  The sound card isn't detected in 5.3.0-41-generic
  Booting 5.3.0-40-generic does work.

  The relevant dmesg message is:

  [9.845441] skl_hda_dsp_generic skl_hda_dsp_generic: Unsupported 
HDAudio/iDisp configuration found
  [9.845447] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with 
error -22

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18
  Uname: Linux 5.3.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  AudioDevicesInUse: Error: command 

[Kernel-packages] [Bug 1856407] Re: nvidia-435 is in eoan, linux-restricted-modules only builds against 430, ubiquity gives me the self-signed modules experience instead of using the Canonical-signed

[dann frazier]

The ubuntu-drivers-common task here appears to be to change it to prefer
the pre-built/signed drivers (linux-modules-nvidia-*) over the DKMS
counterparts. I'd recommend at that point that we start seeding linux-
modules-nvidia-[0-9]+-generic onto the desktop ISO instead of the DKMS
counterparts, so the offline install experiences matches.

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

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

Title:
  nvidia-435 is in eoan, linux-restricted-modules only builds against
  430, ubiquity gives me the self-signed modules experience instead of
  using the Canonical-signed modules

Status in linux package in Ubuntu:
  Invalid
Status in linux-restricted-modules package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  New
Status in linux source package in Eoan:
  Fix Released
Status in linux-restricted-modules source package in Eoan:
  Fix Released
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed
Status in ubuntu-drivers-common source package in Eoan:
  Confirmed
Status in ubuntu-meta source package in Eoan:
  New

Bug description:
  SRU Justification

  Impact: The nvidia-435 drivers are missing from linux-restricted-
  modules in eoan. On install ubuntu-drivers picks 435 as the newest
  version, and users must use self-signed dkms drivers and enroll a MOK.

  Fix: Add nvidia-435 dkms builds to linux and l-r-m for eoan.

  Test Case: A test build is available in ppa:sforshee/test-builds.
  Verify that signed drivers for nvidia-435 can be installed for eoan
  via the linux-modules-nvidia-435-{generic,lowlatency} packages.

  Regression Potential: The nvidia-435 l-r-m drivers are new packages
  built from the same source as the nvidia-435 dkms driver, so
  regressions are unlikely.

  ---

  The linux-restricted-modules package exists so that users who install
  the nvidia drivers can get known-good, signed modules instead of
  having to locally self-sign and enroll a signing key through MOK.  But
  lrm in eoan is only building driver packages for nvidia 390 and 430,
  and nvidia 435 is present in eoan.

  So on a new Ubuntu 19.10 install, ubuntu-drivers is picking 435 as the
  newest driver instead of using the signed 430 driver.

  We should never allow the archive to get into this situation.  We
  should be enforcing that any version of the nvidia driver that we
  expect ubuntu-drivers to install by default on any hardware is
  integrated into linux-restricted-modules, and we should ensure that
  ubuntu-drivers always prefers the signed drivers over other options.

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

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

[Kernel-packages] [Bug 1869672] Re: kdump kernel can't be loaded using kernel 4.15.0-76

[Guilherme G. Piccoli]

Hi yamato, I have good news! Managed to reproduce this in a secure boot
guest (after fighting with the keys hehe). There is an hypothesis of
what's going on: one patch that was merged in -65 changed the way flags
are set on purgatory, a piece of code used on kexec process. If we use
kexec in a secure system, it must use the kexec_file_load syscall, which
will rely in kernel purgatory. In no-secure-boot systems, the
regular/old kexec_load flag is used, which loads the purgatory from
kexec-tools.

If the hypothesis is right, we need to figure why kernel 5.3-hwe works -
there is a potential fix there based on my analysis, could be that
one...but more tests are required. In sosreport dmesg, you can see the
following messages, which are related:

kexec: Undefined symbol: __stack_chk_fail
kexec-bzImage64: Loading purgatory failed

Work is ongoing, thanks again for the report and tests!
Cheers,


Guilherme

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

Title:
  kdump kernel can't be loaded using kernel 4.15.0-76

Status in makedumpfile package in Ubuntu:
  New

Bug description:
  Thank you for reading this report.
  This may caused by bugs in kernel, not in kdump. If so, I will report this to 
kernel team.
  I need your comment to solve this.

  [Impact]
  * Kdump kernel can't be loaded using linux kernel 4.15.0-76.

  [Environment]
  Description:Ubuntu 18.04.4 LTS
  Release:18.04

  uname:
  Linux ubuntu 4.15.0-76-generic #86-Ubuntu SMP Fri Jan 17 17:24:28 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  Secure boot is enabled.

  Versions:
  * kexec-tools/bionic-updates,now 1:2.0.16-1ubuntu1.1
  * kdump-tools/bionic-updates,now 1:1.6.5-1ubuntu1~18.04.4

  [Test case]
  1)After OS booted, run systemctl status kdump-tools shows these messages 
below:

  
  ● kdump-tools.service - Kernel crash dump capture service
     Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
preset: enabled)
     Active: active (exited) since Fri 2020-03-27 16:40:31 JST; 5min ago
    Process: 895 ExecStart=/etc/init.d/kdump-tools start (code=exited, 
status=0/SUCCESS)
   Main PID: 895 (code=exited, status=0/SUCCESS)

  Mar 27 16:40:31 ubuntu systemd[1]: Starting Kernel crash dump capture 
service...
  Mar 27 16:40:31 ubuntu kdump-tools[895]: Starting kdump-tools:  * Creating 
symlink /var/lib/kdump/vmlinuz
  Mar 27 16:40:31 ubuntu kdump-tools[895]:  * Creating symlink 
/var/lib/kdump/initrd.img
  Mar 27 16:40:31 ubuntu kdump-tools[895]: kexec_file_load failed: Exec format 
error
  Mar 27 16:40:31 ubuntu kdump-tools[895]:  * failed to load kdump kernel
  Mar 27 16:40:31 ubuntu systemd[1]: Started Kernel crash dump capture service.
  

  2)Run kexec directly:
  $ sudo /sbin/kexec -p --command-line="/boot/vmlinuz-4.15.0-76-generic 
root=UUID=29a89ad8-8923-435e-a88c-aaf5cb379568 ro mce=ignore_ce reset_devices 
systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb 
ata_piix.prefer_ms_hyperv=0" --initrd=/boot/initrd.img-4.15.0-76-generic 
/boot/vmlinuz-4.15.0-64-generic

  Then,these messages are shown:
  Cannot open /proc/kcore: Operation not permitted
  Cannot read /proc/kcore: Operation not permitted
  Cannot load /boot/vmlinuz-4.15.0-76-generic

  On dmesg, these messages are shown:
  
  [  538.524718] Lockdown: /proc/kcore is restricted; see man kernel_lockdown.7
  

  3) Changing OS kernel to older one(I used 4.15.0-64), kdump kernel can
  be loaded.

  $ sudo systemctl status kdump-tools
  ● kdump-tools.service - Kernel crash dump capture service
     Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
preset: enabled)
     Active: active (exited) since Wed 2020-03-25 13:39:03 JST; 5 days ago
   Main PID: 832 (code=exited, status=0/SUCCESS)
  Tasks: 0 (limit: 4915)
     CGroup: /system.slice/kdump-tools.service

  Mar 25 13:39:02 ubuntu systemd[1]: Starting Kernel crash dump capture 
service...
  Mar 25 13:39:02 ubuntu kdump-tools[832]: Starting kdump-tools:  * Creating 
symlink /var/lib/kdump/vmlinuz
  Mar 25 13:39:02 ubuntu kdump-tools[832]:  * Creating symlink 
/var/lib/kdump/initrd.img
  Mar 25 13:39:03 ubuntu kdump-tools[832]:  * loaded kdump kernel
  Mar 25 13:39:03 ubuntu kdump-tools[938]: loaded kdump kernel
  Mar 25 13:39:03 ubuntu systemd[1]: Started Kernel crash dump capture service.

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Lenovo Yoga C940 frequently does thermal shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a bit higher load and especially if Laptop is charging, very often
  Kernel does an emergency thermal shutdown.

  thermal thermal_zone3: critical temperature reached (80 C), shutting
  down

  It says 80 C, but sensors command shows that temperatures hovering
  close to 100C before the shutdown happens.

  dmesg is often also full of these (for each core):
  mce: CPU2: Core temperature above threshold, cpu clock throttled (total 
events = 246766)

  When I boot to Windows, it seems that CPU is throttled more
  aggressively on load and thermal shutdown doesn't happen with a
  similar load, but CPU frequencies drop to 1600 range, while in Ubuntu
  they are 2800 range.

  I would rather have more throttling that computer shutting down
  randomly without the ability to save work.

  Is there a workaround?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anton  1874 F pulseaudio
   /dev/snd/pcmC0D0p:   anton  1874 F...m pulseaudio
   /dev/snd/pcmC0D6c:   anton  1874 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 23:54:21 2020
  InstallationDate: Installed on 2019-11-29 (137 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q9
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=24af2874-e109-44f9-a5b9-8a9ce34b3f0f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-04 (11 days ago)
  dmi.bios.date: 01/09/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AUCN54WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga C940-14IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL:
  dmi.product.family: Yoga C940-14IIL
  dmi.product.name: 81Q9
  dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL
  dmi.product.version: Lenovo Yoga C940-14IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1873083] [NEW] Lenovo Yoga C940 frequently does thermal shutdown

[Anton Keks]

Public bug reported:

On a bit higher load and especially if Laptop is charging, very often
Kernel does an emergency thermal shutdown.

thermal thermal_zone3: critical temperature reached (80 C), shutting
down

It says 80 C, but sensors command shows that temperatures hovering close
to 100C before the shutdown happens.

dmesg is often also full of these (for each core):
mce: CPU2: Core temperature above threshold, cpu clock throttled (total events 
= 246766)

When I boot to Windows, it seems that CPU is throttled more aggressively
on load and thermal shutdown doesn't happen with a similar load, but CPU
frequencies drop to 1600 range, while in Ubuntu they are 2800 range.

I would rather have more throttling that computer shutting down randomly
without the ability to save work.

Is there a workaround?

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-21-generic 5.4.0-21.25
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu24
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  anton  1874 F pulseaudio
 /dev/snd/pcmC0D0p:   anton  1874 F...m pulseaudio
 /dev/snd/pcmC0D6c:   anton  1874 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 15 23:54:21 2020
InstallationDate: Installed on 2019-11-29 (137 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 81Q9
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=24af2874-e109-44f9-a5b9-8a9ce34b3f0f ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-21-generic N/A
 linux-backports-modules-5.4.0-21-generic  N/A
 linux-firmware1.187
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-04-04 (11 days ago)
dmi.bios.date: 01/09/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: AUCN54WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Yoga C940-14IIL
dmi.modalias: 
dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL:
dmi.product.family: Yoga C940-14IIL
dmi.product.name: 81Q9
dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL
dmi.product.version: Lenovo Yoga C940-14IIL
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

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

Title:
  Lenovo Yoga C940 frequently does thermal shutdown

Status in linux package in Ubuntu:
  New

Bug description:
  On a bit higher load and especially if Laptop is charging, very often
  Kernel does an emergency thermal shutdown.

  thermal thermal_zone3: critical temperature reached (80 C), shutting
  down

  It says 80 C, but sensors command shows that temperatures hovering
  close to 100C before the shutdown happens.

  dmesg is often also full of these (for each core):
  mce: CPU2: Core temperature above threshold, cpu clock throttled (total 
events = 246766)

  When I boot to Windows, it seems that CPU is throttled more
  aggressively on load and thermal shutdown doesn't happen with a
  similar load, but CPU frequencies drop to 1600 range, while in Ubuntu
  they are 2800 range.

  I would rather have more throttling that computer shutting down
  randomly without the ability to save work.

  Is there a workaround?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anton  1874 F pulseaudio
   /dev/snd/pcmC0D0p:   anton  1874 F...m pulseaudio
   /dev/snd/pcmC0D6c:   anton  1874 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 23:54:21 2020
  InstallationDate: Installed on 2019-11-29 (137 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q9
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=24af2874-e109-44f9-a5b9-8a9ce34b3f0f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-04 (11 days ago)
  dmi.bios.date: 01/09/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 

[Kernel-packages] [Bug 1870614] Re: Unable to boot ubuntu 19.10 or newer on dell xps 9570

[Alistair Burrowes]

Er I figured it out.

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

Title:
  Unable to boot ubuntu 19.10 or newer on dell xps 9570

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Since updating my dell xps 9570 (latest BIOS 1.15.0 and a few previous
  versions) from 19.04 to 19.10 I have been unable to boot ubuntu. It
  fails with the following error quickly flashing:

error: file `/boot/` not found

  Then followed by:

error: cannot allocate kernel buffer.
error: you need to load the kernel first.

press any key to continue...
   
  This occurs when doing an update from 19.04 to 19.10 and also when just 
booting off a usb drive with 19.10.

  When booting off the usb drive. The first error flashes quickly before
  displaying the usb installer options. Selecting any install / boot
  option results in the second error about kernel buffer.

  I have tried all combinations of bios settings I can think of, such as
  toggling secure boot and other options. The only thing that made a
  difference is booting via USB with LEGACY EXTERNAL DEVICE BOOT. This
  allows the installer to complete, but I cannot then boot off the hard
  drive.

  I have tried the same USB drive with 19.10 on a Dell XPS 7590 with
  BIOS 1.2.3 and the USB stick boots fine. I have also tried many
  different USB drives on my 9570.

  I have tried a few daily builds of 20.04 with the same result. I
  tested with 20.04 beta as well.

  Note: 19.04 and earlier continues to work no problem.

  I have asked for help previously:

  * https://askubuntu.com/questions/1183129/19-10-usb-installer-boot-fail
  * https://answers.launchpad.net/ubuntu/+question/689546/+index

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubuntu-release-upgrader-core 1:19.04.16.9
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 06:55:59 2020
  InstallationDate: Installed on 2019-10-24 (162 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bananan2456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-04-13 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: Dell Inc. XPS 15 9570
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  bionic
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 07GHH0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1870614] Re: Unable to boot ubuntu 19.10 or newer on dell xps 9570

[Alistair Burrowes]

I have run apport-collect 1870614 . I don't seem to be able to set the
bug status to 'Confirmed'.

Currently I am running 18.04. I intend to try upgrading to 20.04 once it
is released.

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

Title:
  Unable to boot ubuntu 19.10 or newer on dell xps 9570

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Since updating my dell xps 9570 (latest BIOS 1.15.0 and a few previous
  versions) from 19.04 to 19.10 I have been unable to boot ubuntu. It
  fails with the following error quickly flashing:

error: file `/boot/` not found

  Then followed by:

error: cannot allocate kernel buffer.
error: you need to load the kernel first.

press any key to continue...
   
  This occurs when doing an update from 19.04 to 19.10 and also when just 
booting off a usb drive with 19.10.

  When booting off the usb drive. The first error flashes quickly before
  displaying the usb installer options. Selecting any install / boot
  option results in the second error about kernel buffer.

  I have tried all combinations of bios settings I can think of, such as
  toggling secure boot and other options. The only thing that made a
  difference is booting via USB with LEGACY EXTERNAL DEVICE BOOT. This
  allows the installer to complete, but I cannot then boot off the hard
  drive.

  I have tried the same USB drive with 19.10 on a Dell XPS 7590 with
  BIOS 1.2.3 and the USB stick boots fine. I have also tried many
  different USB drives on my 9570.

  I have tried a few daily builds of 20.04 with the same result. I
  tested with 20.04 beta as well.

  Note: 19.04 and earlier continues to work no problem.

  I have asked for help previously:

  * https://askubuntu.com/questions/1183129/19-10-usb-installer-boot-fail
  * https://answers.launchpad.net/ubuntu/+question/689546/+index

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubuntu-release-upgrader-core 1:19.04.16.9
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 06:55:59 2020
  InstallationDate: Installed on 2019-10-24 (162 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bananan2456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-04-13 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: Dell Inc. XPS 15 9570
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  bionic
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 07GHH0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

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

[Alistair Burrowes]

apport information

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

Title:
  Unable to boot ubuntu 19.10 or newer on dell xps 9570

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Since updating my dell xps 9570 (latest BIOS 1.15.0 and a few previous
  versions) from 19.04 to 19.10 I have been unable to boot ubuntu. It
  fails with the following error quickly flashing:

error: file `/boot/` not found

  Then followed by:

error: cannot allocate kernel buffer.
error: you need to load the kernel first.

press any key to continue...
   
  This occurs when doing an update from 19.04 to 19.10 and also when just 
booting off a usb drive with 19.10.

  When booting off the usb drive. The first error flashes quickly before
  displaying the usb installer options. Selecting any install / boot
  option results in the second error about kernel buffer.

  I have tried all combinations of bios settings I can think of, such as
  toggling secure boot and other options. The only thing that made a
  difference is booting via USB with LEGACY EXTERNAL DEVICE BOOT. This
  allows the installer to complete, but I cannot then boot off the hard
  drive.

  I have tried the same USB drive with 19.10 on a Dell XPS 7590 with
  BIOS 1.2.3 and the USB stick boots fine. I have also tried many
  different USB drives on my 9570.

  I have tried a few daily builds of 20.04 with the same result. I
  tested with 20.04 beta as well.

  Note: 19.04 and earlier continues to work no problem.

  I have asked for help previously:

  * https://askubuntu.com/questions/1183129/19-10-usb-installer-boot-fail
  * https://answers.launchpad.net/ubuntu/+question/689546/+index

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubuntu-release-upgrader-core 1:19.04.16.9
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 06:55:59 2020
  InstallationDate: Installed on 2019-10-24 (162 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bananan2456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-04-13 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: Dell Inc. XPS 15 9570
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  bionic
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 07GHH0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

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

[Alistair Burrowes]

apport information

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

Title:
  Unable to boot ubuntu 19.10 or newer on dell xps 9570

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Since updating my dell xps 9570 (latest BIOS 1.15.0 and a few previous
  versions) from 19.04 to 19.10 I have been unable to boot ubuntu. It
  fails with the following error quickly flashing:

error: file `/boot/` not found

  Then followed by:

error: cannot allocate kernel buffer.
error: you need to load the kernel first.

press any key to continue...
   
  This occurs when doing an update from 19.04 to 19.10 and also when just 
booting off a usb drive with 19.10.

  When booting off the usb drive. The first error flashes quickly before
  displaying the usb installer options. Selecting any install / boot
  option results in the second error about kernel buffer.

  I have tried all combinations of bios settings I can think of, such as
  toggling secure boot and other options. The only thing that made a
  difference is booting via USB with LEGACY EXTERNAL DEVICE BOOT. This
  allows the installer to complete, but I cannot then boot off the hard
  drive.

  I have tried the same USB drive with 19.10 on a Dell XPS 7590 with
  BIOS 1.2.3 and the USB stick boots fine. I have also tried many
  different USB drives on my 9570.

  I have tried a few daily builds of 20.04 with the same result. I
  tested with 20.04 beta as well.

  Note: 19.04 and earlier continues to work no problem.

  I have asked for help previously:

  * https://askubuntu.com/questions/1183129/19-10-usb-installer-boot-fail
  * https://answers.launchpad.net/ubuntu/+question/689546/+index

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubuntu-release-upgrader-core 1:19.04.16.9
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 06:55:59 2020
  InstallationDate: Installed on 2019-10-24 (162 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bananan2456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-04-13 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: Dell Inc. XPS 15 9570
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  bionic
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 07GHH0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

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

[Alistair Burrowes]

apport information

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

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

Title:
  Unable to boot ubuntu 19.10 or newer on dell xps 9570

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Since updating my dell xps 9570 (latest BIOS 1.15.0 and a few previous
  versions) from 19.04 to 19.10 I have been unable to boot ubuntu. It
  fails with the following error quickly flashing:

error: file `/boot/` not found

  Then followed by:

error: cannot allocate kernel buffer.
error: you need to load the kernel first.

press any key to continue...
   
  This occurs when doing an update from 19.04 to 19.10 and also when just 
booting off a usb drive with 19.10.

  When booting off the usb drive. The first error flashes quickly before
  displaying the usb installer options. Selecting any install / boot
  option results in the second error about kernel buffer.

  I have tried all combinations of bios settings I can think of, such as
  toggling secure boot and other options. The only thing that made a
  difference is booting via USB with LEGACY EXTERNAL DEVICE BOOT. This
  allows the installer to complete, but I cannot then boot off the hard
  drive.

  I have tried the same USB drive with 19.10 on a Dell XPS 7590 with
  BIOS 1.2.3 and the USB stick boots fine. I have also tried many
  different USB drives on my 9570.

  I have tried a few daily builds of 20.04 with the same result. I
  tested with 20.04 beta as well.

  Note: 19.04 and earlier continues to work no problem.

  I have asked for help previously:

  * https://askubuntu.com/questions/1183129/19-10-usb-installer-boot-fail
  * https://answers.launchpad.net/ubuntu/+question/689546/+index

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubuntu-release-upgrader-core 1:19.04.16.9
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 06:55:59 2020
  InstallationDate: Installed on 2019-10-24 (162 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bananan2456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-04-13 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: Dell Inc. XPS 15 9570
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  bionic
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 07GHH0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

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

[Alistair Burrowes]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1870614/+attachment/5354868/+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/1870614

Title:
  Unable to boot ubuntu 19.10 or newer on dell xps 9570

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Since updating my dell xps 9570 (latest BIOS 1.15.0 and a few previous
  versions) from 19.04 to 19.10 I have been unable to boot ubuntu. It
  fails with the following error quickly flashing:

error: file `/boot/` not found

  Then followed by:

error: cannot allocate kernel buffer.
error: you need to load the kernel first.

press any key to continue...
   
  This occurs when doing an update from 19.04 to 19.10 and also when just 
booting off a usb drive with 19.10.

  When booting off the usb drive. The first error flashes quickly before
  displaying the usb installer options. Selecting any install / boot
  option results in the second error about kernel buffer.

  I have tried all combinations of bios settings I can think of, such as
  toggling secure boot and other options. The only thing that made a
  difference is booting via USB with LEGACY EXTERNAL DEVICE BOOT. This
  allows the installer to complete, but I cannot then boot off the hard
  drive.

  I have tried the same USB drive with 19.10 on a Dell XPS 7590 with
  BIOS 1.2.3 and the USB stick boots fine. I have also tried many
  different USB drives on my 9570.

  I have tried a few daily builds of 20.04 with the same result. I
  tested with 20.04 beta as well.

  Note: 19.04 and earlier continues to work no problem.

  I have asked for help previously:

  * https://askubuntu.com/questions/1183129/19-10-usb-installer-boot-fail
  * https://answers.launchpad.net/ubuntu/+question/689546/+index

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubuntu-release-upgrader-core 1:19.04.16.9
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 06:55:59 2020
  InstallationDate: Installed on 2019-10-24 (162 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bananan2456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-04-13 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: Dell Inc. XPS 15 9570
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  bionic
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 07GHH0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

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

[Alistair Burrowes]

apport information

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

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

Title:
  Unable to boot ubuntu 19.10 or newer on dell xps 9570

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Since updating my dell xps 9570 (latest BIOS 1.15.0 and a few previous
  versions) from 19.04 to 19.10 I have been unable to boot ubuntu. It
  fails with the following error quickly flashing:

error: file `/boot/` not found

  Then followed by:

error: cannot allocate kernel buffer.
error: you need to load the kernel first.

press any key to continue...
   
  This occurs when doing an update from 19.04 to 19.10 and also when just 
booting off a usb drive with 19.10.

  When booting off the usb drive. The first error flashes quickly before
  displaying the usb installer options. Selecting any install / boot
  option results in the second error about kernel buffer.

  I have tried all combinations of bios settings I can think of, such as
  toggling secure boot and other options. The only thing that made a
  difference is booting via USB with LEGACY EXTERNAL DEVICE BOOT. This
  allows the installer to complete, but I cannot then boot off the hard
  drive.

  I have tried the same USB drive with 19.10 on a Dell XPS 7590 with
  BIOS 1.2.3 and the USB stick boots fine. I have also tried many
  different USB drives on my 9570.

  I have tried a few daily builds of 20.04 with the same result. I
  tested with 20.04 beta as well.

  Note: 19.04 and earlier continues to work no problem.

  I have asked for help previously:

  * https://askubuntu.com/questions/1183129/19-10-usb-installer-boot-fail
  * https://answers.launchpad.net/ubuntu/+question/689546/+index

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubuntu-release-upgrader-core 1:19.04.16.9
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 06:55:59 2020
  InstallationDate: Installed on 2019-10-24 (162 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bananan2456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-04-13 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: Dell Inc. XPS 15 9570
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  bionic
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 07GHH0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

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

[Alistair Burrowes]

apport information

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

Title:
  Unable to boot ubuntu 19.10 or newer on dell xps 9570

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Since updating my dell xps 9570 (latest BIOS 1.15.0 and a few previous
  versions) from 19.04 to 19.10 I have been unable to boot ubuntu. It
  fails with the following error quickly flashing:

error: file `/boot/` not found

  Then followed by:

error: cannot allocate kernel buffer.
error: you need to load the kernel first.

press any key to continue...
   
  This occurs when doing an update from 19.04 to 19.10 and also when just 
booting off a usb drive with 19.10.

  When booting off the usb drive. The first error flashes quickly before
  displaying the usb installer options. Selecting any install / boot
  option results in the second error about kernel buffer.

  I have tried all combinations of bios settings I can think of, such as
  toggling secure boot and other options. The only thing that made a
  difference is booting via USB with LEGACY EXTERNAL DEVICE BOOT. This
  allows the installer to complete, but I cannot then boot off the hard
  drive.

  I have tried the same USB drive with 19.10 on a Dell XPS 7590 with
  BIOS 1.2.3 and the USB stick boots fine. I have also tried many
  different USB drives on my 9570.

  I have tried a few daily builds of 20.04 with the same result. I
  tested with 20.04 beta as well.

  Note: 19.04 and earlier continues to work no problem.

  I have asked for help previously:

  * https://askubuntu.com/questions/1183129/19-10-usb-installer-boot-fail
  * https://answers.launchpad.net/ubuntu/+question/689546/+index

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubuntu-release-upgrader-core 1:19.04.16.9
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 06:55:59 2020
  InstallationDate: Installed on 2019-10-24 (162 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bananan2456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-04-13 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: Dell Inc. XPS 15 9570
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  bionic
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 07GHH0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

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

[Alistair Burrowes]

apport information

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

Title:
  Unable to boot ubuntu 19.10 or newer on dell xps 9570

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Since updating my dell xps 9570 (latest BIOS 1.15.0 and a few previous
  versions) from 19.04 to 19.10 I have been unable to boot ubuntu. It
  fails with the following error quickly flashing:

error: file `/boot/` not found

  Then followed by:

error: cannot allocate kernel buffer.
error: you need to load the kernel first.

press any key to continue...
   
  This occurs when doing an update from 19.04 to 19.10 and also when just 
booting off a usb drive with 19.10.

  When booting off the usb drive. The first error flashes quickly before
  displaying the usb installer options. Selecting any install / boot
  option results in the second error about kernel buffer.

  I have tried all combinations of bios settings I can think of, such as
  toggling secure boot and other options. The only thing that made a
  difference is booting via USB with LEGACY EXTERNAL DEVICE BOOT. This
  allows the installer to complete, but I cannot then boot off the hard
  drive.

  I have tried the same USB drive with 19.10 on a Dell XPS 7590 with
  BIOS 1.2.3 and the USB stick boots fine. I have also tried many
  different USB drives on my 9570.

  I have tried a few daily builds of 20.04 with the same result. I
  tested with 20.04 beta as well.

  Note: 19.04 and earlier continues to work no problem.

  I have asked for help previously:

  * https://askubuntu.com/questions/1183129/19-10-usb-installer-boot-fail
  * https://answers.launchpad.net/ubuntu/+question/689546/+index

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubuntu-release-upgrader-core 1:19.04.16.9
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 06:55:59 2020
  InstallationDate: Installed on 2019-10-24 (162 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bananan2456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-04-13 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: Dell Inc. XPS 15 9570
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  bionic
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 07GHH0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

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

[Alistair Burrowes]

apport information

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

Title:
  Unable to boot ubuntu 19.10 or newer on dell xps 9570

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Since updating my dell xps 9570 (latest BIOS 1.15.0 and a few previous
  versions) from 19.04 to 19.10 I have been unable to boot ubuntu. It
  fails with the following error quickly flashing:

error: file `/boot/` not found

  Then followed by:

error: cannot allocate kernel buffer.
error: you need to load the kernel first.

press any key to continue...
   
  This occurs when doing an update from 19.04 to 19.10 and also when just 
booting off a usb drive with 19.10.

  When booting off the usb drive. The first error flashes quickly before
  displaying the usb installer options. Selecting any install / boot
  option results in the second error about kernel buffer.

  I have tried all combinations of bios settings I can think of, such as
  toggling secure boot and other options. The only thing that made a
  difference is booting via USB with LEGACY EXTERNAL DEVICE BOOT. This
  allows the installer to complete, but I cannot then boot off the hard
  drive.

  I have tried the same USB drive with 19.10 on a Dell XPS 7590 with
  BIOS 1.2.3 and the USB stick boots fine. I have also tried many
  different USB drives on my 9570.

  I have tried a few daily builds of 20.04 with the same result. I
  tested with 20.04 beta as well.

  Note: 19.04 and earlier continues to work no problem.

  I have asked for help previously:

  * https://askubuntu.com/questions/1183129/19-10-usb-installer-boot-fail
  * https://answers.launchpad.net/ubuntu/+question/689546/+index

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubuntu-release-upgrader-core 1:19.04.16.9
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 06:55:59 2020
  InstallationDate: Installed on 2019-10-24 (162 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bananan2456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-04-13 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: Dell Inc. XPS 15 9570
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  bionic
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 07GHH0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

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

[Alistair Burrowes]

apport information

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

Title:
  Unable to boot ubuntu 19.10 or newer on dell xps 9570

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Since updating my dell xps 9570 (latest BIOS 1.15.0 and a few previous
  versions) from 19.04 to 19.10 I have been unable to boot ubuntu. It
  fails with the following error quickly flashing:

error: file `/boot/` not found

  Then followed by:

error: cannot allocate kernel buffer.
error: you need to load the kernel first.

press any key to continue...
   
  This occurs when doing an update from 19.04 to 19.10 and also when just 
booting off a usb drive with 19.10.

  When booting off the usb drive. The first error flashes quickly before
  displaying the usb installer options. Selecting any install / boot
  option results in the second error about kernel buffer.

  I have tried all combinations of bios settings I can think of, such as
  toggling secure boot and other options. The only thing that made a
  difference is booting via USB with LEGACY EXTERNAL DEVICE BOOT. This
  allows the installer to complete, but I cannot then boot off the hard
  drive.

  I have tried the same USB drive with 19.10 on a Dell XPS 7590 with
  BIOS 1.2.3 and the USB stick boots fine. I have also tried many
  different USB drives on my 9570.

  I have tried a few daily builds of 20.04 with the same result. I
  tested with 20.04 beta as well.

  Note: 19.04 and earlier continues to work no problem.

  I have asked for help previously:

  * https://askubuntu.com/questions/1183129/19-10-usb-installer-boot-fail
  * https://answers.launchpad.net/ubuntu/+question/689546/+index

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubuntu-release-upgrader-core 1:19.04.16.9
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 06:55:59 2020
  InstallationDate: Installed on 2019-10-24 (162 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bananan2456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-04-13 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: Dell Inc. XPS 15 9570
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  bionic
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 07GHH0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

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

[Alistair Burrowes]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1870614/+attachment/5354873/+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/1870614

Title:
  Unable to boot ubuntu 19.10 or newer on dell xps 9570

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Since updating my dell xps 9570 (latest BIOS 1.15.0 and a few previous
  versions) from 19.04 to 19.10 I have been unable to boot ubuntu. It
  fails with the following error quickly flashing:

error: file `/boot/` not found

  Then followed by:

error: cannot allocate kernel buffer.
error: you need to load the kernel first.

press any key to continue...
   
  This occurs when doing an update from 19.04 to 19.10 and also when just 
booting off a usb drive with 19.10.

  When booting off the usb drive. The first error flashes quickly before
  displaying the usb installer options. Selecting any install / boot
  option results in the second error about kernel buffer.

  I have tried all combinations of bios settings I can think of, such as
  toggling secure boot and other options. The only thing that made a
  difference is booting via USB with LEGACY EXTERNAL DEVICE BOOT. This
  allows the installer to complete, but I cannot then boot off the hard
  drive.

  I have tried the same USB drive with 19.10 on a Dell XPS 7590 with
  BIOS 1.2.3 and the USB stick boots fine. I have also tried many
  different USB drives on my 9570.

  I have tried a few daily builds of 20.04 with the same result. I
  tested with 20.04 beta as well.

  Note: 19.04 and earlier continues to work no problem.

  I have asked for help previously:

  * https://askubuntu.com/questions/1183129/19-10-usb-installer-boot-fail
  * https://answers.launchpad.net/ubuntu/+question/689546/+index

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubuntu-release-upgrader-core 1:19.04.16.9
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 06:55:59 2020
  InstallationDate: Installed on 2019-10-24 (162 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bananan2456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-04-13 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: Dell Inc. XPS 15 9570
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  bionic
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 07GHH0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

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

[Alistair Burrowes]

apport information

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

Title:
  Unable to boot ubuntu 19.10 or newer on dell xps 9570

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Since updating my dell xps 9570 (latest BIOS 1.15.0 and a few previous
  versions) from 19.04 to 19.10 I have been unable to boot ubuntu. It
  fails with the following error quickly flashing:

error: file `/boot/` not found

  Then followed by:

error: cannot allocate kernel buffer.
error: you need to load the kernel first.

press any key to continue...
   
  This occurs when doing an update from 19.04 to 19.10 and also when just 
booting off a usb drive with 19.10.

  When booting off the usb drive. The first error flashes quickly before
  displaying the usb installer options. Selecting any install / boot
  option results in the second error about kernel buffer.

  I have tried all combinations of bios settings I can think of, such as
  toggling secure boot and other options. The only thing that made a
  difference is booting via USB with LEGACY EXTERNAL DEVICE BOOT. This
  allows the installer to complete, but I cannot then boot off the hard
  drive.

  I have tried the same USB drive with 19.10 on a Dell XPS 7590 with
  BIOS 1.2.3 and the USB stick boots fine. I have also tried many
  different USB drives on my 9570.

  I have tried a few daily builds of 20.04 with the same result. I
  tested with 20.04 beta as well.

  Note: 19.04 and earlier continues to work no problem.

  I have asked for help previously:

  * https://askubuntu.com/questions/1183129/19-10-usb-installer-boot-fail
  * https://answers.launchpad.net/ubuntu/+question/689546/+index

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubuntu-release-upgrader-core 1:19.04.16.9
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 06:55:59 2020
  InstallationDate: Installed on 2019-10-24 (162 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bananan2456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-04-13 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: Dell Inc. XPS 15 9570
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  bionic
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 07GHH0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1870614] RfKill.txt

[Alistair Burrowes]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1870614/+attachment/5354874/+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/1870614

Title:
  Unable to boot ubuntu 19.10 or newer on dell xps 9570

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Since updating my dell xps 9570 (latest BIOS 1.15.0 and a few previous
  versions) from 19.04 to 19.10 I have been unable to boot ubuntu. It
  fails with the following error quickly flashing:

error: file `/boot/` not found

  Then followed by:

error: cannot allocate kernel buffer.
error: you need to load the kernel first.

press any key to continue...
   
  This occurs when doing an update from 19.04 to 19.10 and also when just 
booting off a usb drive with 19.10.

  When booting off the usb drive. The first error flashes quickly before
  displaying the usb installer options. Selecting any install / boot
  option results in the second error about kernel buffer.

  I have tried all combinations of bios settings I can think of, such as
  toggling secure boot and other options. The only thing that made a
  difference is booting via USB with LEGACY EXTERNAL DEVICE BOOT. This
  allows the installer to complete, but I cannot then boot off the hard
  drive.

  I have tried the same USB drive with 19.10 on a Dell XPS 7590 with
  BIOS 1.2.3 and the USB stick boots fine. I have also tried many
  different USB drives on my 9570.

  I have tried a few daily builds of 20.04 with the same result. I
  tested with 20.04 beta as well.

  Note: 19.04 and earlier continues to work no problem.

  I have asked for help previously:

  * https://askubuntu.com/questions/1183129/19-10-usb-installer-boot-fail
  * https://answers.launchpad.net/ubuntu/+question/689546/+index

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubuntu-release-upgrader-core 1:19.04.16.9
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 06:55:59 2020
  InstallationDate: Installed on 2019-10-24 (162 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bananan2456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-04-13 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: Dell Inc. XPS 15 9570
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  bionic
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 07GHH0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

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

[Alistair Burrowes]

apport information

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

Title:
  Unable to boot ubuntu 19.10 or newer on dell xps 9570

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Since updating my dell xps 9570 (latest BIOS 1.15.0 and a few previous
  versions) from 19.04 to 19.10 I have been unable to boot ubuntu. It
  fails with the following error quickly flashing:

error: file `/boot/` not found

  Then followed by:

error: cannot allocate kernel buffer.
error: you need to load the kernel first.

press any key to continue...
   
  This occurs when doing an update from 19.04 to 19.10 and also when just 
booting off a usb drive with 19.10.

  When booting off the usb drive. The first error flashes quickly before
  displaying the usb installer options. Selecting any install / boot
  option results in the second error about kernel buffer.

  I have tried all combinations of bios settings I can think of, such as
  toggling secure boot and other options. The only thing that made a
  difference is booting via USB with LEGACY EXTERNAL DEVICE BOOT. This
  allows the installer to complete, but I cannot then boot off the hard
  drive.

  I have tried the same USB drive with 19.10 on a Dell XPS 7590 with
  BIOS 1.2.3 and the USB stick boots fine. I have also tried many
  different USB drives on my 9570.

  I have tried a few daily builds of 20.04 with the same result. I
  tested with 20.04 beta as well.

  Note: 19.04 and earlier continues to work no problem.

  I have asked for help previously:

  * https://askubuntu.com/questions/1183129/19-10-usb-installer-boot-fail
  * https://answers.launchpad.net/ubuntu/+question/689546/+index

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubuntu-release-upgrader-core 1:19.04.16.9
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 06:55:59 2020
  InstallationDate: Installed on 2019-10-24 (162 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bananan2456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-04-13 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: Dell Inc. XPS 15 9570
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  bionic
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 07GHH0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

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

[Alistair Burrowes]

apport information

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

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

Title:
  Unable to boot ubuntu 19.10 or newer on dell xps 9570

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Since updating my dell xps 9570 (latest BIOS 1.15.0 and a few previous
  versions) from 19.04 to 19.10 I have been unable to boot ubuntu. It
  fails with the following error quickly flashing:

error: file `/boot/` not found

  Then followed by:

error: cannot allocate kernel buffer.
error: you need to load the kernel first.

press any key to continue...
   
  This occurs when doing an update from 19.04 to 19.10 and also when just 
booting off a usb drive with 19.10.

  When booting off the usb drive. The first error flashes quickly before
  displaying the usb installer options. Selecting any install / boot
  option results in the second error about kernel buffer.

  I have tried all combinations of bios settings I can think of, such as
  toggling secure boot and other options. The only thing that made a
  difference is booting via USB with LEGACY EXTERNAL DEVICE BOOT. This
  allows the installer to complete, but I cannot then boot off the hard
  drive.

  I have tried the same USB drive with 19.10 on a Dell XPS 7590 with
  BIOS 1.2.3 and the USB stick boots fine. I have also tried many
  different USB drives on my 9570.

  I have tried a few daily builds of 20.04 with the same result. I
  tested with 20.04 beta as well.

  Note: 19.04 and earlier continues to work no problem.

  I have asked for help previously:

  * https://askubuntu.com/questions/1183129/19-10-usb-installer-boot-fail
  * https://answers.launchpad.net/ubuntu/+question/689546/+index

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubuntu-release-upgrader-core 1:19.04.16.9
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 06:55:59 2020
  InstallationDate: Installed on 2019-10-24 (162 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bananan2456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-04-13 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: Dell Inc. XPS 15 9570
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  bionic
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 07GHH0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1870614] Re: Unable to boot ubuntu 19.10 or newer on dell xps 9570

[Alistair Burrowes]

apport information

** Tags added: apport-collected bionic

** Description changed:

  Hi,
  
  Since updating my dell xps 9570 (latest BIOS 1.15.0 and a few previous
  versions) from 19.04 to 19.10 I have been unable to boot ubuntu. It
  fails with the following error quickly flashing:
  
error: file `/boot/` not found
  
  Then followed by:
  
error: cannot allocate kernel buffer.
error: you need to load the kernel first.
  
press any key to continue...
   
  This occurs when doing an update from 19.04 to 19.10 and also when just 
booting off a usb drive with 19.10.
  
  When booting off the usb drive. The first error flashes quickly before
  displaying the usb installer options. Selecting any install / boot
  option results in the second error about kernel buffer.
  
  I have tried all combinations of bios settings I can think of, such as
  toggling secure boot and other options. The only thing that made a
  difference is booting via USB with LEGACY EXTERNAL DEVICE BOOT. This
  allows the installer to complete, but I cannot then boot off the hard
  drive.
  
  I have tried the same USB drive with 19.10 on a Dell XPS 7590 with BIOS
  1.2.3 and the USB stick boots fine. I have also tried many different USB
  drives on my 9570.
  
  I have tried a few daily builds of 20.04 with the same result. I tested
  with 20.04 beta as well.
  
  Note: 19.04 and earlier continues to work no problem.
  
  I have asked for help previously:
  
  * https://askubuntu.com/questions/1183129/19-10-usb-installer-boot-fail
  * https://answers.launchpad.net/ubuntu/+question/689546/+index
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubuntu-release-upgrader-core 1:19.04.16.9
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 06:55:59 2020
  InstallationDate: Installed on 2019-10-24 (162 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.14
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  bananan2456 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2020-04-13 (2 days ago)
+ InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
+ MachineType: Dell Inc. XPS 15 9570
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
+ RelatedPackageVersions:
+  linux-restricted-modules-5.3.0-46-generic N/A
+  linux-backports-modules-5.3.0-46-generic  N/A
+  linux-firmware1.173.17
+ Tags:  bionic
+ Uname: Linux 5.3.0-46-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 12/25/2019
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.15.0
+ dmi.board.name: 07GHH0
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr:
+ dmi.product.family: XPS
+ dmi.product.name: XPS 15 9570
+ dmi.product.sku: 087C
+ dmi.sys.vendor: Dell Inc.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1870614/+attachment/5354862/+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/1870614

Title:
  Unable to boot ubuntu 19.10 or newer on dell xps 9570

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Since updating my dell xps 9570 (latest BIOS 1.15.0 and a few previous
  versions) from 19.04 to 19.10 I have been unable to boot ubuntu. It
  fails with the following error quickly flashing:

error: file `/boot/` not found

  Then followed by:

error: cannot allocate kernel buffer.
error: you need to load the kernel first.

press any key to continue...
   
  This occurs when doing an update from 19.04 to 19.10 and also when just 
booting off a usb drive with 19.10.

  When booting off the usb drive. The first error flashes quickly before
  displaying the usb installer options. Selecting any install / boot
  option results in the second error about kernel buffer.

  I have tried all 

Re: [Kernel-packages] [Bug 1871248] Re: amdgpu kernel errors in Linux 5.4

[Kirt Runolfson]

Hi Alex,

I'd be more than happy to test. I'll jump on it and report as soon as I see
a kernel with the SRU applied.

Thank you again!

-Kirt

On Mon, Apr 13, 2020 at 12:01 PM Alex Hung <1871...@bugs.launchpad.net>
wrote:

> A SRU was sent for reviewing. Your help will be needed to test proposed
> kernel before next kernel updates later.
>
> This patch is contained in kernel 5.7 rc1 and it is likely to be
> included in next Ubuntu release without backporting.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1871248
>
> Title:
>   amdgpu kernel errors in Linux 5.4
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871248/+subscriptions
>

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

Title:
  amdgpu kernel errors in Linux 5.4

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux atlas 5.4.0-21-generic #25-Ubuntu SMP Sat Mar 28 13:10:28 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu 20.04 beta fresh installation. Upgrades applied.
  AMD Ryzen 3 3200G with Radeon Vega Graphics
  Motherboard: Gigabyte B450 I AORUS PRO WIFI/B450 I AORUS PRO WIFI-CF, BIOS 
F50 11/27/2019

  These errors keep appearing in the kernel messages. 
  [3.258890] [ cut here ]
  [3.258944] WARNING: CPU: 1 PID: 621 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link.c:1737 
write_i2c_retimer_setting+0xc8/0x3e0 [amdgpu]
  [3.258945] Modules linked in: amd64_edac_mod(-) cmac algif_hash 
algif_skcipher af_alg bnep edac_mce_amd ccp kvm snd_hda_codec_realtek 
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel 
snd_intel_nhlt snd_hda_codec snd_hda_core snd_hwdep snd_pcm crct10dif_pclmul 
ghash_clmulni_intel snd_seq_midi nls_iso8859_1 snd_seq_midi_event snd_rawmidi 
snd_seq aesni_intel iwlmvm crypto_simd mac80211 amdgpu cryptd libarc4 
glue_helper snd_seq_device amd_iommu_v2 btusb iwlwifi gpu_sched btrtl wmi_bmof 
ttm btbcm k10temp snd_timer btintel input_leds drm_kms_helper bluetooth snd 
fb_sys_fops syscopyarea cfg80211 sysfillrect soundcore sysimgblt ecdh_generic 
ecc mac_hid sch_fq_codel parport_pc ppdev lp drm parport ip_tables x_tables 
autofs4 hid_generic usbhid hid nvme crc32_pclmul i2c_piix4 ahci igb nvme_core 
i2c_algo_bit dca libahci wmi video gpio_amdpt gpio_generic
  [3.258966] CPU: 1 PID: 621 Comm: gpu-manager Not tainted 5.4.0-21-generic 
#25-Ubuntu
  [3.258967] Hardware name: Gigabyte Technology Co., Ltd. B450 I AORUS PRO 
WIFI/B450 I AORUS PRO WIFI-CF, BIOS F50 11/27/2019
  [3.259012] RIP: 0010:write_i2c_retimer_setting+0xc8/0x3e0 [amdgpu]

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kirt   1293 F pulseaudio
   /dev/snd/controlC0:  kirt   1293 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  6 15:52:30 2020
  InstallationDate: Installed on 2020-04-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Gigabyte Technology Co., Ltd. B450 I AORUS PRO WIFI
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=9940ba5b-7683-413e-92a2-854b3816799b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 I AORUS PRO WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450IAORUSPROWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450IAORUSPROWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450 I AORUS PRO WIFI
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 

[Kernel-packages] [Bug 1829978] Re: cpuacct_100_100 from controllers test suite in LTP failed

[Sean Feole]

** Changed in: ubuntu-kernel-tests
   Status: New => Confirmed

** Tags added: sru-20200406

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

Title:
  cpuacct_100_100 from controllers test suite in LTP failed

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-aws source package in Bionic:
  New
Status in linux source package in Disco:
  New
Status in linux-aws source package in Disco:
  New

Bug description:
   startup='Wed May 22 06:50:45 2019'
   cpuacct 1 TINFO: timeout per run is 0h 5m 0s
   cpuacct 1 TINFO: cpuacct: /sys/fs/cgroup/cpu,cpuacct
   cpuacct 1 TINFO: Creating 100 subgroups each with 100 processes
   /opt/ltp/testcases/bin/cpuacct.sh: -2110094999: 
/opt/ltp/testcases/bin/cpuacct.sh: Cannot fork
   tag=cpuacct_100_100 stime=1558507845 dur=9 exit=exited stat=2 core=no cu=30 
cs=53

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   
  Date: Wed May 22 06:59:27 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829978/+subscriptions

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

[Kernel-packages] [Bug 1844493] Re: ubuntu_sysdig_smoke_test failed on Eoan/5.3 kernels

[Sean Feole]

** Tags added: sru-20200406

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

Title:
  ubuntu_sysdig_smoke_test failed on Eoan/5.3 kernels

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux source package in Eoan:
  Incomplete
Status in linux-aws source package in Eoan:
  New
Status in linux-azure source package in Eoan:
  New
Status in linux-gcp source package in Eoan:
  New

Bug description:
  Test failed with:
FAILED (trace at least 25 reads of /dev/zero by dd)
FAILED (trace at least 25 writes to /dev/null by dd)

  Steps:
sudo apt-get install git python-minimal python-yaml gdb -y
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_sysdig_smoke_test/control

  Test output:
== sysdig smoke test to trace dd, cat, read and writes ==
Limiting raw capture file to 16384 blocks
Try 1 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 18 Mbytes
Try 2 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 22 Mbytes
Try 3 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 4 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 5 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 6 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 7 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 8 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 9 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 10 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Found:
   279845 sysdig events
   29882 context switches
   0 reads from /dev/zero by dd
   0 writes to /dev/null by dd
PASSED (trace at least 25 context switches)
FAILED (trace at least 25 reads of /dev/zero by dd)
FAILED (trace at least 25 writes to /dev/null by dd)
 
Summary: 1 passed, 2 failed

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-10-generic 5.3.0-10.11
  ProcVersionSignature: User Name 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 18 08:10 seq
   crw-rw 1 root audio 116, 33 Sep 18 08:10 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   
  Date: Wed Sep 18 08:18:54 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:
   
  ProcFB: 0 mgag200drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-10-generic N/A
   linux-backports-modules-5.3.0-10-generic  N/A
   linux-firmware1.182
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 
  dmi.board.name: S1200RP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G62254-407
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 

[Kernel-packages] [Bug 1873064] [NEW] x86/microcode/AMD: Increase microcode PATCH_MAX_SIZ

[Kim Naru]

Public bug reported:

Future AMD CPUs will have microcode patches that exceed the default 4K
patch size. Raise our limit.

https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=bdf89df3c54518eed879d8fac7577fcfb220c67e

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

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

Title:
  x86/microcode/AMD: Increase microcode PATCH_MAX_SIZ

Status in linux package in Ubuntu:
  New

Bug description:
  Future AMD CPUs will have microcode patches that exceed the default 4K
  patch size. Raise our limit.

  
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=bdf89df3c54518eed879d8fac7577fcfb220c67e

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

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

[Kernel-packages] [Bug 1829849] Re: proc01 in fs from ubuntu_ltp failed with D/B/E

[Sean Feole]

** Tags added: sru-20200406

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

Title:
  proc01 in fs from ubuntu_ltp failed with D/B/E

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  Triaged
Status in linux-oracle-5.0 package in Ubuntu:
  Confirmed

Bug description:
   proc01  0  TINFO  :  /proc/sys/fs/binfmt_misc/register: is write-only.
   proc01  0  TINFO  :  /proc/sys/net/ipv6/conf/all/stable_secret: known 
issue: errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/sys/net/ipv6/conf/default/stable_secret: 
known issue: errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/sys/net/ipv6/conf/ens6/stable_secret: known 
issue: errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/sys/net/ipv6/conf/lo/stable_secret: known 
issue: errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/kmsg: known issue: 
errno=EAGAIN/EWOULDBLOCK(11): Resource temporarily unavailable
   proc01  0  TINFO  :  /proc/sysrq-trigger: is write-only.
   proc01  0  TINFO  :  /proc/self/task/8782/mem: known issue: 
errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/self/task/8782/clear_refs: is write-only.
   proc01  0  TINFO  :  /proc/self/task/8782/pagemap: reached maxmbytes (-m)
   proc01  0  TINFO  :  /proc/self/task/8782/attr/prev: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/task/8782/attr/exec: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/task/8782/attr/fscreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/task/8782/attr/keycreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/task/8782/attr/sockcreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  1  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/current: errno=EINVAL(22): Invalid argument
   proc01  2  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/prev: errno=EINVAL(22): Invalid argument
   proc01  3  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/exec: errno=EINVAL(22): Invalid argument
   proc01  4  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument
   proc01  5  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument
   proc01  6  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument
   proc01  7  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/smack/current: errno=EINVAL(22): Invalid argument
   proc01  8  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/apparmor/prev: errno=EINVAL(22): Invalid argument
   proc01  9  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/apparmor/exec: errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/mem: known issue: errno=EIO(5): 
Input/output error
   proc01  0  TINFO  :  /proc/self/clear_refs: is write-only.
   proc01  0  TINFO  :  /proc/self/pagemap: reached maxmbytes (-m)
   proc01  0  TINFO  :  /proc/self/attr/prev: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/attr/exec: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/attr/fscreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/attr/keycreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/attr/sockcreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01 10  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/current: errno=EINVAL(22): Invalid argument
   proc01 11  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/prev: errno=EINVAL(22): Invalid argument
   proc01 12  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/exec: errno=EINVAL(22): Invalid argument
   proc01 13  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument
   proc01 14  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument
   proc01 15  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument
   proc01 16  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/smack/current: errno=EINVAL(22): Invalid argument
   proc01 17  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/apparmor/prev: errno=EINVAL(22): Invalid argument
   proc01 18  TFAIL  :  proc01.c:397: read 

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

[Sean Feole]

apport information

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

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

Title:
  Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete

Bug description:
  In Focal,

  The following tests fail on baremetal/amd64:

  04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer  
[FAIL]
  04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer   
[FAIL]
  04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test 
inter-event histogram trigger expected fail actions[XFAIL]

  Full output below.

  04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests ===
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check   
[PASS]
  04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing 
check[PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer 
size   [PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing 
setting [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and 
trace_marker  [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - 
add/remove kprobe events [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - 
add/remove synthetic events  [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - 
selective clear (compatibility) [PASS]
  04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - 
generic clear event [PASS]
  04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - 
enable/disable with event level files   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - 
restricts events based on pid   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - 
enable/disable with subsystem level files   [PASS]
  04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - 
enable/disable with top level files [PASS]
  04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from 
module   [PASS]
  04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph 
filters with stack tracer   [PASS]
  04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph 
filters [PASS]
  04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid 
filters   [PASS]
  04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace 
filter command  [PASS]
  04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace 
with cpumask[PASS]
  04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for 
function event triggers   [PASS]
  04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace 
on module   [PASS]
  04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function 
profiling [PASS]
  04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function 
profiler with function tracing[PASS]
  04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading 
of set_ftrace_filter  [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for 
function traceon/off triggers [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing 
error log support [PASS]
  04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and 
deletion of trace instances while setting an event[PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and 
deletion of trace instances   [PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - 
adding and removing  [PASS]
  04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32] Kprobe dynamic event - 
busy event check [PASS]
  04/12 03:26:14 DEBUG| utils:0153| [stdout] # [33] Kprobe dynamic event 
with arguments [PASS]
  04/12 03:26:15 DEBUG| utils:0153| [stdout] # [34] Kprobe event with comm 
arguments[PASS]
  04/12 03:26:15 DEBUG| utils:0153| [stdout] # [35] Kprobe event string 
type argument   [PASS]
  04/12 03:26:16 DEBUG| utils:0153| [stdout] # [36] Kprobe event symbol 
argument[PASS]
  04/12 03:26:18 DEBUG| utils:0153| [stdout] 

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

[Sean Feole]

apport information

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

Title:
  Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete

Bug description:
  In Focal,

  The following tests fail on baremetal/amd64:

  04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer  
[FAIL]
  04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer   
[FAIL]
  04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test 
inter-event histogram trigger expected fail actions[XFAIL]

  Full output below.

  04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests ===
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check   
[PASS]
  04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing 
check[PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer 
size   [PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing 
setting [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and 
trace_marker  [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - 
add/remove kprobe events [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - 
add/remove synthetic events  [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - 
selective clear (compatibility) [PASS]
  04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - 
generic clear event [PASS]
  04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - 
enable/disable with event level files   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - 
restricts events based on pid   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - 
enable/disable with subsystem level files   [PASS]
  04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - 
enable/disable with top level files [PASS]
  04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from 
module   [PASS]
  04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph 
filters with stack tracer   [PASS]
  04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph 
filters [PASS]
  04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid 
filters   [PASS]
  04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace 
filter command  [PASS]
  04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace 
with cpumask[PASS]
  04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for 
function event triggers   [PASS]
  04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace 
on module   [PASS]
  04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function 
profiling [PASS]
  04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function 
profiler with function tracing[PASS]
  04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading 
of set_ftrace_filter  [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for 
function traceon/off triggers [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing 
error log support [PASS]
  04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and 
deletion of trace instances while setting an event[PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and 
deletion of trace instances   [PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - 
adding and removing  [PASS]
  04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32] Kprobe dynamic event - 
busy event check [PASS]
  04/12 03:26:14 DEBUG| utils:0153| [stdout] # [33] Kprobe dynamic event 
with arguments [PASS]
  04/12 03:26:15 DEBUG| utils:0153| [stdout] # [34] Kprobe event with comm 
arguments[PASS]
  04/12 03:26:15 DEBUG| utils:0153| [stdout] # [35] Kprobe event string 
type argument   [PASS]
  04/12 03:26:16 DEBUG| utils:0153| [stdout] # [36] Kprobe event symbol 
argument[PASS]
  04/12 03:26:18 DEBUG| utils:0153| 

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

[Sean Feole]

apport information

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

Title:
  Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete

Bug description:
  In Focal,

  The following tests fail on baremetal/amd64:

  04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer  
[FAIL]
  04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer   
[FAIL]
  04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test 
inter-event histogram trigger expected fail actions[XFAIL]

  Full output below.

  04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests ===
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check   
[PASS]
  04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing 
check[PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer 
size   [PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing 
setting [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and 
trace_marker  [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - 
add/remove kprobe events [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - 
add/remove synthetic events  [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - 
selective clear (compatibility) [PASS]
  04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - 
generic clear event [PASS]
  04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - 
enable/disable with event level files   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - 
restricts events based on pid   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - 
enable/disable with subsystem level files   [PASS]
  04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - 
enable/disable with top level files [PASS]
  04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from 
module   [PASS]
  04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph 
filters with stack tracer   [PASS]
  04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph 
filters [PASS]
  04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid 
filters   [PASS]
  04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace 
filter command  [PASS]
  04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace 
with cpumask[PASS]
  04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for 
function event triggers   [PASS]
  04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace 
on module   [PASS]
  04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function 
profiling [PASS]
  04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function 
profiler with function tracing[PASS]
  04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading 
of set_ftrace_filter  [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for 
function traceon/off triggers [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing 
error log support [PASS]
  04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and 
deletion of trace instances while setting an event[PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and 
deletion of trace instances   [PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - 
adding and removing  [PASS]
  04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32] Kprobe dynamic event - 
busy event check [PASS]
  04/12 03:26:14 DEBUG| utils:0153| [stdout] # [33] Kprobe dynamic event 
with arguments [PASS]
  04/12 03:26:15 DEBUG| utils:0153| [stdout] # [34] Kprobe event with comm 
arguments[PASS]
  04/12 03:26:15 DEBUG| utils:0153| [stdout] # [35] Kprobe event string 
type argument   [PASS]
  04/12 03:26:16 DEBUG| utils:0153| [stdout] # [36] Kprobe event symbol 
argument[PASS]
  04/12 03:26:18 DEBUG| utils:0153| [stdout] # [37] 

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

[Sean Feole]

apport information

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

Title:
  Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete

Bug description:
  In Focal,

  The following tests fail on baremetal/amd64:

  04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer  
[FAIL]
  04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer   
[FAIL]
  04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test 
inter-event histogram trigger expected fail actions[XFAIL]

  Full output below.

  04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests ===
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check   
[PASS]
  04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing 
check[PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer 
size   [PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing 
setting [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and 
trace_marker  [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - 
add/remove kprobe events [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - 
add/remove synthetic events  [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - 
selective clear (compatibility) [PASS]
  04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - 
generic clear event [PASS]
  04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - 
enable/disable with event level files   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - 
restricts events based on pid   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - 
enable/disable with subsystem level files   [PASS]
  04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - 
enable/disable with top level files [PASS]
  04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from 
module   [PASS]
  04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph 
filters with stack tracer   [PASS]
  04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph 
filters [PASS]
  04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid 
filters   [PASS]
  04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace 
filter command  [PASS]
  04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace 
with cpumask[PASS]
  04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for 
function event triggers   [PASS]
  04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace 
on module   [PASS]
  04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function 
profiling [PASS]
  04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function 
profiler with function tracing[PASS]
  04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading 
of set_ftrace_filter  [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for 
function traceon/off triggers [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing 
error log support [PASS]
  04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and 
deletion of trace instances while setting an event[PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and 
deletion of trace instances   [PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - 
adding and removing  [PASS]
  04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32] Kprobe dynamic event - 
busy event check [PASS]
  04/12 03:26:14 DEBUG| utils:0153| [stdout] # [33] Kprobe dynamic event 
with arguments [PASS]
  04/12 03:26:15 DEBUG| utils:0153| [stdout] # [34] Kprobe event with comm 
arguments[PASS]
  04/12 03:26:15 DEBUG| utils:0153| [stdout] # [35] Kprobe event string 
type argument   [PASS]
  04/12 03:26:16 DEBUG| utils:0153| [stdout] # [36] Kprobe event symbol 
argument[PASS]
  04/12 03:26:18 DEBUG| utils:0153| 

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

[Sean Feole]

apport information

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

Title:
  Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete

Bug description:
  In Focal,

  The following tests fail on baremetal/amd64:

  04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer  
[FAIL]
  04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer   
[FAIL]
  04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test 
inter-event histogram trigger expected fail actions[XFAIL]

  Full output below.

  04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests ===
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check   
[PASS]
  04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing 
check[PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer 
size   [PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing 
setting [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and 
trace_marker  [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - 
add/remove kprobe events [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - 
add/remove synthetic events  [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - 
selective clear (compatibility) [PASS]
  04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - 
generic clear event [PASS]
  04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - 
enable/disable with event level files   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - 
restricts events based on pid   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - 
enable/disable with subsystem level files   [PASS]
  04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - 
enable/disable with top level files [PASS]
  04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from 
module   [PASS]
  04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph 
filters with stack tracer   [PASS]
  04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph 
filters [PASS]
  04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid 
filters   [PASS]
  04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace 
filter command  [PASS]
  04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace 
with cpumask[PASS]
  04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for 
function event triggers   [PASS]
  04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace 
on module   [PASS]
  04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function 
profiling [PASS]
  04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function 
profiler with function tracing[PASS]
  04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading 
of set_ftrace_filter  [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for 
function traceon/off triggers [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing 
error log support [PASS]
  04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and 
deletion of trace instances while setting an event[PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and 
deletion of trace instances   [PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - 
adding and removing  [PASS]
  04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32] Kprobe dynamic event - 
busy event check [PASS]
  04/12 03:26:14 DEBUG| utils:0153| [stdout] # [33] Kprobe dynamic event 
with arguments [PASS]
  04/12 03:26:15 DEBUG| utils:0153| [stdout] # [34] Kprobe event with comm 
arguments[PASS]
  04/12 03:26:15 DEBUG| utils:0153| [stdout] # [35] Kprobe event string 
type argument   [PASS]
  04/12 03:26:16 DEBUG| utils:0153| [stdout] # [36] Kprobe event symbol 
argument[PASS]
  04/12 03:26:18 DEBUG| utils:0153| 

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

[Sean Feole]

apport information

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

Title:
  Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete

Bug description:
  In Focal,

  The following tests fail on baremetal/amd64:

  04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer  
[FAIL]
  04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer   
[FAIL]
  04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test 
inter-event histogram trigger expected fail actions[XFAIL]

  Full output below.

  04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests ===
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check   
[PASS]
  04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing 
check[PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer 
size   [PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing 
setting [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and 
trace_marker  [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - 
add/remove kprobe events [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - 
add/remove synthetic events  [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - 
selective clear (compatibility) [PASS]
  04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - 
generic clear event [PASS]
  04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - 
enable/disable with event level files   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - 
restricts events based on pid   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - 
enable/disable with subsystem level files   [PASS]
  04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - 
enable/disable with top level files [PASS]
  04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from 
module   [PASS]
  04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph 
filters with stack tracer   [PASS]
  04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph 
filters [PASS]
  04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid 
filters   [PASS]
  04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace 
filter command  [PASS]
  04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace 
with cpumask[PASS]
  04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for 
function event triggers   [PASS]
  04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace 
on module   [PASS]
  04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function 
profiling [PASS]
  04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function 
profiler with function tracing[PASS]
  04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading 
of set_ftrace_filter  [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for 
function traceon/off triggers [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing 
error log support [PASS]
  04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and 
deletion of trace instances while setting an event[PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and 
deletion of trace instances   [PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - 
adding and removing  [PASS]
  04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32] Kprobe dynamic event - 
busy event check [PASS]
  04/12 03:26:14 DEBUG| utils:0153| [stdout] # [33] Kprobe dynamic event 
with arguments [PASS]
  04/12 03:26:15 DEBUG| utils:0153| [stdout] # [34] Kprobe event with comm 
arguments[PASS]
  04/12 03:26:15 DEBUG| utils:0153| [stdout] # [35] Kprobe event string 
type argument   [PASS]
  04/12 03:26:16 DEBUG| utils:0153| [stdout] # [36] Kprobe event symbol 
argument[PASS]
  04/12 03:26:18 DEBUG| utils:0153| [stdout] # [37] 

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

[Sean Feole]

apport information

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

Title:
  Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete

Bug description:
  In Focal,

  The following tests fail on baremetal/amd64:

  04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer  
[FAIL]
  04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer   
[FAIL]
  04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test 
inter-event histogram trigger expected fail actions[XFAIL]

  Full output below.

  04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests ===
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check   
[PASS]
  04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing 
check[PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer 
size   [PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing 
setting [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and 
trace_marker  [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - 
add/remove kprobe events [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - 
add/remove synthetic events  [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - 
selective clear (compatibility) [PASS]
  04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - 
generic clear event [PASS]
  04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - 
enable/disable with event level files   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - 
restricts events based on pid   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - 
enable/disable with subsystem level files   [PASS]
  04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - 
enable/disable with top level files [PASS]
  04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from 
module   [PASS]
  04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph 
filters with stack tracer   [PASS]
  04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph 
filters [PASS]
  04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid 
filters   [PASS]
  04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace 
filter command  [PASS]
  04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace 
with cpumask[PASS]
  04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for 
function event triggers   [PASS]
  04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace 
on module   [PASS]
  04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function 
profiling [PASS]
  04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function 
profiler with function tracing[PASS]
  04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading 
of set_ftrace_filter  [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for 
function traceon/off triggers [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing 
error log support [PASS]
  04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and 
deletion of trace instances while setting an event[PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and 
deletion of trace instances   [PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - 
adding and removing  [PASS]
  04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32] Kprobe dynamic event - 
busy event check [PASS]
  04/12 03:26:14 DEBUG| utils:0153| [stdout] # [33] Kprobe dynamic event 
with arguments [PASS]
  04/12 03:26:15 DEBUG| utils:0153| [stdout] # [34] Kprobe event with comm 
arguments[PASS]
  04/12 03:26:15 DEBUG| utils:0153| [stdout] # [35] Kprobe event string 
type argument   [PASS]
  04/12 03:26:16 DEBUG| utils:0153| [stdout] # [36] Kprobe event symbol 
argument[PASS]
  04/12 03:26:18 DEBUG| 

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

[Sean Feole]

apport information

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

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

Title:
  Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete

Bug description:
  In Focal,

  The following tests fail on baremetal/amd64:

  04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer  
[FAIL]
  04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer   
[FAIL]
  04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test 
inter-event histogram trigger expected fail actions[XFAIL]

  Full output below.

  04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests ===
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check   
[PASS]
  04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing 
check[PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer 
size   [PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing 
setting [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and 
trace_marker  [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - 
add/remove kprobe events [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - 
add/remove synthetic events  [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - 
selective clear (compatibility) [PASS]
  04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - 
generic clear event [PASS]
  04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - 
enable/disable with event level files   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - 
restricts events based on pid   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - 
enable/disable with subsystem level files   [PASS]
  04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - 
enable/disable with top level files [PASS]
  04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from 
module   [PASS]
  04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph 
filters with stack tracer   [PASS]
  04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph 
filters [PASS]
  04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid 
filters   [PASS]
  04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace 
filter command  [PASS]
  04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace 
with cpumask[PASS]
  04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for 
function event triggers   [PASS]
  04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace 
on module   [PASS]
  04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function 
profiling [PASS]
  04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function 
profiler with function tracing[PASS]
  04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading 
of set_ftrace_filter  [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for 
function traceon/off triggers [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing 
error log support [PASS]
  04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and 
deletion of trace instances while setting an event[PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and 
deletion of trace instances   [PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - 
adding and removing  [PASS]
  04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32] Kprobe dynamic event - 
busy event check [PASS]
  04/12 03:26:14 DEBUG| utils:0153| [stdout] # [33] Kprobe dynamic event 
with arguments [PASS]
  04/12 03:26:15 DEBUG| utils:0153| [stdout] # [34] Kprobe event with comm 
arguments[PASS]
  04/12 03:26:15 DEBUG| utils:0153| [stdout] # [35] Kprobe event string 
type argument   [PASS]
  04/12 03:26:16 DEBUG| utils:0153| [stdout] # [36] Kprobe event symbol 
argument[PASS]
  04/12 03:26:18 DEBUG| utils:0153| [stdout] # 

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

[Sean Feole]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1873054/+attachment/5354785/+files/Lspci-vt.txt

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

Title:
  Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete

Bug description:
  In Focal,

  The following tests fail on baremetal/amd64:

  04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer  
[FAIL]
  04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer   
[FAIL]
  04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test 
inter-event histogram trigger expected fail actions[XFAIL]

  Full output below.

  04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests ===
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check   
[PASS]
  04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing 
check[PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer 
size   [PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing 
setting [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and 
trace_marker  [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - 
add/remove kprobe events [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - 
add/remove synthetic events  [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - 
selective clear (compatibility) [PASS]
  04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - 
generic clear event [PASS]
  04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - 
enable/disable with event level files   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - 
restricts events based on pid   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - 
enable/disable with subsystem level files   [PASS]
  04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - 
enable/disable with top level files [PASS]
  04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from 
module   [PASS]
  04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph 
filters with stack tracer   [PASS]
  04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph 
filters [PASS]
  04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid 
filters   [PASS]
  04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace 
filter command  [PASS]
  04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace 
with cpumask[PASS]
  04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for 
function event triggers   [PASS]
  04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace 
on module   [PASS]
  04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function 
profiling [PASS]
  04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function 
profiler with function tracing[PASS]
  04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading 
of set_ftrace_filter  [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for 
function traceon/off triggers [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing 
error log support [PASS]
  04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and 
deletion of trace instances while setting an event[PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and 
deletion of trace instances   [PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - 
adding and removing  [PASS]
  04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32] Kprobe dynamic event - 
busy event check [PASS]
  04/12 03:26:14 DEBUG| utils:0153| [stdout] # [33] Kprobe dynamic event 
with arguments [PASS]
  04/12 03:26:15 DEBUG| utils:0153| [stdout] # [34] Kprobe event with comm 
arguments[PASS]
  04/12 03:26:15 DEBUG| utils:0153| [stdout] # [35] Kprobe event string 
type argument   [PASS]
  04/12 03:26:16 DEBUG| utils:0153| [stdout] # [36] Kprobe event symbol 
argument[PASS]
  04/12 03:26:18 DEBUG| utils:0153| [stdout] # 

[Kernel-packages] [Bug 1873054] Re: Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests

[Sean Feole]

apport information

** Tags added: apport-collected uec-images

** Description changed:

  In Focal,
  
  The following tests fail on baremetal/amd64:
  
  04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer  
[FAIL]
  04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer   
[FAIL]
  04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test 
inter-event histogram trigger expected fail actions[XFAIL]
  
  Full output below.
  
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests ===
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check   
[PASS]
  04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing 
check[PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer 
size   [PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing 
setting [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and 
trace_marker  [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - 
add/remove kprobe events [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - 
add/remove synthetic events  [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - 
selective clear (compatibility) [PASS]
  04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - 
generic clear event [PASS]
  04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - 
enable/disable with event level files   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - 
restricts events based on pid   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - 
enable/disable with subsystem level files   [PASS]
  04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - 
enable/disable with top level files [PASS]
  04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from 
module   [PASS]
  04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph 
filters with stack tracer   [PASS]
  04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph 
filters [PASS]
  04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid 
filters   [PASS]
  04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace 
filter command  [PASS]
  04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace 
with cpumask[PASS]
  04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for 
function event triggers   [PASS]
  04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace 
on module   [PASS]
  04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function 
profiling [PASS]
  04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function 
profiler with function tracing[PASS]
  04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading 
of set_ftrace_filter  [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for 
function traceon/off triggers [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing 
error log support [PASS]
  04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and 
deletion of trace instances while setting an event[PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and 
deletion of trace instances   [PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - 
adding and removing  [PASS]
  04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32] Kprobe dynamic event - 
busy event check [PASS]
  04/12 03:26:14 DEBUG| utils:0153| [stdout] # [33] Kprobe dynamic event 
with arguments [PASS]
  04/12 03:26:15 DEBUG| utils:0153| [stdout] # [34] Kprobe event with comm 
arguments[PASS]
  04/12 03:26:15 DEBUG| utils:0153| [stdout] # [35] Kprobe event string 
type argument   [PASS]
  04/12 03:26:16 DEBUG| utils:0153| [stdout] # [36] Kprobe event symbol 
argument[PASS]
  04/12 03:26:18 DEBUG| utils:0153| [stdout] # [37] Kprobe event argument 
syntax[PASS]
  04/12 03:26:20 DEBUG| utils:0153| [stdout] # [38] Kprobes event arguments 
with types  [PASS]
  04/12 03:26:20 DEBUG| utils:0153| [stdout] # [39] Kprobe event 
user-memory access [PASS]
  04/12 03:26:21 DEBUG| utils:0153| [stdout] # [40] Kprobe event 
auto/manual naming [PASS]
  04/12 03:26:23 DEBUG| utils:0153| [stdout] # [41] Kprobe dynamic event 
with function tracer   

[Kernel-packages] [Bug 1869860] Re: Ubuntu mainline kernel v5.6 not supported by bcmwl-kernel-source

[Robert Ross]

Having this same issue with building a custom ubuntu iso and pulling in kernel 
package 5.6-oem. 
Seems package broadcom-sta-dkms has support for 5.6 so I'm going to give that a 
try.

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

Title:
  Ubuntu mainline kernel v5.6 not supported by bcmwl-kernel-source

Status in bcmwl package in Ubuntu:
  New

Bug description:
  I am using Ubuntu 18.04 with kernel 4.15.0-91-generic and packet
  bcmwl-kernel-source version 6.30.223.271+bdcom-0ubuntu5~18.04.1 from
  bionic-updates. Wifi BCM43228 802.11a/b/g/n [14e4:4359] is fine
  working.

  
  But working stops after installing ubuntu mainline kernel v5.6 (image, 
modules, headers-all, headers-amd64). While installing kernel there were error 
messages regarding dkms and no dkms-modul was built.

  
  bcmwl-kernel-source should support kernel v5.6

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

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

[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT

[Alexander]

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

Title:
  No sound on ASUS UX534FT

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  after instal Ubuntu in dual boot alongside Windows 10, I've realised
  there is no sound coming out of mine new ASUS Zenbook 15 UX534FT-
  AA024R in Ubuntu. In Windows there is no problem. Found this topic
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had
  the same problem with driver for Realtek ALC294 which is also mine
  sound card. But even with this fix it is not working on UX534FT. Can
  you please add fix also for this newer model?

  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 29 15:11:25 2019
  InstallationDate: Installed on 2019-10-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1872941] Re: [Ubuntu 20.04] virt-install fails to detect path after images folder name has changed

[Frank Heimes]

** No longer affects: 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/1872941

Title:
  [Ubuntu 20.04] virt-install fails to detect path after images folder
  name has changed

Status in Ubuntu CD Images:
  Opinion
Status in Ubuntu on IBM z Systems:
  Triaged
Status in virt-manager package in Ubuntu:
  Invalid

Bug description:
  Installer version: Latest
  https://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x

  Description/Reproduction:
  Start virt-install with the following options:

  virt-install \
  --name ubuntu20-guest1 \
  --memory 4096 \
  --vcpus 4 \
  --disk "size=4" \
  --location 
http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x \
  --network "network=default" 

  Error:
  ERRORError validating install location: Could not find an installable 
distribution at 
'http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x'

  The location must be the root directory of an install tree.
  See virt-install man page for various distro examples.

  
  Looking at previous releases I would guess it expects an "images" directory 
instead of the new "classic-images" directory. I'm aware of the workaround to 
specify kernel/initramfs directly but that shouldn't be a solution.

  == Comment: #2 - Andre Wild1  - 2020-04-15 03:51:21 ==
  (In reply to comment #0)
  > Installer version: Latest
  > https://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x
  > 

  Sorry I've copied the wrong link. This is the link I've used successfully in 
the past:
  http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1872941/+subscriptions

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

[Kernel-packages] [Bug 1873054] Re: Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests

[Sean Feole]

Also exhibited on ARM64: non-xgene systems.

04/12 03:48:06 DEBUG| utils:0153| [stdout] # [50] Meta-selftest [PASS]
04/12 03:48:17 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer
[FAIL]
04/12 03:48:40 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer 
[FAIL]
04/12 03:48:55 DEBUG| utils:0153| [stdout] # [53] event trigger - test 
inter-event histogram trigger expected fail actions  [XFAIL]
04/12 03:49:16 DEBUG| utils:0153| [stdout] # [54] event trigger - test 
field variable support   [PASS]


We do not see these Ftrace Failures on AWS-Nitro backed ARM64 instances. 


** Tags added: arm64

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

Title:
  Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete

Bug description:
  In Focal,

  The following tests fail on baremetal/amd64:

  04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer  
[FAIL]
  04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer   
[FAIL]
  04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test 
inter-event histogram trigger expected fail actions[XFAIL]

  Full output below.

  04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests ===
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check   
[PASS]
  04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing 
check[PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer 
size   [PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing 
setting [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and 
trace_marker  [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - 
add/remove kprobe events [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - 
add/remove synthetic events  [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - 
selective clear (compatibility) [PASS]
  04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - 
generic clear event [PASS]
  04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - 
enable/disable with event level files   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - 
restricts events based on pid   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - 
enable/disable with subsystem level files   [PASS]
  04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - 
enable/disable with top level files [PASS]
  04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from 
module   [PASS]
  04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph 
filters with stack tracer   [PASS]
  04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph 
filters [PASS]
  04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid 
filters   [PASS]
  04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace 
filter command  [PASS]
  04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace 
with cpumask[PASS]
  04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for 
function event triggers   [PASS]
  04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace 
on module   [PASS]
  04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function 
profiling [PASS]
  04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function 
profiler with function tracing[PASS]
  04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading 
of set_ftrace_filter  [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for 
function traceon/off triggers [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing 
error log support [PASS]
  04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and 
deletion of trace instances while setting an event[PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and 
deletion of trace instances   [PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - 
adding and removing  [PASS]
  04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32] 

[Kernel-packages] [Bug 1873054] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1873054

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

Title:
  Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete

Bug description:
  In Focal,

  The following tests fail on baremetal/amd64:

  04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer  
[FAIL]
  04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer   
[FAIL]
  04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test 
inter-event histogram trigger expected fail actions[XFAIL]

  Full output below.

  04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests ===
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check   
[PASS]
  04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing 
check[PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer 
size   [PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing 
setting [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and 
trace_marker  [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - 
add/remove kprobe events [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - 
add/remove synthetic events  [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - 
selective clear (compatibility) [PASS]
  04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - 
generic clear event [PASS]
  04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - 
enable/disable with event level files   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - 
restricts events based on pid   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - 
enable/disable with subsystem level files   [PASS]
  04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - 
enable/disable with top level files [PASS]
  04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from 
module   [PASS]
  04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph 
filters with stack tracer   [PASS]
  04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph 
filters [PASS]
  04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid 
filters   [PASS]
  04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace 
filter command  [PASS]
  04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace 
with cpumask[PASS]
  04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for 
function event triggers   [PASS]
  04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace 
on module   [PASS]
  04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function 
profiling [PASS]
  04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function 
profiler with function tracing[PASS]
  04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading 
of set_ftrace_filter  [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for 
function traceon/off triggers [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing 
error log support [PASS]
  04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and 
deletion of trace instances while setting an event[PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and 
deletion of trace instances   [PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - 
adding and removing  [PASS]
  04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32] Kprobe dynamic event - 
busy event check 

[Kernel-packages] [Bug 1873054] [NEW] Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests

[Sean Feole]

Public bug reported:

In Focal,

The following tests fail on baremetal/amd64:

04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer
[FAIL]
04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer 
[FAIL]
04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test 
inter-event histogram trigger expected fail actions  [XFAIL]

Full output below.

04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest
04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests ===
04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check 
[PASS]
04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers 
[PASS]
04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test 
[PASS]
04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check  
[PASS]
04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size 
[PASS]
04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing 
setting   [PASS]
04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and 
trace_marker[PASS]
04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - 
add/remove kprobe events   [PASS]
04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - 
add/remove synthetic events[PASS]
04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - 
selective clear (compatibility)   [PASS]
04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - 
generic clear event   [PASS]
04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - 
enable/disable with event level files [PASS]
04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - restricts 
events based on pid [PASS]
04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - 
enable/disable with subsystem level files [PASS]
04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - 
enable/disable with top level files   [PASS]
04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from 
module [PASS]
04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph 
filters with stack tracer [PASS]
04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph 
filters   [PASS]
04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid 
filters [PASS]
04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace 
filter command[PASS]
04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace 
with cpumask  [PASS]
04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for 
function event triggers [PASS]
04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace 
on module [PASS]
04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function 
profiling   [PASS]
04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function 
profiler with function tracing  [PASS]
04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading of 
set_ftrace_filter[PASS]
04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for 
function traceon/off triggers   [PASS]
04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing 
error log support   [PASS]
04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and 
deletion of trace instances while setting an event  [PASS]
04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and 
deletion of trace instances [PASS]
04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - 
adding and removing[PASS]
04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32] Kprobe dynamic event - 
busy event check   [PASS]
04/12 03:26:14 DEBUG| utils:0153| [stdout] # [33] Kprobe dynamic event with 
arguments   [PASS]
04/12 03:26:15 DEBUG| utils:0153| [stdout] # [34] Kprobe event with comm 
arguments  [PASS]
04/12 03:26:15 DEBUG| utils:0153| [stdout] # [35] Kprobe event string type 
argument [PASS]
04/12 03:26:16 DEBUG| utils:0153| [stdout] # [36] Kprobe event symbol 
argument  [PASS]
04/12 03:26:18 DEBUG| utils:0153| [stdout] # [37] Kprobe event argument 
syntax  [PASS]
04/12 03:26:20 DEBUG| utils:0153| [stdout] # [38] Kprobes event arguments 
with types[PASS]
04/12 03:26:20 DEBUG| utils:0153| [stdout] # [39] Kprobe event user-memory 
access   [PASS]
04/12 03:26:21 DEBUG| utils:0153| [stdout] # [40] Kprobe event auto/manual 
naming   [PASS]
04/12 03:26:23 DEBUG| utils:0153| [stdout] # [41] Kprobe dynamic event with 
function tracer [PASS]
04/12 03:26:24 DEBUG| utils:0153| [stdout] # [42] Create/delete multiprobe 
on kprobe event  [PASS]
04/12 03:26:25 DEBUG| utils:0153| [stdout] # [43] Kprobe 

[Kernel-packages] [Bug 1563110]

[lionelmiquel]

Hello,
  I know this issue is closed, but should I post
in this thread if I got a problem with my microp
hone on a E200HA, Ubuntu 18.04, custom kernel bas
ed on 5.6.3 with cx2072x support compiled in and 
right UCM files ?
Or should I create a bug report ?

Thanks.

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Fix Released
Status in alsa-driver package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions

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

[Kernel-packages] [Bug 1866972] Re: ftrace test failed with Register/unregister many kprobe events in ubuntu_kernel_selftests on B-AWS-5.0 / E

[Sean Feole]

** Changed in: ubuntu-kernel-tests
   Status: Invalid => Triaged

** Summary changed:

- ftrace test failed with Register/unregister many kprobe events in 
ubuntu_kernel_selftests on B-AWS-5.0 / E
+ ftrace test failed with Register/unregister many kprobe events in 
ubuntu_kernel_selftests on Metal / E

** Summary changed:

- ftrace test failed with Register/unregister many kprobe events in 
ubuntu_kernel_selftests on Metal / E
+ ftrace test failed with Register/unregister many kprobe events in 
ubuntu_kernel_selftests

** Tags removed: 5.0 aws
** Tags added: sru-20200406

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

** No longer affects: linux (Ubuntu Disco)

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

Title:
  ftrace test failed with Register/unregister many kprobe events in
  ubuntu_kernel_selftests

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Eoan:
  New

Bug description:
  Issue found on c4.large with 5.0.0-1027.30-aws

  Test failed with:
  [42] Register/unregister many kprobe events   [FAIL]

   selftests: ftrace: ftracetest
   
   === Ftrace unit tests ===
   [1] Basic trace file check   [PASS]
   [2] Basic test for tracers   [PASS]
   [3] Basic trace clock test   [PASS]
   [4] Basic event tracing check[PASS]
   [5] Change the ringbuffer size   [PASS]
   [6] Snapshot and tracing setting [PASS]
   [7] trace_pipe and trace_marker  [PASS]
   [8] Generic dynamic event - add/remove kprobe events [PASS]
   [9] Generic dynamic event - add/remove synthetic events  [PASS]
   [10] Generic dynamic event - selective clear (compatibility) [PASS]
   [11] Generic dynamic event - generic clear event [PASS]
   [12] event tracing - enable/disable with event level files   [PASS]
   [13] event tracing - restricts events based on pid   [PASS]
   [14] event tracing - enable/disable with subsystem level files   [PASS]
   [15] event tracing - enable/disable with top level files [PASS]
   [16] Test trace_printk from module   [UNRESOLVED]
   [17] ftrace - function graph filters with stack tracer   [PASS]
   [18] ftrace - function graph filters [PASS]
   [19] ftrace - function pid filters   [PASS]
   [20] ftrace - stacktrace filter command  [PASS]
   [21] ftrace - function trace with cpumask[PASS]
   [22] ftrace - test for function event triggers   [PASS]
   [23] ftrace - function trace on module   [UNRESOLVED]
   [24] ftrace - function profiling [PASS]
   [25] ftrace - function profiler with function tracing[PASS]
   [26] ftrace - test reading of set_ftrace_filter  [PASS]
   [27] ftrace - test for function traceon/off triggers [PASS]
   [28] Test creation and deletion of trace instances while setting an event
[PASS]
   [29] Test creation and deletion of trace instances   [PASS]
   [30] Kprobe dynamic event - adding and removing  [PASS]
   [31] Kprobe dynamic event - busy event check [PASS]
   [32] Kprobe dynamic event with arguments [PASS]
   [33] Kprobe event with comm arguments[PASS]
   [34] Kprobe event string type argument   [PASS]
   [35] Kprobe event symbol argument[PASS]
   [36] Kprobe event argument syntax[PASS]
   [37] Kprobes event arguments with types  [PASS]
   [38] Kprobe event auto/manual naming [PASS]
   [39] Kprobe dynamic event with function tracer   [PASS]
   [40] Kretprobe dynamic event with arguments  [PASS]
   [41] Kretprobe dynamic event with maxactive  [PASS]
   [42] Register/unregister many kprobe events  [FAIL]
   [43] Kprobe dynamic event - adding and removing  [PASS]
   [44] test for the preemptirqsoff tracer  [UNSUPPORTED]
   [45] Test wakeup tracer  [PASS]
   [46] Test wakeup RT tracer   [PASS]
   [47] event trigger - test extended error support [PASS]
   [48] event trigger - test field variable support [PASS]
   [49] event trigger - test multiple actions on hist trigger   [PASS]
   [50] event trigger - test inter-event histogram trigger onmatch action   
[PASS]
   [51] event trigger - test inter-event histogram trigger onmatch-onmax action 
[PASS]
   [52] event trigger - test inter-event histogram trigger onmax action [PASS]
   [53] event trigger - test synthetic_events syntax parser [PASS]
   [54] event trigger - test event enable/disable trigger   [PASS]
   [55] event trigger - test trigger filter [PASS]
   [56] event trigger - test histogram modifiers[PASS]
   [57] event trigger - test multiple histogram triggers[PASS]
   [58] event trigger - test snapshot-trigger   [PASS]
   [59] event trigger - test stacktrace-trigger [PASS]
   [60] trace_marker trigger - test snapshot trigger[PASS]
   

[Kernel-packages] [Bug 1830084] Re: ubuntu_kernel_selftests ftrace fails

[Sean Feole]

** Changed in: ubuntu-kernel-tests
   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/1830084

Title:
  ubuntu_kernel_selftests ftrace fails

Status in ubuntu-kernel-tests:
  Invalid
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-gcp package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  New
Status in linux-aws source package in Disco:
  New
Status in linux-azure source package in Disco:
  Confirmed
Status in linux-gcp source package in Disco:
  Confirmed
Status in linux-oracle source package in Disco:
  New
Status in linux-aws source package in Eoan:
  New
Status in linux-azure source package in Eoan:
  New
Status in linux-gcp source package in Eoan:
  New
Status in linux-oracle source package in Eoan:
  New

Bug description:
  Cloud: Azure
  Series: Disco
  Kernel: 5.0.0-1007.7  linux-azure
  Instance: Standard_D2_v3 and others. 

  05/20 14:24:27 DEBUG| utils:0116| Running 'sudo sh -c 'echo 1 > 
/proc/sys/net/ipv4/conf/all/accept_local''
  05/20 14:24:27 DEBUG| utils:0116| Running 'sudo make -C 
linux/tools/testing/selftests TARGETS=ftrace run_tests'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make: Entering directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Nothing to be done 
for 'all'.
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Leaving directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] TAP version 13
  05/20 14:24:27 DEBUG| utils:0153| [stdout] selftests: ftrace: ftracetest
  05/20 14:24:27 DEBUG| utils:0153| [stdout] 

  05/20 14:24:27 ERROR| utils:0153| [stderr] ./ftracetest: 163: [: Illegal 
number: 
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e === Ftrace unit tests ===
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [1] Basic trace file 
check
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [2] Basic test for 
tracers
  05/20 14:24:31 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:31 DEBUG| utils:0153| [stdout] -e -n [3] Basic trace clock 
test
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [4] Basic event tracing 
check
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [5] Change the 
ringbuffer size
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [6] Snapshot and tracing 
setting
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [7] trace_pipe and 
trace_marker
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [8] Generic dynamic 
event - add/remove kprobe events
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [9] Generic dynamic 
event - add/remove synthetic events
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [10] Generic dynamic 
event - selective clear (compatibility)
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [11] Generic dynamic 
event - generic clear event
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [12] event tracing - 
enable/disable with event level files
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [13] event tracing - 
restricts events based on pid
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [14] event tracing - 
enable/disable with subsystem level files
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [15] event tracing - 
enable/disable with top level files
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [16] Test 

[Kernel-packages] [Bug 1830084] Re: ubuntu_kernel_selftests ftrace fails

[Sean Feole]

After identifying multiple affected archs with different tests failing,
we will open new bugs for each affected arch.

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

Title:
  ubuntu_kernel_selftests ftrace fails

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-gcp package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  New
Status in linux-aws source package in Disco:
  New
Status in linux-azure source package in Disco:
  Confirmed
Status in linux-gcp source package in Disco:
  Confirmed
Status in linux-oracle source package in Disco:
  New
Status in linux-aws source package in Eoan:
  New
Status in linux-azure source package in Eoan:
  New
Status in linux-gcp source package in Eoan:
  New
Status in linux-oracle source package in Eoan:
  New

Bug description:
  Cloud: Azure
  Series: Disco
  Kernel: 5.0.0-1007.7  linux-azure
  Instance: Standard_D2_v3 and others. 

  05/20 14:24:27 DEBUG| utils:0116| Running 'sudo sh -c 'echo 1 > 
/proc/sys/net/ipv4/conf/all/accept_local''
  05/20 14:24:27 DEBUG| utils:0116| Running 'sudo make -C 
linux/tools/testing/selftests TARGETS=ftrace run_tests'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make: Entering directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Nothing to be done 
for 'all'.
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Leaving directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] TAP version 13
  05/20 14:24:27 DEBUG| utils:0153| [stdout] selftests: ftrace: ftracetest
  05/20 14:24:27 DEBUG| utils:0153| [stdout] 

  05/20 14:24:27 ERROR| utils:0153| [stderr] ./ftracetest: 163: [: Illegal 
number: 
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e === Ftrace unit tests ===
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [1] Basic trace file 
check
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [2] Basic test for 
tracers
  05/20 14:24:31 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:31 DEBUG| utils:0153| [stdout] -e -n [3] Basic trace clock 
test
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [4] Basic event tracing 
check
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [5] Change the 
ringbuffer size
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [6] Snapshot and tracing 
setting
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [7] trace_pipe and 
trace_marker
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [8] Generic dynamic 
event - add/remove kprobe events
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [9] Generic dynamic 
event - add/remove synthetic events
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [10] Generic dynamic 
event - selective clear (compatibility)
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [11] Generic dynamic 
event - generic clear event
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [12] event tracing - 
enable/disable with event level files
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [13] event tracing - 
restricts events based on pid
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [14] event tracing - 
enable/disable with subsystem level files
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [15] event tracing - 
enable/disable with top level files
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:35 

[Kernel-packages] [Bug 1837040] Re: function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on Disco ARM64 / B-hwe P9

[Sean Feole]

On Eoan, we no longer see the failure for traceon/off triggers ;
however,

[45] Register/unregister many kprobe events [FAIL]

Is failing, on arm64. Giving there are so many ftracetests open in the
project that are stale, i'm going to close this bug as its originally
intended to target against Disco, and re-open a new one for the new
failure on Eoan, if in fact is does not align with any of the already
existing bugs.

04/12 21:49:30 DEBUG| utils:0153| [stdout] 1..1
04/12 21:49:30 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest
04/12 21:49:30 DEBUG| utils:0153| [stdout] # === Ftrace unit tests ===
04/12 21:49:34 DEBUG| utils:0153| [stdout] # [1] Basic trace file check 
[PASS]
04/12 21:50:35 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers 
[PASS]
04/12 21:51:46 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test 
[PASS]
04/12 21:51:50 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check  
[PASS]
04/12 21:51:54 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size 
[PASS]
04/12 21:52:02 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing 
setting   [PASS]
04/12 21:52:09 DEBUG| utils:0153| [stdout] # [7] trace_pipe and 
trace_marker[PASS]
04/12 21:52:17 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - 
add/remove kprobe events   [PASS]
04/12 21:52:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - 
add/remove synthetic events[PASS]
04/12 21:52:28 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - 
selective clear (compatibility)   [PASS]
04/12 21:52:32 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - 
generic clear event   [PASS]
04/12 21:52:44 DEBUG| utils:0153| [stdout] # [12] event tracing - 
enable/disable with event level files [PASS]
04/12 21:52:59 DEBUG| utils:0153| [stdout] # [13] event tracing - restricts 
events based on pid [PASS]
04/12 21:53:10 DEBUG| utils:0153| [stdout] # [14] event tracing - 
enable/disable with subsystem level files [PASS]
04/12 21:53:21 DEBUG| utils:0153| [stdout] # [15] event tracing - 
enable/disable with top level files   [PASS]
04/12 21:53:26 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from 
module [PASS]
04/12 21:53:48 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph 
filters with stack tracer [PASS]
04/12 21:54:04 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph 
filters   [PASS]
04/12 21:54:42 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid 
filters [PASS]
04/12 21:54:50 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace 
filter command[PASS]
04/12 21:55:06 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace 
with cpumask  [PASS]
04/12 21:55:24 DEBUG| utils:0153| [stdout] # [22] ftrace - test for 
function event triggers [PASS]
04/12 21:55:28 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace 
on module [PASS]
04/12 21:55:34 DEBUG| utils:0153| [stdout] # [24] ftrace - function 
profiling   [PASS]
04/12 21:55:53 DEBUG| utils:0153| [stdout] # [25] ftrace - function 
profiler with function tracing  [PASS]
04/12 21:56:02 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading of 
set_ftrace_filter[PASS]
04/12 21:56:16 DEBUG| utils:0153| [stdout] # [27] ftrace - test for 
function traceon/off triggers   [PASS]
04/12 21:56:20 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing 
error log support   [PASS]
04/12 21:56:28 DEBUG| utils:0153| [stdout] # [29] Test creation and 
deletion of trace instances while setting an event  [PASS]
04/12 21:56:34 DEBUG| utils:0153| [stdout] # [30] Test creation and 
deletion of trace instances [PASS]
04/12 21:56:38 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - 
adding and removing[PASS]
04/12 21:56:42 DEBUG| utils:0153| [stdout] # [32] Kprobe dynamic event - 
busy event check   [PASS]
04/12 21:56:49 DEBUG| utils:0153| [stdout] # [33] Kprobe dynamic event with 
arguments   [PASS]
04/12 21:56:53 DEBUG| utils:0153| [stdout] # [34] Kprobe event with comm 
arguments  [PASS]
04/12 21:56:57 DEBUG| utils:0153| [stdout] # [35] Kprobe event string type 
argument [PASS]
04/12 21:57:01 DEBUG| utils:0153| [stdout] # [36] Kprobe event symbol 
argument  [PASS]
04/12 21:57:06 DEBUG| utils:0153| [stdout] # [37] Kprobe event argument 
syntax  [PASS]
04/12 21:57:25 DEBUG| utils:0153| [stdout] # [38] Kprobes event arguments 
with types[PASS]
04/12 21:57:29 DEBUG| utils:0153| [stdout] # [39] Kprobe event user-memory 
access   [PASS]
04/12 21:57:33 DEBUG| utils:0153| [stdout] # [40] Kprobe event auto/manual 
naming   [PASS]
04/12 21:58:03 DEBUG| utils:0153| [stdout] # [41] Kprobe dynamic event with 
function tracer [PASS]
04/12 21:58:08 DEBUG| utils:0153| [stdout] # [42] Kprobe event parser error 
log check   

[Kernel-packages] [Bug 1866972] Re: ftrace test failed with Register/unregister many kprobe events in ubuntu_kernel_selftests on B-AWS-5.0 / E

[Sean Feole]

Please note disco has been EOL, if the failures are still exhibited with
another release, lets open a new bug as this has been stale for quite
some time

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

Title:
  ftrace test failed with Register/unregister many kprobe events in
  ubuntu_kernel_selftests on B-AWS-5.0 / E

Status in ubuntu-kernel-tests:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  Invalid

Bug description:
  Issue found on c4.large with 5.0.0-1027.30-aws

  Test failed with:
  [42] Register/unregister many kprobe events   [FAIL]

   selftests: ftrace: ftracetest
   
   === Ftrace unit tests ===
   [1] Basic trace file check   [PASS]
   [2] Basic test for tracers   [PASS]
   [3] Basic trace clock test   [PASS]
   [4] Basic event tracing check[PASS]
   [5] Change the ringbuffer size   [PASS]
   [6] Snapshot and tracing setting [PASS]
   [7] trace_pipe and trace_marker  [PASS]
   [8] Generic dynamic event - add/remove kprobe events [PASS]
   [9] Generic dynamic event - add/remove synthetic events  [PASS]
   [10] Generic dynamic event - selective clear (compatibility) [PASS]
   [11] Generic dynamic event - generic clear event [PASS]
   [12] event tracing - enable/disable with event level files   [PASS]
   [13] event tracing - restricts events based on pid   [PASS]
   [14] event tracing - enable/disable with subsystem level files   [PASS]
   [15] event tracing - enable/disable with top level files [PASS]
   [16] Test trace_printk from module   [UNRESOLVED]
   [17] ftrace - function graph filters with stack tracer   [PASS]
   [18] ftrace - function graph filters [PASS]
   [19] ftrace - function pid filters   [PASS]
   [20] ftrace - stacktrace filter command  [PASS]
   [21] ftrace - function trace with cpumask[PASS]
   [22] ftrace - test for function event triggers   [PASS]
   [23] ftrace - function trace on module   [UNRESOLVED]
   [24] ftrace - function profiling [PASS]
   [25] ftrace - function profiler with function tracing[PASS]
   [26] ftrace - test reading of set_ftrace_filter  [PASS]
   [27] ftrace - test for function traceon/off triggers [PASS]
   [28] Test creation and deletion of trace instances while setting an event
[PASS]
   [29] Test creation and deletion of trace instances   [PASS]
   [30] Kprobe dynamic event - adding and removing  [PASS]
   [31] Kprobe dynamic event - busy event check [PASS]
   [32] Kprobe dynamic event with arguments [PASS]
   [33] Kprobe event with comm arguments[PASS]
   [34] Kprobe event string type argument   [PASS]
   [35] Kprobe event symbol argument[PASS]
   [36] Kprobe event argument syntax[PASS]
   [37] Kprobes event arguments with types  [PASS]
   [38] Kprobe event auto/manual naming [PASS]
   [39] Kprobe dynamic event with function tracer   [PASS]
   [40] Kretprobe dynamic event with arguments  [PASS]
   [41] Kretprobe dynamic event with maxactive  [PASS]
   [42] Register/unregister many kprobe events  [FAIL]
   [43] Kprobe dynamic event - adding and removing  [PASS]
   [44] test for the preemptirqsoff tracer  [UNSUPPORTED]
   [45] Test wakeup tracer  [PASS]
   [46] Test wakeup RT tracer   [PASS]
   [47] event trigger - test extended error support [PASS]
   [48] event trigger - test field variable support [PASS]
   [49] event trigger - test multiple actions on hist trigger   [PASS]
   [50] event trigger - test inter-event histogram trigger onmatch action   
[PASS]
   [51] event trigger - test inter-event histogram trigger onmatch-onmax action 
[PASS]
   [52] event trigger - test inter-event histogram trigger onmax action [PASS]
   [53] event trigger - test synthetic_events syntax parser [PASS]
   [54] event trigger - test event enable/disable trigger   [PASS]
   [55] event trigger - test trigger filter [PASS]
   [56] event trigger - test histogram modifiers[PASS]
   [57] event trigger - test multiple histogram triggers[PASS]
   [58] event trigger - test snapshot-trigger   [PASS]
   [59] event trigger - test stacktrace-trigger [PASS]
   [60] trace_marker trigger - test snapshot trigger[PASS]
   [61] trace_marker trigger - test histogram with synthetic event against 
kernel event [PASS]
   [62] trace_marker trigger - test histogram with synthetic event  [PASS]
   [63] event trigger - test traceon/off trigger[PASS]
   [64] (instance) Basic test for tracers   [PASS]
   [65] (instance) Basic trace clock test   [PASS]
   [66] (instance) Change the ringbuffer size   [PASS]
   [67] (instance) Snapshot and tracing setting [PASS]
   [68] (instance) trace_pipe and trace_marker  [PASS]
   [69] (instance) event tracing - enable/disable with event level files
[PASS]
   

[Kernel-packages] [Bug 1866972] Re: ftrace test failed with Register/unregister many kprobe events in ubuntu_kernel_selftests on B-AWS-5.0 / E

[Sean Feole]

No longer see a failure with KProbe events on AWS for SRU cycle
2020.04.06 : 5.3.0-1017.18

[41] Kprobe dynamic event with function tracer  [PASS]
[42] Kprobe event parser error log check[PASS]
[43] Kretprobe dynamic event with arguments [PASS]


** Changed in: ubuntu-kernel-tests
   Status: New => Invalid

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

** Changed in: linux (Ubuntu Disco)
   Status: Incomplete => 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/1866972

Title:
  ftrace test failed with Register/unregister many kprobe events in
  ubuntu_kernel_selftests on B-AWS-5.0 / E

Status in ubuntu-kernel-tests:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  Invalid

Bug description:
  Issue found on c4.large with 5.0.0-1027.30-aws

  Test failed with:
  [42] Register/unregister many kprobe events   [FAIL]

   selftests: ftrace: ftracetest
   
   === Ftrace unit tests ===
   [1] Basic trace file check   [PASS]
   [2] Basic test for tracers   [PASS]
   [3] Basic trace clock test   [PASS]
   [4] Basic event tracing check[PASS]
   [5] Change the ringbuffer size   [PASS]
   [6] Snapshot and tracing setting [PASS]
   [7] trace_pipe and trace_marker  [PASS]
   [8] Generic dynamic event - add/remove kprobe events [PASS]
   [9] Generic dynamic event - add/remove synthetic events  [PASS]
   [10] Generic dynamic event - selective clear (compatibility) [PASS]
   [11] Generic dynamic event - generic clear event [PASS]
   [12] event tracing - enable/disable with event level files   [PASS]
   [13] event tracing - restricts events based on pid   [PASS]
   [14] event tracing - enable/disable with subsystem level files   [PASS]
   [15] event tracing - enable/disable with top level files [PASS]
   [16] Test trace_printk from module   [UNRESOLVED]
   [17] ftrace - function graph filters with stack tracer   [PASS]
   [18] ftrace - function graph filters [PASS]
   [19] ftrace - function pid filters   [PASS]
   [20] ftrace - stacktrace filter command  [PASS]
   [21] ftrace - function trace with cpumask[PASS]
   [22] ftrace - test for function event triggers   [PASS]
   [23] ftrace - function trace on module   [UNRESOLVED]
   [24] ftrace - function profiling [PASS]
   [25] ftrace - function profiler with function tracing[PASS]
   [26] ftrace - test reading of set_ftrace_filter  [PASS]
   [27] ftrace - test for function traceon/off triggers [PASS]
   [28] Test creation and deletion of trace instances while setting an event
[PASS]
   [29] Test creation and deletion of trace instances   [PASS]
   [30] Kprobe dynamic event - adding and removing  [PASS]
   [31] Kprobe dynamic event - busy event check [PASS]
   [32] Kprobe dynamic event with arguments [PASS]
   [33] Kprobe event with comm arguments[PASS]
   [34] Kprobe event string type argument   [PASS]
   [35] Kprobe event symbol argument[PASS]
   [36] Kprobe event argument syntax[PASS]
   [37] Kprobes event arguments with types  [PASS]
   [38] Kprobe event auto/manual naming [PASS]
   [39] Kprobe dynamic event with function tracer   [PASS]
   [40] Kretprobe dynamic event with arguments  [PASS]
   [41] Kretprobe dynamic event with maxactive  [PASS]
   [42] Register/unregister many kprobe events  [FAIL]
   [43] Kprobe dynamic event - adding and removing  [PASS]
   [44] test for the preemptirqsoff tracer  [UNSUPPORTED]
   [45] Test wakeup tracer  [PASS]
   [46] Test wakeup RT tracer   [PASS]
   [47] event trigger - test extended error support [PASS]
   [48] event trigger - test field variable support [PASS]
   [49] event trigger - test multiple actions on hist trigger   [PASS]
   [50] event trigger - test inter-event histogram trigger onmatch action   
[PASS]
   [51] event trigger - test inter-event histogram trigger onmatch-onmax action 
[PASS]
   [52] event trigger - test inter-event histogram trigger onmax action [PASS]
   [53] event trigger - test synthetic_events syntax parser [PASS]
   [54] event trigger - test event enable/disable trigger   [PASS]
   [55] event trigger - test trigger filter [PASS]
   [56] event trigger - test histogram modifiers[PASS]
   [57] event trigger - test multiple histogram triggers[PASS]
   [58] event trigger - test snapshot-trigger   [PASS]
   [59] event trigger - test stacktrace-trigger [PASS]
   [60] trace_marker trigger - test snapshot trigger[PASS]
   [61] trace_marker trigger - test histogram with synthetic event against 
kernel event [PASS]
   [62] trace_marker trigger - test histogram with synthetic event  [PASS]
   [63] event trigger - test traceon/off trigger[PASS]
   [64] (instance) Basic test for tracers   

[Kernel-packages] [Bug 1862588] Re: user_notification_basic in seccomp of ubuntu_kernel_selftest failed on Bionic-5.0 Kernels

[Thadeu Lima de Souza Cascardo]

I sent a revert for the patch that PHLin identified.

** Changed in: linux (Ubuntu Eoan)
   Status: Confirmed => In Progress

** Changed in: linux (Ubuntu Disco)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Disco)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu Disco)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

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

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1862588

Title:
  user_notification_basic in seccomp of ubuntu_kernel_selftest failed on
  Bionic-5.0 Kernels

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in linux-aws package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-signed-oracle-5.0 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-aws source package in Bionic:
  New
Status in linux-gcp source package in Bionic:
  New
Status in linux-signed-oracle-5.0 source package in Bionic:
  New
Status in linux source package in Disco:
  In Progress
Status in linux-aws source package in Disco:
  New
Status in linux-gcp source package in Disco:
  New
Status in linux-signed-oracle-5.0 source package in Disco:
  New
Status in linux source package in Eoan:
  In Progress
Status in linux-aws source package in Eoan:
  New
Status in linux-gcp source package in Eoan:
  New
Status in linux-signed-oracle-5.0 source package in Eoan:
  New

Bug description:
  [Impact]
  Running seccomp kernel selftests will fail.

  [Test case]
  Run linux/tools/testing/selftests/seccomp/seccomp_bpf.

  On failure:

  seccomp_bpf.c:3149:global.user_notification_basic:Expected -1 
(18446744073709551615) == ret (0)
  seccomp_bpf.c:3150:global.user_notification_basic:Expected EINVAL (22) == 
errno (0)
  global.user_notification_basic: Test failed at step #3
  [ FAIL ] global.user_notification_basic

  On success:

  [ RUN  ] global.user_notification_basic
  [   OK ] global.user_notification_basic

  
  [Regression potential]
  The test is checking that the given structure which the kernel will write to 
is all zeroes. It's doing it because it wants userspace to have the possibility 
in the future to give data there indicating support for an extension that might 
be developed in the future. As the test is there right now, not applying the 
breaking uABI fix might cause us to miss applications that would break in 
future kernels. As the backport for that is prone for more regression 
potential, we are deciding to revert the new test.

  ==

  Issue found on Oracle Bionic 5.0 (oracle : 5.0.0-1011.16 : amd64)

  [ RUN  ] global.user_notification_basic
  seccomp_bpf.c:3149:global.user_notification_basic:Expected -1 
(18446744073709551615) == ret (0)
  seccomp_bpf.c:3150:global.user_notification_basic:Expected EINVAL (22) == 
errno (0)
  global.user_notification_basic: Test failed at step #3
  [ FAIL ] global.user_notification_basic

  This cannot be reproduced with the kselftest in older kernel, probably
  a test case issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1011-oracle 5.0.0-1011.16
  ProcVersionSignature: User Name 5.0.0-1011.16-oracle 5.0.21
  Uname: Linux 5.0.0-1011-oracle x86_64
  ApportVersion: 2.20.9-0ubuntu7.10
  Architecture: amd64
  Date: Mon Feb 10 05:17:54 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-oracle-5.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1862588/+subscriptions

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

[Kernel-packages] [Bug 1873043] [NEW] Bionic update: upstream stable patchset 2020-04-15

[Kamal Mostafa]

Public bug reported:

SRU Justification

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

   upstream stable patchset 2020-04-15

Ported from the following upstream stable releases:
v4.14.176, v4.19.115

   from git://git.kernel.org/

ipv4: fix a RCU-list lock in fib_triestat_seq_show
net, ip_tunnel: fix interface lookup with no key
sctp: fix refcount bug in sctp_wfree
sctp: fix possibly using a bad saddr with a given dst
drm/bochs: downgrade pci_request_region failure from error to warning
initramfs: restore default compression behavior
tools/power turbostat: Fix gcc build warnings
drm/etnaviv: replace MMU flush marker with flush sequence
blk-mq: sync the update nr_hw_queues with blk_mq_queue_tag_busy_iter
blk-mq: Allow blocking queue tag iter callbacks
misc: pci_endpoint_test: Fix to support > 10 pci-endpoint-test devices
coresight: do not use the BIT() macro in the UAPI header
padata: always acquire cpu_hotplug_lock before pinst->lock
mm: mempolicy: require at least one nodeid for MPOL_PREFERRED
ipv6: don't auto-add link-local address to lag ports
net: dsa: bcm_sf2: Ensure correct sub-node is parsed
net: phy: micrel: kszphy_resume(): add delay after genphy_resume() before 
accessing PHY registers
net: stmmac: dwmac1000: fix out-of-bounds mac address reg setting
slcan: Don't transmit uninitialized stack data in padding
mlxsw: spectrum_flower: Do not stop at FLOW_ACTION_VLAN_MANGLE
random: always use batched entropy for get_random_u{32,64}
tools/accounting/getdelays.c: fix netlink attribute length
hwrng: imx-rngc - fix an error path
ASoC: jz4740-i2s: Fix divider written at incorrect offset in register
IB/hfi1: Call kobject_put() when kobject_init_and_add() fails
IB/hfi1: Fix memory leaks in sysfs registration and unregistration
ceph: remove the extra slashes in the server path
ceph: canonicalize server path in place
Bluetooth: RFCOMM: fix ODEBUG bug in rfcomm_dev_ioctl
RDMA/cm: Update num_paths in cma_resolve_iboe_route error flow
fbcon: fix null-ptr-deref in fbcon_switch
clk: qcom: rcg: Return failure for RCG update
drm/msm: stop abusing dma_map/unmap for cache
arm64: Fix size of __early_cpu_boot_status
rpmsg: glink: Remove chunk size word align warning
usb: dwc3: don't set gadget->is_otg flag
drm_dp_mst_topology: fix broken drm_dp_sideband_parse_remote_dpcd_read()
drm/msm: Use the correct dma_sync calls in msm_gem
misc: rtsx: set correct pcr_ops for rts522A
mei: me: add cedar fork device ids
power: supply: axp288_charger: Add special handling for HP Pavilion x2 10
rxrpc: Fix sendmsg(MSG_WAITALL) handling
bitops: protect variables in set_mask_bits() macro
RDMA/ucma: Put a lock around every call to the rdma_cm layer
RDMA/cma: Teach lockdep about the order of rtnl and lock
UBUNTU: upstream stable to v4.14.176, v4.19.115

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

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Description changed:

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

[Kernel-packages] [Bug 1860552] Re: Xiaomi RedmiBook 14" Ryzen Edition broken WiFi

[ALEKSEI VOLKOV]

[   67.221260] ath10k_pci :01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 
reset_mode 0   [   67.487211] ath10k_pci :01:00.0: qca6174 hw3.2 target 
0x0503 chip_id 0x00340aff sub 11ad:0847 
   [   67.487214] 
ath10k_pci :01:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0   
   [   67.487753] ath10k_pci :01:00.0: firmware ver 
WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 
29eb8ca1[   
67.552054] ath10k_pci :01:00.0: failed to fetch board data for 
bus=pci,vendor=168c,device=003e,subsystem-vendor=11ad,subsystem-device=0847 
from ath10k/QCA6174/hw3.0/board-2.bin
[   67.552240] ath10k_pci :01:00.0: board_file api 1 bmi_id N/A crc32 
ed5f849a
[   70.821819] ath10k_pci :01:00.0: htt version request timed out   
  [   70.821824] ath10k_pci :01:00.0: failed to setup htt: 
-110 [   70.901871] ath10k_pci :01:00.0: 
could not init core (-110)
[   70.901919] ath10k_pci :01:00.0: could not probe fw (-110)   
  kot@RedmiBook:~$ uname -a 
Linux RedmiBook 5.6.4-050604-generic 
#202004131234 SMP Mon Apr 13 12:36:46 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Xiaomi RedmiBook 14" Ryzen Edition broken WiFi

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  
  Running

  Linux RedmiBook 5.3.0-26-generic #28-Ubuntu SMP Wed Dec 18 05:37:46 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux
  lspci reports the device

  01:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
  dmesg shows following messages when modprobe ath10_pci

  [   35.405479] ath10k_pci :01:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [   35.677189] ath10k_pci :01:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 11ad:0847
  [   35.677191] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [   35.677655] ath10k_pci :01:00.0: firmware ver 
WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 
29eb8ca1
  [   35.741238] ath10k_pci :01:00.0: failed to fetch board data for 
bus=pci,vendor=168c,device=003e,subsystem-vendor=11ad,subsystem-device=0847 
from ath10k/QCA6174/hw3.0/board-2.bin
  [   35.741396] ath10k_pci :01:00.0: board_file api 1 bmi_id N/A crc32 
ed5f849a
  [   35.813765] ath10k_pci :01:00.0: unsupported HTC service id: 1536
  [   36.237594] ath10k_pci :01:00.0: htt version request timed out
  [   36.237601] ath10k_pci :01:00.0: failed to setup htt: -110
  [   36.317707] ath10k_pci :01:00.0: could not init core (-110)
  [   36.317770] ath10k_pci :01:00.0: could not probe fw (-110)

  as a result no wifi no networks visible and no connection possible

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-firmware 1.183.3
  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
  Date: Wed Jan 22 16:26:03 2020
  Dependencies:
   
  InstallationDate: Installed on 2020-01-20 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1860552] Re: Xiaomi RedmiBook 14" Ryzen Edition broken WiFi

[ALEKSEI VOLKOV]

Recent 5.6.4 kernel with latest firmware git pull does not get it alive.

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

Title:
  Xiaomi RedmiBook 14" Ryzen Edition broken WiFi

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  
  Running

  Linux RedmiBook 5.3.0-26-generic #28-Ubuntu SMP Wed Dec 18 05:37:46 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux
  lspci reports the device

  01:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
  dmesg shows following messages when modprobe ath10_pci

  [   35.405479] ath10k_pci :01:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [   35.677189] ath10k_pci :01:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 11ad:0847
  [   35.677191] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [   35.677655] ath10k_pci :01:00.0: firmware ver 
WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 
29eb8ca1
  [   35.741238] ath10k_pci :01:00.0: failed to fetch board data for 
bus=pci,vendor=168c,device=003e,subsystem-vendor=11ad,subsystem-device=0847 
from ath10k/QCA6174/hw3.0/board-2.bin
  [   35.741396] ath10k_pci :01:00.0: board_file api 1 bmi_id N/A crc32 
ed5f849a
  [   35.813765] ath10k_pci :01:00.0: unsupported HTC service id: 1536
  [   36.237594] ath10k_pci :01:00.0: htt version request timed out
  [   36.237601] ath10k_pci :01:00.0: failed to setup htt: -110
  [   36.317707] ath10k_pci :01:00.0: could not init core (-110)
  [   36.317770] ath10k_pci :01:00.0: could not probe fw (-110)

  as a result no wifi no networks visible and no connection possible

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-firmware 1.183.3
  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
  Date: Wed Jan 22 16:26:03 2020
  Dependencies:
   
  InstallationDate: Installed on 2020-01-20 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0

[trickv]

I think I've been having the same issue as well, but I'm also not sure
that this is 100% "new". The symptoms I'm having are consistent (mouse
cursor continues to move, video freezes for ~2 seconds at a time leading
me to think that the machine has crashed, GPU HANG and Resetting rcs0
log events, but machine is running underneath which is obvious because
audio keeps working.)  I can kill the offending video process (Zoom) and
the issue subsides.

I can reliably reproduce the problem on 5.3.0-46-generic (Ubuntu 19.10
latest) and downgrading to 5.3.0-45-generic seemed at first to fix the
problem. But I think that it's just less frequent on the previous
kernels.  I use my machine 5 days a week for 2-4 hours a day on Zoom.
With the -46 kernel, simply launching a Zoom meeting kicks off the
problem.  However today after downgrading to the -45 kernel, while the
problem doesn't immediately happen, it has "glitched" once where the
machine had the same behavior for ~2 seconds and went back to working as
expected.

Looking back over the last 3 months, these events - assuming that the 
"Resetting rcs0 for hang on rcs0" log event indicates the 2 second video 
glitch, it's been rather common.  It's just *much* more common on the -46 
kernel.  Attached is a grep of journalctl since 2020-01-01 for the relevant log 
messages:
- kernel boot message to show the version
- i915 GPU HANG
- i915 Resetting rcs0 for hang on rcs0

Command: journalctl -o short-iso --since=2020-01-01 | egrep "Command
line: |Resetting rcs0 for hang on rcs0|GPU HANG"

** Attachment added: "lp-1872001-logs.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+attachment/5354740/+files/lp-1872001-logs.txt

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

Title:
  5.3.0-46-generic - i915 - frequent GPU hangs  / resets rcs0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent
  (every couple of minutes) GPU hangs and reset manifesting as 2-3
  seconds freezes of the GUI (other than the mouse pointer).

  No particular triggers identified although have Chrome / Chromium
  running with Hardware Acceleration enabled does appear to increase the
  frequency.

  I have seen incidences of these hangs in jounralctl output using
  previous kernels in the 5.3.0-xx series but they were very infrequent
  (one or twice in a week of daily usage)

  System Info
  steve@steve-Inspiron-5580:~$ inxi -SCGxxxz
  System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 
compiler: gcc v: 7.5.0
     Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 
Distro: Linux Mint 19.3 Tricia
     base: Ubuntu 18.04 bionic
  CPU:   Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT 
MCP arch: Kaby Lake rev: B
     L2 cache: 6144 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 28800
     Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 
800 3: 800 4: 800 5: 800 6: 800 7: 800
     8: 800
  Graphics:  Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 
00:02.0 chip ID: 8086:3ea0
     Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: 
fbdev,vesa resolution: 1920x1080~60Hz
     OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 
GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0
     direct render: Yes

  steve@steve-Inspiron-5580:~$ journalctl -b | grep i915
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: 
deactivate vga console
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: 
changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC 
firmware i915/kbl_dmc_ver1_04.bin (v1.4)
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 
20190619 for :00:02.0 on minor 0
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary 
device
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb 
frame buffer device
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound 
:00:02.0 (ops i915_audio_component_bind_ops [i915])
  Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: 
ecode 9:0:0x, hang on rcs0
  Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0
  Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0
  Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0
  Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0

  I note another user has reported similar issues on 

[Kernel-packages] [Bug 1830084] Re: ubuntu_kernel_selftests ftrace fails

[Sean Feole]

** Tags added: sru-20200406

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

Title:
  ubuntu_kernel_selftests ftrace fails

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-gcp package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  New
Status in linux-aws source package in Disco:
  New
Status in linux-azure source package in Disco:
  Confirmed
Status in linux-gcp source package in Disco:
  Confirmed
Status in linux-oracle source package in Disco:
  New
Status in linux-aws source package in Eoan:
  New
Status in linux-azure source package in Eoan:
  New
Status in linux-gcp source package in Eoan:
  New
Status in linux-oracle source package in Eoan:
  New

Bug description:
  Cloud: Azure
  Series: Disco
  Kernel: 5.0.0-1007.7  linux-azure
  Instance: Standard_D2_v3 and others. 

  05/20 14:24:27 DEBUG| utils:0116| Running 'sudo sh -c 'echo 1 > 
/proc/sys/net/ipv4/conf/all/accept_local''
  05/20 14:24:27 DEBUG| utils:0116| Running 'sudo make -C 
linux/tools/testing/selftests TARGETS=ftrace run_tests'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make: Entering directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Nothing to be done 
for 'all'.
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Leaving directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] TAP version 13
  05/20 14:24:27 DEBUG| utils:0153| [stdout] selftests: ftrace: ftracetest
  05/20 14:24:27 DEBUG| utils:0153| [stdout] 

  05/20 14:24:27 ERROR| utils:0153| [stderr] ./ftracetest: 163: [: Illegal 
number: 
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e === Ftrace unit tests ===
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [1] Basic trace file 
check
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [2] Basic test for 
tracers
  05/20 14:24:31 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:31 DEBUG| utils:0153| [stdout] -e -n [3] Basic trace clock 
test
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [4] Basic event tracing 
check
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [5] Change the 
ringbuffer size
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [6] Snapshot and tracing 
setting
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [7] trace_pipe and 
trace_marker
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [8] Generic dynamic 
event - add/remove kprobe events
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [9] Generic dynamic 
event - add/remove synthetic events
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [10] Generic dynamic 
event - selective clear (compatibility)
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [11] Generic dynamic 
event - generic clear event
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [12] event tracing - 
enable/disable with event level files
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [13] event tracing - 
restricts events based on pid
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [14] event tracing - 
enable/disable with subsystem level files
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [15] event tracing - 
enable/disable with top level files
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [16] Test trace_printk 
from module
  05/20 

[Kernel-packages] [Bug 1862588] Re: user_notification_basic in seccomp of ubuntu_kernel_selftest failed on Bionic-5.0 Kernels

[Sean Feole]

AWS/ Eoan/ 5.3.0-1017.18 affected. 
188.04/09 02:20:14 DEBUG| utils:0153| [stdout] # 
seccomp_bpf.c:3160:global.user_notification_basic:Expected -1 
(18446744073709551615) == ret (0)
189.04/09 02:20:14 DEBUG| utils:0153| [stdout] # 
seccomp_bpf.c:3161:global.user_notification_basic:Expected EINVAL (22) == errno 
(0)
190.04/09 02:20:14 DEBUG| utils:0153| [stdout] # fter_ptrace

** Tags added: sru-20200406

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

Title:
  user_notification_basic in seccomp of ubuntu_kernel_selftest failed on
  Bionic-5.0 Kernels

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-signed-oracle-5.0 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-aws source package in Bionic:
  New
Status in linux-gcp source package in Bionic:
  New
Status in linux-signed-oracle-5.0 source package in Bionic:
  New
Status in linux source package in Disco:
  Incomplete
Status in linux-aws source package in Disco:
  New
Status in linux-gcp source package in Disco:
  New
Status in linux-signed-oracle-5.0 source package in Disco:
  New
Status in linux source package in Eoan:
  Confirmed
Status in linux-aws source package in Eoan:
  New
Status in linux-gcp source package in Eoan:
  New
Status in linux-signed-oracle-5.0 source package in Eoan:
  New

Bug description:
  [Impact]
  Running seccomp kernel selftests will fail.

  [Test case]
  Run linux/tools/testing/selftests/seccomp/seccomp_bpf.

  On failure:

  seccomp_bpf.c:3149:global.user_notification_basic:Expected -1 
(18446744073709551615) == ret (0)
  seccomp_bpf.c:3150:global.user_notification_basic:Expected EINVAL (22) == 
errno (0)
  global.user_notification_basic: Test failed at step #3
  [ FAIL ] global.user_notification_basic

  On success:

  [ RUN  ] global.user_notification_basic
  [   OK ] global.user_notification_basic

  
  [Regression potential]
  The test is checking that the given structure which the kernel will write to 
is all zeroes. It's doing it because it wants userspace to have the possibility 
in the future to give data there indicating support for an extension that might 
be developed in the future. As the test is there right now, not applying the 
breaking uABI fix might cause us to miss applications that would break in 
future kernels. As the backport for that is prone for more regression 
potential, we are deciding to revert the new test.

  ==

  Issue found on Oracle Bionic 5.0 (oracle : 5.0.0-1011.16 : amd64)

  [ RUN  ] global.user_notification_basic
  seccomp_bpf.c:3149:global.user_notification_basic:Expected -1 
(18446744073709551615) == ret (0)
  seccomp_bpf.c:3150:global.user_notification_basic:Expected EINVAL (22) == 
errno (0)
  global.user_notification_basic: Test failed at step #3
  [ FAIL ] global.user_notification_basic

  This cannot be reproduced with the kselftest in older kernel, probably
  a test case issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1011-oracle 5.0.0-1011.16
  ProcVersionSignature: User Name 5.0.0-1011.16-oracle 5.0.21
  Uname: Linux 5.0.0-1011-oracle x86_64
  ApportVersion: 2.20.9-0ubuntu7.10
  Architecture: amd64
  Date: Mon Feb 10 05:17:54 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-oracle-5.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1862588/+subscriptions

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

[Kernel-packages] [Bug 1872941] Re: [Ubuntu 20.04] virt-install fails to detect path after images folder name has changed

[Dimitri John Ledkov]

Renaming the artefacts was a compromise. the other option was to not
publish them at all.

d-i artefacts will not exist for 20.10 release, nor for 20.04.1 release,
on any architecture. Thus renamed d-i artefacts is a transitional period
of ~3 months until 20.04.1 is released.

cloud-images for s390x with working cloud-init existed since the pre-
release of the very first s390x architecture build. And work with
xenial, bionic, and focal, and all intermediate releases.

Why is using cloud-images not suitable for your test team which works
for all Ubuntu s390x releases, and are pre-built and refreshed for every
new kernel SRU? Unlike the d-i based images which are only refreshed
every 6 months?

https://cloud-images.ubuntu.com/ are genuinely more up to date, and are
quicker to provision than d-i based installs. There are tested/curated
release streams with ~2-3 week cadence, and daily streams which are
updated ~1-3 days, with all packages up to date from the first boot.

Can we help you move away from virt-instal d-i, to booting cloud images
with any configuration applied on first-boot with cloud-init?

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

Title:
  [Ubuntu 20.04] virt-install fails to detect path after images folder
  name has changed

Status in Ubuntu CD Images:
  Opinion
Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in virt-manager package in Ubuntu:
  Invalid

Bug description:
  Installer version: Latest
  https://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x

  Description/Reproduction:
  Start virt-install with the following options:

  virt-install \
  --name ubuntu20-guest1 \
  --memory 4096 \
  --vcpus 4 \
  --disk "size=4" \
  --location 
http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x \
  --network "network=default" 

  Error:
  ERRORError validating install location: Could not find an installable 
distribution at 
'http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x'

  The location must be the root directory of an install tree.
  See virt-install man page for various distro examples.

  
  Looking at previous releases I would guess it expects an "images" directory 
instead of the new "classic-images" directory. I'm aware of the workaround to 
specify kernel/initramfs directly but that shouldn't be a solution.

  == Comment: #2 - Andre Wild1  - 2020-04-15 03:51:21 ==
  (In reply to comment #0)
  > Installer version: Latest
  > https://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x
  > 

  Sorry I've copied the wrong link. This is the link I've used successfully in 
the past:
  http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1872941/+subscriptions

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

[Kernel-packages] [Bug 1872941] Re: [Ubuntu 20.04] virt-install fails to detect path after images folder name has changed

[Dimitri John Ledkov]

** Also affects: ubuntu-cdimage
   Importance: Undecided
   Status: New

** Changed in: ubuntu-cdimage
   Status: New => Opinion

** Changed in: virt-manager (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/1872941

Title:
  [Ubuntu 20.04] virt-install fails to detect path after images folder
  name has changed

Status in Ubuntu CD Images:
  Opinion
Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in virt-manager package in Ubuntu:
  Invalid

Bug description:
  Installer version: Latest
  https://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x

  Description/Reproduction:
  Start virt-install with the following options:

  virt-install \
  --name ubuntu20-guest1 \
  --memory 4096 \
  --vcpus 4 \
  --disk "size=4" \
  --location 
http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x \
  --network "network=default" 

  Error:
  ERRORError validating install location: Could not find an installable 
distribution at 
'http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x'

  The location must be the root directory of an install tree.
  See virt-install man page for various distro examples.

  
  Looking at previous releases I would guess it expects an "images" directory 
instead of the new "classic-images" directory. I'm aware of the workaround to 
specify kernel/initramfs directly but that shouldn't be a solution.

  == Comment: #2 - Andre Wild1  - 2020-04-15 03:51:21 ==
  (In reply to comment #0)
  > Installer version: Latest
  > https://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x
  > 

  Sorry I've copied the wrong link. This is the link I've used successfully in 
the past:
  http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1872941/+subscriptions

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

[Kernel-packages] [Bug 1872526] Re: dbgsym package for linux-image-4.15.0-1065-aws missing

[Sean Feole]

We have identified the problem as to why this package is not in -updates
it would appear the copy process from -proposed to -updates was stalled.
Awaiting some requests to see if the package can be re-triggered for
another copy attempt

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

Title:
  dbgsym package for linux-image-4.15.0-1065-aws missing

Status in linux-aws package in Ubuntu:
  Triaged

Bug description:
  On April 6th, a new linux-aws was released, targeting linux-
  image-4.15.0-1065-aws. However it's been over a week and the linux-
  image-4.15.0-1065-aws-dbgsym is still not available on
  http://ddebs.ubuntu.com/ubuntu "bionic-updates". It does seem to be
  there on "bionic-proposed", but I think it should be there on "bionic-
  updates" as well given that "linux-image-4.15.0-1065-aws" is there on
  bionic-updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1065-aws (not installed)
  ProcVersionSignature: User Name 4.15.0-1051.53-aws 4.15.18
  Uname: Linux 4.15.0-1051-aws x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Mon Apr 13 19:00:32 2020
  Ec2AMI: ami-096bb69690a48bcc9
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2a
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-aws
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1871687] Re: System hard locks up intermittently

[Seth Forshee]

I'm not finding much in the logs. There's some i915 splat which could
possibly be related to the corruption, but nothing to explain the hard
lockup.

The current focal-proposed kernel (5.4.0-24) has some fixes for
races/deadlocks in i915, so it's worth trying that out to see if it
helps. You can use ppa:canonical-kernel-team/proposed to get that
kernel.

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

Title:
  System hard locks up intermittently

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My T450 main laptop is generally left on all day and night. I
  sometimes suspend it when moving around the house, but it's often left
  on all the time. Sometimes when I go to start work in the morning
  there's some corruption on screen and the laptop won't respond. I
  can't REISUB or ssh in.

  This has happened a few times since clean installing 20.04. Previously
  I was on an upgraded-to-20.04 install and don't recall it happening
  there. The other obvious difference is I'm now running ZFS which I
  wasn't before. :S

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  alan   8365 F pulseaudio
   /dev/snd/controlC2:  alan   8365 F pulseaudio
   /dev/snd/controlC1:  alan   8365 F pulseaudio
   /dev/snd/controlC0:  alan   8365 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  8 19:30:46 2020
  InstallationDate: Installed on 2020-03-01 (38 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
  MachineType: LENOVO 20BV001BUK
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  StagingDrivers: exfat
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET73WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BV001BUK
  dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

[Andrea Righi]

Hi Seth, sorry for my late response.

I did more tests this morning on my laptop tracing the callers of
__alloc_pages_nodemask() and I noticed that pretty much all the time it
is called by the i915 shrinker. So I tried to disable it and I have to
say that on my laptop (at least) the system is always very responsive
now even when the system is swapping out pages and I generate a lot of
I/O.

I've uploaded this test kernel here (5.4.0-24.28+lp1861359v1):
https://kernel.ubuntu.com/~arighi/LP-1861359/

Can you do one more test with it and verify if it does some improvements
also in your case?

Probably it's not yet a valid solution, but if it works it would tell us
that the problem is exactly there. Thanks!

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

Title:
  swap storms kills interactive use

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

Bug description:
  [Impact]

  High watermark boosting can cause large swap activity under certain
  memory intensive workloads, making the system very unresponsive
  (screen does not refresh, keyboard not responding, etc.).

  This large swap activity seems to be prevented disabling high
  watermark boosting.

  [Test case]

  Opening this web page in chrome seems to be a good reproducer of the
  problem:

  
https://platform.leolabs.space/visualizations/conjunction?type=conjunction=2004981040

  When this page is opened we can clearly see from 'top' (for example)
  that the used swap is going up very quickly.

  With the fix applied swap is not used at all and the system is always
  responsive.

  [Fix]

  Set vm.watermark_boost_factor to 0, disabling watermark boosting by
  default.

  [Regression potential]

  Regression potential is minimal, setting vm.watermark_boost_factor to
  0 by default restores the old kernel behavior before watermark
  boosting was introduced. In case of unexpected regressions we can
  always fix this in user-space via sysctl.

  [Original report]

  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
     Mixer name : 'Realtek ALC285'
     Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
     Controls  : 53
     Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
     Mixer name : 'USB Mixer'
     Components : 'USB17ef:306f'
     Controls  : 9
     Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: 

[Kernel-packages] [Bug 1870559] Re: Kernel NULL pointer dereference while receiving zfs snapshots

[Colin Ian King]

For reference, the splat was:

[ 2465.077373] BUG: kernel NULL pointer dereference, address: 
[ 2465.077397] #PF: supervisor read access in kernel mode
[ 2465.077403] #PF: error_code(0x) - not-present page
[ 2465.077409] PGD 0 P4D 0 
[ 2465.077415] Oops:  [#1] SMP NOPTI
[ 2465.077422] CPU: 0 PID: 23215 Comm: receive_writer Tainted: P   O
  5.4.0-21-generic #25-Ubuntu
[ 2465.077433] Hardware name: System manufacturer System Product 
Name/P5LD2-X/1333, BIOS 021412/23/2008
[ 2465.077619] RIP: 0010:abd_verify+0xa/0x40 [zfs]
[ 2465.077626] Code: ff 85 c0 74 12 48 c7 03 00 00 00 00 48 c7 43 08 00 00 00 
00 5b 5d c3 e8 04 ff ff ff eb e7 c3 90 55 48 89 e5 41 54 53 48 89 fb <8b> 3f e8 
0f ff ff ff 85 c0 75 22 44 8b 63 1c 48 8b 7b 20 4d 85 e4
[ 2465.077642] RSP: 0018:b28b51f6f998 EFLAGS: 00010282
[ 2465.077649] RAX: 4000 RBX:  RCX: 
[ 2465.077656] RDX: 4000 RSI: 4000 RDI: 
[ 2465.077662] RBP: b28b51f6f9a8 R08: 03da R09: 0045e54c
[ 2465.077669] R10: 36bf R11:  R12: 4000
[ 2465.077675] R13: 8ff6af5bd5f0 R14: 4000 R15: 
[ 2465.077683] FS:  () GS:8ff70c60() 
knlGS:
[ 2465.077691] CS:  0010 DS:  ES:  CR0: 80050033
[ 2465.077697] CR2:  CR3: 58e5 CR4: 06f0
[ 2465.077704] Call Trace:
[ 2465.077754]  abd_borrow_buf+0x19/0x60 [zfs]
[ 2465.077801]  abd_borrow_buf_copy+0x1a/0x50 [zfs]
[ 2465.077873]  zio_crypt_copy_dnode_bonus+0x30/0x130 [zfs]
[ 2465.077922]  arc_buf_untransform_in_place.isra.0+0x2b/0x40 [zfs]
[ 2465.077971]  arc_buf_fill+0x1f0/0x4a0 [zfs]
[ 2465.078021]  arc_untransform+0x22/0x90 [zfs]
[ 2465.078070]  dbuf_read_verify_dnode_crypt+0xed/0x160 [zfs]
[ 2465.078141]  ? atomic_cmpxchg+0x16/0x30 [zfs]
[ 2465.078191]  dbuf_read_impl+0x117/0x610 [zfs]
[ 2465.078240]  ? atomic64_add_return+0x12/0x30 [zfs]
[ 2465.078291]  dbuf_read+0xcb/0x5f0 [zfs]
[ 2465.078340]  ? dbuf_hold_impl+0x2f/0x40 [zfs]
[ 2465.078395]  dmu_tx_check_ioerr+0x70/0xd0 [zfs]
[ 2465.078450]  dmu_tx_hold_free_impl+0x12c/0x240 [zfs]
[ 2465.078507]  dmu_tx_hold_free+0x40/0x50 [zfs]
[ 2465.078559]  dmu_free_long_range_impl+0x124/0x350 [zfs]
[ 2465.078612]  dmu_free_long_range+0x74/0xc0 [zfs]
[ 2465.078665]  dmu_free_long_object+0x27/0xc0 [zfs]
[ 2465.078720]  receive_freeobjects.isra.0+0x7a/0x100 [zfs]
[ 2465.078777]  receive_process_record+0x89/0x1c0 [zfs]
[ 2465.078833]  receive_writer_thread+0x9a/0x150 [zfs]
[ 2465.078889]  ? receive_process_record+0x1c0/0x1c0 [zfs]
[ 2465.078910]  thread_generic_wrapper+0x83/0xa0 [spl]
[ 2465.078919]  kthread+0x104/0x140
[ 2465.078929]  ? clear_bit+0x20/0x20 [spl]
[ 2465.078934]  ? kthread_park+0x90/0x90
[ 2465.078941]  ret_from_fork+0x1f/0x40
[ 2465.078946] Modules linked in: nfnetlink xt_CHECKSUM xt_MASQUERADE 
xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat 
iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter 
essiv authenc dm_crypt zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) 
znvpair(PO) spl(O) zlua(PO) snd_ctxfi snd_pcm snd_timer snd soundcore 
input_leds 8021q garp mrp asus_atk0110 kvm_intel bridge stp llc mac_hid kvm 
serio_raw sch_fq_codel nfsd nfs_acl lockd grace auth_rpcgss hwmon_vid coretemp 
sunrpc ip_tables x_tables autofs4 btrfs xor zstd_compress hid_generic usbhid 
hid raid6_pq libcrc32c nouveau mxm_wmi wmi gpio_ich video i2c_algo_bit ttm 
drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 i2c_i801 
pata_acpi lpc_ich drm realtek
[ 2465.079029] CR2: 
[ 2465.079035] ---[ end trace 7a059aed43188006 ]---
[ 2465.079084] RIP: 0010:abd_verify+0xa/0x40 [zfs]
[ 2465.079090] Code: ff 85 c0 74 12 48 c7 03 00 00 00 00 48 c7 43 08 00 00 00 
00 5b 5d c3 e8 04 ff ff ff eb e7 c3 90 55 48 89 e5 41 54 53 48 89 fb <8b> 3f e8 
0f ff ff ff 85 c0 75 22 44 8b 63 1c 48 8b 7b 20 4d 85 e4
[ 2465.079104] RSP: 0018:b28b51f6f998 EFLAGS: 00010282
[ 2465.079110] RAX: 4000 RBX:  RCX: 
[ 2465.079116] RDX: 4000 RSI: 4000 RDI: 
[ 2465.079411] RBP: b28b51f6f9a8 R08: 03da R09: 0045e54c
[ 2465.079702] R10: 36bf R11:  R12: 4000
[ 2465.079993] R13: 8ff6af5bd5f0 R14: 4000 R15: 
[ 2465.080279] FS:  () GS:8ff70c60() 
knlGS:
[ 2465.080571] CS:  0010 DS:  ES:  CR0: 80050033
[ 2465.080883] CR2:  CR3: 58e5 CR4: 06f0

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** 

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

[bugproxy]

--- Comment From mihaj...@de.ibm.com 2020-04-15 11:14 EDT---
If I read the comments correctly, virt-install --location isn't supported 
anymore for the 20.04 default installer.
It would work however for the d-i installer, if virt-install would employ 
current/legacy-images as suffix to the URL in the case of distro being focal or 
higher, potentially with a warning that this method is deprecated.
No good idea to break an existing, well-working solution.
This creates additional churn in our test team, and I'd be surprised, if we're 
the only ones affected.

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

Title:
  [Ubuntu 20.04] virt-install fails to detect path after images folder
  name has changed

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in virt-manager package in Ubuntu:
  New

Bug description:
  Installer version: Latest
  https://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x

  Description/Reproduction:
  Start virt-install with the following options:

  virt-install \
  --name ubuntu20-guest1 \
  --memory 4096 \
  --vcpus 4 \
  --disk "size=4" \
  --location 
http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x \
  --network "network=default" 

  Error:
  ERRORError validating install location: Could not find an installable 
distribution at 
'http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x'

  The location must be the root directory of an install tree.
  See virt-install man page for various distro examples.

  
  Looking at previous releases I would guess it expects an "images" directory 
instead of the new "classic-images" directory. I'm aware of the workaround to 
specify kernel/initramfs directly but that shouldn't be a solution.

  == Comment: #2 - Andre Wild1  - 2020-04-15 03:51:21 ==
  (In reply to comment #0)
  > Installer version: Latest
  > https://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x
  > 

  Sorry I've copied the wrong link. This is the link I've used successfully in 
the past:
  http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x

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

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

[Kernel-packages] [Bug 1865471] Re: USB 3.1 Gen 1 not work after using suspend

[MARTIN]

** Description changed:

  Good morning.
  
  I use "suspend"(settings -> energy -> When the shutdown...) on 18.04.
  
- Each wake up, motherboard (back panel) USB ports 3.1 Gen 1 don't work.
+ Each wake up, USB ports 3.1 Gen 1 don't work (only those on the
+ motherboard on the back of the case).
  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  christophe   1648 F pulseaudio
   /dev/snd/controlC2:  christophe   1648 F pulseaudio
   /dev/snd/controlC0:  christophe   1648 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-18 (14 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IwConfig:
   lono wireless extensions.
  
   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-A320M-S2H (rev. 1.x)
  
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=9757d7ed-95dd-47d2-a3a7-80be35d05879 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.15
  RfKill:
  
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/28/2019:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  ---

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

Title:
  USB 3.1 Gen 1 not work after using suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Good morning.

  I use "suspend"(settings -> energy -> When the shutdown...) on 18.04.

  Each wake up, USB ports 3.1 Gen 1 don't work (only those on the
  motherboard on the back of the case).

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  christophe   1648 F pulseaudio
   /dev/snd/controlC2:  christophe   1648 F pulseaudio
   /dev/snd/controlC0:  christophe   1648 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-18 (14 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IwConfig:
   lono wireless extensions.

   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-A320M-S2H (rev. 1.x)

  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=9757d7ed-95dd-47d2-a3a7-80be35d05879 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.15
  RfKill:

  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 

[Kernel-packages] [Bug 1846305] Re: generic/397 from ubuntu_xfstests_ext4 failed on D

[Po-Hsu Lin]

Spotted on node bavor with 5.4.0-24.28

** Tags added: focal

** Tags added: sru-20200406

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

Title:
  generic/397 from ubuntu_xfstests_ext4 failed on D

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Issue found on node amd64 node "gonzo"

   generic/397- output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/397.out.bad)
   --- tests/generic/397.out  2019-10-01 07:38:07.080386390 +
   +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/397.out.bad
   2019-10-01 13:01:22.850581563 +
   @@ -1,4 +1,5 @@
QA output created by 397
   +keyctl_session_to_parent: Operation not permitted
stat: cannot stat 'SCRATCH_MNT/edir/empty': No such file or directory 
stat: cannot stat 'SCRATCH_MNT/edir/symlink': No such file or directory
8
   ...
   (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/tests/generic/397.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/397.out.bad'
  to see the entire diff) 

  
  $ cat 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/397.out.bad
  QA output created by 397
  keyctl_session_to_parent: Operation not permitted
  stat: cannot stat 'SCRATCH_MNT/edir/empty': No such file or directory
  stat: cannot stat 'SCRATCH_MNT/edir/symlink': No such file or directory
  8
  1
  Required key not available
  SCRATCH_MNT/edir/newfile: Required key not available
  SCRATCH_MNT/edir/0123456789abcdef: Required key not available
  mkdir: cannot create directory 'SCRATCH_MNT/edir/newdir': Required key not 
available
  mkdir: cannot create directory 'SCRATCH_MNT/edir/0123456789abcdef': Required 
key not available
  ln: failed to create symbolic link 'SCRATCH_MNT/edir/newlink': Required key 
not available
  ln: failed to create symbolic link 'SCRATCH_MNT/edir/0123456789abcdef': 
Required key not available
  stat: cannot stat 'SCRATCH_MNT/edir': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-29-generic 5.0.0-29.31
  ProcVersionSignature: User Name 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct  1 11:07 seq
   crw-rw 1 root audio 116, 33 Oct  1 11:07 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [68184.314209] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [68184.315939] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed Oct  2 07:32:58 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R415
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=3e0e190e-d425-4d00-a9a9-deb0c452399b ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.178.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.3
  dmi.board.name: 08WNM9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.3:bd04/26/2012:svnDellInc.:pnPowerEdgeR415:pvr:rvnDellInc.:rn08WNM9:rvrA02:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R415
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1846305/+subscriptions

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

[Kernel-packages] [Bug 1872961] Re: Error loading the kernel module for the Realtek RTL8812AU Wireless USB adapter

[Mau]

I also have this problem with the latest upstream mainline kernel
(5.6.4-050604-generic)

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

Title:
  Error loading the kernel module for the Realtek RTL8812AU Wireless USB
  adapter

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've installed the package "rtl8812au-dkms". 
  Then plug the "Alfa AWUS036ACH" (Realtek RTL8812AU) WiFi 802.11ac AC1200 
Long-Range USB adapter (https://www.alfa.com.tw/products_detail/1.htm) and the 
module cannot load. It fails an dumps to the kernel.log file this information:
  Apr 15 12:57:18 capicuapl-ng kernel: [20528.015294] usb 1-1: new high-speed 
USB device number 10 using xhci_hcd
  Apr 15 12:57:18 capicuapl-ng kernel: [20528.035845] usb 1-1: New USB device 
found, idVendor=0bda, idProduct=8812, bcdDevice= 0.00
  Apr 15 12:57:18 capicuapl-ng kernel: [20528.035851] usb 1-1: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
  Apr 15 12:57:18 capicuapl-ng kernel: [20528.035854] usb 1-1: Product: 802.11n 
NIC
  Apr 15 12:57:18 capicuapl-ng kernel: [20528.035857] usb 1-1: Manufacturer: 
Realtek
  Apr 15 12:57:18 capicuapl-ng kernel: [20528.035860] usb 1-1: SerialNumber: 
123456
  Apr 15 12:57:18 capicuapl-ng kernel: [20528.038077] [ cut here 
]
  Apr 15 12:57:18 capicuapl-ng kernel: [20528.038151] WARNING: CPU: 7 PID: 
45138 at net/wireless/core.c:867 wiphy_register+0x6d1/0x930 [cfg80211]
  Apr 15 12:57:18 capicuapl-ng kernel: [20528.038154] Modules linked in: btrfs 
xor zstd_compress raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs 
8812au(OE) ppp_mppe ppp_async nf_conntrack_pptp nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 libcrc32c ccm rfcomm cmac algif_hash algif_skcipher af_alg bnep 
nls_iso8859_1 snd_hda_codec_hdmi mei_hdcp snd_sof_pci snd_sof_intel_hda_common 
snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc 
intel_rapl_msr snd_sof snd_sof_xtensa_dsp snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress 
snd_hda_codec_realtek ac97_bus snd_hda_codec_generic snd_pcm_dmaengine 
ledtrig_audio snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core snd_hwdep 
snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi x86_pkg_temp_thermal 
intel_powerclamp joydev iwlmvm coretemp kvm_intel uvcvideo mac80211 snd_seq 
videobuf2_vmalloc kvm snd_seq_device videobuf2_memops libarc4 snd_timer 
videobuf2_v4l2 videobuf2_common intel_cstate btusb intel_rapl_perf btrtl snd 
videodev btbcm
  Apr 15 12:57:18 capicuapl-ng kernel: [20528.038248]  asus_nb_wmi iwlwifi 
btintel rtsx_pci_ms asus_wmi input_leds sparse_keymap wmi_bmof soundcore mc 
bluetooth serio_raw mxm_wmi 8250_dw hid_multitouch memstick cfg80211 mei_me 
ecdh_generic ecc processor_thermal_device intel_rapl_common mei 
intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone 
mac_hid acpi_tad int3400_thermal acpi_pad asus_wireless acpi_thermal_rel 
nvidia_uvm(OE) sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables 
autofs4 dm_crypt nvidia_drm(POE) usbhid nvidia_modeset(POE) hid_generic 
spi_pxa2xx_platform dw_dmac dw_dmac_core nvidia(POE) crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel i915 aesni_intel crypto_simd cryptd 
i2c_algo_bit rtsx_pci_sdmmc nvme glue_helper drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops nvme_core i2c_i801 drm rtsx_pci 
intel_lpss_pci ipmi_devintf intel_lpss ipmi_msghandler idma64 virt_dma i2c_hid 
hid wmi video pinctrl_cannonlake pinctrl_intel
  Apr 15 12:57:18 capicuapl-ng kernel: [20528.038330] CPU: 7 PID: 45138 Comm: 
kworker/7:0 Tainted: PW  OE 5.4.0-21-generic #25-Ubuntu
  Apr 15 12:57:18 capicuapl-ng kernel: [20528.038333] Hardware name: ASUSTeK 
COMPUTER INC. ZenBook 13 UX331FN_UX331FN/UX331FN, BIOS UX331FN.305 10/16/2019
  Apr 15 12:57:18 capicuapl-ng kernel: [20528.038343] Workqueue: usb_hub_wq 
hub_event
  Apr 15 12:57:18 capicuapl-ng kernel: [20528.038380] RIP: 
0010:wiphy_register+0x6d1/0x930 [cfg80211]
  Apr 15 12:57:18 capicuapl-ng kernel: [20528.038385] Code: ff e9 78 fa ff ff 
0f 0b b8 ea ff ff ff e9 6c fa ff ff 0f 0b b8 ea ff ff ff e9 60 fa ff ff 0f 0b 
b8 ea ff ff ff e9 54 fa ff ff <0f> 0b b8 ea ff ff ff e9 48 fa ff ff 0f 0b b8 ea 
ff ff ff e9 3c fa
  Apr 15 12:57:18 capicuapl-ng kernel: [20528.038388] RSP: 
0018:b39c0746f730 EFLAGS: 00010246
  Apr 15 12:57:18 capicuapl-ng kernel: [20528.038391] RAX: c2642690 
RBX: 9a9df58c4b00 RCX: c2642680
  Apr 15 12:57:18 capicuapl-ng kernel: [20528.038393] RDX: c2642720 
RSI: 0001 RDI: 001e
  Apr 15 12:57:18 capicuapl-ng kernel: [20528.038395] RBP: b39c0746f7a8 
R08: 0004 R09: 0003
  Apr 15 12:57:18 capicuapl-ng kernel: [20528.038397] R10:  
R11: b39d00548fc5 R12: 9a9df58c4b00
  Apr 15 12:57:18 capicuapl-ng kernel: 

[Kernel-packages] [Bug 1872941] Re: [Ubuntu 20.04] virt-install fails to detect path after images folder name has changed

[Dimitri John Ledkov]

The URL is changed intentionally, to notify all users that these images
are deprecated and will not be updated after 20.04.0 GA, and will no
longer be published in the future.

You should not be using virt-install, and simply boot the s390x cloud-
image in-place, with suitable cloud-config drive attached. This way, you
simply directly boot into installed ubuntu server, which executes cloud-
init and reconfigures the instance on first boot as desired without
performing installation & reboot.

If you want to test the installer, please use the new installer
interactively or with auto-install config provided as a cloud-config
drive as mentioned on the download page itself
http://ports.ubuntu.com/dists/focal/main/installer-s390x/current/legacy-
images/

We felt that we had to rename and change URLs, to notify all automated
systems that these images are going away.

This communication / notification mechanism seems to be working as
intended. Because it broke your current setup.

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

Title:
  [Ubuntu 20.04] virt-install fails to detect path after images folder
  name has changed

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in virt-manager package in Ubuntu:
  New

Bug description:
  Installer version: Latest
  https://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x

  Description/Reproduction:
  Start virt-install with the following options:

  virt-install \
  --name ubuntu20-guest1 \
  --memory 4096 \
  --vcpus 4 \
  --disk "size=4" \
  --location 
http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x \
  --network "network=default" 

  Error:
  ERRORError validating install location: Could not find an installable 
distribution at 
'http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x'

  The location must be the root directory of an install tree.
  See virt-install man page for various distro examples.

  
  Looking at previous releases I would guess it expects an "images" directory 
instead of the new "classic-images" directory. I'm aware of the workaround to 
specify kernel/initramfs directly but that shouldn't be a solution.

  == Comment: #2 - Andre Wild1  - 2020-04-15 03:51:21 ==
  (In reply to comment #0)
  > Installer version: Latest
  > https://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x
  > 

  Sorry I've copied the wrong link. This is the link I've used successfully in 
the past:
  http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x

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

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

[Kernel-packages] [Bug 1872941] Re: [Ubuntu 20.04] virt-install fails to detect path after images folder name has changed

[Frank Heimes]

First of all, both examples from comment #3 work (subiquity also
installs that way).

I guess it's obvious that the '--location' doesn't work with the directory tree 
anymore due to the change in the URL from
http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x/current/images/
to:
http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x/current/legacy-images/
(notice that  
http://ports.ubuntu.com/ubuntu-ports/dists/eoan/main/installer-s390x still 
works).
As far as I can tell the URL change was done by intention and to indicate that 
the default installer for 20.04 is no longer d-i, but subiquity.

The '--cdrom' is a valid option for many cases, but unfortunately not
for all, since it doesn't allow the '-extra-args' argument - '-extra-
args' only works in combination with '--location', not with '--cdrom'.

I currently see two options, one is renaming the URL back and the second
option is to directly specify kernel and initrd, like:

ubuntu@s1lp11:~$ virt-install --name ubuntu20-guest1 --memory 4096
--vcpus 4 --disk "size=4" --install kernel=http://ports.ubuntu.com
/ubuntu-ports/dists/focal/main/installer-s390x/current/legacy-
images/generic/kernel.ubuntu,initrd=http://ports.ubuntu.com/ubuntu-
ports/dists/focal/main/installer-s390x/current/legacy-
images/generic/initrd.ubuntu --network "network=default"

As far as I can tell netboot images/files at 'ports.ubuntu.com' are all d-i 
only.
For subiquity one needs to grab kernel and initrd for potential netbooting from 
the focal-live-server-s390x.iso or the iso itself.

Btw. preseed is the non-interactive installation method based on d-i.
With the new subiquity installer the preseed successor is 'autoinstallation' - 
for more details let me refer to:

Automated Server Installs for 20.04
https://wiki.ubuntu.com/FoundationsTeam/AutomatedServerInstalls

Automated Server Installs Config File Reference
https://wiki.ubuntu.com/FoundationsTeam/AutomatedServerInstalls/ConfigReference

JSON Schema for autoinstall config
https://wiki.ubuntu.com/FoundationsTeam/AutomatedServerInstalls/ConfigSchema

Autoinstall Quick Start
https://wiki.ubuntu.com/FoundationsTeam/AutomatedServerInstalls/QuickStart

Autoinstall Quick Start for s390x
https://wiki.ubuntu.com/FoundationsTeam/AutomatedServerInstalls/QuickStart/s390x

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

Title:
  [Ubuntu 20.04] virt-install fails to detect path after images folder
  name has changed

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in virt-manager package in Ubuntu:
  New

Bug description:
  Installer version: Latest
  https://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x

  Description/Reproduction:
  Start virt-install with the following options:

  virt-install \
  --name ubuntu20-guest1 \
  --memory 4096 \
  --vcpus 4 \
  --disk "size=4" \
  --location 
http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x \
  --network "network=default" 

  Error:
  ERRORError validating install location: Could not find an installable 
distribution at 
'http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x'

  The location must be the root directory of an install tree.
  See virt-install man page for various distro examples.

  
  Looking at previous releases I would guess it expects an "images" directory 
instead of the new "classic-images" directory. I'm aware of the workaround to 
specify kernel/initramfs directly but that shouldn't be a solution.

  == Comment: #2 - Andre Wild1  - 2020-04-15 03:51:21 ==
  (In reply to comment #0)
  > Installer version: Latest
  > https://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x
  > 

  Sorry I've copied the wrong link. This is the link I've used successfully in 
the past:
  http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x

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

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

[Kernel-packages] [Bug 1872941] Re: [Ubuntu 20.04] virt-install fails to detect path after images folder name has changed

[Christian Ehrhardt ]

Agreed @cborntra, if that is your use case then those two ways are not 
equivalent.
Then for now I only know of the "workaround to specify kernel/initramfs 
directly" that you are aware of as well.

Let's see what feedback Andrew gets when asking to change the path back.

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

Title:
  [Ubuntu 20.04] virt-install fails to detect path after images folder
  name has changed

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in virt-manager package in Ubuntu:
  New

Bug description:
  Installer version: Latest
  https://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x

  Description/Reproduction:
  Start virt-install with the following options:

  virt-install \
  --name ubuntu20-guest1 \
  --memory 4096 \
  --vcpus 4 \
  --disk "size=4" \
  --location 
http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x \
  --network "network=default" 

  Error:
  ERRORError validating install location: Could not find an installable 
distribution at 
'http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x'

  The location must be the root directory of an install tree.
  See virt-install man page for various distro examples.

  
  Looking at previous releases I would guess it expects an "images" directory 
instead of the new "classic-images" directory. I'm aware of the workaround to 
specify kernel/initramfs directly but that shouldn't be a solution.

  == Comment: #2 - Andre Wild1  - 2020-04-15 03:51:21 ==
  (In reply to comment #0)
  > Installer version: Latest
  > https://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x
  > 

  Sorry I've copied the wrong link. This is the link I've used successfully in 
the past:
  http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x

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

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

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

[bugproxy]

--- Comment From andre.wi...@ibm.com 2020-04-15 09:50 EDT---
Unfortunately this won't work with our preseed files.

ERRORKernel arguments are only supported with location or kernel
installs.

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

Title:
  [Ubuntu 20.04] virt-install fails to detect path after images folder
  name has changed

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in virt-manager package in Ubuntu:
  New

Bug description:
  Installer version: Latest
  https://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x

  Description/Reproduction:
  Start virt-install with the following options:

  virt-install \
  --name ubuntu20-guest1 \
  --memory 4096 \
  --vcpus 4 \
  --disk "size=4" \
  --location 
http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x \
  --network "network=default" 

  Error:
  ERRORError validating install location: Could not find an installable 
distribution at 
'http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x'

  The location must be the root directory of an install tree.
  See virt-install man page for various distro examples.

  
  Looking at previous releases I would guess it expects an "images" directory 
instead of the new "classic-images" directory. I'm aware of the workaround to 
specify kernel/initramfs directly but that shouldn't be a solution.

  == Comment: #2 - Andre Wild1  - 2020-04-15 03:51:21 ==
  (In reply to comment #0)
  > Installer version: Latest
  > https://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x
  > 

  Sorry I've copied the wrong link. This is the link I've used successfully in 
the past:
  http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x

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

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

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

[bugproxy]

--- Comment From cborn...@de.ibm.com 2020-04-15 09:32 EDT---
The ISO is not equivalent to the install file tree. virt-install can change 
things like kernel parameters on the fly for a file tree. This is used for 
kickstart and pre-seed when necessary. virt-install is not able to do the same 
for iso files.

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

Title:
  [Ubuntu 20.04] virt-install fails to detect path after images folder
  name has changed

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in virt-manager package in Ubuntu:
  New

Bug description:
  Installer version: Latest
  https://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x

  Description/Reproduction:
  Start virt-install with the following options:

  virt-install \
  --name ubuntu20-guest1 \
  --memory 4096 \
  --vcpus 4 \
  --disk "size=4" \
  --location 
http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x \
  --network "network=default" 

  Error:
  ERRORError validating install location: Could not find an installable 
distribution at 
'http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x'

  The location must be the root directory of an install tree.
  See virt-install man page for various distro examples.

  
  Looking at previous releases I would guess it expects an "images" directory 
instead of the new "classic-images" directory. I'm aware of the workaround to 
specify kernel/initramfs directly but that shouldn't be a solution.

  == Comment: #2 - Andre Wild1  - 2020-04-15 03:51:21 ==
  (In reply to comment #0)
  > Installer version: Latest
  > https://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x
  > 

  Sorry I've copied the wrong link. This is the link I've used successfully in 
the past:
  http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x

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

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

[Kernel-packages] [Bug 1872984] Re: RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

[Matthew M]

** Summary changed:

- RTL8822BE network driver now crashes on boot in Focal Fossa 20.04 - 
5.4.0-21-generic and mainline 5.7.0-050700rc1-generic
+ RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 
5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

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

Title:
  RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04
  - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  RTL8822BE crashes after rtw_pci starts on boot after kernel update to
  5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is
  still present on latest mainline kernel version
  5.7.0-050700rc1-generic .

  [   10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0
  [   10.714544] [ cut here ]
  [   10.714545] failed to read DBI register, addr=0x0719
  [   10.714577] WARNING: CPU: 0 PID: 939 at 
drivers/net/wireless/realtek/rtw88/pci.c:1156 
rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714577] Modules linked in: (see attached dmesg)
  [   10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 
5.7.0-050700rc1-generic #202004122032
  [   10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 
01/23/2018
  [   10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 
31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 
fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00
  [   10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282
  [   10.714618] RAX:  RBX:  RCX: 
0007
  [   10.714619] RDX: 0007 RSI: 0092 RDI: 
933cc9e19c80
  [   10.714619] RBP: b466007e7898 R08: 03d2 R09: 
0004
  [   10.714620] R10:  R11: 0001 R12: 
933cbdf31ea0
  [   10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: 

  [   10.714622] FS:  7fbcedc6efc0() GS:933cc9e0() 
knlGS:
  [   10.714622] CS:  0010 DS:  ES:  CR0: 80050033
  [   10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 
003606f0
  [   10.714623] Call Trace:
  [   10.714627]  rtw_pci_link_ps+0x4e/0x90 [rtwpci]
  [   10.714630]  ? _raw_spin_unlock_bh+0x1e/0x20
  [   10.714637]  rtw_leave_ips+0x1f/0x80 [rtw88]
  [   10.714640]  rtw_ops_config+0xa3/0xe0 [rtw88]
  [   10.714658]  ieee80211_hw_config+0x95/0x390 [mac80211]
  [   10.714669]  ieee80211_recalc_idle+0x27/0x30 [mac80211]
  [   10.714679]  __ieee80211_start_scan+0x334/0x750 [mac80211]
  [   10.714688]  ieee80211_request_scan+0x30/0x50 [mac80211]
  [   10.714699]  ieee80211_scan+0x5c/0xa0 [mac80211]
  [   10.714719]  nl80211_trigger_scan+0x59a/0x6c0 [cfg80211]
  [   10.714722]  genl_rcv_msg+0x1a8/0x470
  [   10.714724]  ? ep_poll_callback+0x2a0/0x2c0
  [   10.714725]  ? genl_family_rcv_msg_attrs_parse+0x100/0x100
  [   10.714726]  netlink_rcv_skb+0x50/0x120
  [   10.714728]  genl_rcv+0x29/0x40
  [   10.714729]  netlink_unicast+0x1a8/0x250
  [   10.714730]  netlink_sendmsg+0x233/0x460
  [   10.714739]  ? _copy_from_user+0x31/0x60
  [   10.714750]  sock_sendmsg+0x65/0x70
  [   10.714751]  sys_sendmsg+0x212/0x280
  [   10.714752]  ? copy_msghdr_from_user+0x5c/0x90
  [   10.714755]  ? __check_object_size+0x4d/0x150
  [   10.714756]  ___sys_sendmsg+0x81/0xc0
  [   10.714757]  ? __check_object_size+0x4d/0x150
  [   10.714759]  ? unix_ioctl+0x99/0x180
  [   10.714760]  ? sock_getsockopt+0x198/0xc04
  [   10.714761]  ? sock_do_ioctl+0x47/0x140
  [   10.714763]  ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0
  [   10.714765]  ? _cond_resched+0x19/0x30
  [   10.714767]  ? aa_sk_perm+0x43/0x1b0
  [   10.714768]  __sys_sendmsg+0x5c/0xa0
  [   10.714770]  __x64_sys_sendmsg+0x1f/0x30
  [   10.714772]  do_syscall_64+0x57/0x1b0
  [   10.714773]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   10.714774] RIP: 0033:0x7fbcedffb5b7
  [   10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 
f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10
  [   10.714776] RSP: 002b:7fff88e22288 EFLAGS: 0246 ORIG_RAX: 
002e
  [   10.714777] RAX: ffda RBX: 5632787355d0 RCX: 
7fbcedffb5b7
  [   10.714777] RDX:  RSI: 7fff88e222c0 RDI: 
0006
  [   10.714778] RBP: 563278761380 R08: 0004 R09: 
563278761380
  [   10.714778] R10: 7fff88e22394 R11: 0246 R12: 
5632787354e0
  [   10.714779] R13: 7fff88e222c0 R14: 7fff88e22394 R15: 
563278766710
  [   10.714780] ---[ end 

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04
  - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  RTL8822BE crashes after rtw_pci starts on boot after kernel update to
  5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is
  still present on latest mainline kernel version
  5.7.0-050700rc1-generic .

  [   10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0
  [   10.714544] [ cut here ]
  [   10.714545] failed to read DBI register, addr=0x0719
  [   10.714577] WARNING: CPU: 0 PID: 939 at 
drivers/net/wireless/realtek/rtw88/pci.c:1156 
rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714577] Modules linked in: (see attached dmesg)
  [   10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 
5.7.0-050700rc1-generic #202004122032
  [   10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 
01/23/2018
  [   10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 
31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 
fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00
  [   10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282
  [   10.714618] RAX:  RBX:  RCX: 
0007
  [   10.714619] RDX: 0007 RSI: 0092 RDI: 
933cc9e19c80
  [   10.714619] RBP: b466007e7898 R08: 03d2 R09: 
0004
  [   10.714620] R10:  R11: 0001 R12: 
933cbdf31ea0
  [   10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: 

  [   10.714622] FS:  7fbcedc6efc0() GS:933cc9e0() 
knlGS:
  [   10.714622] CS:  0010 DS:  ES:  CR0: 80050033
  [   10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 
003606f0
  [   10.714623] Call Trace:
  [   10.714627]  rtw_pci_link_ps+0x4e/0x90 [rtwpci]
  [   10.714630]  ? _raw_spin_unlock_bh+0x1e/0x20
  [   10.714637]  rtw_leave_ips+0x1f/0x80 [rtw88]
  [   10.714640]  rtw_ops_config+0xa3/0xe0 [rtw88]
  [   10.714658]  ieee80211_hw_config+0x95/0x390 [mac80211]
  [   10.714669]  ieee80211_recalc_idle+0x27/0x30 [mac80211]
  [   10.714679]  __ieee80211_start_scan+0x334/0x750 [mac80211]
  [   10.714688]  ieee80211_request_scan+0x30/0x50 [mac80211]
  [   10.714699]  ieee80211_scan+0x5c/0xa0 [mac80211]
  [   10.714719]  nl80211_trigger_scan+0x59a/0x6c0 [cfg80211]
  [   10.714722]  genl_rcv_msg+0x1a8/0x470
  [   10.714724]  ? ep_poll_callback+0x2a0/0x2c0
  [   10.714725]  ? genl_family_rcv_msg_attrs_parse+0x100/0x100
  [   10.714726]  netlink_rcv_skb+0x50/0x120
  [   10.714728]  genl_rcv+0x29/0x40
  [   10.714729]  netlink_unicast+0x1a8/0x250
  [   10.714730]  netlink_sendmsg+0x233/0x460
  [   10.714739]  ? _copy_from_user+0x31/0x60
  [   10.714750]  sock_sendmsg+0x65/0x70
  [   10.714751]  sys_sendmsg+0x212/0x280
  [   10.714752]  ? copy_msghdr_from_user+0x5c/0x90
  [   10.714755]  ? __check_object_size+0x4d/0x150
  [   10.714756]  ___sys_sendmsg+0x81/0xc0
  [   10.714757]  ? __check_object_size+0x4d/0x150
  [   10.714759]  ? unix_ioctl+0x99/0x180
  [   10.714760]  ? sock_getsockopt+0x198/0xc04
  [   10.714761]  ? sock_do_ioctl+0x47/0x140
  [   10.714763]  ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0
  [   10.714765]  ? _cond_resched+0x19/0x30
  [   10.714767]  ? aa_sk_perm+0x43/0x1b0
  [   10.714768]  __sys_sendmsg+0x5c/0xa0
  [   10.714770]  __x64_sys_sendmsg+0x1f/0x30
  [   10.714772]  do_syscall_64+0x57/0x1b0
  [   10.714773]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   10.714774] RIP: 0033:0x7fbcedffb5b7
  [   10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 
f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10
  [   10.714776] RSP: 002b:7fff88e22288 EFLAGS: 0246 ORIG_RAX: 
002e
  [   10.714777] RAX: ffda RBX: 5632787355d0 RCX: 
7fbcedffb5b7
  [   10.714777] RDX:  RSI: 7fff88e222c0 RDI: 
0006
  [   10.714778] RBP: 563278761380 R08: 0004 R09: 
563278761380
  [   10.714778] R10: 7fff88e22394 R11: 0246 R12: 
5632787354e0
  [   10.714779] R13: 7fff88e222c0 R14: 7fff88e22394 R15: 
563278766710
  [   10.714780] ---[ end trace f00c16109236af6f ]---
  [   10.714782] rtw_pci :3a:00.0: failed to read ASPM, ret=-5

  
  Device is unable to scan for networks and error occurs when attempting to 
turn 

[Kernel-packages] [Bug 1872984] Re: RTL8822BE network driver now crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

[Matthew M]

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

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

Title:
  RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04
  - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  RTL8822BE crashes after rtw_pci starts on boot after kernel update to
  5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is
  still present on latest mainline kernel version
  5.7.0-050700rc1-generic .

  [   10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0
  [   10.714544] [ cut here ]
  [   10.714545] failed to read DBI register, addr=0x0719
  [   10.714577] WARNING: CPU: 0 PID: 939 at 
drivers/net/wireless/realtek/rtw88/pci.c:1156 
rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714577] Modules linked in: (see attached dmesg)
  [   10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 
5.7.0-050700rc1-generic #202004122032
  [   10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 
01/23/2018
  [   10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 
31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 
fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00
  [   10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282
  [   10.714618] RAX:  RBX:  RCX: 
0007
  [   10.714619] RDX: 0007 RSI: 0092 RDI: 
933cc9e19c80
  [   10.714619] RBP: b466007e7898 R08: 03d2 R09: 
0004
  [   10.714620] R10:  R11: 0001 R12: 
933cbdf31ea0
  [   10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: 

  [   10.714622] FS:  7fbcedc6efc0() GS:933cc9e0() 
knlGS:
  [   10.714622] CS:  0010 DS:  ES:  CR0: 80050033
  [   10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 
003606f0
  [   10.714623] Call Trace:
  [   10.714627]  rtw_pci_link_ps+0x4e/0x90 [rtwpci]
  [   10.714630]  ? _raw_spin_unlock_bh+0x1e/0x20
  [   10.714637]  rtw_leave_ips+0x1f/0x80 [rtw88]
  [   10.714640]  rtw_ops_config+0xa3/0xe0 [rtw88]
  [   10.714658]  ieee80211_hw_config+0x95/0x390 [mac80211]
  [   10.714669]  ieee80211_recalc_idle+0x27/0x30 [mac80211]
  [   10.714679]  __ieee80211_start_scan+0x334/0x750 [mac80211]
  [   10.714688]  ieee80211_request_scan+0x30/0x50 [mac80211]
  [   10.714699]  ieee80211_scan+0x5c/0xa0 [mac80211]
  [   10.714719]  nl80211_trigger_scan+0x59a/0x6c0 [cfg80211]
  [   10.714722]  genl_rcv_msg+0x1a8/0x470
  [   10.714724]  ? ep_poll_callback+0x2a0/0x2c0
  [   10.714725]  ? genl_family_rcv_msg_attrs_parse+0x100/0x100
  [   10.714726]  netlink_rcv_skb+0x50/0x120
  [   10.714728]  genl_rcv+0x29/0x40
  [   10.714729]  netlink_unicast+0x1a8/0x250
  [   10.714730]  netlink_sendmsg+0x233/0x460
  [   10.714739]  ? _copy_from_user+0x31/0x60
  [   10.714750]  sock_sendmsg+0x65/0x70
  [   10.714751]  sys_sendmsg+0x212/0x280
  [   10.714752]  ? copy_msghdr_from_user+0x5c/0x90
  [   10.714755]  ? __check_object_size+0x4d/0x150
  [   10.714756]  ___sys_sendmsg+0x81/0xc0
  [   10.714757]  ? __check_object_size+0x4d/0x150
  [   10.714759]  ? unix_ioctl+0x99/0x180
  [   10.714760]  ? sock_getsockopt+0x198/0xc04
  [   10.714761]  ? sock_do_ioctl+0x47/0x140
  [   10.714763]  ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0
  [   10.714765]  ? _cond_resched+0x19/0x30
  [   10.714767]  ? aa_sk_perm+0x43/0x1b0
  [   10.714768]  __sys_sendmsg+0x5c/0xa0
  [   10.714770]  __x64_sys_sendmsg+0x1f/0x30
  [   10.714772]  do_syscall_64+0x57/0x1b0
  [   10.714773]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   10.714774] RIP: 0033:0x7fbcedffb5b7
  [   10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 
f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10
  [   10.714776] RSP: 002b:7fff88e22288 EFLAGS: 0246 ORIG_RAX: 
002e
  [   10.714777] RAX: ffda RBX: 5632787355d0 RCX: 
7fbcedffb5b7
  [   10.714777] RDX:  RSI: 7fff88e222c0 RDI: 
0006
  [   10.714778] RBP: 563278761380 R08: 0004 R09: 
563278761380
  [   10.714778] R10: 7fff88e22394 R11: 0246 R12: 
5632787354e0
  [   10.714779] R13: 7fff88e222c0 R14: 7fff88e22394 R15: 
563278766710
  [   10.714780] ---[ end trace f00c16109236af6f ]---
  [   10.714782] rtw_pci :3a:00.0: failed to read ASPM, ret=-5

  
  Device is unable to scan for networks and error occurs when attempting to 
turn on/off wifi in settings:

  [  

[Kernel-packages] [Bug 1872984] Re: RTL8822BE network driver now crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

[Matthew M]

** Attachment added: "dmesg-5.4.0-21.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872984/+attachment/5354565/+files/dmesg-5.4.0-21.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/1872984

Title:
  RTL8822BE network driver now crashes on boot in Focal Fossa 20.04 -
  5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

Status in linux package in Ubuntu:
  New

Bug description:
  RTL8822BE crashes after rtw_pci starts on boot after kernel update to
  5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is
  still present on latest mainline kernel version
  5.7.0-050700rc1-generic .

  [   10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0
  [   10.714544] [ cut here ]
  [   10.714545] failed to read DBI register, addr=0x0719
  [   10.714577] WARNING: CPU: 0 PID: 939 at 
drivers/net/wireless/realtek/rtw88/pci.c:1156 
rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714577] Modules linked in: (see attached dmesg)
  [   10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 
5.7.0-050700rc1-generic #202004122032
  [   10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 
01/23/2018
  [   10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 
31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 
fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00
  [   10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282
  [   10.714618] RAX:  RBX:  RCX: 
0007
  [   10.714619] RDX: 0007 RSI: 0092 RDI: 
933cc9e19c80
  [   10.714619] RBP: b466007e7898 R08: 03d2 R09: 
0004
  [   10.714620] R10:  R11: 0001 R12: 
933cbdf31ea0
  [   10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: 

  [   10.714622] FS:  7fbcedc6efc0() GS:933cc9e0() 
knlGS:
  [   10.714622] CS:  0010 DS:  ES:  CR0: 80050033
  [   10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 
003606f0
  [   10.714623] Call Trace:
  [   10.714627]  rtw_pci_link_ps+0x4e/0x90 [rtwpci]
  [   10.714630]  ? _raw_spin_unlock_bh+0x1e/0x20
  [   10.714637]  rtw_leave_ips+0x1f/0x80 [rtw88]
  [   10.714640]  rtw_ops_config+0xa3/0xe0 [rtw88]
  [   10.714658]  ieee80211_hw_config+0x95/0x390 [mac80211]
  [   10.714669]  ieee80211_recalc_idle+0x27/0x30 [mac80211]
  [   10.714679]  __ieee80211_start_scan+0x334/0x750 [mac80211]
  [   10.714688]  ieee80211_request_scan+0x30/0x50 [mac80211]
  [   10.714699]  ieee80211_scan+0x5c/0xa0 [mac80211]
  [   10.714719]  nl80211_trigger_scan+0x59a/0x6c0 [cfg80211]
  [   10.714722]  genl_rcv_msg+0x1a8/0x470
  [   10.714724]  ? ep_poll_callback+0x2a0/0x2c0
  [   10.714725]  ? genl_family_rcv_msg_attrs_parse+0x100/0x100
  [   10.714726]  netlink_rcv_skb+0x50/0x120
  [   10.714728]  genl_rcv+0x29/0x40
  [   10.714729]  netlink_unicast+0x1a8/0x250
  [   10.714730]  netlink_sendmsg+0x233/0x460
  [   10.714739]  ? _copy_from_user+0x31/0x60
  [   10.714750]  sock_sendmsg+0x65/0x70
  [   10.714751]  sys_sendmsg+0x212/0x280
  [   10.714752]  ? copy_msghdr_from_user+0x5c/0x90
  [   10.714755]  ? __check_object_size+0x4d/0x150
  [   10.714756]  ___sys_sendmsg+0x81/0xc0
  [   10.714757]  ? __check_object_size+0x4d/0x150
  [   10.714759]  ? unix_ioctl+0x99/0x180
  [   10.714760]  ? sock_getsockopt+0x198/0xc04
  [   10.714761]  ? sock_do_ioctl+0x47/0x140
  [   10.714763]  ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0
  [   10.714765]  ? _cond_resched+0x19/0x30
  [   10.714767]  ? aa_sk_perm+0x43/0x1b0
  [   10.714768]  __sys_sendmsg+0x5c/0xa0
  [   10.714770]  __x64_sys_sendmsg+0x1f/0x30
  [   10.714772]  do_syscall_64+0x57/0x1b0
  [   10.714773]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   10.714774] RIP: 0033:0x7fbcedffb5b7
  [   10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 
f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10
  [   10.714776] RSP: 002b:7fff88e22288 EFLAGS: 0246 ORIG_RAX: 
002e
  [   10.714777] RAX: ffda RBX: 5632787355d0 RCX: 
7fbcedffb5b7
  [   10.714777] RDX:  RSI: 7fff88e222c0 RDI: 
0006
  [   10.714778] RBP: 563278761380 R08: 0004 R09: 
563278761380
  [   10.714778] R10: 7fff88e22394 R11: 0246 R12: 
5632787354e0
  [   10.714779] R13: 7fff88e222c0 R14: 7fff88e22394 R15: 
563278766710
  [   10.714780] ---[ end trace f00c16109236af6f ]---
  [   10.714782] rtw_pci :3a:00.0: failed to read ASPM, ret=-5

  
  Device is unable to scan for 

[Kernel-packages] [Bug 1872984] Re: RTL8822BE network driver now crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

[Matthew M]

I am unsure how to attach multiple log files so here are the contents of
the short logs. Attached is the output of "lspci -vvnn" in 5.7.0-rc1

Output of "uname -a" on 5.7.0:

Linux laptop 5.7.0-050700rc1-generic #202004122032 SMP Sun Apr 12
20:36:25 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

---
"cat /proc/version" on 5.7.0 yields:

Linux version 5.7.0-050700rc1-generic (kernel@sita) (gcc version 9.3.0
(Ubuntu 9.3.0-10ubuntu1), GNU ld (GNU Binutils for Ubuntu) 2.34)
#202004122032 SMP Sun Apr 12 20:36:25 UTC 2020

---
"cat /proc/version" on 5.4.0-21 yields:

Ubuntu 5.4.0-21.25-generic 5.4.27

---
"uname -a" on 5.4.0 yields:

Linux laptop 5.4.0-21-generic #25-Ubuntu SMP Sat Mar 28 13:10:28 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux


** Attachment added: "lspci-vvnn-5.7.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872984/+attachment/5354564/+files/lspci-vvnn-5.7.0.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/1872984

Title:
  RTL8822BE network driver now crashes on boot in Focal Fossa 20.04 -
  5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

Status in linux package in Ubuntu:
  New

Bug description:
  RTL8822BE crashes after rtw_pci starts on boot after kernel update to
  5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is
  still present on latest mainline kernel version
  5.7.0-050700rc1-generic .

  [   10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0
  [   10.714544] [ cut here ]
  [   10.714545] failed to read DBI register, addr=0x0719
  [   10.714577] WARNING: CPU: 0 PID: 939 at 
drivers/net/wireless/realtek/rtw88/pci.c:1156 
rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714577] Modules linked in: (see attached dmesg)
  [   10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 
5.7.0-050700rc1-generic #202004122032
  [   10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 
01/23/2018
  [   10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 
31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 
fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00
  [   10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282
  [   10.714618] RAX:  RBX:  RCX: 
0007
  [   10.714619] RDX: 0007 RSI: 0092 RDI: 
933cc9e19c80
  [   10.714619] RBP: b466007e7898 R08: 03d2 R09: 
0004
  [   10.714620] R10:  R11: 0001 R12: 
933cbdf31ea0
  [   10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: 

  [   10.714622] FS:  7fbcedc6efc0() GS:933cc9e0() 
knlGS:
  [   10.714622] CS:  0010 DS:  ES:  CR0: 80050033
  [   10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 
003606f0
  [   10.714623] Call Trace:
  [   10.714627]  rtw_pci_link_ps+0x4e/0x90 [rtwpci]
  [   10.714630]  ? _raw_spin_unlock_bh+0x1e/0x20
  [   10.714637]  rtw_leave_ips+0x1f/0x80 [rtw88]
  [   10.714640]  rtw_ops_config+0xa3/0xe0 [rtw88]
  [   10.714658]  ieee80211_hw_config+0x95/0x390 [mac80211]
  [   10.714669]  ieee80211_recalc_idle+0x27/0x30 [mac80211]
  [   10.714679]  __ieee80211_start_scan+0x334/0x750 [mac80211]
  [   10.714688]  ieee80211_request_scan+0x30/0x50 [mac80211]
  [   10.714699]  ieee80211_scan+0x5c/0xa0 [mac80211]
  [   10.714719]  nl80211_trigger_scan+0x59a/0x6c0 [cfg80211]
  [   10.714722]  genl_rcv_msg+0x1a8/0x470
  [   10.714724]  ? ep_poll_callback+0x2a0/0x2c0
  [   10.714725]  ? genl_family_rcv_msg_attrs_parse+0x100/0x100
  [   10.714726]  netlink_rcv_skb+0x50/0x120
  [   10.714728]  genl_rcv+0x29/0x40
  [   10.714729]  netlink_unicast+0x1a8/0x250
  [   10.714730]  netlink_sendmsg+0x233/0x460
  [   10.714739]  ? _copy_from_user+0x31/0x60
  [   10.714750]  sock_sendmsg+0x65/0x70
  [   10.714751]  sys_sendmsg+0x212/0x280
  [   10.714752]  ? copy_msghdr_from_user+0x5c/0x90
  [   10.714755]  ? __check_object_size+0x4d/0x150
  [   10.714756]  ___sys_sendmsg+0x81/0xc0
  [   10.714757]  ? __check_object_size+0x4d/0x150
  [   10.714759]  ? unix_ioctl+0x99/0x180
  [   10.714760]  ? sock_getsockopt+0x198/0xc04
  [   10.714761]  ? sock_do_ioctl+0x47/0x140
  [   10.714763]  ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0
  [   10.714765]  ? _cond_resched+0x19/0x30
  [   10.714767]  ? aa_sk_perm+0x43/0x1b0
  [   10.714768]  __sys_sendmsg+0x5c/0xa0
  [   10.714770]  __x64_sys_sendmsg+0x1f/0x30
  [   10.714772]  do_syscall_64+0x57/0x1b0
  [   10.714773]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   10.714774] RIP: 0033:0x7fbcedffb5b7
  [   10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 
f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 

[Kernel-packages] [Bug 1872984] Re: RTL8822BE network driver now crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

[Matthew M]

** Attachment added: "lspci-vvnn-5.4.0-21.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872984/+attachment/5354566/+files/lspci-vvnn-5.4.0-21.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/1872984

Title:
  RTL8822BE network driver now crashes on boot in Focal Fossa 20.04 -
  5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

Status in linux package in Ubuntu:
  New

Bug description:
  RTL8822BE crashes after rtw_pci starts on boot after kernel update to
  5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is
  still present on latest mainline kernel version
  5.7.0-050700rc1-generic .

  [   10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0
  [   10.714544] [ cut here ]
  [   10.714545] failed to read DBI register, addr=0x0719
  [   10.714577] WARNING: CPU: 0 PID: 939 at 
drivers/net/wireless/realtek/rtw88/pci.c:1156 
rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714577] Modules linked in: (see attached dmesg)
  [   10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 
5.7.0-050700rc1-generic #202004122032
  [   10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 
01/23/2018
  [   10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 
31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 
fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00
  [   10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282
  [   10.714618] RAX:  RBX:  RCX: 
0007
  [   10.714619] RDX: 0007 RSI: 0092 RDI: 
933cc9e19c80
  [   10.714619] RBP: b466007e7898 R08: 03d2 R09: 
0004
  [   10.714620] R10:  R11: 0001 R12: 
933cbdf31ea0
  [   10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: 

  [   10.714622] FS:  7fbcedc6efc0() GS:933cc9e0() 
knlGS:
  [   10.714622] CS:  0010 DS:  ES:  CR0: 80050033
  [   10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 
003606f0
  [   10.714623] Call Trace:
  [   10.714627]  rtw_pci_link_ps+0x4e/0x90 [rtwpci]
  [   10.714630]  ? _raw_spin_unlock_bh+0x1e/0x20
  [   10.714637]  rtw_leave_ips+0x1f/0x80 [rtw88]
  [   10.714640]  rtw_ops_config+0xa3/0xe0 [rtw88]
  [   10.714658]  ieee80211_hw_config+0x95/0x390 [mac80211]
  [   10.714669]  ieee80211_recalc_idle+0x27/0x30 [mac80211]
  [   10.714679]  __ieee80211_start_scan+0x334/0x750 [mac80211]
  [   10.714688]  ieee80211_request_scan+0x30/0x50 [mac80211]
  [   10.714699]  ieee80211_scan+0x5c/0xa0 [mac80211]
  [   10.714719]  nl80211_trigger_scan+0x59a/0x6c0 [cfg80211]
  [   10.714722]  genl_rcv_msg+0x1a8/0x470
  [   10.714724]  ? ep_poll_callback+0x2a0/0x2c0
  [   10.714725]  ? genl_family_rcv_msg_attrs_parse+0x100/0x100
  [   10.714726]  netlink_rcv_skb+0x50/0x120
  [   10.714728]  genl_rcv+0x29/0x40
  [   10.714729]  netlink_unicast+0x1a8/0x250
  [   10.714730]  netlink_sendmsg+0x233/0x460
  [   10.714739]  ? _copy_from_user+0x31/0x60
  [   10.714750]  sock_sendmsg+0x65/0x70
  [   10.714751]  sys_sendmsg+0x212/0x280
  [   10.714752]  ? copy_msghdr_from_user+0x5c/0x90
  [   10.714755]  ? __check_object_size+0x4d/0x150
  [   10.714756]  ___sys_sendmsg+0x81/0xc0
  [   10.714757]  ? __check_object_size+0x4d/0x150
  [   10.714759]  ? unix_ioctl+0x99/0x180
  [   10.714760]  ? sock_getsockopt+0x198/0xc04
  [   10.714761]  ? sock_do_ioctl+0x47/0x140
  [   10.714763]  ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0
  [   10.714765]  ? _cond_resched+0x19/0x30
  [   10.714767]  ? aa_sk_perm+0x43/0x1b0
  [   10.714768]  __sys_sendmsg+0x5c/0xa0
  [   10.714770]  __x64_sys_sendmsg+0x1f/0x30
  [   10.714772]  do_syscall_64+0x57/0x1b0
  [   10.714773]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   10.714774] RIP: 0033:0x7fbcedffb5b7
  [   10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 
f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10
  [   10.714776] RSP: 002b:7fff88e22288 EFLAGS: 0246 ORIG_RAX: 
002e
  [   10.714777] RAX: ffda RBX: 5632787355d0 RCX: 
7fbcedffb5b7
  [   10.714777] RDX:  RSI: 7fff88e222c0 RDI: 
0006
  [   10.714778] RBP: 563278761380 R08: 0004 R09: 
563278761380
  [   10.714778] R10: 7fff88e22394 R11: 0246 R12: 
5632787354e0
  [   10.714779] R13: 7fff88e222c0 R14: 7fff88e22394 R15: 
563278766710
  [   10.714780] ---[ end trace f00c16109236af6f ]---
  [   10.714782] rtw_pci :3a:00.0: failed to read ASPM, ret=-5

  
  Device is unable to scan 

[Kernel-packages] [Bug 1872984] [NEW] RTL8822BE network driver now crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

[Matthew M]

Public bug reported:

RTL8822BE crashes after rtw_pci starts on boot after kernel update to
5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is
still present on latest mainline kernel version 5.7.0-050700rc1-generic
.

[   10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0
[   10.714544] [ cut here ]
[   10.714545] failed to read DBI register, addr=0x0719
[   10.714577] WARNING: CPU: 0 PID: 939 at 
drivers/net/wireless/realtek/rtw88/pci.c:1156 
rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
[   10.714577] Modules linked in: (see attached dmesg)
[   10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 
5.7.0-050700rc1-generic #202004122032
[   10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 
01/23/2018
[   10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
[   10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 
31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 
fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00
[   10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282
[   10.714618] RAX:  RBX:  RCX: 0007
[   10.714619] RDX: 0007 RSI: 0092 RDI: 933cc9e19c80
[   10.714619] RBP: b466007e7898 R08: 03d2 R09: 0004
[   10.714620] R10:  R11: 0001 R12: 933cbdf31ea0
[   10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: 
[   10.714622] FS:  7fbcedc6efc0() GS:933cc9e0() 
knlGS:
[   10.714622] CS:  0010 DS:  ES:  CR0: 80050033
[   10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 003606f0
[   10.714623] Call Trace:
[   10.714627]  rtw_pci_link_ps+0x4e/0x90 [rtwpci]
[   10.714630]  ? _raw_spin_unlock_bh+0x1e/0x20
[   10.714637]  rtw_leave_ips+0x1f/0x80 [rtw88]
[   10.714640]  rtw_ops_config+0xa3/0xe0 [rtw88]
[   10.714658]  ieee80211_hw_config+0x95/0x390 [mac80211]
[   10.714669]  ieee80211_recalc_idle+0x27/0x30 [mac80211]
[   10.714679]  __ieee80211_start_scan+0x334/0x750 [mac80211]
[   10.714688]  ieee80211_request_scan+0x30/0x50 [mac80211]
[   10.714699]  ieee80211_scan+0x5c/0xa0 [mac80211]
[   10.714719]  nl80211_trigger_scan+0x59a/0x6c0 [cfg80211]
[   10.714722]  genl_rcv_msg+0x1a8/0x470
[   10.714724]  ? ep_poll_callback+0x2a0/0x2c0
[   10.714725]  ? genl_family_rcv_msg_attrs_parse+0x100/0x100
[   10.714726]  netlink_rcv_skb+0x50/0x120
[   10.714728]  genl_rcv+0x29/0x40
[   10.714729]  netlink_unicast+0x1a8/0x250
[   10.714730]  netlink_sendmsg+0x233/0x460
[   10.714739]  ? _copy_from_user+0x31/0x60
[   10.714750]  sock_sendmsg+0x65/0x70
[   10.714751]  sys_sendmsg+0x212/0x280
[   10.714752]  ? copy_msghdr_from_user+0x5c/0x90
[   10.714755]  ? __check_object_size+0x4d/0x150
[   10.714756]  ___sys_sendmsg+0x81/0xc0
[   10.714757]  ? __check_object_size+0x4d/0x150
[   10.714759]  ? unix_ioctl+0x99/0x180
[   10.714760]  ? sock_getsockopt+0x198/0xc04
[   10.714761]  ? sock_do_ioctl+0x47/0x140
[   10.714763]  ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0
[   10.714765]  ? _cond_resched+0x19/0x30
[   10.714767]  ? aa_sk_perm+0x43/0x1b0
[   10.714768]  __sys_sendmsg+0x5c/0xa0
[   10.714770]  __x64_sys_sendmsg+0x1f/0x30
[   10.714772]  do_syscall_64+0x57/0x1b0
[   10.714773]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[   10.714774] RIP: 0033:0x7fbcedffb5b7
[   10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 
f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10
[   10.714776] RSP: 002b:7fff88e22288 EFLAGS: 0246 ORIG_RAX: 
002e
[   10.714777] RAX: ffda RBX: 5632787355d0 RCX: 7fbcedffb5b7
[   10.714777] RDX:  RSI: 7fff88e222c0 RDI: 0006
[   10.714778] RBP: 563278761380 R08: 0004 R09: 563278761380
[   10.714778] R10: 7fff88e22394 R11: 0246 R12: 5632787354e0
[   10.714779] R13: 7fff88e222c0 R14: 7fff88e22394 R15: 563278766710
[   10.714780] ---[ end trace f00c16109236af6f ]---
[   10.714782] rtw_pci :3a:00.0: failed to read ASPM, ret=-5


Device is unable to scan for networks and error occurs when attempting to turn 
on/off wifi in settings:

[  302.451636] rtw_pci :3a:00.0: stop vif 5c:ea:1d:b6:17:11 on port 0
[  308.820551] rtw_pci :3a:00.0: mac power on failed
[  308.820554] rtw_pci :3a:00.0: failed to power on mac


However, issue is NOT present for me on kernel version 5.4.0-18-generic (but is 
present on 5.4.0-21-generic and 5.7.0- as mentioned above). Changing kernel 
versions with grub has been a temporary solution.

Relevant log files are attached from tests in both kernel versions
mentioned above (5.4.0-21 and 5.7.0-). Additional log files can be added
upon request, as I am able