[Kernel-packages] [Bug 1875252] Re: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers

[Rajasekharan N]

Bogdan (elrohe)

Oops. I couldn't save you the trouble. Sorry. It didn't strike me for
about 12 hours or so since the update to alert the remaining affected
people. During this time, after realizing that Pulseaudio has broken
down again, I was trying if I can do with Alsa alone or if I could find
any other alternative for Pulseaudio. However, I was unsuccessful.

It's nearing a month since I ran into this trouble by updating to 20.04
LTS and have run wall to post.

There is hope. There is a new fix/update coming. It's already in the
git. I don't know when it will be available in the updates channel.

See bug 1876065 for the latest info regarding this.

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

Title:
  Ubuntu 20.04 LTS update causing no sound coming from built-in speakers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to Ubuntu 20.04 LTS, the only way of hearing audio is
  through headphones. The sound settings tab doesn't even show any other
  output option other than "Dummy output" . I have already checked other
  versions and everything works perfectly when I downgrade to Ubuntu
  19.10, so I think this is a version related bug. Just to reiterate my
  laptop is a DELL Inspiron 14 3420.The sound card showing in alsamixer
  window is HDA Intel PCH, and the chip is Cirrus Logic CS4213. I have
  looked up solutions online for 2 days and none has worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  george 1499 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 19:04:06 2020
  InstallationDate: Installed on 2020-04-26 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Inspiron 3420
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=ec9a2552-c1da-44bd-9967-5be8bc6da075 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-26 (0 days ago)
  dmi.bios.date: 09/28/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 04XGDT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd09/28/2012:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn04XGDT:rvrA05:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3420
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1860847] Re: [nvidia] system is feeze

[Launchpad Bug Tracker]

[Expired for nvidia-graphics-drivers-390 (Ubuntu) because there has been
no activity for 60 days.]

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [nvidia] system is feeze

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Expired

Bug description:
  I have problem with graphic cards. After work, when I reboot system
  then system feeze and I can't work. I must change to the recovery mode
  and next work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Jest katalogiem: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.129  Mon Jul 22 21:10:21 
PDT 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Jan 25 10:07:46 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.3.0-18-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.3.0-26-generic, x86_64: installed
   nvidia, 390.129, 5.3.0-18-generic, x86_64: installed
   nvidia, 390.129, 5.3.0-26-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: Dell GF119M [NVS 4200M] [1028:0494]
  InstallationDate: Installed on 2020-01-24 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Latitude E6520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=e65c7e31-8fb3-43f7-8a68-c1bb187f8f8c ro recovery nomodeset
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 07/11/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0J4TFW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/11/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Jan 25 09:24:56 2020
  xserver.configfile: default
  xserver.errors:
   open /dev/fb0: No such file or directory
   systemd-logind: failed to release device: Device not taken
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.5+git20191008-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1860847/+subscriptions

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

[Kernel-packages] [Bug 1865175] Re: Demo

[Launchpad Bug Tracker]

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

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

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

Title:
  Demo

Status in linux package in Ubuntu:
  Expired

Bug description:
  Intel ACPI Component Architecture
  ACPI Binary Table Extraction Utility version 20190509
  Copyright (c) 2000 - 2019 Intel Corporation

DSDT -   24651 bytes written (0x604B) - dsdt.dat
SSDT -2128 bytes written (0x0850) - ssdt1.dat
SSDT -2272 bytes written (0x08E0) - ssdt2.dat
SSDT -6547 bytes written (0x1993) - ssdt3.dat
SSDT -3781 bytes written (0x0EC5) - ssdt4.dat
SSDT -   21351 bytes written (0x5367) - ssdt5.dat
  (base) eduardo@eduardo-Lenovo-ideapad-330-15ARR:~$ iasl -d DSDT.dat

  Intel ACPI Component Architecture
  ASL+ Optimizing Compiler/Disassembler version 20190509
  Copyright (c) 2000 - 2019 Intel Corporation

  Error6092 - Could not open file "DSDT.dat" (Source Input) - No
  such file or directory

  (base) eduardo@eduardo-Lenovo-ideapad-330-15ARR:~$ sudo fwts > fwts
  Test: Gather kernel system information. 
Gather kernel signature.1 info only 

Gather kernel system information.   1 info only 

Gather kernel boot command line.1 info only 

Gather ACPI driver version. 1 info only 

  Test: Gather BIOS DMI information.  
Gather BIOS DMI information 1 info only 

  Test: OPAL Processor Power Management DT Validation Tests   
Test skipped, missing features: devicetree  

  Test: OPAL Reserved memory DT Validation Test   
Test skipped, missing features: devicetree  

  Test: OPAL Processor Recovery Diagnostics Info  
Test skipped, missing features: devicetree  

  Test: Scan kernel log for Oopses.   
Kernel log oops check.  2 passed

  Test: Run OLOG scan and analysis checks.
   Test skipped.

  Test: Scan kernel log for errors and warnings.  
Kernel log error check. 1 passed

  Test: BMC Info  
Test skipped, missing features: IPMI

  Test: Scan coreboot log for errors and warnings.
   Test skipped.

  Test: MTRR tests.   
Validate the kernel MTRR IOMEM setup.   1 passed

Validate the MTRR setup across all processors.  1 passed

Test for AMD MtrrFixDramModEn being cleared by the B..  1 passed

  Test: General ACPI information test.
Determine Kernel ACPI version.  1 info only 

Determine machine's ACPI version.   1 info only 

Determine AML compiler. 1 info only 

  Test: Device tree system information test   
Test skipped, missing features: devicetree  

  Test: Base device tree validity check   
Test skipped, missing features: devicetree  

  Test: OPAL CPU Info 
Test skipped, missing features: devicetree  

  Test: OPAL MEM Info 
Test skipped, missing features: devicetree  

  Test: Sanity check for UEFI Boot Path Boot. 
Test UEFI Boot Path Boot.   7 passed

  Test: UEFI Compatibility Support Module test.   
UEFI Compatibility Support Module test. 1 info only 

  Test: Test firmware has set PCI Express MaxReadReq to a higher value on 

[Kernel-packages] [Bug 1867440] Re: touchpad not recognized

[Launchpad Bug Tracker]

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

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

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

Title:
  touchpad not recognized

Status in linux package in Ubuntu:
  Expired

Bug description:
  Laptop model: xiaomi mi notebook air 12.5 m3-7y30
  Touchpad: Synaptics
  Ubuntu version: Ubuntu 4.15.0-88.88-generic 4.15.18
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  
  Problem appeared ~2 months ago

  Touchpad worked fine for 2 years, now suddenly not anymore. No sign of
  activity. Touchpad and mouse usage does not activate anything on the
  computer screen. I can't find help on how to restore the previous
  state, how to get the touchpad working again.

  when filing cmd command xinput list, synaptics touchpad and/or mouse
  are NOT displayed. command "cat /proc/bus/input/devices" also does not
  show a touchpad device.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-88-generic 4.15.0-88.88
  ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18
  Uname: Linux 4.15.0-88-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  clara  1511 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 14 15:38:09 2020
  HibernationDevice: RESUME=UUID=284b28ec-5e8d-4423-9c9d-dccd8b7257ac
  InstallationDate: Installed on 2018-12-29 (441 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b59a Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Timi TM1607
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic 
root=UUID=c6a6166b-6804-4061-8ec9-d2e688e3cd96 ro quiet splash 
ivrs_ioapic[32]=00:14.0 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-88-generic N/A
   linux-backports-modules-4.15.0-88-generic  N/A
   linux-firmware 1.173.16
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2017
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: XMAKB200P0100
  dmi.board.asset.tag: Any
  dmi.board.name: TM1607
  dmi.board.vendor: Timi
  dmi.board.version: MP
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrXMAKB200P0100:bd05/07/2017:svnTimi:pnTM1607:pvr:rvnTimi:rnTM1607:rvrMP:cvnTimi:ct10:cvrChassisVersion:
  dmi.product.family: Timibook
  dmi.product.name: TM1607
  dmi.sys.vendor: Timi

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

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

Re: [Kernel-packages] [Bug 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

[Seth Arnold]

On Sat, May 16, 2020 at 01:56:08AM -, Seth Arnold wrote:
> Sadly, journalctl doesn't have the dmesg from the previous boot:

I meant to say, journalctl's copy of dmesg from the previous boot doesn't
have the new debug output. Sorry.

Thanks

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

Title:
  zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

Status in Linux:
  New
Status in zfs-linux package in Ubuntu:
  Incomplete
Status in zfs-linux source package in Bionic:
  New

Bug description:
  Same as bug 1861228 but with a newer kernel installed.

  [  790.702566] VERIFY(size != 0) failed
  [  790.702590] PANIC at range_tree.c:304:range_tree_find_impl()
  [  790.702611] Showing stack for process 28685
  [  790.702614] CPU: 17 PID: 28685 Comm: receive_writer Tainted: P   O 
4.15.0-76-generic #86-Ubuntu
  [  790.702615] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 
2.0 12/17/2015
  [  790.702616] Call Trace:
  [  790.702626]  dump_stack+0x6d/0x8e
  [  790.702637]  spl_dumpstack+0x42/0x50 [spl]
  [  790.702640]  spl_panic+0xc8/0x110 [spl]
  [  790.702645]  ? __switch_to_asm+0x41/0x70
  [  790.702714]  ? arc_prune_task+0x1a/0x40 [zfs]
  [  790.702740]  ? dbuf_dirty+0x43d/0x850 [zfs]
  [  790.702745]  ? getrawmonotonic64+0x43/0xd0
  [  790.702746]  ? getrawmonotonic64+0x43/0xd0
  [  790.702775]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702778]  ? getrawmonotonic64+0x43/0xd0
  [  790.702805]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702807]  ? mutex_lock+0x12/0x40
  [  790.702833]  ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs]
  [  790.702866]  range_tree_find_impl+0x88/0x90 [zfs]
  [  790.702870]  ? spl_kmem_zalloc+0xdc/0x1a0 [spl]
  [  790.702902]  range_tree_clear+0x4f/0x60 [zfs]
  [  790.702930]  dnode_free_range+0x11f/0x5a0 [zfs]
  [  790.702957]  dmu_object_free+0x53/0x90 [zfs]
  [  790.702983]  dmu_free_long_object+0x9f/0xc0 [zfs]
  [  790.703010]  receive_freeobjects.isra.12+0x7a/0x100 [zfs]
  [  790.703036]  receive_writer_thread+0x6d2/0xa60 [zfs]
  [  790.703040]  ? set_curr_task_fair+0x2b/0x60
  [  790.703043]  ? spl_kmem_free+0x33/0x40 [spl]
  [  790.703048]  ? kfree+0x165/0x180
  [  790.703073]  ? receive_free.isra.13+0xc0/0xc0 [zfs]
  [  790.703078]  thread_generic_wrapper+0x74/0x90 [spl]
  [  790.703081]  kthread+0x121/0x140
  [  790.703084]  ? __thread_exit+0x20/0x20 [spl]
  [  790.703085]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  790.703088]  ret_from_fork+0x35/0x40
  [  967.636923] INFO: task txg_quiesce:14810 blocked for more than 120 seconds.
  [  967.636979]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
  [  967.637024] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.637076] txg_quiesce D0 14810  2 0x8000
  [  967.637080] Call Trace:
  [  967.637089]  __schedule+0x24e/0x880
  [  967.637092]  schedule+0x2c/0x80
  [  967.637106]  cv_wait_common+0x11e/0x140 [spl]
  [  967.637114]  ? wait_woken+0x80/0x80
  [  967.637122]  __cv_wait+0x15/0x20 [spl]
  [  967.637210]  txg_quiesce_thread+0x2cb/0x3d0 [zfs]
  [  967.637278]  ? txg_delay+0x1b0/0x1b0 [zfs]
  [  967.637286]  thread_generic_wrapper+0x74/0x90 [spl]
  [  967.637291]  kthread+0x121/0x140
  [  967.637297]  ? __thread_exit+0x20/0x20 [spl]
  [  967.637299]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  967.637304]  ret_from_fork+0x35/0x40
  [  967.637326] INFO: task zfs:28590 blocked for more than 120 seconds.
  [  967.637371]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
  [  967.637416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.637467] zfs D0 28590  28587 0x8080
  [  967.637470] Call Trace:
  [  967.637474]  __schedule+0x24e/0x880
  [  967.637477]  schedule+0x2c/0x80
  [  967.637486]  cv_wait_common+0x11e/0x140 [spl]
  [  967.637491]  ? wait_woken+0x80/0x80
  [  967.637498]  __cv_wait+0x15/0x20 [spl]
  [  967.637554]  dmu_recv_stream+0xa51/0xef0 [zfs]
  [  967.637630]  zfs_ioc_recv_impl+0x306/0x1100 [zfs]
  [  967.637679]  ? dbuf_read+0x34a/0x920 [zfs]
  [  967.637725]  ? dbuf_rele+0x36/0x40 [zfs]
  [  967.637728]  ? _cond_resched+0x19/0x40
  [  967.637798]  zfs_ioc_recv_new+0x33d/0x410 [zfs]
  [  967.637809]  ? spl_kmem_alloc_impl+0xe5/0x1a0 [spl]
  [  967.637816]  ? spl_vmem_alloc+0x19/0x20 [spl]
  [  967.637828]  ? nv_alloc_sleep_spl+0x1f/0x30 [znvpair]
  [  967.637834]  ? nv_mem_zalloc.isra.0+0x2e/0x40 [znvpair]
  [  967.637840]  ? nvlist_xalloc.part.2+0x50/0xb0 [znvpair]
  [  967.637905]  zfsdev_ioctl+0x451/0x610 [zfs]
  [  967.637913]  do_vfs_ioctl+0xa8/0x630
  [  967.637917]  ? __audit_syscall_entry+0xbc/0x110
  [  967.637924]  ? syscall_trace_enter+0x1da/0x2d0
  [  967.637927]  SyS_ioctl+0x79/0x90
  [  967.637930]  do_syscall_64+0x73/0x130
  [  967.637935]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [  967.637938] RIP: 

[Kernel-packages] [Bug 1879017] 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/1879017

Title:
  dd caused systemd-udevd call trace

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Using dd to copy an image onto sdcard seems to cause a kernel stack
  trace.  dd seems to hang.

  [ 3747.220647] INFO: task systemd-udevd:2451 blocked for more than 483 
seconds.
  [ 3747.220652]   Tainted: P  IOE 5.4.0-29-generic #33-Ubuntu
  [ 3747.220654] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.   
 
  [ 3747.220656] systemd-udevd   D0  2451  1 0x4124
  [ 3747.220660] Call Trace:
  [ 3747.220670]  __schedule+0x2e3/0x740
  [ 3747.220673]  schedule+0x42/0xb0
  [ 3747.220675]  schedule_preempt_disabled+0xe/0x10
  [ 3747.220678]  __mutex_lock.isra.0+0x182/0x4f0
  [ 3747.220683]  ? exact_lock+0x11/0x20
  [ 3747.220685]  __mutex_lock_slowpath+0x13/0x20
  [ 3747.220687]  mutex_lock+0x2e/0x40
  [ 3747.220692]  __blkdev_get+0x78/0x550
  [ 3747.220694]  blkdev_get+0x3d/0x140
  [ 3747.220697]  ? blkdev_get_by_dev+0x50/0x50
  [ 3747.220699]  blkdev_open+0x8f/0xa0
  [ 3747.220704]  do_dentry_open+0x143/0x3a0
  [ 3747.220706]  vfs_open+0x2d/0x30
  [ 3747.220710]  do_last+0x194/0x900
  [ 3747.220713]  path_openat+0x8d/0x290
  [ 3747.220716]  do_filp_open+0x91/0x100
  [ 3747.220720]  ? __alloc_fd+0x46/0x150
  [ 3747.220722]  do_sys_open+0x17e/0x290
  [ 3747.220724]  __x64_sys_openat+0x20/0x30
  [ 3747.220729]  do_syscall_64+0x57/0x190
  [ 3747.220735]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 3747.220738] RIP: 0033:0x7f18e48a1d1b
  [ 3747.220745] Code: Bad RIP value.
  [ 3747.220746] RSP: 002b:7ffd19e936a0 EFLAGS: 0246 ORIG_RAX: 
0101
  [ 3747.220748] RAX: ffda RBX: 7ffd19e937b0 RCX: 
7f18e48a1d1b
  [ 3747.220749] RDX: 000a0800 RSI: 558d7f09f470 RDI: 
ff9c
  [ 3747.220750] RBP: 558d7f09f470 R08: 558d7d4740c0 R09: 

  [ 3747.220751] R10:  R11: 0246 R12: 
000a0800
  [ 3747.220752] R13: 558d7f0b2920 R14: 7ffd19e93778 R15: 
0001

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  js11209 F pulseaudio
   /dev/snd/controlC1:  js11209 F pulseaudio
   /dev/snd/controlC0:  js11209 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Fri May 15 22:44:18 2020
  InstallationDate: Installed on 2020-02-02 (103 days ago)
  InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1)
  MachineType: Dell Inc. Precision WorkStation T7500
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=93fc02c6-baa4-4282-96d7-ea5ad53b0c78 ro ipv6.disable=1 
elevator=deadline splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0D881F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd10/15/2018:svnDellInc.:pnPrecisionWorkStationT7500:pvr:rvnDellInc.:rn0D881F:rvrA05:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation T7500
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1879017] [NEW] dd caused systemd-udevd call trace

[js1]

Public bug reported:

Using dd to copy an image onto sdcard seems to cause a kernel stack
trace.  dd seems to hang.

[ 3747.220647] INFO: task systemd-udevd:2451 blocked for more than 483 seconds.
[ 3747.220652]   Tainted: P  IOE 5.4.0-29-generic #33-Ubuntu
[ 3747.220654] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.

[ 3747.220656] systemd-udevd   D0  2451  1 0x4124
[ 3747.220660] Call Trace:
[ 3747.220670]  __schedule+0x2e3/0x740
[ 3747.220673]  schedule+0x42/0xb0
[ 3747.220675]  schedule_preempt_disabled+0xe/0x10
[ 3747.220678]  __mutex_lock.isra.0+0x182/0x4f0
[ 3747.220683]  ? exact_lock+0x11/0x20
[ 3747.220685]  __mutex_lock_slowpath+0x13/0x20
[ 3747.220687]  mutex_lock+0x2e/0x40
[ 3747.220692]  __blkdev_get+0x78/0x550
[ 3747.220694]  blkdev_get+0x3d/0x140
[ 3747.220697]  ? blkdev_get_by_dev+0x50/0x50
[ 3747.220699]  blkdev_open+0x8f/0xa0
[ 3747.220704]  do_dentry_open+0x143/0x3a0
[ 3747.220706]  vfs_open+0x2d/0x30
[ 3747.220710]  do_last+0x194/0x900
[ 3747.220713]  path_openat+0x8d/0x290
[ 3747.220716]  do_filp_open+0x91/0x100
[ 3747.220720]  ? __alloc_fd+0x46/0x150
[ 3747.220722]  do_sys_open+0x17e/0x290
[ 3747.220724]  __x64_sys_openat+0x20/0x30
[ 3747.220729]  do_syscall_64+0x57/0x190
[ 3747.220735]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 3747.220738] RIP: 0033:0x7f18e48a1d1b
[ 3747.220745] Code: Bad RIP value.
[ 3747.220746] RSP: 002b:7ffd19e936a0 EFLAGS: 0246 ORIG_RAX: 
0101
[ 3747.220748] RAX: ffda RBX: 7ffd19e937b0 RCX: 7f18e48a1d1b
[ 3747.220749] RDX: 000a0800 RSI: 558d7f09f470 RDI: ff9c
[ 3747.220750] RBP: 558d7f09f470 R08: 558d7d4740c0 R09: 
[ 3747.220751] R10:  R11: 0246 R12: 000a0800
[ 3747.220752] R13: 558d7f0b2920 R14: 7ffd19e93778 R15: 0001

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-29-generic 5.4.0-29.33
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  js11209 F pulseaudio
 /dev/snd/controlC1:  js11209 F pulseaudio
 /dev/snd/controlC0:  js11209 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: LXQt
Date: Fri May 15 22:44:18 2020
InstallationDate: Installed on 2020-02-02 (103 days ago)
InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1)
MachineType: Dell Inc. Precision WorkStation T7500
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=93fc02c6-baa4-4282-96d7-ea5ad53b0c78 ro ipv6.disable=1 
elevator=deadline splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-29-generic N/A
 linux-backports-modules-5.4.0-29-generic  N/A
 linux-firmware1.187
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/15/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A18
dmi.board.name: 0D881F
dmi.board.vendor: Dell Inc.
dmi.board.version: A05
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd10/15/2018:svnDellInc.:pnPrecisionWorkStationT7500:pvr:rvnDellInc.:rn0D881F:rvrA05:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision WorkStation T7500
dmi.sys.vendor: Dell Inc.

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

Title:
  dd caused systemd-udevd call trace

Status in linux package in Ubuntu:
  New

Bug description:
  Using dd to copy an image onto sdcard seems to cause a kernel stack
  trace.  dd seems to hang.

  [ 3747.220647] INFO: task systemd-udevd:2451 blocked for more than 483 
seconds.
  [ 3747.220652]   Tainted: P  IOE 5.4.0-29-generic #33-Ubuntu
  [ 3747.220654] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.   
 
  [ 3747.220656] systemd-udevd   D0  2451  1 0x4124
  [ 3747.220660] Call Trace:
  [ 3747.220670]  __schedule+0x2e3/0x740
  [ 3747.220673]  schedule+0x42/0xb0
  [ 3747.220675]  schedule_preempt_disabled+0xe/0x10
  [ 3747.220678]  __mutex_lock.isra.0+0x182/0x4f0
  [ 3747.220683]  ? exact_lock+0x11/0x20
  [ 3747.220685]  __mutex_lock_slowpath+0x13/0x20
  [ 3747.220687]  mutex_lock+0x2e/0x40
  [ 3747.220692]  __blkdev_get+0x78/0x550
  [ 3747.220694]  blkdev_get+0x3d/0x140
  [ 3747.220697]  

Re: [Kernel-packages] [Bug 1876847] Re: HP-Spectre 2019 Intel wireless driver is detected incorrectly.

[You-Sheng Yang]

For Bluetooth:

  Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi
  ...
  Bluetooth: hci0: command 0xfc09 tx timeout

That's a known issue for Bionic, but it should be fine for focal with
REL0384 fw. However it still fails on your system, so we may need you to
run a few commands to capture btsnoop logs:

  1. Power off completely. Unplug power cable for 1 minute, and then power
on,
  2. Boot with following parameters to prevent automatical driver loading
for Bluetooth:

 modprobe.blacklist=btusb,btintel

  3. Run `sudo btmon -w coldboot.btsnoop` in a separate terminal,
  4. Run `sudo modprobe btusb`,
  5. Check if Bluetooth is up,
  6. Run `journalctl -b 0 > coldboot.journal`
  7. If Bluetooth is dead, attach the btsnoop and journal log; or, continue
to following steps,
  8. Warm reboot with same parameters as step 2.,
  9. Run `sudo btmon -w warmboot.btsnoop` in a separate terminal,
  10. Run `sudo modprobe btusb`,
  11. Check if Bluetooth is up,
  12. Run `journalctl -b 0 > warmboot.journal`,
  13. If Bluetooth is dead, attach the btsnoop and journal log for both
cold boot and warm boot; or, repeat steps 8. to 13. for a few (10) times to
see if it reproduces.

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

Title:
  HP-Spectre 2019 Intel wireless driver is detected incorrectly.

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Output of lsb_release -rd,
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  Issue:
  I have Intel AX-201 for wireless but when i do "lspci -k", the driver is 
detected as "Intel-9462". When i did "journalctl -k | grep iwlwifi", it shows 
that the wireless driver detected is "Intel AX-201".

  Output of lspci -k,
  00:14.3 Network controller: Intel Corporation Wireless-AC 9462
   Subsystem: Intel Corporation Wireless-AC 9462
   Kernel driver in use: iwlwifi
   Kernel modules: iwlwifi

  Output of journalctl -k | grep iwlwifi,
  May 04 23:20:12 kernel: iwlwifi :00:14.3: enabling device ( -> 0002)
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuZ-a0-hr-b0-50.ucode failed with error -2
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuZ-a0-hr-b0-49.ucode failed with error -2
  May 04 23:20:12 kernel: iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ 
Version: 43.2.23.17
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug destination: 
EXTERNAL_DRAM
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug configuration: 0
  May 04 23:20:12 kernel: iwlwifi :00:14.3: loaded firmware version 
48.4fa0041f.0 op_mode iwlmvm
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX201 
160MHz, REV=0x354
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Allocated 0x0040 bytes for 
firmware monitor.
  May 04 23:20:12 kernel: iwlwifi :00:14.3: base HW address: 
7c:b2:7d:d0:d5:95
  May 04 23:20:12 kernel: iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0
  May 04 23:20:13 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
  May 04 23:20:13 kernel: iwlwifi :00:14.3: FW already configured (0) - 
re-configuring

  In the additional drivers module, it shows that module Intel-9462 no
  longer works. My bluetooth is also not detected and doesn't work.

  I came across this but no else responded yet. So decided to report a bug here.
  
https://askubuntu.com/questions/1232224/intel-ax201-detected-as-ac9462-wifi-connectivity-problems

  Please let me know if any more information is required.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  srikar 1447 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-03 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP HP Spectre x360 Convertible 15-df1xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=8d5d378c-648e-4355-8c1c-10cb298b2677 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:
   1: phy0: Wireless LAN
Soft 

