Re: [Kernel-packages] [Bug 1871303] Re: [nvidia] Boot hangs up on initiating graphics. I can only finish the boot if I use the recovery mode.

[Kenneth]

Thank you have locating the error for me.

What should I do?

Ken

On Wed, Apr 8, 2020 at 6:01 AM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> Thanks. The problem indeed looks like it's confined to the Nvidia
> driver:
>
> Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]: (EE)
> NVIDIA(0): Failed to allocate software rendering cache surface: out of
> Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]: (EE)
> NVIDIA(0): memory.
> Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]: (EE)
> NVIDIA(0):  *** Aborting ***
> Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]: (EE)
> Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]: Fatal
> server error:
> Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]: (EE)
> NVIDIA: A GPU exception occurred during X server initialization(EE)
> Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]: (EE)
> Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]: Please
> consult the The X.Org Foundation support
> Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]:
> at http://wiki.x.org
> Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]:  for help.
> Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]: (EE)
> Please also check the log file at "/var/log/Xorg.0.log" for additional
> information.
> Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]: (EE)
> Apr 07 13:05:05 Kens-computer kernel: NVRM: GPU at PCI::01:00:
> GPU-0cbf6562-d7da-f433-1671-3edebe83dd01
> Apr 07 13:05:05 Kens-computer kernel: NVRM: Xid (PCI::01:00): 31, Ch
> 0008, engmask 0101, intr 1000
> Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]: (EE)
> Server terminated with error (1). Closing log file.
>
> ** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
>Status: Incomplete => New
>
> ** Summary changed:
>
> - [nvidia] Boot hangs up on initiating graphics. I can only finish the
> boot if I use the recovery mode.
> + [nvidia] Xorg crashes in (EE) NVIDIA(0): Failed to allocate software
> rendering cache surface: out of memory
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1871303
>
> Title:
>   [nvidia] Xorg crashes in (EE) NVIDIA(0): Failed to allocate software
>   rendering cache surface: out of memory
>
> Status in nvidia-graphics-drivers-390 package in Ubuntu:
>   New
>
> Bug description:
>   Boot hangs up on initiating graphics. I can only finish the boot if I
>   use the recovery mode.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: xorg 1:7.7+19ubuntu7.1
>   ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
>   Uname: Linux 4.15.0-91-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia
>   .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory:
> '/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.116  Sun Jan 27
> 07:21:36 PST 2019
>GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.9-0ubuntu7.14
>   Architecture: amd64
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: None
>   Date: Tue Apr  7 09:02:40 2020
>   DistUpgraded: Fresh install
>   DistroCodename: bionic
>   DistroVariant: ubuntu
>   DkmsStatus:
>nvidia, 390.116, 4.15.0-88-generic, x86_64: installed
>nvidia, 390.116, 4.15.0-91-generic, x86_64: installed
>   ExtraDebuggingInterest: Yes, if not too technical
>   GraphicsCard:
>NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1)
> (prog-if 00 [VGA controller])
>  Subsystem: ASUSTeK Computer Inc. GK208B [GeForce GT 710] [1043:8572]
>   InstallationDate: Installed on 2017-07-14 (997 days ago)
>   InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64
> (20170215.2)
>   MachineType: ASUS All Series
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic
> root=UUID=671dec46-62d2-4163-a941-c528578feb4d ro recovery nomodeset
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 05/14/2015
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 1103
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: H81M-K
>   dmi.board.vendor: ASUSTeK COMPUTER INC.
>   dmi.board.version: Rev X.0x
>   dmi.chassis.asset.tag: Asset-1234567890
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Chassis Manufacture
>   dmi.chassis.version: Chassis Version
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr1103:bd05/14/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
>   dmi.product.family: ASUS MB
>   

[Kernel-packages] [Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache

[Ryan Finnie]

I can confirm going from 4.15.0-88 to 4.15.0-91 on my bcache system
panics in the same way.  Here's my layout:

-> sd{c,d,f,g,h}: each 4TB gpt, sd{c,d,f,g,h}1: each type linux_raid_member
--> md0: raid6, sd{c,d,f,g,h}1
--> sda: 512GB gpt, sda1: type bcache
---> bcache0: md0 + sda1
> whatadisk_crypt: LUKS on bcache0
-> LVM VG whatadisk: whatadisk_crypt
--> multiple LVs

There are also a handful of other disks (for example, nvme0n1 is the
encrypted boot disk), but the layout above is the only part which bcache
touches.

Happy to help with additional info or testing, please let me know.

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

Title:
  Regression in kernel 4.15.0-91 causes kernel panic with Bcache

Status in linux package in Ubuntu:
  In Progress

Bug description:
  After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems
  does not boot any longer. It always crashes during boot with a kernel
  panic.

  I suspect that this crash might be related to Bcache because this is
  the only one of our systems where we use Bcache and the kernel panic
  appears right after Bcache initialization.

  I already checked that this bug still exists in the 4.15.0-92.93
  kernel from proposed.

  Unfortunately, I cannot do a bisect because this is a critical
  production system and we do not have any other system with a similar
  configuration.

  I attached a screenshot with the trace of the kernel panic.

  The last message that appears before the kernel panic (or rather the
  last one that I can see - there is a rather long pause between that
  message and the panic and I cannot scroll up far enough to ensure that
  there are no other messages in between) is:

  bcache: register_bcache() error /dev/dm-0: device already registered

  When booting with kernel 4.15.0-88 that does not have this problem,
  the next message is

  bcache: register_bcache() error /dev/dm-12: device already registered
  (emitting change event)

  After that the next message is:

  Begin: Loading essential drivers ... done

  This message also appears after the kernel panic, but the boot process
  stalls and the system can only be recovered by doing a hardware reset.

  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
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 17 21:08 seq
   crw-rw 1 root audio 116, 33 Mar 17 21:08 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Mar 18 12:55:18 2020
  HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a
  InstallationDate: Installed on 2013-07-02 (2450 days ago)
  InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release 
amd64 (20130214)
  MachineType: HP ProLiant DL160 G6
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic 
root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-09-23 (541 days ago)
  dmi.bios.date: 11/06/2009
  dmi.bios.vendor: HP
  dmi.bios.version: O33
  dmi.chassis.asset.tag: 0191525
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrO33:bd11/06/2009:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL160 G6
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1870140] Re: Laptop freeze after unplug power-AC (USB-C)

[Kai-Heng Feng]

Just wait for that commit lands in Ubuntu kernel...

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

Title:
  Laptop freeze after unplug power-AC (USB-C)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ## Power adapter plugged in,  charging goes well

  [ 1018.621820] asus_wmi: Unknown key cf pressed

  
  ## Power adapter unplugged, after few moments system freeze

  [  567.444810] BUG: kernel NULL pointer dereference, address: 0080
  [  567.444819] #PF: supervisor read access in kernel mode
  [  567.444823] #PF: error_code(0x) - not-present page
  [  567.444827] PGD 0 P4D 0 
  [  567.444834] Oops:  [#1] PREEMPT SMP PTI
  [  567.444841] CPU: 0 PID: 2873 Comm: kworker/0:0 Not tainted 
5.5.11-151.current #1
  [  567.444845] Hardware name: ASUSTeK COMPUTER INC. UX370UAR/UX370UAR, BIOS 
UX370UAR.310 04/17/2019
  [  567.444857] Workqueue: events ucsi_handle_connector_change [typec_ucsi]
  [  567.444868] RIP: 0010:ucsi_displayport_remove_partner+0xa/0x20 [typec_ucsi]
  [  567.444874] Code: 38 00 c7 43 28 00 00 00 00 48 83 c7 10 5b e9 6d cd 75 e1 
66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 48 85 ff 74 0f <48> 8b 47 
78 48 c7 00 00 00 00 00 c6 40 3d 00 c3 66 0f 1f 44 00 00
  [  567.444878] RSP: 0018:c9477df0 EFLAGS: 00010202
  [  567.444883] RAX: 0008 RBX: 88844685c418 RCX: 
000efd00
  [  567.444886] RDX:  RSI: 0001 RDI: 
0008
  [  567.444889] RBP:  R08:  R09: 
c9477ce0
  [  567.444892] R10: 888443e9f218 R11: 88844edeb478 R12: 
88844685c418
  [  567.444895] R13: 0001 R14: 88844685c2a8 R15: 

  [  567.444900] FS:  () GS:88844ec0() 
knlGS:
  [  567.444903] CS:  0010 DS:  ES:  CR0: 80050033
  [  567.444906] CR2: 0080 CR3: 0240a006 CR4: 
003606f0
  [  567.444909] Call Trace:
  [  567.444921]  ucsi_unregister_altmodes+0x7b/0x90 [typec_ucsi]
  [  567.444930]  ucsi_unregister_partner.part.0+0x13/0x30 [typec_ucsi]
  [  567.444938]  ucsi_handle_connector_change+0x231/0x310 [typec_ucsi]
  [  567.444949]  ? kmem_cache_free+0x22a/0x290
  [  567.444960]  process_one_work+0x1e1/0x3d0
  [  567.444968]  worker_thread+0x4a/0x3d0
  [  567.444976]  kthread+0xfb/0x130
  [  567.444983]  ? process_one_work+0x3d0/0x3d0
  [  567.444988]  ? kthread_park+0x90/0x90
  [  567.444998]  ret_from_fork+0x35/0x40
  [  567.445006] Modules linked in: typec_displayport hidp rfcomm ccm cmac fuse 
snd_hda_codec_hdmi joydev snd_hda_codec_realtek snd_hda_codec_generic 
ledtrig_audio bnep intel_rapl_msr snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi iTCO_wdt 
hid_multitouch iTCO_vendor_support mei_hdcp iwlmvm intel_rapl_common 
snd_soc_core mac80211 snd_compress libarc4 x86_pkg_temp_thermal 
intel_powerclamp snd_pcm_dmaengine uvcvideo ac97_bus coretemp videobuf2_vmalloc 
videobuf2_memops i915 snd_hda_intel videobuf2_v4l2 snd_intel_dspcfg iwlwifi 
kvm_intel videobuf2_common hid_sensor_accel_3d i2c_algo_bit videodev 
snd_hda_codec btusb hid_sensor_trigger kvm industrialio_triggered_buffer 
snd_hda_core drm_kms_helper kfifo_buf btrtl btbcm syscopyarea snd_hwdep 
sysfillrect btintel industrialio asus_nb_wmi irqbypass mc wmi_bmof asus_wmi 
evdev sysimgblt hid_sensor_iio_common bluetooth cfg80211 sparse_keymap snd_pcm 
fb_sys_fops i2c_i801 ucsi_acpi snd_timer
  [  567.445072]  typec_ucsi efivars snd soundcore spi_pxa2xx_platform mei_me 
dw_dmac rfkill thermal typec i2c_designware_platform mei i2c_designware_core 
drm elan_i2c ac tpm_tis tpm_tis_core pinctrl_sunrisepoint tpm pinctrl_intel 
rng_core asus_wireless acpi_pad button hid_sensor_hub hid_generic 
intel_ishtp_hid xhci_pci serio_raw xhci_hcd intel_ish_ipc usbcore intel_ishtp 
usb_common wmi i2c_hid hid battery video
  [  567.445112] CR2: 0080
  [  567.445117] ---[ end trace a50cf550f0b4969a ]---
  [  567.445126] RIP: 0010:ucsi_displayport_remove_partner+0xa/0x20 [typec_ucsi]
  [  567.445132] Code: 38 00 c7 43 28 00 00 00 00 48 83 c7 10 5b e9 6d cd 75 e1 
66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 48 85 ff 74 0f <48> 8b 47 
78 48 c7 00 00 00 00 00 c6 40 3d 00 c3 66 0f 1f 44 00 00
  [  567.445136] RSP: 0018:c9477df0 EFLAGS: 00010202
  [  567.445140] RAX: 0008 RBX: 88844685c418 RCX: 
000efd00
  [  567.445143] RDX:  RSI: 0001 RDI: 
0008
  [  567.445146] RBP:  R08:  R09: 
c9477ce0
  [  567.445149] R10: 888443e9f218 R11: 88844edeb478 R12: 
88844685c418
  [  567.445152] R13: 0001 R14: 88844685c2a8 R15: 

  [  567.445156] FS:  () 

[Kernel-packages] [Bug 1866357] Re: Pop sound from build-in speaker during cold boot and resume from S3

[David Chen]

I have enabled proposed and installed latest oem kernel 5.0 in proposed,
still can reproduce this issue.  Could you let me know which kernel
version should I test?

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

Title:
  Pop sound from build-in speaker during cold boot and resume from S3

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

Bug description:
  [Description]
  On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot 
and resume from S3, internal speaker will have a noticeable short pop noise.  

  [More detail]
  There are similar bugs reported indicating it's related to codec powersaving 
[1].  On some devices, disable powersaving can workaround it, but the same 
workaround does not work on this device.
  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663

  [Experiment]
  With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise
  With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise
  With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise
  So I started testing kernels between 4.13 and 4.15, found the issue does not 
present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that 
started to have the pop noise.

  [HW info]
  Codec: Realtek ALC3253
  00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03)


  Device is not with me at this moment, I will provide more info if required.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1901 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-somerville-bionic-amd64-20180608-47+beaver-osp1-sanbernardino+X100
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-03-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Wyse 5070 Thin Client
  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.3.0-40-generic 
root=UUID=22fa172b-895b-4061-834e-d616380befc5 ro mem_sleep_default=deep quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.9
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd01/08/2020:svnDellInc.:pnWyse5070ThinClient:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr:
  dmi.product.family: Wyse Thin Client 5000 Series
  dmi.product.name: Wyse 5070 Thin Client
  dmi.product.sku: 080C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1866326] Re: Login freezes when using Nvidia drivers 435 and 440 (Ubuntu 18.04, Quadro T2000)

[Launchpad Bug Tracker]

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

** Changed in: nvidia-graphics-drivers-435 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Login freezes when using Nvidia drivers 435 and 440 (Ubuntu 18.04,
  Quadro T2000)

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

Bug description:
  I have a Lenovo P53 which has hybrid graphics (Intel and Nvidia). I
  have chosen to use "discrete graphics" which means that I am using the
  Nvidia card.

  Until a recent update everything was working fine. After the automatic
  update and the upgrade from kernel 5.3.0-28 to 5.3.0-40 (and possibly
  an upgrade of the Nvidia drivers) the opearing system hands after I
  enter the login credentials. I have tried to get some output from the
  startup screen by removing the "quite splash" from the grub file but
  it does not give any error information. It just hangs.

  I am using Nouveau to login to the computer, but with Nouveau I the
  HDMI port is not working

  I can try to add more debugging information if one helps me to collect
  it

  I am using Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  6 11:39:29 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Once a week
  GpuHangReproducibility: I don't know
  GpuHangStarted: I don't know
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:2297]
   NVIDIA Corporation Device [10de:1fb8] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:2297]
  InstallationDate: Installed on 2020-02-29 (5 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: LENOVO 20QQS1JE00
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-40-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2NET34W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QQS1JE00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2NET34W(1.19):bd11/28/2019:svnLENOVO:pn20QQS1JE00:pvrThinkPadP53:rvnLENOVO:rn20QQS1JE00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P53
  dmi.product.name: 20QQS1JE00
  dmi.product.sku: LENOVO_MT_20QQ_BU_Think_FM_ThinkPad P53
  dmi.product.version: ThinkPad P53
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1871414

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  [Gigabyte GA-AB350M-D3H] Pulseaudio repeatedly detects a headphone
  being plugged in when nothing is plugged in

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Software details:
  Distro: Kubuntu 20.04 Beta
  Kernel: 5.4.0-21-generic
  alsa-base version 1.0.25+dfsg-0ubuntu5
  alsa-utils version 1.2.2-1ubuntu1
  pulseaudio version 1:13.99.1-1ubuntu1

  Hardware details:
  Motherboard: Gigabyte GA-AB350M-D3H
  Audio Codec: Realtek ALC887
  GPU: Nvidia RTX 2060 Super (with the audio output disabled in PulseAudio)

  Regarding the issue:
  Every time I start an audio stream (regardless of the application), I can 
hear interruptions in the sound and when opening alsamixer I can also see the 
interface kind of flickering for a few milliseconds.
  After running pulseaudio with logging enabled for a few seconds (while 
playing music), this pattern can be seen:

  [pulseaudio] sink.c: alsa_output.pci-_0a_00.3.analog-stereo: state: IDLE 
-> RUNNING
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port 

[Kernel-packages] [Bug 1871403] Re: Intel Wireless 8265 / 8275 [8086:24fd] subsystem [8086:9010] WiFi won't connect, but kernel 5.6 fixes it

[You-Sheng Yang]

** Summary changed:

- wifi won't connect, but kernel 5.6 fixes it
+ Intel Wireless 8265 / 8275 [8086:24fd] subsystem [8086:9010] WiFi won't 
connect, but kernel 5.6 fixes it

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

Title:
  Intel Wireless 8265 / 8275 [8086:24fd] subsystem [8086:9010] WiFi
  won't connect, but kernel 5.6 fixes it

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My wifi adapter won't connect under Kubuntu.  It works fine when I
  boot the same laptop under Ubuntu 18.04, but when I boot under Kubuntu
  20.04, I get "Configuring Interface" followed by "Wireless interface
  (wlp1s0)  The wifi network could not be found."

  It worked fine up until today.  Ethernet connection works fine.

  I tried restarting NetworkManager.service in systemctl and I get this:

  NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Tue 2020-04-07 10:08:47 EDT; 1min 3s ago
 Docs: man:NetworkManager(8)
 Main PID: 4231 (NetworkManager)
Tasks: 3 (limit: 16627)
   Memory: 5.0M
   CGroup: /system.slice/NetworkManager.service
   └─4231 /usr/sbin/NetworkManager --no-daemon

  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.1829] 
device (wlp1s0): supplicant interface state: scanning -> authenticating
  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.1830] 
device (p2p-dev-wlp1s0): supplicant management interface state: scanning -> 
authenticating
  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.2268] 
device (wlp1s0): supplicant interface state: authenticating -> disconnected
  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.2269] 
device (p2p-dev-wlp1s0): supplicant management interface state: authenticating 
-> disconnected
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8910] 
device (wlp1s0): Activation: (wifi) association took too long, failing 
activation
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8911] 
device (wlp1s0): state change: config -> failed (reason 'ssid-not-found', 
sys-iface-state: 'managed')
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8933] 
device (wlp1s0): Activation: failed for connection 'BoulderNET'
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8939] 
device (wlp1s0): state change: failed -> disconnected (reason 'none', 
sys-iface-state: 'managed')
  Apr 07 10:09:34 ZenBook NetworkManager[4231]:   [1586268574.2285] 
device (wlp1s0): supplicant interface state: disconnected -> inactive
  Apr 07 10:09:34 ZenBook NetworkManager[4231]:   [1586268574.2287] 
device (p2p-dev-wlp1s0): supplicant management interface state: disconnected -> 
inactive
  dennis@ZenBook:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.6.1-050601-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Tue Apr  7 10:14:23 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Picasso [1043:1b71]
  InstallationDate: Installed on 2020-03-06 (31 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.1-050601-generic 
root=UUID=f2ef7f4c-875c-4861-a849-e5ebf6d646fd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX434DA_UM433DA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX434DA
  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.:bvrUX434DA_UM433DA.302:bd09/05/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX434DA_UM433DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX434DA_UM433DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  

[Kernel-packages] [Bug 1865499] Re: pulseaudio doesn't detect (new) USB headset

[Daniel van Vugt]

It looks like that fix is already released as an official update in
1.1.3-5ubuntu0.4 on 24 March 2020. If that didn't fix the problem here
then I might have linked to the wrong thing. Please update your system
and tell us if the problem still occurs.

** Changed in: alsa-lib (Ubuntu)
   Status: Fix Committed => Incomplete

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

Title:
  pulseaudio doesn't detect (new) USB headset

Status in alsa-lib package in Ubuntu:
  Incomplete

Bug description:
  When booting the system (Lenovo Thinkpad L480/L490), all connected USB
  headsets are recognized and can be used, and configured via
  pavucontrol.

  When hot-plugging the USB headset, either the speaker is recognized,
  or the microphone, rarely both. But when both are recognized, the
  microphone is always a "multichannel" device. When both the speaker
  and the "multichannel" microphone are recognized, only one can be used
  - either speaker or microphone. When selecting the speaker, the
  microphone is switched back to any other device available, them same
  goes for the microphone and the speaker - any other speaker is
  selected.

  A workaround is to plug in the USB headset and run "pkill -U $USER
  pulseaudio". Everything works fine until the next hot-plug (eg. a
  second headset).

  Running "lsb_release -a" gives   
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  Codename: bionic

  Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
  our users are affected by this bug, all running the same Ubuntu and
  package versions. I activated the proposed repository to check if any
  updates available fix the problem, but to no avail. I also switched
  kernels (from 4.15 to 5.5 mainline from
  https://wiki.ubuntu.com/Kernel/MainlineBuilds).

  I read bug #1325282
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
  and it sounds somewhat very familiar, but instead of "env={}" in
  /usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
  Removing "env=env" doesn't resolve the problem.

  Do you require additional information?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1865499/+subscriptions

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

[Kernel-packages] [Bug 1869229] Re: Mounting LVM snapshots with xfs can hit kernel BUG in nvme driver

[Matthew Ruffell]

I created a new c5d.large instance on AWS, and installed
4.4.0-177-generic from -updates. I ran through the reproduction steps,
and the issue reproduces.

I then created a new c5d.large instance, enabled -proposed and installed
4.4.0-178-generic. I again ran through the reproduction steps, and this
time, the final mount succeeds, there is no segmentation fault and dmesg
is clean of any errors.

I am happy to mark this as verified.

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  Mounting LVM snapshots with xfs can hit kernel BUG in nvme driver

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  When mounting LVM snapshots using xfs, it's possible to hit a BUG_ON() in 
nvme driver.

  Upstream commit 729204ef49ec ("block: relax check on sg gap")
  introduced a way to merge bios if they are physically contiguous. This
  can lead to issues if one rq starts with a non-aligned buffer, as it
  can cause the merged segment to end in an unaligned virtual boundary.
  In some AWS instances, it's possible to craft such a request when
  attempting to mount LVM snapshots using xfs. This will then cause a
  kernel spew due to a BUG_ON in nvme_setup_prps(), which checks if
  dma_len is aligned to the page size.

  [Fix]
  Upstream commit 5a8d75a1b8c9 ("block: fix bio_will_gap() for first bvec with 
offset") prevents requests that begin with an unaligned buffer from being 
merged.

  [Test Case]
  This has been verified on AWS with c5d.large instances:

  1) Prepare the LVM device + snapshot
  $ sudo vgcreate vg0 /dev/nvme1n1
  $ sudo lvcreate -L5G -n data0 vg0
  $ sudo mkfs.xfs /dev/vg0/data0
  $ sudo mount /dev/vg0/data0 /mnt
  $ sudo touch /mnt/test
  $ sudo touch /mnt/test2
  $ sudo ls /mnt
  $ sudo umount /mnt
  $ sudo lvcreate -l100%FREE -s /dev/vg0/data0 -n data0_snap

  2) Attempting to mount the previously created snapshot results in the Oops:
  $ sudo mount /dev/vg0/data0_snap /mnt
  Segmentation fault (core dumped)

  [Regression Potential]
  The fix prevents some bios from being merged, so it can have a performance 
impact in certain scenarios. The patch only targets misaligned segments, so the 
impact should be less noticeable in the general case.
  The commit is also present in mainline kernels since 4.13, and hasn't been 
changed significantly, so potential for other regressions should be low.

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

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

[Kernel-packages] [Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes

[satmandu]

I think this is the same issue as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385113

has anybody submitted this upstream to the linux-input mailing list yet?

It's definitely happening with 5.4.0-23-lowlatency on focal beta and my
magicmouse trackpad.

I will try with a mainline kernel next...

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

Title:
  Bluetooth touchpad (Apple Magic Trackpad) disconnects every few
  minutes

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

Bug description:
  I recently got an Apple's Magic Trackpad. I paired it with Ubuntu
  18.04.2 LTS and worked out of the box, no special drivers needed.

  However, I experience frequent disconnections that last a few seconds
  (5-15 seconds usually), which are quite annoying, as the cursor stops
  responding during that interval. The trackpad connects by itself after
  that period. That usually happens every 20-40 minutes.

  I use the onboard bluetooth device of my laptop. I also have, at the
  same time, two more bluetooth devices (keyboard and mouse) and they do
  not experience that issue, just the trackpad. On ocassion I use
  bluetooth headphones which work just fine.

  First of all:

  Using the command "bluetoothctl" I get the following every time I
  experience a disconnection:

  [CHG] Device F4:1B:A1:33:F9:8D Connected: no
  [CHG] Device F4:1B:A1:33:F9:8D Connected: yes

  Checking "dmesg" I can see more information: (if I am not mistaken,
  this shows 4 disconnections)

  
  [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0
  [ 1609.070797] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23
  [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
  [ 1676.917377] NET: Registered protocol family 38
  [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0
  [ 1872.815559] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24
  [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
  [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0
  [ 3101.683100] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25
  [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
  [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0
  [ 3110.683929] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26
  [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98

  
  And this is what journalctl -b shows at the moment of the 
disconnection/reconnection:

  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
config/udev: removing device Apple Wireless Trackpad
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option 
"fd" "64" (1,63 m)˜
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - 
Apple Wireless Trackpad: device removed
  de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 
'array' failed
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
UnloadModule: "libinput"
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
systemd-logind: releasing fd for 13:80
  de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on 
/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008
  de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown 
main item tag 0x0
  de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25
  de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: 
input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 
64:5d:86:86:3f:98
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1)
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input 
driver specified, ignoring this device.
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This 
device may have been added with another device file.
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
config/udev: Adding 

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

[Ubuntu Kernel Bot]

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

apport-collect 1871477

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

** Tags added: eoan

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

Title:
  [nouveau] Ubuntu 18.04 freezes when using Zoom

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use two monitors.
  I noticed that every time I use Zoom, Ubuntu frezzes completely, at least the 
desktop. Other zoom participants inform me that they can hear me and see me but 
my system is not responsive no matter how long I leave it run.

  I use : 
  Ubuntu 18.04.4 LTS
  5.3.0-45-generic #37~18.04.1-Ubuntu SMP Fri Mar 27 15:58:10 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

  I believe that the error is due to what is displayed in :

  Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #5 0x55ac1bdb07c0 
i   resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7fb5040d2cd0 @ 
10)
  Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #6 0x7ffdb79d9a50 
I   resource:///org/gnome/gjs/modules/signals.js:128 (0x7fb5040d2230 @ 386)
  Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #7 0x55ac1bdb0730 
i   resource:///org/gnome/shell/ui/tweener.js:244 (0x7fb5040cf808 @ 159)
  Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #8 0x7ffdb79da630 
I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fb5040b5de0 @ 71)
  Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #9 0x55ac1bdb06b0 
i   resource:///org/gnome/shell/ui/tweener.js:219 (0x7fb5040cf780 @ 15)
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009

  Any hint?

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1871414] Re: Pulseaudio repeatedly detects a headphone being plugged in when nothing is plugged in

[Daniel van Vugt]

** Summary changed:

- Pulseaudio incorrectly detects a headphone being plugged in
+ Pulseaudio repeatedly detects a headphone being plugged in when nothing is 
plugged in

** Tags added: focal

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

** Summary changed:

- Pulseaudio repeatedly detects a headphone being plugged in when nothing is 
plugged in
+ [Gigabyte GA-AB350M-D3H] Pulseaudio repeatedly detects a headphone being 
plugged in when nothing is plugged in

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

Title:
  [Gigabyte GA-AB350M-D3H] Pulseaudio repeatedly detects a headphone
  being plugged in when nothing is plugged in

Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Software details:
  Distro: Kubuntu 20.04 Beta
  Kernel: 5.4.0-21-generic
  alsa-base version 1.0.25+dfsg-0ubuntu5
  alsa-utils version 1.2.2-1ubuntu1
  pulseaudio version 1:13.99.1-1ubuntu1

  Hardware details:
  Motherboard: Gigabyte GA-AB350M-D3H
  Audio Codec: Realtek ALC887
  GPU: Nvidia RTX 2060 Super (with the audio output disabled in PulseAudio)

  Regarding the issue:
  Every time I start an audio stream (regardless of the application), I can 
hear interruptions in the sound and when opening alsamixer I can also see the 
interface kind of flickering for a few milliseconds.
  After running pulseaudio with logging enabled for a few seconds (while 
playing music), this pattern can be seen:

  [pulseaudio] sink.c: alsa_output.pci-_0a_00.3.analog-stereo: state: IDLE 
-> RUNNING
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 

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

Title:
  wifi won't connect, but kernel 5.6 fixes it

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My wifi adapter won't connect under Kubuntu.  It works fine when I
  boot the same laptop under Ubuntu 18.04, but when I boot under Kubuntu
  20.04, I get "Configuring Interface" followed by "Wireless interface
  (wlp1s0)  The wifi network could not be found."

  It worked fine up until today.  Ethernet connection works fine.

  I tried restarting NetworkManager.service in systemctl and I get this:

  NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Tue 2020-04-07 10:08:47 EDT; 1min 3s ago
 Docs: man:NetworkManager(8)
 Main PID: 4231 (NetworkManager)
Tasks: 3 (limit: 16627)
   Memory: 5.0M
   CGroup: /system.slice/NetworkManager.service
   └─4231 /usr/sbin/NetworkManager --no-daemon

  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.1829] 
device (wlp1s0): supplicant interface state: scanning -> authenticating
  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.1830] 
device (p2p-dev-wlp1s0): supplicant management interface state: scanning -> 
authenticating
  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.2268] 
device (wlp1s0): supplicant interface state: authenticating -> disconnected
  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.2269] 
device (p2p-dev-wlp1s0): supplicant management interface state: authenticating 
-> disconnected
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8910] 
device (wlp1s0): Activation: (wifi) association took too long, failing 
activation
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8911] 
device (wlp1s0): state change: config -> failed (reason 'ssid-not-found', 
sys-iface-state: 'managed')
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8933] 
device (wlp1s0): Activation: failed for connection 'BoulderNET'
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8939] 
device (wlp1s0): state change: failed -> disconnected (reason 'none', 
sys-iface-state: 'managed')
  Apr 07 10:09:34 ZenBook NetworkManager[4231]:   [1586268574.2285] 