[Kernel-packages] [Bug 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

[Seth Arnold]

Hello Colin, trying the zfs recv operation on the .3 dkms eventually
kills my system dead. There was nothing on the console. The cursor on
the console stopped blinking; I couldn't switch VTs. My ssh sessions
were hung. ping reported destination host unreachable.

It ran for about two and a half minutes, transferred around 10 datasets or 
snapshots:
$ journalctl -b -1  | grep -c "COMMAND=/sbin/zfs receive"
10


Sadly, journalctl doesn't have the dmesg from the previous boot:

$ journalctl -b -1 -k
[...]
May 15 17:25:10 wopr kernel: ZFS: Loaded module 
v0.7.5-1ubuntu16.10~lp1861235.3, ZFS pool version 5000, ZFS filesystem version 5
May 15 17:25:15 wopr kernel:  zd32: p1
May 15 17:25:20 wopr kernel: pps pps0: new PPS source ptp0
May 15 17:25:20 wopr kernel: ixgbe :05:00.0: registered PHC device on 
enp5s0f0
May 15 17:25:20 wopr kernel: IPv6: ADDRCONF(NETDEV_UP): enp5s0f0: link is not 
ready
May 15 17:25:20 wopr kernel: new mount options do not match the existing 
superblock, will be ignored
May 15 17:25:21 wopr kernel: Process accounting resumed
May 15 17:25:24 wopr kernel: ixgbe :05:00.0 enp5s0f0: NIC Link is Up 1 
Gbps, Flow Control: None
May 15 17:25:24 wopr kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp5s0f0: link 
becomes ready
May 15 17:25:29 wopr kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 
state recovery directory
May 15 17:25:29 wopr kernel: NFSD: starting 90-second grace period (net 
f0a9)
May 15 17:25:32 wopr kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
May 15 17:25:32 wopr kernel: Ebtables v2.0 registered
May 15 17:25:33 wopr kernel: bridge: filtering via arp/ip/ip6tables is no 
longer available by default. Update your scripts to load br_netfilter if you 
need this.
May 15 17:25:33 wopr kernel: virbr0: port 1(virbr0-nic) entered blocking state
May 15 17:25:33 wopr kernel: virbr0: port 1(virbr0-nic) entered disabled state
May 15 17:25:33 wopr kernel: device virbr0-nic entered promiscuous mode
May 15 17:25:33 wopr kernel: nf_conntrack version 0.5.0 (65536 buckets, 262144 
max)
May 15 17:25:33 wopr kernel: virbr0: port 1(virbr0-nic) entered blocking state
May 15 17:25:33 wopr kernel: virbr0: port 1(virbr0-nic) entered listening state
May 15 17:25:33 wopr kernel: virbr0: port 1(virbr0-nic) entered disabled state


Thanks

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

Title:
  zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

Status in Linux:
  New
Status in zfs-linux package in Ubuntu:
  Incomplete
Status in zfs-linux source package in Bionic:
  New

Bug description:
  Same as bug 1861228 but with a newer kernel installed.

  [  790.702566] VERIFY(size != 0) failed
  [  790.702590] PANIC at range_tree.c:304:range_tree_find_impl()
  [  790.702611] Showing stack for process 28685
  [  790.702614] CPU: 17 PID: 28685 Comm: receive_writer Tainted: P   O 
4.15.0-76-generic #86-Ubuntu
  [  790.702615] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 
2.0 12/17/2015
  [  790.702616] Call Trace:
  [  790.702626]  dump_stack+0x6d/0x8e
  [  790.702637]  spl_dumpstack+0x42/0x50 [spl]
  [  790.702640]  spl_panic+0xc8/0x110 [spl]
  [  790.702645]  ? __switch_to_asm+0x41/0x70
  [  790.702714]  ? arc_prune_task+0x1a/0x40 [zfs]
  [  790.702740]  ? dbuf_dirty+0x43d/0x850 [zfs]
  [  790.702745]  ? getrawmonotonic64+0x43/0xd0
  [  790.702746]  ? getrawmonotonic64+0x43/0xd0
  [  790.702775]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702778]  ? getrawmonotonic64+0x43/0xd0
  [  790.702805]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702807]  ? mutex_lock+0x12/0x40
  [  790.702833]  ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs]
  [  790.702866]  range_tree_find_impl+0x88/0x90 [zfs]
  [  790.702870]  ? spl_kmem_zalloc+0xdc/0x1a0 [spl]
  [  790.702902]  range_tree_clear+0x4f/0x60 [zfs]
  [  790.702930]  dnode_free_range+0x11f/0x5a0 [zfs]
  [  790.702957]  dmu_object_free+0x53/0x90 [zfs]
  [  790.702983]  dmu_free_long_object+0x9f/0xc0 [zfs]
  [  790.703010]  receive_freeobjects.isra.12+0x7a/0x100 [zfs]
  [  790.703036]  receive_writer_thread+0x6d2/0xa60 [zfs]
  [  790.703040]  ? set_curr_task_fair+0x2b/0x60
  [  790.703043]  ? spl_kmem_free+0x33/0x40 [spl]
  [  790.703048]  ? kfree+0x165/0x180
  [  790.703073]  ? receive_free.isra.13+0xc0/0xc0 [zfs]
  [  790.703078]  thread_generic_wrapper+0x74/0x90 [spl]
  [  790.703081]  kthread+0x121/0x140
  [  790.703084]  ? __thread_exit+0x20/0x20 [spl]
  [  790.703085]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  790.703088]  ret_from_fork+0x35/0x40
  [  967.636923] INFO: task txg_quiesce:14810 blocked for more than 120 seconds.
  [  967.636979]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
  [  967.637024] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.637076] txg_quiesce D0 14810  2 0x8000
  [  967.637080] Call Trace:
  [  967.637089]  

[Kernel-packages] [Bug 1876847] Re: HP-Spectre 2019 Intel wireless driver is detected incorrectly.

[You-Sheng Yang]

** Tags added: hwe-networking-wifi

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

Title:
  HP-Spectre 2019 Intel wireless driver is detected incorrectly.

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Output of lsb_release -rd,
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  Issue:
  I have Intel AX-201 for wireless but when i do "lspci -k", the driver is 
detected as "Intel-9462". When i did "journalctl -k | grep iwlwifi", it shows 
that the wireless driver detected is "Intel AX-201".

  Output of lspci -k,
  00:14.3 Network controller: Intel Corporation Wireless-AC 9462
   Subsystem: Intel Corporation Wireless-AC 9462
   Kernel driver in use: iwlwifi
   Kernel modules: iwlwifi

  Output of journalctl -k | grep iwlwifi,
  May 04 23:20:12 kernel: iwlwifi :00:14.3: enabling device ( -> 0002)
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuZ-a0-hr-b0-50.ucode failed with error -2
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuZ-a0-hr-b0-49.ucode failed with error -2
  May 04 23:20:12 kernel: iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ 
Version: 43.2.23.17
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug destination: 
EXTERNAL_DRAM
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug configuration: 0
  May 04 23:20:12 kernel: iwlwifi :00:14.3: loaded firmware version 
48.4fa0041f.0 op_mode iwlmvm
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX201 
160MHz, REV=0x354
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Allocated 0x0040 bytes for 
firmware monitor.
  May 04 23:20:12 kernel: iwlwifi :00:14.3: base HW address: 
7c:b2:7d:d0:d5:95
  May 04 23:20:12 kernel: iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0
  May 04 23:20:13 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
  May 04 23:20:13 kernel: iwlwifi :00:14.3: FW already configured (0) - 
re-configuring

  In the additional drivers module, it shows that module Intel-9462 no
  longer works. My bluetooth is also not detected and doesn't work.

  I came across this but no else responded yet. So decided to report a bug here.
  
https://askubuntu.com/questions/1232224/intel-ax201-detected-as-ac9462-wifi-connectivity-problems

  Please let me know if any more information is required.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  srikar 1447 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-03 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP HP Spectre x360 Convertible 15-df1xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=8d5d378c-648e-4355-8c1c-10cb298b2677 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:
   1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 863F
  dmi.board.vendor: HP
  dmi.board.version: 54.23
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.20:bd11/29/2019:svnHP:pnHPSpectrex360Convertible15-df1xxx:pvr:rvnHP:rn863F:rvr54.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-df1xxx
  dmi.product.sku: 7UT64UA#ABA
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1879010] [NEW] Bluetooth speaker defaults to lower quality (HSP/HFP) instead of higher quality (A2DP) sink

[Chris S.]

Public bug reported:

This seems identical to this bug:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046, but was
suggested to open a new bug as the other one was closed.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluez 5.53-0ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri May 15 16:13:24 2020
InstallationDate: Installed on 2020-05-06 (9 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. XPS 13 9300
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=21f0214d-8c30-4e9b-bf3b-1b3576c64628 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/26/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.7
dmi.board.name: 077Y9N
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd02/26/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9300
dmi.product.sku: 096D
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 54:8D:5A:D8:BA:43  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1126282 acl:178 sco:0 events:156624 errors:0
TX bytes:130927152 acl:152574 sco:8 commands:3326 errors:0

** Affects: bluez (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 bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1879010

Title:
  Bluetooth speaker defaults to lower quality (HSP/HFP) instead of
  higher quality (A2DP) sink

Status in bluez package in Ubuntu:
  New

Bug description:
  This seems identical to this bug:
  https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046, but was
  suggested to open a new bug as the other one was closed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 15 16:13:24 2020
  InstallationDate: Installed on 2020-05-06 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9300
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=21f0214d-8c30-4e9b-bf3b-1b3576c64628 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 077Y9N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd02/26/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 54:8D:5A:D8:BA:43  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1126282 acl:178 sco:0 events:156624 errors:0
TX bytes:130927152 acl:152574 sco:8 commands:3326 errors:0

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

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

[Kernel-packages] [Bug 1861009] Re: Asus Zenbook Flip 15 ux563fd no sound

[Driuchatyi Nikolay]

I've managed to get sound on this laptop. Please have a look:
https://bugzilla.kernel.org/show_bug.cgi?id=206589#c2

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

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

Title:
  Asus Zenbook Flip 15 ux563fd no sound

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bought a new laptop for a couple weeks ago and want to have a dual
  boot with W10 and Linux like my older one. First, I installed Ubuntu
  18.04 and tried to make sound working via the speakers. I tried
  alsamixer, made sure everything was on OO, reinstalled both alsamixer
  and pulseaudio couple times, checked permissions on the config of
  pulseaudio and more what could fix it in regular terms including
  installing and replacing kernels older and new ones. As a last option,
  I installed version 19.10 from Ubuntu as someone mentioned that the
  higher version could fix it because of the different supported
  packages but is not resolving it.

  Nothing of the above mentioned things where fixing it, but I still see
  some movement at streaming bar in the sound option menu when I'm
  playing some music. I hope there is a workaround for this issue, I
  just found the whole Zenbook laptop line that has this problem so I
  really hope for a solution to this.

  Version - kernel: Ubuntu 5.3.0-26.28-generic 5.3.13

  lspci -vnvn

  00:00.0 Host bridge [0600]: Intel Corporation Device [8086:9b61] (rev 0c)
Subsystem: ASUSTeK Computer Inc. Device [1043:1b31]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

  00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:9b41] (rev 02) (prog-if 00 [VGA controller])
DeviceName: VGA
Subsystem: ASUSTeK Computer Inc. Device [1043:1b31]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
 AtomicOpsCtl: ReqEn-
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00018  Data: 
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max PASID Width: 14
PASIDCtl: Enable- Exec- Priv-
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] Page Request Interface (PRI)
PRICtl: Enable- Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 8000, Page Request Allocation: 

Kernel driver in use: i915
Kernel modules: i915

  00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 0c)
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v5/E3-1500 v5/6th Gen 
Core Processor Thermal Subsystem [1043:1b31]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

  00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / 
E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [8086:1911]
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v5/v6 / E3-1500 v5 / 
6th/7th Gen Core Processor Gaussian Mixture Model [1043:1b31]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- 

[Kernel-packages] [Bug 1878782] Re: Bluetooth is on but scanned devices are not showing.

[Sebastien Bacher]

** Package changed: alsa-driver (Ubuntu) => bluez (Ubuntu)

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

Title:
  Bluetooth is on but scanned devices are not showing.

Status in bluez package in Ubuntu:
  New

Bug description:
  Bluetooth in spite of being switched on, shows the same image as when
  it is off in the paired devices menu. I cannot access my paired
  devices.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dashtrox   1582 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 15 13:48:16 2020
  InstallationDate: Installed on 2020-05-12 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 1TCN27WW(V2.08)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr1TCN27WW(V2.08):bd07/06/2018:svnLENOVO:pn80UD:pvrLenovoideapad110-15ISK:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad110-15ISK:
  dmi.product.family: ideapad 110-15ISK
  dmi.product.name: 80UD
  dmi.product.sku: LENOVO_MT_80UD_BU_idea_FM_ideapad 110-15ISK
  dmi.product.version: Lenovo ideapad 110-15ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1878782] [NEW] Bluetooth is on but scanned devices are not showing.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Bluetooth in spite of being switched on, shows the same image as when it
is off in the paired devices menu. I cannot access my paired devices.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dashtrox   1582 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri May 15 13:48:16 2020
InstallationDate: Installed on 2020-05-12 (2 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: Bluetooth sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/06/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 1TCN27WW(V2.08)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 110-15ISK
dmi.modalias: 
dmi:bvnLENOVO:bvr1TCN27WW(V2.08):bd07/06/2018:svnLENOVO:pn80UD:pvrLenovoideapad110-15ISK:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad110-15ISK:
dmi.product.family: ideapad 110-15ISK
dmi.product.name: 80UD
dmi.product.sku: LENOVO_MT_80UD_BU_idea_FM_ideapad 110-15ISK
dmi.product.version: Lenovo ideapad 110-15ISK
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal
-- 
Bluetooth is on but scanned devices are not showing.
https://bugs.launchpad.net/bugs/1878782
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to bluez in Ubuntu.

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

[Kernel-packages] [Bug 1870995] Re: i8042: Warning: Keylock active

[Sebastien Bacher]

Thank you for your bug report, the warning is from the kernel,
reassigning

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

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

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

Title:
  i8042: Warning: Keylock active

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I see "i8042: Warning: Keylock active" in my dmesg.  Since this is a
  warning, I get, ergo, warned.  Well, about what do I get warned?  I
  feel warned, but I don't know what's wrong and what do I have to avoid
  doing so that I don't get into trouble.  Is there an issue there that
  needs to be solved?

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

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

[Kernel-packages] [Bug 1862080] Re: [MS-7B51, Nvidia GPU 94 HDMI/DP, Digital Out, HDMI] No sound at all

[Sebastien Bacher]

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

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

Title:
  [MS-7B51, Nvidia GPU 94 HDMI/DP, Digital Out, HDMI] No sound at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  If I use xserver-xorg-video-nouveau/focal,now 1:1.0.16-1 amd64
  there is no sound on Display port.
  My graphic card is GTX 1650. 

  Please see bug 1859096. It work with 440 nvidia driver 
  but I want to use Nouveau driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Feb  5 23:50:39 2020
  InstallationDate: Installed on 2020-01-05 (31 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200104)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
  Symptom_Card: HDA NVidia - HDA NVidia
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [MS-7B51, Nvidia GPU 94 HDMI/DP, Digital Out, HDMI] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.50
  dmi.board.asset.tag: Default string
  dmi.board.name: MPG Z390 GAMING PLUS (MS-7B51)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.50:bd02/21/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B51:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ390GAMINGPLUS(MS-7B51):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7B51
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Kernel-packages] [Bug 1870995] [NEW] i8042: Warning: Keylock active

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I see "i8042: Warning: Keylock active" in my dmesg.  Since this is a
warning, I get, ergo, warned.  Well, about what do I get warned?  I feel
warned, but I don't know what's wrong and what do I have to avoid doing
so that I don't get into trouble.  Is there an issue there that needs to
be solved?

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

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

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

[Kernel-packages] [Bug 1862080] [NEW] [MS-7B51, Nvidia GPU 94 HDMI/DP, Digital Out, HDMI] No sound at all

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

$ lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:20.04

If I use xserver-xorg-video-nouveau/focal,now 1:1.0.16-1 amd64
there is no sound on Display port.
My graphic card is GTX 1650. 

Please see bug 1859096. It work with 440 nvidia driver 
but I want to use Nouveau driver.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: MATE
Date: Wed Feb  5 23:50:39 2020
InstallationDate: Installed on 2020-01-05 (31 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
Symptom_Card: HDA NVidia - HDA NVidia
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [MS-7B51, Nvidia GPU 94 HDMI/DP, Digital Out, HDMI] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/21/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.50
dmi.board.asset.tag: Default string
dmi.board.name: MPG Z390 GAMING PLUS (MS-7B51)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.50:bd02/21/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B51:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ390GAMINGPLUS(MS-7B51):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: Default string
dmi.product.name: MS-7B51
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


** Tags: amd64 apport-bug focal
-- 
[MS-7B51, Nvidia GPU 94 HDMI/DP, Digital Out, HDMI] No sound at all
https://bugs.launchpad.net/bugs/1862080
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1878990] [NEW] Eoan update: upstream stable patchset 2020-05-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-05-15

Ported from the following upstream stable releases:
v4.19.120, v5.4.37
   v5.4.38

   from git://git.kernel.org/

remoteproc: Fix wrong rvring index computation
usb: dwc3: gadget: Do link recovery for SS and SSP
usb: gadget: udc: bdc: Remove unnecessary NULL checks in bdc_req_complete
iio:ad7797: Use correct attribute_group
ASoC: q6dsp6: q6afe-dai: add missing channels to MI2S DAIs
ASoC: tas571x: disable regulators on failed probe
ASoC: wm8960: Fix wrong clock after suspend & resume
nfsd: memory corruption in nfsd4_lock()
i2c: altera: use proper variable to hold errno
rxrpc: Fix DATA Tx to disable nofrag for UDP on AF_INET6 socket
net/cxgb4: Check the return from t4_query_params properly
xfs: acquire superblock freeze protection on eofblocks scans
svcrdma: Fix trace point use-after-free race
svcrdma: Fix leak of svc_rdma_recv_ctxt objects
PCI: Move Apex Edge TPU class quirk to fix BAR assignment
ARM: dts: bcm283x: Disable dsi0 node
cpumap: Avoid warning when CONFIG_DEBUG_PER_CPU_MAPS is enabled
net/mlx5: Fix failing fw tracer allocation on s390
perf/core: fix parent pid/tid in task exit events
bpf, x86_32: Fix incorrect encoding in BPF_LDX zero-extension
mm: shmem: disable interrupt when acquiring info->lock in userfaultfd_copy path
xfs: clear PF_MEMALLOC before exiting xfsaild thread
bpf, x86: Fix encoding for lower 8-bit registers in BPF_STX BPF_B
net: fec: set GPR bit on suspend by DT configuration.
x86: hyperv: report value of misc_features
xfs: fix partially uninitialized structure in xfs_reflink_remap_extent
ALSA: hda: Keep the controller initialization even if no codecs found
ALSA: hda: Explicitly permit using autosuspend if runtime PM is supported
scsi: target: fix PR IN / READ FULL STATUS for FC
scsi: target: tcmu: reset_ring should reset TCMU_DEV_BIT_BROKEN
objtool: Fix CONFIG_UBSAN_TRAP unreachable warnings
objtool: Support Clang non-section symbols in ORC dump
xen/xenbus: ensure xenbus_map_ring_valloc() returns proper grant status
ALSA: hda: call runtime_allow() for all hda controllers
arm64: Delete the space separator in __emit_inst
ext4: use matching invalidatepage in ext4_writepage
ext4: increase wait time needed before reuse of deleted inode numbers
ext4: convert BUG_ON's to WARN_ON's in mballoc.c
hwmon: (jc42) Fix name to have no illegal characters
bpf, x86_32: Fix clobbering of dst for BPF_JSET
qed: Fix use after free in qed_chain_free
ext4: check for non-zero journal inum in ext4_calculate_overhead
ubifs: Fix ubifs_tnc_lookup() usage in do_kill_orphans()
printk: queue wake_up_klogd irq_work only if per-CPU areas are ready
ASoC: stm32: sai: fix sai probe
kbuild: fix DT binding schema rule again to avoid needless rebuilds
usb: gadget: udc: atmel: Fix vbus disconnect handling
afs: Make record checking use TASK_UNINTERRUPTIBLE when appropriate
afs: Fix to actually set AFS_SERVER_FL_HAVE_EPOCH
counter: 104-quad-8: Add lock guards - generic interface
s390/ftrace: fix potential crashes when switching tracers
drivers: soc: xilinx: fix firmware driver Kconfig dependency
bpf: Forbid XADD on spilled pointers for unprivileged users
net/mlx5e: Don't trigger IRQ multiple times on XSK wakeup to avoid WQ overruns
net/mlx5e: Get the latest values from counters in switchdev mode
PCI: Add ACS quirk for Zhaoxin multi-function devices
PCI: Make ACS quirk implementations more uniform
PCI: Unify ACS quirk desired vs provided checking
PCI: Add Zhaoxin Vendor ID
PCI: Add ACS quirk for Zhaoxin Root/Downstream Ports
s390/pci: do not set affinity for floating irqs
sched/core: Fix reset-on-fork from RT with uclamp
netfilter: nat: fix error handling upon registering inet hook
PM: sleep: core: Switch back to async_schedule_dev()
um: ensure `make ARCH=um mrproper` removes arch/$(SUBARCH)/include/generated/
bpf, x86_32: Fix logic error in BPF_LDX zero-extension
libbpf: Initialize *nl_pid so gcc 10 is happy
signal: check sig before setting info in kill_pid_usb_asyncio
afs: Fix length of dump of bad YFSFetchStatus record
ALSA: hda: Release resources at error in delayed probe
net: stmmac: socfpga: Allow all RGMII modes
mac80211: fix channel switch trigger from unknown mesh peer
blk-mq: Put driver tag in blk_mq_dispatch_rq_list() when no budget
qed: Fix race condition between scheduling and destroying the slowpath workqueue
Crypto: chelsio - Fixes a hang issue during driver registration
net: use indirect call wrappers for 

[Kernel-packages] [Bug 1878976] [NEW] Rebuild linux-raspi kernel snaps against new initrd and gate it with QA to unbreak PiFi

[Dimitri John Ledkov]

Public bug reported:

Rebuild linux-raspi kernel snaps against new initrd and gate it with QA

[Next Tasks]

1) Please change 
https://launchpad.net/~canonical-kernel-snaps/+snap/pi-kernel--uc20 publication 
channels:
from
20/beta 20/edge

to
20/edge

I.e. remove the beta risk level via the API  NB!!!

$ lp-shell
snap = lp.load('~canonical-kernel-snaps/+snap/pi-kernel--uc20') 
snap.store_channels = ['20/edge']
sanp.lp_save()


2) Trigger rebuild of 
https://launchpad.net/~canonical-kernel-snaps/+snap/pi-kernel--uc20 such that 
it is rebuild against ubuntu-core-initramfs 36

3) Notify when above is publised in 20/edge channel only

[BLOCKED]

4) [release team] => trigger respin of dangerous & edge channels of core
for UC20 (DIST=focal)

5) [ijonson|cert|cwayne] test dangerous pi image in the lab; or edge pi
image locally

6) [release team] If pifi works, kernel team is notified to promote pi-
kernel snap from 20/edge to 20/beta

7) [kernel team] promotes pi-kernel from 20/edge to 20/beta

8) [release team] respins 20/beta image

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


** Tags: core20 uc20

** Summary changed:

- Rebuild linux-raspi kernel snaps against new initrd and gate it with QA
+ Rebuild linux-raspi kernel snaps against new initrd and gate it with QA to 
unbreak PiFi

** Tags added: core20

** Tags added: uc20

** Description changed:

  Rebuild linux-raspi kernel snaps against new initrd and gate it with QA
  
  [Next Tasks]
  
  1) Please change 
https://launchpad.net/~canonical-kernel-snaps/+snap/pi-kernel--uc20 publication 
channels:
  from
  20/beta 20/edge
  
- to 
+ to
  20/edge
  
  I.e. remove the beta risk level via the API  NB!!!
  
- 2) Trigger rebuild of https://launchpad.net/~canonical-kernel-
- snaps/+snap/pi-kernel--uc20 such that it is rebuild against ubuntu-core-
- initramfs 36
+ $ lp-shell
+ snap = lp.load('~canonical-kernel-snaps/+snap/pi-kernel--uc20') 
+ snap.store_channels = ['20/edge']
+ sanp.lp_save()
+ 
+ 
+ 2) Trigger rebuild of 
https://launchpad.net/~canonical-kernel-snaps/+snap/pi-kernel--uc20 such that 
it is rebuild against ubuntu-core-initramfs 36
  
  3) Notify when above is publised in 20/edge channel only
- 
  
  [BLOCKED]
  
  4) [release team] => trigger respin of dangerous & edge channels of core
  for UC20 (DIST=focal)
  
  5) [ijonson|cert|cwayne] test dangerous pi image in the lab; or edge pi
  image locally
  
  6) [release team] If pifi works, kernel team is notified to promote pi-
  kernel snap from 20/edge to 20/beta
  
  7) [kernel team] promotes pi-kernel from 20/edge to 20/beta
  
  8) [release team] respins 20/beta image

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

Title:
  Rebuild linux-raspi kernel snaps against new initrd and gate it with
  QA to unbreak PiFi

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  Rebuild linux-raspi kernel snaps against new initrd and gate it with
  QA

  [Next Tasks]

  1) Please change 
https://launchpad.net/~canonical-kernel-snaps/+snap/pi-kernel--uc20 publication 
channels:
  from
  20/beta 20/edge

  to
  20/edge

  I.e. remove the beta risk level via the API  NB!!!

  $ lp-shell
  snap = lp.load('~canonical-kernel-snaps/+snap/pi-kernel--uc20') 
  snap.store_channels = ['20/edge']
  sanp.lp_save()

  
  2) Trigger rebuild of 
https://launchpad.net/~canonical-kernel-snaps/+snap/pi-kernel--uc20 such that 
it is rebuild against ubuntu-core-initramfs 36

  3) Notify when above is publised in 20/edge channel only

  [BLOCKED]

  4) [release team] => trigger respin of dangerous & edge channels of
  core for UC20 (DIST=focal)

  5) [ijonson|cert|cwayne] test dangerous pi image in the lab; or edge
  pi image locally

  6) [release team] If pifi works, kernel team is notified to promote
  pi-kernel snap from 20/edge to 20/beta

  7) [kernel team] promotes pi-kernel from 20/edge to 20/beta

  8) [release team] respins 20/beta image

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

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

[Kernel-packages] [Bug 1878670] Re: Gnome crash frequently

[Kurt Aaholst]

Hi,

Thanks for the fast responses.

I have tried to collect the requested information but:

1) There are no files in /var/crash

2) The only item in https://errors.ubuntu.com/user/8dfc634ec... is:
2020-04-28 23:042020-04-28 21:04 UTCCrash   google-chrome-stable
https://errors.ubuntu.com/oops/6c75c4c0-8996-11ea-a340-fa163e6cac46

3) I commented out line23 :"'problem_types': ['Bug', 'Package']," from
/etc/apport/crashdb.conf, rebooted and managed to reproduce the crash.
(it's not easily reproducible, or at least I haven't found out how to
reliably reproduce). But still no files in var/crash.

I also tried "apport-collect 1878670" (with and without sudo):

kaa@kaa-XPS-13-9300:~$ apport-collect 1878670
ERROR: The python3-launchpadlib package is not installed. This functionality is 
not available.
kaa@kaa-XPS-13-9300:~$ sudo apt list python3-launchpadlib
Listing... Færdig
python3-launchpadlib/bionic,bionic,now 1.10.6-1 all [Installeret]

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

Title:
  Gnome crash frequently

Status in OEM Priority Project:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  The system freezes frequently then logs out.
  If happens at apparently random times, and using no particular app.

  Extract of syslog is attached.

  Requested info is below:

  1) release
  Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30)

  2) package version
  gnome-session:
Installeret: (ingen)
Kandidat:3.28.1-0ubuntu3
Versionstabel:
   3.28.1-0ubuntu3 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
   3.28.1-0ubuntu2 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) Gnome shouldn't crash

  4) Gnome crashed

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

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

[Kernel-packages] [Bug 1501972] Re: nvidia kernel module failed to build [/bin/sh: 1: cc: not found]

[Ken Sharp]

"Fix:
sudo apt install -y --reinstall gcc g++ gcc-7 g++-7"

How on Earth is that a fix? Does an updated package do this for you? I'm
doubting it very much.

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

Title:
  nvidia kernel module failed to build [/bin/sh: 1: cc: not found]

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-352 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-352-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  I really have no idea of this issue, i just booted up and ubuntu
  notified me that there was a problem... hopefully ubuntu is self
  reporting enough information.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-346 346.96-0ubuntu0.0.1
  ProcVersionSignature: Ubuntu 3.19.0-30.33~14.04.1-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-65-generic
  Date: Thu Oct  1 18:17:00 2015
  InstallationDate: Installed on 2015-09-25 (6 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageVersion: 346.96-0ubuntu0.0.1
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: nvidia-graphics-drivers-346
  Title: nvidia-346 346.96-0ubuntu0.0.1: nvidia-346 kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia.346.hybrid.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1501972/+subscriptions

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

[Kernel-packages] [Bug 1690085]

[stellicht]

Hi folks again!

I have been testing the new AGESA 1.0.0.4 these days. Currently my
uptime is reaching 3days+, which was impossible before - the system
always hangs within 2 days. Hence I consider the new firmware indeed
solved this Soft Lock issue!

I'm testing on Ubuntu Focal, acpi related settings are all left default.
On my Asus PRIME B350M, default optimised settings are being used.

In addition, the CPU C6 State seems also normal, during idle, CPU enters
its idle state with very low power consumption (measured externally).
k10temp reports Vcore 850mV(approx.).

>Thank you for the clarification. Though I am confused now, as I thought you
>could use Zen2 devices in “Zen+ boards” (boards original for Zen+). So, AGESA
>1.0.0.4 for Zen2 also support the predecessor generation?

It seems that to address to this versioning mess, AMD claims that this
1.0.0.4 release reunited all architectures into one codebase.[1] I guess
they also "reunited" the version number. The AGESA was also 1.0.0.7 on
my motherboard  before.


---REFERENCES---
[1]: 
https://www.reddit.com/r/Amd/comments/dtgutp/an_update_on_the_am4_platform_agesa_1004/

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 

[Kernel-packages] [Bug 1877887] Re: [USB-Audio - Scarlett 2i2 USB, playback] fails after a while

[Kai-Heng Feng]

Well, test an old kernel and we can know if it's a regression.

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

Title:
  [USB-Audio - Scarlett 2i2 USB, playback] fails after a while

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am encountering some very bizarre and difficult to reliably
  replicate issues.

  I am using a Focusrite Scarlett 2i2 USB audio interface, and am having
  a number of issues that I did not have in older version of ubuntu
  (these issues started occuring sometime in 19.04-19.10, can't remember
  which).

  I am having three major issues. Number one is, if USB autosuspend is
  enabled, it will stop working completely until reboot after anywhere
  from a few minutes to several hours. Reconnecting the device does not
  fix it and it seems to not power on at all, with dmesg reporting a
  "usb_set_interface failed -110" error. Sometimes this bug can be
  recreated by manually disconnecting and reconnecting the device,
  however I was unable to replicate it in this manner at the time of
  filing the bug.

  EDIT: Ignore the two more issue below, however I'm leaving them in the
  post in case they end up being relevant.

  Another (presumably related) issue I am having is that if I reconnect
  the device and it doesn't fail, it outputs very crackly audio, as if
  the bitrate or sample rate were set incorrectly. This persists until a
  restart of pulseaudio. Previously, I had a similar bug where it would
  randomly start doing the crackly audio thing until reconnecting the
  device and in this case a restart of pulse did *not* fix the problem.
  I am unsure if this issue still happens as it was fairly rare.

  The third problem is that sometimes when performing a suspend/wake
  cycle, the interface will power cycle several times, in intervals of
  15-30 seconds or so before staying on properly.

  As previously mentioned, these issues are fairly new and did not occur
  in older versions of ubuntu. I have confirmed that the audio interface
  works fine under windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun May 10 14:09:28 2020
  InstallationDate: Installed on 2020-05-08 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: USB-Audio - microKEY-37
  Symptom_PulseAudioLog:

  Symptom_Type: Sound works for a while, then breaks
  Title: [USB-Audio - Scarlett 2i2 USB, playback] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-08 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   enp37s0   no wireless extensions.

   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=UUID=6108192f-9dc3-480d-9a32-517609064dcd ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:

  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:

  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be 

[Kernel-packages] [Bug 1878138] Re: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822] problemas

[You-Sheng Yang]

[   11.000439] rtw_pci :03:00.0: failed to poll offset=0x5 mask=0x2 
value=0x0
[   11.000444] rtw_pci :03:00.0: mac power on failed
[   11.000446] rtw_pci :03:00.0: failed to power on mac

Can you remove all other out of tree drivers and test again?

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

Title:
  Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822] problemas

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Mi servicio de wifi no funciona bien de deshabilita sola

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yesid  2249 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 00:30:50 2020
  InstallationDate: Installed on 2019-11-21 (172 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: ASUSTeK COMPUTER INC. X405UA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-11 (0 days ago)
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X405UA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X405UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX405UA.203:bd05/05/2017:svnASUSTeKCOMPUTERINC.:pnX405UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX405UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X405UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1878138] Re: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822] problemas

[You-Sheng Yang]

** Summary changed:

- wifi problemas  rtlbe8822be
+ Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822] problemas

** Tags added: hwe-networking-wifi

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

Title:
  Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822] problemas

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Mi servicio de wifi no funciona bien de deshabilita sola

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yesid  2249 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 00:30:50 2020
  InstallationDate: Installed on 2019-11-21 (172 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: ASUSTeK COMPUTER INC. X405UA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-11 (0 days ago)
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X405UA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X405UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX405UA.203:bd05/05/2017:svnASUSTeKCOMPUTERINC.:pnX405UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX405UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X405UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1878670] Re: Gnome crash frequently

[You-Sheng Yang]

Probably a duplicate of bug 1872001.

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

Title:
  Gnome crash frequently

Status in OEM Priority Project:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  The system freezes frequently then logs out.
  If happens at apparently random times, and using no particular app.

  Extract of syslog is attached.

  Requested info is below:

  1) release
  Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30)

  2) package version
  gnome-session:
Installeret: (ingen)
Kandidat:3.28.1-0ubuntu3
Versionstabel:
   3.28.1-0ubuntu3 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
   3.28.1-0ubuntu2 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) Gnome shouldn't crash

  4) Gnome crashed

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

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

[Kernel-packages] [Bug 1870559] Re: Kernel NULL pointer dereference while receiving zfs snapshots

[Colin Ian King]

Marking it as invalid. Fee free to re-open this bug if it occurs again.

** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1870559

Title:
  Kernel NULL pointer dereference while receiving zfs snapshots

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I was transferring my zfs snapshots to the backup server, when
  suddenly it stalled. I checked dmesg on the server and found a "kernel
  bug" entry.

  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
  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-0ubuntu22
  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/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Fri Apr  3 14:48:19 2020
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=7934268a-8e6f-11e8-828e-00133b1029de ro mitigations=off maybe-ubiquity
  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'
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-01-19 (75 days ago)
  dmi.bios.date: 12/23/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0214
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5LD2-X/1333
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: Rev 1.xx
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0214:bd12/23/2008:svnSystemmanufacturer:pnSystemProductName:pvrRev1.xx:rvnASUSTeKComputerINC.:rnP5LD2-X/1333:rvrRevx.xx:cvnASUSTekComputerINC.:ct3:cvrRev1.xx:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: Rev 1.xx
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1878480] Re: Centrino Wireless-N 1000 [Condor Peak]

[You-Sheng Yang]

** Tags added: hwe-networking-wifi

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

Title:
  Centrino Wireless-N 1000 [Condor Peak]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to 20.04 my wireless starts to be very unstable, it goes
  from 65mbs to 1mbs. I need to reenable wirless

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-generic 5.4.0.29.34
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  miguel 2846 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 13 20:57:07 2020
  HibernationDevice: RESUME=UUID=0f71c458-758c-439d-9dd0-b7ddcd620218
  MachineType: Alienware M14xR1
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=fcba8370-4563-4d59-8a53-f1a70ebb8e1d ro quiet splash 
nouveau.blacklist=1 nvidia-drm.modeset=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2011
  dmi.bios.vendor: Alienware
  dmi.bios.version: A08
  dmi.board.name: M14xR1
  dmi.board.vendor: Alienware
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnAlienware:bvrA08:bd12/24/2011:svnAlienware:pnM14xR1:pvrA08:rvnAlienware:rnM14xR1:rvrA08:cvnAlienware:ct8:cvrA08:
  dmi.product.family: 103C_5335KV
  dmi.product.name: M14xR1
  dmi.product.sku: xxx123x#ABA
  dmi.product.version: A08
  dmi.sys.vendor: Alienware

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

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

[Kernel-packages] [Bug 1870559] Re: Kernel NULL pointer dereference while receiving zfs snapshots

[Andreas Hasenack]

I marked it incomplete so it will expire on its own if there is no new
information, but feel free to actually close it if you prefer ("invalid"
is fine).

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

Title:
  Kernel NULL pointer dereference while receiving zfs snapshots

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I was transferring my zfs snapshots to the backup server, when
  suddenly it stalled. I checked dmesg on the server and found a "kernel
  bug" entry.

  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
  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-0ubuntu22
  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/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Fri Apr  3 14:48:19 2020
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=7934268a-8e6f-11e8-828e-00133b1029de ro mitigations=off maybe-ubiquity
  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'
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-01-19 (75 days ago)
  dmi.bios.date: 12/23/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0214
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5LD2-X/1333
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: Rev 1.xx
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0214:bd12/23/2008:svnSystemmanufacturer:pnSystemProductName:pvrRev1.xx:rvnASUSTeKComputerINC.:rnP5LD2-X/1333:rvrRevx.xx:cvnASUSTekComputerINC.:ct3:cvrRev1.xx:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: Rev 1.xx
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1870559] Re: Kernel NULL pointer dereference while receiving zfs snapshots

[Andreas Hasenack]

+1, this is not like sarnold's crash-with-every-snapshot-send


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

Title:
  Kernel NULL pointer dereference while receiving zfs snapshots

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I was transferring my zfs snapshots to the backup server, when
  suddenly it stalled. I checked dmesg on the server and found a "kernel
  bug" entry.

  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
  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-0ubuntu22
  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/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Fri Apr  3 14:48:19 2020
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=7934268a-8e6f-11e8-828e-00133b1029de ro mitigations=off maybe-ubiquity
  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'
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-01-19 (75 days ago)
  dmi.bios.date: 12/23/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0214
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5LD2-X/1333
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: Rev 1.xx
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0214:bd12/23/2008:svnSystemmanufacturer:pnSystemProductName:pvrRev1.xx:rvnASUSTeKComputerINC.:rnP5LD2-X/1333:rvrRevx.xx:cvnASUSTekComputerINC.:ct3:cvrRev1.xx:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: Rev 1.xx
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1870559] Re: Kernel NULL pointer dereference while receiving zfs snapshots

[Colin Ian King]

Considering it is a rare issue that does not seem to be reproducible,
perhaps it may be a spurious corruption issue of some sort. I've not
seen any similar bug reports against ZFS so it is a curious issue.

Perhaps we should close this bug and re-open it if you hit it again.

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

Title:
  Kernel NULL pointer dereference while receiving zfs snapshots

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I was transferring my zfs snapshots to the backup server, when
  suddenly it stalled. I checked dmesg on the server and found a "kernel
  bug" entry.

  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
  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-0ubuntu22
  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/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Fri Apr  3 14:48:19 2020
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=7934268a-8e6f-11e8-828e-00133b1029de ro mitigations=off maybe-ubiquity
  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'
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-01-19 (75 days ago)
  dmi.bios.date: 12/23/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0214
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5LD2-X/1333
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: Rev 1.xx
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0214:bd12/23/2008:svnSystemmanufacturer:pnSystemProductName:pvrRev1.xx:rvnASUSTeKComputerINC.:rnP5LD2-X/1333:rvrRevx.xx:cvnASUSTekComputerINC.:ct3:cvrRev1.xx:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: Rev 1.xx
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1878271] Re: rpi: no uboot or kernel boot mesages on console during boot on core20

[Paul Larson]

** Tags added: uc20

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

Title:
  rpi: no uboot or kernel boot mesages on console during boot on core20

Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  I'm currently testing the image from http://cdimage.ubuntu.com/ubuntu-
  core/20/beta/20200512.3/ on rpi4-4GB. Normally, we would expect to see
  uboot prompt on screen, as well as kernel boot messages - as well as
  on serial. I see all of this coming over serial, but nothing on the
  screen until the system is completely booted.

  Current kernel version and snaps in this image are:
  $ uname -a
  Linux ubuntu 5.4.0-1011-raspi #11-Ubuntu SMP Fri May 8 07:43:33 UTC 2020 
aarch64 aarch64 aarch64 GNU/Linux

  $ snap list
  Name   VersionRev   Tracking Publisher   Notes
  core20 20 635   latest/beta  canonical✓  base
  pi 20-1   5820/beta  canonical✓  gadget
  pi-kernel  5.4.0-1011.11  154   20/beta  canonical✓  kernel
  snapd  2.45   7780  latest/beta  canonical✓  snapd

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

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

[Kernel-packages] [Bug 1071434] Re: /proc/cpuinfo doesn't support showing the correct Turbo Core frequency

[Bug Watch Updater]

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

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


On 2012-12-13T08:43:09+00:00 sworddragon2 wrote:

My AMD Phenom II X6 1045T has a normal maximum frequenzy of 2.7 GHz but
can boost up to 3 cores to 3.2 GHz if needed. My BIOS is showing
correctly 3.2 GHz as the maximum frequenzy. Here are some informations
about my system:

sworddragon@ubuntu:~$ uname -m
x86_64
sworddragon@ubuntu:~$ cat 
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
270 200 140 80 

I have written a script which uses 100% of cpu time for 1 core.
Theoretically this should force the processor to go up to 3.2 GHz on
this core. In the attachments is a log which shows the output from
/proc/cpuinfo and top which shows that my processor is still using just
2.7 GHz.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1071434/comments/29


On 2012-12-13T08:43:52+00:00 sworddragon2 wrote:

Created attachment 89081
Log of /proc/cpuinfo and top

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1071434/comments/30


On 2013-01-04T18:53:16+00:00 muziofg wrote:

I have two different AMD CPUs with turbo core feature enabled: a Phenom
II X6 1055T and a dualcore C-70