device (wlp1s0): supplicant interface state: disconnected -> inactive
  Apr 07 10:09:34 ZenBook NetworkManager[4231]:   [1586268574.2287] 
device (p2p-dev-wlp1s0): supplicant management interface state: disconnected -> 
inactive
  dennis@ZenBook:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.6.1-050601-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Tue Apr  7 10:14:23 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Picasso [1043:1b71]
  InstallationDate: Installed on 2020-03-06 (31 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.1-050601-generic 
root=UUID=f2ef7f4c-875c-4861-a849-e5ebf6d646fd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX434DA_UM433DA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX434DA
  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.:bvrUX434DA_UM433DA.302:bd09/05/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX434DA_UM433DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX434DA_UM433DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

[Kernel-packages] [Bug 1865962] Re: Dell XPS 13 9300 Intel 1650S wifi [34f0:1651] fails to load firmware

[Robert E. Griffith]

For anyone googling, I can confirm that my Thinkpad X1 Yoga Gen4 with
intel AC 9560 wifi card has no wifi with 5.3.0-29+ but does work with
5.4.0-17

Thinkpad X1 Yoga Gen4 with intel AC 9560 wifi
* 5.3.0-28: wifi works 
* 5.3.0-40,43,45,46: wifi does not work 
* 5.4.0-17: wifi works

--BobG

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

Title:
  Dell XPS 13 9300 Intel 1650S wifi [34f0:1651] fails to load firmware

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  It dumps some debug messages while loading iwlwifi firmware every time after 
booted up and finally got below errors
     [5.632845] iwlwifi :00:14.3: Failed to start RT ucode: -110
     [5.632849] iwlwifi :00:14.3: Firmware not running - cannot dump 
error
     [5.645491] iwlwifi :00:14.3: Failed to run INIT ucode: -110

  [Fix]
  It looks like it fails to load the firmware since mainline v5.4 kernel, and 
got fixed at v5.6-rc1. After bisect the kernel, the first bad commit is
     b3bd6416fc77 iwlwifi: assume the driver_data is a trans_cfg, but allow 
full cfg

  To avoid conflicts, we have to backport the following commits from mainline 
kernel
     b81b7bd02eda iwlwifi: remove some outdated iwl22000 configurations
     c042f0c77f3d iwlwifi: allocate more receive buffers for HE devices
     5661925a9b38 iwlwifi: pcie: rx: use rxq queue_size instead of constant
     bfc3e9fdbfb8 iwlwifi: 22000: fix some indentation
     3681021fc6af iwlwifi: remove IWL_DEVICE_22560/IWL_DEVICE_FAMILY_22560

  [Test]
  Verified on Dell XPS 9300 with Killer AX1650i wifi card and XPS 13 2-1 
platform, wifi keeps working after reboot 10 times.

  [Regression Potential]
  Medium, the code changes a lot, although the test results are all positive, 
it's still hard to evaluate the regression potential.

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

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

[Kernel-packages] [Bug 1871303] Re: [nvidia] Boot hangs up on initiating graphics. I can only finish the boot if I use the recovery mode.

[Daniel van Vugt]

Thanks. The problem indeed looks like it's confined to the Nvidia
driver:

Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]: (EE) 
NVIDIA(0): Failed to allocate software rendering cache surface: out of
Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]: (EE) 
NVIDIA(0): memory.
Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]: (EE) 
NVIDIA(0):  *** Aborting ***
Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]: (EE)
Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]: Fatal server 
error:
Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]: (EE) NVIDIA: A 
GPU exception occurred during X server initialization(EE)
Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]: (EE)
Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]: Please consult 
the The X.Org Foundation support
Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]:  at 
http://wiki.x.org
Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]:  for help.
Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]: (EE) Please 
also check the log file at "/var/log/Xorg.0.log" for additional information.
Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]: (EE)
Apr 07 13:05:05 Kens-computer kernel: NVRM: GPU at PCI::01:00: 
GPU-0cbf6562-d7da-f433-1671-3edebe83dd01
Apr 07 13:05:05 Kens-computer kernel: NVRM: Xid (PCI::01:00): 31, Ch 
0008, engmask 0101, intr 1000
Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]: (EE) Server 
terminated with error (1). Closing log file.

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

** Summary changed:

- [nvidia] Boot hangs up on initiating graphics. I can only finish the boot if 
I use the recovery mode.
+ [nvidia] Xorg crashes in (EE) NVIDIA(0): Failed to allocate software 
rendering cache surface: out of memory

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

Title:
  [nvidia] Xorg crashes in (EE) NVIDIA(0): Failed to allocate software
  rendering cache surface: out of memory

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

Bug description:
  Boot hangs up on initiating graphics. I can only finish the boot if I
  use the recovery mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
  Uname: Linux 4.15.0-91-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/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.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Apr  7 09:02:40 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.15.0-88-generic, x86_64: installed
   nvidia, 390.116, 4.15.0-91-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GK208B [GeForce GT 710] [1043:8572]
  InstallationDate: Installed on 2017-07-14 (997 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic 
root=UUID=671dec46-62d2-4163-a941-c528578feb4d ro recovery nomodeset
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1103:bd05/14/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  

[Kernel-packages] [Bug 1871403] Re: wifi won't connect, but kernel 5.6 fixes it

[Daniel van Vugt]

** Summary changed:

- wifi won't connect
+ wifi won't connect, but kernel 5.6 fixes it

** Package changed: xorg (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/1871403

Title:
  wifi won't connect, but kernel 5.6 fixes it

Status in linux package in Ubuntu:
  New

Bug description:
  My wifi adapter won't connect under Kubuntu.  It works fine when I
  boot the same laptop under Ubuntu 18.04, but when I boot under Kubuntu
  20.04, I get "Configuring Interface" followed by "Wireless interface
  (wlp1s0)  The wifi network could not be found."

  It worked fine up until today.  Ethernet connection works fine.

  I tried restarting NetworkManager.service in systemctl and I get this:

  NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Tue 2020-04-07 10:08:47 EDT; 1min 3s ago
 Docs: man:NetworkManager(8)
 Main PID: 4231 (NetworkManager)
Tasks: 3 (limit: 16627)
   Memory: 5.0M
   CGroup: /system.slice/NetworkManager.service
   └─4231 /usr/sbin/NetworkManager --no-daemon

  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.1829] 
device (wlp1s0): supplicant interface state: scanning -> authenticating
  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.1830] 
device (p2p-dev-wlp1s0): supplicant management interface state: scanning -> 
authenticating
  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.2268] 
device (wlp1s0): supplicant interface state: authenticating -> disconnected
  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.2269] 
device (p2p-dev-wlp1s0): supplicant management interface state: authenticating 
-> disconnected
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8910] 
device (wlp1s0): Activation: (wifi) association took too long, failing 
activation
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8911] 
device (wlp1s0): state change: config -> failed (reason 'ssid-not-found', 
sys-iface-state: 'managed')
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8933] 
device (wlp1s0): Activation: failed for connection 'BoulderNET'
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8939] 
device (wlp1s0): state change: failed -> disconnected (reason 'none', 
sys-iface-state: 'managed')
  Apr 07 10:09:34 ZenBook NetworkManager[4231]:   [1586268574.2285] 
device (wlp1s0): supplicant interface state: disconnected -> inactive
  Apr 07 10:09:34 ZenBook NetworkManager[4231]:   [1586268574.2287] 
device (p2p-dev-wlp1s0): supplicant management interface state: disconnected -> 
inactive
  dennis@ZenBook:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.6.1-050601-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Tue Apr  7 10:14:23 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Picasso [1043:1b71]
  InstallationDate: Installed on 2020-03-06 (31 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.1-050601-generic 
root=UUID=f2ef7f4c-875c-4861-a849-e5ebf6d646fd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX434DA_UM433DA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX434DA
  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.:bvrUX434DA_UM433DA.302:bd09/05/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX434DA_UM433DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX434DA_UM433DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: 

[Kernel-packages] [Bug 1871477] Re: [nouveau] Ubuntu 18.04 freezes when using Zoom

[Daniel van Vugt]

It appears the nouveau kernel driver is crashing so that's likely the
problem.

You might want to try the proprietary Nvidia driver instead, in:

  Software & Updates > Additional Drivers


** Summary changed:

- Ubuntu 18.04 freezes when using Zoom
+ [nouveau] Ubuntu 18.04 freezes when using Zoom

** Tags added: bionic nouveau

** Package changed: gnome-shell (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/1871477

Title:
  [nouveau] Ubuntu 18.04 freezes when using Zoom

Status in linux package in Ubuntu:
  New

Bug description:
  I use two monitors.
  I noticed that every time I use Zoom, Ubuntu frezzes completely, at least the 
desktop. Other zoom participants inform me that they can hear me and see me but 
my system is not responsive no matter how long I leave it run.

  I use : 
  Ubuntu 18.04.4 LTS
  5.3.0-45-generic #37~18.04.1-Ubuntu SMP Fri Mar 27 15:58:10 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

  I believe that the error is due to what is displayed in :

  Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #5 0x55ac1bdb07c0 
i   resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7fb5040d2cd0 @ 
10)
  Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #6 0x7ffdb79d9a50 
I   resource:///org/gnome/gjs/modules/signals.js:128 (0x7fb5040d2230 @ 386)
  Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #7 0x55ac1bdb0730 
i   resource:///org/gnome/shell/ui/tweener.js:244 (0x7fb5040cf808 @ 159)
  Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #8 0x7ffdb79da630 
I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fb5040b5de0 @ 71)
  Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #9 0x55ac1bdb06b0 
i   resource:///org/gnome/shell/ui/tweener.js:219 (0x7fb5040cf780 @ 15)
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
  Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009

  Any hint?

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

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

[Kernel-packages] [Bug 1871403] [NEW] wifi won't connect, but kernel 5.6 fixes it

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

My wifi adapter won't connect under Kubuntu.  It works fine when I boot
the same laptop under Ubuntu 18.04, but when I boot under Kubuntu 20.04,
I get "Configuring Interface" followed by "Wireless interface (wlp1s0)
The wifi network could not be found."

It worked fine up until today.  Ethernet connection works fine.

I tried restarting NetworkManager.service in systemctl and I get this:

NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Tue 2020-04-07 10:08:47 EDT; 1min 3s ago
   Docs: man:NetworkManager(8)
   Main PID: 4231 (NetworkManager)
  Tasks: 3 (limit: 16627)
 Memory: 5.0M
 CGroup: /system.slice/NetworkManager.service
 └─4231 /usr/sbin/NetworkManager --no-daemon

Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.1829] device 
(wlp1s0): supplicant interface state: scanning -> authenticating
Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.1830] device 
(p2p-dev-wlp1s0): supplicant management interface state: scanning -> 
authenticating
Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.2268] device 
(wlp1s0): supplicant interface state: authenticating -> disconnected
Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.2269] device 
(p2p-dev-wlp1s0): supplicant management interface state: authenticating -> 
disconnected
Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8910] device 
(wlp1s0): Activation: (wifi) association took too long, failing activation
Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8911] device 
(wlp1s0): state change: config -> failed (reason 'ssid-not-found', 
sys-iface-state: 'managed')
Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8933] device 
(wlp1s0): Activation: failed for connection 'BoulderNET'
Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8939] device 
(wlp1s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 
'managed')
Apr 07 10:09:34 ZenBook NetworkManager[4231]:   [1586268574.2285] device 
(wlp1s0): supplicant interface state: disconnected -> inactive
Apr 07 10:09:34 ZenBook NetworkManager[4231]:   [1586268574.2287] device 
(p2p-dev-wlp1s0): supplicant management interface state: disconnected -> 
inactive
dennis@ZenBook:~$

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
Uname: Linux 5.6.1-050601-generic x86_64
ApportVersion: 2.20.11-0ubuntu24
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
Date: Tue Apr  7 10:14:23 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Picasso [1043:1b71]
InstallationDate: Installed on 2020-03-06 (31 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306)
MachineType: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.1-050601-generic 
root=UUID=f2ef7f4c-875c-4861-a849-e5ebf6d646fd ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/05/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX434DA_UM433DA.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX434DA
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.:bvrUX434DA_UM433DA.302:bd09/05/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX434DA_UM433DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ZenBook
dmi.product.name: ZenBook UX434DA_UM433DA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal kubuntu ubuntu
-- 
wifi won't connect, but kernel 5.6 fixes it
https://bugs.launchpad.net/bugs/1871403
You received this bug notification because you are a member of 

[Kernel-packages] [Bug 1871477] [NEW] [nouveau] Ubuntu 18.04 freezes when using Zoom

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I use two monitors.
I noticed that every time I use Zoom, Ubuntu frezzes completely, at least the 
desktop. Other zoom participants inform me that they can hear me and see me but 
my system is not responsive no matter how long I leave it run.

I use : 
Ubuntu 18.04.4 LTS
5.3.0-45-generic #37~18.04.1-Ubuntu SMP Fri Mar 27 15:58:10 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

I believe that the error is due to what is displayed in :

Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #5 0x55ac1bdb07c0 i 
  resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7fb5040d2cd0 @ 10)
Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #6 0x7ffdb79d9a50 I 
  resource:///org/gnome/gjs/modules/signals.js:128 (0x7fb5040d2230 @ 386)
Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #7 0x55ac1bdb0730 i 
  resource:///org/gnome/shell/ui/tweener.js:244 (0x7fb5040cf808 @ 159)
Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #8 0x7ffdb79da630 I 
  resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fb5040b5de0 @ 71)
Απρ 07 20:37:57 igor-MS-7A72 org.gnome.Shell.desktop[1994]: #9 0x55ac1bdb06b0 i 
  resource:///org/gnome/shell/ui/tweener.js:219 (0x7fb5040cf780 @ 15)
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: TRAP ch 15 
[007f3bf000 Xorg[1859]]
Απρ 07 20:38:33 igor-MS-7A72 kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 
8009

Any hint?

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


** Tags: bionic nouveau
-- 
[nouveau] Ubuntu 18.04 freezes when using Zoom
https://bugs.launchpad.net/bugs/1871477
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 1866357] Re: Pop sound from build-in speaker during cold boot and resume from S3

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-bionic

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

Title:
  Pop sound from build-in speaker during cold boot and resume from S3

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

Bug description:
  [Description]
  On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot 
and resume from S3, internal speaker will have a noticeable short pop noise.  

  [More detail]
  There are similar bugs reported indicating it's related to codec powersaving 
[1].  On some devices, disable powersaving can workaround it, but the same 
workaround does not work on this device.
  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663

  [Experiment]
  With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise
  With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise
  With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise
  So I started testing kernels between 4.13 and 4.15, found the issue does not 
present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that 
started to have the pop noise.

  [HW info]
  Codec: Realtek ALC3253
  00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03)


  Device is not with me at this moment, I will provide more info if required.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1901 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-somerville-bionic-amd64-20180608-47+beaver-osp1-sanbernardino+X100
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-03-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Wyse 5070 Thin Client
  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.3.0-40-generic 
root=UUID=22fa172b-895b-4061-834e-d616380befc5 ro mem_sleep_default=deep quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.9
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd01/08/2020:svnDellInc.:pnWyse5070ThinClient:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr:
  dmi.product.family: Wyse Thin Client 5000 Series
  dmi.product.name: Wyse 5070 Thin Client
  dmi.product.sku: 080C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1866772] Re: Sys oopsed with sysfs test in ubuntu_stress_smoke_test on X-hwe ARM64

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-bionic

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

Title:
  Sys oopsed with sysfs test in ubuntu_stress_smoke_test on X-hwe ARM64

Status in Stress-ng:
  New
Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released

Bug description:
  == SRU Request [ BIONIC, EOAN, FOCAL ] ==

  Reading /sys/firmware/acpi/tables/data/BERT as root at at odd byte
  offset will cause an oops.  This is because the source address is I/O
  mapped and this needs to be read with an I/O memcpy rather than an
  memcpy.

  == Fix ==

  The fix is upstream (linux-next) commit that will land in 5.7, the
  backport to bionic, eoan and focal is just a minor context wiggle.

  commit 08c07cefb3042a55bc9f8243814b504d5eff93f3
  Author: Colin Ian King 
  Date:   Thu Mar 12 11:13:45 2020 +

  ACPI: sysfs: copy ACPI data using io memory copying

  == Test ==

  Running on hotdog with the reproducer below (run as root):

  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(void)
  {
  int fd;
  char buffer[3];
  ssize_t n;

  fd = open("/sys/firmware/acpi/tables/data/BERT", O_RDONLY);
  if (fd < 0) {
  fprintf(stderr, "open failed: %d (%s)\n", errno, 
strerror(errno));
  return -1;
  }
  do {
  n = read(fd, buffer, sizeof(buffer));
  } while (n > 0);

  return 0;
  }

  Without the fix it will oops. With the fix it works OK.

  == Regession Potential ==

  This only affects the reading of the ACPI BERT table from /sys as root
  so it is limited in scope to just a very narrow use case. Normally the
  BERT table is just handled by the kernel, so access to this table is
  just for debugging purposes.

  ---

  Issue found on new ARM64 node "hotdog" 4.15.0-91.92~16.04.1
  Failed 2 of 2 attempts.

  Test suite HEAD SHA1: 3f43e81

   sysfs STARTING
   sysfs RETURNED 0
   sysfs FAILED (kernel oopsed)
   [ 1075.760640] Unable to handle kernel paging request at virtual address 
4a70072a
   [ 1075.763319] Unable to handle kernel paging request at virtual address 
4a70e4ba
   [ 1075.768563] Mem abort info:
   [ 1075.768566]   ESR = 0x9621
   [ 1075.768568]   Exception class = DABT (current EL), IL = 32 bits
   [ 1075.768569]   SET = 0, FnV = 0
   [ 1075.768570]   EA = 0, S1PTW = 0
   [ 1075.768571] Data abort info:
   [ 1075.768577]   ISV = 0, ISS = 0x0021
   [ 1075.776489] Mem abort info:
   [ 1075.776491]   ESR = 0x9621
   [ 1075.776493]   Exception class = DABT (current EL), IL = 32 bits
   [ 1075.776494]   SET = 0, FnV = 0
   [ 1075.776495]   EA = 0, S1PTW = 0
   [ 1075.776496] Data abort info:
   [ 1075.776500]   ISV = 0, ISS = 0x0021
   [ 1075.779284]   CM = 0, WnR = 0
   [ 1075.779288] swapper pgtable: 4k pages, 48-bit VAs, pgd = facfed4f
   [ 1075.779290] [4a70072a] *pgd=00bffcffe003, 
*pud=009f6122c003, *pmd=00bf5adf4003, *pte=006880280703
   [ 1075.782342]   CM = 0, WnR = 0
   [ 1075.782346] swapper pgtable: 4k pages, 48-bit VAs, pgd = facfed4f
   [ 1075.782352] [4a70e4ba] *pgd=00bffcffe003, 
*pud=009f6122c003, *pmd=00bf5adf4003, *pte=00688028e703
   [ 1075.788262] Internal error: Oops: 9621 [#2] SMP
   [ 1075.788269] Modules linked in: unix_diag binfmt_misc snd_seq 
snd_seq_device snd_timer snd soundcore userio vfio_iommu_type1 vfio hci_vhci 
bluetooth ecdh_generic uhid cuse vhost_vsock vmw_vsock_virtio_transport_common 
vhost_net vhost vsock tap dccp_ipv4 dccp ipx p8023 atm psnap p8022 llc 
algif_rng algif_aead anubis fcrypt khazad seed tea md4 michael_mic 
poly1305_generic rmd128 rmd160 rmd256 rmd320 sha3_generic sm3_generic tgr192 
wp512 algif_hash chacha20_neon chacha20_generic blowfish_generic 
blowfish_common cast5_generic des_generic salsa20_generic camellia_generic 
cast6_generic cast_common serpent_generic twofish_generic twofish_common 
algif_skcipher af_alg nls_iso8859_1 ipmi_ssif ipmi_devintf 

[Kernel-packages] [Bug 1867790] Re: update-version-dkms doesn't add a BugLink

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-bionic

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

Title:
  update-version-dkms doesn't add a BugLink

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released

Bug description:
  == Impact ==
  When there are updates on the dkms versions used for a linux build, 
'update-version-dkms' saves the new version(s) in 'debian/dkms-versions' and 
commits it. The commit doesn't have any BugLink, so it gets added to the debian 
changelog under "* Miscellaneous Ubuntu changes".

  == Fix ==
  Change 'update-version-dkms' to add a BugLink to 
https://bugs.launchpad.net/bugs/1786013 ("Packaging resync"), which is the bug 
report being used for all the other automated commits.

  == Test Case ==
  In one of the main kernels, run 'update-version-dkms' and make sure it adds a 
valid BugLink.

  == Regression Potential ==
  Low. This only changes how the automated commits are generated and later 
added to the changelog.

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

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

[Kernel-packages] [Bug 1812638] Re: reuseport_bpf_numa in net from ubuntu_kernel_selftests failed on i386

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-bionic

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

Title:
  reuseport_bpf_numa in net from ubuntu_kernel_selftests failed on i386

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  The reuseport_bpf_numa test in net category from ubuntu_kernel_selftests
  will fail on i386 systems with:
selftests: reuseport_bpf_numa

not ok 1..3 selftests: reuseport_bpf_numa [FAIL]

  If you run it directly, you will see the test is simply not supported.
$ sudo ./reuseport_bpf_numa
./reuseport_bpf_numa: no numa api support: Function not implemented

  == Fix ==
  * 1a2b80ec (selftests: net: reuseport_bpf_numa: don't fail if no numa
   support)

  We have this patch in newer kernel from D, and we don't run this test
  on Xenial so only Bionic needs this patch.

  == Test ==
  Tested on a Bionic i386 node and it works as expected.
selftests: reuseport_bpf_numa

1..0 # Skipped: no numa api support
ok 1..3 selftests: reuseport_bpf_numa [PASS]

  == Regression Potential ==
  Low, trival change to testing tool itself.

  
  == Original Bug Report ==
  Test failed with:
  $ sudo ./reuseport_bpf_numa
  ./reuseport_bpf_numa: no numa api support: Function not implemented

  Maybe this one should be skipped.

  selftests: reuseport_bpf_numa
   
   not ok 1..3 selftests: reuseport_bpf_numa [FAIL]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic i686
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 21 10:52 seq
   crw-rw 1 root audio 116, 33 Jan 21 10:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Mon Jan 21 11:06:26 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R310
  PciMultimedia:

  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=6aaa11f6-d386-4c0c-b4b8-38e6c408980a ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 05XKKK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd09/18/2012:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R310
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1869948] Re: Multiple Kexec in AWS Nitro instances fail

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-bionic

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

Title:
  Multiple Kexec in AWS Nitro instances fail

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  * Currently, users cannot perform multiple kernel kexec loads on AWS Nitro 
instances (KVM-based); after the 2nd or 3rd kexec, an initrd corruption is 
observed, with the following signature:

   Initramfs unpacking failed: junk within compressed archive
  [...]
   Kernel panic - not syncing: No working init found.
  Try passing init= option to kernel. See Linux 
Documentation/admin-guide/init.rst for guidance.
  CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.5.0-rc7-gpiccoli+ #26  Hardware 
name: Amazon EC2 t3.large/, BIOS 1.0 10/16/2017
  Call Trace:
dump_stack+0x6d/0x9a
? csum_partial_copy_generic+0x150/0x170
panic+0x101/0x2e3
? do_execve+0x25/0x30
? rest_init+0xb0/0xb0
kernel_init+0xfb/0x100
ret_from_fork+0x35/0x40

  * After investigation (see comment 2), it was noticed the Amazon ena
  network driver doesn't provide a shutdown() handler, hence it could be
  performing a DMA transaction to a previous valid address during boot,
  which would then corrupt kernel memory. The following patch was
  proposed and fixed the issue, allowing 1000 kexecs to be executed
  successfully with no issues observed: 428c491332bc("net: ena: Add PCI
  shutdown handler to allow safe kexec") [
  git.kernel.org/linus/428c491332bc ].

  * Hence, we are hereby requesting SRU for this patch. It was tested in
  all supported series (4.4, 4.15 and 5.3) in Amazon Nitro instances
  with success, and reviewed/acked by ena driver team and a kexec
  developer from other distro. Worth mentioning that we proposed an
  upstream multi-vendor discussion about this issue:
  marc.info/?l=kexec=158299605013194

  [Test case]

  * The basic test procedure is about performing multiple kexecs
  sequentially; AWS does not provide a full console, so in case of
  failures one could check the instance screenshot or use pstore/ramoops
  in order to collect dmesg after a crash in a preserved memory area.
  The commands used to perform kexec are:

  kexec -l  --initrd  --reuse-cmdline
  systemctl kexec

  Alternatively, one could user "--append=" instead of "--reuse-cmdline"
  if a change in kexec command-line is desired; also, to execute the
  kexec-loaded kernel both "kexec -e" and "systemctl kexec" are equally
  valid.

  * On comment 3 we proposed a script/approach to auto-test kexecs, used
  here to perform 1000 kexecs with the proposed patch.

  [Regression Potential]

  * Although the patch proposed here introduce a PCI handler, it kept
  the remove handler identical and based shutdown strongly on
  ena_remove(), changing just netdev handling following other upstream
  drivers. It was extensively tested and presented no issue. Also, it's
  self-contained and affect only one driver, so any other cloud
  providers or non-cloud environment wouldn't be even affected by the
  patch.

  * In case of a potential regression, it could manifest as a delay or
  issue on reboot/shutdown path, only if ena driver is in use.

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

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

[Kernel-packages] [Bug 1858299] Re: This laptop contains a touchpadwhich is not recognized.

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-bionic

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

Title:
  This laptop contains a touchpadwhich is not recognized.

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  This laptop contains a touchpad which is not recognized. The laptop is
  the Trekstore Surfbook E11B.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  deathmetal   1119 F pulseaudio
  CurrentDesktop: LXQt
  Date: Sat Jan  4 23:09:34 2020
  InstallationDate: Installed on 2020-01-04 (0 days ago)
  InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TREKSTOR SURFBOOK E11B
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=c3bcb5e6-3626-422a-b348-dbdb31c269d9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: BIOS_V1.1.5
  dmi.board.asset.tag: Default string
  dmi.board.name: Gemini_Lake_Celeron_V01
  dmi.board.vendor: TS_EMDOOR
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrBIOS_V1.1.5:bd08/30/2018:svnTREKSTOR:pnSURFBOOKE11B:pvrDefaultstring:rvnTS_EMDOOR:rnGemini_Lake_Celeron_V01:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Surfbook
  dmi.product.name: SURFBOOK E11B
  dmi.product.sku: NFCN4SW03
  dmi.product.version: Default string
  dmi.sys.vendor: TREKSTOR

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

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

[Kernel-packages] [Bug 1869694] Re: Support SMO8840 as LIS2DH12

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-bionic

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

Title:
  Support SMO8840 as LIS2DH12

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  In Progress

Bug description:
  === Impact ===
  According to ST, HID SMO8840 is for LIS2DH12. In Ubuntu kernel, support for 
this ID is missing in Bionic, and it's mapped to LNG2DM in D/E/F.

  === Fix ===
  * e43d110cdc20 - iio: st_sensors: remap SMO8840 to LIS2DH12
  This is in mainline kernel 5.6, and also 4.19, 5.4, and 5.5 stable trees.

  === Risk of Regression ===
  Low.
  Hans de Goede@redhat, who originally mapped SMO8840 to LNG2DM, confirmed the 
patch works for his Lenovo Ideapad Miix 320: 
  
https://lore.kernel.org/linux-iio/20200224095426.25681-1-jesse.s...@canonical.com/T/#u

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

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

[Kernel-packages] [Bug 1869642] Re: No audio output from Dell WD19 HDMI/DP after resumed from S3 or s2idle

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-bionic

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

Title:
  No audio output from Dell WD19 HDMI/DP after resumed from S3 or s2idle

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  In Progress

Bug description:
  [Impact]
  Plug-in HDMI/DP cable onto docking station after system resumed from 
S3/s2idle, there is no audio output from HDMI/DP even if you select the HDMI/DP 
audio output manually from sound settings.
  It shows this in dmesg when try testing speakers from sound settings
  [ 2052.030247] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 
0x2f0d00. -5

  [Fix]
  This issue has been fixed in 4.16-rc1 by below commit
  4918e1f87c5f PM / runtime: Rework pm_runtime_force_suspend/resume()

  [Test]
  Verified on Dell Latitude 3310 + Dell WD19 docking station

  [Regression Potential]
  Low, it fixes the device usage counter, and should also fix some other runpm 
issues.

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

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

[Kernel-packages] [Bug 1870637] Re: Nvidia+modeset: Can't set 4K@60Hz: HDMI max TMDS frequency 300000KHz

[Daniel van Vugt]

I forgot to mention; if the Nvidia driver is in a mode that will support
Wayland we still hide the Wayland option. To unhide it you need to
uncomment the last line of:

  /usr/lib/udev/rules.d/61-gdm.rules

Although that will reintroduce bug 1705369 so you might need to also use
one of the other workarounds mentioned in that bug.

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

Title:
  Nvidia+modeset: Can't set 4K@60Hz: HDMI max TMDS frequency 30KHz

Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  When i do get it to work, on reboot it'll be back to fullhd.
  this happens on nvidia 440, 435 and 390.

  On X.Org X server it does work.

  Graphics card: nVidia GT1030
  Amp: Onkyo TX-NR646

  On 19.10 there are no problems.
  A couple of weeks ago i tested a daily build and there were no troubles also, 
so this is new.

  My favourite setting: 3840x2160 200% 60hz.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..10.00.0: Error: [Errno 21] Is een map: 
'/proc/driver/nvidia/gpus/:10:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 01:02:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] 
[19da:2476]
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Micro-Star International Co., Ltd. MS-7B84
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=99bd1cce-b30c-44fb-8ead-90317474c33f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.D0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M PRO-M2 (MS-7B84)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.D0:bd12/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2(MS-7B84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B84
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-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.7-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+git20190815-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/nvidia-graphics-drivers-435/+bug/1870637/+subscriptions

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

[Kernel-packages] [Bug 1870637] Re: Nvidia+modeset: Can't set 4K@60Hz: HDMI max TMDS frequency 300000KHz

[Daniel van Vugt]

I forgot to mention; if the Nvidia driver is in a mode that will support
Wayland we still hide the Wayland option. To unhide it you need to
comment out the last line of:

  /usr/lib/udev/rules.d/61-gdm.rules

Although that will reintroduce bug 1705369 so you might need to also use
one of the other workarounds mentioned in that bug.

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

Title:
  Nvidia+modeset: Can't set 4K@60Hz: HDMI max TMDS frequency 30KHz

Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  When i do get it to work, on reboot it'll be back to fullhd.
  this happens on nvidia 440, 435 and 390.

  On X.Org X server it does work.

  Graphics card: nVidia GT1030
  Amp: Onkyo TX-NR646

  On 19.10 there are no problems.
  A couple of weeks ago i tested a daily build and there were no troubles also, 
so this is new.

  My favourite setting: 3840x2160 200% 60hz.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..10.00.0: Error: [Errno 21] Is een map: 
'/proc/driver/nvidia/gpus/:10:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 01:02:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] 
[19da:2476]
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Micro-Star International Co., Ltd. MS-7B84
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=99bd1cce-b30c-44fb-8ead-90317474c33f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.D0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M PRO-M2 (MS-7B84)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.D0:bd12/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2(MS-7B84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B84
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-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.7-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+git20190815-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/nvidia-graphics-drivers-435/+bug/1870637/+subscriptions

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

[Kernel-packages] [Bug 1867591] Re: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch

[Fred Kimmy]

crypto: hisilicon/sec2 - Add pbuffer mode for SEC driver
 crypto: hisilicon/sec2 - Update IV and MAC operation
 crypto: hisilicon/sec2 - Add iommu status check
 crypto: hisilicon/sec2 - Add workqueue for SEC driver.

this aboving sec2 optimize code have a small bug, we have fixing it and
can you revert aboving four patches?

crypto: hisilicon - Use one workqueue per qm instead of per qp
 crypto: hisilicon - qm depends on UACCE
 crypto: hisilicon - remove redundant assignment of pointer ctx
 hisilicon - register zip engine to uacce
 hisilicon - Remove module_param uacce_mode
 uacce: add uacce driver
 uacce: Add documents for uacce
 crypto: hisilicon - Fix duplicate print when qm occur multiple errors
 crypto: hisilicon - Unify error detect process into qm
 crypto: hisilicon - Configure zip RAS error type
 crypto: hisilicon - Unify hardware error init/uninit into QM

this aboving 11 ACC patches is not problem and you merge it.

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

Title:
  [ACC-0316]sync mainline kernel 5.6rc6  ACC patchset into ubuntu HWE
  kernel branch

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

Bug description:
  [Bug Description]
  roce patchset have merged into mainline 5.6rc2 kernel.

  [Steps to Reproduce]
1)
2)
3)

  [Actual Results]

  [Expected Results]

  [Reproducibility]

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

  [Resolution]
  crypto: hisilicon/sec2 - Add pbuffer mode for SEC driver
  crypto: hisilicon/sec2 - Update IV and MAC operation
  crypto: hisilicon/sec2 - Add iommu status check
  crypto: hisilicon/sec2 - Add workqueue for SEC driver.
  crypto: hisilicon - Use one workqueue per qm instead of per qp
  crypto: hisilicon - qm depends on UACCE
  crypto: hisilicon - remove redundant assignment of pointer ctx
  hisilicon - register zip engine to uacce
  hisilicon - Remove module_param uacce_mode
  uacce: add uacce driver
  uacce: Add documents for uacce
  crypto: hisilicon - Fix duplicate print when qm occur multiple errors
  crypto: hisilicon - Unify error detect process into qm
  crypto: hisilicon - Configure zip RAS error type
  crypto: hisilicon - Unify hardware error init/uninit into QM

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

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

[Kernel-packages] [Bug 1864950] Re: [roce-0227]sync mainline kernel 5.6rc3 roce patchset into ubuntu HWE kernel branch

[Ike Panhc]

Patches has been applied to focal/master-next

https://lists.ubuntu.com/archives/kernel-team/2020-April/108836.html


** Changed in: kunpeng920/ubuntu-20.04
   Status: In Progress => Fix Committed

** Changed in: kunpeng920/ubuntu-18.04-hwe
   Status: In Progress => Fix Committed

** Changed in: kunpeng920
   Status: In Progress => Fix Committed

** Changed in: kunpeng920/ubuntu-18.04-hwe
Milestone: None => ubuntu-18.04.5

** Changed in: kunpeng920/ubuntu-20.04
Milestone: None => ubuntu-20.04-ga

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

Title:
  [roce-0227]sync mainline kernel 5.6rc3  roce patchset into ubuntu HWE
  kernel branch

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

Bug description:
  [Bug Description]
  roce patchset have merged into mainline 5.6rc2 kernel.

  [Steps to Reproduce]
    1)
    2)
    3)

  [Actual Results]

  [Expected Results]

  [Reproducibility]

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

  [Resolution]
  RDMA/hns: Optimize eqe buffer allocation flow
  RDMA/hns: Cleanups of magic numbers
  RDMA/hns: fix spelling mistake: "attatch" -> "attach"
  RDMA/hns: Delayed flush cqe process with workqueue
  RDMA/hns: Add the workqueue framework for flush cqe handler
  RDMA/hns: Initialize all fields of doorbells to zero
  RDMA/hns: Optimize qp doorbell allocation flow
  RDMA/hns: Optimize kernel qp wrid allocation flow
  RDMA/hns: Optimize qp param setup flow
  RDMA/hns: Optimize qp buffer allocation flow
  RDMA/hns: Optimize qp number assign flow
  RDMA/hns: Optimize qp context create and destroy flow
  RDMA/hns: Optimize qp destroy flow
  RDMA/hns: Stop doorbell update while qp state error
  RDMA/hns: Use flush framework for the case in aeq
  RDMA/hns: Treat revision HIP08_A as a special case

  https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git/log/?h=wip
  /jgg-for-next

  RDMA/hns: Treat revision HIP08_A as a special case

  https://www.spinics.net/lists/linux-rdma/msg89428.html

  RDMA/hns: Support to set mininum depth of qp to 0
  https://patchwork.kernel.org/patch/11415067/

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

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

[Kernel-packages] [Bug 1867586] Re: [hns3-0316]sync mainline kernel 5.6rc4 hns3 patchset into ubuntu HWE kernel branch

[Ike Panhc]

Patch has been applied to focal/master-next

https://lists.ubuntu.com/archives/kernel-team/2020-April/108836.html

** Changed in: kunpeng920/ubuntu-20.04
   Status: In Progress => Fix Committed

** Changed in: kunpeng920/ubuntu-18.04-hwe
   Status: In Progress => Fix Committed

** Changed in: kunpeng920
   Status: In Progress => Fix Committed

** Changed in: kunpeng920/ubuntu-20.04
Milestone: None => ubuntu-20.04-ga

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

Title:
  [hns3-0316]sync mainline kernel 5.6rc4  hns3 patchset into ubuntu HWE
  kernel branch

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

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

  [Steps to Reproduce]
    1)
    2)
    3)

  [Actual Results]

  [Expected Results]

  [Reproducibility]

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

  [Resolution]
  net: hns3: clear port base VLAN when unload PF
  net: hns3: fix RMW issue for VLAN filter switch
  net: hns3: fix VF VLAN table entries inconsistent issue
  net: hns3: fix "tc qdisc del" failed issue
  net: hns3: reject unsupported coalescing params
  net: hns3: delete unnecessary logs after kzalloc fails
  net: hns3: synchronize some print relating to reset issue
  net: hns3: print out command code when dump fails in debugfs
  net: hns3: print out status register when VF receives unknown source interrupt
  net: hns3: add a check before PF inform VF to reset
  net: hns3: delete some reduandant code
  net: hns3: remove an unnecessary resetting check in 
hclge_handle_hw_ras_error()
  net: hns3: rename macro HCLGE_MAX_NCL_CONFIG_LENGTH
  net: hns3: fix some mixed type assignment
  net: hns3: fix a not link up issue when fibre port supports autoneg
  net: hns3: add missing help info for QS shaper in debugfs
  net: hns3: add support for dump MAC ID and loopback status in debugfs
  net: hns3: add enabled TC numbers and DWRR weight info in debugfs
  net: hns3: modify an unsuitable print when setting unknown duplex to fibre

  [Status]
  (Rejected] net: hns3: reject unsupported coalescing params
  (In progress) net: hns3: delete unnecessary logs after kzalloc fails
  (In progress) net: hns3: synchronize some print relating to reset issue
  (In progress) net: hns3: print out command code when dump fails in debugfs
  (In progress) net: hns3: print out status register when VF receives unknown 
source interrupt
  (In progress) net: hns3: add a check before PF inform VF to reset
  (In progress) net: hns3: delete some reduandant code
  (In progress) net: hns3: remove an unnecessary resetting check in 
hclge_handle_hw_ras_error()
  (In progress) net: hns3: rename macro HCLGE_MAX_NCL_CONFIG_LENGTH
  (In progress) net: hns3: fix some mixed type assignment
  (In progress) net: hns3: add missing help info for QS shaper in debugfs
  (In progress) net: hns3: add support for dump MAC ID and loopback status in 
debugfs
  (In progress) net: hns3: add enabled TC numbers and DWRR weight info in 
debugfs
  (In progress) net: hns3: modify an unsuitable print when setting unknown 
duplex to fibre
  (Fix committed) net: hns3: clear port base VLAN when unload PF
  (Fix committed) net: hns3: fix RMW issue for VLAN filter switch
  (Fix committed) net: hns3: fix VF VLAN table entries inconsistent issue
  (Fix committed) net: hns3: fix "tc qdisc del" failed issue
  (Fix committed) net: hns3: fix a not link up issue when fibre port supports 
autoneg

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

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

[Kernel-packages] [Bug 1863574] Re: Update mpt3sas Driver to 33.100.00.00 for Ubuntu 20.04

[Michael Reed]

Hi Suganath,

Can you test this in proposed, it is available now in 5.4.0-23.27
 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/proposed?field.series_filter=focal


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

Thank you,
Michael

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

Title:
  Update mpt3sas Driver to 33.100.00.00 for Ubuntu 20.04

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

Bug description:
  [IMPACT]
  This is a feature request to update the mpt3sas driver in focal to latest 
version 33.100.00.00 in Ubuntu 20.04.  This will allow users to use
  fixes and enhancements that landed upstream in 5.6.  For this reason,
  Broadcom and Dell have requested that we pull these patches to update the 
  mpt3sas driver to the current upstream version.  

  [FIXES]
  The following commit ID's from Broadcom that whould be cherry-picked form 
mainline

  commit c53cf10ef6d9faeee9baa1fab824139c6f10a134
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=c53cf10ef6d9faeee9baa1fab824139c6f10a134
  commit c50ed99cd56ee725d9e14dffec8e8f1641b8ca30
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=c50ed99cd56ee725d9e14dffec8e8f1641b8ca30
  commit c6bdb6a10892d1130638a5e28d1523a813e45d5e
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=c6bdb6a10892d1130638a5e28d1523a813e45d5e
  commit 5b061980e362820894d7d884370b37005bed23ec
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=5b061980e362820894d7d884370b37005bed23ec
  commit c59777189433621392f6f5c82ecfc62f00a1232d
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=c59777189433621392f6f5c82ecfc62f00a1232d
  commit fce0aa08792b3ae725395fa25d44507dee0b603b
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=fce0aa08792b3ae725395fa25d44507dee0b603b
  commit e8c2307e6a690db9aaff84153b2857c5c4dfd969
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=e8c2307e6a690db9aaff84153b2857c5c4dfd969
  commit 36c6c7f75b0998f5a4b5c79cbb94ee1ab4ee35c0
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=36c6c7f75b0998f5a4b5c79cbb94ee1ab4ee35c0
  commit d3f623ae8e0323ca434ee9029100312a8be37773
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=d3f623ae8e0323ca434ee9029100312a8be37773
  commit 1ade26b616cc2da0b7277a97e3799c99bae0655b
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=1ade26b616cc2da0b7277a97e3799c99bae0655b
  commit ee560e7bbab0c10cf3f0e71997fbc354ab2ee5cb
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=ee560e7bbab0c10cf3f0e71997fbc354ab2ee5cb
  commit 5bb2f743cdaa6da618e77a6aab5c38b46072365b
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=5bb2f743cdaa6da618e77a6aab5c38b46072365b
  commit 3524a38e594dd5f090cbc3226e5f47cb4067fac7
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=3524a38e594dd5f090cbc3226e5f47cb4067fac7
  commit d8b2625f4699a36b1753d87e96b0c50a4531c065
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=d8b2625f4699a36b1753d87e96b0c50a4531c065
  commit 9e64fd1e65f72d229f96fcf390576e772770a01c
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=9e64fd1e65f72d229f96fcf390576e772770a01c
  commit 77fd4f2c88bf83205a21f9ca49fdcc0c7868dba9
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=77fd4f2c88bf83205a21f9ca49fdcc0c7868dba9
  commit b06ff10249036eec74fa8565503ac40d0ee92213
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=b06ff10249036eec74fa8565503ac40d0ee92213
  commit 29f571f8b4cc652cae9244630f714a610549d301
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=29f571f8b4cc652cae9244630f714a610549d301
  commit a8a6cbcd038de4ee3722c17edd7a4d84ce423f7d
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=a8a6cbcd038de4ee3722c17edd7a4d84ce423f7d
  commit a066f4c31359d07b1a2c5144b4b9a29901365fd0
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=a066f4c31359d07b1a2c5144b4b9a29901365fd0
  commit dd180e4eedfd85b80020a6fd566601f4765a9d69
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=dd180e4eedfd85b80020a6fd566601f4765a9d69
  commit 08e7378ee331a803cfdd91c512a3dea040f1da79
  

[Kernel-packages] [Bug 1863581] Re: Ubuntu 20.04: megaraid_sas driver update to version 07.713.01.00-rc1

[Michael Reed]

Hi Sumit,

Can you test this in proposed, it is available now in 5.4.0-23.27

https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/proposed?field.series_filter=focal

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

Thank you,
Michael

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

Title:
  Ubuntu 20.04: megaraid_sas driver update to version 07.713.01.00-rc1

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

Bug description:
  [IMPACT]
  This is a feature request to update megaraid_sas driver in Ubuntu 20.04 
release to latest Linux upstream tip.
  The current latest upstream megaraid_sas driver version is- 07.713.01.00-rc1.
  The current latest Ubuntu 20.04 Pre GA kernel has megaraid_sas driver 
version- 07.710.50.00-rc1. This will allow users to utilize features of
  the PERC 11 device. For this reason, Broadcom and Dell have requested that we 
pull these patches to update the megaraid_sas driver to the current upstream 
version.

  [FIXES]
  Below set of upstream commit ids will lift driver version to 07.713.01.00-rc1 
from 07.710.50.00-rc1:

  92b4f9d15059 scsi: megaraid_sas: fixup MSIx interrupt setup during resume
  824b72db5086 scsi: megaraid_sas: Update driver version to 07.713.01.00-rc1
  4d1634b8d12e scsi: megaraid_sas: Use Block layer API to check SCSI device 
in-flight IO requests
  56ee0c585602 scsi: megaraid_sas: Limit the number of retries for the IOCTLs 
causing firmware fault
  6d7537270e32 scsi: megaraid_sas: Do not initiate OCR if controller is not in 
ready state
  201a810cc188 scsi: megaraid_sas: Re-Define enum DCMD_RETURN_STATUS
  eeb63c23ffe1 scsi: megaraid_sas: Do not set HBA Operational if FW is not in 
operational state
  9330a0fd827a scsi: megaraid_sas: Do not kill HBA if JBOD Seqence map or RAID 
map is disabled
  eb974f34bb9d scsi: megaraid_sas: Do not kill host bus adapter, if adapter is 
already dead
  6e73550670ed scsi: megaraid_sas: Update optimal queue depth for SAS and NVMe 
devices
  a7faf81d7858 scsi: megaraid_sas: Set no_write_same only for Virtual Disk
  499e7246d6da scsi: megaraid_sas: Reset adapter if FW is not in READY state 
after device resume
  73374b39b01e scsi: megaraid_sas: Make poll_aen_lock static
  01b8bca81e18 compat_ioctl: use correct compat_ptr() translation in drivers
  8cfb8e40d686 scsi: megaraid_sas: remove unused variables 'debugBlk','fusion'
  ff7ca7fd03ce scsi: megaraid_sas: Unique names for MSI-X vectors
  9ab089d30bcf scsi: megaraid_sas: Introduce module parameter for default queue 
depth
  e5460f084b84 scsi: megaraid_sas: Fix a compilation warning
  88d5c343949e scsi: megaraid_sas: Make a bunch of functions static
  e45ab43b1d40 scsi: megaraid_sas: Make some functions static
  3b5f307ef3cb scsi: megaraid_sas: fix panic on loading firmware crashdump
  359603a3847e scsi: megaraid_sas: fix spelling mistake "megarid_sas" -> 
"megaraid_sas"
  07d9aa143464 scsi: megaraid_sas: set an unlimited max_segment_size

  Here is the link to latest Linux upstream megaraid_sas driver source:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/scsi/megaraid

  Please let me know if any further information is required.

  Thanks,
  Sumit

  All are clean cherry picks into the 5.4 branch and can be pulled from the
  following branch:

  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/lp1863581_megaraid_sas

  [TESTING]
  Modinfo should show that the megaraid_sas driver has been updated to 
07.713.01.00

  [REGRESSION RISK]
  Low - Focal is not yet released, this is not being backported to current 
releases.

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

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