both have the same behaviour: if I read the frequency value from 
/sys/devices/system/cpu/*/cpufreq/* or /proc/cpuinfo I see the cores to never 
reach the "turbo" frequency. 
But the software cpufreq-aperf (found in the cpufrequtils package on a Debian 
system) can show me these peaks, expecially if I force 5 cores to powersave and 
1 on performance governor

for use cpuafreq-aper must be load the msr kernel module, I think the
Turbo frequency is an internal feature of a CPU, difficult to control
and monitor

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1071434/comments/33


On 2013-11-20T15:04:42+00:00 sworddragon2 wrote:

Thanks for the hint of cpufreq-aperf. Here are the results:

root@ubuntu:~# taskset -c 0 sh -c "./test.py & sleep 1 && cpufreq-aperf --once 
&& echo -- && cat /proc/cpuinfo | grep MHz && pkill ^test.py$"
CPU Average freq(KHz) Time in C0 Time in Cx C0 percentage
000 3186000 01 sec 005 ms 6832127434 sec 705 ms 100
001 0783000 00 sec 026 ms 00 sec 976 ms 02
002 0783000 00 sec 032 ms 00 sec 970 ms 03
003 0783000 00 sec 001 ms 01 sec 001 ms 00
004 0783000 00 sec 016 ms 00 sec 986 ms 01
005 0783000 00 sec 039 ms 00 sec 963 ms 03
--
cpu MHz : 2700.000
cpu MHz : 800.000
cpu MHz : 800.000
cpu MHz : 800.000
cpu MHz : 800.000
cpu MHz : 800.000


Turbo Core is working but /proc/cpuinfo doesn't support showing the correct 
frequency.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1071434/comments/54


On 2020-05-15T12:27:01+00:00 david wrote:

It's working on 4.19.0-9-amd64 Debian 10 kernel directly from
/proc/cpuinfo:

# cat /proc/cpuinfo |grep -i model
model   : 10
model name  : AMD Phenom(tm) II X6 1090T Processor

# cat /proc/cpuinfo |grep MHz
cpu MHz : 3528.820
cpu MHz : 831.966
cpu MHz : 893.121
cpu MHz : 800.173
cpu MHz : 1354.755
cpu MHz : 979.302
# cat /proc/cpuinfo |grep MHz
cpu MHz : 3505.403
cpu MHz : 834.381
cpu MHz : 1281.693
cpu MHz : 1555.635
cpu MHz : 1476.154
cpu MHz : 955.208

3600 MHz turbo core.

I think this bug can be closed as resolved.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1071434/comments/55


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

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

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

Title:
  /proc/cpuinfo doesn't support showing the correct Turbo Core frequency

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

Bug description:
  I'm using Ubuntu 12.10 (64 bit) and my AMD Phenom II X6 1045T doesn't
  boost from 2.7 GHz to 3.2 GHz if a core is using 100% of cpu time.

  sworddragon@ubuntu:~$ uname -a
  Linux ubuntu 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012 
x86_64 x86_64 x86_64 GNU/Linux

  sworddragon@ubuntu:~$ dmesg | grep powernow
  [ 1.204050] powernow-k8: Found 1 AMD Phenom(tm) II X6 1045T Processor (6 cpu 
cores) (version 2.20.00)
  [ 1.204074] 

[Kernel-packages] [Bug 1870559] Re: Kernel NULL pointer dereference while receiving zfs snapshots

[Andreas Hasenack]

Sorry, I mistook this for a comment on another zfs bug that I was
watching.


I haven't seen that crash again since the day I reported it. Since it's so rare 
(happened just once), do you think it's worth it to try the kernel from the 
ppa? I'd rather not stay away from the official focal kernel for long.

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

Title:
  Kernel NULL pointer dereference while receiving zfs snapshots

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I was transferring my zfs snapshots to the backup server, when
  suddenly it stalled. I checked dmesg on the server and found a "kernel
  bug" entry.

  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
  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-0ubuntu22
  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/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Fri Apr  3 14:48:19 2020
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=7934268a-8e6f-11e8-828e-00133b1029de ro mitigations=off maybe-ubiquity
  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'
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-01-19 (75 days ago)
  dmi.bios.date: 12/23/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0214
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5LD2-X/1333
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: Rev 1.xx
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0214:bd12/23/2008:svnSystemmanufacturer:pnSystemProductName:pvrRev1.xx:rvnASUSTeKComputerINC.:rnP5LD2-X/1333:rvrRevx.xx:cvnASUSTekComputerINC.:ct3:cvrRev1.xx:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: Rev 1.xx
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1877894] Re: "True Wireless" Bluetooth headsets not connecting in Ubuntu 20.04

[You-Sheng Yang]

Please do:

  1. reboot
  2. run `sudo btmon -w btsnoop.log` in a separate terminal,
  3. pair/connect your device once,
  4. when the connection disconnects, interrupt  the btmon log capture,
  5. run `journalctl -b > journal.log`,
  6. attach btsnoop.log and journal.log here as attachments

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

Title:
  "True Wireless" Bluetooth headsets not connecting in Ubuntu 20.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I upgraded my Ubuntu installation from 19.10 to 20.04 and I have lost
  the ability to connect to any kind of Bluetooth "True Wireless"
  earphones (Apple AirPods, Galaxy Earpods+, etc). Standard Bluetooth
  headphones connect correctly but all "True Wireless" style headphones
  briefly connect then disconnect immediately.

  bluetoothctl output:

  ```
  [bluetooth]# devices
  Device C0:28:8D:1D:42:90 Jaybird X3
  Device 7C:38:AD:4A:C8:F9 Galaxy Buds (C8F9)
  Device 40:26:19:DC:12:E6 Apple AirPods

  [bluetooth]# connect C0:28:8D:1D:42:90
  Attempting to connect to C0:28:8D:1D:42:90
  [CHG] Device C0:28:8D:1D:42:90 Connected: yes
  Connection successful

  [Jaybird X3]# connect 7C:38:AD:4A:C8:F9
  ttempting to connect to 7C:38:AD:4A:C8:F9
  [CHG] Device 7C:38:AD:4A:C8:F9 Connected: yes
  Failed to connect: org.bluez.Error.Failed

  Jaybird X3]# connect 40:26:19:DC:12:E6
  Attempting to connect to 40:26:19:DC:12:E6
  [CHG] Device 40:26:19:DC:12:E6 Connected: yes
  Failed to connect: org.bluez.Error.Failed

  [CHG] Device 40:26:19:DC:12:E6 Connected: no
  [CHG] Device 40:26:19:DC:12:E6 Connected: yes
  [CHG] Device 40:26:19:DC:12:E6 Connected: no

  [Jaybird X3]#

  ```


  ```
  $ lsb_release -rd

  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  ```

  possible packages involved:
  -pulseaudio
  -pulseaudio-module-bluetooth
  -bluez

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  curtis 8167 F pulseaudio
   /dev/snd/controlC2:  curtis 8167 F pulseaudio
   /dev/snd/pcmC2D0c:   curtis 8167 F...m pulseaudio
   /dev/snd/controlC0:  curtis 8167 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 10 15:52:42 2020
  InstallationDate: Installed on 2019-05-24 (352 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: Upgraded to focal on 2020-05-04 (5 days ago)
  dmi.bios.date: 06/20/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1204
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-AR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1204:bd06/20/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-AR:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1874933] Re: Performance workaround for Dell 7390 2-in-1 Ice Lake

[Colin Ian King]

@Srinivas, commit f7db434293387c965e8d9141608f855893740e3a does not
apply cleanly, I guess there are some RAPL related patches that are
prerequisites.  Do you mind assisting on a backport here as I don't want
to miss out the important commits that are also required.

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

Title:
  Performance workaround for Dell 7390 2-in-1 Ice Lake

Status in thermald package in Ubuntu:
  In Progress

Bug description:
  As reported here:
  
https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice-lake-performance-hit-hard-by-a-linux-kernel-regression?view=stream

  This primarily impacts "Ubuntu 20.04 LTS (Focal Fossa)." as it switched to 
5.4 kernel.
  The 5.4 kernel added support for "Processor thermal device", for Ice Lake, 
which will expose the power tables (via PPCC).

  This system default "max RAPL long term power limit" is 15W. But this
  power table is specifying as 9W. So thermald will limit power to 9W.

  If dptfxtract is executed, then power limit will be higher than power
  up value, but most of the users will use out of the box setup. So this
  need a workaround.

  This workaround will ignore any power limit less than the power up
  power limit.

  This is addressed in thermald 2.1 with two commits:
  
https://github.com/intel/thermal_daemon/commit/f7db434293387c965e8d9141608f855893740e3a
  
https://github.com/intel/thermal_daemon/commit/c3461690eafb7304bf59a39fb02955a5154b3861

  I know 20.04 LTS uses 1.9.1. I can assist in backport if required.

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

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

[Kernel-packages] [Bug 1792612] Re: dkms: ERROR: kernel package linux-headers-4.15.0-34-generic is not supported

[indigocat]

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

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

Title:
  dkms: ERROR: kernel package linux-headers-4.15.0-34-generic is not
  supported

Status in linux package in Ubuntu:
  Invalid

Bug description:
  When installing kernel 4.15 (all HWE versions), I get the following
  error message:

  /etc/kernel/header_postinst.d/dkms:
  ERROR (dkms apport): kernel package linux-headers-4.15.0-34-generic is not 
supported
  Error! Bad return status for module build on kernel: 4.15.0-34-generic 
(x86_64)
  Consult /var/lib/dkms/tp_smapi/0.42/build/make.log for more information.

  The tp_smpapi module cannot be compiled for this kernel.
  It does get compiled for kernel 4.4 (lts-xenial).

  ProblemType: Bug
  DistroRelease: elementary 0.4.1
  Package: linux-headers-4.15.0-34-generic 4.15.0-34.37~16.04.1 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140
  Uname: Linux 4.4.0-135-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia wl
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Pantheon
  Date: Fri Sep 14 14:05:34 2018
  InstallationDate: Installed on 2017-09-24 (355 days ago)
  InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170814)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1877894] Re: "True Wireless" Bluetooth headsets not connecting in Ubuntu 20.04

[You-Sheng Yang]

** Tags added: hwe-bluetooth

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

Title:
  "True Wireless" Bluetooth headsets not connecting in Ubuntu 20.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I upgraded my Ubuntu installation from 19.10 to 20.04 and I have lost
  the ability to connect to any kind of Bluetooth "True Wireless"
  earphones (Apple AirPods, Galaxy Earpods+, etc). Standard Bluetooth
  headphones connect correctly but all "True Wireless" style headphones
  briefly connect then disconnect immediately.

  bluetoothctl output:

  ```
  [bluetooth]# devices
  Device C0:28:8D:1D:42:90 Jaybird X3
  Device 7C:38:AD:4A:C8:F9 Galaxy Buds (C8F9)
  Device 40:26:19:DC:12:E6 Apple AirPods

  [bluetooth]# connect C0:28:8D:1D:42:90
  Attempting to connect to C0:28:8D:1D:42:90
  [CHG] Device C0:28:8D:1D:42:90 Connected: yes
  Connection successful

  [Jaybird X3]# connect 7C:38:AD:4A:C8:F9
  ttempting to connect to 7C:38:AD:4A:C8:F9
  [CHG] Device 7C:38:AD:4A:C8:F9 Connected: yes
  Failed to connect: org.bluez.Error.Failed

  Jaybird X3]# connect 40:26:19:DC:12:E6
  Attempting to connect to 40:26:19:DC:12:E6
  [CHG] Device 40:26:19:DC:12:E6 Connected: yes
  Failed to connect: org.bluez.Error.Failed

  [CHG] Device 40:26:19:DC:12:E6 Connected: no
  [CHG] Device 40:26:19:DC:12:E6 Connected: yes
  [CHG] Device 40:26:19:DC:12:E6 Connected: no

  [Jaybird X3]#

  ```


  ```
  $ lsb_release -rd

  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  ```

  possible packages involved:
  -pulseaudio
  -pulseaudio-module-bluetooth
  -bluez

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  curtis 8167 F pulseaudio
   /dev/snd/controlC2:  curtis 8167 F pulseaudio
   /dev/snd/pcmC2D0c:   curtis 8167 F...m pulseaudio
   /dev/snd/controlC0:  curtis 8167 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 10 15:52:42 2020
  InstallationDate: Installed on 2019-05-24 (352 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: Upgraded to focal on 2020-05-04 (5 days ago)
  dmi.bios.date: 06/20/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1204
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-AR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1204:bd06/20/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-AR:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1874933] Re: Performance workaround for Dell 7390 2-in-1 Ice Lake

[Colin Ian King]

Ubuntu 20.10 Groovy will have the latest 2.1 thermald hopefully in the
next few hours.  I'll backport the fixes and SRU this for focal.

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

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

** Changed in: thermald (Ubuntu)
   Importance: Medium => High

** Changed in: thermald (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  Performance workaround for Dell 7390 2-in-1 Ice Lake

Status in thermald package in Ubuntu:
  In Progress

Bug description:
  As reported here:
  
https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice-lake-performance-hit-hard-by-a-linux-kernel-regression?view=stream

  This primarily impacts "Ubuntu 20.04 LTS (Focal Fossa)." as it switched to 
5.4 kernel.
  The 5.4 kernel added support for "Processor thermal device", for Ice Lake, 
which will expose the power tables (via PPCC).

  This system default "max RAPL long term power limit" is 15W. But this
  power table is specifying as 9W. So thermald will limit power to 9W.

  If dptfxtract is executed, then power limit will be higher than power
  up value, but most of the users will use out of the box setup. So this
  need a workaround.

  This workaround will ignore any power limit less than the power up
  power limit.

  This is addressed in thermald 2.1 with two commits:
  
https://github.com/intel/thermal_daemon/commit/f7db434293387c965e8d9141608f855893740e3a
  
https://github.com/intel/thermal_daemon/commit/c3461690eafb7304bf59a39fb02955a5154b3861

  I know 20.04 LTS uses 1.9.1. I can assist in backport if required.

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

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

[Kernel-packages] [Bug 1874519] Re: ZFS installation on Raspberry Pi is problematic

[andrum99]

Thanks for the heads up. The package dependencies should probably be
fixed as well. Glad to hear you've now qualified zfs on Pi - it's worked
fine for my limited use, so it gives me more confidence that I'm not
going to run into trouble if I start stressing the box a bit more.

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

Title:
  ZFS installation on Raspberry Pi is problematic

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Version: Ubuntu Server 20.04 - preinstalled 64-bit image for Raspberry
  Pi.

  ZFS on the Pi under 20.04 is currently a bit problematic. Upon issuing
  the command 'zpool status', I'm helpfully directed to install
  zfsutils-linux. When I do this, it complains that it cannot find the
  ZFS module, then errors out. Worse than that, the zfsutils-linux
  package does not depend on the zfs-dkms package, so it doesn't attempt
  to build the ZFS kernel modules automatically.

  The workaround is to install zfs-dkms, which builds the required
  kernel modules. (Once this has been done, the usual errors when
  installing the zfsutils-linux package, caused by there being no ZFS
  pools on the system, can be worked around by creating a zpool, then
  rerunning 'sudo apt install zfsutils-linux', as with previous versions
  of Ubuntu and Debian).

  I have not tested on other hardware platforms - this problem may also
  exist on other platforms where the user has not selected to install to
  ZFS.

  I have selected 'zfsutils' as the affected package, which is not the
  name of an actual current package, since launchpad won't let me submit
  the bug without selecting a package, however it's not clear to me that
  the problem is caused by that package.

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

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

[Kernel-packages] [Bug 1872373] Re: zfs patches needed for 5.7

[Colin Ian King]

My plan is to get this working for Groovy and then once we have some
kernels built against the driver from the ZFS package and through the
regressions tests I'll then consider SRU'ing them for Focal.

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

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

** Changed in: zfs-linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  zfs patches needed for 5.7

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  As per https://github.com/openzfs/zfs/pull/10187 there is now a patch
  for Linux 5.7 compat: blk_alloc_queue(). Of course there may be more
  patches for the 5.7 series.

  I've hacked up the patch to backport it to work with the 0.8.x series.

  It appears to work: zfs, 0.8.3, 5.7.0-050700rc1-generic, x86_64:
  installed

  The changes to zvol.c may be somewhat questionable.

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

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

[Kernel-packages] [Bug 1814983] Re: zfs poor sustained read performance from ssd pool

[Colin Ian King]

Thanks for the heads-up on this fix. It does not seem to have been
merged yet, so I'll wait for it to get through the regression tests and
once it's upstream I'll backport it for you to test.

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

Title:
  zfs poor sustained read performance from ssd pool

Status in Native ZFS for Linux:
  Unknown
Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I'm seeing substantially slower read performance from an ssd pool than
  I expected.

  I have two pools on this computer; one ('fst') is four sata ssds, the
  other ('srv') is nine spinning metal drives.

  With a long-running ripgrep process on the fst pool, performance
  started out really good and grew to astonishingly good (iirc ~30kiops,
  as measured by zpool iostat -v 1). However after a few hours the
  performance has dropped to 30-40 iops. top reports an arc_reclaim and
  many arc_prune processes to be consuming most of the CPU time.

  I've included a screenshot of top, some output from zpool iostat -v 1,
  and arc_summary, with "===" to indicate the start of the next
  command's output:

  ===
  top (memory in gigabytes):

  top - 16:27:53 up 70 days, 16:03,  3 users,  load average: 35.67, 35.81, 35.58
  Tasks: 809 total,  19 running, 612 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.0 us, 58.1 sy,  0.0 ni, 39.2 id,  2.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  GiB Mem :  125.805 total,0.620 free,   96.942 used,   28.243 buff/cache
  GiB Swap:5.694 total,5.688 free,0.006 used.   27.840 avail Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   1523 root  20   00.0m   0.0m   0.0m R 100.0  0.0 290:52.26 
arc_reclaim 
   4484 root  20   00.0m   0.0m   0.0m R  56.2  0.0   1:18.79 arc_prune 
  
   6225 root  20   00.0m   0.0m   0.0m R  56.2  0.0   1:11.92 arc_prune 
  
   7601 root  20   00.0m   0.0m   0.0m S  56.2  0.0   2:50.25 arc_prune 
  
  30891 root  20   00.0m   0.0m   0.0m S  56.2  0.0   1:33.08 arc_prune 
  
   3057 root  20   00.0m   0.0m   0.0m S  55.9  0.0   9:00.95 arc_prune 
  
   3259 root  20   00.0m   0.0m   0.0m R  55.9  0.0   3:16.84 arc_prune 
  
  24008 root  20   00.0m   0.0m   0.0m S  55.9  0.0   1:55.71 arc_prune 
  
   1285 root  20   00.0m   0.0m   0.0m R  55.6  0.0   3:20.52 arc_prune 
  
   5345 root  20   00.0m   0.0m   0.0m R  55.6  0.0   1:15.99 arc_prune 
  
  30121 root  20   00.0m   0.0m   0.0m S  55.6  0.0   1:35.50 arc_prune 
  
  31192 root  20   00.0m   0.0m   0.0m S  55.6  0.0   6:17.16 arc_prune 
  
  32287 root  20   00.0m   0.0m   0.0m S  55.6  0.0   1:28.02 arc_prune 
  
  32625 root  20   00.0m   0.0m   0.0m R  55.6  0.0   1:27.34 arc_prune 
  
  22572 root  20   00.0m   0.0m   0.0m S  55.3  0.0  10:02.92 arc_prune 
  
  31989 root  20   00.0m   0.0m   0.0m R  55.3  0.0   1:28.03 arc_prune 
  
   3353 root  20   00.0m   0.0m   0.0m R  54.9  0.0   8:58.81 arc_prune 
  
  10252 root  20   00.0m   0.0m   0.0m R  54.9  0.0   2:36.37 arc_prune 
  
   1522 root  20   00.0m   0.0m   0.0m S  53.9  0.0 158:42.45 arc_prune 
  
   3694 root  20   00.0m   0.0m   0.0m R  53.9  0.0   1:20.79 arc_prune 
  
  13394 root  20   00.0m   0.0m   0.0m R  53.9  0.0  10:35.78 arc_prune 
  
  24592 root  20   00.0m   0.0m   0.0m R  53.9  0.0   1:54.19 arc_prune 
  
  25859 root  20   00.0m   0.0m   0.0m S  53.9  0.0   1:51.71 arc_prune 
  
   8194 root  20   00.0m   0.0m   0.0m S  53.6  0.0   0:54.51 arc_prune 
  
  18472 root  20   00.0m   0.0m   0.0m R  53.6  0.0   2:08.73 arc_prune 
  
  29525 root  20   00.0m   0.0m   0.0m R  53.6  0.0   1:35.81 arc_prune 
  
  32291 root  20   00.0m   0.0m   0.0m S  53.6  0.0   1:28.00 

[Kernel-packages] [Bug 1874519] Re: ZFS installation on Raspberry Pi is problematic

[Colin Ian King]

Just for the heads-up, I've evaluated ZFS on a range of raspberry Pis
now and recommended we enable ZFS as part of the kernel package build.
I can't promise when this will land but it will remove this problem in
the long term.

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

Title:
  ZFS installation on Raspberry Pi is problematic

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Version: Ubuntu Server 20.04 - preinstalled 64-bit image for Raspberry
  Pi.

  ZFS on the Pi under 20.04 is currently a bit problematic. Upon issuing
  the command 'zpool status', I'm helpfully directed to install
  zfsutils-linux. When I do this, it complains that it cannot find the
  ZFS module, then errors out. Worse than that, the zfsutils-linux
  package does not depend on the zfs-dkms package, so it doesn't attempt
  to build the ZFS kernel modules automatically.

  The workaround is to install zfs-dkms, which builds the required
  kernel modules. (Once this has been done, the usual errors when
  installing the zfsutils-linux package, caused by there being no ZFS
  pools on the system, can be worked around by creating a zpool, then
  rerunning 'sudo apt install zfsutils-linux', as with previous versions
  of Ubuntu and Debian).

  I have not tested on other hardware platforms - this problem may also
  exist on other platforms where the user has not selected to install to
  ZFS.

  I have selected 'zfsutils' as the affected package, which is not the
  name of an actual current package, since launchpad won't let me submit
  the bug without selecting a package, however it's not clear to me that
  the problem is caused by that package.

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

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

[Kernel-packages] [Bug 1877894] Re: "True Wireless" Bluetooth headsets not connecting in Ubuntu 20.04

[Curtis Mumby]

Here is the output from `journalctl -b 0`:

$ journalctl -b 0
-- Logs begin at Sun 2020-05-03 06:17:09 EDT, end at Fri 20>
May 14 12:11:14 user-linux kernel: microcode: microcode u>
May 14 12:11:14 user-linux kernel: Linux version 5.4.0-29>
May 14 12:11:14 user-linux kernel: Command line: BOOT_IMA>
May 14 12:11:14 user-linux kernel: KERNEL supported cpus:
May 14 12:11:14 user-linux kernel:   Intel GenuineIntel
May 14 12:11:14 user-linux kernel:   AMD AuthenticAMD
May 14 12:11:14 user-linux kernel:   Hygon HygonGenuine
May 14 12:11:14 user-linux kernel:   Centaur CentaurHauls
May 14 12:11:14 user-linux kernel:   zhaoxin   Shanghai  
May 14 12:11:14 user-linux kernel: x86/fpu: Supporting XS>
May 14 12:11:14 user-linux kernel: x86/fpu: Supporting XS>
May 14 12:11:14 user-linux kernel: x86/fpu: Supporting XS

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

Title:
  "True Wireless" Bluetooth headsets not connecting in Ubuntu 20.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I upgraded my Ubuntu installation from 19.10 to 20.04 and I have lost
  the ability to connect to any kind of Bluetooth "True Wireless"
  earphones (Apple AirPods, Galaxy Earpods+, etc). Standard Bluetooth
  headphones connect correctly but all "True Wireless" style headphones
  briefly connect then disconnect immediately.

  bluetoothctl output:

  ```
  [bluetooth]# devices
  Device C0:28:8D:1D:42:90 Jaybird X3
  Device 7C:38:AD:4A:C8:F9 Galaxy Buds (C8F9)
  Device 40:26:19:DC:12:E6 Apple AirPods

  [bluetooth]# connect C0:28:8D:1D:42:90
  Attempting to connect to C0:28:8D:1D:42:90
  [CHG] Device C0:28:8D:1D:42:90 Connected: yes
  Connection successful

  [Jaybird X3]# connect 7C:38:AD:4A:C8:F9
  ttempting to connect to 7C:38:AD:4A:C8:F9
  [CHG] Device 7C:38:AD:4A:C8:F9 Connected: yes
  Failed to connect: org.bluez.Error.Failed

  Jaybird X3]# connect 40:26:19:DC:12:E6
  Attempting to connect to 40:26:19:DC:12:E6
  [CHG] Device 40:26:19:DC:12:E6 Connected: yes
  Failed to connect: org.bluez.Error.Failed

  [CHG] Device 40:26:19:DC:12:E6 Connected: no
  [CHG] Device 40:26:19:DC:12:E6 Connected: yes
  [CHG] Device 40:26:19:DC:12:E6 Connected: no

  [Jaybird X3]#

  ```


  ```
  $ lsb_release -rd

  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  ```

  possible packages involved:
  -pulseaudio
  -pulseaudio-module-bluetooth
  -bluez

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  curtis 8167 F pulseaudio
   /dev/snd/controlC2:  curtis 8167 F pulseaudio
   /dev/snd/pcmC2D0c:   curtis 8167 F...m pulseaudio
   /dev/snd/controlC0:  curtis 8167 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 10 15:52:42 2020
  InstallationDate: Installed on 2019-05-24 (352 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: Upgraded to focal on 2020-05-04 (5 days ago)
  dmi.bios.date: 06/20/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1204
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-AR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1204:bd06/20/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-AR:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Colin Ian King]

This appears not to be a kernel issue per-se, so any idea of an ETA for
a fix with udev for this?

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in linux source package in Focal:
  New
Status in linux-signed source package in Focal:
  New
Status in systemd source package in Focal:
  New
Status in linux source package in Groovy:
  Incomplete
Status in linux-signed source package in Groovy:
  New
Status in systemd source package in Groovy:
  New

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  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
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1870559] Re: Kernel NULL pointer dereference while receiving zfs snapshots

[Colin Ian King]

@Ping? Any chance of trying out my debug test debs?

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

Title:
  Kernel NULL pointer dereference while receiving zfs snapshots

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I was transferring my zfs snapshots to the backup server, when
  suddenly it stalled. I checked dmesg on the server and found a "kernel
  bug" entry.

  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
  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-0ubuntu22
  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/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Fri Apr  3 14:48:19 2020
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=7934268a-8e6f-11e8-828e-00133b1029de ro mitigations=off maybe-ubiquity
  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'
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-01-19 (75 days ago)
  dmi.bios.date: 12/23/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0214
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5LD2-X/1333
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: Rev 1.xx
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0214:bd12/23/2008:svnSystemmanufacturer:pnSystemProductName:pvrRev1.xx:rvnASUSTeKComputerINC.:rnP5LD2-X/1333:rvrRevx.xx:cvnASUSTekComputerINC.:ct3:cvrRev1.xx:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: Rev 1.xx
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1878646] Re: Realtek RTL8723DE [10ec:d723] Subsystem [103c:8319] WiFi is slow

[anggun pribadi]

i am sorry for late response, yes i tried https://github.com/rtlwifi-
linux/rtw88_8723de seems to be better than before. how do i give the
result? sorry i am new to to linux

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

Title:
  Realtek RTL8723DE [10ec:d723] Subsystem [103c:8319] WiFi is slow

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  wifi is running very slow. low on signal indicator.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  anggun 1988 F pulseaudio
   /dev/snd/controlC0:  anggun 1988 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 23:05:40 2020
  MachineType: HP HP Laptop 15-bw0xx
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=fb392428-f4dc-46b4-b100-2f57364db1f4 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.52
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8333
  dmi.board.vendor: HP
  dmi.board.version: 28.35
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.52:bd12/03/2019:svnHP:pnHPLaptop15-bw0xx:pvrType1ProductConfigId:rvnHP:rn8333:rvr28.35:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-bw0xx
  dmi.product.sku: 2DN94PA#AR6
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1849214] Re: "nvidia on-demand" mode does not support external displays

[bram lagerweij]

Just for future reference on the Nvidia Forum, this problem is mentioned in:
https://forums.developer.nvidia.com/t/support-external-displays-in-render-offload-mode/107046/7

This make the whole On-Demand option impossible to use for me, and I was
seeing forward to it so much.

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

Title:
  "nvidia on-demand" mode does not support external displays

Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed

Bug description:
  In a recent driver, Nvidia finally added Linux support for render
  offload, where most graphics are rendered on the CPU-onboard GPU and
  only certain applications are rendered on the discrete Nvidia GPU. I
  know that Ubuntu 19.10 started shipping some updated Xorg packages to
  support this. For the most part the mode seems to work great.

  On my laptop, however, I have found that the "on demand" mode does not
  detect external monitors (and the monitor says it is not receiving a
  signal). Switching to "Nvidia" mode, where everything is rendered on
  the discrete GPU, makes the external displays work. The laptop is a
  Lenovo Thinkpad X1 Extreme (Gen 1). I have found this occurs both with
  nvidia-graphics-drivers-435 and nvidia-graphics-drivers-440 in the
  "graphics-drivers" ppa.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nvidia-driver-435 435.21-0ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 21 13:17:38 2019
  InstallationDate: Installed on 2019-09-04 (47 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-graphics-drivers-435
  UpgradeStatus: Upgraded to eoan on 2019-10-21 (0 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-04 (47 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: nvidia-driver-435 435.21-0ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Tags: eoan third-party-packages
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-21 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1877887] Re: [USB-Audio - Scarlett 2i2 USB, playback] fails after a while

[MIchael Porter]

Unfortunately it seems to still be producing the same issue as before on
the latest kernel. Is it possible for this to be hardware failure? It
doesn't make a whole lot of sense as the issue persist even when
reconnecting the device and it works fine with a reboot. I've also
noticed that it most commonly occurs when something tries to start
playing audio.

I also had it holding solid for a couple days off my USB 3 hub but it
would still produce the issue at a much lower frequency.

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

Title:
  [USB-Audio - Scarlett 2i2 USB, playback] fails after a while

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am encountering some very bizarre and difficult to reliably
  replicate issues.

  I am using a Focusrite Scarlett 2i2 USB audio interface, and am having
  a number of issues that I did not have in older version of ubuntu
  (these issues started occuring sometime in 19.04-19.10, can't remember
  which).

  I am having three major issues. Number one is, if USB autosuspend is
  enabled, it will stop working completely until reboot after anywhere
  from a few minutes to several hours. Reconnecting the device does not
  fix it and it seems to not power on at all, with dmesg reporting a
  "usb_set_interface failed -110" error. Sometimes this bug can be
  recreated by manually disconnecting and reconnecting the device,
  however I was unable to replicate it in this manner at the time of
  filing the bug.

  EDIT: Ignore the two more issue below, however I'm leaving them in the
  post in case they end up being relevant.

  Another (presumably related) issue I am having is that if I reconnect
  the device and it doesn't fail, it outputs very crackly audio, as if
  the bitrate or sample rate were set incorrectly. This persists until a
  restart of pulseaudio. Previously, I had a similar bug where it would
  randomly start doing the crackly audio thing until reconnecting the
  device and in this case a restart of pulse did *not* fix the problem.
  I am unsure if this issue still happens as it was fairly rare.

  The third problem is that sometimes when performing a suspend/wake
  cycle, the interface will power cycle several times, in intervals of
  15-30 seconds or so before staying on properly.

  As previously mentioned, these issues are fairly new and did not occur
  in older versions of ubuntu. I have confirmed that the audio interface
  works fine under windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun May 10 14:09:28 2020
  InstallationDate: Installed on 2020-05-08 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: USB-Audio - microKEY-37
  Symptom_PulseAudioLog:

  Symptom_Type: Sound works for a while, then breaks
  Title: [USB-Audio - Scarlett 2i2 USB, playback] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-08 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   enp37s0   no wireless extensions.

   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=UUID=6108192f-9dc3-480d-9a32-517609064dcd ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:

  Tags:  focal
 

[Kernel-packages] [Bug 1065400] Re: Support for loading Broadcom bluetooth firmware

[Jesse Sung]

@xnor:

Naming rule of the firmware has been changed for some historical
reasons...

* In 14.04, it is "/lib/firmware/brcm/fw-_.hcd". ( 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/trusty/tree/drivers/bluetooth/btusb.c#n1410
 )
* In 16.04, it is "/lib/firmware/brcm/.hcd". ( 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/tree/drivers/bluetooth/btbcm.c#n323
 )
* In 18.04, it is either "/lib/firmware/brcm/.hcd" or 
"/lib/firmware/brcm/--.hcd". ( 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/drivers/bluetooth/btbcm.c#n478
 and 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/drivers/bluetooth/btbcm.c#n499
 )

Unfortunately because of its incompatible license, we're not able to
include the firmware in linux-firmware package. Even in the linux-
firmware upstream, there are only a very small amount of such bluebooth
firmware files and those should already be included in 18.04 linux-
firmware package. (
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/tree/brcm )

If it used to work on 14.04 but stops working after upgrade, you may
already have "/lib/firmware/brcm/fw-_.hcd" in your 14.04
installation (maybe either from a preload Ubuntu system or it was
downloaded from somewhere). Filename of the firmware needs to be changed
after upgrade so that driver can find it. In this case:

$ sudo mv /lib/firmware/brcm/fw-0a5c_21e6.hcd
/lib/firmware/brcm/BCM20702A1-0a5c-21e6.hcd

If you wiped the whole system before installing 18.04, you have to find
the file elsewhere though.

If you are not sure what the correct hcd filename is, please check the
output of dmesg and you'll see the driver complaining about missing
firmware.

$ dmesg

-

For converting the hex formatted firmware to hcd, hex2hcd is included in
newer bluez. In 18.04, simply install bluez then you'll have the tool:

$ sudo apt-get install bluez

Still you can use dmesg to determine the hcd filename to use:

$ dmesg

You'll have to find the hex firmware in Windows driver provided by
laptop vendors, then convert it and place the output to the right place.
For example:

$ sudo hex2hcd -o /lib/firmware/brcm/BCM20702A1-0a5c-21e6.hcd



Hope this helps.

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

Title:
  Support for loading Broadcom bluetooth firmware

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux source package in Quantal:
  Fix Released
Status in linux source package in Raring:
  Fix Released
Status in linux source package in Saucy:
  Fix Released
Status in linux source package in Trusty:
  Confirmed

Bug description:
  Broadcom bluetooth chips require a tool called patchram uploader [1]
  to load firmware. This applies to at least BCM20702 and BCM43142.
  Although some of the devices have an OTPROM that contains required
  firmware, but it is found that these devices would not have HFP/HSP
  support unless a upgraded firmware is loaded via patchram uploader.

  This tool requires hci device to do the firmware loading, but this may
  cause some race condition between patchram tool and bluetoothd or
  something that also works on hci interface.

  Also it needs some hooks to make firmware loads after bootup, s3,  s4,
  rfkill, and device hotplug events. Implement this loader in kernel
  module would make things more easier.

  [1] http://marc.info/?l=linux-bluetooth=132039175324993=2

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

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

[Kernel-packages] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver

[khitschler]

@jose: The above workaround seems to be related with your patch
mentioned at #42.

The function "amdgpu_present_check_flip()" returns prematurely if the
variable "info->allowPageFlip" is set to false. "info->allowPageFlip"
contains the evaluation of the configuration "OPTION_PAGE_FLIP"
evaluated from the option setting "EnablePageFlip". So the mentioned
part of code where the patch is located is never processed.

Maybe this helps a piece more.

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 

[Kernel-packages] [Bug 1877887] Re: [USB-Audio - Scarlett 2i2 USB, playback] fails after a while

[MIchael Porter]

Okay, I have updated to the latest mainline kernel. If it manages to
hold steady the next few days I'll go ahead and close this issue.

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

Title:
  [USB-Audio - Scarlett 2i2 USB, playback] fails after a while

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am encountering some very bizarre and difficult to reliably
  replicate issues.

  I am using a Focusrite Scarlett 2i2 USB audio interface, and am having
  a number of issues that I did not have in older version of ubuntu
  (these issues started occuring sometime in 19.04-19.10, can't remember
  which).

  I am having three major issues. Number one is, if USB autosuspend is
  enabled, it will stop working completely until reboot after anywhere
  from a few minutes to several hours. Reconnecting the device does not
  fix it and it seems to not power on at all, with dmesg reporting a
  "usb_set_interface failed -110" error. Sometimes this bug can be
  recreated by manually disconnecting and reconnecting the device,
  however I was unable to replicate it in this manner at the time of
  filing the bug.

  EDIT: Ignore the two more issue below, however I'm leaving them in the
  post in case they end up being relevant.

  Another (presumably related) issue I am having is that if I reconnect
  the device and it doesn't fail, it outputs very crackly audio, as if
  the bitrate or sample rate were set incorrectly. This persists until a
  restart of pulseaudio. Previously, I had a similar bug where it would
  randomly start doing the crackly audio thing until reconnecting the
  device and in this case a restart of pulse did *not* fix the problem.
  I am unsure if this issue still happens as it was fairly rare.

  The third problem is that sometimes when performing a suspend/wake
  cycle, the interface will power cycle several times, in intervals of
  15-30 seconds or so before staying on properly.

  As previously mentioned, these issues are fairly new and did not occur
  in older versions of ubuntu. I have confirmed that the audio interface
  works fine under windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun May 10 14:09:28 2020
  InstallationDate: Installed on 2020-05-08 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: USB-Audio - microKEY-37
  Symptom_PulseAudioLog:

  Symptom_Type: Sound works for a while, then breaks
  Title: [USB-Audio - Scarlett 2i2 USB, playback] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-08 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   enp37s0   no wireless extensions.

   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=UUID=6108192f-9dc3-480d-9a32-517609064dcd ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:

  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:

  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be 

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

[Paillomams]

apport information

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

Title:
  Kernel bug when running btrfs balance

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  syslog extract:

  May 15 00:38:28 rpi4 kernel: [ 1464.345380] kernel BUG at 
/build/linux-raspi2-5.3-5IVhed/linux-raspi2-5.3-5.3.0/fs/btrfs/relocation.c:4729!
  May 15 00:38:28 rpi4 kernel: [ 1464.355281] Internal error: Oops - BUG: 0 
[#1] SMP
  May 15 00:38:28 rpi4 kernel: [ 1464.360141] Modules linked in: xt_nat 
iptable_nat dm_crypt nls_ascii algif_skcipher af_alg ip6t_REJECT nf_reject_ipv6 
nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_comment btsdio 
nf_log_ipv4 nf_log_common bluetooth bcm2835_v4l2(CE) xt_LOG ecdh_generic 
bcm2835_mmal_vchiq(CE) ecc vc_sm_cma(CE) xt_multiport v4l2_common xt_recent 
videobuf2_vmalloc videobuf2_memops brcmfmac videobuf2_v4l2 brcmutil 
videobuf2_common cfg80211 videodev xt_limit xt_tcpudp raspberrypi_hwmon mc 
xt_addrtype rpivid_mem spidev uio_pdrv_genirq uio xt_conntrack ip6table_filter 
ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat 
nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 sch_fq_codel nf_defrag_ipv4 
iptable_filter bpfilter iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 
raid0 multipath linear broadcom bcm_phy_lib hid_generic
  May 15 00:38:28 rpi4 kernel: [ 1464.360198]  usbhid mdio_bcm_unimac 
crct10dif_ce sdhci_iproc genet gpio_regulator phy_generic fixed uas usb_storage 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  May 15 00:38:28 rpi4 kernel: [ 1464.464074] CPU: 0 PID: 8225 Comm: 
btrfs-balance Tainted: G C  E 5.3.0-1023-raspi2 #25~18.04.1-Ubuntu
  May 15 00:38:28 rpi4 kernel: [ 1464.474482] Hardware name: Raspberry Pi 4 
Model B Rev 1.2 (DT)
  May 15 00:38:28 rpi4 kernel: [ 1464.480395] pstate: 2045 (nzCv daif +PAN 
-UAO)
  May 15 00:38:28 rpi4 kernel: [ 1464.485330] pc : 
btrfs_reloc_cow_block+0x34c/0x3a0 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.490928] lr : 
__btrfs_cow_block+0x368/0x600 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.496133] sp : 13b437b0
  May 15 00:38:28 rpi4 kernel: [ 1464.499487] x29: 13b437b0 x28: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.504870] x27: 0001 x26: 
0001 
  May 15 00:38:28 rpi4 kernel: [ 1464.510253] x25: 9c0ac32c4a80 x24: 
9c0bb321c618 
  May 15 00:38:28 rpi4 kernel: [ 1464.515634] x23: 0001 x22: 
9c0b63242a50 
  May 15 00:38:28 rpi4 kernel: [ 1464.521016] x21: 9c0b23e51ef0 x20: 
9c0b4f111000 
  May 15 00:38:28 rpi4 kernel: [ 1464.526399] x19: 9c0b74bb5000 x18: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.531780] x17:  x16: 
40af26f8be78 
  May 15 00:38:28 rpi4 kernel: [ 1464.537163] x15:  x14: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.542545] x13:  x12: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.547926] x11:  x10: 
9c0b10e83a40 
  May 15 00:38:28 rpi4 kernel: [ 1464.553308] x9 : 9c0aca004750 x8 : 
40af2775b9e7 
  May 15 00:38:28 rpi4 kernel: [ 1464.558690] x7 : 9c0b578814e1 x6 : 
9c0b578814e0 
  May 15 00:38:28 rpi4 kernel: [ 1464.564071] x5 : 9c0b552b59c0 x4 : 
9c0b552b59c0 
  May 15 00:38:28 rpi4 kernel: [ 1464.569452] x3 : 9c0b63242a50 x2 : 
00096be7 
  May 15 00:38:28 rpi4 kernel: [ 1464.574833] x1 :  x0 : 
012e979b4000 
  May 15 00:38:28 rpi4 kernel: [ 1464.580216] Call trace:
  May 15 00:38:28 rpi4 kernel: [ 1464.582735]  
btrfs_reloc_cow_block+0x34c/0x3a0 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.587979]  __btrfs_cow_block+0x368/0x600 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.592869]  btrfs_cow_block+0x100/0x218 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.597583]  btrfs_search_slot+0x560/0x930 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.602475]  do_relocation+0x408/0x5b8 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.607014]  relocate_tree_blocks+0x4f8/0x5c0 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.612170]  relocate_block_group+0x3dc/0x638 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.617325]  
btrfs_relocate_block_group+0x18c/0x2d8 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.623009]  btrfs_relocate_chunk+0x48/0xe0 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.627988]  __btrfs_balance+0x864/0xa38 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.632703]  btrfs_balance+0x434/0x748 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.637301]  balance_kthread+0x38/0x70 [btrfs]
  May 15 00:38:28 rpi4 

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

[Paillomams]

apport information

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

Title:
  Kernel bug when running btrfs balance

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  syslog extract:

  May 15 00:38:28 rpi4 kernel: [ 1464.345380] kernel BUG at 
/build/linux-raspi2-5.3-5IVhed/linux-raspi2-5.3-5.3.0/fs/btrfs/relocation.c:4729!
  May 15 00:38:28 rpi4 kernel: [ 1464.355281] Internal error: Oops - BUG: 0 
[#1] SMP
  May 15 00:38:28 rpi4 kernel: [ 1464.360141] Modules linked in: xt_nat 
iptable_nat dm_crypt nls_ascii algif_skcipher af_alg ip6t_REJECT nf_reject_ipv6 
nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_comment btsdio 
nf_log_ipv4 nf_log_common bluetooth bcm2835_v4l2(CE) xt_LOG ecdh_generic 
bcm2835_mmal_vchiq(CE) ecc vc_sm_cma(CE) xt_multiport v4l2_common xt_recent 
videobuf2_vmalloc videobuf2_memops brcmfmac videobuf2_v4l2 brcmutil 
videobuf2_common cfg80211 videodev xt_limit xt_tcpudp raspberrypi_hwmon mc 
xt_addrtype rpivid_mem spidev uio_pdrv_genirq uio xt_conntrack ip6table_filter 
ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat 
nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 sch_fq_codel nf_defrag_ipv4 
iptable_filter bpfilter iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 
raid0 multipath linear broadcom bcm_phy_lib hid_generic
  May 15 00:38:28 rpi4 kernel: [ 1464.360198]  usbhid mdio_bcm_unimac 
crct10dif_ce sdhci_iproc genet gpio_regulator phy_generic fixed uas usb_storage 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  May 15 00:38:28 rpi4 kernel: [ 1464.464074] CPU: 0 PID: 8225 Comm: 
btrfs-balance Tainted: G C  E 5.3.0-1023-raspi2 #25~18.04.1-Ubuntu
  May 15 00:38:28 rpi4 kernel: [ 1464.474482] Hardware name: Raspberry Pi 4 
Model B Rev 1.2 (DT)
  May 15 00:38:28 rpi4 kernel: [ 1464.480395] pstate: 2045 (nzCv daif +PAN 
-UAO)
  May 15 00:38:28 rpi4 kernel: [ 1464.485330] pc : 
btrfs_reloc_cow_block+0x34c/0x3a0 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.490928] lr : 
__btrfs_cow_block+0x368/0x600 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.496133] sp : 13b437b0
  May 15 00:38:28 rpi4 kernel: [ 1464.499487] x29: 13b437b0 x28: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.504870] x27: 0001 x26: 
0001 
  May 15 00:38:28 rpi4 kernel: [ 1464.510253] x25: 9c0ac32c4a80 x24: 
9c0bb321c618 
  May 15 00:38:28 rpi4 kernel: [ 1464.515634] x23: 0001 x22: 
9c0b63242a50 
  May 15 00:38:28 rpi4 kernel: [ 1464.521016] x21: 9c0b23e51ef0 x20: 
9c0b4f111000 
  May 15 00:38:28 rpi4 kernel: [ 1464.526399] x19: 9c0b74bb5000 x18: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.531780] x17:  x16: 
40af26f8be78 
  May 15 00:38:28 rpi4 kernel: [ 1464.537163] x15:  x14: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.542545] x13:  x12: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.547926] x11:  x10: 
9c0b10e83a40 
  May 15 00:38:28 rpi4 kernel: [ 1464.553308] x9 : 9c0aca004750 x8 : 
40af2775b9e7 
  May 15 00:38:28 rpi4 kernel: [ 1464.558690] x7 : 9c0b578814e1 x6 : 
9c0b578814e0 
  May 15 00:38:28 rpi4 kernel: [ 1464.564071] x5 : 9c0b552b59c0 x4 : 
9c0b552b59c0 
  May 15 00:38:28 rpi4 kernel: [ 1464.569452] x3 : 9c0b63242a50 x2 : 
00096be7 
  May 15 00:38:28 rpi4 kernel: [ 1464.574833] x1 :  x0 : 
012e979b4000 
  May 15 00:38:28 rpi4 kernel: [ 1464.580216] Call trace:
  May 15 00:38:28 rpi4 kernel: [ 1464.582735]  
btrfs_reloc_cow_block+0x34c/0x3a0 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.587979]  __btrfs_cow_block+0x368/0x600 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.592869]  btrfs_cow_block+0x100/0x218 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.597583]  btrfs_search_slot+0x560/0x930 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.602475]  do_relocation+0x408/0x5b8 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.607014]  relocate_tree_blocks+0x4f8/0x5c0 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.612170]  relocate_block_group+0x3dc/0x638 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.617325]  
btrfs_relocate_block_group+0x18c/0x2d8 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.623009]  btrfs_relocate_chunk+0x48/0xe0 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.627988]  __btrfs_balance+0x864/0xa38 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.632703]  btrfs_balance+0x434/0x748 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.637301]  balance_kthread+0x38/0x70 [btrfs]
  May 15 00:38:28 rpi4 

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

[Paillomams]

apport information

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

Title:
  Kernel bug when running btrfs balance

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  syslog extract:

  May 15 00:38:28 rpi4 kernel: [ 1464.345380] kernel BUG at 
/build/linux-raspi2-5.3-5IVhed/linux-raspi2-5.3-5.3.0/fs/btrfs/relocation.c:4729!
  May 15 00:38:28 rpi4 kernel: [ 1464.355281] Internal error: Oops - BUG: 0 
[#1] SMP
  May 15 00:38:28 rpi4 kernel: [ 1464.360141] Modules linked in: xt_nat 
iptable_nat dm_crypt nls_ascii algif_skcipher af_alg ip6t_REJECT nf_reject_ipv6 
nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_comment btsdio 
nf_log_ipv4 nf_log_common bluetooth bcm2835_v4l2(CE) xt_LOG ecdh_generic 
bcm2835_mmal_vchiq(CE) ecc vc_sm_cma(CE) xt_multiport v4l2_common xt_recent 
videobuf2_vmalloc videobuf2_memops brcmfmac videobuf2_v4l2 brcmutil 
videobuf2_common cfg80211 videodev xt_limit xt_tcpudp raspberrypi_hwmon mc 
xt_addrtype rpivid_mem spidev uio_pdrv_genirq uio xt_conntrack ip6table_filter 
ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat 
nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 sch_fq_codel nf_defrag_ipv4 
iptable_filter bpfilter iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 
raid0 multipath linear broadcom bcm_phy_lib hid_generic
  May 15 00:38:28 rpi4 kernel: [ 1464.360198]  usbhid mdio_bcm_unimac 
crct10dif_ce sdhci_iproc genet gpio_regulator phy_generic fixed uas usb_storage 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  May 15 00:38:28 rpi4 kernel: [ 1464.464074] CPU: 0 PID: 8225 Comm: 
btrfs-balance Tainted: G C  E 5.3.0-1023-raspi2 #25~18.04.1-Ubuntu
  May 15 00:38:28 rpi4 kernel: [ 1464.474482] Hardware name: Raspberry Pi 4 
Model B Rev 1.2 (DT)
  May 15 00:38:28 rpi4 kernel: [ 1464.480395] pstate: 2045 (nzCv daif +PAN 
-UAO)
  May 15 00:38:28 rpi4 kernel: [ 1464.485330] pc : 
btrfs_reloc_cow_block+0x34c/0x3a0 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.490928] lr : 
__btrfs_cow_block+0x368/0x600 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.496133] sp : 13b437b0
  May 15 00:38:28 rpi4 kernel: [ 1464.499487] x29: 13b437b0 x28: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.504870] x27: 0001 x26: 
0001 
  May 15 00:38:28 rpi4 kernel: [ 1464.510253] x25: 9c0ac32c4a80 x24: 
9c0bb321c618 
  May 15 00:38:28 rpi4 kernel: [ 1464.515634] x23: 0001 x22: 
9c0b63242a50 
  May 15 00:38:28 rpi4 kernel: [ 1464.521016] x21: 9c0b23e51ef0 x20: 
9c0b4f111000 
  May 15 00:38:28 rpi4 kernel: [ 1464.526399] x19: 9c0b74bb5000 x18: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.531780] x17:  x16: 
40af26f8be78 
  May 15 00:38:28 rpi4 kernel: [ 1464.537163] x15:  x14: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.542545] x13:  x12: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.547926] x11:  x10: 
9c0b10e83a40 
  May 15 00:38:28 rpi4 kernel: [ 1464.553308] x9 : 9c0aca004750 x8 : 
40af2775b9e7 
  May 15 00:38:28 rpi4 kernel: [ 1464.558690] x7 : 9c0b578814e1 x6 : 
9c0b578814e0 
  May 15 00:38:28 rpi4 kernel: [ 1464.564071] x5 : 9c0b552b59c0 x4 : 
9c0b552b59c0 
  May 15 00:38:28 rpi4 kernel: [ 1464.569452] x3 : 9c0b63242a50 x2 : 
00096be7 
  May 15 00:38:28 rpi4 kernel: [ 1464.574833] x1 :  x0 : 
012e979b4000 
  May 15 00:38:28 rpi4 kernel: [ 1464.580216] Call trace:
  May 15 00:38:28 rpi4 kernel: [ 1464.582735]  
btrfs_reloc_cow_block+0x34c/0x3a0 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.587979]  __btrfs_cow_block+0x368/0x600 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.592869]  btrfs_cow_block+0x100/0x218 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.597583]  btrfs_search_slot+0x560/0x930 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.602475]  do_relocation+0x408/0x5b8 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.607014]  relocate_tree_blocks+0x4f8/0x5c0 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.612170]  relocate_block_group+0x3dc/0x638 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.617325]  
btrfs_relocate_block_group+0x18c/0x2d8 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.623009]  btrfs_relocate_chunk+0x48/0xe0 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.627988]  __btrfs_balance+0x864/0xa38 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.632703]  btrfs_balance+0x434/0x748 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.637301]  balance_kthread+0x38/0x70 [btrfs]
  May 15 00:38:28 rpi4 

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

[Paillomams]

apport information

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

Title:
  Kernel bug when running btrfs balance

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  syslog extract:

  May 15 00:38:28 rpi4 kernel: [ 1464.345380] kernel BUG at 
/build/linux-raspi2-5.3-5IVhed/linux-raspi2-5.3-5.3.0/fs/btrfs/relocation.c:4729!
  May 15 00:38:28 rpi4 kernel: [ 1464.355281] Internal error: Oops - BUG: 0 
[#1] SMP
  May 15 00:38:28 rpi4 kernel: [ 1464.360141] Modules linked in: xt_nat 
iptable_nat dm_crypt nls_ascii algif_skcipher af_alg ip6t_REJECT nf_reject_ipv6 
nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_comment btsdio 
nf_log_ipv4 nf_log_common bluetooth bcm2835_v4l2(CE) xt_LOG ecdh_generic 
bcm2835_mmal_vchiq(CE) ecc vc_sm_cma(CE) xt_multiport v4l2_common xt_recent 
videobuf2_vmalloc videobuf2_memops brcmfmac videobuf2_v4l2 brcmutil 
videobuf2_common cfg80211 videodev xt_limit xt_tcpudp raspberrypi_hwmon mc 
xt_addrtype rpivid_mem spidev uio_pdrv_genirq uio xt_conntrack ip6table_filter 
ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat 
nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 sch_fq_codel nf_defrag_ipv4 
iptable_filter bpfilter iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 
raid0 multipath linear broadcom bcm_phy_lib hid_generic
  May 15 00:38:28 rpi4 kernel: [ 1464.360198]  usbhid mdio_bcm_unimac 
crct10dif_ce sdhci_iproc genet gpio_regulator phy_generic fixed uas usb_storage 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  May 15 00:38:28 rpi4 kernel: [ 1464.464074] CPU: 0 PID: 8225 Comm: 
btrfs-balance Tainted: G C  E 5.3.0-1023-raspi2 #25~18.04.1-Ubuntu
  May 15 00:38:28 rpi4 kernel: [ 1464.474482] Hardware name: Raspberry Pi 4 
Model B Rev 1.2 (DT)
  May 15 00:38:28 rpi4 kernel: [ 1464.480395] pstate: 2045 (nzCv daif +PAN 
-UAO)
  May 15 00:38:28 rpi4 kernel: [ 1464.485330] pc : 
btrfs_reloc_cow_block+0x34c/0x3a0 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.490928] lr : 
__btrfs_cow_block+0x368/0x600 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.496133] sp : 13b437b0
  May 15 00:38:28 rpi4 kernel: [ 1464.499487] x29: 13b437b0 x28: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.504870] x27: 0001 x26: 
0001 
  May 15 00:38:28 rpi4 kernel: [ 1464.510253] x25: 9c0ac32c4a80 x24: 
9c0bb321c618 
  May 15 00:38:28 rpi4 kernel: [ 1464.515634] x23: 0001 x22: 
9c0b63242a50 
  May 15 00:38:28 rpi4 kernel: [ 1464.521016] x21: 9c0b23e51ef0 x20: 
9c0b4f111000 
  May 15 00:38:28 rpi4 kernel: [ 1464.526399] x19: 9c0b74bb5000 x18: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.531780] x17:  x16: 
40af26f8be78 
  May 15 00:38:28 rpi4 kernel: [ 1464.537163] x15:  x14: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.542545] x13:  x12: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.547926] x11:  x10: 
9c0b10e83a40 
  May 15 00:38:28 rpi4 kernel: [ 1464.553308] x9 : 9c0aca004750 x8 : 
40af2775b9e7 
  May 15 00:38:28 rpi4 kernel: [ 1464.558690] x7 : 9c0b578814e1 x6 : 
9c0b578814e0 
  May 15 00:38:28 rpi4 kernel: [ 1464.564071] x5 : 9c0b552b59c0 x4 : 
9c0b552b59c0 
  May 15 00:38:28 rpi4 kernel: [ 1464.569452] x3 : 9c0b63242a50 x2 : 
00096be7 
  May 15 00:38:28 rpi4 kernel: [ 1464.574833] x1 :  x0 : 
012e979b4000 
  May 15 00:38:28 rpi4 kernel: [ 1464.580216] Call trace:
  May 15 00:38:28 rpi4 kernel: [ 1464.582735]  
btrfs_reloc_cow_block+0x34c/0x3a0 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.587979]  __btrfs_cow_block+0x368/0x600 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.592869]  btrfs_cow_block+0x100/0x218 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.597583]  btrfs_search_slot+0x560/0x930 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.602475]  do_relocation+0x408/0x5b8 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.607014]  relocate_tree_blocks+0x4f8/0x5c0 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.612170]  relocate_block_group+0x3dc/0x638 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.617325]  
btrfs_relocate_block_group+0x18c/0x2d8 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.623009]  btrfs_relocate_chunk+0x48/0xe0 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.627988]  __btrfs_balance+0x864/0xa38 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.632703]  btrfs_balance+0x434/0x748 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.637301]  balance_kthread+0x38/0x70 [btrfs]
  

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

[Paillomams]

apport information

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

Title:
  Kernel bug when running btrfs balance

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  syslog extract:

  May 15 00:38:28 rpi4 kernel: [ 1464.345380] kernel BUG at 
/build/linux-raspi2-5.3-5IVhed/linux-raspi2-5.3-5.3.0/fs/btrfs/relocation.c:4729!
  May 15 00:38:28 rpi4 kernel: [ 1464.355281] Internal error: Oops - BUG: 0 
[#1] SMP
  May 15 00:38:28 rpi4 kernel: [ 1464.360141] Modules linked in: xt_nat 
iptable_nat dm_crypt nls_ascii algif_skcipher af_alg ip6t_REJECT nf_reject_ipv6 
nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_comment btsdio 
nf_log_ipv4 nf_log_common bluetooth bcm2835_v4l2(CE) xt_LOG ecdh_generic 
bcm2835_mmal_vchiq(CE) ecc vc_sm_cma(CE) xt_multiport v4l2_common xt_recent 
videobuf2_vmalloc videobuf2_memops brcmfmac videobuf2_v4l2 brcmutil 
videobuf2_common cfg80211 videodev xt_limit xt_tcpudp raspberrypi_hwmon mc 
xt_addrtype rpivid_mem spidev uio_pdrv_genirq uio xt_conntrack ip6table_filter 
ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat 
nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 sch_fq_codel nf_defrag_ipv4 
iptable_filter bpfilter iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 
raid0 multipath linear broadcom bcm_phy_lib hid_generic
  May 15 00:38:28 rpi4 kernel: [ 1464.360198]  usbhid mdio_bcm_unimac 
crct10dif_ce sdhci_iproc genet gpio_regulator phy_generic fixed uas usb_storage 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  May 15 00:38:28 rpi4 kernel: [ 1464.464074] CPU: 0 PID: 8225 Comm: 
btrfs-balance Tainted: G C  E 5.3.0-1023-raspi2 #25~18.04.1-Ubuntu
  May 15 00:38:28 rpi4 kernel: [ 1464.474482] Hardware name: Raspberry Pi 4 
Model B Rev 1.2 (DT)
  May 15 00:38:28 rpi4 kernel: [ 1464.480395] pstate: 2045 (nzCv daif +PAN 
-UAO)
  May 15 00:38:28 rpi4 kernel: [ 1464.485330] pc : 
btrfs_reloc_cow_block+0x34c/0x3a0 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.490928] lr : 
__btrfs_cow_block+0x368/0x600 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.496133] sp : 13b437b0
  May 15 00:38:28 rpi4 kernel: [ 1464.499487] x29: 13b437b0 x28: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.504870] x27: 0001 x26: 
0001 
  May 15 00:38:28 rpi4 kernel: [ 1464.510253] x25: 9c0ac32c4a80 x24: 
9c0bb321c618 
  May 15 00:38:28 rpi4 kernel: [ 1464.515634] x23: 0001 x22: 
9c0b63242a50 
  May 15 00:38:28 rpi4 kernel: [ 1464.521016] x21: 9c0b23e51ef0 x20: 
9c0b4f111000 
  May 15 00:38:28 rpi4 kernel: [ 1464.526399] x19: 9c0b74bb5000 x18: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.531780] x17:  x16: 
40af26f8be78 
  May 15 00:38:28 rpi4 kernel: [ 1464.537163] x15:  x14: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.542545] x13:  x12: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.547926] x11:  x10: 
9c0b10e83a40 
  May 15 00:38:28 rpi4 kernel: [ 1464.553308] x9 : 9c0aca004750 x8 : 
40af2775b9e7 
  May 15 00:38:28 rpi4 kernel: [ 1464.558690] x7 : 9c0b578814e1 x6 : 
9c0b578814e0 
  May 15 00:38:28 rpi4 kernel: [ 1464.564071] x5 : 9c0b552b59c0 x4 : 
9c0b552b59c0 
  May 15 00:38:28 rpi4 kernel: [ 1464.569452] x3 : 9c0b63242a50 x2 : 
00096be7 
  May 15 00:38:28 rpi4 kernel: [ 1464.574833] x1 :  x0 : 
012e979b4000 
  May 15 00:38:28 rpi4 kernel: [ 1464.580216] Call trace:
  May 15 00:38:28 rpi4 kernel: [ 1464.582735]  
btrfs_reloc_cow_block+0x34c/0x3a0 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.587979]  __btrfs_cow_block+0x368/0x600 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.592869]  btrfs_cow_block+0x100/0x218 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.597583]  btrfs_search_slot+0x560/0x930 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.602475]  do_relocation+0x408/0x5b8 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.607014]  relocate_tree_blocks+0x4f8/0x5c0 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.612170]  relocate_block_group+0x3dc/0x638 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.617325]  
btrfs_relocate_block_group+0x18c/0x2d8 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.623009]  btrfs_relocate_chunk+0x48/0xe0 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.627988]  __btrfs_balance+0x864/0xa38 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.632703]  btrfs_balance+0x434/0x748 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.637301]  balance_kthread+0x38/0x70 [btrfs]
  May 15 

[Kernel-packages] [Bug 1878749] Re: Kernel bug when running btrfs balance

[Paillomams]

apport information

** Tags added: apport-collected bionic uec-images

** Description changed:

  syslog extract:
  
  May 15 00:38:28 rpi4 kernel: [ 1464.345380] kernel BUG at 
/build/linux-raspi2-5.3-5IVhed/linux-raspi2-5.3-5.3.0/fs/btrfs/relocation.c:4729!
  May 15 00:38:28 rpi4 kernel: [ 1464.355281] Internal error: Oops - BUG: 0 
[#1] SMP
  May 15 00:38:28 rpi4 kernel: [ 1464.360141] Modules linked in: xt_nat 
iptable_nat dm_crypt nls_ascii algif_skcipher af_alg ip6t_REJECT nf_reject_ipv6 
nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_comment btsdio 
nf_log_ipv4 nf_log_common bluetooth bcm2835_v4l2(CE) xt_LOG ecdh_generic 
bcm2835_mmal_vchiq(CE) ecc vc_sm_cma(CE) xt_multiport v4l2_common xt_recent 
videobuf2_vmalloc videobuf2_memops brcmfmac videobuf2_v4l2 brcmutil 
videobuf2_common cfg80211 videodev xt_limit xt_tcpudp raspberrypi_hwmon mc 
xt_addrtype rpivid_mem spidev uio_pdrv_genirq uio xt_conntrack ip6table_filter 
ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat 
nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 sch_fq_codel nf_defrag_ipv4 
iptable_filter bpfilter iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 
raid0 multipath linear broadcom bcm_phy_lib hid_generic
  May 15 00:38:28 rpi4 kernel: [ 1464.360198]  usbhid mdio_bcm_unimac 
crct10dif_ce sdhci_iproc genet gpio_regulator phy_generic fixed uas usb_storage 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  May 15 00:38:28 rpi4 kernel: [ 1464.464074] CPU: 0 PID: 8225 Comm: 
btrfs-balance Tainted: G C  E 5.3.0-1023-raspi2 #25~18.04.1-Ubuntu
  May 15 00:38:28 rpi4 kernel: [ 1464.474482] Hardware name: Raspberry Pi 4 
Model B Rev 1.2 (DT)
  May 15 00:38:28 rpi4 kernel: [ 1464.480395] pstate: 2045 (nzCv daif +PAN 
-UAO)
  May 15 00:38:28 rpi4 kernel: [ 1464.485330] pc : 
btrfs_reloc_cow_block+0x34c/0x3a0 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.490928] lr : 
__btrfs_cow_block+0x368/0x600 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.496133] sp : 13b437b0
  May 15 00:38:28 rpi4 kernel: [ 1464.499487] x29: 13b437b0 x28: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.504870] x27: 0001 x26: 
0001 
  May 15 00:38:28 rpi4 kernel: [ 1464.510253] x25: 9c0ac32c4a80 x24: 
9c0bb321c618 
  May 15 00:38:28 rpi4 kernel: [ 1464.515634] x23: 0001 x22: 
9c0b63242a50 
  May 15 00:38:28 rpi4 kernel: [ 1464.521016] x21: 9c0b23e51ef0 x20: 
9c0b4f111000 
  May 15 00:38:28 rpi4 kernel: [ 1464.526399] x19: 9c0b74bb5000 x18: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.531780] x17:  x16: 
40af26f8be78 
  May 15 00:38:28 rpi4 kernel: [ 1464.537163] x15:  x14: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.542545] x13:  x12: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.547926] x11:  x10: 
9c0b10e83a40 
  May 15 00:38:28 rpi4 kernel: [ 1464.553308] x9 : 9c0aca004750 x8 : 
40af2775b9e7 
  May 15 00:38:28 rpi4 kernel: [ 1464.558690] x7 : 9c0b578814e1 x6 : 
9c0b578814e0 
  May 15 00:38:28 rpi4 kernel: [ 1464.564071] x5 : 9c0b552b59c0 x4 : 
9c0b552b59c0 
  May 15 00:38:28 rpi4 kernel: [ 1464.569452] x3 : 9c0b63242a50 x2 : 
00096be7 
  May 15 00:38:28 rpi4 kernel: [ 1464.574833] x1 :  x0 : 
012e979b4000 
  May 15 00:38:28 rpi4 kernel: [ 1464.580216] Call trace:
  May 15 00:38:28 rpi4 kernel: [ 1464.582735]  
btrfs_reloc_cow_block+0x34c/0x3a0 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.587979]  __btrfs_cow_block+0x368/0x600 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.592869]  btrfs_cow_block+0x100/0x218 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.597583]  btrfs_search_slot+0x560/0x930 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.602475]  do_relocation+0x408/0x5b8 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.607014]  relocate_tree_blocks+0x4f8/0x5c0 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.612170]  relocate_block_group+0x3dc/0x638 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.617325]  
btrfs_relocate_block_group+0x18c/0x2d8 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.623009]  btrfs_relocate_chunk+0x48/0xe0 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.627988]  __btrfs_balance+0x864/0xa38 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.632703]  btrfs_balance+0x434/0x748 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.637301]  balance_kthread+0x38/0x70 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.641811]  kthread+0x124/0x128
  May 15 00:38:28 rpi4 kernel: [ 1464.645081]  ret_from_fork+0x10/0x1c
  May 15 00:38:28 rpi4 kernel: [ 1464.648706] Code: f9401321 eb01001f 54fff020 
f9002fbc (d421) 
  May 15 00:38:28 rpi4 kernel: [ 1464.654884] ---[ end trace 01ad7c5a4a25131c 
]---
  May 15 00:38:28 

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

[Paillomams]

apport information

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

Title:
  Kernel bug when running btrfs balance

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  syslog extract:

  May 15 00:38:28 rpi4 kernel: [ 1464.345380] kernel BUG at 
/build/linux-raspi2-5.3-5IVhed/linux-raspi2-5.3-5.3.0/fs/btrfs/relocation.c:4729!
  May 15 00:38:28 rpi4 kernel: [ 1464.355281] Internal error: Oops - BUG: 0 
[#1] SMP
  May 15 00:38:28 rpi4 kernel: [ 1464.360141] Modules linked in: xt_nat 
iptable_nat dm_crypt nls_ascii algif_skcipher af_alg ip6t_REJECT nf_reject_ipv6 
nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_comment btsdio 
nf_log_ipv4 nf_log_common bluetooth bcm2835_v4l2(CE) xt_LOG ecdh_generic 
bcm2835_mmal_vchiq(CE) ecc vc_sm_cma(CE) xt_multiport v4l2_common xt_recent 
videobuf2_vmalloc videobuf2_memops brcmfmac videobuf2_v4l2 brcmutil 
videobuf2_common cfg80211 videodev xt_limit xt_tcpudp raspberrypi_hwmon mc 
xt_addrtype rpivid_mem spidev uio_pdrv_genirq uio xt_conntrack ip6table_filter 
ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat 
nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 sch_fq_codel nf_defrag_ipv4 
iptable_filter bpfilter iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 
raid0 multipath linear broadcom bcm_phy_lib hid_generic
  May 15 00:38:28 rpi4 kernel: [ 1464.360198]  usbhid mdio_bcm_unimac 
crct10dif_ce sdhci_iproc genet gpio_regulator phy_generic fixed uas usb_storage 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  May 15 00:38:28 rpi4 kernel: [ 1464.464074] CPU: 0 PID: 8225 Comm: 
btrfs-balance Tainted: G C  E 5.3.0-1023-raspi2 #25~18.04.1-Ubuntu
  May 15 00:38:28 rpi4 kernel: [ 1464.474482] Hardware name: Raspberry Pi 4 
Model B Rev 1.2 (DT)
  May 15 00:38:28 rpi4 kernel: [ 1464.480395] pstate: 2045 (nzCv daif +PAN 
-UAO)
  May 15 00:38:28 rpi4 kernel: [ 1464.485330] pc : 
btrfs_reloc_cow_block+0x34c/0x3a0 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.490928] lr : 
__btrfs_cow_block+0x368/0x600 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.496133] sp : 13b437b0
  May 15 00:38:28 rpi4 kernel: [ 1464.499487] x29: 13b437b0 x28: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.504870] x27: 0001 x26: 
0001 
  May 15 00:38:28 rpi4 kernel: [ 1464.510253] x25: 9c0ac32c4a80 x24: 
9c0bb321c618 
  May 15 00:38:28 rpi4 kernel: [ 1464.515634] x23: 0001 x22: 
9c0b63242a50 
  May 15 00:38:28 rpi4 kernel: [ 1464.521016] x21: 9c0b23e51ef0 x20: 
9c0b4f111000 
  May 15 00:38:28 rpi4 kernel: [ 1464.526399] x19: 9c0b74bb5000 x18: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.531780] x17:  x16: 
40af26f8be78 
  May 15 00:38:28 rpi4 kernel: [ 1464.537163] x15:  x14: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.542545] x13:  x12: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.547926] x11:  x10: 
9c0b10e83a40 
  May 15 00:38:28 rpi4 kernel: [ 1464.553308] x9 : 9c0aca004750 x8 : 
40af2775b9e7 
  May 15 00:38:28 rpi4 kernel: [ 1464.558690] x7 : 9c0b578814e1 x6 : 
9c0b578814e0 
  May 15 00:38:28 rpi4 kernel: [ 1464.564071] x5 : 9c0b552b59c0 x4 : 
9c0b552b59c0 
  May 15 00:38:28 rpi4 kernel: [ 1464.569452] x3 : 9c0b63242a50 x2 : 
00096be7 
  May 15 00:38:28 rpi4 kernel: [ 1464.574833] x1 :  x0 : 
012e979b4000 
  May 15 00:38:28 rpi4 kernel: [ 1464.580216] Call trace:
  May 15 00:38:28 rpi4 kernel: [ 1464.582735]  
btrfs_reloc_cow_block+0x34c/0x3a0 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.587979]  __btrfs_cow_block+0x368/0x600 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.592869]  btrfs_cow_block+0x100/0x218 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.597583]  btrfs_search_slot+0x560/0x930 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.602475]  do_relocation+0x408/0x5b8 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.607014]  relocate_tree_blocks+0x4f8/0x5c0 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.612170]  relocate_block_group+0x3dc/0x638 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.617325]  
btrfs_relocate_block_group+0x18c/0x2d8 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.623009]  btrfs_relocate_chunk+0x48/0xe0 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.627988]  __btrfs_balance+0x864/0xa38 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.632703]  btrfs_balance+0x434/0x748 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.637301]  balance_kthread+0x38/0x70 [btrfs]
  May 15 

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

[Paillomams]

apport information

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

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

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

Title:
  Kernel bug when running btrfs balance

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  syslog extract:

  May 15 00:38:28 rpi4 kernel: [ 1464.345380] kernel BUG at 
/build/linux-raspi2-5.3-5IVhed/linux-raspi2-5.3-5.3.0/fs/btrfs/relocation.c:4729!
  May 15 00:38:28 rpi4 kernel: [ 1464.355281] Internal error: Oops - BUG: 0 
[#1] SMP
  May 15 00:38:28 rpi4 kernel: [ 1464.360141] Modules linked in: xt_nat 
iptable_nat dm_crypt nls_ascii algif_skcipher af_alg ip6t_REJECT nf_reject_ipv6 
nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_comment btsdio 
nf_log_ipv4 nf_log_common bluetooth bcm2835_v4l2(CE) xt_LOG ecdh_generic 
bcm2835_mmal_vchiq(CE) ecc vc_sm_cma(CE) xt_multiport v4l2_common xt_recent 
videobuf2_vmalloc videobuf2_memops brcmfmac videobuf2_v4l2 brcmutil 
videobuf2_common cfg80211 videodev xt_limit xt_tcpudp raspberrypi_hwmon mc 
xt_addrtype rpivid_mem spidev uio_pdrv_genirq uio xt_conntrack ip6table_filter 
ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat 
nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 sch_fq_codel nf_defrag_ipv4 
iptable_filter bpfilter iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 
raid0 multipath linear broadcom bcm_phy_lib hid_generic
  May 15 00:38:28 rpi4 kernel: [ 1464.360198]  usbhid mdio_bcm_unimac 
crct10dif_ce sdhci_iproc genet gpio_regulator phy_generic fixed uas usb_storage 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  May 15 00:38:28 rpi4 kernel: [ 1464.464074] CPU: 0 PID: 8225 Comm: 
btrfs-balance Tainted: G C  E 5.3.0-1023-raspi2 #25~18.04.1-Ubuntu
  May 15 00:38:28 rpi4 kernel: [ 1464.474482] Hardware name: Raspberry Pi 4 
Model B Rev 1.2 (DT)
  May 15 00:38:28 rpi4 kernel: [ 1464.480395] pstate: 2045 (nzCv daif +PAN 
-UAO)
  May 15 00:38:28 rpi4 kernel: [ 1464.485330] pc : 
btrfs_reloc_cow_block+0x34c/0x3a0 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.490928] lr : 
__btrfs_cow_block+0x368/0x600 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.496133] sp : 13b437b0
  May 15 00:38:28 rpi4 kernel: [ 1464.499487] x29: 13b437b0 x28: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.504870] x27: 0001 x26: 
0001 
  May 15 00:38:28 rpi4 kernel: [ 1464.510253] x25: 9c0ac32c4a80 x24: 
9c0bb321c618 
  May 15 00:38:28 rpi4 kernel: [ 1464.515634] x23: 0001 x22: 
9c0b63242a50 
  May 15 00:38:28 rpi4 kernel: [ 1464.521016] x21: 9c0b23e51ef0 x20: 
9c0b4f111000 
  May 15 00:38:28 rpi4 kernel: [ 1464.526399] x19: 9c0b74bb5000 x18: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.531780] x17:  x16: 
40af26f8be78 
  May 15 00:38:28 rpi4 kernel: [ 1464.537163] x15:  x14: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.542545] x13:  x12: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.547926] x11:  x10: 
9c0b10e83a40 
  May 15 00:38:28 rpi4 kernel: [ 1464.553308] x9 : 9c0aca004750 x8 : 
40af2775b9e7 
  May 15 00:38:28 rpi4 kernel: [ 1464.558690] x7 : 9c0b578814e1 x6 : 
9c0b578814e0 
  May 15 00:38:28 rpi4 kernel: [ 1464.564071] x5 : 9c0b552b59c0 x4 : 
9c0b552b59c0 
  May 15 00:38:28 rpi4 kernel: [ 1464.569452] x3 : 9c0b63242a50 x2 : 
00096be7 
  May 15 00:38:28 rpi4 kernel: [ 1464.574833] x1 :  x0 : 
012e979b4000 
  May 15 00:38:28 rpi4 kernel: [ 1464.580216] Call trace:
  May 15 00:38:28 rpi4 kernel: [ 1464.582735]  
btrfs_reloc_cow_block+0x34c/0x3a0 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.587979]  __btrfs_cow_block+0x368/0x600 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.592869]  btrfs_cow_block+0x100/0x218 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.597583]  btrfs_search_slot+0x560/0x930 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.602475]  do_relocation+0x408/0x5b8 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.607014]  relocate_tree_blocks+0x4f8/0x5c0 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.612170]  relocate_block_group+0x3dc/0x638 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.617325]  
btrfs_relocate_block_group+0x18c/0x2d8 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.623009]  btrfs_relocate_chunk+0x48/0xe0 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.627988]  __btrfs_balance+0x864/0xa38 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.632703]  btrfs_balance+0x434/0x748 [btrfs]
  May 15 00:38:28 rpi4 

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

[Paillomams]

apport information

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

Title:
  Kernel bug when running btrfs balance

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  syslog extract:

  May 15 00:38:28 rpi4 kernel: [ 1464.345380] kernel BUG at 
/build/linux-raspi2-5.3-5IVhed/linux-raspi2-5.3-5.3.0/fs/btrfs/relocation.c:4729!
  May 15 00:38:28 rpi4 kernel: [ 1464.355281] Internal error: Oops - BUG: 0 
[#1] SMP
  May 15 00:38:28 rpi4 kernel: [ 1464.360141] Modules linked in: xt_nat 
iptable_nat dm_crypt nls_ascii algif_skcipher af_alg ip6t_REJECT nf_reject_ipv6 
nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_comment btsdio 
nf_log_ipv4 nf_log_common bluetooth bcm2835_v4l2(CE) xt_LOG ecdh_generic 
bcm2835_mmal_vchiq(CE) ecc vc_sm_cma(CE) xt_multiport v4l2_common xt_recent 
videobuf2_vmalloc videobuf2_memops brcmfmac videobuf2_v4l2 brcmutil 
videobuf2_common cfg80211 videodev xt_limit xt_tcpudp raspberrypi_hwmon mc 
xt_addrtype rpivid_mem spidev uio_pdrv_genirq uio xt_conntrack ip6table_filter 
ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat 
nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 sch_fq_codel nf_defrag_ipv4 
iptable_filter bpfilter iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 
raid0 multipath linear broadcom bcm_phy_lib hid_generic
  May 15 00:38:28 rpi4 kernel: [ 1464.360198]  usbhid mdio_bcm_unimac 
crct10dif_ce sdhci_iproc genet gpio_regulator phy_generic fixed uas usb_storage 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  May 15 00:38:28 rpi4 kernel: [ 1464.464074] CPU: 0 PID: 8225 Comm: 
btrfs-balance Tainted: G C  E 5.3.0-1023-raspi2 #25~18.04.1-Ubuntu
  May 15 00:38:28 rpi4 kernel: [ 1464.474482] Hardware name: Raspberry Pi 4 
Model B Rev 1.2 (DT)
  May 15 00:38:28 rpi4 kernel: [ 1464.480395] pstate: 2045 (nzCv daif +PAN 
-UAO)
  May 15 00:38:28 rpi4 kernel: [ 1464.485330] pc : 
btrfs_reloc_cow_block+0x34c/0x3a0 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.490928] lr : 
__btrfs_cow_block+0x368/0x600 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.496133] sp : 13b437b0
  May 15 00:38:28 rpi4 kernel: [ 1464.499487] x29: 13b437b0 x28: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.504870] x27: 0001 x26: 
0001 
  May 15 00:38:28 rpi4 kernel: [ 1464.510253] x25: 9c0ac32c4a80 x24: 
9c0bb321c618 
  May 15 00:38:28 rpi4 kernel: [ 1464.515634] x23: 0001 x22: 
9c0b63242a50 
  May 15 00:38:28 rpi4 kernel: [ 1464.521016] x21: 9c0b23e51ef0 x20: 
9c0b4f111000 
  May 15 00:38:28 rpi4 kernel: [ 1464.526399] x19: 9c0b74bb5000 x18: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.531780] x17:  x16: 
40af26f8be78 
  May 15 00:38:28 rpi4 kernel: [ 1464.537163] x15:  x14: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.542545] x13:  x12: 
 
  May 15 00:38:28 rpi4 kernel: [ 1464.547926] x11:  x10: 
9c0b10e83a40 
  May 15 00:38:28 rpi4 kernel: [ 1464.553308] x9 : 9c0aca004750 x8 : 
40af2775b9e7 
  May 15 00:38:28 rpi4 kernel: [ 1464.558690] x7 : 9c0b578814e1 x6 : 
9c0b578814e0 
  May 15 00:38:28 rpi4 kernel: [ 1464.564071] x5 : 9c0b552b59c0 x4 : 
9c0b552b59c0 
  May 15 00:38:28 rpi4 kernel: [ 1464.569452] x3 : 9c0b63242a50 x2 : 
00096be7 
  May 15 00:38:28 rpi4 kernel: [ 1464.574833] x1 :  x0 : 
012e979b4000 
  May 15 00:38:28 rpi4 kernel: [ 1464.580216] Call trace:
  May 15 00:38:28 rpi4 kernel: [ 1464.582735]  
btrfs_reloc_cow_block+0x34c/0x3a0 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.587979]  __btrfs_cow_block+0x368/0x600 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.592869]  btrfs_cow_block+0x100/0x218 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.597583]  btrfs_search_slot+0x560/0x930 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.602475]  do_relocation+0x408/0x5b8 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.607014]  relocate_tree_blocks+0x4f8/0x5c0 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.612170]  relocate_block_group+0x3dc/0x638 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.617325]  
btrfs_relocate_block_group+0x18c/0x2d8 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.623009]  btrfs_relocate_chunk+0x48/0xe0 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.627988]  __btrfs_balance+0x864/0xa38 
[btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.632703]  btrfs_balance+0x434/0x748 [btrfs]
  May 15 00:38:28 rpi4 kernel: [ 1464.637301]  balance_kthread+0x38/0x70 [btrfs]
  May 15 

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

[Max Barth]

apport information

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

Title:
  Ubuntu 20.04 HDMI connected, no boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 20.04 (using the image created on 20 april) on
  my Dell XPS15 9560. This laptop has a Intel / nVidia combo.

  The problem i am facing is that when i have an external monitor
  connected to the laptop through the HDMI connector of the laptop,
  Ubuntu does not boot and hangs on the splash screen. I have not found
  any way to get logging on any kind.

  Before i was running Ubuntu 18.04 and did not have any problems with
  the monitor and HDMI cable. After boot is finished (without monitor
  connected) inserting the HDMI cable works fine and i can use the
  monitor and laptop screen without any problem.

  I have installed the preferred nVida proprietary driver. Also it does
  not matter if booting with nVidia selected or Intel selected.

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

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

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

[Max Barth]

apport information

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

Title:
  Ubuntu 20.04 HDMI connected, no boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 20.04 (using the image created on 20 april) on
  my Dell XPS15 9560. This laptop has a Intel / nVidia combo.

  The problem i am facing is that when i have an external monitor
  connected to the laptop through the HDMI connector of the laptop,
  Ubuntu does not boot and hangs on the splash screen. I have not found
  any way to get logging on any kind.

  Before i was running Ubuntu 18.04 and did not have any problems with
  the monitor and HDMI cable. After boot is finished (without monitor
  connected) inserting the HDMI cable works fine and i can use the
  monitor and laptop screen without any problem.

  I have installed the preferred nVida proprietary driver. Also it does
  not matter if booting with nVidia selected or Intel selected.

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

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

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

[Max Barth]

apport information

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

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

Title:
  Ubuntu 20.04 HDMI connected, no boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 20.04 (using the image created on 20 april) on
  my Dell XPS15 9560. This laptop has a Intel / nVidia combo.

  The problem i am facing is that when i have an external monitor
  connected to the laptop through the HDMI connector of the laptop,
  Ubuntu does not boot and hangs on the splash screen. I have not found
  any way to get logging on any kind.

  Before i was running Ubuntu 18.04 and did not have any problems with
  the monitor and HDMI cable. After boot is finished (without monitor
  connected) inserting the HDMI cable works fine and i can use the
  monitor and laptop screen without any problem.

  I have installed the preferred nVida proprietary driver. Also it does
  not matter if booting with nVidia selected or Intel selected.

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

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

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

[Max Barth]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1874194/+attachment/5372012/+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/1874194

Title:
  Ubuntu 20.04 HDMI connected, no boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 20.04 (using the image created on 20 april) on
  my Dell XPS15 9560. This laptop has a Intel / nVidia combo.

  The problem i am facing is that when i have an external monitor
  connected to the laptop through the HDMI connector of the laptop,
  Ubuntu does not boot and hangs on the splash screen. I have not found
  any way to get logging on any kind.

  Before i was running Ubuntu 18.04 and did not have any problems with
  the monitor and HDMI cable. After boot is finished (without monitor
  connected) inserting the HDMI cable works fine and i can use the
  monitor and laptop screen without any problem.

  I have installed the preferred nVida proprietary driver. Also it does
  not matter if booting with nVidia selected or Intel selected.

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

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

[Kernel-packages] [Bug 1874194] apport information

[Max Barth]

ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  max1804 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-04-30 (14 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Acer Aspire VN7-592G
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=ab475c17-6be6-426b-97b2-179a498b8a14 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-29-generic N/A
 linux-backports-modules-5.4.0-29-generic  N/A
 linux-firmware1.187
Tags:  focal
Uname: Linux 5.4.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/06/2016
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.12
dmi.board.name: Aspire VN7-592G
dmi.board.vendor: Acer
dmi.board.version: V1.12
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.12
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.12:bd10/06/2016:svnAcer:pnAspireVN7-592G:pvrV1.12:rvnAcer:rnAspireVN7-592G:rvrV1.12:cvnAcer:ct10:cvrV1.12:
dmi.product.family: SKL
dmi.product.name: Aspire VN7-592G
dmi.product.sku: Aspire VN7-592G_1039_1.12
dmi.product.version: V1.12
dmi.sys.vendor: Acer

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

Title:
  Ubuntu 20.04 HDMI connected, no boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 20.04 (using the image created on 20 april) on
  my Dell XPS15 9560. This laptop has a Intel / nVidia combo.

  The problem i am facing is that when i have an external monitor
  connected to the laptop through the HDMI connector of the laptop,
  Ubuntu does not boot and hangs on the splash screen. I have not found
  any way to get logging on any kind.

  Before i was running Ubuntu 18.04 and did not have any problems with
  the monitor and HDMI cable. After boot is finished (without monitor
  connected) inserting the HDMI cable works fine and i can use the
  monitor and laptop screen without any problem.

  I have installed the preferred nVida proprietary driver. Also it does
  not matter if booting with nVidia selected or Intel selected.

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

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

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

[Max Barth]

apport information

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

Title:
  Ubuntu 20.04 HDMI connected, no boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 20.04 (using the image created on 20 april) on
  my Dell XPS15 9560. This laptop has a Intel / nVidia combo.

  The problem i am facing is that when i have an external monitor
  connected to the laptop through the HDMI connector of the laptop,
  Ubuntu does not boot and hangs on the splash screen. I have not found
  any way to get logging on any kind.

  Before i was running Ubuntu 18.04 and did not have any problems with
  the monitor and HDMI cable. After boot is finished (without monitor
  connected) inserting the HDMI cable works fine and i can use the
  monitor and laptop screen without any problem.

  I have installed the preferred nVida proprietary driver. Also it does
  not matter if booting with nVidia selected or Intel selected.

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

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

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

[Max Barth]

apport information

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

Title:
  Ubuntu 20.04 HDMI connected, no boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 20.04 (using the image created on 20 april) on
  my Dell XPS15 9560. This laptop has a Intel / nVidia combo.

  The problem i am facing is that when i have an external monitor
  connected to the laptop through the HDMI connector of the laptop,
  Ubuntu does not boot and hangs on the splash screen. I have not found
  any way to get logging on any kind.

  Before i was running Ubuntu 18.04 and did not have any problems with
  the monitor and HDMI cable. After boot is finished (without monitor
  connected) inserting the HDMI cable works fine and i can use the
  monitor and laptop screen without any problem.

  I have installed the preferred nVida proprietary driver. Also it does
  not matter if booting with nVidia selected or Intel selected.

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

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

[Kernel-packages] [Bug 1874194] Re: Ubuntu 20.04 HDMI connected, no boot

[Max Barth]

Same here on Acer Nitro BE with intel + Nvidia Graphics 
Mesa Intel® HD Graphics 530 (SKL GT2)
NVIDIA Corporation GM107M [GeForce GTX 960M] (rev a2)


** Tags added: apport-collected

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

Title:
  Ubuntu 20.04 HDMI connected, no boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 20.04 (using the image created on 20 april) on
  my Dell XPS15 9560. This laptop has a Intel / nVidia combo.

  The problem i am facing is that when i have an external monitor
  connected to the laptop through the HDMI connector of the laptop,
  Ubuntu does not boot and hangs on the splash screen. I have not found
  any way to get logging on any kind.

  Before i was running Ubuntu 18.04 and did not have any problems with
  the monitor and HDMI cable. After boot is finished (without monitor
  connected) inserting the HDMI cable works fine and i can use the
  monitor and laptop screen without any problem.

  I have installed the preferred nVida proprietary driver. Also it does
  not matter if booting with nVidia selected or Intel selected.

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

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

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

[Max Barth]

apport information

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

Title:
  Ubuntu 20.04 HDMI connected, no boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 20.04 (using the image created on 20 april) on
  my Dell XPS15 9560. This laptop has a Intel / nVidia combo.

  The problem i am facing is that when i have an external monitor
  connected to the laptop through the HDMI connector of the laptop,
  Ubuntu does not boot and hangs on the splash screen. I have not found
  any way to get logging on any kind.

  Before i was running Ubuntu 18.04 and did not have any problems with
  the monitor and HDMI cable. After boot is finished (without monitor
  connected) inserting the HDMI cable works fine and i can use the
  monitor and laptop screen without any problem.

  I have installed the preferred nVida proprietary driver. Also it does
  not matter if booting with nVidia selected or Intel selected.

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

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

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

[Max Barth]

apport information

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

Title:
  Ubuntu 20.04 HDMI connected, no boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 20.04 (using the image created on 20 april) on
  my Dell XPS15 9560. This laptop has a Intel / nVidia combo.

  The problem i am facing is that when i have an external monitor
  connected to the laptop through the HDMI connector of the laptop,
  Ubuntu does not boot and hangs on the splash screen. I have not found
  any way to get logging on any kind.

  Before i was running Ubuntu 18.04 and did not have any problems with
  the monitor and HDMI cable. After boot is finished (without monitor
  connected) inserting the HDMI cable works fine and i can use the
  monitor and laptop screen without any problem.

  I have installed the preferred nVida proprietary driver. Also it does
  not matter if booting with nVidia selected or Intel selected.

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

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

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

[Max Barth]

apport information

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

Title:
  Ubuntu 20.04 HDMI connected, no boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 20.04 (using the image created on 20 april) on
  my Dell XPS15 9560. This laptop has a Intel / nVidia combo.

  The problem i am facing is that when i have an external monitor
  connected to the laptop through the HDMI connector of the laptop,
  Ubuntu does not boot and hangs on the splash screen. I have not found
  any way to get logging on any kind.

  Before i was running Ubuntu 18.04 and did not have any problems with
  the monitor and HDMI cable. After boot is finished (without monitor
  connected) inserting the HDMI cable works fine and i can use the
  monitor and laptop screen without any problem.

  I have installed the preferred nVida proprietary driver. Also it does
  not matter if booting with nVidia selected or Intel selected.

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

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

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

[Max Barth]

apport information

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

Title:
  Ubuntu 20.04 HDMI connected, no boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 20.04 (using the image created on 20 april) on
  my Dell XPS15 9560. This laptop has a Intel / nVidia combo.

  The problem i am facing is that when i have an external monitor
  connected to the laptop through the HDMI connector of the laptop,
  Ubuntu does not boot and hangs on the splash screen. I have not found
  any way to get logging on any kind.

  Before i was running Ubuntu 18.04 and did not have any problems with
  the monitor and HDMI cable. After boot is finished (without monitor
  connected) inserting the HDMI cable works fine and i can use the
  monitor and laptop screen without any problem.

  I have installed the preferred nVida proprietary driver. Also it does
  not matter if booting with nVidia selected or Intel selected.

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

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

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

[Max Barth]

apport information

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

Title:
  Ubuntu 20.04 HDMI connected, no boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 20.04 (using the image created on 20 april) on
  my Dell XPS15 9560. This laptop has a Intel / nVidia combo.

  The problem i am facing is that when i have an external monitor
  connected to the laptop through the HDMI connector of the laptop,
  Ubuntu does not boot and hangs on the splash screen. I have not found
  any way to get logging on any kind.

  Before i was running Ubuntu 18.04 and did not have any problems with
  the monitor and HDMI cable. After boot is finished (without monitor
  connected) inserting the HDMI cable works fine and i can use the
  monitor and laptop screen without any problem.

  I have installed the preferred nVida proprietary driver. Also it does
  not matter if booting with nVidia selected or Intel selected.

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

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

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

[Max Barth]

apport information

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

Title:
  Ubuntu 20.04 HDMI connected, no boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 20.04 (using the image created on 20 april) on
  my Dell XPS15 9560. This laptop has a Intel / nVidia combo.

  The problem i am facing is that when i have an external monitor
  connected to the laptop through the HDMI connector of the laptop,
  Ubuntu does not boot and hangs on the splash screen. I have not found
  any way to get logging on any kind.

  Before i was running Ubuntu 18.04 and did not have any problems with
  the monitor and HDMI cable. After boot is finished (without monitor
  connected) inserting the HDMI cable works fine and i can use the
  monitor and laptop screen without any problem.

  I have installed the preferred nVida proprietary driver. Also it does
  not matter if booting with nVidia selected or Intel selected.

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

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

[Kernel-packages] [Bug 1874194] AlsaInfo.txt

[Max Barth]

apport information

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

Title:
  Ubuntu 20.04 HDMI connected, no boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 20.04 (using the image created on 20 april) on
  my Dell XPS15 9560. This laptop has a Intel / nVidia combo.

  The problem i am facing is that when i have an external monitor
  connected to the laptop through the HDMI connector of the laptop,
  Ubuntu does not boot and hangs on the splash screen. I have not found
  any way to get logging on any kind.

  Before i was running Ubuntu 18.04 and did not have any problems with
  the monitor and HDMI cable. After boot is finished (without monitor
  connected) inserting the HDMI cable works fine and i can use the
  monitor and laptop screen without any problem.

  I have installed the preferred nVida proprietary driver. Also it does
  not matter if booting with nVidia selected or Intel selected.

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

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

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

[Max Barth]

apport information

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

Title:
  Ubuntu 20.04 HDMI connected, no boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 20.04 (using the image created on 20 april) on
  my Dell XPS15 9560. This laptop has a Intel / nVidia combo.

  The problem i am facing is that when i have an external monitor
  connected to the laptop through the HDMI connector of the laptop,
  Ubuntu does not boot and hangs on the splash screen. I have not found
  any way to get logging on any kind.

  Before i was running Ubuntu 18.04 and did not have any problems with
  the monitor and HDMI cable. After boot is finished (without monitor
  connected) inserting the HDMI cable works fine and i can use the
  monitor and laptop screen without any problem.

  I have installed the preferred nVida proprietary driver. Also it does
  not matter if booting with nVidia selected or Intel selected.

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

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

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

[Max Barth]

apport information

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

Title:
  Ubuntu 20.04 HDMI connected, no boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 20.04 (using the image created on 20 april) on
  my Dell XPS15 9560. This laptop has a Intel / nVidia combo.

  The problem i am facing is that when i have an external monitor
  connected to the laptop through the HDMI connector of the laptop,
  Ubuntu does not boot and hangs on the splash screen. I have not found
  any way to get logging on any kind.

  Before i was running Ubuntu 18.04 and did not have any problems with
  the monitor and HDMI cable. After boot is finished (without monitor
  connected) inserting the HDMI cable works fine and i can use the
  monitor and laptop screen without any problem.

  I have installed the preferred nVida proprietary driver. Also it does
  not matter if booting with nVidia selected or Intel selected.

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

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

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

[Max Barth]

apport information

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

Title:
  Ubuntu 20.04 HDMI connected, no boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 20.04 (using the image created on 20 april) on
  my Dell XPS15 9560. This laptop has a Intel / nVidia combo.

  The problem i am facing is that when i have an external monitor
  connected to the laptop through the HDMI connector of the laptop,
  Ubuntu does not boot and hangs on the splash screen. I have not found
  any way to get logging on any kind.

  Before i was running Ubuntu 18.04 and did not have any problems with
  the monitor and HDMI cable. After boot is finished (without monitor
  connected) inserting the HDMI cable works fine and i can use the
  monitor and laptop screen without any problem.

  I have installed the preferred nVida proprietary driver. Also it does
  not matter if booting with nVidia selected or Intel selected.

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

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

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

[Max Barth]

apport information

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

Title:
  Ubuntu 20.04 HDMI connected, no boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 20.04 (using the image created on 20 april) on
  my Dell XPS15 9560. This laptop has a Intel / nVidia combo.

  The problem i am facing is that when i have an external monitor
  connected to the laptop through the HDMI connector of the laptop,
  Ubuntu does not boot and hangs on the splash screen. I have not found
  any way to get logging on any kind.

  Before i was running Ubuntu 18.04 and did not have any problems with
  the monitor and HDMI cable. After boot is finished (without monitor
  connected) inserting the HDMI cable works fine and i can use the
  monitor and laptop screen without any problem.

  I have installed the preferred nVida proprietary driver. Also it does
  not matter if booting with nVidia selected or Intel selected.

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

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

[Kernel-packages] [Bug 1878919] 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/1878919

Title:
  kworker/0:1+kacpid uses 100% of one CPU core

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  At some point, kworker/0:1+kacpid starts using 100% of one CPU's core;
  this can be seen in the top command.

  I captured some performance data via the following command:
  $ perf record -g -a sleep 10

  Then, perf report gives the following:


  Samples: 75K of event 'cycles', Event count (approx.): 44710762967
Children  Self  Command  Shared Object  
 Symbol
  +   65,46% 0,00%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] ret_from_fork
  +   65,46% 0,00%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] kthread
  +   65,46% 0,00%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] worker_thread
  +   65,44% 0,00%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] process_one_work
  +   65,44% 0,00%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] acpi_os_execute_deferred
  +   65,33% 0,00%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] acpi_ev_asynch_execute_gpe_method
  +   65,32% 0,00%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] acpi_ns_evaluate
  +   65,26% 0,00%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] acpi_ps_execute_method
  +   65,16% 0,06%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] acpi_ps_parse_aml
  +   61,00% 0,94%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] acpi_ps_parse_loop
  +   37,83% 0,75%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] acpi_ds_exec_end_op
  +   18,33% 0,04%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] acpi_ds_evaluate_name_path
  +   16,12% 0,23%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] acpi_ns_lookup
  +   15,79% 0,20%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] acpi_ns_search_and_enter
  +   15,23%14,99%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] acpi_ns_search_one_scope
  +   14,38% 0,00%  swapper  [kernel.kallsyms]  
 [k] secondary_startup_64
  +   14,38% 0,02%  swapper  [kernel.kallsyms]  
 [k] cpu_startup_entry
  +   14,31% 0,12%  swapper  [kernel.kallsyms]  
 [k] do_idle
  +   13,79% 0,00%  swapper  [kernel.kallsyms]  
 [k] start_secondary
  +   12,92% 0,03%  swapper  [kernel.kallsyms]  
 [k] call_cpuidle
  +   12,89% 0,00%  swapper  [kernel.kallsyms]  
 [k] cpuidle_enter
  +   12,85% 0,05%  swapper  [kernel.kallsyms]  
 [k] cpuidle_enter_state
  +   12,35% 2,15%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] acpi_ut_update_object_reference
  +   12,05% 0,28%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] acpi_ex_resolve_to_value
  +   10,40% 0,04%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] acpi_ex_resolve_node_to_value
  +9,90% 0,44%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] acpi_ds_create_operand
  +9,50% 0,05%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] acpi_ex_read_data_from_field
  +9,39% 0,06%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] acpi_ex_field_datum_io
  +9,26% 0,12%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] acpi_ex_access_region
  +9,23% 0,08%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] acpi_ps_get_next_namepath
  +9,15% 1,28%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] acpi_ut_update_ref_count.part.0
  +9,01% 0,08%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] acpi_ev_address_space_dispatch
  +8,96% 0,14%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] acpi_ex_extract_from_field
  +8,78% 7,70%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] acpi_ex_system_memory_space_handler
  +7,81% 0,22%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] acpi_ut_remove_reference
  +6,63% 6,43%  swapper  [kernel.kallsyms]  
 [k] intel_idle
  +5,31% 0,68%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] acpi_ps_create_op
  +5,12% 0,08%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] acpi_ut_add_reference
  +4,89% 0,07%  kworker/0:1+kac  [kernel.kallsyms]  
 [k] acpi_ds_delete_result_if_not_used

[Kernel-packages] [Bug 1877887] Re: [USB-Audio - Scarlett 2i2 USB, playback] fails after a while

[Kai-Heng Feng]

Ok, please test latest mainline kernel.

This commit may fix the issue:
commit 93ceaa808e8defc67ebca1396e2f42f812a2efc0
Author: Mathias Nyman 
Date:   Tue Apr 21 17:08:20 2020 +0300

xhci: Fix handling halted endpoint even if endpoint ring appears
empty

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

Title:
  [USB-Audio - Scarlett 2i2 USB, playback] fails after a while

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am encountering some very bizarre and difficult to reliably
  replicate issues.

  I am using a Focusrite Scarlett 2i2 USB audio interface, and am having
  a number of issues that I did not have in older version of ubuntu
  (these issues started occuring sometime in 19.04-19.10, can't remember
  which).

  I am having three major issues. Number one is, if USB autosuspend is
  enabled, it will stop working completely until reboot after anywhere
  from a few minutes to several hours. Reconnecting the device does not
  fix it and it seems to not power on at all, with dmesg reporting a
  "usb_set_interface failed -110" error. Sometimes this bug can be
  recreated by manually disconnecting and reconnecting the device,
  however I was unable to replicate it in this manner at the time of
  filing the bug.

  EDIT: Ignore the two more issue below, however I'm leaving them in the
  post in case they end up being relevant.

  Another (presumably related) issue I am having is that if I reconnect
  the device and it doesn't fail, it outputs very crackly audio, as if
  the bitrate or sample rate were set incorrectly. This persists until a
  restart of pulseaudio. Previously, I had a similar bug where it would
  randomly start doing the crackly audio thing until reconnecting the
  device and in this case a restart of pulse did *not* fix the problem.
  I am unsure if this issue still happens as it was fairly rare.

  The third problem is that sometimes when performing a suspend/wake
  cycle, the interface will power cycle several times, in intervals of
  15-30 seconds or so before staying on properly.

  As previously mentioned, these issues are fairly new and did not occur
  in older versions of ubuntu. I have confirmed that the audio interface
  works fine under windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun May 10 14:09:28 2020
  InstallationDate: Installed on 2020-05-08 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: USB-Audio - microKEY-37
  Symptom_PulseAudioLog:

  Symptom_Type: Sound works for a while, then breaks
  Title: [USB-Audio - Scarlett 2i2 USB, playback] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-08 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   enp37s0   no wireless extensions.

   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=UUID=6108192f-9dc3-480d-9a32-517609064dcd ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:

  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:

  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends 

[Kernel-packages] [Bug 1864132] Re: g_ether missing eem support

[Juerg Haefliger]

Is this still an issue with a current focal image from
http://cdimage.ubuntu.com/releases/20.04/release/?

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

Title:
  g_ether missing eem support

Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Eoan:
  New

Bug description:
  I am looking into enabling EEM with g_ether by module option
  use_eem=1, and g_ether won't be loaded because it has no EEM support
  compiled.

  Expected: EEM is compiled with g_ether (no such option for g_cdc) so
  that it can be enabled by use_eem=1.

  My "/sys/module/g_ether/parameters":
  -r--r--r-- 1 root root 4096 Feb 20 13:40 bcdDevice
  -r--r--r-- 1 root root 4096 Feb 20 13:40 dev_addr
  -r--r--r-- 1 root root 4096 Feb 20 13:40 host_addr
  -r--r--r-- 1 root root 4096 Feb 20 13:40 iManufacturer
  -r--r--r-- 1 root root 4096 Feb 20 13:40 iProduct
  -r--r--r-- 1 root root 4096 Feb 20 13:40 iSerialNumber
  -r--r--r-- 1 root root 4096 Feb 20 13:40 idProduct
  -r--r--r-- 1 root root 4096 Feb 20 13:40 idVendor
  -rw-r--r-- 1 root root 4096 Feb 20 14:08 qmult

  modinfo g_ether:
  parm:   idVendor:USB Vendor ID (ushort)
  parm:   idProduct:USB Product ID (ushort)
  parm:   bcdDevice:USB Device version (BCD) (ushort)
  parm:   iSerialNumber:SerialNumber string (charp)
  parm:   iManufacturer:USB Manufacturer string (charp)
  parm:   iProduct:USB Product string (charp)
  parm:   qmult:queue length multiplier at high/super speed (uint)
  parm:   dev_addr:Device Ethernet Address (charp)
  parm:   host_addr:Host Ethernet Address (charp)
  parm:   use_eem:use CDC EEM mode (bool)

  dmesg:
  ...
  [4.474689] udc-core: couldn't find an available UDC - added [g_ether] to 
list of pending drivers
  ...
  [5.768660] dwc2 fe98.usb: EPs: 8, dedicated fifos, 4080 entries in 
SPRAM
  [5.772414] g_ether fe98.usb: failed to start g_ether: -2
  ...

   should it be another bug? -
  There is another issue that when my laptop is connected and the with my Pi 4 
reboot, the cdc_ether function provided to my laptop will not be available 
again until I reconnect the cable (I have USB Y-cable + type-c adapter so I can 
unplug on laptop side w/o Pi 4 losing power).  I remember it was working as 
expected when I was testing out OTG function.

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

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

[Kernel-packages] [Bug 1871977] Re: g_ether not working after reboot

[Juerg Haefliger]

I believe this is fixed in Focal. Can you check if this is still an
issue for you with a current image from
http://cdimage.ubuntu.com/releases/20.04/release/?

After rebooting a Pi running a current Focal image I get (on the
connected host):

May 15 15:28:51 smeagol kernel: [ 3824.785702] usb 1-2: new high-speed USB 
device number 28 using xhci_hcd
May 15 15:28:56 smeagol kernel: [ 3829.845566] xhci_hcd :00:14.0: Timeout 
while waiting for setup device command
May 15 15:29:02 smeagol kernel: [ 3835.221286] xhci_hcd :00:14.0: Timeout 
while waiting for setup device command
May 15 15:29:02 smeagol kernel: [ 3835.429202] usb 1-2: device not accepting 
address 28, error -62
May 15 15:29:02 smeagol kernel: [ 3835.557210] usb 1-2: new high-speed USB 
device number 29 using xhci_hcd
May 15 15:29:07 smeagol kernel: [ 3840.597042] xhci_hcd :00:14.0: Timeout 
while waiting for setup device command
May 15 15:29:12 smeagol kernel: [ 3845.972785] xhci_hcd :00:14.0: Timeout 
while waiting for setup device command
May 15 15:29:13 smeagol kernel: [ 3846.180713] usb 1-2: device not accepting 
address 29, error -62
May 15 15:29:13 smeagol kernel: [ 3846.180894] usb usb1-port2: attempt power 
cycle
May 15 15:29:13 smeagol kernel: [ 3846.832715] usb 1-2: new high-speed USB 
device number 30 using xhci_hcd
May 15 15:29:18 smeagol kernel: [ 3851.988499] usb 1-2: device descriptor 
read/64, error -110
May 15 15:29:34 smeagol kernel: [ 3867.603793] usb 1-2: device descriptor 
read/64, error -110
May 15 15:29:34 smeagol kernel: [ 3867.839763] usb 1-2: new high-speed USB 
device number 31 using xhci_hcd
May 15 15:29:39 smeagol kernel: [ 3872.979541] usb 1-2: device descriptor 
read/64, error -110


And after loading g_{cdc,ether} on the Pi:

May 15 15:29:55 smeagol kernel: [ 3888.702904] usb usb1-port2: unable to 
enumerate USB device
May 15 15:30:22 smeagol kernel: [ 3915.165600] usb 1-2: new high-speed USB 
device number 32 using xhci_hcd
May 15 15:30:22 smeagol kernel: [ 3915.186797] usb 1-2: New USB device found, 
idVendor=0525, idProduct=a4a2, bcdDevice= 5.04
May 15 15:30:22 smeagol kernel: [ 3915.186805] usb 1-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=0
May 15 15:30:22 smeagol kernel: [ 3915.186811] usb 1-2: Product: RNDIS/Ethernet 
Gadget
May 15 15:30:22 smeagol kernel: [ 3915.186815] usb 1-2: Manufacturer: Linux 
5.4.0-1010-raspi with fe98.usb
May 15 15:30:22 smeagol kernel: [ 3915.192463] cdc_ether 1-2:1.0 usb0: register 
'cdc_ether' at usb-:00:14.0-2, CDC Ethernet Device, a6:b3:33:a5:9e:5c
May 15 15:30:22 smeagol kernel: [ 3915.225267] cdc_ether 1-2:1.0 
enxa6b333a59e5c: renamed from usb0


And the connected host reports:
$ lsusb 

Bus 001 Device 032: ID 0525:a4a2 Netchip Technology, Inc. Linux-USB 
Ethernet/RNDIS Gadget


So from my POV this looks as good as it gets. Please confirm.

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

Title:
  g_ether not working after reboot

Status in linux-raspi package in Ubuntu:
  Incomplete
Status in linux-raspi2 package in Ubuntu:
  Incomplete
Status in linux-raspi2 source package in Eoan:
  New
Status in linux-raspi source package in Focal:
  Confirmed

Bug description:
  There is an issue with g_ether after warm reboot.

  Hardware I used for testing:

  Thinkpad L470 + Dock, Ubuntu 19.10
  USB 3.0 "A male-plug Y-cable" + USB-A to USB-C adapter
  Pi4 4GB powered by Y-cable connecting to dock and separate USB PSU, Ubuntu 
19.10

  ==
  it seems like whenever I reboot my Pi, USB gadget port is not detected.  How 
to reproduce:

  1) make sure g_ether works on Pi 4
  2) make sure cdc_ether works on L470, as in dmesg it shows...
  [112961.147030] usb 1-3.2: new high-speed USB device number 11 using xhci_hcd
  [112961.237399] usb 1-3.2: New USB device found, idVendor=045e, 
idProduct=0301, bcdDevice= 5.03
  [112961.237406] usb 1-3.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [112961.237411] usb 1-3.2: Product: USB Adapter
  [112961.237414] usb 1-3.2: Manufacturer: Raspberry Pi
  [112961.237418] usb 1-3.2: SerialNumber: ***MASKED***
  [112961.245067] cdc_ether 1-3.2:1.0 eth1: register 'cdc_ether' at 
usb-:00:14.0-3.2, CDC Ethernet Device, ***MASKED***
  3) verify IP connectivity works from L470 to Pi 4.
  4) reboot Pi 4; on L470 it shows:
  [113343.783925] usb 1-3.2: USB disconnect, device number 11
  [113343.784164] cdc_ether 1-3.2:1.0 eth1: unregister 'cdc_ether' 
usb-:00:14.0-3.2, CDC Ethernet Device
  5) wait for Pi 4 to become available (I use wifi on Pi 4 + ssh on L470)
  ==

  Expected: Pi4 should show up to L470 as USB ethernet gadget after warm reboot
  Actual: g_ether is loaded on Pi4 but L470 does not detect it
  Workaround: unplug Pi4 and plug in again, it will work;  given that I am 
using Y-cable, unplugging will not power down Pi 

[Kernel-packages] [Bug 1877887] Re: [USB-Audio - Scarlett 2i2 USB, playback] fails after a while

[MIchael Porter]

> 0x202a0 means it's no longer connected. This can be a hardware or
firmware bug.

I believe this is to be expected. I unplugged the device at this point
to show that plugging it back in does not fix the problem. If you keep
going down you will see it flounder when I attempt to reconnect the
device.

[ 1559.761720] xhci_hcd :03:00.0: Cancel URB 2a63aa76, dev
2.1, ep 0x83, starting at offset 0xff04be90

Is the line that I believe is when the device locked up.

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

Title:
  [USB-Audio - Scarlett 2i2 USB, playback] fails after a while

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am encountering some very bizarre and difficult to reliably
  replicate issues.

  I am using a Focusrite Scarlett 2i2 USB audio interface, and am having
  a number of issues that I did not have in older version of ubuntu
  (these issues started occuring sometime in 19.04-19.10, can't remember
  which).

  I am having three major issues. Number one is, if USB autosuspend is
  enabled, it will stop working completely until reboot after anywhere
  from a few minutes to several hours. Reconnecting the device does not
  fix it and it seems to not power on at all, with dmesg reporting a
  "usb_set_interface failed -110" error. Sometimes this bug can be
  recreated by manually disconnecting and reconnecting the device,
  however I was unable to replicate it in this manner at the time of
  filing the bug.

  EDIT: Ignore the two more issue below, however I'm leaving them in the
  post in case they end up being relevant.

  Another (presumably related) issue I am having is that if I reconnect
  the device and it doesn't fail, it outputs very crackly audio, as if
  the bitrate or sample rate were set incorrectly. This persists until a
  restart of pulseaudio. Previously, I had a similar bug where it would
  randomly start doing the crackly audio thing until reconnecting the
  device and in this case a restart of pulse did *not* fix the problem.
  I am unsure if this issue still happens as it was fairly rare.

  The third problem is that sometimes when performing a suspend/wake
  cycle, the interface will power cycle several times, in intervals of
  15-30 seconds or so before staying on properly.

  As previously mentioned, these issues are fairly new and did not occur
  in older versions of ubuntu. I have confirmed that the audio interface
  works fine under windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun May 10 14:09:28 2020
  InstallationDate: Installed on 2020-05-08 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: USB-Audio - microKEY-37
  Symptom_PulseAudioLog:

  Symptom_Type: Sound works for a while, then breaks
  Title: [USB-Audio - Scarlett 2i2 USB, playback] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-08 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   enp37s0   no wireless extensions.

   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=UUID=6108192f-9dc3-480d-9a32-517609064dcd ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:

  Tags:  focal
  Uname: 

[Kernel-packages] [Bug 1878919] [NEW] kworker/0:1+kacpid uses 100% of one CPU core

[Martin Vysny]

Public bug reported:

At some point, kworker/0:1+kacpid starts using 100% of one CPU's core;
this can be seen in the top command.

I captured some performance data via the following command:
$ perf record -g -a sleep 10

Then, perf report gives the following:


Samples: 75K of event 'cycles', Event count (approx.): 44710762967
  Children  Self  Command  Shared Object   
Symbol
+   65,46% 0,00%  kworker/0:1+kac  [kernel.kallsyms]   
[k] ret_from_fork
+   65,46% 0,00%  kworker/0:1+kac  [kernel.kallsyms]   
[k] kthread
+   65,46% 0,00%  kworker/0:1+kac  [kernel.kallsyms]   
[k] worker_thread
+   65,44% 0,00%  kworker/0:1+kac  [kernel.kallsyms]   
[k] process_one_work
+   65,44% 0,00%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_os_execute_deferred
+   65,33% 0,00%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ev_asynch_execute_gpe_method
+   65,32% 0,00%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ns_evaluate
+   65,26% 0,00%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ps_execute_method
+   65,16% 0,06%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ps_parse_aml
+   61,00% 0,94%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ps_parse_loop
+   37,83% 0,75%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ds_exec_end_op
+   18,33% 0,04%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ds_evaluate_name_path
+   16,12% 0,23%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ns_lookup
+   15,79% 0,20%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ns_search_and_enter
+   15,23%14,99%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ns_search_one_scope
+   14,38% 0,00%  swapper  [kernel.kallsyms]   
[k] secondary_startup_64
+   14,38% 0,02%  swapper  [kernel.kallsyms]   
[k] cpu_startup_entry
+   14,31% 0,12%  swapper  [kernel.kallsyms]   
[k] do_idle
+   13,79% 0,00%  swapper  [kernel.kallsyms]   
[k] start_secondary
+   12,92% 0,03%  swapper  [kernel.kallsyms]   
[k] call_cpuidle
+   12,89% 0,00%  swapper  [kernel.kallsyms]   
[k] cpuidle_enter
+   12,85% 0,05%  swapper  [kernel.kallsyms]   
[k] cpuidle_enter_state
+   12,35% 2,15%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ut_update_object_reference
+   12,05% 0,28%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ex_resolve_to_value
+   10,40% 0,04%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ex_resolve_node_to_value
+9,90% 0,44%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ds_create_operand
+9,50% 0,05%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ex_read_data_from_field
+9,39% 0,06%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ex_field_datum_io
+9,26% 0,12%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ex_access_region
+9,23% 0,08%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ps_get_next_namepath
+9,15% 1,28%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ut_update_ref_count.part.0
+9,01% 0,08%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ev_address_space_dispatch
+8,96% 0,14%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ex_extract_from_field
+8,78% 7,70%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ex_system_memory_space_handler
+7,81% 0,22%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ut_remove_reference
+6,63% 6,43%  swapper  [kernel.kallsyms]   
[k] intel_idle
+5,31% 0,68%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ps_create_op
+5,12% 0,08%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ut_add_reference
+4,89% 0,07%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ds_delete_result_if_not_used
+4,71% 0,09%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ds_do_implicit_return
+4,61% 0,17%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ds_is_result_used
+3,91% 3,62%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ut_track_stack_ptr
+3,83% 0,31%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ps_complete_op
+3,39% 

[Kernel-packages] [Bug 1873325] Re: update-initramfs complains of missing amdgpu firmware files

[Seth Forshee]

** Description changed:

+ SRU Justification
+ 
+ Impact: amdgpu references firmware files in modinfo which have not been
+ supplied to linux-firmware. This causes update-initramfs to generate
+ "Possible missing firmware" warnings.
+ 
+ Fix: Since the firmware is not available, all we can do is remove the
+ files from modinfo.
+ 
+ Test Case: Confirm that update-initramfs no longer produces the
+ warnings.
+ 
+ Regression Potential: Low. If someone had managed to obtain these files
+ they will no longer be added to the initramfs, potentially causing
+ regressions for these users. This would be an atypical situation.
+ 
+ ---
+ 
  Ubuntu 20.04 during initramfs update reports missing firmware files:
  W: Possible missing firmware /lib/firmware/amdgpu/navi12_vcn.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/navi12_smc.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module 
amdgpu
  
  Kernel: 5.4.0-24-generic
  linux-firmware: 1.187

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

Title:
  update-initramfs complains of missing amdgpu firmware files

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  New

Bug description:
  SRU Justification

  Impact: amdgpu references firmware files in modinfo which have not
  been supplied to linux-firmware. This causes update-initramfs to
  generate "Possible missing firmware" warnings.

  Fix: Since the firmware is not available, all we can do is remove the
  files from modinfo.

  Test Case: Confirm that update-initramfs no longer produces the
  warnings.

  Regression Potential: Low. If someone had managed to obtain these
  files they will no longer be added to the initramfs, potentially
  causing regressions for these users. This would be an atypical
  situation.

  ---

  Ubuntu 20.04 during initramfs update reports missing firmware files:
  W: Possible missing firmware /lib/firmware/amdgpu/navi12_vcn.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/navi12_smc.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module 
amdgpu

  Kernel: 5.4.0-24-generic
  linux-firmware: 1.187

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

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

[Kernel-packages] [Bug 1878341] Re: Ubuntu 20.04 install image does not boot

[Jouni Mettala]

This panic is happening early in boot. No modules are linked in. We can assume 
it is not usb subsystem bug. This is from dmesg.
"pci :00:00.0:[Firmware Bug]: reg 0x1c: invalid BAR (can't size)".

It is perhaps possible to boot your usb with some boot paramater like
pci=nocrs https://wiki.ubuntu.com/Kernel/KernelBootParameters

If you happen to upgrade to focal via update-manager or do-release
upgrade it would be good to know does kernel still panic.

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

Title:
  Ubuntu 20.04 install image does not boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 20.04 LTS install image doesn't boot on my computer, where Ubuntu 
19.10 works just fine.
  CPU AMD Phenom II X4 965
  RAM Kingston, DDR3, 4 × 4 GiB
  MB Gigabyte GA-990XA-UD3 rev. 1.1, Last BIOS
  GPU Gigabyte Radeon RX 550
  Result is kernel panic.

  The same image on the same USB flash disk works on another computer, so 
problem isn't caused by corrupted image download or malfunctioned USB flash 
disk.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mermar 1791 F pulseaudio
   /dev/snd/controlC1:  mermar 1791 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-30 (197 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=1c03cde1-ba25-4c24-bd9b-31b9cf3051f6 ro
  ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-51-generic N/A
   linux-backports-modules-5.3.0-51-generic  N/A
   linux-firmware1.183.5
  RfKill:
   
  Tags:  eoan wayland-session
  Uname: Linux 5.3.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/09/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F14e
  dmi.board.name: GA-990XA-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF14e:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-990XA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990XA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-990XA-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1878670] Re: Gnome crash frequently

[Rex Tsai]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
 Assignee: (unassigned) => Leon Liao (lihow731)

** Changed in: oem-priority
   Importance: Undecided => Medium

** Changed in: oem-priority
   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/1878670

Title:
  Gnome crash frequently

Status in OEM Priority Project:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  The system freezes frequently then logs out.
  If happens at apparently random times, and using no particular app.

  Extract of syslog is attached.

  Requested info is below:

  1) release
  Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30)

  2) package version
  gnome-session:
Installeret: (ingen)
Kandidat:3.28.1-0ubuntu3
Versionstabel:
   3.28.1-0ubuntu3 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
   3.28.1-0ubuntu2 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) Gnome shouldn't crash

  4) Gnome crashed

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

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

[Kernel-packages] [Bug 1878918] 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/1878918

Title:
  Button power don’t shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  I realized that since I updated the system to version 20.04 it is not
  responding when I press the shutdown button on my notebook, even
  though in the power management in the settings it is to shut down when
  I press it. When I put it to suspend, he responds, but when I put it
  off he does nothing

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neto   1092 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Fri May 15 10:19:38 2020
  InstallationDate: Installed on 2020-02-28 (76 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/532U3C
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=7949306b-901a-4602-8b3f-ce5078d80526 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-09 (5 days ago)
  dmi.bios.date: 07/22/2015
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P13ABH
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP530U3C-AD5BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP13ABH:bd07/22/2015:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C/532U3C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP530U3C-AD5BR:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C/532U3C
  dmi.product.sku: System SKUNumber
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1878918] [NEW] Button power don’t shutdown

[Glauco Neto]

Public bug reported:

Description:Ubuntu 20.04 LTS
Release:20.04

I realized that since I updated the system to version 20.04 it is not
responding when I press the shutdown button on my notebook, even though
in the power management in the settings it is to shut down when I press
it. When I put it to suspend, he responds, but when I put it off he does
nothing

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-29-generic 5.4.0-29.33
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  neto   1092 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: Budgie:GNOME
Date: Fri May 15 10:19:38 2020
InstallationDate: Installed on 2020-02-28 (76 days ago)
InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/532U3C
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=7949306b-901a-4602-8b3f-ce5078d80526 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-29-generic N/A
 linux-backports-modules-5.4.0-29-generic  N/A
 linux-firmware1.187
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-05-09 (5 days ago)
dmi.bios.date: 07/22/2015
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P13ABH
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: NP530U3C-AD5BR
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP13ABH:bd07/22/2015:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C/532U3C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP530U3C-AD5BR:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.family: ChiefRiver System
dmi.product.name: 530U3C/530U4C/532U3C
dmi.product.sku: System SKUNumber
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


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

Title:
  Button power don’t shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  I realized that since I updated the system to version 20.04 it is not
  responding when I press the shutdown button on my notebook, even
  though in the power management in the settings it is to shut down when
  I press it. When I put it to suspend, he responds, but when I put it
  off he does nothing

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neto   1092 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Fri May 15 10:19:38 2020
  InstallationDate: Installed on 2020-02-28 (76 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/532U3C
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=7949306b-901a-4602-8b3f-ce5078d80526 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-09 (5 days ago)
  dmi.bios.date: 07/22/2015
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P13ABH
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP530U3C-AD5BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP13ABH:bd07/22/2015:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C/532U3C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP530U3C-AD5BR:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C/532U3C
  dmi.product.sku: System SKUNumber
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1871977] Re: g_ether not working after reboot

[Juerg Haefliger]

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

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

** No longer affects: linux-raspi (Ubuntu Eoan)

** No longer affects: linux-raspi2 (Ubuntu Focal)

** Changed in: linux-raspi (Ubuntu)
   Status: New => Incomplete

** Changed in: linux-raspi2 (Ubuntu)
   Status: New => Incomplete

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

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

Title:
  g_ether not working after reboot

Status in linux-raspi package in Ubuntu:
  Incomplete
Status in linux-raspi2 package in Ubuntu:
  Incomplete
Status in linux-raspi2 source package in Eoan:
  New
Status in linux-raspi source package in Focal:
  Confirmed

Bug description:
  There is an issue with g_ether after warm reboot.

  Hardware I used for testing:

  Thinkpad L470 + Dock, Ubuntu 19.10
  USB 3.0 "A male-plug Y-cable" + USB-A to USB-C adapter
  Pi4 4GB powered by Y-cable connecting to dock and separate USB PSU, Ubuntu 
19.10

  ==
  it seems like whenever I reboot my Pi, USB gadget port is not detected.  How 
to reproduce:

  1) make sure g_ether works on Pi 4
  2) make sure cdc_ether works on L470, as in dmesg it shows...
  [112961.147030] usb 1-3.2: new high-speed USB device number 11 using xhci_hcd
  [112961.237399] usb 1-3.2: New USB device found, idVendor=045e, 
idProduct=0301, bcdDevice= 5.03
  [112961.237406] usb 1-3.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [112961.237411] usb 1-3.2: Product: USB Adapter
  [112961.237414] usb 1-3.2: Manufacturer: Raspberry Pi
  [112961.237418] usb 1-3.2: SerialNumber: ***MASKED***
  [112961.245067] cdc_ether 1-3.2:1.0 eth1: register 'cdc_ether' at 
usb-:00:14.0-3.2, CDC Ethernet Device, ***MASKED***
  3) verify IP connectivity works from L470 to Pi 4.
  4) reboot Pi 4; on L470 it shows:
  [113343.783925] usb 1-3.2: USB disconnect, device number 11
  [113343.784164] cdc_ether 1-3.2:1.0 eth1: unregister 'cdc_ether' 
usb-:00:14.0-3.2, CDC Ethernet Device
  5) wait for Pi 4 to become available (I use wifi on Pi 4 + ssh on L470)
  ==

  Expected: Pi4 should show up to L470 as USB ethernet gadget after warm reboot
  Actual: g_ether is loaded on Pi4 but L470 does not detect it
  Workaround: unplug Pi4 and plug in again, it will work;  given that I am 
using Y-cable, unplugging will not power down Pi 4.
  Concern: lose connectivity that needs human intervention to correct, i.e. 
cannot do it remotely.

  Note: I remember it is detected okay before I file for bug #1861070,
  not sure if it is related or not.  using g_cdc should be the same, but
  not separately tested.

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

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

[Kernel-packages] [Bug 1873325] Re: update-initramfs complains of missing amdgpu firmware files

[Seth Forshee]

AMD has not released this firmware to linux-firmware. For now all we can
do is remove the files from modinfo so that update-initramfs will stop
complaining.

** Package changed: linux-firmware (Ubuntu) => linux (Ubuntu)

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

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

Title:
  update-initramfs complains of missing amdgpu firmware files

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  New

Bug description:
  Ubuntu 20.04 during initramfs update reports missing firmware files:
  W: Possible missing firmware /lib/firmware/amdgpu/navi12_vcn.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/navi12_smc.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module 
amdgpu

  Kernel: 5.4.0-24-generic
  linux-firmware: 1.187

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

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

[Kernel-packages] [Bug 1878670] Re: Gnome crash frequently

[Anthony Wong]

Hi Kurt,

I see you have a Ubuntu preload machine, we will try to see if we can reproduce 
your problem.
Meanwhile, please upload more details by apport-collect as Daniel said.

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

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

Title:
  Gnome crash frequently

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  The system freezes frequently then logs out.
  If happens at apparently random times, and using no particular app.

  Extract of syslog is attached.

  Requested info is below:

  1) release
  Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30)

  2) package version
  gnome-session:
Installeret: (ingen)
Kandidat:3.28.1-0ubuntu3
Versionstabel:
   3.28.1-0ubuntu3 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
   3.28.1-0ubuntu2 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) Gnome shouldn't crash

  4) Gnome crashed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878670/+subscriptions

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

[Kernel-packages] [Bug 1878907] 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/1878907

Title:
  package linux-image-3.13.0-55-generic 3.13.0-55.94 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 17

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  linux update error

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-55-generic 3.13.0-55.94
  ProcVersionSignature: Ubuntu 3.13.0-55.92-generic 3.13.11-ckt20
  Uname: Linux 3.13.0-55-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  emody  1906 F pulseaudio
  Date: Fri May 15 14:03:24 2020
  DuplicateSignature: 
package:linux-image-3.13.0-55-generic:3.13.0-55.94:subprocess installed 
post-installation script returned error exit status 17
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 17
  HibernationDevice: RESUME=UUID=27e9443b-f477-40c7-b543-282e6a516ecc
  InstallationDate: Installed on 2013-02-09 (2651 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MachineType: TOSHIBA Satellite L305
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-55-generic 
root=UUID=0946b065-28e5-49f1-bcca-563f551acbbd ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.17
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-3.13.0-55-generic 3.13.0-55.94 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 17
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (2217 days ago)
  dmi.bios.date: 09/23/2009
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.10:bd09/23/2009:svnTOSHIBA:pnSatelliteL305:pvrPSLB8U-13T038:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Satellite L305
  dmi.product.version: PSLB8U-13T038
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1877655] Re: [Dell Venue 11 Pro 7140] Trackpad does not work

[Tony Harris]

Any other suggestions for what I should try?

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

Title:
  [Dell Venue 11 Pro 7140] Trackpad does not work

Status in libinput package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery
  dock.  PopOS 20.04 fully updated.  I have experienced this bug on
  stock Ubuntu 20.04 as well as Kubuntu 20.04.

    When at the login page, the trackpad and keyboard operate as they
  should.  Once the login process is complete and the desktop is
  displayed, the keyboard still works as expected but the trackpad no
  longer controls the pointer.  The touch display still functions as
  expected but the trackpad on the keyboard dock doesn't work.

  The attached document is my device list, here is the evtest:

  Input driver version is 1.0.1
  Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111
  Input device name: "Synaptics T Pad V 01.31 Touchpad"
  Supported events:
    Event type 0 (EV_SYN)
    Event type 1 (EV_KEY)
  Event code 272 (BTN_LEFT)
  Event code 325 (BTN_TOOL_FINGER)
  Event code 330 (BTN_TOUCH)
  Event code 333 (BTN_TOOL_DOUBLETAP)
  Event code 334 (BTN_TOOL_TRIPLETAP)
    Event type 3 (EV_ABS)
  Event code 0 (ABS_X)
    Value483
    Min0
    Max 1056
    Resolution  12
  Event code 1 (ABS_Y)
    Value266
    Min0
    Max  516
    Resolution  12
  Event code 47 (ABS_MT_SLOT)
    Value  0
    Min0
    Max2
  Event code 53 (ABS_MT_POSITION_X)
    Value  0
    Min0
    Max 1056
    Resolution  12
  Event code 54 (ABS_MT_POSITION_Y)
    Value  0
    Min0
    Max  516
    Resolution  12
  Event code 55 (ABS_MT_TOOL_TYPE)
    Value  0
    Min0
    Max2
  Event code 57 (ABS_MT_TRACKING_ID)
    Value  0
    Min0
    Max65535
    Event type 4 (EV_MSC)
  Event code 5 (MSC_TIMESTAMP)
  Properties:
    Property type 0 (INPUT_PROP_POINTER)
    Property type 2 (INPUT_PROP_BUTTONPAD)
  Testing ... (interrupt to exit)

  I did try to remove xserver-xorg-input-synaptics, but it is not
  installed on 20.04.

  There is still an issue with Wayland and the trackpad, but it's different 
than Xorg so the problem may be in how Xorg is processing the trackpad (I 
honestly don't know) - in Wayland, it will work until I attempt to run the 
sofware center.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Pop!_OS 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5300 [1028:066b]
  MachineType: Dell Inc. Venue 11 Pro 7140
  Package: xorg-server (not installed)
  ProcKernelCmdLine: 
initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img 
root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 
systemd.show_status=false splash
  ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 
5.4.30
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-7626-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/10/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0XMVMH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7140
  dmi.product.sku: 066B
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1878623] Re: Dell Inspiron 1525 Laptop internal speakers not working

[Anthony Wong]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Hui Wang (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/1878623

Title:
  Dell Inspiron 1525 Laptop internal speakers not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded from ubuntu 19.10 to 20.04 recently. 20.04 is excellent for
  me other than the laptop internal speakers (e.g when watching you tube
  video) do not work/are not recognised in 20.04. The internal speakers
  did work in 19.10. I can still listen to sound via headphone socket
  and external speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alfred  983 F pulseaudio
   /dev/snd/pcmC0D0p:   alfred  983 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 15:09:01 2020
  InstallationDate: Installed on 2019-11-21 (174 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Inspiron 1525
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=44d00494-3bf6-479f-a3aa-582d0bc78c25 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-11 (2 days ago)
  dmi.bios.date: 10/16/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0U990C
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd10/16/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1878907] Re: package linux-image-3.13.0-55-generic 3.13.0-55.94 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-3.13.0-55-generic 3.13.0-55.94 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 17

Status in linux package in Ubuntu:
  New

Bug description:
  linux update error

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-55-generic 3.13.0-55.94
  ProcVersionSignature: Ubuntu 3.13.0-55.92-generic 3.13.11-ckt20
  Uname: Linux 3.13.0-55-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  emody  1906 F pulseaudio
  Date: Fri May 15 14:03:24 2020
  DuplicateSignature: 
package:linux-image-3.13.0-55-generic:3.13.0-55.94:subprocess installed 
post-installation script returned error exit status 17
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 17
  HibernationDevice: RESUME=UUID=27e9443b-f477-40c7-b543-282e6a516ecc
  InstallationDate: Installed on 2013-02-09 (2651 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MachineType: TOSHIBA Satellite L305
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-55-generic 
root=UUID=0946b065-28e5-49f1-bcca-563f551acbbd ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.17
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-3.13.0-55-generic 3.13.0-55.94 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 17
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (2217 days ago)
  dmi.bios.date: 09/23/2009
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.10:bd09/23/2009:svnTOSHIBA:pnSatelliteL305:pvrPSLB8U-13T038:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Satellite L305
  dmi.product.version: PSLB8U-13T038
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1878907] [NEW] package linux-image-3.13.0-55-generic 3.13.0-55.94 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17

[Emődy András]

Public bug reported:

linux update error

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-55-generic 3.13.0-55.94
ProcVersionSignature: Ubuntu 3.13.0-55.92-generic 3.13.11-ckt20
Uname: Linux 3.13.0-55-generic i686
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  emody  1906 F pulseaudio
Date: Fri May 15 14:03:24 2020
DuplicateSignature: 
package:linux-image-3.13.0-55-generic:3.13.0-55.94:subprocess installed 
post-installation script returned error exit status 17
ErrorMessage: subprocess installed post-installation script returned error exit 
status 17
HibernationDevice: RESUME=UUID=27e9443b-f477-40c7-b543-282e6a516ecc
InstallationDate: Installed on 2013-02-09 (2651 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
MachineType: TOSHIBA Satellite L305
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-55-generic 
root=UUID=0946b065-28e5-49f1-bcca-563f551acbbd ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.17
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: package linux-image-3.13.0-55-generic 3.13.0-55.94 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 17
UpgradeStatus: Upgraded to trusty on 2014-04-19 (2217 days ago)
dmi.bios.date: 09/23/2009
dmi.bios.vendor: INSYDE
dmi.bios.version: 2.10
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnINSYDE:bvr2.10:bd09/23/2009:svnTOSHIBA:pnSatelliteL305:pvrPSLB8U-13T038:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Satellite L305
dmi.product.version: PSLB8U-13T038
dmi.sys.vendor: TOSHIBA

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


** Tags: apport-package i386 trusty

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

Title:
  package linux-image-3.13.0-55-generic 3.13.0-55.94 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 17

Status in linux package in Ubuntu:
  New

Bug description:
  linux update error

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-55-generic 3.13.0-55.94
  ProcVersionSignature: Ubuntu 3.13.0-55.92-generic 3.13.11-ckt20
  Uname: Linux 3.13.0-55-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  emody  1906 F pulseaudio
  Date: Fri May 15 14:03:24 2020
  DuplicateSignature: 
package:linux-image-3.13.0-55-generic:3.13.0-55.94:subprocess installed 
post-installation script returned error exit status 17
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 17
  HibernationDevice: RESUME=UUID=27e9443b-f477-40c7-b543-282e6a516ecc
  InstallationDate: Installed on 2013-02-09 (2651 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MachineType: TOSHIBA Satellite L305
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-55-generic 
root=UUID=0946b065-28e5-49f1-bcca-563f551acbbd ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.17
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-3.13.0-55-generic 3.13.0-55.94 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 17
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (2217 days ago)
  dmi.bios.date: 09/23/2009
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.10:bd09/23/2009:svnTOSHIBA:pnSatelliteL305:pvrPSLB8U-13T038:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Satellite L305
  dmi.product.version: PSLB8U-13T038
  dmi.sys.vendor: TOSHIBA

To