[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

[Seth Arnold]

I should point out that the period bursts of writes every five seconds
in my vmstat 1 output is due to zfs's flushing mechanism; by default it
flushes dirty pages every five seconds.

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

Title:
  swap storms kills interactive use

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

Bug description:
  [Impact]

  High watermark boosting can cause large swap activity under certain
  memory intensive workloads, making the system very unresponsive
  (screen does not refresh, keyboard not responding, etc.).

  This large swap activity seems to be prevented disabling high
  watermark boosting.

  [Test case]

  Opening this web page in chrome seems to be a good reproducer of the
  problem:

  
https://platform.leolabs.space/visualizations/conjunction?type=conjunction=2004981040

  When this page is opened we can clearly see from 'top' (for example)
  that the used swap is going up very quickly.

  With the fix applied swap is not used at all and the system is always
  responsive.

  [Fix]

  Set vm.watermark_boost_factor to 0, disabling watermark boosting by
  default.

  [Regression potential]

  Regression potential is minimal, setting vm.watermark_boost_factor to
  0 by default restores the old kernel behavior before watermark
  boosting was introduced. In case of unexpected regressions we can
  always fix this in user-space via sysctl.

  [Original report]

  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
     Mixer name : 'Realtek ALC285'
     Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
     Controls  : 53
     Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
     Mixer name : 'USB Mixer'
     Components : 'USB17ef:306f'
     Controls  : 9
     Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 

[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

[Seth Arnold]

Thanks Andrea, I don't think that helped. I'll attach a file with vmstat
1 output and funclatency output, along with a few notes on the testing.

Thanks

** Attachment added: "after-limiting-dirty-bytes"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861359/+attachment/5349071/+files/after-limiting-dirty-bytes

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

Title:
  swap storms kills interactive use

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

Bug description:
  [Impact]

  High watermark boosting can cause large swap activity under certain
  memory intensive workloads, making the system very unresponsive
  (screen does not refresh, keyboard not responding, etc.).

  This large swap activity seems to be prevented disabling high
  watermark boosting.

  [Test case]

  Opening this web page in chrome seems to be a good reproducer of the
  problem:

  
https://platform.leolabs.space/visualizations/conjunction?type=conjunction=2004981040

  When this page is opened we can clearly see from 'top' (for example)
  that the used swap is going up very quickly.

  With the fix applied swap is not used at all and the system is always
  responsive.

  [Fix]

  Set vm.watermark_boost_factor to 0, disabling watermark boosting by
  default.

  [Regression potential]

  Regression potential is minimal, setting vm.watermark_boost_factor to
  0 by default restores the old kernel behavior before watermark
  boosting was introduced. In case of unexpected regressions we can
  always fix this in user-space via sysctl.

  [Original report]

  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
     Mixer name : 'Realtek ALC285'
     Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
     Controls  : 53
     Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
     Mixer name : 'USB Mixer'
     Components : 'USB17ef:306f'
     Controls  : 9
     Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset 

[Kernel-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!

[Здравко]

Hi @caldarella,
You can see if your are using the firmware on focus in this thread using the 
results from:

glxinfo -v | grep renderer
DRI_PRIME=1 glxinfo -v | grep renderer
inxi -xxG
DRI_PRIME=1 inxi -xxG

Is somewhere inside "AMD OLAND"? If not, you can't find anything useful for you 
in this thread!
And last, but not least: Are you sure the linux-firmware package is up to date? 
If not, use:

sudo apt-get install linux-firmware

Good luck!

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

Title:
  [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to
  reset the VCPU!!!

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-firmware source package in Eoan:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact] 
  Firmware update of radeon/oland_rlc.bin breaks some radeon cards.

  [Fix]
  Revert the new firmware.

  [Regression Potential]
  Low. The old firmware has been used for a long time.

  === Original Bug Report ===

  when trying > DRI_PRIME=1 glxgears , the result in dmesg is as
  following

  [  +0.91] radeon :01:00.0: WB enabled
  [  +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x8c00 and cpu addr 0x8ac2d26f
  [  +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x8c04 and cpu addr 0xa848de20
  [  +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x8c08 and cpu addr 0x1e4494a9
  [  +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x8c0c and cpu addr 0x98a9748e
  [  +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x8c10 and cpu addr 0xb6ff734d
  [  +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0x6b4da526
  [  +0.100566] radeon :01:00.0: failed VCE resume (-110).
  [  +0.179115] [drm] ring test on 0 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 1 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 2 succeeded in 1 usecs
  [  +0.06] [drm] ring test on 3 succeeded in 3 usecs
  [  +0.04] [drm] ring test on 4 succeeded in 3 usecs
  [  +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
giving up!!!
  [  +0.40] radeon :01:00.0: failed initializing UVD (-1).
  [  +0.60] [drm] ib test on ring 0 succeeded in 0 usecs
  [  +0.51] [drm] ib test on ring 1 succeeded in 0 usecs
  [  +0.32] [drm] ib test on ring 2 succeeded in 0 usecs
  [  +0.52] [drm] ib test on ring 3 succeeded in 0 usecs
  [  +0.29] [drm] ib test on ring 4 succeeded in 0 usecs

  Also it affects the boot time.

  the used OpenGL renderer is:
  "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Fri Feb 28 11:50:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA 

[Kernel-packages] [Bug 1867803] Re: ALSA: No soundcards found after updating kernel to 5.3.0.42.36

[Hui Wang]

@Arnau,

According to dmesg2, the firmware is still not loaded successfully. If
you really created symlink for sof-cfl.ri, it looks like the firmware
sof-cnl.ri is not suitable for cfl platform. please double check the
symlink is correct: ls -la /lib/firmware/intel/sof

[3.680733] sof-audio-pci :00:1f.3: Direct firmware load for 
intel/sof/sof-cfl.ri failed with error -2
[3.680735] sof-audio-pci :00:1f.3: error: request firmware 
intel/sof/sof-cfl.ri failed err: -2
[3.680736] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2
[3.680992] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2

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

Title:
  ALSA: No soundcards found after updating kernel to 5.3.0.42.36

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  There seems to be some changes in ALSA in 5.3.0.41 and it seems to
  have caused some regression on my HP Spectrre (details attached).

  ~$ alsactl init
  alsactl: init:1759: No soundcards found...

  I verified that 5.3.0.40 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-42-generic 5.3.0-42.34
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 18 01:11:42 2020
  InstallationDate: Installed on 2019-07-11 (249 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: HP HP Spectre x360 Convertible 13-ap0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=57fb6fa4-a696-476b-813a-635b91fbc299 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.28
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8514
  dmi.board.vendor: HP
  dmi.board.version: 09.48
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.28:bd04/22/2019:svnHP:pnHPSpectrex360Convertible13-ap0xxx:pvr:rvnHP:rn8514:rvr09.48:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ap0xxx
  dmi.product.sku: 5KX23PA#ABJ
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!

[Carmelo Caldarella]

** Attachment removed: "2020-04-01 10.29.19 - journalctl - dell-studio-1537 - 
Ubuntu 19.10.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1865130/+attachment/5344222/+files/2020-04-01%2010.29.19%20-%20journalctl%20-%20dell-studio-1537%20-%20Ubuntu%2019.10.txt

** Attachment added: "2020-04-07 20.14.53 - dell-studio-1537 - Xubuntu 20.04 - 
journalctl.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1865130/+attachment/5349061/+files/2020-04-07%2020.14.53%20-%20dell-studio-1537%20-%20Xubuntu%2020.04%20-%20journalctl.txt

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

Title:
  [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to
  reset the VCPU!!!

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-firmware source package in Eoan:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact] 
  Firmware update of radeon/oland_rlc.bin breaks some radeon cards.

  [Fix]
  Revert the new firmware.

  [Regression Potential]
  Low. The old firmware has been used for a long time.

  === Original Bug Report ===

  when trying > DRI_PRIME=1 glxgears , the result in dmesg is as
  following

  [  +0.91] radeon :01:00.0: WB enabled
  [  +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x8c00 and cpu addr 0x8ac2d26f
  [  +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x8c04 and cpu addr 0xa848de20
  [  +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x8c08 and cpu addr 0x1e4494a9
  [  +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x8c0c and cpu addr 0x98a9748e
  [  +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x8c10 and cpu addr 0xb6ff734d
  [  +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0x6b4da526
  [  +0.100566] radeon :01:00.0: failed VCE resume (-110).
  [  +0.179115] [drm] ring test on 0 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 1 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 2 succeeded in 1 usecs
  [  +0.06] [drm] ring test on 3 succeeded in 3 usecs
  [  +0.04] [drm] ring test on 4 succeeded in 3 usecs
  [  +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
giving up!!!
  [  +0.40] radeon :01:00.0: failed initializing UVD (-1).
  [  +0.60] [drm] ib test on ring 0 succeeded in 0 usecs
  [  +0.51] [drm] ib test on ring 1 succeeded in 0 usecs
  [  +0.32] [drm] ib test on ring 2 succeeded in 0 usecs
  [  +0.52] [drm] ib test on ring 3 succeeded in 0 usecs
  [  +0.29] [drm] ib test on ring 4 succeeded in 0 usecs

  Also it affects the boot time.

  the used OpenGL renderer is:
  "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Fri Feb 28 11:50:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  

[Kernel-packages] [Bug 1866852] Re: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor

[Steve Langasek]

** Package changed: grub (Ubuntu) => grub2 (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/1866852

Title:
  System Display black screen on reboot or after a clean shutdown with
  USB-C Dock Monitor

Status in grub2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  I'm running focal devel and the latest kernel (see proc version below)

  Linux version 5.4.0-18-generic (buildd@lgw01-amd64-034) (gcc version
  9.2.1 20200306 (Ubuntu 9.2.1-31ubuntu3)) #22-Ubuntu SMP Sat Mar 7
  18:13:06 UTC 2020

  Dock Monitor is supported very well with multiple usb devices plugged
  on the monitor.

  However on reboot I face a black screen with no ability to enter my FDE 
password.
  Both my Laptop screen and the attached usb-c display nothing
  I have to hard power off and reboot without the USB-C monitor plugged in.

  Otherwise A reboot cycle with the usb-c unplugged works perfectly.

  Also I tried to run ubuntu-bug linux or ubuntu-bug linux-image-generic 
without success. I would be happy to provide much more debugging information. I 
will attach then to the launchpad Bug #
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mclemenceau   2988 F pulseaudio
   /dev/snd/controlC0:  mclemenceau   2988 F pulseaudio
   /dev/snd/controlC1:  mclemenceau   2988 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-05 (64 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  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=/vmlinuz-5.4.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.186
  Tags:  focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-23 (47 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.41
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.21:bd06/14/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.41:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.product.sku: 2TV18AS#ABA
  dmi.sys.vendor: HP

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1871408

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

** Tags added: focal

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

Title:
  Upgrading 18.04 to 20.04 causes Network/WIFI Throughput Slowdowns

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In brief, I upgraded Kubuntu 18.04 to 20.04 Beta.

  STEPS TO REPRODUCE
  1. Connecting to as yet "random"(?) websites (duckduckgo, startpage, and 
OMGUbuntu for example) can result in extenuated wait times for page loading.
  2. Attempting to updatwapt leads to failures to fetch.
  3. Connecting to Speedtest.net resulted in 300 mbps upload and download 
whereas onnecting to https://www.speakeasy.net/speedtest/ resulted in a 
Connection Has Timed Out Error. 

  System:Host: ThinkPad Kernel: 5.4.0-21-generic x86_64 bits: 64 Desktop: 
KDE Plasma 5.18.3 
 Distro: Ubuntu 20.04 LTS (Focal Fossa) 
  Machine:   Type: Laptop System: LENOVO product: 20HF0012US v: ThinkPad T470s 
serial:  
 Mobo: LENOVO model: 20HF0012US v: SDK0J40697 WIN serial: 
 UEFI: LENOVO v: N1WET31W (1.10 ) 
 date: 04/17/2017 
  Battery:   ID-1: BAT0 charge: 21.6 Wh condition: 22.0/23.5 Wh (94%) 
 ID-2: BAT1 charge: 21.4 Wh condition: 21.7/26.3 Wh (82%) 
  CPU:   Topology: Dual Core model: Intel Core i5-7300U bits: 64 type: MT 
MCP L2 cache: 3072 KiB 
 Speed: 800 MHz min/max: 400/3500 MHz Core speeds (MHz): 1: 792 2: 
830 3: 809 4: 822 
  Graphics:  Device-1: Intel HD Graphics 620 driver: i915 v: kernel 
 Display: x11 server: X.Org 1.20.7 driver: modesetting unloaded: 
fbdev,vesa resolution: 1920x1080~60Hz 
 OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 
20.0.2 
  Audio: Device-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel 
 Sound Server: ALSA v: k5.4.0-21-generic 
  Network:   Device-1: Intel Ethernet I219-LM driver: e1000e 
 IF: enp0s31f6 state: down mac: c8:5b:76:e3:99:5b 
 Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi 
 IF: wlp58s0 state: up mac: f8:59:71:49:f6:2e 
  Drives:Local Storage: total: 476.94 GiB used: 272.06 GiB (57.0%) 
 ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 PRO 512GB size: 
476.94 GiB 
  Partition: ID-1: / size: 33.65 GiB used: 22.44 GiB (66.7%) fs: ext4 dev: 
/dev/nvme0n1p2 
 ID-2: swap-1 size: 15.62 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/nvme0n1p4 
  Sensors:   System Temperatures: cpu: 36.5 C mobo: N/A 
 Fan Speeds (RPM): cpu: 0 
  Info:  Processes: 236 Uptime: 1d 19h 44m Memory: 19.43 GiB used: 6.50 GiB 
(33.5%) Shell: bash inxi: 3.0.38

  WORKAROUND:

  This may have to do with a Kernel Regression or is at least Kernel
  related? (This is getting quickly above my pay grade.) I used Grub
  Customizer to boot with kernel 4.18.5-041805-generic and network
  connectivity/throughput is now functioning as it should.

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

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

[Kernel-packages] [Bug 1866852] Re: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor

[Matthieu Clemenceau]

After removing all devices plugged in one by one,  Issue seems to be
caused by my USB dongle needed for my wireless keyboard and mouse...

I've seen report online see below

https://askubuntu.com/questions/884199/grub-freezes-when-logitech-unifying-receiver-plugged-in
https://h30434.www3.hp.com/t5/Notebook-Operating-System-and-Recovery/Linux-Spectre-x360-13-late-2019-does-not-work-with-Linux/td-p/7316977

Those two reports seem limited to my hardware, could be HP BIOS.

the recommended workaround is to enable Legacy Mode which isn't
acceptable for me since it requires to disable Secure Boot.

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

Title:
  System Display black screen on reboot or after a clean shutdown with
  USB-C Dock Monitor

Status in grub2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  I'm running focal devel and the latest kernel (see proc version below)

  Linux version 5.4.0-18-generic (buildd@lgw01-amd64-034) (gcc version
  9.2.1 20200306 (Ubuntu 9.2.1-31ubuntu3)) #22-Ubuntu SMP Sat Mar 7
  18:13:06 UTC 2020

  Dock Monitor is supported very well with multiple usb devices plugged
  on the monitor.

  However on reboot I face a black screen with no ability to enter my FDE 
password.
  Both my Laptop screen and the attached usb-c display nothing
  I have to hard power off and reboot without the USB-C monitor plugged in.

  Otherwise A reboot cycle with the usb-c unplugged works perfectly.

  Also I tried to run ubuntu-bug linux or ubuntu-bug linux-image-generic 
without success. I would be happy to provide much more debugging information. I 
will attach then to the launchpad Bug #
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mclemenceau   2988 F pulseaudio
   /dev/snd/controlC0:  mclemenceau   2988 F pulseaudio
   /dev/snd/controlC1:  mclemenceau   2988 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-05 (64 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  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=/vmlinuz-5.4.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.186
  Tags:  focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-23 (47 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.41
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.21:bd06/14/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.41:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.product.sku: 2TV18AS#ABA
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)

[Tomislav]

Is there anything a Ubuntu 18.04 user (upgraded from the preinstalled
Dell XPS Ubuntu 16.04) can do without manually replacing kernels and
possibly compromising laptop bootability?

This is what I'm currently running:

$ uname -a
Linux dell-desktop 4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:09:48 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

This is what iwconfig claims:

$ iwconfig 
lono wireless extensions.

wlp2s0IEEE 802.11  ESSID:"AndroidAPCC99"  
  Mode:Managed  Frequency:2.422 GHz  Access Point: 66:89:F1:8F:8C:99   
  Bit Rate=1 Mb/s   Tx-Power=20 dBm   
  Retry short limit:7   RTS thr:off   Fragment thr:off
  Power Management:off
  Link Quality=70/70  Signal level=-24 dBm  
  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
  Tx excessive retries:0  Invalid misc:51   Missed beacon:0

In practice, I get up to 20 Mb/s UL/DL when communicating with an FTP
server on my phone (both my laptop and the phone support 802.11ac).
Another laptop easily reaches 50 Mb/s in the same scenario.

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

Title:
  Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless
  1535)

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed

Bug description:
  Update (2017-05-20):
  Kalle Valo suggested a hack which increased client -> AP TCP performance - so 
it does not look like a firmware issue as I thought originally, rather an 
ath10k driver issue:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/11
  https://patchwork.kernel.org/patch/5784701/ (the hack is at the bottom)
  Tested here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/17

  Update: added some forensics in the paste (a long read):
  http://paste.ubuntu.com/24118478/

  -

  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
  qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535

  Original message:
  --
  I experience a very poor 802.11ac performance of a QCA6174 Wireless card 
(Killer Wireless 1535).

  This is a dev version of Zesty with a recently released 4.10 kernel:

  uname -r
  4.10.0-9-generic

  dpkg -l linux-firmware | grep ii
  ii  linux-firmware 1.163all  Firmware for Linux kernel drivers

  lspci -vvv:

  ...
  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
  Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network 
Adapter
  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: ath10k_pci
  Kernel modules: ath10k_pci

  -

  Testing wireless speed with RT-87U 802.11ac router shows that the
  speed is only 27.3 megabits per second which is very low for an
  802.11ac card:

  iperf -c rtr
  
  Client connecting to rtr, TCP port 5001
  TCP window size: 85.0 KByte (default)
  
  [  3] local 10.10.10.78 port 48930 connected with 10.10.10.1 port 5001
  [ ID] Interval   Transfer Bandwidth
  [  3]  0.0-10.0 sec  32.6 MBytes  27.3 Mbits/sec

  

  For comparison, on the same network (from the same distance to the
  router) I have the following result with an Intel's card (on a 4.8
  kernel, different laptop):

  UX32LN:~$ lspci | grep 7260
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  UX32LN:~$ iperf -c rtr
  
  Client connecting to rtr, TCP port 5001
  TCP window size: 85.0 KByte (default)
  
  [ 3] local 10.10.10.208 port 37196 connected with 10.10.10.1 port 5001
  [ ID] Interval Transfer Bandwidth
  [ 3] 0.0-10.1 sec 237 MBytes 198 Mbits/sec
  administrator@UX32LN:~$ lsp
  lspci lspcmcia lspgpot

  200 Mbps is much better.

  ---

  Back to the problematic card:

  Booted 16.04.2 with the rolling HWE kernel 4.8:

  journalctl -k | grep -i ath
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: enabling device ( 
-> 0002)
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: pci irq msi 
oper_irq_mode 2 irq_mode 0 reset_mode 0
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/pre-cal-pci-:3b:00.0.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 

[Kernel-packages] [Bug 1866852] Re: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor

[Matthieu Clemenceau]

** Also affects: grub (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  System Display black screen on reboot or after a clean shutdown with
  USB-C Dock Monitor

Status in grub package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  I'm running focal devel and the latest kernel (see proc version below)

  Linux version 5.4.0-18-generic (buildd@lgw01-amd64-034) (gcc version
  9.2.1 20200306 (Ubuntu 9.2.1-31ubuntu3)) #22-Ubuntu SMP Sat Mar 7
  18:13:06 UTC 2020

  Dock Monitor is supported very well with multiple usb devices plugged
  on the monitor.

  However on reboot I face a black screen with no ability to enter my FDE 
password.
  Both my Laptop screen and the attached usb-c display nothing
  I have to hard power off and reboot without the USB-C monitor plugged in.

  Otherwise A reboot cycle with the usb-c unplugged works perfectly.

  Also I tried to run ubuntu-bug linux or ubuntu-bug linux-image-generic 
without success. I would be happy to provide much more debugging information. I 
will attach then to the launchpad Bug #
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mclemenceau   2988 F pulseaudio
   /dev/snd/controlC0:  mclemenceau   2988 F pulseaudio
   /dev/snd/controlC1:  mclemenceau   2988 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-05 (64 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  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=/vmlinuz-5.4.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.186
  Tags:  focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-23 (47 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.41
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.21:bd06/14/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.41:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.product.sku: 2TV18AS#ABA
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1870092] Re: ftbfs in focal

[Seth Forshee]

You rebuilt the package with a different compiler than what was used to
compute the signatures/checksums in the kernel build, so you get
different objects and mismatching checksums. This is expected.

** Changed in: linux-restricted-modules-gcp (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  ftbfs in focal

Status in linux-restricted-modules-gcp package in Ubuntu:
  Invalid

Bug description:
  seen in the second focal test rebuild
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18946776/+files/buildlog_ubuntu-focal-amd64.linux-restricted-modules-gcp_5.4.0-1005.5_BUILDING.txt.gz

  II: dkms-build installing nvidia-390 into 
/<>/debian/linux-modules-nvidia-390-5.4.0-1005-gcp/lib/modules/5.4.0-1005-gcp/kernel/nvidia-390
  copying nvidia-uvm.ko
  copying nvidia.ko
  copying nvidia-drm.ko
  copying nvidia-modeset.ko
  II: dkms-build override dkms-build--nvidia-N found, executing
  II: checking gcc version ...
  GCC: (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306
  gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0
  Copyright (C) 2019 Free Software Foundation, Inc.
  This is free software; see the source for copying conditions.  There is NO
  warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

  WW: gcc version missmatch between linux and linux-restricted-modules
  WW: was: gcc (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306  is: gcc (Ubuntu 
9.3.0-8ubuntu1) 9.3.0
  II: adding signatures from /usr/lib/linux/5.4.0-1005-gcp ...
  nvidia-drm.ko: FAILED
  nvidia-modeset.ko: FAILED
  nvidia-uvm.ko: FAILED
  nvidia.ko: FAILED
  sha256sum: WARNING: 4 computed checksums did NOT match
  make[1]: *** [debian/rules:129: nvidia-gcp] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:82: binary] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-gcp/+bug/1870092/+subscriptions

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

[Kernel-packages] [Bug 1870094] Re: ftbfs in focal

[Seth Forshee]

You rebuilt the package with a different compiler than what was used to
compute the signatures/checksums in the kernel build, so you get
different objects and mismatching checksums. This is expected.

** Changed in: linux-restricted-modules-oracle (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  ftbfs in focal

Status in linux-restricted-modules-oracle package in Ubuntu:
  Invalid

Bug description:
  seen in the second focal test rebuild
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18946778/+files/buildlog_ubuntu-focal-amd64.linux-restricted-modules-oracle_5.4.0-1005.5_BUILDING.txt.gz

  II: dkms-build installing nvidia-390 into 
/<>/debian/linux-modules-nvidia-390-5.4.0-1005-oracle/lib/modules/5.4.0-1005-oracle/kernel/nvidia-390
  copying nvidia-uvm.ko
  copying nvidia.ko
  copying nvidia-drm.ko
  copying nvidia-modeset.ko
  II: dkms-build override dkms-build--nvidia-N found, executing
  II: checking gcc version ...
  GCC: (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306
  gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0
  Copyright (C) 2019 Free Software Foundation, Inc.
  This is free software; see the source for copying conditions.  There is NO
  warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

  WW: gcc version missmatch between linux and linux-restricted-modules
  WW: was: gcc (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306  is: gcc (Ubuntu 
9.3.0-8ubuntu1) 9.3.0
  II: adding signatures from /usr/lib/linux/5.4.0-1005-oracle ...
  nvidia-drm.ko: FAILED
  nvidia-modeset.ko: FAILED
  nvidia-uvm.ko: FAILED
  nvidia.ko: FAILED
  sha256sum: WARNING: 4 computed checksums did NOT match
  make[1]: *** [debian/rules:129: nvidia-oracle] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:82: binary] Error 2
  dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-oracle/+bug/1870094/+subscriptions

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

[Kernel-packages] [Bug 1871408] Re: Upgrading 18.04 to 20.04 causes Network/WIFI Throughput Slowdowns

[Brian Murray]

** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  Upgrading 18.04 to 20.04 causes Network/WIFI Throughput Slowdowns

Status in linux package in Ubuntu:
  New

Bug description:
  In brief, I upgraded Kubuntu 18.04 to 20.04 Beta.

  STEPS TO REPRODUCE
  1. Connecting to as yet "random"(?) websites (duckduckgo, startpage, and 
OMGUbuntu for example) can result in extenuated wait times for page loading.
  2. Attempting to updatwapt leads to failures to fetch.
  3. Connecting to Speedtest.net resulted in 300 mbps upload and download 
whereas onnecting to https://www.speakeasy.net/speedtest/ resulted in a 
Connection Has Timed Out Error. 

  System:Host: ThinkPad Kernel: 5.4.0-21-generic x86_64 bits: 64 Desktop: 
KDE Plasma 5.18.3 
 Distro: Ubuntu 20.04 LTS (Focal Fossa) 
  Machine:   Type: Laptop System: LENOVO product: 20HF0012US v: ThinkPad T470s 
serial:  
 Mobo: LENOVO model: 20HF0012US v: SDK0J40697 WIN serial: 
 UEFI: LENOVO v: N1WET31W (1.10 ) 
 date: 04/17/2017 
  Battery:   ID-1: BAT0 charge: 21.6 Wh condition: 22.0/23.5 Wh (94%) 
 ID-2: BAT1 charge: 21.4 Wh condition: 21.7/26.3 Wh (82%) 
  CPU:   Topology: Dual Core model: Intel Core i5-7300U bits: 64 type: MT 
MCP L2 cache: 3072 KiB 
 Speed: 800 MHz min/max: 400/3500 MHz Core speeds (MHz): 1: 792 2: 
830 3: 809 4: 822 
  Graphics:  Device-1: Intel HD Graphics 620 driver: i915 v: kernel 
 Display: x11 server: X.Org 1.20.7 driver: modesetting unloaded: 
fbdev,vesa resolution: 1920x1080~60Hz 
 OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 
20.0.2 
  Audio: Device-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel 
 Sound Server: ALSA v: k5.4.0-21-generic 
  Network:   Device-1: Intel Ethernet I219-LM driver: e1000e 
 IF: enp0s31f6 state: down mac: c8:5b:76:e3:99:5b 
 Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi 
 IF: wlp58s0 state: up mac: f8:59:71:49:f6:2e 
  Drives:Local Storage: total: 476.94 GiB used: 272.06 GiB (57.0%) 
 ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 PRO 512GB size: 
476.94 GiB 
  Partition: ID-1: / size: 33.65 GiB used: 22.44 GiB (66.7%) fs: ext4 dev: 
/dev/nvme0n1p2 
 ID-2: swap-1 size: 15.62 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/nvme0n1p4 
  Sensors:   System Temperatures: cpu: 36.5 C mobo: N/A 
 Fan Speeds (RPM): cpu: 0 
  Info:  Processes: 236 Uptime: 1d 19h 44m Memory: 19.43 GiB used: 6.50 GiB 
(33.5%) Shell: bash inxi: 3.0.38

  WORKAROUND:

  This may have to do with a Kernel Regression or is at least Kernel
  related? (This is getting quickly above my pay grade.) I used Grub
  Customizer to boot with kernel 4.18.5-041805-generic and network
  connectivity/throughput is now functioning as it should.

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

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

[Kernel-packages] [Bug 1870091] Re: ftbfs in focal

[Seth Forshee]

You rebuilt the package with a different compiler than what was used to
compute the signatures/checksums in the kernel build, so you get
different objects and mismatching checksums. This is expected.

** Changed in: linux-restricted-modules-azure (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  ftbfs in focal

Status in linux-restricted-modules-azure package in Ubuntu:
  Invalid

Bug description:
  seen in the second focal test rebuild
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18946775/+files/buildlog_ubuntu-focal-amd64.linux-restricted-modules-azure_5.4.0-1006.6_BUILDING.txt.gz

  II: dkms-build installing nvidia-390 into 
/<>/debian/linux-modules-nvidia-390-5.4.0-1006-azure/lib/modules/5.4.0-1006-azure/kernel/nvidia-390
  copying nvidia-uvm.ko
  copying nvidia.ko
  copying nvidia-drm.ko
  copying nvidia-modeset.ko
  II: dkms-build override dkms-build--nvidia-N found, executing
  II: checking gcc version ...
  GCC: (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306
  gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0
  Copyright (C) 2019 Free Software Foundation, Inc.
  This is free software; see the source for copying conditions.  There is NO
  warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

  WW: gcc version missmatch between linux and linux-restricted-modules
  WW: was: gcc (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306  is: gcc (Ubuntu 
9.3.0-8ubuntu1) 9.3.0
  II: adding signatures from /usr/lib/linux/5.4.0-1006-azure ...
  nvidia-drm.ko: FAILED
  nvidia-modeset.ko: FAILED
  nvidia-uvm.ko: FAILED
  nvidia.ko: FAILED
  sha256sum: WARNING: 4 computed checksums did NOT match
  make[1]: *** [debian/rules:129: nvidia-azure] Error 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-azure/+bug/1870091/+subscriptions

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

[Kernel-packages] [Bug 1870090] Re: ftbfs in focal

[Seth Forshee]

You rebuilt the package with a different compiler than what was used to
compute the signatures/checksums in the kernel build, so you get
different objects and mismatching checksums. This is expected.

** Changed in: linux-restricted-modules-aws (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  ftbfs in focal

Status in linux-restricted-modules-aws package in Ubuntu:
  Invalid

Bug description:
  seen in the second focal test rebuild
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18946774/+files/buildlog_ubuntu-focal-amd64.linux-restricted-modules-aws_5.4.0-1005.5_BUILDING.txt.gz

  copying nvidia-uvm.ko
  copying nvidia.ko
  copying nvidia-drm.ko
  copying nvidia-modeset.ko
  II: dkms-build override dkms-build--nvidia-N found, executing
  II: checking gcc version ...
  GCC: (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306
  gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0
  Copyright (C) 2019 Free Software Foundation, Inc.
  This is free software; see the source for copying conditions.  There is NO
  warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

  WW: gcc version missmatch between linux and linux-restricted-modules
  WW: was: gcc (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306  is: gcc (Ubuntu 
9.3.0-8ubuntu1) 9.3.0
  II: adding signatures from /usr/lib/linux/5.4.0-1005-aws ...
  nvidia-drm.ko: FAILED
  nvidia-modeset.ko: FAILED
  nvidia-uvm.ko: FAILED
  nvidia.ko: FAILED
  sha256sum: WARNING: 4 computed checksums did NOT match
  make[1]: *** [debian/rules:129: nvidia-aws] Error 1
  make[1]: Leaving directory '/<>'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-aws/+bug/1870090/+subscriptions

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

[Kernel-packages] [Bug 1871408] [NEW] Upgrading 18.04 to 20.04 causes Network/WIFI Throughput Slowdowns

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

In brief, I upgraded Kubuntu 18.04 to 20.04 Beta.

STEPS TO REPRODUCE
1. Connecting to as yet "random"(?) websites (duckduckgo, startpage, and 
OMGUbuntu for example) can result in extenuated wait times for page loading.
2. Attempting to updatwapt leads to failures to fetch.
3. Connecting to Speedtest.net resulted in 300 mbps upload and download whereas 
onnecting to https://www.speakeasy.net/speedtest/ resulted in a Connection Has 
Timed Out Error. 

System:Host: ThinkPad Kernel: 5.4.0-21-generic x86_64 bits: 64 Desktop: KDE 
Plasma 5.18.3 
   Distro: Ubuntu 20.04 LTS (Focal Fossa) 
Machine:   Type: Laptop System: LENOVO product: 20HF0012US v: ThinkPad T470s 
serial:  
   Mobo: LENOVO model: 20HF0012US v: SDK0J40697 WIN serial: 
 UEFI: LENOVO v: N1WET31W (1.10 ) 
   date: 04/17/2017 
Battery:   ID-1: BAT0 charge: 21.6 Wh condition: 22.0/23.5 Wh (94%) 
   ID-2: BAT1 charge: 21.4 Wh condition: 21.7/26.3 Wh (82%) 
CPU:   Topology: Dual Core model: Intel Core i5-7300U bits: 64 type: MT MCP 
L2 cache: 3072 KiB 
   Speed: 800 MHz min/max: 400/3500 MHz Core speeds (MHz): 1: 792 2: 
830 3: 809 4: 822 
Graphics:  Device-1: Intel HD Graphics 620 driver: i915 v: kernel 
   Display: x11 server: X.Org 1.20.7 driver: modesetting unloaded: 
fbdev,vesa resolution: 1920x1080~60Hz 
   OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 
20.0.2 
Audio: Device-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel 
   Sound Server: ALSA v: k5.4.0-21-generic 
Network:   Device-1: Intel Ethernet I219-LM driver: e1000e 
   IF: enp0s31f6 state: down mac: c8:5b:76:e3:99:5b 
   Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi 
   IF: wlp58s0 state: up mac: f8:59:71:49:f6:2e 
Drives:Local Storage: total: 476.94 GiB used: 272.06 GiB (57.0%) 
   ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 PRO 512GB size: 
476.94 GiB 
Partition: ID-1: / size: 33.65 GiB used: 22.44 GiB (66.7%) fs: ext4 dev: 
/dev/nvme0n1p2 
   ID-2: swap-1 size: 15.62 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/nvme0n1p4 
Sensors:   System Temperatures: cpu: 36.5 C mobo: N/A 
   Fan Speeds (RPM): cpu: 0 
Info:  Processes: 236 Uptime: 1d 19h 44m Memory: 19.43 GiB used: 6.50 GiB 
(33.5%) Shell: bash inxi: 3.0.38

WORKAROUND:

This may have to do with a Kernel Regression or is at least Kernel
related? (This is getting quickly above my pay grade.) I used Grub
Customizer to boot with kernel 4.18.5-041805-generic and network
connectivity/throughput is now functioning as it should.

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


** Tags: bot-comment
-- 
Upgrading 18.04 to 20.04 causes Network/WIFI Throughput Slowdowns 
https://bugs.launchpad.net/bugs/1871408
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 1866852] Re: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor

[Matthieu Clemenceau]

I started thinking this wasn't a kernel issue since I wasn't getting any
display from a cold boot...

I changed grub configuration to show menu and remove quiet splash from
Linux CMD LINE and it turns out that when I press the power button the
first thing I see is the Grub menu and no keyboard input are working,
arrows or enter key when USB-C is plugged in but when I unplugged the
USB-Type C monitor, I can press enter during the Grub menu and it boots.

So I believe the issue is with Grub hanging while USB-C monitor plugged
in.

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

Title:
  System Display black screen on reboot or after a clean shutdown with
  USB-C Dock Monitor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm running focal devel and the latest kernel (see proc version below)

  Linux version 5.4.0-18-generic (buildd@lgw01-amd64-034) (gcc version
  9.2.1 20200306 (Ubuntu 9.2.1-31ubuntu3)) #22-Ubuntu SMP Sat Mar 7
  18:13:06 UTC 2020

  Dock Monitor is supported very well with multiple usb devices plugged
  on the monitor.

  However on reboot I face a black screen with no ability to enter my FDE 
password.
  Both my Laptop screen and the attached usb-c display nothing
  I have to hard power off and reboot without the USB-C monitor plugged in.

  Otherwise A reboot cycle with the usb-c unplugged works perfectly.

  Also I tried to run ubuntu-bug linux or ubuntu-bug linux-image-generic 
without success. I would be happy to provide much more debugging information. I 
will attach then to the launchpad Bug #
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mclemenceau   2988 F pulseaudio
   /dev/snd/controlC0:  mclemenceau   2988 F pulseaudio
   /dev/snd/controlC1:  mclemenceau   2988 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-05 (64 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  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=/vmlinuz-5.4.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.186
  Tags:  focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-23 (47 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.41
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.21:bd06/14/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.41:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.product.sku: 2TV18AS#ABA
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1869996] Re: Hibernation can NOT work due to incorrect RESUME=

[Francis Ginther]

Removing linux-azure as this appears to be unrelated.

** No longer affects: linux-azure (Ubuntu)

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

Title:
  Hibernation can NOT work due to incorrect RESUME=

Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu 18.04 I have the below 4 lines, but in Ubuntu 20.04 (dev
  build) these lines are missing:

  --- /usr/share/initramfs-tools/init2020-04-01 01:15:20.533208700 +
  +++ /usr/share/initramfs-tools/init 2020-04-01 00:59:43.931655200 +
  @@ -163,6 +163,10 @@
  ;;
  resume=*)
  RESUME="${x#resume=}"
  +   case $RESUME in
  +   UUID=*)
  +RESUME="/dev/disk/by-uuid/${RESUME#UUID=}"
  +   esac
  ;;
  resume_offset=*)
  resume_offset="${x#resume_offset=}"

  As a result, hibernation can not work: the saved state in the swap
  partition is lost and no resume happens.

  The issue is: when I use the "resume=UUID=533b2cd9-31ac-449b-82ff-
  014f09ab0a9c" kernel parameter for hibernation, due to the missing
  lines, the variable 'resume' in a later place in "/usr/share
  /initramfs-tools/init" is set to "UUID=533b2cd9-31ac-449b-82ff-
  014f09ab0a9c" rather than "/dev/disk/by-uuid/533b2cd9-31ac-449b-82ff-
  014f09ab0a9c". Next, in /usr/share/initramfs-tools/scripts/local-
  premount/resume:

  DEV=$(readlink "$resume")
  DEV=/sys/class/block/${DEV##*/}/dev
  if [ -r "$DEV" ]; then
  read -r MAJMIN < "$DEV"
  fi
  if [ -z "$MAJMIN" ]; then
  exit 1
  fi

  Here the 'readlink' will fail, so $DEV is not pointing to a valid device, and 
then $MAJMIN is empty and
  we "exit 1", so no resume can happen!

  
  Not sure why the 4 lines are removed in Ubuntu 20.04...

  
  PS, this is my version info:

  root@localhost:~# dpkg-query -s initramfs-tools-core
  Package: initramfs-tools-core
  Status: install ok installed
  Priority: optional
  Section: utils
  Installed-Size: 271
  Maintainer: Ubuntu Developers 
  Architecture: all
  Multi-Arch: foreign
  Source: initramfs-tools
  Version: 0.136ubuntu1
  Replaces: initramfs-tools (<< 0.121~)
  Depends: busybox-initramfs (>= 1:1.30.1-4ubuntu5~), initramfs-tools-bin (= 
0.136ubuntu1), klibc-utils (>= 2.0.4-8~), cpio (>= 2.12), lz4, kmod, udev, 
coreutils (>= 8.24), logsave | e2fsprogs (<< 1.45.3-1~)
  Suggests: bash-completion
  Breaks: busybox-initramfs (<< 1:1.30.1-4ubuntu5~), initramfs-tools (<< 0.121~)
  Conffiles:
   /etc/initramfs-tools/initramfs.conf 4ec999d424d01b9ca685e65ba0f22a13
  Description: generic modular initramfs generator (core tools)
   This package contains the mkinitramfs program that can be used to
   create a bootable initramfs for a Linux kernel.  The initramfs should
   be loaded along with the kernel and is then responsible for mounting
   the root filesystem and starting the main init system.
  Original-Maintainer: Debian kernel team 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1869996/+subscriptions

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

[Kernel-packages] [Bug 1870837] Re: hcitool lescan says 'Set scan parameters failed: Input/output error'

[mm]

Bluetoothctl and blueman are both using LE Extended commands and are
therefor working I think.

(btw: I would edit my comments if I could ...)

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

Title:
  hcitool lescan says 'Set scan parameters failed: Input/output error'

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Hi,

  after some testing with Ubuntu 20.04 beta I couldn't get hcitool
  lescan working. I get the following error:

  hcitool lescan
  Set scan parameters failed: Input/output error

  Bluetooth hardware: 
  hci0:   Type: Primary  Bus: USB
  BD Address: 04:EA:56:21:xx:xx  ACL MTU: 1021:4  SCO MTU: 96:6
  UP RUNNING
  RX bytes:1605 acl:0 sco:0 events:123 errors:0
  TX bytes:5801 acl:0 sco:0 commands:123 errors:0
  Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
  Link policy: RSWITCH SNIFF
  Link mode: SLAVE ACCEPT
  Name: 'xx'
  Class: 0x200104
  Service Classes: Audio
  Device Class: Computer, Desktop workstation
  HCI Version: 5.1 (0xa)  Revision: 0x100
  LMP Version: 5.1 (0xa)  Subversion: 0x100
  Manufacturer: Intel Corp. (2)

  It is not hardware related, since I get the same error with a USB
  bluetooth dongle:

  hcitool -i hci1 lescan
  Set scan parameters failed: Input/output error

  hcitool scan is working fine on both devices; bluetoothctl is also working 
and able to find ble devices.
  I would normally prefer bluetoothctl, but I got a software which is based on 
hcitool.

  dmesg shows this errors:
  [  138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already 
present!
  [  138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already 
present!

  Bluez version:
  bluez 5.53-0ubuntu2 amd64

  System:
  Distributor ID: Ubuntu
  Description:Ubuntu Focal Fossa (development branch)
  Release:20.04
  Codename:   focal
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-01 (4 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 
(20200331)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0463: MGE UPS Systems UPS
   Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 
(ZW090) - UZB
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel(R) Client Systems NUC8i3BEH
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/vgcs2ubct-root ro
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/23/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0075.2019.1023.1448
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-306
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-305
  dmi.sys.vendor: Intel(R) Client Systems
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 04:EA:56:21:1E:D3  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:17030 acl:0 sco:0 events:2764 errors:0
TX bytes:677849 acl:0 sco:0 commands:2757 errors:0

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

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

[Kernel-packages] [Bug 1870837] Re: hcitool lescan says 'Set scan parameters failed: Input/output error'

[mm]

It seems to me that the "normal" LE commands are broken and only the LE
Extended commands are working?

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

Title:
  hcitool lescan says 'Set scan parameters failed: Input/output error'

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Hi,

  after some testing with Ubuntu 20.04 beta I couldn't get hcitool
  lescan working. I get the following error:

  hcitool lescan
  Set scan parameters failed: Input/output error

  Bluetooth hardware: 
  hci0:   Type: Primary  Bus: USB
  BD Address: 04:EA:56:21:xx:xx  ACL MTU: 1021:4  SCO MTU: 96:6
  UP RUNNING
  RX bytes:1605 acl:0 sco:0 events:123 errors:0
  TX bytes:5801 acl:0 sco:0 commands:123 errors:0
  Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
  Link policy: RSWITCH SNIFF
  Link mode: SLAVE ACCEPT
  Name: 'xx'
  Class: 0x200104
  Service Classes: Audio
  Device Class: Computer, Desktop workstation
  HCI Version: 5.1 (0xa)  Revision: 0x100
  LMP Version: 5.1 (0xa)  Subversion: 0x100
  Manufacturer: Intel Corp. (2)

  It is not hardware related, since I get the same error with a USB
  bluetooth dongle:

  hcitool -i hci1 lescan
  Set scan parameters failed: Input/output error

  hcitool scan is working fine on both devices; bluetoothctl is also working 
and able to find ble devices.
  I would normally prefer bluetoothctl, but I got a software which is based on 
hcitool.

  dmesg shows this errors:
  [  138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already 
present!
  [  138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already 
present!

  Bluez version:
  bluez 5.53-0ubuntu2 amd64

  System:
  Distributor ID: Ubuntu
  Description:Ubuntu Focal Fossa (development branch)
  Release:20.04
  Codename:   focal
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-01 (4 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 
(20200331)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0463: MGE UPS Systems UPS
   Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 
(ZW090) - UZB
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel(R) Client Systems NUC8i3BEH
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/vgcs2ubct-root ro
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/23/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0075.2019.1023.1448
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-306
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-305
  dmi.sys.vendor: Intel(R) Client Systems
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 04:EA:56:21:1E:D3  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:17030 acl:0 sco:0 events:2764 errors:0
TX bytes:677849 acl:0 sco:0 commands:2757 errors:0

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

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

[Kernel-packages] [Bug 1785171] Re: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection

[Robert Hardy]

FYI in terms of sustainable options I was able to find a very hard to
find .deb with the latest driver as a DKMS module. It works fine for me
on Ubuntu 19.10. I really wish this was in a repository which was part
of universe but I'm never figured out how to do things like that.

# dpkg -l | grep e1000e
ii  e1000e-dkms   3.6.0 
 all  Intel e1000e Ethernet adapter driver (DKMS version)

Details here: https://github.com/koljah-de/e1000e-dkms-debian

The latest V3.6.0 driver I use: https://github.com/koljah-de/e1000e-
dkms-debian/releases/tag/3.6.0

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

Title:
  Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver
  keeps Dropping Internet Connection

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

Bug description:
  I've turned up many, many new server and workstation systems over the
  years on both Linux and Windows. Never seen anything like this
  behaviour I'm witnessing on Ubuntu Server 18.04 before where I simply
  lose Internet connectivity while using a browser.  Ethernet interfaces
  usually either work or they don't work.

  I've configured the Intel I219-V Ethernet interface (wired Ethernet
  connection, there is no wifi on this system) using the e1000e driver
  for Ubuntu.  The Ethernet connection is configured to use
  NetworkManager via Netplan on Ubuntu 18.04 LTS Server version.  ASRock
  Z370m Pro4 motherboard.

  The Ethernet interface will drop the Internet connectivity when I'm
  using either the Firefox or Chrome browser.  It usually happens when
  I'm using the search features of the browser. I can't figure out what
  would cause this type of behaviour.  When the Internet connection
  drops, the only way to get back Internet connectivity is to disconnect
  the wired connection using the Ubuntu features and then re-connect
  (this restarts the NetworkManager service I notice).

  In the NetworkManager logs I do notice an "auth" error about a file or
  directory not found. I've never seen that before.

  Note:  The auth error does not coincide with the loss of Internet
  connectivity, but it does proceed it.  Often there can be many hours
  between the auth error and the actual loss of Internet connectivity.

  After I reconnect the connection (via re-starting the NetworkManager
  service) all will be fine for up to a day or so, but then I stress
  test it with a bunch of searches using the browser and usually I can
  get the Internet connectivity to drop again.  Repeat the disconnect
  and reconnect process again (aka re-start NetworkManager) and the
  Internet connectivity will be fine again.  The longest I've seen it go
  without an "Internet connectivity drop" issue is about 36 hours.

  I notice that the e1000e driver does not list the I219-V as a
  supported Ethernet interface in the Intel documentation for the Linux
  version of the driver.  I'm not sure why that is.  The I219-V is
  supposed to used another driver, but it's not clear there's a Linux
  version for of the driver for the I219-V.

  I'm really disappointed that I've run into this issue with Ubuntu
  Server LTS 18.04 on this motherboard.  I had CentOS Server 7.4 (my
  standard server OS, a great Linux distro) on this same motherboard for
  a week with no issues, so I know the motherboard and the I219-V
  Ethernet interface are 100% good hardware wise and can work properly.
  CentOS 7.4 uses NetworkManager as the default for managing the
  Ethernet interface.

  The only reason I'm using Ubuntu Server 18.04 on this motherboard is
  because of a specific package that Ubuntu has a newer packaged version
  than CentOS. CentOS is extremely stable when it comes to basic server
  functionality.

  Hopefully, this bug with the I219-V Ethernet interface using the
  e1000e drive for Linux can be verified and a fix rolled out.

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

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

[Kernel-packages] [Bug 1870837] Re: hcitool lescan says 'Set scan parameters failed: Input/output error'

[mm]

After some time I am back to:
hcitool lescan
Set scan parameters failed: Input/output error

Issuing
hcitool cmd 0x03 0x0003
< HCI Command: ogf 0x03, ocf 0x0003, plen 0
> HCI Event: 0x0e plen 4
  02 03 0C 00

helps again, but I still can't find any BLE devices with hcitool lescan. 
Nevertheless the i/o error is gone and btmon also doesn't report any error.
Sadly the result is still a non functional lescan ...

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

Title:
  hcitool lescan says 'Set scan parameters failed: Input/output error'

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Hi,

  after some testing with Ubuntu 20.04 beta I couldn't get hcitool
  lescan working. I get the following error:

  hcitool lescan
  Set scan parameters failed: Input/output error

  Bluetooth hardware: 
  hci0:   Type: Primary  Bus: USB
  BD Address: 04:EA:56:21:xx:xx  ACL MTU: 1021:4  SCO MTU: 96:6
  UP RUNNING
  RX bytes:1605 acl:0 sco:0 events:123 errors:0
  TX bytes:5801 acl:0 sco:0 commands:123 errors:0
  Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
  Link policy: RSWITCH SNIFF
  Link mode: SLAVE ACCEPT
  Name: 'xx'
  Class: 0x200104
  Service Classes: Audio
  Device Class: Computer, Desktop workstation
  HCI Version: 5.1 (0xa)  Revision: 0x100
  LMP Version: 5.1 (0xa)  Subversion: 0x100
  Manufacturer: Intel Corp. (2)

  It is not hardware related, since I get the same error with a USB
  bluetooth dongle:

  hcitool -i hci1 lescan
  Set scan parameters failed: Input/output error

  hcitool scan is working fine on both devices; bluetoothctl is also working 
and able to find ble devices.
  I would normally prefer bluetoothctl, but I got a software which is based on 
hcitool.

  dmesg shows this errors:
  [  138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already 
present!
  [  138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already 
present!

  Bluez version:
  bluez 5.53-0ubuntu2 amd64

  System:
  Distributor ID: Ubuntu
  Description:Ubuntu Focal Fossa (development branch)
  Release:20.04
  Codename:   focal
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-01 (4 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 
(20200331)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0463: MGE UPS Systems UPS
   Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 
(ZW090) - UZB
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel(R) Client Systems NUC8i3BEH
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/vgcs2ubct-root ro
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/23/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0075.2019.1023.1448
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-306
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-305
  dmi.sys.vendor: Intel(R) Client Systems
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 04:EA:56:21:1E:D3  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:17030 acl:0 sco:0 events:2764 errors:0
TX bytes:677849 acl:0 sco:0 commands:2757 errors:0

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

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

[Kernel-packages] [Bug 1785171] Re: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection

[Robert Hardy]

FYI a kernel bisection may be outside the skill set of your average user
and chances are much lower without detailed instructions. Please don't
shoot the messenger.

I too have a Asrock motherboard but a ASRock Z370M-ITX/ac. I had a lot
off trouble getting my I219-V NICs to behave on Ubuntu.

I started on 18.04 and eventually went to 19.10 with the Intel e1000e
3.6.0-NAPI driver and a bunch of commands to get good performance.

File transfers were severely impacted but it is immediately obvious in iperf3 
when the card is not performing properly. 
Tweaking several of these options added several hundred Mbps to transfers 
giving a consistent 60MB/s over SMB but I'm still getting half the throughput 
of my Windows 10 workstation when talking to the same Ubuntu server. Given my 
Ubuntu client storage is 5X faster the cause is unknown.

I'm curious if anyone has figured out if the firmware version on the
I219-V NIC is updateable and how. It's odd the same chip users different
drivers and shows different firmware revisions.

$ ethtool -i enp2s0
driver: igb
version: 5.6.0-k
firmware-version:  0. 4-1
$ ethtool -i eno1
driver: e1000e
version: 3.6.0-NAPI
firmware-version: 0.2-4

It's really odd to be using two different drivers for the same NIC:
sudo lspci -v | grep -i ether
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V
DeviceName: Onboard - Ethernet
Subsystem: ASRock Incorporation Ethernet Connection (2) I219-V
02:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection 
(rev 03)

I have this in my rc.local now:
ethtool -A eno1 autoneg off tx off rx off 2> /dev/null || :
ethtool -K eno1 gso off tso off 2> /dev/null || :
ethtool -A enp2s0 autoneg off tx off rx off 2> /dev/null || :
ethtool --set-eee eno1 eee off 2> /dev/null || :
ethtool --set-eee enp2s0 eee off 2> /dev/null || :

1st line turns off flow control, 2nd turns off offloading specifically gso and 
tso, the last ones turn off a energy efficient Ethernet option.
Post tweaks I consistently get 935-958Mbit/s in perf3.

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

Title:
  Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver
  keeps Dropping Internet Connection

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

Bug description:
  I've turned up many, many new server and workstation systems over the
  years on both Linux and Windows. Never seen anything like this
  behaviour I'm witnessing on Ubuntu Server 18.04 before where I simply
  lose Internet connectivity while using a browser.  Ethernet interfaces
  usually either work or they don't work.

  I've configured the Intel I219-V Ethernet interface (wired Ethernet
  connection, there is no wifi on this system) using the e1000e driver
  for Ubuntu.  The Ethernet connection is configured to use
  NetworkManager via Netplan on Ubuntu 18.04 LTS Server version.  ASRock
  Z370m Pro4 motherboard.

  The Ethernet interface will drop the Internet connectivity when I'm
  using either the Firefox or Chrome browser.  It usually happens when
  I'm using the search features of the browser. I can't figure out what
  would cause this type of behaviour.  When the Internet connection
  drops, the only way to get back Internet connectivity is to disconnect
  the wired connection using the Ubuntu features and then re-connect
  (this restarts the NetworkManager service I notice).

  In the NetworkManager logs I do notice an "auth" error about a file or
  directory not found. I've never seen that before.

  Note:  The auth error does not coincide with the loss of Internet
  connectivity, but it does proceed it.  Often there can be many hours
  between the auth error and the actual loss of Internet connectivity.

  After I reconnect the connection (via re-starting the NetworkManager
  service) all will be fine for up to a day or so, but then I stress
  test it with a bunch of searches using the browser and usually I can
  get the Internet connectivity to drop again.  Repeat the disconnect
  and reconnect process again (aka re-start NetworkManager) and the
  Internet connectivity will be fine again.  The longest I've seen it go
  without an "Internet connectivity drop" issue is about 36 hours.

  I notice that the e1000e driver does not list the I219-V as a
  supported Ethernet interface in the Intel documentation for the Linux
  version of the driver.  I'm not sure why that is.  The I219-V is
  supposed to used another driver, but it's not clear there's a Linux
  version for of the driver for the I219-V.

  I'm really disappointed that I've run into this issue with Ubuntu
  Server LTS 18.04 on this motherboard.  I had CentOS Server 7.4 (my
  standard server OS, a great Linux distro) on this same motherboard for
  a week with no issues, so I know the motherboard and the I219-V
  

[Kernel-packages] [Bug 1867803] Re: ALSA: No soundcards found after updating kernel to 5.3.0.42.36

[Arnau]

@hui: Here you go

** Attachment added: "dmesg2"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867803/+attachment/5348993/+files/dmesg2

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

Title:
  ALSA: No soundcards found after updating kernel to 5.3.0.42.36

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  There seems to be some changes in ALSA in 5.3.0.41 and it seems to
  have caused some regression on my HP Spectrre (details attached).

  ~$ alsactl init
  alsactl: init:1759: No soundcards found...

  I verified that 5.3.0.40 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-42-generic 5.3.0-42.34
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 18 01:11:42 2020
  InstallationDate: Installed on 2019-07-11 (249 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: HP HP Spectre x360 Convertible 13-ap0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=57fb6fa4-a696-476b-813a-635b91fbc299 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.28
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8514
  dmi.board.vendor: HP
  dmi.board.version: 09.48
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.28:bd04/22/2019:svnHP:pnHPSpectrex360Convertible13-ap0xxx:pvr:rvnHP:rn8514:rvr09.48:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ap0xxx
  dmi.product.sku: 5KX23PA#ABJ
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1870837] Re: hcitool lescan says 'Set scan parameters failed: Input/output error'

[mm]

Executing "hcitool cmd 0x03 0x0003" made the error with hcitool disappear:
hcitool lescan
LE Scan ...

But hcitool does not seem to work as I can't find any ble devices.
btmon output after executing "hcitool cmd 0x03 0x0003 and hcitool lescan:

> HCI Event: Command Complete (0x0e) plen 4 
>#51 [hci0] 21:45:08.127791
  LE Set Scan Enable (0x08|0x000c) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Scan Parameters (0x08|0x000b) plen 7  
   #52 [hci0] 21:45:08.127962
Type: Passive (0x00)
Interval: 10.000 msec (0x0010)
Window: 10.000 msec (0x0010)
Own address type: Public (0x00)
Filter policy: Accept all advertisement (0x00)
> HCI Event: Command Complete (0x0e) plen 4 
>#53 [hci0] 21:45:08.128699
  LE Set Scan Parameters (0x08|0x000b) ncmd 1
Status: Success (0x00)
< HCI Command: LE Set Scan Parameters (0x08|0x000b) plen 7  
   #54 [hci0] 21:45:08.128795
Type: Passive (0x00)
Interval: 10.000 msec (0x0010)
Window: 10.000 msec (0x0010)
Own address type: Public (0x00)
Filter policy: Accept all advertisement (0x00)
> HCI Event: Command Complete (0x0e) plen 4 
>#55 [hci0] 21:45:08.129744
  LE Set Scan Parameters (0x08|0x000b) ncmd 1
Status: Success (0x00)
< HCI Command: LE Set Scan Enable (0x08|0x000c) plen 2  
   #56 [hci0] 21:45:08.129821
Scanning: Enabled (0x01)
Filter duplicates: Disabled (0x00)
> HCI Event: Command Complete (0x0e) plen 4 
>#57 [hci0] 21:45:08.131737
  LE Set Scan Enable (0x08|0x000c) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Scan Enable (0x08|0x000c) plen 2  
   #58 [hci0] 21:45:08.190201
Scanning: Disabled (0x00)
Filter duplicates: Enabled (0x01)
> HCI Event: Command Complete (0x0e) plen 4 
>#59 [hci0] 21:45:08.200856
  LE Set Scan Enable (0x08|0x000c) ncmd 2
Status: Success (0x00)
@ RAW Close: hcitool

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

Title:
  hcitool lescan says 'Set scan parameters failed: Input/output error'

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Hi,

  after some testing with Ubuntu 20.04 beta I couldn't get hcitool
  lescan working. I get the following error:

  hcitool lescan
  Set scan parameters failed: Input/output error

  Bluetooth hardware: 
  hci0:   Type: Primary  Bus: USB
  BD Address: 04:EA:56:21:xx:xx  ACL MTU: 1021:4  SCO MTU: 96:6
  UP RUNNING
  RX bytes:1605 acl:0 sco:0 events:123 errors:0
  TX bytes:5801 acl:0 sco:0 commands:123 errors:0
  Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
  Link policy: RSWITCH SNIFF
  Link mode: SLAVE ACCEPT
  Name: 'xx'
  Class: 0x200104
  Service Classes: Audio
  Device Class: Computer, Desktop workstation
  HCI Version: 5.1 (0xa)  Revision: 0x100
  LMP Version: 5.1 (0xa)  Subversion: 0x100
  Manufacturer: Intel Corp. (2)

  It is not hardware related, since I get the same error with a USB
  bluetooth dongle:

  hcitool -i hci1 lescan
  Set scan parameters failed: Input/output error

  hcitool scan is working fine on both devices; bluetoothctl is also working 
and able to find ble devices.
  I would normally prefer bluetoothctl, but I got a software which is based on 
hcitool.

  dmesg shows this errors:
  [  138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already 
present!
  [  138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already 
present!

  Bluez version:
  bluez 5.53-0ubuntu2 amd64

  System:
  Distributor ID: Ubuntu
  Description:Ubuntu Focal Fossa (development branch)
  Release:20.04
  Codename:   focal
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-01 (4 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 
(20200331)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 

[Kernel-packages] [Bug 1869531] Re: Shutdown, restart, and hibernate do not work from "power-button"

[Francis Ginther]

Issues appears to be related to the power button applet in the panel
(sorry if the terminology is incorrect) and not with the kernel actually
being able to shutdown/restart/hibernate the system. Also, submitter
indicated they were using budgie in comment #15.

** Package changed: linux (Ubuntu) => budgie-desktop (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/1869531

Title:
  Shutdown, restart, and hibernate do not work from "power-button"

Status in budgie-desktop package in Ubuntu:
  Confirmed

Bug description:
  The shutdown, restart, and hibernate menu items under the "power button" drop 
down in the top right-hand corner of the Gnome desktop do not work.  I can use 
these same options under the application menu.  This issue has been a problem 
since I upgraded from 18.04 to 19.10.  I would like to be able to use these 
menu items, as it is how I work on other systems and having to remember which 
system I am on is not always simple.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  belanger   2197 F pulseaudio
   /dev/snd/controlC0:  belanger   2197 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-26 (154 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  MachineType: BIOSTAR Group A780L3G
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=759460a2-c89a-4d8b-93bc-efc5f7b11d89 ro
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  eoan
  Uname: Linux 5.3.0-42-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: 04/09/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080014
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: A780L3G
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080014:bd04/09/2010:svnBIOSTARGroup:pnA780L3G:pvr:rvnBIOSTARGroup:rnA780L3G:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: A780L3G
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.sys.vendor: BIOSTAR Group

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1869531/+subscriptions

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

[Kernel-packages] [Bug 1860182] Re: zpool scrub malfunction after kernel upgrade

[Launchpad Bug Tracker]

This bug was fixed in the package zfs-linux - 0.7.5-1ubuntu16.9

---
zfs-linux (0.7.5-1ubuntu16.9) bionic; urgency=medium

  * Fix scan rate reporting statistics (LP: #1860182)
- 3322-add-scrub-compat-fixes.patch
- 2200-add-zfs-0.6.x-ioctl-compat-shim.patch (refreshed)
Use the zfs 8.x pool_scan_stat_t extra fields to calculate
the scan progress when using zfs 8.x kernel drivers. For
0.7.5 we can pass the larger 8.x port_scan_stat_t to 0.7.5
zfs w/o problems and ignore these new fields and continue
to use the 0.7.5 rate calculations.
Refresh the ioctl compat shim to export the zfs module
version for the scrub version check.

 -- Colin Ian King   Thu, 27 Feb 2020 17:09:12
+

** Changed in: zfs-linux (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  zpool scrub malfunction after kernel upgrade

Status in zfs-linux package in Ubuntu:
  In Progress
Status in zfs-linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Request [BIONIC] ==

  The HWE kernel on bionic provides zfs 0.8.1 driver which includes an
  improved scrub however, the progress stats reported by the kernel are
  incompatible to the 0.7.x zfs driver.

  == Fix ==

  Use the new zfs 8.x pool_scan_stat_t extra fields to calculate
  the scan progress when using zfs 8.x kernel drivers. Add detection of the 
kernel module version and use an approximation to the zfs 0.8.0 progress and 
rate reporting for newer kernels.

  For 0.7.5 we can pass the larger 8.x port_scan_stat_t to 0.7.5
  zfs w/o problems and ignore these new fields and continue
  to use the 0.7.5 rate calculations. 

  == Test ==

  Install the HWE kernel on Bionic, create some large ZFS pools and
  populate with a lot of data.  Issue:

  sudo zpool scrub poolname
  and then look at the progress using

  sudo zpool status

  Without the fix, the progress stats are incorrect. With the fix the
  duration and rate stats as a fairly good approximation of the
  progress. Since the newer 0.8.x zfs does scanning now in two phases
  the older zfs tools will only report accurate stats for phase #2 of
  the scan to keep it roughly compatible with the 0.7.x zfs utils
  output.

  == Regression Potential ==

  This is a userspace reporting fix so the zpool status output is only
  affected by this fix when doing a scrub, so the impact of this fix is
  very small and limited.

  

  I ran a zpool scrub prior to upgrading my 18.04 to the latest HWE
  kernel (5.3.0-26-generic #28~18.04.1-Ubuntu) and it ran properly:

  eric@eric-8700K:~$ zpool status
    pool: storagepool1
   state: ONLINE
    scan: scrub repaired 1M in 4h21m with 0 errors on Fri Jan 17 07:01:24 2020
  config:

   NAME  STATE READ WRITE CKSUM
   storagepool1  ONLINE   0 0 0
     mirror-0ONLINE   0 0 0
   ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M3YFRVJ3  ONLINE   0 0 0
   ata-ST2000DM001-1CH164_Z1E285A4   ONLINE   0 0 0
     mirror-1ONLINE   0 0 0
   ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M1DSASHD  ONLINE   0 0 0
   ata-ST2000DM006-2DM164_Z4ZA3ENE   ONLINE   0 0 0

  I ran zpool scrub after upgrading the kernel and rebooting, and now it
  fails to work properly. It appeared to finish in about 5 minutes but
  did not, and says it is going slow:

  eric@eric-8700K:~$ sudo zpool status
    pool: storagepool1
   state: ONLINE
    scan: scrub in progress since Fri Jan 17 15:32:07 2020
   1.89T scanned out of 1.89T at 589M/s, (scan is slow, no estimated time)
   0B repaired, 100.00% done
  config:

   NAME  STATE READ WRITE CKSUM
   storagepool1  ONLINE   0 0 0
     mirror-0ONLINE   0 0 0
   ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M3YFRVJ3  ONLINE   0 0 0
   ata-ST2000DM001-1CH164_Z1E285A4   ONLINE   0 0 0
     mirror-1ONLINE   0 0 0
   ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M1DSASHD  ONLINE   0 0 0
   ata-ST2000DM006-2DM164_Z4ZA3ENE   ONLINE   0 0 0

  errors: No known data errors

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: zfsutils-linux 0.7.5-1ubuntu16.7
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 17 16:22:01 2020
  

[Kernel-packages] [Bug 1860182] Update Released

[Brian Murray]

The verification of the Stable Release Update for zfs-linux has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  zpool scrub malfunction after kernel upgrade

Status in zfs-linux package in Ubuntu:
  In Progress
Status in zfs-linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Request [BIONIC] ==

  The HWE kernel on bionic provides zfs 0.8.1 driver which includes an
  improved scrub however, the progress stats reported by the kernel are
  incompatible to the 0.7.x zfs driver.

  == Fix ==

  Use the new zfs 8.x pool_scan_stat_t extra fields to calculate
  the scan progress when using zfs 8.x kernel drivers. Add detection of the 
kernel module version and use an approximation to the zfs 0.8.0 progress and 
rate reporting for newer kernels.

  For 0.7.5 we can pass the larger 8.x port_scan_stat_t to 0.7.5
  zfs w/o problems and ignore these new fields and continue
  to use the 0.7.5 rate calculations. 

  == Test ==

  Install the HWE kernel on Bionic, create some large ZFS pools and
  populate with a lot of data.  Issue:

  sudo zpool scrub poolname
  and then look at the progress using

  sudo zpool status

  Without the fix, the progress stats are incorrect. With the fix the
  duration and rate stats as a fairly good approximation of the
  progress. Since the newer 0.8.x zfs does scanning now in two phases
  the older zfs tools will only report accurate stats for phase #2 of
  the scan to keep it roughly compatible with the 0.7.x zfs utils
  output.

  == Regression Potential ==

  This is a userspace reporting fix so the zpool status output is only
  affected by this fix when doing a scrub, so the impact of this fix is
  very small and limited.

  

  I ran a zpool scrub prior to upgrading my 18.04 to the latest HWE
  kernel (5.3.0-26-generic #28~18.04.1-Ubuntu) and it ran properly:

  eric@eric-8700K:~$ zpool status
    pool: storagepool1
   state: ONLINE
    scan: scrub repaired 1M in 4h21m with 0 errors on Fri Jan 17 07:01:24 2020
  config:

   NAME  STATE READ WRITE CKSUM
   storagepool1  ONLINE   0 0 0
     mirror-0ONLINE   0 0 0
   ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M3YFRVJ3  ONLINE   0 0 0
   ata-ST2000DM001-1CH164_Z1E285A4   ONLINE   0 0 0
     mirror-1ONLINE   0 0 0
   ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M1DSASHD  ONLINE   0 0 0
   ata-ST2000DM006-2DM164_Z4ZA3ENE   ONLINE   0 0 0

  I ran zpool scrub after upgrading the kernel and rebooting, and now it
  fails to work properly. It appeared to finish in about 5 minutes but
  did not, and says it is going slow:

  eric@eric-8700K:~$ sudo zpool status
    pool: storagepool1
   state: ONLINE
    scan: scrub in progress since Fri Jan 17 15:32:07 2020
   1.89T scanned out of 1.89T at 589M/s, (scan is slow, no estimated time)
   0B repaired, 100.00% done
  config:

   NAME  STATE READ WRITE CKSUM
   storagepool1  ONLINE   0 0 0
     mirror-0ONLINE   0 0 0
   ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M3YFRVJ3  ONLINE   0 0 0
   ata-ST2000DM001-1CH164_Z1E285A4   ONLINE   0 0 0
     mirror-1ONLINE   0 0 0
   ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M1DSASHD  ONLINE   0 0 0
   ata-ST2000DM006-2DM164_Z4ZA3ENE   ONLINE   0 0 0

  errors: No known data errors

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: zfsutils-linux 0.7.5-1ubuntu16.7
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 17 16:22:01 2020
  InstallationDate: Installed on 2018-03-07 (681 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: zfs-linux
  UpgradeStatus: Upgraded to bionic on 2018-08-02 (533 days ago)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

To manage 

[Kernel-packages] [Bug 1864041] Update Released

[Brian Murray]

The verification of the Stable Release Update for ec2-hibinit-agent has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  xen_netfront devices unresponsive after hibernation/resume

Status in ec2-hibinit-agent package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  New
Status in ec2-hibinit-agent source package in Bionic:
  Fix Released
Status in linux-aws source package in Bionic:
  New
Status in ec2-hibinit-agent source package in Eoan:
  Fix Committed
Status in linux-aws source package in Eoan:
  New
Status in ec2-hibinit-agent source package in Focal:
  Fix Released
Status in linux-aws source package in Focal:
  New

Bug description:
  [Impact]

  The xen_netfront device is sometimes unresponsive after a hibernate
  and resume event. This is limited to the c4, c5, m4, m5, r4, r5
  instance families, all of which are xen based, and support
  hibernation.

  When the issue occurrs, the instance is inaccessible without a full
  restart. Debugging by running a process which outputs regularly to the
  serial console shows that the instance is still running.

  [Test Case]

  1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel 
with on-demand hibernation support enabled.
  2) Start a long-running process which generates messages to the serial console
  3) Begin observing these messages on the console (using the AWS UI or CLI  to 
grab a screenshot).
  4) Suspend and resume the instance, continuing to refresh the console 
screenshot.
  5) The screenshot should continue to show updates even if ssh access is no 
longer working.

  [Regression Potential]

  The workaround in ec2-hibinit-agent is reloading the xen_netfront kernel 
module before restarting systemd-networkd. If the kernel module is removed (for 
example when hitting LP: #1615381) the module reloading fails and
  the instance can not restore network connections. This is expected to a be 
very rare situation and the module reload is the best workaround the Kernel 
Team found to mitigate the original issue.

  The workaround also adds a 2 second delay before reloading the modules
  to let things settle a bit after resuming. The 2 seconds is very short
  compared to the overall time needed resuming an instance.

  [Original Bug Text]

  The xen_netfront device is sometimes unresponsive after a hibernate
  and resume event. This is limited to the c4, c5, m4, m5, r4, r5
  instance families, all of which are xen based, and support
  hibernation.

  When the issue occurrs, the instance is inaccessible without a full
  restart. Debugging by running a process which outputs regularly to the
  serial console shows that the instance is still running.

  A workaround is to build the xen_netfront module separately and
  restart the module and networking during the resume handler. For
  example:

  modprobe -r xen_netfront
  modprobe xen_netfront
  systemctl restart systemd-networkd

  With this workaround in place, the unresponsive issue is no longer
  observed.

  To reproduce this problem:

  1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel 
with on-demand hibernation support enabled.
  2) Start a long-running process which generates messages to the serial console
  3) Begin observing these messages on the console (using the AWS UI or CLI  to 
grab a screenshot).
  4) Suspend and resume the instance, continuing to refresh the console 
screenshot.
  5) The screenshot should continue to show updates even if ssh access is no 
longer working.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-0edf3b95e26a682df
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2a
  Ec2InstanceType: m4.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Package: linux-aws 4.15.0.1058.59
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21
  Tags:  bionic ec2-images
  Uname: Linux 5.0.0-1025-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1864041/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to  

[Kernel-packages] [Bug 1864041] Re: xen_netfront devices unresponsive after hibernation/resume

[Launchpad Bug Tracker]

This bug was fixed in the package ec2-hibinit-agent -
1.0.0-0ubuntu4~18.04.4

---
ec2-hibinit-agent (1.0.0-0ubuntu4~18.04.4) bionic; urgency=medium

  * debian/hibinit-resume: Add extra steps around swapoff to avoid OOM errors.
Also work around xen-netfront not resuming properly.
Thanks to Francis Ginther for the initial patch (LP: #1863242, #1864041)

 -- Balint Reczey   Mon, 23 Mar 2020 13:03:38 +0100

** Changed in: ec2-hibinit-agent (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  xen_netfront devices unresponsive after hibernation/resume

Status in ec2-hibinit-agent package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  New
Status in ec2-hibinit-agent source package in Bionic:
  Fix Released
Status in linux-aws source package in Bionic:
  New
Status in ec2-hibinit-agent source package in Eoan:
  Fix Committed
Status in linux-aws source package in Eoan:
  New
Status in ec2-hibinit-agent source package in Focal:
  Fix Released
Status in linux-aws source package in Focal:
  New

Bug description:
  [Impact]

  The xen_netfront device is sometimes unresponsive after a hibernate
  and resume event. This is limited to the c4, c5, m4, m5, r4, r5
  instance families, all of which are xen based, and support
  hibernation.

  When the issue occurrs, the instance is inaccessible without a full
  restart. Debugging by running a process which outputs regularly to the
  serial console shows that the instance is still running.

  [Test Case]

  1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel 
with on-demand hibernation support enabled.
  2) Start a long-running process which generates messages to the serial console
  3) Begin observing these messages on the console (using the AWS UI or CLI  to 
grab a screenshot).
  4) Suspend and resume the instance, continuing to refresh the console 
screenshot.
  5) The screenshot should continue to show updates even if ssh access is no 
longer working.

  [Regression Potential]

  The workaround in ec2-hibinit-agent is reloading the xen_netfront kernel 
module before restarting systemd-networkd. If the kernel module is removed (for 
example when hitting LP: #1615381) the module reloading fails and
  the instance can not restore network connections. This is expected to a be 
very rare situation and the module reload is the best workaround the Kernel 
Team found to mitigate the original issue.

  The workaround also adds a 2 second delay before reloading the modules
  to let things settle a bit after resuming. The 2 seconds is very short
  compared to the overall time needed resuming an instance.

  [Original Bug Text]

  The xen_netfront device is sometimes unresponsive after a hibernate
  and resume event. This is limited to the c4, c5, m4, m5, r4, r5
  instance families, all of which are xen based, and support
  hibernation.

  When the issue occurrs, the instance is inaccessible without a full
  restart. Debugging by running a process which outputs regularly to the
  serial console shows that the instance is still running.

  A workaround is to build the xen_netfront module separately and
  restart the module and networking during the resume handler. For
  example:

  modprobe -r xen_netfront
  modprobe xen_netfront
  systemctl restart systemd-networkd

  With this workaround in place, the unresponsive issue is no longer
  observed.

  To reproduce this problem:

  1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel 
with on-demand hibernation support enabled.
  2) Start a long-running process which generates messages to the serial console
  3) Begin observing these messages on the console (using the AWS UI or CLI  to 
grab a screenshot).
  4) Suspend and resume the instance, continuing to refresh the console 
screenshot.
  5) The screenshot should continue to show updates even if ssh access is no 
longer working.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-0edf3b95e26a682df
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2a
  Ec2InstanceType: m4.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Package: linux-aws 4.15.0.1058.59
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21
  Tags:  bionic ec2-images
  Uname: Linux 5.0.0-1025-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1864041/+subscriptions

-- 
Mailing list: 

[Kernel-packages] [Bug 1870837] Re: hcitool lescan says 'Set scan parameters failed: Input/output error'

[mm]

Installed blueman for testing purpose (wasn't installed before): it is allowed 
to perform these commands:
@ RAW Open: blueman-manager (privileged) version 2.22   
   {0x0004} 
20:43:17.578682
@ RAW Close: blueman-manager
   {0x0004} 
20:43:17.578707
@ MGMT Command: Start Discovery (0x0023) plen 1 
{0x0001} [hci0] 
20:43:17.751082
Address type: 0x07
  BR/EDR
  LE Public
  LE Random
< HCI Command: LE Set Random Address (0x08|0x0005) plen 6   
#495 [hci0] 
20:43:17.751177
Address: 16:68:B8:85:83:60 (Non-Resolvable)
> HCI Event: Command Complete (0x0e) plen 4 
> #496 [hci0] 
> 20:43:17.866069
  LE Set Random Address (0x08|0x0005) ncmd 1
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8 
#497 [hci0] 
20:43:17.866147
Own address type: Random (0x01)
Filter policy: Accept all advertisement (0x00)
PHYs: 0x01
Entry 0: LE 1M
  Type: Active (0x01)
  Interval: 22.500 msec (0x0024)
  Window: 11.250 msec (0x0012)
> HCI Event: Command Complete (0x0e) plen 4 
> #498 [hci0] 
> 20:43:17.867046
  LE Set Extended Scan Parameters (0x08|0x0041) ncmd 1
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6 
#499 [hci0] 
20:43:17.867156
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
...

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

Title:
  hcitool lescan says 'Set scan parameters failed: Input/output error'

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Hi,

  after some testing with Ubuntu 20.04 beta I couldn't get hcitool
  lescan working. I get the following error:

  hcitool lescan
  Set scan parameters failed: Input/output error

  Bluetooth hardware: 
  hci0:   Type: Primary  Bus: USB
  BD Address: 04:EA:56:21:xx:xx  ACL MTU: 1021:4  SCO MTU: 96:6
  UP RUNNING
  RX bytes:1605 acl:0 sco:0 events:123 errors:0
  TX bytes:5801 acl:0 sco:0 commands:123 errors:0
  Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
  Link policy: RSWITCH SNIFF
  Link mode: SLAVE ACCEPT
  Name: 'xx'
  Class: 0x200104
  Service Classes: Audio
  Device Class: Computer, Desktop workstation
  HCI Version: 5.1 (0xa)  Revision: 0x100
  LMP Version: 5.1 (0xa)  Subversion: 0x100
  Manufacturer: Intel Corp. (2)

  It is not hardware related, since I get the same error with a USB
  bluetooth dongle:

  hcitool -i hci1 lescan
  Set scan parameters failed: Input/output error

  hcitool scan is working fine on both devices; bluetoothctl is also working 
and able to find ble devices.
  I would normally prefer bluetoothctl, but I got a software which is based on 
hcitool.

  dmesg shows this errors:
  [  138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already 
present!
  [  138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already 
present!

  Bluez version:
  bluez 5.53-0ubuntu2 amd64

  System:
  Distributor ID: Ubuntu
  Description:Ubuntu Focal Fossa (development branch)
  Release:20.04
  Codename:   focal
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-01 (4 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 
(20200331)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0463: MGE UPS Systems UPS
   Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 
(ZW090) - UZB
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel(R) Client Systems NUC8i3BEH
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/vgcs2ubct-root ro
  

[Kernel-packages] [Bug 1871466] Re: Disco update: upstream stable patchset 2020-04-07

[Kamal Mostafa]

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    upstream stable patchset 2020-04-07
  
-upstream stable patchset 2020-04-07
-from git://git.kernel.org/
+ Ported from the following upstream stable releases:
+ v4.19.114, v5.4.29,
+v5.4.30
+ 
+    from git://git.kernel.org/
+ 
+ mmc: core: Allow host controllers to require R1B for CMD6
+ mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for erase/trim/discard
+ mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for eMMC sleep command
+ mmc: sdhci-omap: Fix busy detection by enabling MMC_CAP_NEED_RSP_BUSY
+ mmc: sdhci-tegra: Fix busy detection by enabling MMC_CAP_NEED_RSP_BUSY
+ geneve: move debug check after netdev unregister
+ hsr: fix general protection fault in hsr_addr_is_self()
+ macsec: restrict to ethernet devices
+ mlxsw: spectrum_mr: Fix list iteration in error path
+ net: cbs: Fix software cbs to consider packet sending time
+ net: dsa: Fix duplicate frames flooded by learning
+ net: mvneta: Fix the case where the last poll did not process all rx
+ net/packet: tpacket_rcv: avoid a producer race condition
+ net: qmi_wwan: add support for ASKEY WWHC050
+ net_sched: cls_route: remove the right filter from hashtable
+ net_sched: keep alloc_hash updated after hash allocation
+ net: stmmac: dwmac-rk: fix error path in rk_gmac_probe
+ NFC: fdp: Fix a signedness bug in fdp_nci_send_patch()
+ slcan: not call free_netdev before rtnl_unlock in slcan_open
+ bnxt_en: fix memory leaks in bnxt_dcbnl_ieee_getets()
+ bnxt_en: Reset rings if ring reservation fails during open()
+ net: ip_gre: Separate ERSPAN newlink / changelink callbacks
+ net: ip_gre: Accept IFLA_INFO_DATA-less configuration
+ net: dsa: mt7530: Change the LINK bit to reflect the link status
+ net: phy: mdio-mux-bcm-iproc: check clk_prepare_enable() return value
+ r8169: re-enable MSI on RTL8168c
+ tcp: repair: fix TCP_QUEUE_SEQ implementation
+ vxlan: check return value of gro_cells_init()
+ hsr: use rcu_read_lock() in hsr_get_node_{list/status}()
+ hsr: add restart routine into hsr_get_node_list()
+ hsr: set .netnsok flag
+ cgroup-v1: cgroup_pidlist_next should update position index
+ nfs: add minor version to nfs_server_key for fscache
+ cpupower: avoid multiple definition with gcc -fno-common
+ drivers/of/of_mdio.c:fix of_mdiobus_register()
+ cgroup1: don't call release_agent when it is ""
+ UBUNTU: [Config] updateconfigs for DPAA_ERRATUM_A050385
+ dt-bindings: net: FMan erratum A050385
+ arm64: dts: ls1043a: FMan erratum A050385
+ fsl/fman: detect FMan erratum A050385
+ s390/qeth: handle error when backing RX buffer
+ scsi: ipr: Fix softlockup when rescanning devices in petitboot
+ mac80211: Do not send mesh HWMP PREQ if HWMP is disabled
+ dpaa_eth: Remove unnecessary boolean expression in dpaa_get_headroom
+ sxgbe: Fix off by one in samsung driver strncpy size arg
+ ftrace/x86: Anotate text_mutex split between 
ftrace_arch_code_modify_post_process() and ftrace_arch_code_modify_prepare()
+ i2c: hix5hd2: add missed clk_disable_unprepare in remove
+ Input: raydium_i2c_ts - fix error codes in raydium_i2c_boot_trigger()
+ Input: synaptics - enable RMI on HP Envy 13-ad105ng
+ Input: avoid BIT() macro usage in the serio.h UAPI header
+ ceph: check POOL_FLAG_FULL/NEARFULL in addition to OSDMAP_FULL/NEARFULL
+ ARM: dts: dra7: Add bus_dma_limit for L3 bus
+ ARM: dts: omap5: Add bus_dma_limit for L3 bus
+ perf probe: Do not depend on dwfl_module_addrsym()
+ tools: Let O= makes handle a relative path with -C option
+ scripts/dtc: Remove redundant YYLOC global declaration
+ scsi: sd: Fix optimal I/O size for devices that change reported values
+ nl80211: fix NL80211_ATTR_CHANNEL_WIDTH attribute type
+ mac80211: mark station unauthorized before key removal
+ gpiolib: acpi: Correct comment for HP x2 10 honor_wakeup quirk
+ gpiolib: acpi: Rework honor_wakeup option into an ignore_wake option
+ gpiolib: acpi: Add quirk to ignore EC wakeups on HP x2 10 BYT + AXP288 model
+ RDMA/core: Ensure security pkey modify is not lost
+ genirq: 

[Kernel-packages] [Bug 1870837] Re: hcitool lescan says 'Set scan parameters failed: Input/output error'

[mm]

After some more investigation I found out that the software I am using
is NOT using hcitool. It really seems to be another problem since the
custom software and the hcitool lescan command are throwing the same
error observed with btmon:

@ RAW Close: hcitool
   {0x0004} 
20:16:29.633716
@ RAW Open: hcitool (privileged) version 2.22   
{0x0004} [hci0] 
20:16:29.633742
< HCI Command: LE Set Scan Parameters (0x08|0x000b) plen 7  
 #35 [hci0] 
20:16:29.633780
Type: Active (0x01)
Interval: 10.000 msec (0x0010)
Window: 10.000 msec (0x0010)
Own address type: Public (0x00)
Filter policy: Accept all advertisement (0x00)
> HCI Event: Command Complete (0x0e) plen 4 
>  #36 [hci0] 
> 20:16:29.750680
  LE Set Scan Parameters (0x08|0x000b) ncmd 1
Status: Command Disallowed (0x0c)
@ RAW Close: hcitool

Software (phython):
@ RAW Open: python (privileged) version 2.22
{0x0003} [hci0] 
20:14:38.006713
> HCI Event: Command Complete (0x0e) plen 4 
>  #28 [hci0] 
> 20:14:38.119126
  LE Set Scan Enable (0x08|0x000c) ncmd 1
Status: Command Disallowed (0x0c)
< HCI Command: LE Set Scan Parameters (0x08|0x000b) plen 7  
 #29 [hci0] 
20:14:38.119219
Type: Passive (0x00)
Interval: 10.000 msec (0x0010)
Window: 10.000 msec (0x0010)
Own address type: Public (0x00)
Filter policy: Accept all advertisement (0x00)
> HCI Event: Command Complete (0x0e) plen 4 
>  #30 [hci0] 
> 20:14:38.119989
  LE Set Scan Parameters (0x08|0x000b) ncmd 1
Status: Command Disallowed (0x0c)
< HCI Command: LE Set Scan Parameters (0x08|0x000b) plen 7  
 #31 [hci0] 
20:14:38.120063
Type: Passive (0x00)
Interval: 10.000 msec (0x0010)
Window: 10.000 msec (0x0010)
Own address type: Public (0x00)
Filter policy: Accept all advertisement (0x00)
> HCI Event: Command Complete (0x0e) plen 4 
>  #32 [hci0] 
> 20:14:38.120946
  LE Set Scan Parameters (0x08|0x000b) ncmd 1
Status: Command Disallowed (0x0c)
< HCI Command: LE Set Scan Enable (0x08|0x000c) plen 2  
 #33 [hci0] 
20:14:38.120988
Scanning: Enabled (0x01)
Filter duplicates: Disabled (0x00)
> HCI Event: Command Complete (0x0e) plen 4 
>  #34 [hci0] 
> 20:14:38.121945
  LE Set Scan Enable (0x08|0x000c) ncmd 1
Status: Command Disallowed (0x0c)

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

Title:
  hcitool lescan says 'Set scan parameters failed: Input/output error'

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Hi,

  after some testing with Ubuntu 20.04 beta I couldn't get hcitool
  lescan working. I get the following error:

  hcitool lescan
  Set scan parameters failed: Input/output error

  Bluetooth hardware: 
  hci0:   Type: Primary  Bus: USB
  BD Address: 04:EA:56:21:xx:xx  ACL MTU: 1021:4  SCO MTU: 96:6
  UP RUNNING
  RX bytes:1605 acl:0 sco:0 events:123 errors:0
  TX bytes:5801 acl:0 sco:0 commands:123 errors:0
  Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
  Link policy: RSWITCH SNIFF
  Link mode: SLAVE ACCEPT
  Name: 'xx'
  Class: 0x200104
  Service Classes: Audio
  Device Class: Computer, Desktop workstation
  HCI Version: 5.1 (0xa)  Revision: 0x100
  LMP Version: 5.1 (0xa)  Subversion: 0x100
  Manufacturer: Intel Corp. (2)

  It is not hardware related, since I get the same error with a USB
  bluetooth dongle:

  hcitool -i hci1 lescan
  Set scan parameters failed: Input/output error

  hcitool scan is working fine on both devices; bluetoothctl is also working 
and able to find ble devices.
  I would normally prefer 

[Kernel-packages] [Bug 1871466] [NEW] Disco update: upstream stable patchset 2020-04-07

[Kamal Mostafa]

Public bug reported:


SRU Justification

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

   upstream stable patchset 2020-04-07
   from git://git.kernel.org/

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

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

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

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

Title:
  Disco update: upstream stable patchset 2020-04-07

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  In Progress

Bug description:
  
  SRU Justification

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

 upstream stable patchset 2020-04-07
 from git://git.kernel.org/

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

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

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

[Wladimir Mutel]

apport information

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

Title:
  iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My home server/router/access point runs under Ubuntu 18.04.4 with all updates 
and has 2 wifi adapters operated by hostapd
  one is USB AR9271 (0cf3:9271, driver ath9k_htc), another is PCIe Intel AC 
9260 (8086:2526, driver iwlwifi).
  with kernel 4.15.0-88 it worked quite stable, with reboots required mostly 
after kernel upgrades (much less frequent reboots due to panics)
  with kernel 4.15.0-91 and -96 it started rebooting by itself by panic when a 
lot of activity happening via Intel 9260.
  In /etc/sysctl* I have kernel.panic=10 , kernel.softlockup_panic=1 and 
kernel.panic_on_oops=1 overrides of default values.
  In dmesg logs preceding the reboot, I see multiple warnings with stacks 
inside iwl_mvm functions which I could provide by apport. Also, multiple 
messages like "Command LQ_CMD: a command is already active!" or "Error sending 
LQ_CMD: time out after 2000ms"
  Unfortunately I run this box headless and I don't have another wired Ethernet 
host to capture its panics by netconsole
  The rest of hardware is pretty standard. Asus B85M-G mobo, Core i3-4130T CPU, 
nothing overly special.
  More details I would provide in your further requests but the current kernel 
behavior is very annoying.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: #RESUME=UUID=f7bcdeb1-6c61-4012-81c4-a43a492ffb6e
  InstallationDate: Installed on 2009-11-01 (3810 days ago)
  InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-96-generic 
root=/dev/mapper/vg00-root64 ro rootflags=commit=3600 rootflags=commit=3600 
loop.max_part=63
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-96-generic N/A
   linux-backports-modules-4.15.0-96-generic  N/A
   linux-firmware 1.173.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-96-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2010-10-11 (3466 days ago)
  UserGroups: adm admin audio cdrom dialout dip disk dos fuse jabber kvm 
libvirt libvirtd lpadmin plugdev proxy pulse pulse-access sambashare src
  _MarkForUpload: True
  dmi.bios.date: 07/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-G
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/22/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-G:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  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/1871430/+subscriptions

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

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

[Wladimir Mutel]

apport information

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

Title:
  iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My home server/router/access point runs under Ubuntu 18.04.4 with all updates 
and has 2 wifi adapters operated by hostapd
  one is USB AR9271 (0cf3:9271, driver ath9k_htc), another is PCIe Intel AC 
9260 (8086:2526, driver iwlwifi).
  with kernel 4.15.0-88 it worked quite stable, with reboots required mostly 
after kernel upgrades (much less frequent reboots due to panics)
  with kernel 4.15.0-91 and -96 it started rebooting by itself by panic when a 
lot of activity happening via Intel 9260.
  In /etc/sysctl* I have kernel.panic=10 , kernel.softlockup_panic=1 and 
kernel.panic_on_oops=1 overrides of default values.
  In dmesg logs preceding the reboot, I see multiple warnings with stacks 
inside iwl_mvm functions which I could provide by apport. Also, multiple 
messages like "Command LQ_CMD: a command is already active!" or "Error sending 
LQ_CMD: time out after 2000ms"
  Unfortunately I run this box headless and I don't have another wired Ethernet 
host to capture its panics by netconsole
  The rest of hardware is pretty standard. Asus B85M-G mobo, Core i3-4130T CPU, 
nothing overly special.
  More details I would provide in your further requests but the current kernel 
behavior is very annoying.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: #RESUME=UUID=f7bcdeb1-6c61-4012-81c4-a43a492ffb6e
  InstallationDate: Installed on 2009-11-01 (3810 days ago)
  InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-96-generic 
root=/dev/mapper/vg00-root64 ro rootflags=commit=3600 rootflags=commit=3600 
loop.max_part=63
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-96-generic N/A
   linux-backports-modules-4.15.0-96-generic  N/A
   linux-firmware 1.173.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-96-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2010-10-11 (3466 days ago)
  UserGroups: adm admin audio cdrom dialout dip disk dos fuse jabber kvm 
libvirt libvirtd lpadmin plugdev proxy pulse pulse-access sambashare src
  _MarkForUpload: True
  dmi.bios.date: 07/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-G
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/22/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-G:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  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/1871430/+subscriptions

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

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

[Wladimir Mutel]

apport information

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

Title:
  iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My home server/router/access point runs under Ubuntu 18.04.4 with all updates 
and has 2 wifi adapters operated by hostapd
  one is USB AR9271 (0cf3:9271, driver ath9k_htc), another is PCIe Intel AC 
9260 (8086:2526, driver iwlwifi).
  with kernel 4.15.0-88 it worked quite stable, with reboots required mostly 
after kernel upgrades (much less frequent reboots due to panics)
  with kernel 4.15.0-91 and -96 it started rebooting by itself by panic when a 
lot of activity happening via Intel 9260.
  In /etc/sysctl* I have kernel.panic=10 , kernel.softlockup_panic=1 and 
kernel.panic_on_oops=1 overrides of default values.
  In dmesg logs preceding the reboot, I see multiple warnings with stacks 
inside iwl_mvm functions which I could provide by apport. Also, multiple 
messages like "Command LQ_CMD: a command is already active!" or "Error sending 
LQ_CMD: time out after 2000ms"
  Unfortunately I run this box headless and I don't have another wired Ethernet 
host to capture its panics by netconsole
  The rest of hardware is pretty standard. Asus B85M-G mobo, Core i3-4130T CPU, 
nothing overly special.
  More details I would provide in your further requests but the current kernel 
behavior is very annoying.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: #RESUME=UUID=f7bcdeb1-6c61-4012-81c4-a43a492ffb6e
  InstallationDate: Installed on 2009-11-01 (3810 days ago)
  InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-96-generic 
root=/dev/mapper/vg00-root64 ro rootflags=commit=3600 rootflags=commit=3600 
loop.max_part=63
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-96-generic N/A
   linux-backports-modules-4.15.0-96-generic  N/A
   linux-firmware 1.173.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-96-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2010-10-11 (3466 days ago)
  UserGroups: adm admin audio cdrom dialout dip disk dos fuse jabber kvm 
libvirt libvirtd lpadmin plugdev proxy pulse pulse-access sambashare src
  _MarkForUpload: True
  dmi.bios.date: 07/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-G
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/22/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-G:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  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/1871430/+subscriptions

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

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

[Wladimir Mutel]

apport information

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

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

Title:
  iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My home server/router/access point runs under Ubuntu 18.04.4 with all updates 
and has 2 wifi adapters operated by hostapd
  one is USB AR9271 (0cf3:9271, driver ath9k_htc), another is PCIe Intel AC 
9260 (8086:2526, driver iwlwifi).
  with kernel 4.15.0-88 it worked quite stable, with reboots required mostly 
after kernel upgrades (much less frequent reboots due to panics)
  with kernel 4.15.0-91 and -96 it started rebooting by itself by panic when a 
lot of activity happening via Intel 9260.
  In /etc/sysctl* I have kernel.panic=10 , kernel.softlockup_panic=1 and 
kernel.panic_on_oops=1 overrides of default values.
  In dmesg logs preceding the reboot, I see multiple warnings with stacks 
inside iwl_mvm functions which I could provide by apport. Also, multiple 
messages like "Command LQ_CMD: a command is already active!" or "Error sending 
LQ_CMD: time out after 2000ms"
  Unfortunately I run this box headless and I don't have another wired Ethernet 
host to capture its panics by netconsole
  The rest of hardware is pretty standard. Asus B85M-G mobo, Core i3-4130T CPU, 
nothing overly special.
  More details I would provide in your further requests but the current kernel 
behavior is very annoying.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: #RESUME=UUID=f7bcdeb1-6c61-4012-81c4-a43a492ffb6e
  InstallationDate: Installed on 2009-11-01 (3810 days ago)
  InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-96-generic 
root=/dev/mapper/vg00-root64 ro rootflags=commit=3600 rootflags=commit=3600 
loop.max_part=63
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-96-generic N/A
   linux-backports-modules-4.15.0-96-generic  N/A
   linux-firmware 1.173.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-96-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2010-10-11 (3466 days ago)
  UserGroups: adm admin audio cdrom dialout dip disk dos fuse jabber kvm 
libvirt libvirtd lpadmin plugdev proxy pulse pulse-access sambashare src
  _MarkForUpload: True
  dmi.bios.date: 07/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-G
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/22/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-G:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  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/1871430/+subscriptions

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

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

[Wladimir Mutel]

apport information

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

Title:
  iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My home server/router/access point runs under Ubuntu 18.04.4 with all updates 
and has 2 wifi adapters operated by hostapd
  one is USB AR9271 (0cf3:9271, driver ath9k_htc), another is PCIe Intel AC 
9260 (8086:2526, driver iwlwifi).
  with kernel 4.15.0-88 it worked quite stable, with reboots required mostly 
after kernel upgrades (much less frequent reboots due to panics)
  with kernel 4.15.0-91 and -96 it started rebooting by itself by panic when a 
lot of activity happening via Intel 9260.
  In /etc/sysctl* I have kernel.panic=10 , kernel.softlockup_panic=1 and 
kernel.panic_on_oops=1 overrides of default values.
  In dmesg logs preceding the reboot, I see multiple warnings with stacks 
inside iwl_mvm functions which I could provide by apport. Also, multiple 
messages like "Command LQ_CMD: a command is already active!" or "Error sending 
LQ_CMD: time out after 2000ms"
  Unfortunately I run this box headless and I don't have another wired Ethernet 
host to capture its panics by netconsole
  The rest of hardware is pretty standard. Asus B85M-G mobo, Core i3-4130T CPU, 
nothing overly special.
  More details I would provide in your further requests but the current kernel 
behavior is very annoying.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: #RESUME=UUID=f7bcdeb1-6c61-4012-81c4-a43a492ffb6e
  InstallationDate: Installed on 2009-11-01 (3810 days ago)
  InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-96-generic 
root=/dev/mapper/vg00-root64 ro rootflags=commit=3600 rootflags=commit=3600 
loop.max_part=63
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-96-generic N/A
   linux-backports-modules-4.15.0-96-generic  N/A
   linux-firmware 1.173.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-96-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2010-10-11 (3466 days ago)
  UserGroups: adm admin audio cdrom dialout dip disk dos fuse jabber kvm 
libvirt libvirtd lpadmin plugdev proxy pulse pulse-access sambashare src
  _MarkForUpload: True
  dmi.bios.date: 07/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-G
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/22/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-G:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  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/1871430/+subscriptions

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

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

[Wladimir Mutel]

apport information

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

Title:
  iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My home server/router/access point runs under Ubuntu 18.04.4 with all updates 
and has 2 wifi adapters operated by hostapd
  one is USB AR9271 (0cf3:9271, driver ath9k_htc), another is PCIe Intel AC 
9260 (8086:2526, driver iwlwifi).
  with kernel 4.15.0-88 it worked quite stable, with reboots required mostly 
after kernel upgrades (much less frequent reboots due to panics)
  with kernel 4.15.0-91 and -96 it started rebooting by itself by panic when a 
lot of activity happening via Intel 9260.
  In /etc/sysctl* I have kernel.panic=10 , kernel.softlockup_panic=1 and 
kernel.panic_on_oops=1 overrides of default values.
  In dmesg logs preceding the reboot, I see multiple warnings with stacks 
inside iwl_mvm functions which I could provide by apport. Also, multiple 
messages like "Command LQ_CMD: a command is already active!" or "Error sending 
LQ_CMD: time out after 2000ms"
  Unfortunately I run this box headless and I don't have another wired Ethernet 
host to capture its panics by netconsole
  The rest of hardware is pretty standard. Asus B85M-G mobo, Core i3-4130T CPU, 
nothing overly special.
  More details I would provide in your further requests but the current kernel 
behavior is very annoying.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: #RESUME=UUID=f7bcdeb1-6c61-4012-81c4-a43a492ffb6e
  InstallationDate: Installed on 2009-11-01 (3810 days ago)
  InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-96-generic 
root=/dev/mapper/vg00-root64 ro rootflags=commit=3600 rootflags=commit=3600 
loop.max_part=63
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-96-generic N/A
   linux-backports-modules-4.15.0-96-generic  N/A
   linux-firmware 1.173.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-96-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2010-10-11 (3466 days ago)
  UserGroups: adm admin audio cdrom dialout dip disk dos fuse jabber kvm 
libvirt libvirtd lpadmin plugdev proxy pulse pulse-access sambashare src
  _MarkForUpload: True
  dmi.bios.date: 07/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-G
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/22/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-G:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  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/1871430/+subscriptions

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

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

[Wladimir Mutel]

apport information

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

Title:
  iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My home server/router/access point runs under Ubuntu 18.04.4 with all updates 
and has 2 wifi adapters operated by hostapd
  one is USB AR9271 (0cf3:9271, driver ath9k_htc), another is PCIe Intel AC 
9260 (8086:2526, driver iwlwifi).
  with kernel 4.15.0-88 it worked quite stable, with reboots required mostly 
after kernel upgrades (much less frequent reboots due to panics)
  with kernel 4.15.0-91 and -96 it started rebooting by itself by panic when a 
lot of activity happening via Intel 9260.
  In /etc/sysctl* I have kernel.panic=10 , kernel.softlockup_panic=1 and 
kernel.panic_on_oops=1 overrides of default values.
  In dmesg logs preceding the reboot, I see multiple warnings with stacks 
inside iwl_mvm functions which I could provide by apport. Also, multiple 
messages like "Command LQ_CMD: a command is already active!" or "Error sending 
LQ_CMD: time out after 2000ms"
  Unfortunately I run this box headless and I don't have another wired Ethernet 
host to capture its panics by netconsole
  The rest of hardware is pretty standard. Asus B85M-G mobo, Core i3-4130T CPU, 
nothing overly special.
  More details I would provide in your further requests but the current kernel 
behavior is very annoying.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: #RESUME=UUID=f7bcdeb1-6c61-4012-81c4-a43a492ffb6e
  InstallationDate: Installed on 2009-11-01 (3810 days ago)
  InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-96-generic 
root=/dev/mapper/vg00-root64 ro rootflags=commit=3600 rootflags=commit=3600 
loop.max_part=63
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-96-generic N/A
   linux-backports-modules-4.15.0-96-generic  N/A
   linux-firmware 1.173.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-96-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2010-10-11 (3466 days ago)
  UserGroups: adm admin audio cdrom dialout dip disk dos fuse jabber kvm 
libvirt libvirtd lpadmin plugdev proxy pulse pulse-access sambashare src
  _MarkForUpload: True
  dmi.bios.date: 07/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-G
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/22/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-G:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  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/1871430/+subscriptions

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

[Kernel-packages] [Bug 1871430] Re: iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91

[Wladimir Mutel]

apport information

** Description changed:

  My home server/router/access point runs under Ubuntu 18.04.4 with all updates 
and has 2 wifi adapters operated by hostapd
  one is USB AR9271 (0cf3:9271, driver ath9k_htc), another is PCIe Intel AC 
9260 (8086:2526, driver iwlwifi).
  with kernel 4.15.0-88 it worked quite stable, with reboots required mostly 
after kernel upgrades (much less frequent reboots due to panics)
  with kernel 4.15.0-91 and -96 it started rebooting by itself by panic when a 
lot of activity happening via Intel 9260.
  In /etc/sysctl* I have kernel.panic=10 , kernel.softlockup_panic=1 and 
kernel.panic_on_oops=1 overrides of default values.
  In dmesg logs preceding the reboot, I see multiple warnings with stacks 
inside iwl_mvm functions which I could provide by apport. Also, multiple 
messages like "Command LQ_CMD: a command is already active!" or "Error sending 
LQ_CMD: time out after 2000ms"
  Unfortunately I run this box headless and I don't have another wired Ethernet 
host to capture its panics by netconsole
  The rest of hardware is pretty standard. Asus B85M-G mobo, Core i3-4130T CPU, 
nothing overly special.
  More details I would provide in your further requests but the current kernel 
behavior is very annoying.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.14
+ Architecture: amd64
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
+ DistroRelease: Ubuntu 18.04
+ HibernationDevice: #RESUME=UUID=f7bcdeb1-6c61-4012-81c4-a43a492ffb6e
+ InstallationDate: Installed on 2009-11-01 (3810 days ago)
+ InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
+ MachineType: ASUS All Series
+ Package: linux (not installed)
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-96-generic 
root=/dev/mapper/vg00-root64 ro rootflags=commit=3600 rootflags=commit=3600 
loop.max_part=63
+ ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-96-generic N/A
+  linux-backports-modules-4.15.0-96-generic  N/A
+  linux-firmware 1.173.17
+ RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
+ Tags:  bionic
+ Uname: Linux 4.15.0-96-generic x86_64
+ UpgradeStatus: Upgraded to bionic on 2010-10-11 (3466 days ago)
+ UserGroups: adm admin audio cdrom dialout dip disk dos fuse jabber kvm 
libvirt libvirtd lpadmin plugdev proxy pulse pulse-access sambashare src
+ _MarkForUpload: True
+ dmi.bios.date: 07/22/2015
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 2501
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: B85M-G
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: Rev X.0x
+ dmi.chassis.asset.tag: Asset-1234567890
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Chassis Manufacture
+ dmi.chassis.version: Chassis Version
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/22/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-G:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
+ dmi.product.family: ASUS MB
+ dmi.product.name: All Series
+ dmi.product.version: System Version
+ dmi.sys.vendor: ASUS

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

Title:
  iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My home server/router/access point runs under Ubuntu 18.04.4 with all updates 
and has 2 wifi adapters operated by hostapd
  one is USB AR9271 (0cf3:9271, driver ath9k_htc), another is PCIe Intel AC 
9260 (8086:2526, driver iwlwifi).
  with kernel 4.15.0-88 it worked quite stable, with reboots required mostly 
after kernel upgrades (much less frequent reboots due to panics)
  with kernel 4.15.0-91 and -96 it started rebooting by itself by panic when a 
lot of activity happening via Intel 9260.
  In /etc/sysctl* I have kernel.panic=10 , kernel.softlockup_panic=1 and 
kernel.panic_on_oops=1 overrides of default values.
  In dmesg logs preceding the reboot, I see multiple warnings with stacks 
inside iwl_mvm functions which I could provide by apport. Also, multiple 
messages like "Command LQ_CMD: a command is already active!" or "Error sending 
LQ_CMD: time out after 2000ms"
  

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

[Wladimir Mutel]

apport information

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

Title:
  iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My home server/router/access point runs under Ubuntu 18.04.4 with all updates 
and has 2 wifi adapters operated by hostapd
  one is USB AR9271 (0cf3:9271, driver ath9k_htc), another is PCIe Intel AC 
9260 (8086:2526, driver iwlwifi).
  with kernel 4.15.0-88 it worked quite stable, with reboots required mostly 
after kernel upgrades (much less frequent reboots due to panics)
  with kernel 4.15.0-91 and -96 it started rebooting by itself by panic when a 
lot of activity happening via Intel 9260.
  In /etc/sysctl* I have kernel.panic=10 , kernel.softlockup_panic=1 and 
kernel.panic_on_oops=1 overrides of default values.
  In dmesg logs preceding the reboot, I see multiple warnings with stacks 
inside iwl_mvm functions which I could provide by apport. Also, multiple 
messages like "Command LQ_CMD: a command is already active!" or "Error sending 
LQ_CMD: time out after 2000ms"
  Unfortunately I run this box headless and I don't have another wired Ethernet 
host to capture its panics by netconsole
  The rest of hardware is pretty standard. Asus B85M-G mobo, Core i3-4130T CPU, 
nothing overly special.
  More details I would provide in your further requests but the current kernel 
behavior is very annoying.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: #RESUME=UUID=f7bcdeb1-6c61-4012-81c4-a43a492ffb6e
  InstallationDate: Installed on 2009-11-01 (3810 days ago)
  InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-96-generic 
root=/dev/mapper/vg00-root64 ro rootflags=commit=3600 rootflags=commit=3600 
loop.max_part=63
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-96-generic N/A
   linux-backports-modules-4.15.0-96-generic  N/A
   linux-firmware 1.173.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-96-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2010-10-11 (3466 days ago)
  UserGroups: adm admin audio cdrom dialout dip disk dos fuse jabber kvm 
libvirt libvirtd lpadmin plugdev proxy pulse pulse-access sambashare src
  _MarkForUpload: True
  dmi.bios.date: 07/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-G
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/22/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-G:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  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/1871430/+subscriptions

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

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

[Wladimir Mutel]

apport information

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

Title:
  iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My home server/router/access point runs under Ubuntu 18.04.4 with all updates 
and has 2 wifi adapters operated by hostapd
  one is USB AR9271 (0cf3:9271, driver ath9k_htc), another is PCIe Intel AC 
9260 (8086:2526, driver iwlwifi).
  with kernel 4.15.0-88 it worked quite stable, with reboots required mostly 
after kernel upgrades (much less frequent reboots due to panics)
  with kernel 4.15.0-91 and -96 it started rebooting by itself by panic when a 
lot of activity happening via Intel 9260.
  In /etc/sysctl* I have kernel.panic=10 , kernel.softlockup_panic=1 and 
kernel.panic_on_oops=1 overrides of default values.
  In dmesg logs preceding the reboot, I see multiple warnings with stacks 
inside iwl_mvm functions which I could provide by apport. Also, multiple 
messages like "Command LQ_CMD: a command is already active!" or "Error sending 
LQ_CMD: time out after 2000ms"
  Unfortunately I run this box headless and I don't have another wired Ethernet 
host to capture its panics by netconsole
  The rest of hardware is pretty standard. Asus B85M-G mobo, Core i3-4130T CPU, 
nothing overly special.
  More details I would provide in your further requests but the current kernel 
behavior is very annoying.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: #RESUME=UUID=f7bcdeb1-6c61-4012-81c4-a43a492ffb6e
  InstallationDate: Installed on 2009-11-01 (3810 days ago)
  InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-96-generic 
root=/dev/mapper/vg00-root64 ro rootflags=commit=3600 rootflags=commit=3600 
loop.max_part=63
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-96-generic N/A
   linux-backports-modules-4.15.0-96-generic  N/A
   linux-firmware 1.173.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-96-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2010-10-11 (3466 days ago)
  UserGroups: adm admin audio cdrom dialout dip disk dos fuse jabber kvm 
libvirt libvirtd lpadmin plugdev proxy pulse pulse-access sambashare src
  _MarkForUpload: True
  dmi.bios.date: 07/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-G
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/22/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-G:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  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/1871430/+subscriptions

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

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

[Wladimir Mutel]

apport information

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

Title:
  iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My home server/router/access point runs under Ubuntu 18.04.4 with all updates 
and has 2 wifi adapters operated by hostapd
  one is USB AR9271 (0cf3:9271, driver ath9k_htc), another is PCIe Intel AC 
9260 (8086:2526, driver iwlwifi).
  with kernel 4.15.0-88 it worked quite stable, with reboots required mostly 
after kernel upgrades (much less frequent reboots due to panics)
  with kernel 4.15.0-91 and -96 it started rebooting by itself by panic when a 
lot of activity happening via Intel 9260.
  In /etc/sysctl* I have kernel.panic=10 , kernel.softlockup_panic=1 and 
kernel.panic_on_oops=1 overrides of default values.
  In dmesg logs preceding the reboot, I see multiple warnings with stacks 
inside iwl_mvm functions which I could provide by apport. Also, multiple 
messages like "Command LQ_CMD: a command is already active!" or "Error sending 
LQ_CMD: time out after 2000ms"
  Unfortunately I run this box headless and I don't have another wired Ethernet 
host to capture its panics by netconsole
  The rest of hardware is pretty standard. Asus B85M-G mobo, Core i3-4130T CPU, 
nothing overly special.
  More details I would provide in your further requests but the current kernel 
behavior is very annoying.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: #RESUME=UUID=f7bcdeb1-6c61-4012-81c4-a43a492ffb6e
  InstallationDate: Installed on 2009-11-01 (3810 days ago)
  InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-96-generic 
root=/dev/mapper/vg00-root64 ro rootflags=commit=3600 rootflags=commit=3600 
loop.max_part=63
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-96-generic N/A
   linux-backports-modules-4.15.0-96-generic  N/A
   linux-firmware 1.173.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-96-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2010-10-11 (3466 days ago)
  UserGroups: adm admin audio cdrom dialout dip disk dos fuse jabber kvm 
libvirt libvirtd lpadmin plugdev proxy pulse pulse-access sambashare src
  _MarkForUpload: True
  dmi.bios.date: 07/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-G
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/22/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-G:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  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/1871430/+subscriptions

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

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

[Wladimir Mutel]

apport information

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

Title:
  iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My home server/router/access point runs under Ubuntu 18.04.4 with all updates 
and has 2 wifi adapters operated by hostapd
  one is USB AR9271 (0cf3:9271, driver ath9k_htc), another is PCIe Intel AC 
9260 (8086:2526, driver iwlwifi).
  with kernel 4.15.0-88 it worked quite stable, with reboots required mostly 
after kernel upgrades (much less frequent reboots due to panics)
  with kernel 4.15.0-91 and -96 it started rebooting by itself by panic when a 
lot of activity happening via Intel 9260.
  In /etc/sysctl* I have kernel.panic=10 , kernel.softlockup_panic=1 and 
kernel.panic_on_oops=1 overrides of default values.
  In dmesg logs preceding the reboot, I see multiple warnings with stacks 
inside iwl_mvm functions which I could provide by apport. Also, multiple 
messages like "Command LQ_CMD: a command is already active!" or "Error sending 
LQ_CMD: time out after 2000ms"
  Unfortunately I run this box headless and I don't have another wired Ethernet 
host to capture its panics by netconsole
  The rest of hardware is pretty standard. Asus B85M-G mobo, Core i3-4130T CPU, 
nothing overly special.
  More details I would provide in your further requests but the current kernel 
behavior is very annoying.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: #RESUME=UUID=f7bcdeb1-6c61-4012-81c4-a43a492ffb6e
  InstallationDate: Installed on 2009-11-01 (3810 days ago)
  InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-96-generic 
root=/dev/mapper/vg00-root64 ro rootflags=commit=3600 rootflags=commit=3600 
loop.max_part=63
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-96-generic N/A
   linux-backports-modules-4.15.0-96-generic  N/A
   linux-firmware 1.173.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-96-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2010-10-11 (3466 days ago)
  UserGroups: adm admin audio cdrom dialout dip disk dos fuse jabber kvm 
libvirt libvirtd lpadmin plugdev proxy pulse pulse-access sambashare src
  _MarkForUpload: True
  dmi.bios.date: 07/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-G
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/22/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-G:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  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/1871430/+subscriptions

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

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

[Wladimir Mutel]

apport information

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

Title:
  iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My home server/router/access point runs under Ubuntu 18.04.4 with all updates 
and has 2 wifi adapters operated by hostapd
  one is USB AR9271 (0cf3:9271, driver ath9k_htc), another is PCIe Intel AC 
9260 (8086:2526, driver iwlwifi).
  with kernel 4.15.0-88 it worked quite stable, with reboots required mostly 
after kernel upgrades (much less frequent reboots due to panics)
  with kernel 4.15.0-91 and -96 it started rebooting by itself by panic when a 
lot of activity happening via Intel 9260.
  In /etc/sysctl* I have kernel.panic=10 , kernel.softlockup_panic=1 and 
kernel.panic_on_oops=1 overrides of default values.
  In dmesg logs preceding the reboot, I see multiple warnings with stacks 
inside iwl_mvm functions which I could provide by apport. Also, multiple 
messages like "Command LQ_CMD: a command is already active!" or "Error sending 
LQ_CMD: time out after 2000ms"
  Unfortunately I run this box headless and I don't have another wired Ethernet 
host to capture its panics by netconsole
  The rest of hardware is pretty standard. Asus B85M-G mobo, Core i3-4130T CPU, 
nothing overly special.
  More details I would provide in your further requests but the current kernel 
behavior is very annoying.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: #RESUME=UUID=f7bcdeb1-6c61-4012-81c4-a43a492ffb6e
  InstallationDate: Installed on 2009-11-01 (3810 days ago)
  InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-96-generic 
root=/dev/mapper/vg00-root64 ro rootflags=commit=3600 rootflags=commit=3600 
loop.max_part=63
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-96-generic N/A
   linux-backports-modules-4.15.0-96-generic  N/A
   linux-firmware 1.173.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-96-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2010-10-11 (3466 days ago)
  UserGroups: adm admin audio cdrom dialout dip disk dos fuse jabber kvm 
libvirt libvirtd lpadmin plugdev proxy pulse pulse-access sambashare src
  _MarkForUpload: True
  dmi.bios.date: 07/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-G
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/22/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-G:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  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/1871430/+subscriptions

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

[Kernel-packages] [Bug 1871430] Re: iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91

[Wladimir Mutel]

** Tags added: apport-collected bionic

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

Title:
  iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My home server/router/access point runs under Ubuntu 18.04.4 with all updates 
and has 2 wifi adapters operated by hostapd
  one is USB AR9271 (0cf3:9271, driver ath9k_htc), another is PCIe Intel AC 
9260 (8086:2526, driver iwlwifi).
  with kernel 4.15.0-88 it worked quite stable, with reboots required mostly 
after kernel upgrades (much less frequent reboots due to panics)
  with kernel 4.15.0-91 and -96 it started rebooting by itself by panic when a 
lot of activity happening via Intel 9260.
  In /etc/sysctl* I have kernel.panic=10 , kernel.softlockup_panic=1 and 
kernel.panic_on_oops=1 overrides of default values.
  In dmesg logs preceding the reboot, I see multiple warnings with stacks 
inside iwl_mvm functions which I could provide by apport. Also, multiple 
messages like "Command LQ_CMD: a command is already active!" or "Error sending 
LQ_CMD: time out after 2000ms"
  Unfortunately I run this box headless and I don't have another wired Ethernet 
host to capture its panics by netconsole
  The rest of hardware is pretty standard. Asus B85M-G mobo, Core i3-4130T CPU, 
nothing overly special.
  More details I would provide in your further requests but the current kernel 
behavior is very annoying.

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

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

[Kernel-packages] [Bug 1870637] Re: Nvidia+modeset: Can't set 4K@60Hz: HDMI max TMDS frequency 300000KHz

[Paul Berkx]

I found the wayland option on the login screen and i enabled it,
than i selected the nvidia 440 driver, rebooted and i was back to full hd, not 
being able to get 4K @60

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

Title:
  Nvidia+modeset: Can't set 4K@60Hz: HDMI max TMDS frequency 30KHz

Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  When i do get it to work, on reboot it'll be back to fullhd.
  this happens on nvidia 440, 435 and 390.

  On X.Org X server it does work.

  Graphics card: nVidia GT1030
  Amp: Onkyo TX-NR646

  On 19.10 there are no problems.
  A couple of weeks ago i tested a daily build and there were no troubles also, 
so this is new.

  My favourite setting: 3840x2160 200% 60hz.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..10.00.0: Error: [Errno 21] Is een map: 
'/proc/driver/nvidia/gpus/:10:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 01:02:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] 
[19da:2476]
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Micro-Star International Co., Ltd. MS-7B84
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=99bd1cce-b30c-44fb-8ead-90317474c33f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.D0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M PRO-M2 (MS-7B84)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.D0:bd12/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2(MS-7B84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B84
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-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.7-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+git20190815-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/nvidia-graphics-drivers-435/+bug/1870637/+subscriptions

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

[Kernel-packages] [Bug 1869235] Re: Ryzen 3rd gen (3900X) ECC support missing from kernel

[Alex Hung]

** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan

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

Title:
  Ryzen 3rd gen (3900X) ECC support missing from kernel

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  Ubuntu server:
  Description:Ubuntu 19.10
  Release:19.10
  Installed kernel:
  linux-generic:
Installed: 5.3.0.42.36
  (I could not figure out what package to select in the 'in what package did 
you find this bug' chooser)

  Expected behavior: ECC RAM is detected and utilized
  Result instead:
  Error in dmesg at boot:
  EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) (more in the 
attached KernelErrors.log)

  Kernel 5.3 is missing ECC support for some families of AMD Ryzen 3rd
  gen CPUs.

  Support is added via these two commits in the mainline tree:
  
https://github.com/torvalds/linux/commit/e53a3b267fb0a79db9ca1f1e08b97889b22013e6
  
https://github.com/torvalds/linux/commit/3e443eb353eda6f4b4796e07f2599683fa752f1d

  The second commit actually adds the missing support, but it relies on
  the first commit: a partial refactor of the AMD ECC code.

  I tested myself, followed the instructions at 
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel to build my own kernel, 
cherry-picked the two above commits, and have working ECC support on my 
self-built kernel:
  Linux smaug 5.3.0-43-generic #36 SMP Sat Mar 21 02:33:30 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux:

  EDAC MC: Ver: 3.0.0
  EDAC amd64: Node 0: DRAM ECC enabled.
  EDAC amd64: F17h_M70h detected (node 0).
  EDAC MC: UMC0 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC MC: UMC1 chip selects:
  EDAC amd64: MC: 0: 0MB 1: 0MB
  EDAC amd64: MC: 2: 16384MB 3: 16384MB
  EDAC amd64: using x16 syndromes.
  EDAC amd64: MCT channel count: 2
  EDAC MC0: Giving out device to module amd64_edac controller F17h_M70h: DEV 
:00:18.3 (INTERRUPT)
  EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI 
controller: DEV :00:18.0 (POLLED)
  AMD64 EDAC driver v3.5.0

  
  If this could be included in a future hardware support kernel release, that 
would be very helpful.  I am unsure what the policy is for including this kind 
of backport in non-LTS kernels, though I know the LTS releases have hardware 
support updates that include this type of fix.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-03-20 (6 days ago)
  InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=89cfcc61-dbca-43d3-9a2e-5961df9ae5b4 ro
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  RfKill:
   
  Tags:  eoan uec-images
  Uname: Linux 5.3.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lxd plugdev sudo
  _MarkForUpload: False
  dmi.bios.date: 10/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.30
  dmi.board.name: X470D4U2-2T
  dmi.board.vendor: ASRockRack
  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.:bvrP3.30:bd10/03/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRockRack:rnX470D4U2-2T:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

-- 
Mailing list: https://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 1870946] Re: iwlwifi breaking on dell precision 7740 with Intel Wi-Fi 6 AX200 [8086:2723] subsystem [8086:4080]

[max m]

hmm, it was "off" in the settings.

So I tried turning it on and connecting to my bluetooth speaker to see
what would happen, and the dmesg output looks like a mess (attached).

The interface says the device is connected but it doesn't show up in
pavucontrol.

I'll try version 50 of the driver later today and report back

On Tue, Apr 7, 2020, at 5:59 AM, You-Sheng Yang wrote:
> I also noticed in your WifiSyslog.txt it has:
> 
>   kernel: Bluetooth: hci0: command 0xfc09 tx timeout
> 
> Does this Dell 7740 have Bluetooth functioning at all time?
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1870946
> 
> Title:
>   iwlwifi breaking on dell precision 7740 with Intel Wi-Fi 6 AX200
>   [8086:2723] subsystem [8086:4080]
> 
> Status in linux package in Ubuntu:
>   Incomplete
> 
> Bug description:
>   0
> 
>   I'm running an up-to-date version of the dev branch and have had a
>   problem since I first installed it.
> 
>   I'm on a new Dell Precision 7740, with:
> 
>   Intel i9-9880H
> 
>   Radeon Pro WX 3200
> 
>   and network card is:
> 
>   Intel Wi-Fi 6 AX200 2x2 .11ax 160MHz + Bluetooth 5.0 Driver
> 
>   I'm getting a bunch of problems. Packet loss varies from 15%-35%,
>   often I can't load anything when I'm on wifi. Also sometimes `ping`
>   errors out with:
> 
>   From 192.168.1.247 icmp_seq=138 Destination Host Unreachable
> 
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: linux-modules-extra-5.4.0-21-generic 5.4.0-21.25
>   ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
>   Uname: Linux 5.4.0-21-generic x86_64
>   NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
>   ApportVersion: 2.20.11-0ubuntu21
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  max8466 F pulseaudio
>/dev/snd/pcmC0D0p:   max8466 F...m pulseaudio
>/dev/snd/controlC1:  max8466 F pulseaudio
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Apr  5 11:57:32 2020
>   InstallationDate: Installed on 2020-03-13 (23 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
>   IwConfig:
>wlp112s0  no wireless extensions.
>
>eno1  no wireless extensions.
>
>lono wireless extensions.
>   MachineType: Dell Inc. Precision 7740
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/usr/bin/fish
>   ProcFB:
>0 i915drmfb
>1 amdgpudrmfb
>   ProcKernelCmdLine: 
> BOOT_IMAGE=/BOOT/ubuntu_igsmls@/vmlinuz-5.4.0-21-generic 
> root=ZFS=rpool/ROOT/ubuntu_igsmls ro quiet splash vt.handoff=1
>   RelatedPackageVersions:
>linux-restricted-modules-5.4.0-21-generic N/A
>linux-backports-modules-5.4.0-21-generic  N/A
>linux-firmware1.187
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 12/10/2019
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 1.6.0
>   dmi.board.name: 0FRKPX
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias: 
> dmi:bvnDellInc.:bvr1.6.0:bd12/10/2019:svnDellInc.:pnPrecision7740:pvr:rvnDellInc.:rn0FRKPX:rvrA00:cvnDellInc.:ct10:cvr:
>   dmi.product.family: Precision
>   dmi.product.name: Precision 7740
>   dmi.product.sku: 0927
>   dmi.sys.vendor: Dell Inc.
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870946/+subscriptions
>

** Attachment added: "dmesg | grep iwlwifi.log"
   
https://bugs.launchpad.net/bugs/1870946/+attachment/5348842/+files/dmesg%20%7C%20grep%20iwlwifi.log

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

Title:
  iwlwifi breaking on dell precision 7740 with Intel Wi-Fi 6 AX200
  [8086:2723] subsystem [8086:4080]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  0

  I'm running an up-to-date version of the dev branch and have had a
  problem since I first installed it.

  I'm on a new Dell Precision 7740, with:

  Intel i9-9880H

  Radeon Pro WX 3200

  and network card is:

  Intel Wi-Fi 6 AX200 2x2 .11ax 160MHz + Bluetooth 5.0 Driver

  I'm getting a bunch of problems. Packet loss varies from 15%-35%,
  often I can't load anything when I'm on wifi. Also sometimes `ping`
  errors out with:

  From 192.168.1.247 icmp_seq=138 Destination Host Unreachable

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-modules-extra-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USER   

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

[Ubuntu Kernel Bot]

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

apport-collect 1871430

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My home server/router/access point runs under Ubuntu 18.04.4 with all updates 
and has 2 wifi adapters operated by hostapd
  one is USB AR9271 (0cf3:9271, driver ath9k_htc), another is PCIe Intel AC 
9260 (8086:2526, driver iwlwifi).
  with kernel 4.15.0-88 it worked quite stable, with reboots required mostly 
after kernel upgrades (much less frequent reboots due to panics)
  with kernel 4.15.0-91 and -96 it started rebooting by itself by panic when a 
lot of activity happening via Intel 9260.
  In /etc/sysctl* I have kernel.panic=10 , kernel.softlockup_panic=1 and 
kernel.panic_on_oops=1 overrides of default values.
  In dmesg logs preceding the reboot, I see multiple warnings with stacks 
inside iwl_mvm functions which I could provide by apport. Also, multiple 
messages like "Command LQ_CMD: a command is already active!" or "Error sending 
LQ_CMD: time out after 2000ms"
  Unfortunately I run this box headless and I don't have another wired Ethernet 
host to capture its panics by netconsole
  The rest of hardware is pretty standard. Asus B85M-G mobo, Core i3-4130T CPU, 
nothing overly special.
  More details I would provide in your further requests but the current kernel 
behavior is very annoying.

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

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

[Kernel-packages] [Bug 1821564] Re: b44 Ethernet driver null pointer during initialization

[Nelson Hennemann F]

@Boris Gjenero, try using the kernel parameter "iommu=soft" instead of
limiting the memory to 1GB. It will force the use of a 64MB swiotlb
bounce buffer to workaround this issue. Tested with Focal Fossa Beta ISO
(Kernel 5.4.0-21-generic) on my Optiplex 320 with 2GB of RAM.

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

Title:
  b44 Ethernet driver null pointer during initialization

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This problem started after upgrading to Ubuntu 19.04. It was not
  present with 4.18.0-16-generic kernel and is present in the
  4.18.0-15-generic kernel. Ever time during boot there is a null
  pointer dereference in the b44 driver for the on-board Ethernet on
  this Dell Inspiron 6400. After that I can log in but networking
  related commands hang and the computer eventually locks up.
  Blacklisting the b44 module so it doesn't load works as a workaround,
  though of course the on board Ethernet can't be used that way. The b43
  WiFi still works then. The following is pasted from the log of one
  crash:

  6.483003] BUG: unable to handle kernel NULL pointer dereference at 

  6.483052] #PF error: [normal kernel read fault]
  6.483093] PGD 0 P4D 0 
  6.483133] Oops:  [#1] SMP PTI
  6.483175] CPU: 0 PID: 725 Comm: NetworkManager Tainted: GW 
5.0.0-7-generic #8-Ubuntu
  6.483217] Hardware name: Dell Inc. MM061   /0XD720, 
BIOS A17 06/13/2007
  6.483267] RIP: 0010:swiotlb_tbl_map_single+0x120/0x310
  6.483310] Code: 4c 8b 45 a8 4c 8b 1d 0f b2 a9 01 89 d3 45 31 d2 44 8b 4d a4 
44 89 c7 41 89 dc 4b 8d 44 25 00 48 21 f0 48 01 f8 49 39 c7 72 0a <47> 39 0c a3 
0f 83 cb 00 00 00 42 8d 04 33 48 89 c3 48 39 c1 41 0f
  6.483368] RSP: 0018:bc7040c7f3c0 EFLAGS: 00010016
  6.483416] RAX: 0001 RBX:  RCX: 
  6.483467] RDX:  RSI: 001f RDI: 0001
  6.483521] RBP: bc7040c7f420 R08: 0001 R09: 0001
  6.483572] R10:  R11:  R12: 
  6.483621] R13:  R14: 0001 R15: 0020
  6.483670] FS:  7f2cb49ccbc0() GS:9d8a4c40() 
knlGS:
  6.483726] CS:  0010 DS:  ES:  CR0: 80050033
  6.483773] CR2:  CR3: c72ce000 CR4: 06f0
  6.483820] Call Trace:
  6.483869]  swiotlb_map+0x6c/0x1c0
  6.483915]  dma_direct_map_page+0xc5/0x160
  6.483965]  b44_alloc_rx_skb+0x18e/0x3f0 [b44]
  6.484013]  b44_init_rings+0xbe/0x1b0 [b44]
  6.484060]  b44_open+0xfc/0x3f0 [b44]
  6.484107]  __dev_open+0xd4/0x170
  6.484153]  __dev_change_flags+0x18f/0x200
  6.484199]  dev_change_flags+0x27/0x60
  6.484246]  do_setlink+0x31c/0xe30
  6.484292]  ? __nla_parse+0xf1/0x120
  6.484340]  ? cpumask_next+0x1b/0x20
  6.484388]  ? __snmp6_fill_stats64.isra.57+0xf6/0x120
  6.484439]  ? __nla_parse+0x38/0x120
  6.484488]  __rtnl_newlink+0x531/0x910
  6.484535]  ? __nla_put+0x20/0x30
  6.484586]  ? __kmalloc_node_track_caller+0x1e6/0x2b0
  6.484636]  ? pskb_expand_head+0x70/0x2e0
  6.484693]  ? __kmalloc_reserve.isra.53+0x31/0x90
  6.484751]  ? apparmor_inet_conn_request+0x40/0x40
  6.484822]  ? security_sock_rcv_skb+0x2f/0x50
  6.484879]  ? skb_queue_tail+0x43/0x50
  6.484934]  ? __netlink_sendskb+0x53/0x70
  6.484992]  ? syscall_return_via_sysret+0xf/0x7f
  6.485043]  ? __switch_to_asm+0x40/0x70
  6.485097]  ? syscall_return_via_sysret+0xf/0x7f
  6.485153]  ? _cond_resched+0x19/0x30
  6.485204]  ? kmem_cache_alloc_trace+0x153/0x1d0
  6.485253]  rtnl_newlink+0x48/0x70
  6.485301]  rtnetlink_rcv_msg+0x213/0x300
  6.485348]  ? __d_lookup+0x126/0x140
  6.485393]  ? rtnl_calcit.isra.31+0x100/0x100
  6.485440]  netlink_rcv_skb+0x4f/0x120
  6.485485]  rtnetlink_rcv+0x15/0x20
  6.485518]  netlink_unicast+0x1a1/0x260
  6.485518]  netlink_sendmsg+0x20d/0x3c0
  6.485518]  sock_sendmsg+0x3e/0x50
  6.485518]  ___sys_sendmsg+0x295/0x2f0
  6.485518]  ? rtnl_unlock+0xe/0x10
  6.485518]  ? addrconf_sysctl_forward+0x114/0x280
  6.485518]  ? dev_forward_change+0x140/0x140
  6.485518]  ? __fget_light+0x54/0x60
  6.485518]  __sys_sendmsg+0x5c/0xa0
  6.485518]  __x64_sys_sendmsg+0x1f/0x30
  6.485518]  do_syscall_64+0x5a/0x110
  6.485518]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  6.485518] RIP: 0033:0x7f2cb6153cb7
  6.485518] Code: 44 00 00 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 
3b ed ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 
ff ff 77 35 44 89 c7 48 89 44 24 08 e8 74 ed ff ff 48
  6.485518] RSP: 002b:7ffe93a35c80 EFLAGS: 0293 ORIG_RAX: 
002e
  6.485518] RAX: ffda RBX: 0008 RCX: 7f2cb6153cb7
  6.485518] RDX:  RSI: 7ffe93a35cd0 RDI: 0008
  6.485518] RBP: 7ffe93a35cd0 

[Kernel-packages] [Bug 1870637] Re: Nvidia+modeset: Can't set 4K@60Hz: HDMI max TMDS frequency 300000KHz

[Paul Berkx]

I don't see an option at the login screen to switch to wayland, how do i
do this?

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

Title:
  Nvidia+modeset: Can't set 4K@60Hz: HDMI max TMDS frequency 30KHz

Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  When i do get it to work, on reboot it'll be back to fullhd.
  this happens on nvidia 440, 435 and 390.

  On X.Org X server it does work.

  Graphics card: nVidia GT1030
  Amp: Onkyo TX-NR646

  On 19.10 there are no problems.
  A couple of weeks ago i tested a daily build and there were no troubles also, 
so this is new.

  My favourite setting: 3840x2160 200% 60hz.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..10.00.0: Error: [Errno 21] Is een map: 
'/proc/driver/nvidia/gpus/:10:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 01:02:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] 
[19da:2476]
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Micro-Star International Co., Ltd. MS-7B84
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=99bd1cce-b30c-44fb-8ead-90317474c33f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.D0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M PRO-M2 (MS-7B84)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.D0:bd12/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2(MS-7B84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B84
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-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.7-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+git20190815-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/nvidia-graphics-drivers-435/+bug/1870637/+subscriptions

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

[Kernel-packages] [Bug 1871430] [NEW] iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91

[Wladimir Mutel]

Public bug reported:

My home server/router/access point runs under Ubuntu 18.04.4 with all updates 
and has 2 wifi adapters operated by hostapd
one is USB AR9271 (0cf3:9271, driver ath9k_htc), another is PCIe Intel AC 9260 
(8086:2526, driver iwlwifi).
with kernel 4.15.0-88 it worked quite stable, with reboots required mostly 
after kernel upgrades (much less frequent reboots due to panics)
with kernel 4.15.0-91 and -96 it started rebooting by itself by panic when a 
lot of activity happening via Intel 9260.
In /etc/sysctl* I have kernel.panic=10 , kernel.softlockup_panic=1 and 
kernel.panic_on_oops=1 overrides of default values.
In dmesg logs preceding the reboot, I see multiple warnings with stacks inside 
iwl_mvm functions which I could provide by apport. Also, multiple messages like 
"Command LQ_CMD: a command is already active!" or "Error sending LQ_CMD: time 
out after 2000ms"
Unfortunately I run this box headless and I don't have another wired Ethernet 
host to capture its panics by netconsole
The rest of hardware is pretty standard. Asus B85M-G mobo, Core i3-4130T CPU, 
nothing overly special.
More details I would provide in your further requests but the current kernel 
behavior is very annoying.

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

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

Title:
  iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91

Status in linux package in Ubuntu:
  New

Bug description:
  My home server/router/access point runs under Ubuntu 18.04.4 with all updates 
and has 2 wifi adapters operated by hostapd
  one is USB AR9271 (0cf3:9271, driver ath9k_htc), another is PCIe Intel AC 
9260 (8086:2526, driver iwlwifi).
  with kernel 4.15.0-88 it worked quite stable, with reboots required mostly 
after kernel upgrades (much less frequent reboots due to panics)
  with kernel 4.15.0-91 and -96 it started rebooting by itself by panic when a 
lot of activity happening via Intel 9260.
  In /etc/sysctl* I have kernel.panic=10 , kernel.softlockup_panic=1 and 
kernel.panic_on_oops=1 overrides of default values.
  In dmesg logs preceding the reboot, I see multiple warnings with stacks 
inside iwl_mvm functions which I could provide by apport. Also, multiple 
messages like "Command LQ_CMD: a command is already active!" or "Error sending 
LQ_CMD: time out after 2000ms"
  Unfortunately I run this box headless and I don't have another wired Ethernet 
host to capture its panics by netconsole
  The rest of hardware is pretty standard. Asus B85M-G mobo, Core i3-4130T CPU, 
nothing overly special.
  More details I would provide in your further requests but the current kernel 
behavior is very annoying.

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

-- 
Mailing list: https://launchpad.net/~kernel-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] Missing required logs.

[Ubuntu Kernel Bot]

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

apport-collect 1861941

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed-5.4 package in Ubuntu:
  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 1870637] Re: Nvidia+modeset: Can't set 4K@60Hz: HDMI max TMDS frequency 300000KHz

[Paul Berkx]

The first time i was able to install third party propietary software
through the ubuntu installation process. (So nvidia was enabled after
the ubuntu installation process if i remeber correctly.

Today I installed the nvidia driver through Updatemanagement console, because
currently the ubuntu installer crashes if i set it to install propietary 
software, this appearently already has been reported.

I have made a second thread (to get new report files to you, since i
swapped my 2200G with a ryzen 5 2600.
https://bugs.launchpad.net/ubuntu/+bug/1871422 ) - i will now try to
login with wayland

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

Title:
  Nvidia+modeset: Can't set 4K@60Hz: HDMI max TMDS frequency 30KHz

Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  When i do get it to work, on reboot it'll be back to fullhd.
  this happens on nvidia 440, 435 and 390.

  On X.Org X server it does work.

  Graphics card: nVidia GT1030
  Amp: Onkyo TX-NR646

  On 19.10 there are no problems.
  A couple of weeks ago i tested a daily build and there were no troubles also, 
so this is new.

  My favourite setting: 3840x2160 200% 60hz.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..10.00.0: Error: [Errno 21] Is een map: 
'/proc/driver/nvidia/gpus/:10:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 01:02:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] 
[19da:2476]
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Micro-Star International Co., Ltd. MS-7B84
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=99bd1cce-b30c-44fb-8ead-90317474c33f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.D0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M PRO-M2 (MS-7B84)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.D0:bd12/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2(MS-7B84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B84
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-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.7-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+git20190815-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/nvidia-graphics-drivers-435/+bug/1870637/+subscriptions

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

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

[Joshua Powers]

Adding Linux task to get kernel team's attention

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

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in linux package in Ubuntu:
  New
Status in linux-signed-5.4 package in Ubuntu:
  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 1871414] Re: Pulseaudio incorrectly detects a headphone being plugged in

[Yosep Perez]

** Package changed: alsa-lib (Ubuntu) => pulseaudio (Ubuntu)

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

Title:
  Pulseaudio incorrectly detects a headphone being plugged in

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Software details:
  Distro: Kubuntu 20.04 Beta
  Kernel: 5.4.0-21-generic
  alsa-base version 1.0.25+dfsg-0ubuntu5
  alsa-utils version 1.2.2-1ubuntu1
  pulseaudio version 1:13.99.1-1ubuntu1

  Hardware details:
  Motherboard: Gigabyte GA-AB350M-D3H
  Audio Codec: Realtek ALC887
  GPU: Nvidia RTX 2060 Super (with the audio output disabled in PulseAudio)

  Regarding the issue:
  Every time I start an audio stream (regardless of the application), I can 
hear interruptions in the sound and when opening alsamixer I can also see the 
interface kind of flickering for a few milliseconds.
  After running pulseaudio with logging enabled for a few seconds (while 
playing music), this pattern can be seen:

  [pulseaudio] sink.c: alsa_output.pci-_0a_00.3.analog-stereo: state: IDLE 
-> RUNNING
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes

  Note: I've no headphones attached ! Only the line out is connected to
  a 2.1 Speaker

  It seems basically the same bug as this: 
https://bbs.archlinux.org/viewtopic.php?id=147225
  but in my case disabling "module-switch-on-port-available" doesn't remove the 

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

[Ryan Harper]

This is still occurring daily.

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in linux-signed-5.4 package in Ubuntu:
  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-signed-5.4/+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 1867803] Re: ALSA: No soundcards found after updating kernel to 5.3.0.42.36

[Hui Wang]

@Arnau,

please upload the dmesg after created the symlink.

thx.

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

Title:
  ALSA: No soundcards found after updating kernel to 5.3.0.42.36

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  There seems to be some changes in ALSA in 5.3.0.41 and it seems to
  have caused some regression on my HP Spectrre (details attached).

  ~$ alsactl init
  alsactl: init:1759: No soundcards found...

  I verified that 5.3.0.40 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-42-generic 5.3.0-42.34
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 18 01:11:42 2020
  InstallationDate: Installed on 2019-07-11 (249 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: HP HP Spectre x360 Convertible 13-ap0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=57fb6fa4-a696-476b-813a-635b91fbc299 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.28
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8514
  dmi.board.vendor: HP
  dmi.board.version: 09.48
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.28:bd04/22/2019:svnHP:pnHPSpectrex360Convertible13-ap0xxx:pvr:rvnHP:rn8514:rvr09.48:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ap0xxx
  dmi.product.sku: 5KX23PA#ABJ
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1871414] [NEW] Pulseaudio incorrectly detects a headphone being plugged in

[Yosep Perez]

Public bug reported:

Software details:
Distro: Kubuntu 20.04 Beta
Kernel: 5.4.0-21-generic
alsa-base version 1.0.25+dfsg-0ubuntu5
alsa-utils version 1.2.2-1ubuntu1
pulseaudio version 1:13.99.1-1ubuntu1

Hardware details:
Motherboard: Gigabyte GA-AB350M-D3H
Audio Codec: Realtek ALC887
GPU: Nvidia RTX 2060 Super (with the audio output disabled in PulseAudio)

Regarding the issue:
Every time I start an audio stream (regardless of the application), I can hear 
interruptions in the sound and when opening alsamixer I can also see the 
interface kind of flickering for a few milliseconds.
After running pulseaudio with logging enabled for a few seconds (while playing 
music), this pattern can be seen:

[pulseaudio] sink.c: alsa_output.pci-_0a_00.3.analog-stereo: state: IDLE -> 
RUNNING
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged 
in
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
yes
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
no
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged 
in
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
yes
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
no
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged 
in
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
yes
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
no
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged 
in
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
yes
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
no
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged 
in
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
yes
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
no
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged 
in
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
yes
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
no
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged 
in
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
yes
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
no
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged 
in
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
yes
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
no
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged 
in
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
yes
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
no
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged 
in
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
yes
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
no
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged 
in
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
yes

Note: I've no headphones attached ! Only the line out is connected to a
2.1 Speaker

It seems basically the same bug as this: 
https://bbs.archlinux.org/viewtopic.php?id=147225
but in my case disabling "module-switch-on-port-available" doesn't remove the 
audio "artifacts"

** Affects: alsa-lib (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Verbose Logs"
   
https://bugs.launchpad.net/bugs/1871414/+attachment/5348776/+files/pulseverbose.log

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

Title:
  Pulseaudio incorrectly detects a headphone being plugged in

Status in 

[Kernel-packages] [Bug 1866852] Re: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor

[Matthieu Clemenceau]

Unfortunately, when the screen is black I have no ssh access

>From a cold boot, When I press the power button, nothing happen, the screen 
>remains black, I don't even see the BIOS logo or FDE password key. (when USB-C 
>is plugged in)
I'm having a feeling the kernel might not even be started and it could be a 
Hardware BIOS 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/1866852

Title:
  System Display black screen on reboot or after a clean shutdown with
  USB-C Dock Monitor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm running focal devel and the latest kernel (see proc version below)

  Linux version 5.4.0-18-generic (buildd@lgw01-amd64-034) (gcc version
  9.2.1 20200306 (Ubuntu 9.2.1-31ubuntu3)) #22-Ubuntu SMP Sat Mar 7
  18:13:06 UTC 2020

  Dock Monitor is supported very well with multiple usb devices plugged
  on the monitor.

  However on reboot I face a black screen with no ability to enter my FDE 
password.
  Both my Laptop screen and the attached usb-c display nothing
  I have to hard power off and reboot without the USB-C monitor plugged in.

  Otherwise A reboot cycle with the usb-c unplugged works perfectly.

  Also I tried to run ubuntu-bug linux or ubuntu-bug linux-image-generic 
without success. I would be happy to provide much more debugging information. I 
will attach then to the launchpad Bug #
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mclemenceau   2988 F pulseaudio
   /dev/snd/controlC0:  mclemenceau   2988 F pulseaudio
   /dev/snd/controlC1:  mclemenceau   2988 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-05 (64 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  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=/vmlinuz-5.4.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.186
  Tags:  focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-23 (47 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.41
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.21:bd06/14/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.41:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.product.sku: 2TV18AS#ABA
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1867338] Re: Is kerneloops still useful on Ubuntu?

[Bug Watch Updater]

** Changed in: kerneloops (Debian)
   Status: Confirmed => Fix Released

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

Title:
  Is kerneloops still useful on Ubuntu?

Status in kerneloops package in Ubuntu:
  New
Status in kerneloops package in Debian:
  Fix Released

Bug description:
  The package is scheduled for removal in Debian due to oops.kernel.org
  not accepting and showing uploaded oops-es anymore.

  In Ubuntu kerneloops is changes to collect OOPS-es via apport but it
  is still possible to configure it to send reports to oops.kernel.org.

  Kerneloops' removal in Debian may point to the direction of
  redesigning OOPS collection in Ubuntu without it, then this package
  should be removed in Ubuntu, too.

  If kerneloops is kept as an Ubuntu-only package it would be useful to
  add a note in the configuration file that oops.kernel.org does not
  accept submissions anymore and the relevant parts could be removed
  from the codebase.

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

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

[Kernel-packages] [Bug 1871395] Re: CONFIG_RESET_ATTACK_MITIGATION should not be enabled by default without additional scripts

[valdikss]

systemd service which disables reset mitigation upon shutdown

** Attachment added: "disable-reset-attack-mitigation.service"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871395/+attachment/5348751/+files/disable-reset-attack-mitigation.service

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

Title:
  CONFIG_RESET_ATTACK_MITIGATION should not be enabled by default
  without additional scripts

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description of problem:

  Ubuntu 19.10 kernel 5.3.0-46-generic has Reset Attack Mitigation enabled 
(CONFIG_RESET_ATTACK_MITIGATION) which may cause strange reboot sequence on 
certain hardware (Lenovo Thinkpad X220).
  Instead of rebooting normally, the laptop would hard power off (without 
properly stopping peripherals and internal devices, which may be spotted by HDD 
losing power with a specific unusual sound) and then powers on again after 1 
second.

  This kernel configuration option should not be enabled unless additional 
scripts, which disable RAM clean step upon normal poweroff/reboot. I made the 
systemd service to workaround the problem, which writes "0" to 
MemoryOverwriteRequestControl EFI variable:
  https://gist.github.com/ValdikSS/86352b03ec3ed3c8713b78c7e20dc222

  The author of this kernel option, Matthew Garett, wrote the following:
  >if userspace can ensure that all secrets are
  >removed as part of a controlled shutdown, it can reset this variable to
  >0 before triggering a hardware reboot.

  https://lwn.net/Articles/730006/

  
  Version-Release number of selected component (if applicable):
  linux-image 5.3.0-46-generic

  How reproducible:
  Always

  Steps to Reproduce:
  1. Boot Ubuntu 19.10, either live or installed
  2. Reboot the computer (Lenovo X220 laptop in my case)

  Actual results:
  The computer perform hard power off and power on after 1 second

  Expected results:
  The computer reboots without losing power

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

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

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

Title:
  watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [kworker/6:2:225]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  All I can say is that this error keeps on occurring

  ProblemType: KernelOops
  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
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 966 F pulseaudio
dwrdj  1457 F pulseaudio
   /dev/snd/controlC1:  gdm 966 F pulseaudio
dwrdj  1457 F pulseaudio
  Date: Tue Apr  7 15:06:49 2020
  Failure: oops
  InstallationDate: Installed on 2020-04-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200405)
  MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DV_FX505DV
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=669b0fce-4369-4d96-b5ee-74274faf2a13 ro quiet splash nomodeset 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [kworker/6:2:225]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX505DV.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX505DV
  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.:bvrFX505DV.303:bd09/19/2019:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505DV_FX505DV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505DV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF Gaming
  dmi.product.name: TUF Gaming FX505DV_FX505DV
  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/1871401/+subscriptions

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