date:20220201

Hi,

thanks for the fast reply! I have just installed it:

:~$ uname -a
Linux foo.bar 5.4.0-98-generic #111~lp1959665.1 SMP Tue Feb 1 19:50:04 UTC 2022 
x86_64 x86_64 x86_64 GNU/Linux

I mount all shares and start my tests (ncdu and a simple bash
testscript). With 97#110 it takes 30 seconds to crash a machine. ...with
the 98#111 the scripts work (i abort the test after 60 minutes). I dont
get a kernel panic with this kernel. Maybe Sebastian can confirm this ?

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

Title:
  linux-image-5.4.0-97.110 freezes by accessing cifs shares

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress

Bug description:
  Ubuntu 20.04 with kernel image 5.4.0-97.110 randomly freezes when we
  access cifs shares. The system needs a hard reset after the freeze.

  The previous kernel image (5.4.0-96.109) does not show this behavior.
  Multiple Ubuntu 20.04 systems running on kernel image 9.4.0-97.110 are
  affected on our sites.

  The cifs shares are accessed via autofs using Kerberos authentication.

  The following info is the only error message we could actively catch
  on a different system before the system was frozen:

  general protection fault:  [#3] SMP PTI
  CPU: 0 PID: 21294 Comm: automount Tainted: G  DOE 
5.4.0-97-generic #110-Ubuntu
  Hardware name: Dell Inc. Precision 7530/03RV2M, BIOS 1.14.4 10/21/2020
  RIP: 0010:kmem_cache_alloc_trace+0x8c/0x240
  Code: 08 65 4c 03 05 1d e8 f7 6e 49 83 78 10 00 4d 8b 38 0f 84 92 01 00 00 4d 
85 ff 0f 84 89 01 00 00 41 8b 41 20 49 8b 39 4c 01 f8 <48> 8b 18 48 89 c1 49 33 
99 70 01 00 00 4c 89 f8 48 0f c9 48 31 cb
  RSP: 0018:a6ca860f7ba0 EFLAGS: 00010286
  RAX: fdd44d7c219190e1 RBX:  RCX: 
  RDX: d558 RSI: 0cc0 RDI: 00035060
  RBP: a6ca860f7bd0 R08: 99233c035060 R09: 992338c079c0
  R10: 0001 R11: 0004 R12: 0cc0
  R13: 000b R14: 992338c079c0 R15: fdd44d7c219190e1
  FS:  7fdc24e29700() GS:99233c00() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7f15a80ee010 CR3: 0007e36b2006 CR4: 003606f0
  Call Trace:
   ? proc_self_get_link+0x70/0xd0
   proc_self_get_link+0x70/0xd0
   link_path_walk.part.0+0x478/0x550
   ? trailing_symlink+0x1d1/0x280
   path_openat+0xb7/0x290
   do_filp_open+0x91/0x100
   ? unuse_pde+0x30/0x30
   do_sys_open+0x17e/0x290
   __x64_sys_openat+0x20/0x30
   __orig_openat+0x71/0xc0 [eset_rtp]
   ? __switch_to_asm+0x40/0x70
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   ? __x64_sys_futex+0x13f/0x170
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   __x64_sys_ertp_openat+0x29/0x60 [eset_rtp]
   do_syscall_64+0x57/0x190
   entry_SYSCALL_64_after_hwframe+0x44/0xa9
  RIP: 0033:0x7fdc28a41f24
  Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 
48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 
44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44
  RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101
  RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24
   ? unuse_pde+0x30/0x30
   do_sys_open+0x17e/0x290
   __x64_sys_openat+0x20/0x30
   __orig_openat+0x71/0xc0 [eset_rtp]
   ? __switch_to_asm+0x40/0x70
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   ? __x64_sys_futex+0x13f/0x170
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   __x64_sys_ertp_openat+0x29/0x60 [eset_rtp]
   do_syscall_64+0x57/0x190
   entry_SYSCALL_64_after_hwframe+0x44/0xa9
  RIP: 0033:0x7fdc28a41f24
  Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 
48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 
44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44
  RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101
  RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24
  RDX: 0008 RSI: 564d4410a8c8 RDI: ff9c
  RBP: 564d4410a8c8 R08:  R09: 0001
  R10:  R11: 0293 R12: 0008
  R13: 564d4410e28a R14: 7fdc24e25b40 R15: 7fdc24e28fc0
  Modules linked in: cmac nls_utf8 cifs fscache libdes ccm vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) eset_rtp(OE) xt_conntrack xt_MASQUERADE 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter 
iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ip>
   snd_seq_midi coretemp snd_seq_midi_event snd_rawmidi kvm_intel snd_seq kvm 
dell_wmi snd_seq_device rapl dell_smbios snd_timer dcdbas intel_

[Kernel-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390

For the nvidia-settings upload, the new wording looks somewhat strange:

++   " in on-demand mode (only if nvidia version >= 
450; "
++   "otherwise, the behavior will approach to "
++   "performance mode). This option is applied 
after "
++   "a system restart.");

Perhaps better wording would be something along the lines of “(only
using nvidia driver versions >= 450. On earlier drivers this behaves the
same as performance mode)”?

Also: is this a translatable string?

Alternatively: how hard would it be to *detect* the driver version, as
ubuntu-drivers-common does, and grey out the option?

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

Title:
  on-demand mode doesn't work with nvidia-390

Status in OEM Priority Project:
  New
Status in nvidia-settings package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Committed
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in nvidia-settings source package in Impish:
  New
Status in ubuntu-drivers-common source package in Impish:
  Fix Committed
Status in nvidia-settings source package in Jammy:
  New
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

   * In any Ubuntu series, if user using a old GPU (which supported by
  nvidia-390 only) then issuing glxinfo will get "Error: couldn't find
  RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri
  driver correctly.

  [Test Plan]

   * install nvidia-390 on nvidia-390 supported system.
   * prime-select on-demand
   * reboot
   * glxinfo
   * after applying this patch, it will fall back to "ON" mode after reboot.

   * install nvidia-450 on nvidia-450 supported system.
   * prime-select on-demand
   * 

  [Where problems could occur]
   * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user 
stays in on-demand mode with 390 without problem, the after upgrading u-d-c and 
reboot. The mode will fall back to "ON" mode.
   * From my point of view, it's fine because nvidia-390 doesn't support RTD3. 
Thus, the nvidia will always stay in "Active" stage no matter which mode it is.
  * While there is no way to inform the user about this change, changing to the 
only supported default will avoid breaking GLX.

  ---

  The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu-
  drivers-common/+bug/1942789.

  It impacts Jammy and Impish so far.

  [Steps to reproduce]
  1. Find a GPU supports nvidia-390
  2. ubuntu-drivers install nvidia:390
  3. prime-select on-demand
  4. glxinfo

  [Expected result]
  Shows intel or nvidia drives monitor

  [Actual result]
  Error: couldn't find RGB GLX visual or fbconfig

  Since we are all agree "on-demand" mode as default mode.
  Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter 
RTD3).
  We could consider to make it as performance mode and leave a note on 
nvidia-settings.
  I'll prepare some test packages.

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


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

[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works

2022-02-01 Thread Daniel

All issues seem to be resolved for my Ryzen 7 4700U with
5.13.0-28-lowlatency too.

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

Title:
  amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22
  works

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  SRU Justification

  Impact:

  This does not occur with linux-image-5.13.0-22-generic, but does with 
linux-image-5.13.0-23-generic.
  On startup, I get about a 60 second hang, with the following in the kernel 
dmesg:
  Jan  4 15:26:36 inspiron-3505 kernel: [   34.160572] amdgpu :04:00.0: 
amdgp : failed to write reg 28b4 wait reg 28c6
  Jan  4 15:26:56 inspiron-3505 kernel: [   54.189055] amdgpu :04:00.0: 
amdgp : failed to write reg 1a6f4 wait reg 1a706
  Jan  4 15:27:16 inspiron-3505 kernel: [   74.329264] amdgpu :04:00.0: 
amdgp : failed to write reg 28b4 wait reg 28c6
  Jan  4 15:27:36 inspiron-3505 kernel: [   94.337904] amdgpu :04:00.0: 
amdgp : failed to write reg 1a6f4 wait reg 1a706
  I have the following GPU:
  04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Picass
  o (rev c2) (prog-if 00 [VGA controller])
  04:00.0 0300: 1002:15d8 (rev c2)
  (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.)

  I get a similar hang if I start firefox (when it's probing OpenGL
  contexts), and even with glxgears and glxinfo. Seems like anything
  that'd kick on a OpenGL context does it.  I had a freeze as well when
  I tried running firefox and glxgears both.  Along with odd BUG:
  messages logged (I have some in the attached log.)

  I was running with "iommu=pt", but did try with this removed, still
  got the errors (I think amdgpu driver uses the IOMMU even when it's
  set to IOMMU=pt though.).  See the attached log for some very odd
  "[Hardware Error]" messages that were logged on one test run.  I think
  this was when I tried to run firestorm (second life viewer) -- that
  had a large pause then opened to a black window.

  Per Google, I see there was a bug like this that turned up in kernel
  5.14.15 but fixed in 5.14.17.  See
  https://gitlab.freedesktop.org/drm/amd/-/issues/1770

  Thanks!
  --Henry

  Fix:
  upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is 
disabled in Picasso.")

  Patch was included in the Impish kernel in -proposed (5.13.0.24.24)
  from an upstream patch set. multiple confirmations the problem is
  resolved with the kernel in -proposed.

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


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

[Kernel-packages] [Bug 1953264] Re: Ubuntu 21.10 Bluetooth adapter not detected

2022-02-01 Thread Xiaodong

I'm having the same problem.

I'm also able to fix this issue by following this: shutting down and
unplugging my computer from the power for a while.

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

Title:
  Ubuntu 21.10 Bluetooth adapter not detected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth adapter not detected on machine running Ubuntu 21.10 with
  ASUS ROG B550-F.

  Upon clicking taskbar, bluetooth is shown as OFF. Expanding the
  bluetooth menu in the taskbar shows the option to turn OFF bluetooth.

  Going into the bluetooth settings, it says "No bluetooth found. Plugin
  a dongle to use bluetooth."

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-21-generic 5.13.0-21.21
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nabeel 2239 F pulseaudio
   /dev/snd/pcmC1D1p:   nabeel 2239 F...m pulseaudio
   /dev/snd/controlC0:  nabeel 2239 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Sun Dec  5 23:38:54 2021
  InstallationDate: Installed on 2021-09-06 (90 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: ASUS System Product Name
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-21-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-21-generic N/A
   linux-backports-modules-5.13.0-21-generic  N/A
   linux-firmware 1.201.1
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-10-15 (51 days ago)
  dmi.bios.date: 08/10/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2423
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B550-F GAMING (WI-FI)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2423:bd08/10/2021:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-FGAMING(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  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/1953264/+subscriptions


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

[Kernel-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390

Hello jeremyszu, or anyone else affected,

Accepted ubuntu-drivers-common into focal-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-drivers-
common/1:0.9.0~0.20.04.5 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: ubuntu-drivers-common (Ubuntu Focal)
   Status: New => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  on-demand mode doesn't work with nvidia-390

Status in OEM Priority Project:
  New
Status in nvidia-settings package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Committed
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in nvidia-settings source package in Impish:
  New
Status in ubuntu-drivers-common source package in Impish:
  Fix Committed
Status in nvidia-settings source package in Jammy:
  New
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

   * In any Ubuntu series, if user using a old GPU (which supported by
  nvidia-390 only) then issuing glxinfo will get "Error: couldn't find
  RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri
  driver correctly.

  [Test Plan]

   * install nvidia-390 on nvidia-390 supported system.
   * prime-select on-demand
   * reboot
   * glxinfo
   * after applying this patch, it will fall back to "ON" mode after reboot.

   * install nvidia-450 on nvidia-450 supported system.
   * prime-select on-demand
   * 

  [Where problems could occur]
   * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user 
stays in on-demand mode with 390 without problem, the after upgrading u-d-c and 
reboot. The mode will fall back to "ON" mode.
   * From my point of view, it's fine because nvidia-390 doesn't support RTD3. 
Thus, the nvidia will always stay in "Active" stage no matter which mode it is.
  * While there is no way to inform the user about this change, changing to the 
only supported default will avoid breaking GLX.

  ---

  The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu-
  drivers-common/+bug/1942789.

  It impacts Jammy and Impish so far.

  [Steps to reproduce]
  1. Find a GPU supports nvidia-390
  2. ubuntu-drivers install nvidia:390
  3. prime-select on-demand
  4. glxinfo

  [Expected result]
  Shows intel or nvidia drives monitor

  [Actual result]
  Error: couldn't find RGB GLX visual or fbconfig

  Since we are all agree "on-demand" mode as default mode.
  Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter 
RTD3).
  We could consider to make it as performance mode and leave a note on 
nvidia-settings.
  I'll prepare some test packages.

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


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

[Kernel-packages] [Bug 1946507] Re: Ubuntu Install Setup Freeze

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

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

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

Title:
  Ubuntu Install Setup Freeze

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hello,

  While trying to Install Ubuntu 21.10 , the setup freeze after clicking
  continue on Step 4 where it asks if you wish to install Updates , and
  i have selected Normal Installation when i click continue then setup
  freeze so im not able to click any other button just QUIT button is
  working , other buttons are grayed out and not clickable , i have
  tried many methods since 2 days been trying nomodeset acpi=off and
  other but nothing works for me , i need help .

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity 21.10.6 [modified: 
lib/partman/automatically_partition/question]
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  8 15:56:06 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset 
file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211006)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390

I've accepted this, but have amended the test plan to try and ensure
this doesn't change the behaviour on the -450 series drivers.

I'm not entirely sure what the "" check
should be. @Alberto, @Jeremy: Could you please replace that part of the
test-plan with the steps required to check that on-demand still works
for -450?

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

Title:
  on-demand mode doesn't work with nvidia-390

Status in OEM Priority Project:
  New
Status in nvidia-settings package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Committed
Status in nvidia-settings source package in Impish:
  New
Status in ubuntu-drivers-common source package in Impish:
  Fix Committed
Status in nvidia-settings source package in Jammy:
  New
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

   * In any Ubuntu series, if user using a old GPU (which supported by
  nvidia-390 only) then issuing glxinfo will get "Error: couldn't find
  RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri
  driver correctly.

  [Test Plan]

   * install nvidia-390 on nvidia-390 supported system.
   * prime-select on-demand
   * reboot
   * glxinfo
   * after applying this patch, it will fall back to "ON" mode after reboot.

   * install nvidia-450 on nvidia-450 supported system.
   * prime-select on-demand
   * 

  [Where problems could occur]
   * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user 
stays in on-demand mode with 390 without problem, the after upgrading u-d-c and 
reboot. The mode will fall back to "ON" mode.
   * From my point of view, it's fine because nvidia-390 doesn't support RTD3. 
Thus, the nvidia will always stay in "Active" stage no matter which mode it is.
  * While there is no way to inform the user about this change, changing to the 
only supported default will avoid breaking GLX.

  ---

  The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu-
  drivers-common/+bug/1942789.

  It impacts Jammy and Impish so far.

  [Steps to reproduce]
  1. Find a GPU supports nvidia-390
  2. ubuntu-drivers install nvidia:390
  3. prime-select on-demand
  4. glxinfo

  [Expected result]
  Shows intel or nvidia drives monitor

  [Actual result]
  Error: couldn't find RGB GLX visual or fbconfig

  Since we are all agree "on-demand" mode as default mode.
  Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter 
RTD3).
  We could consider to make it as performance mode and leave a note on 
nvidia-settings.
  I'll prepare some test packages.

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


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

[Kernel-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390

Hello jeremyszu, or anyone else affected,

Accepted ubuntu-drivers-common into impish-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-drivers-common/1:0.9.2.3 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: ubuntu-drivers-common (Ubuntu Impish)
   Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-impish

** Description changed:

  [Impact]
  
   * In any Ubuntu series, if user using a old GPU (which supported by
  nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB
  GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver
  correctly.
  
  [Test Plan]
  
   * install nvidia-390 on nvidia-390 supported system.
   * prime-select on-demand
   * reboot
   * glxinfo
   * after applying this patch, it will fall back to "ON" mode after reboot.
  
+  * install nvidia-450 on nvidia-450 supported system.
+  * prime-select on-demand
+  * 
+ 
  [Where problems could occur]
   * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user 
stays in on-demand mode with 390 without problem, the after upgrading u-d-c and 
reboot. The mode will fall back to "ON" mode.
   * From my point of view, it's fine because nvidia-390 doesn't support RTD3. 
Thus, the nvidia will always stay in "Active" stage no matter which mode it is.
  * While there is no way to inform the user about this change, changing to the 
only supported default will avoid breaking GLX.
- 
  
  ---
  
  The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu-
  drivers-common/+bug/1942789.
  
  It impacts Jammy and Impish so far.
  
  [Steps to reproduce]
  1. Find a GPU supports nvidia-390
  2. ubuntu-drivers install nvidia:390
  3. prime-select on-demand
  4. glxinfo
  
  [Expected result]
  Shows intel or nvidia drives monitor
  
  [Actual result]
  Error: couldn't find RGB GLX visual or fbconfig
  
  Since we are all agree "on-demand" mode as default mode.
  Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter 
RTD3).
  We could consider to make it as performance mode and leave a note on 
nvidia-settings.
  I'll prepare some test packages.

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

Title:
  on-demand mode doesn't work with nvidia-390

Status in OEM Priority Project:
  New
Status in nvidia-settings package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Committed
Status in nvidia-settings source package in Impish:
  New
Status in ubuntu-drivers-common source package in Impish:
  Fix Committed
Status in nvidia-settings source package in Jammy:
  New
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

   * In any Ubuntu series, if user using a old GPU (which supported by
  nvidia-390 only) then issuing glxinfo will get "Error: couldn't find
  RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri
  driver correctly.

  [Test Plan]

   * install nvidia-390 on nvidia-390 supported system.
   * prime-select on-demand
   * reboot
   * glxinfo
   * after applying this patch, it will fall back to "ON" mode after reboot.

   * install nvidia-450 on nvidia-450 supported system.
   * prime-select on-demand
   * 

  [Where problems could occur]
   * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user 
stays in on-demand mode with 390 without problem, the after upgrading u-d-c and 
reboot. The mode will fall back to "ON" mode.
   * From my point of view, it's fine because nvidia-390 doesn't support RTD3. 
Thus, the nvidia will always stay in "Active" stage no matter which mode it is.
  * While there is no way to inform the user about this change, changing to the 
only supported default will avoid breaking GLX.

  ---

  The regressio

[Kernel-packages] [Bug 1959695] Re: [amdgpu] Black screen with flashing horizontal lines

2022-02-01 Thread Daniel van Vugt

I wonder if this is related to another 5.13 kernel issue: bug 1958591

** Summary changed:

- Xorg crash
+ [amdgpu] Black screen with flashing horizontal lines

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

** Tags added: amdgpu

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

Title:
  [amdgpu] Black screen with flashing horizontal lines

Status in linux package in Ubuntu:
  New

Bug description:
  Una disculpa si me llego a equivocar, soy un usuario principiante.

  Desde que instale "Ubuntu" (tanto en la versión LTS como en la actual)
  la pantalla llega a tener un problema, se pone en negro y tiene lineas
  que están parpadeando como si fueran guiones (___---) de color verde o
  blanco tanto en el borde superior e inferior, una vez se pasa eso no
  vuelve a dar imagen sin importar cuanto tiempo pase o haga cualquier
  otra cosa y dejando como única opción el apagar el equipo de forma
  forzada con el botón.

  Hay varios puntos con respecto a esto:

  -Esto sucede desde que se termina de instalar, ya sea con la instalación 
normal o la mínima e incluso sin mover ninguna configuración.
  -Sucede después de iniciar el sistema e ingresar la contraseña de usuario, 
debo de forzar el apagado varias veces e iniciar sesión hasta que funciona, 
ademas no hay ni un numero de veces que deba hacerlo para que funcione o algo 
en especifico, parece que es completamente aleatorio si funciona o no.
  -Sucede cuando el equipo entra en suspencion o cambio de usuario.
  -En el momento de iniciar el sistema después de pasar el GRUB y antes de la 
pantalla que muestra los usuarios, en la pantalla que muestra la imagen de 
Lenovo, no se pierde la imagen pero por un segundo muestra una linea horizontal 
blanca aprox. a la altura de la rueda de carga.

  -Adicional a esto aunque desconozco si es el mismo problema, al
  momento de apagar el equipo, el sistema se cierra, lleva a la pantalla
  negra con el logo de "Ubuntu", se apaga la pantalla, etc. pero no
  corta la energía, el ventilador sigue funcionando y el equipo sigue
  encendido. De igual forma esto no cambia hasta que se apaga
  forzosamente con el botón.

  Eh intentado varias cosas sin exito dentro de las cuales están:

  -Instalar los drivers Radeon descargados directamente de la pagina de AMD
  -Instalar Xorg-edgers con el comando "sudo add-apt-repository 
ppa:xorg-edgers/ppa"

  -Respecto al ultimo problema intente solucionarlo con
  "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force apm=power_off""

  Nada de lo anterior funciono.

  Agradezco la atención.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
  Uname: Linux 5.13.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  1 10:40:09 2022
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev e2) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Stoney [Radeon R2/R3/R4/R5 Graphics] [17aa:3f1a]
  InstallationDate: Installed on 2022-01-28 (4 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 81ST
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic 
root=UUID=31c16c62-8a32-4efd-bccc-3e10e3b1b103 ro quiet splash acpi=force 
apm=power_off vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2021
  dmi.bios.release: 1.25
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AYCN25WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T31540WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S145-14AST
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrAYCN25WW:bd05/14/2021:br1.25:efr1.25:svnLENOVO:pn81ST:pvrLenovoIdeaPadS145-14AST:rvnLENOVO:rnLNVNB161216:rvrSDK0T31540WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-14AST:skuLENOVO_MT_81ST_BU_idea_FM_IdeaPadS145-14AST:
  dmi.product.family: IdeaPad S145-14AST
  dmi.product.name: 81ST
  dmi.product.sku: LENOVO_MT_81ST_BU_idea_FM_IdeaPad S145-14AST
  dmi.product.version: Lenovo IdeaPad S145-14AST
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubunt

[Kernel-packages] [Bug 1959695] [NEW] [amdgpu] Black screen with flashing horizontal lines

You have been subscribed to a public bug:

Una disculpa si me llego a equivocar, soy un usuario principiante.

Desde que instale "Ubuntu" (tanto en la versión LTS como en la actual)
la pantalla llega a tener un problema, se pone en negro y tiene lineas
que están parpadeando como si fueran guiones (___---) de color verde o
blanco tanto en el borde superior e inferior, una vez se pasa eso no
vuelve a dar imagen sin importar cuanto tiempo pase o haga cualquier
otra cosa y dejando como única opción el apagar el equipo de forma
forzada con el botón.

Hay varios puntos con respecto a esto:

-Esto sucede desde que se termina de instalar, ya sea con la instalación normal 
o la mínima e incluso sin mover ninguna configuración.
-Sucede después de iniciar el sistema e ingresar la contraseña de usuario, debo 
de forzar el apagado varias veces e iniciar sesión hasta que funciona, ademas 
no hay ni un numero de veces que deba hacerlo para que funcione o algo en 
especifico, parece que es completamente aleatorio si funciona o no.
-Sucede cuando el equipo entra en suspencion o cambio de usuario.
-En el momento de iniciar el sistema después de pasar el GRUB y antes de la 
pantalla que muestra los usuarios, en la pantalla que muestra la imagen de 
Lenovo, no se pierde la imagen pero por un segundo muestra una linea horizontal 
blanca aprox. a la altura de la rueda de carga.

-Adicional a esto aunque desconozco si es el mismo problema, al momento
de apagar el equipo, el sistema se cierra, lleva a la pantalla negra con
el logo de "Ubuntu", se apaga la pantalla, etc. pero no corta la
energía, el ventilador sigue funcionando y el equipo sigue encendido. De
igual forma esto no cambia hasta que se apaga forzosamente con el botón.

Eh intentado varias cosas sin exito dentro de las cuales están:

-Instalar los drivers Radeon descargados directamente de la pagina de AMD
-Instalar Xorg-edgers con el comando "sudo add-apt-repository 
ppa:xorg-edgers/ppa"

-Respecto al ultimo problema intente solucionarlo con
"GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force apm=power_off""

Nada de lo anterior funciono.

Agradezco la atención.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xorg 1:7.7+22ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
Uname: Linux 5.13.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb  1 10:40:09 2022
DistUpgraded: Fresh install
DistroCodename: impish
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev e2) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Stoney [Radeon R2/R3/R4/R5 Graphics] [17aa:3f1a]
InstallationDate: Installed on 2022-01-28 (4 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 81ST
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic 
root=UUID=31c16c62-8a32-4efd-bccc-3e10e3b1b103 ro quiet splash acpi=force 
apm=power_off vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/14/2021
dmi.bios.release: 1.25
dmi.bios.vendor: LENOVO
dmi.bios.version: AYCN25WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T31540WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad S145-14AST
dmi.ec.firmware.release: 1.25
dmi.modalias: 
dmi:bvnLENOVO:bvrAYCN25WW:bd05/14/2021:br1.25:efr1.25:svnLENOVO:pn81ST:pvrLenovoIdeaPadS145-14AST:rvnLENOVO:rnLNVNB161216:rvrSDK0T31540WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-14AST:skuLENOVO_MT_81ST_BU_idea_FM_IdeaPadS145-14AST:
dmi.product.family: IdeaPad S145-14AST
dmi.product.name: 81ST
dmi.product.sku: LENOVO_MT_81ST_BU_idea_FM_IdeaPad S145-14AST
dmi.product.version: Lenovo IdeaPad S145-14AST
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1

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


** Tags: amd64 apport-bug crash impish ubuntu wayland-session
-- 
[amdgpu] Black screen with flashing horizontal lines
https://bugs.launchpad.net/bugs/1959695
You received this bug notification because you are a member of Kernel Packages, 
which

[Kernel-packages] [Bug 1950720] Re: GSYNC bug regression in 495.44 Ubuntu 21.10

2022-02-01 Thread Daniel van Vugt

berglh, can you please describe the problem/symptoms in the Bug
Description? I can't seem to find any description of the problem itself.

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

Title:
GSYNC bug regression in 495.44 Ubuntu 21.10

Status in nvidia-graphics-drivers-470 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-495 package in Ubuntu:
Confirmed

Bug description:
Similar to bug https://launchpad.net/bugs/1950665, the GSYNC
regression bug has returned in 495.44 on Ubuntu 21.10. I have tried
the standard kernel and 5.14.1 and 5.14.17, but they are all
experiencing the same bug again.

Hardware is:
- NVIDIA GeForce RTX 2080 Super
- Dell 27" S2721DGF G-Sync Compatible monitor
- High quality DisplayPort cable (This was replaced previously under
suspicion)

This issue happens at all refresh rates: 60 Hz, 120 Hz, 144 Hz and 165
Hz.

Prior to upgrading to Ubuntu 21.10, I had upgraded to 495.44 on Ubuntu
21.04 and kernel 5.14.1, and this problem was not present.

I then upgraded to Ubuntu 21.10, and the problem didn't seem to be
present, but as of today I've noticed again.

I'm not sure what the cause is, but I have tried full driver purges,
returned to 470.82, went back to the standard kernel for 21.10
(5.13.0-21-generic), 5.14.1 and 5.14.17, and the problem continues to
occur when any GPU accelerated application starts, in some cases when
switching between applications (i.e. alt tabbing out of a game). A
second or so of no signal occurs as it re-syncs.

I am unsure if X11 has been updated in this time, I know there was
work happening on GBM support, wondering if X11 has switched to using
this instead of the EGL Streams direct approach that was used
previously. Either-way, I'm still running X11 in all of these tests.

Let me know if there are any tests you'd like me to try.

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

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

[Kernel-packages] [Bug 1954676] Re: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 / gcc-11 PLT regression on s390x

2022-02-01 Thread Ilya Leoshkevich

The fix is now in v5.15 stable branch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.15.y&id=2025d5cb381e4bf8fecc78015da6ef6168f9ace8

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

Title:
  jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >=
  11.2.0-10ubuntu1 / gcc-11 PLT regression on s390x

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in gcc-11 package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  New
Status in gcc-11 source package in Jammy:
  Fix Released
Status in zfs-linux source package in Jammy:
  New

Bug description:
  [Impact]

  Installing zfs-dkms seems to trigger a soft lockup issue as soon as
  zfs.ko is loaded. When the soft lockup happens the system isn't
  reachable anymore via ssh and on the console we can see some exlicit
  rcu stall warnings.

  This seems to happen only when zfs is compile with gcc >=
  11.2.0-10ubuntu1. Downgrading gcc to previous versions doesn't show
  the problem and zfs is working just fine.

  [Test case]

  On s390x install the latest 5.15 Jammy kernel and run:
  apt install zfs-dkms

  [Fix]

  Temporary workaround is to build zfs with gcc-10 on s390x.

  [Regression potential]

  Building a kernel module with a different compiler is never 100% safe,
  we may experience potential crashes / panics if the ABI is not
  compatible. Moreover, if we build zfs with gcc-10 we are going to lose
  some of the performance benefits provided by gcc-11.

  However these regressions are limited to zfs on s390x and without this
  change zfs is broken anyway on this architecture.

  [Further analysis]

  @IBM

  Issue report to zfs upstream at
  https://github.com/openzfs/zfs/issues/12942

  Reverting
  
https://gcc.gnu.org/git/?p=gcc.git;a=patch;h=2335aa8771acd06b082d3e15d9f21ae0a802afd7
  appears to make everything work, the compiled kernel and zfs.ko are
  loadable/unloadable once again.

  Please bring this issue to the attention of  Ilya Leoshkevich

  Potentially this means we may have missbuilt userspace binaries in the
  archive for s390x.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1954676/+subscriptions


-- 
Mailing list: https://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 1959702] Re: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb

2022-02-01 Thread Harry Coin

Yup, those failures were to do with an old radeon chipset on an ancient 
server.

On 2/1/22 17:33, Seth Arnold wrote:
> Sounds good, thanks:
>
>   [0.00] Linux version 5.11.0-49-generic (buildd@lcy02-amd64-054)
> (gcc (Ubuntu 10.3.0-1ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu)
> 2.36.1) #55-Ubuntu SMP Wed Jan 12 17:36:34 UTC 2022 (Ubuntu
> 5.11.0-49.55-generic 5.11.22)
>
> btw, there were a bunch of memory allocation failures in the dmesg, in
> case they weren't obvious.
>
> ** Attachment removed: "apport.linux-image-5.11.0-49-generic.rw5aqx7x.apport"
> 
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959702/+attachment/5558647/+files/apport.linux-image-5.11.0-49-generic.rw5aqx7x.apport
>
> ** Information type changed from Private Security to Public Security
>

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

Title:
  Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry
  to mdb

Status in linux package in Ubuntu:
  New

Bug description:
  Starting at the end: I believe as the bug presently requires each of
  the host's bridge ports to be ipv6 addressable to enable ipv6 to
  function in the guest, and most admins won't think to add special
  entries into their host's nftables.conf to allow for it 'because who
  knew?' it represents what you might call a 'passive security
  vulnerability'.

  A recent kernel upgrade has broken ipv6/ip6 ndp in a host/kvm setup
  using a bridge on the host and vlans for some guests.  I've tracked
  the problem to a failure of the mcast code to add entries to the
  host's mdb table.  Manually adding the entries to the mdb on the
  bridge corrects the problem.

  It's very easy to demonstrate the bug in an all ubuntu setup.

  1. On an ubuntu host, create two vms, I used libvirt, as set up below.

  2. On the host, create a bridge and vlan with two ports, each with the
  chosen vlan as PVID and egress untagged. Assign those ports one each
  to the guests as the interface, use e1000. Be sure to NOT
  autoconfigure the host side of the bridge ports with any ip4 or ip6
  address (including fe80::), it's just an avoidable security risk.  We
  don't want to allow the host any sort of ip access / exposure to the
  vlan.  In other words, treat the host's bridge ports as if a 'real
  off-host switch' without expectation of making each bridge's port
  being ip6 addressable on the bridge itself.   (FWIW: Worth checking if
  the vlan is left tagged and not pvid, and the vlan is decoded in the
  guest as a separate interface, does the problem go away? It imposes
  the burden of vlan management awareness to the guest and so is not
  acceptable as a solution.)

  3. On the host, assign a physical NIC to the bridge and the vlan to
  the nic.  The egress is tagged for the chosen vlan and not PVID.
  Optionally set up an off-host gateway for the vlan, but it isn't
  necessary to show the bug.

  4. On each guest, manually assign a unique ip4 and ip6 address on the
  same subnet (you'll see though dhcp4 could work if there was an off-
  host router providing related services, the bug prevents dhcp6 from
  working).

  5. On one vm, ping the other.  Notice ip4 pings work, ip6 pings do
  not.

  6. Manually add the fe02::ffxx: entries for each vm to the vlan to
  the host bridge's multicast table. Use 'temp' if you're quick enough,
  otherwise perm.

  7. Notice pings between the guests now work on ip6 and ipv4.

  Using tcpdump and watching icmp6 traffic, you'll notice the packets
  making it across the various bridge ports the moment you manually add
  the appropriate fe02::ff... multicast address to the mdb table.
  Beware a false sense of security: Once the ndp completes and the link
  addresses are in the fdb, it can 'seem like' everything is fine until
  the fdb times out and the required mdb entry again must be used to
  allow ndp to refresh the address.

  Setting mcast_querier doesn't help.  Perhaps previous kernels turned
  off the multicast snooping by default and just flooded all the bridge
  ports with all multicast traffic so this bug was avoided.

  It's my hunch the reason there hasn't been more complaint about this
  is it takes an extra step to not autoconfigure the vm ports with
  fe80:: link local addresses on the host.  I believe the existence of
  the fe80 address on the host ports engages ndp code on the host to
  load the mdb as if preparing for the host's side of the bridge to
  participate in ip4 and ip6 higher layer traffic, but that's a 'bad
  hack that happens to work' -- it shouldn't be a requirement that each
  host vlan port have an ip6 address, after all it didn't need an IP4
  address

  I've attached a linux-bug for you, but it's probably mostly unrelated
  info.

  I believe as the bug presently requires each of the host's bridge
  ports to be ipv6 addressable to enable ipv6 to function in the guest

[Kernel-packages] [Bug 1959702] Re: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb

2022-02-01 Thread Seth Arnold

Sounds good, thanks:

[0.00] Linux version 5.11.0-49-generic (buildd@lcy02-amd64-054)
(gcc (Ubuntu 10.3.0-1ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu)
2.36.1) #55-Ubuntu SMP Wed Jan 12 17:36:34 UTC 2022 (Ubuntu
5.11.0-49.55-generic 5.11.22)

btw, there were a bunch of memory allocation failures in the dmesg, in
case they weren't obvious.

** Attachment removed: "apport.linux-image-5.11.0-49-generic.rw5aqx7x.apport"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959702/+attachment/5558647/+files/apport.linux-image-5.11.0-49-generic.rw5aqx7x.apport

** Information type changed from Private Security to Public Security

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

Title:
Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry
to mdb

Status in linux package in Ubuntu:
New

Bug description:
Starting at the end: I believe as the bug presently requires each of
the host's bridge ports to be ipv6 addressable to enable ipv6 to
function in the guest, and most admins won't think to add special
entries into their host's nftables.conf to allow for it 'because who
knew?' it represents what you might call a 'passive security
vulnerability'.

A recent kernel upgrade has broken ipv6/ip6 ndp in a host/kvm setup
using a bridge on the host and vlans for some guests. I've tracked
the problem to a failure of the mcast code to add entries to the
host's mdb table. Manually adding the entries to the mdb on the
bridge corrects the problem.

It's very easy to demonstrate the bug in an all ubuntu setup.

1. On an ubuntu host, create two vms, I used libvirt, as set up below.

2. On the host, create a bridge and vlan with two ports, each with the
chosen vlan as PVID and egress untagged. Assign those ports one each
to the guests as the interface, use e1000. Be sure to NOT
autoconfigure the host side of the bridge ports with any ip4 or ip6
address (including fe80::), it's just an avoidable security risk. We
don't want to allow the host any sort of ip access / exposure to the
vlan. In other words, treat the host's bridge ports as if a 'real
off-host switch' without expectation of making each bridge's port
being ip6 addressable on the bridge itself. (FWIW: Worth checking if
the vlan is left tagged and not pvid, and the vlan is decoded in the
guest as a separate interface, does the problem go away? It imposes
the burden of vlan management awareness to the guest and so is not
acceptable as a solution.)

3. On the host, assign a physical NIC to the bridge and the vlan to
the nic. The egress is tagged for the chosen vlan and not PVID.
Optionally set up an off-host gateway for the vlan, but it isn't
necessary to show the bug.

4. On each guest, manually assign a unique ip4 and ip6 address on the
same subnet (you'll see though dhcp4 could work if there was an off-
host router providing related services, the bug prevents dhcp6 from
working).

5. On one vm, ping the other. Notice ip4 pings work, ip6 pings do
not.

6. Manually add the fe02::ffxx: entries for each vm to the vlan to
the host bridge's multicast table. Use 'temp' if you're quick enough,
otherwise perm.

7. Notice pings between the guests now work on ip6 and ipv4.

Using tcpdump and watching icmp6 traffic, you'll notice the packets
making it across the various bridge ports the moment you manually add
the appropriate fe02::ff... multicast address to the mdb table.
Beware a false sense of security: Once the ndp completes and the link
addresses are in the fdb, it can 'seem like' everything is fine until
the fdb times out and the required mdb entry again must be used to
allow ndp to refresh the address.

Setting mcast_querier doesn't help. Perhaps previous kernels turned
off the multicast snooping by default and just flooded all the bridge
ports with all multicast traffic so this bug was avoided.

It's my hunch the reason there hasn't been more complaint about this
is it takes an extra step to not autoconfigure the vm ports with
fe80:: link local addresses on the host. I believe the existence of
the fe80 address on the host ports engages ndp code on the host to
load the mdb as if preparing for the host's side of the bridge to
participate in ip4 and ip6 higher layer traffic, but that's a 'bad
hack that happens to work' -- it shouldn't be a requirement that each
host vlan port have an ip6 address, after all it didn't need an IP4
address

I've attached a linux-bug for you, but it's probably mostly unrelated
info.

I believe as the bug presently requires each of the host's bridge
ports to be ipv6 addressable to enable ipv6 to function in the guest,
and most admins won't think to add special entries into their host's
nftables.conf to allow for it 'because who knew?' it represents what
y

[Kernel-packages] [Bug 1954692] Re: Reconsider compressed kernels on arm64

2022-02-01 Thread dann frazier

** Changed in: maas-images
   Status: New => In Progress

** Changed in: maas-images
 Assignee: (unassigned) => dann frazier (dannf)

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

Title:
  Reconsider compressed kernels on arm64

Status in maas-images:
  In Progress
Status in flash-kernel package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Compressed kernel images were introduced in bug 1384955 to work around
  some limits on old u-boot systems. This in turn broke grub-check-
  signatures, meaning that while cloud images booted in secure boot, you
  could not upgrade grub or install new kernels on secure systems as
  that would trigger a "you have unsigned kernels" message. grub 2.06
  also fails to boot the images, as it verifies before decompressing.

  Work to fix grub to handle such images on arm64 for backward
  compatibility is tracked in bug 1954683. This bug is to reconsider
  whether the change is still necessary or could be removed in 22.04
  such that we can have proper UEFI executables again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/1954692/+subscriptions


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

[Kernel-packages] [Bug 1954692] Re: Reconsider compressed kernels on arm64

** Merge proposal linked:
   https://code.launchpad.net/~dannf/maas-images/+git/maas-images/+merge/414929

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

Title:
  Reconsider compressed kernels on arm64

Status in maas-images:
  In Progress
Status in flash-kernel package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Compressed kernel images were introduced in bug 1384955 to work around
  some limits on old u-boot systems. This in turn broke grub-check-
  signatures, meaning that while cloud images booted in secure boot, you
  could not upgrade grub or install new kernels on secure systems as
  that would trigger a "you have unsigned kernels" message. grub 2.06
  also fails to boot the images, as it verifies before decompressing.

  Work to fix grub to handle such images on arm64 for backward
  compatibility is tracked in bug 1954683. This bug is to reconsider
  whether the change is still necessary or could be removed in 22.04
  such that we can have proper UEFI executables again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/1954692/+subscriptions


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

[Kernel-packages] [Bug 1959728] [NEW] trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

2022-02-01 Thread Roland Dreier

Public bug reported:

On my X1 Yoga Titanium (which has a fancy new "Sensel" trackpad with
haptic response to clicks), the trackpad stops working after a
suspend/resume cycle, although the red trackpoint continues to work fine
for controlling the pointer.  I believe this system is using S0i3 for
suspend, in case that's relevant.

If I boot from power off, then the trackpad works fine in both the pre-
boot BIOS and in Ubuntu 22.04 (prerelease), including haptic response to
clicks.  After a suspend/resume cycle, the trackpad stops responding,
although a lot of swiping/pressing will occasionally produce a button
press event.  This state persists even if I reboot out of Linux (without
a power cycle) - for example the trackpad no longer works for the pre-
boot BIOS configuration screen, until a full power cycle (which fixes
the trackpad).

Possibly relevant, the trackpad seems to be this device to the kernel:

[2.016917] input: SNSL0001:00 2C2F:0006 Mouse as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input6
[2.016964] input: SNSL0001:00 2C2F:0006 Touchpad as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input7
[2.017027] hid-generic 0018:2C2F:0006.0001: input,hidraw0: I2C HID v1.00 
Mouse [SNSL0001:00 2C2F:0006] on i2c-SNSL0001:00

and the last kernel messages before suspend are:

[  305.216189] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
[  305.217435] printk: Suspending console(s) (use no_console_suspend to debug)
[  305.274332] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort: lost 
arbitration
[  306.030947] i2c_hid_acpi i2c-SNSL0001:00: failed to set a report to device.
[  306.616463] ACPI: EC: interrupt blocked
[  331.551118] ACPI: EC: interrupt unblocked

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-generic (not installed)
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu76
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bina   1543 F pipewire
  bina   1544 F pipewire-media-
  bina   1545 F pulseaudio
 /dev/snd/seq:bina   1543 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb  1 14:54:14 2022
InstallationDate: Installed on 2022-02-01 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
MachineType: LENOVO 20QA000EUS
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.15.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-18-generic N/A
 linux-backports-modules-5.15.0-18-generic  N/A
 linux-firmware 20220124.git0c6a7b3b-0ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/30/2021
dmi.bios.release: 1.18
dmi.bios.vendor: LENOVO
dmi.bios.version: N2MET53W (1.18 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QA000EUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.11
dmi.modalias: 
dmi:bvnLENOVO:bvrN2MET53W(1.18):bd09/30/2021:br1.18:efr1.11:svnLENOVO:pn20QA000EUS:pvrThinkPadX1TitaniumGen1:rvnLENOVO:rn20QA000EUS:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20QA_BU_Think_FM_ThinkPadX1TitaniumGen1:
dmi.product.family: ThinkPad X1 Titanium Gen 1
dmi.product.name: 20QA000EUS
dmi.product.sku: LENOVO_MT_20QA_BU_Think_FM_ThinkPad X1 Titanium Gen 1
dmi.product.version: ThinkPad X1 Titanium Gen 1
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

Status in linux package in Ubuntu:
  New

Bug description:
  On my X1 Yoga Titanium (which has a fancy new "Sensel" trackpad with
  haptic response to clicks), the trackpad stops working after a
  suspend/resume cycle, although the red trackpoint continues to work
  fine for controlling the pointer.  I believe this system is using S0i3
  for suspend, in case that's relevant.

  If I boot from power off, then the trackpad works fine in both the
  pre-boot BIOS and in Ubuntu 22.04 (prerelease), including haptic
  response to clicks.  After a suspend/resume cycle, the trackpad stops
  responding, although a lot of swiping/pressing will occasionally
  produ

[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze

2022-02-01 Thread Paul Szabo

Released "fix" did not solve issue

** Changed in: linux (Ubuntu Impish)
   Status: Fix Released => Confirmed

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

Title:
  rtw88_8821ce causes freeze

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.13 source package in Focal:
  Confirmed
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Confirmed
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Confirmed
Status in linux-oem-5.13 source package in Jammy:
  Invalid
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card.
  Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic 
kernel,and it works "well" for both WiFi and Bluetooth.
  However, this module (driver) causes frequent freezes, randomly but usually 
within a few minutes of running (thus very soon after boot): screen display 
remains frozen, no response to either keyboard or mouse input. All I can do is 
to hold the power button to power off, then reboot.

  After reboot, I do not see any crash reports, nor logs about the freeze.
  Please let me know if I should try to collect some info, and how.

  For now I use the DKMS module/driver from
    https://github.com/tomaspinho/rtl8821ce
  (having blacklisted rtw88_8821ce), and it seems to work perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-16-generic 5.11.0-16.17
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  psz1189 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  8 16:58:19 2021
  InstallationDate: Installed on 2021-04-23 (14 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  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 2.0 Camera
   Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio
   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: Protempo Ltd L116HTN6SPW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2020
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  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.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Notebook
  dmi.product.name: L116HTN6SPW
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Protempo Ltd

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


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

[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze

2022-02-01 Thread Paul Szabo

Released "fix" did not solve issue

** Changed in: linux-oem-5.13 (Ubuntu Focal)
   Status: Fix Released => Confirmed

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

Title:
  rtw88_8821ce causes freeze

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.13 source package in Focal:
  Confirmed
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Confirmed
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Confirmed
Status in linux-oem-5.13 source package in Jammy:
  Invalid
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card.
  Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic 
kernel,and it works "well" for both WiFi and Bluetooth.
  However, this module (driver) causes frequent freezes, randomly but usually 
within a few minutes of running (thus very soon after boot): screen display 
remains frozen, no response to either keyboard or mouse input. All I can do is 
to hold the power button to power off, then reboot.

  After reboot, I do not see any crash reports, nor logs about the freeze.
  Please let me know if I should try to collect some info, and how.

  For now I use the DKMS module/driver from
    https://github.com/tomaspinho/rtl8821ce
  (having blacklisted rtw88_8821ce), and it seems to work perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-16-generic 5.11.0-16.17
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  psz1189 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  8 16:58:19 2021
  InstallationDate: Installed on 2021-04-23 (14 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  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 2.0 Camera
   Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio
   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: Protempo Ltd L116HTN6SPW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2020
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  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.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Notebook
  dmi.product.name: L116HTN6SPW
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Protempo Ltd

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


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

[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze

2022-02-01 Thread Paul Szabo

Released "fix" did not solve issue

** Changed in: linux (Ubuntu Jammy)
   Status: Fix Released => Confirmed

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

Title:
  rtw88_8821ce causes freeze

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.13 source package in Focal:
  Confirmed
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Confirmed
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Confirmed
Status in linux-oem-5.13 source package in Jammy:
  Invalid
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card.
  Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic 
kernel,and it works "well" for both WiFi and Bluetooth.
  However, this module (driver) causes frequent freezes, randomly but usually 
within a few minutes of running (thus very soon after boot): screen display 
remains frozen, no response to either keyboard or mouse input. All I can do is 
to hold the power button to power off, then reboot.

  After reboot, I do not see any crash reports, nor logs about the freeze.
  Please let me know if I should try to collect some info, and how.

  For now I use the DKMS module/driver from
    https://github.com/tomaspinho/rtl8821ce
  (having blacklisted rtw88_8821ce), and it seems to work perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-16-generic 5.11.0-16.17
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  psz1189 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  8 16:58:19 2021
  InstallationDate: Installed on 2021-04-23 (14 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  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 2.0 Camera
   Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio
   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: Protempo Ltd L116HTN6SPW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2020
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  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.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Notebook
  dmi.product.name: L116HTN6SPW
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Protempo Ltd

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


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

[Kernel-packages] [Bug 1959721] [NEW] unchecked MSR access error: WRMSR to 0xd10

2022-02-01 Thread Bram Stolk

Public bug reported:

When booting 5.13.0-28-generic on a fully up-to-date Ubuntu 21.10 I get:

[0.526209] unchecked MSR access error: WRMSR to 0xd10 (tried to write 
0x) at rIP: 0xb8880b34 (native_write_msr+0x4/0x30)
[0.527769] Call Trace:
[0.528290]  
[0.528805]  ? cat_wrmsr+0x4c/0x70
[0.529348]  domain_add_cpu+0x2b2/0x430
[0.529840]  ? domain_add_cpu+0x430/0x430
[0.530326]  resctrl_online_cpu+0x4d/0xb0
[0.530811]  cpuhp_invoke_callback+0x298/0x420
[0.531295]  cpuhp_thread_fun+0x92/0x150
[0.531771]  smpboot_thread_fn+0xcd/0x170
[0.532245]  kthread+0x11c/0x140
[0.532714]  ? smpboot_register_percpu_thread+0xe0/0xe0
[0.533184]  ? set_kthread_struct+0x50/0x50
[0.533908]  ret_from_fork+0x1f/0x30
[0.534373]  

CPU: i5-12600k
MB: ASUS PRIME Z690M-PLUS D4

This is on a CPU with both performance (6 w HT) and efficiency (4)
cores:

root@deca:/home/bram# cat /proc/cpuinfo 
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 151
model name  : 12th Gen Intel(R) Core(TM) i5-12600K
stepping: 2
microcode   : 0x18
cpu MHz : 800.000
cache size  : 20480 KB
physical id : 0
siblings: 16
core id : 0
cpu cores   : 10
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 32
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb 
rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl 
vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe 
popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch 
cpuid_fault epb cat_l2 invpcid_single cdp_l2 ssbd ibrs ibpb stibp ibrs_enhanced 
tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep 
bmi2 erms invpcid rdt_a rdseed adx smap clflushopt clwb intel_pt sha_ni 
xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln 
pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req umip pku ospke waitpkg 
gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize 
pconfig arch_lbr flush_l1d arch_capabilities
vmx flags   : vnmi preemption_timer posted_intr invvpid ept_x_only ept_ad 
ept_1gb flexpriority apicv tsc_offset vtpr mtf vapic ept vpid 
unrestricted_guest vapic_reg vid ple shadow_vmcs ept_mode_based_exec 
tsc_scaling usr_wait_pause
bugs: spectre_v1 spectre_v2 spec_store_bypass swapgs
bogomips: 7372.80
clflush size: 64
cache_alignment : 64
address sizes   : 46 bits physical, 48 bits virtual
power management:

processor   : 1
vendor_id   : GenuineIntel
cpu family  : 6
model   : 151
model name  : 12th Gen Intel(R) Core(TM) i5-12600K
stepping: 2
microcode   : 0x18
cpu MHz : 800.000
cache size  : 20480 KB
physical id : 0
siblings: 16
core id : 0
cpu cores   : 10
apicid  : 1
initial apicid  : 1
fpu : yes
fpu_exception   : yes
cpuid level : 32
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb 
rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl 
vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe 
popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch 
cpuid_fault epb cat_l2 invpcid_single cdp_l2 ssbd ibrs ibpb stibp ibrs_enhanced 
tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep 
bmi2 erms invpcid rdt_a rdseed adx smap clflushopt clwb intel_pt sha_ni 
xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln 
pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req umip pku ospke waitpkg 
gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize 
pconfig arch_lbr flush_l1d arch_capabilities
vmx flags   : vnmi preemption_timer posted_intr invvpid ept_x_only ept_ad 
ept_1gb flexpriority apicv tsc_offset vtpr mtf vapic ept vpid 
unrestricted_guest vapic_reg vid ple shadow_vmcs ept_mode_based_exec 
tsc_scaling usr_wait_pause
bugs: spectre_v1 spectre_v2 spec_store_bypass swapgs
bogomips: 7372.80
clflush size: 64
cache_alignment : 64
address sizes   : 46 bits physical, 48 bits virtual
power management:

processor   : 2
vendor_id   : GenuineIntel
cpu family  : 6
model   : 151
model name  : 12th Gen Intel(R) Core(TM) i5-12600K
stepping: 2
microcode   : 0x18
cpu MHz : 800.000
cache size  : 20480 KB
physical id : 0
siblings

[Kernel-packages] [Bug 1959665] Re: linux-image-5.4.0-97.110 freezes by accessing cifs shares

There were 3 cifs patches in this last version. I've reverted all 3.
please try this test kernel to see if it corrects your issues:

wget 
https://kernel.ubuntu.com/~rtg/focal-cifs-freeze-lp1959665/lp1959665.1/amd64/linux-image-unsigned-5.4.0-98-generic_5.4.0-98.111~lp1959665.1_amd64.deb
wget 
https://kernel.ubuntu.com/~rtg/focal-cifs-freeze-lp1959665/lp1959665.1/amd64/linux-modules-5.4.0-98-generic_5.4.0-98.111~lp1959665.1_amd64.deb
wget 
https://kernel.ubuntu.com/~rtg/focal-cifs-freeze-lp1959665/lp1959665.1/amd64/linux-modules-extra-5.4.0-98-generic_5.4.0-98.111~lp1959665.1_amd64.deb
sudo dpkg -i *.deb
sudo apt-get -f install


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

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

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  linux-image-5.4.0-97.110 freezes by accessing cifs shares

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress

Bug description:
  Ubuntu 20.04 with kernel image 5.4.0-97.110 randomly freezes when we
  access cifs shares. The system needs a hard reset after the freeze.

  The previous kernel image (5.4.0-96.109) does not show this behavior.
  Multiple Ubuntu 20.04 systems running on kernel image 9.4.0-97.110 are
  affected on our sites.

  The cifs shares are accessed via autofs using Kerberos authentication.

  The following info is the only error message we could actively catch
  on a different system before the system was frozen:

  general protection fault:  [#3] SMP PTI
  CPU: 0 PID: 21294 Comm: automount Tainted: G  DOE 
5.4.0-97-generic #110-Ubuntu
  Hardware name: Dell Inc. Precision 7530/03RV2M, BIOS 1.14.4 10/21/2020
  RIP: 0010:kmem_cache_alloc_trace+0x8c/0x240
  Code: 08 65 4c 03 05 1d e8 f7 6e 49 83 78 10 00 4d 8b 38 0f 84 92 01 00 00 4d 
85 ff 0f 84 89 01 00 00 41 8b 41 20 49 8b 39 4c 01 f8 <48> 8b 18 48 89 c1 49 33 
99 70 01 00 00 4c 89 f8 48 0f c9 48 31 cb
  RSP: 0018:a6ca860f7ba0 EFLAGS: 00010286
  RAX: fdd44d7c219190e1 RBX:  RCX: 
  RDX: d558 RSI: 0cc0 RDI: 00035060
  RBP: a6ca860f7bd0 R08: 99233c035060 R09: 992338c079c0
  R10: 0001 R11: 0004 R12: 0cc0
  R13: 000b R14: 992338c079c0 R15: fdd44d7c219190e1
  FS:  7fdc24e29700() GS:99233c00() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7f15a80ee010 CR3: 0007e36b2006 CR4: 003606f0
  Call Trace:
   ? proc_self_get_link+0x70/0xd0
   proc_self_get_link+0x70/0xd0
   link_path_walk.part.0+0x478/0x550
   ? trailing_symlink+0x1d1/0x280
   path_openat+0xb7/0x290
   do_filp_open+0x91/0x100
   ? unuse_pde+0x30/0x30
   do_sys_open+0x17e/0x290
   __x64_sys_openat+0x20/0x30
   __orig_openat+0x71/0xc0 [eset_rtp]
   ? __switch_to_asm+0x40/0x70
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   ? __x64_sys_futex+0x13f/0x170
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   __x64_sys_ertp_openat+0x29/0x60 [eset_rtp]
   do_syscall_64+0x57/0x190
   entry_SYSCALL_64_after_hwframe+0x44/0xa9
  RIP: 0033:0x7fdc28a41f24
  Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 
48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 
44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44
  RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101
  RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24
   ? unuse_pde+0x30/0x30
   do_sys_open+0x17e/0x290
   __x64_sys_openat+0x20/0x30
   __orig_openat+0x71/0xc0 [eset_rtp]
   ? __switch_to_asm+0x40/0x70
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   ? __x64_sys_futex+0x13f/0x170
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   __x64_sys_ertp_openat+0x29/0x60 [eset_rtp]
   do_syscall_64+0x57/0x190
   entry_SYSCALL_64_after_hwframe+0x44/0xa9
  RIP: 0033:0x7fdc28a41f24
  Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 
48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 
44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44
  RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101
  RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24
  RDX: 0008 RSI: 564d4410a8c8 RDI: ff9c
  RBP: 564d4410a8c8 R08:  R09: 0001
  R10

[Kernel-packages] [Bug 1959715] [NEW] Touchpad is not working after installing Ubuntu. Worked fine with windows

2022-02-01 Thread David Jepsson

Public bug reported:

Ubuntu not finding the touchpad. Attaching output from cat
/proc/bus/input/devices. Followed guide on
https://wiki.ubuntu.com/DebuggingTouchpadDetection. Please let me know
if there is anything else you need from me.

Description:Ubuntu 20.04.3 LTS
Release:20.04

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb  1 20:33:13 2022
InstallationDate: Installed on 2022-02-01 (0 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe-5.13
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.13 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Attachment added: "cat /proc/bus/input/devices"
   https://bugs.launchpad.net/bugs/1959715/+attachment/5558674/+files/devices

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

Title:
  Touchpad is not working after installing Ubuntu. Worked fine with
  windows

Status in linux-signed-hwe-5.13 package in Ubuntu:
  New

Bug description:
  Ubuntu not finding the touchpad. Attaching output from cat
  /proc/bus/input/devices. Followed guide on
  https://wiki.ubuntu.com/DebuggingTouchpadDetection. Please let me know
  if there is anything else you need from me.

  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  1 20:33:13 2022
  InstallationDate: Installed on 2022-02-01 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1959715/+subscriptions


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

[Kernel-packages] [Bug 1959012] Re: MANA updates

** Changed in: linux-azure (Ubuntu Impish)
   Status: In Progress => Fix Committed

** Changed in: linux-azure (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

Title:
  MANA updates

Status in linux-azure package in Ubuntu:
  Fix Committed
Status in linux-azure source package in Focal:
  New
Status in linux-azure source package in Impish:
  Fix Committed
Status in linux-azure source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  The MANA driver is missing 2 updates.

  commit 6cc74443a7732d7e93bee3d0c3704a22cc7274d9 ("net: mana: Add RX fencing")
  commit 9acfc57fa2b8944ed079cedbf846823ea32b8a31 ("net: mana: Fix memory leak 
in mana_hwc_create_wq")

  [Test Plan]

  Microsoft tested

  [Where things could go wrong]

  Fencing requests could get dropped or sent out of order.

  [Other Info]

  SF: #00324494

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


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

[Kernel-packages] [Bug 1959710] [NEW] i40e NIC no longer working

2022-02-01 Thread mzac

Public bug reported:

Running Intel X710-DA4 NICs and they are no longer showing up since
upgrading to 5.4.0-97 from 5.4.0-96.

Note that we are running pf_ring ZC on this system and we are getting
errors.

The interfaces no longer show up with ifconfig either after boot however
they are seen in dmesg.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-97-generic 5.4.0-97.110
ProcVersionSignature: Ubuntu 5.4.0-97.110-generic 5.4.162
Uname: Linux 5.4.0-97-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Feb  1 14:02 seq
 crw-rw 1 root audio 116, 33 Feb  1 14:02 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
Date: Tue Feb  1 14:03:20 2022
InstallationDate: Installed on 2021-10-26 (98 days ago)
InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210824)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04b4:6570 Cypress Semiconductor Corp. Unprogrammed 
CY7C65632/34 hub HX2VL
 Bus 001 Device 004: ID 0624:0402 Avocent Corp. Cisco Virtual Keyboard and Mouse
 Bus 001 Device 002: ID 05a6:0a00 Cisco Systems, Inc. Integrated Management 
Controller Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Cisco Systems Inc UCSC-C240-M5SX
PciMultimedia:
 
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 mgag200drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-97-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-97-generic N/A
 linux-backports-modules-5.4.0-97-generic  N/A
 linux-firmware1.187.25
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/10/2020
dmi.bios.vendor: Cisco Systems, Inc.
dmi.bios.version: C240M5.4.1.3e.0.1210201753
dmi.board.asset.tag: Unknown
dmi.board.name: UCSC-C240-M5SX
dmi.board.vendor: Cisco Systems Inc
dmi.board.version: 74-105773-01
dmi.chassis.asset.tag: Unknown
dmi.chassis.type: 23
dmi.chassis.vendor: Cisco Systems Inc
dmi.chassis.version: 74-105778-02
dmi.modalias: 
dmi:bvnCiscoSystems,Inc.:bvrC240M5.4.1.3e.0.1210201753:bd12/10/2020:svnCiscoSystemsInc:pnUCSC-C240-M5SX:pvrA0:rvnCiscoSystemsInc:rnUCSC-C240-M5SX:rvr74-105773-01:cvnCiscoSystemsInc:ct23:cvr74-105778-02:
dmi.product.name: UCSC-C240-M5SX
dmi.product.version: A0
dmi.sys.vendor: Cisco Systems Inc

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


** Tags: amd64 apport-bug focal uec-images

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

Title:
  i40e NIC no longer working

Status in linux package in Ubuntu:
  New

Bug description:
  Running Intel X710-DA4 NICs and they are no longer showing up since
  upgrading to 5.4.0-97 from 5.4.0-96.

  Note that we are running pf_ring ZC on this system and we are getting
  errors.

  The interfaces no longer show up with ifconfig either after boot
  however they are seen in dmesg.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-97-generic 5.4.0-97.110
  ProcVersionSignature: Ubuntu 5.4.0-97.110-generic 5.4.162
  Uname: Linux 5.4.0-97-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb  1 14:02 seq
   crw-rw 1 root audio 116, 33 Feb  1 14:02 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  Date: Tue Feb  1 14:03:20 2022
  InstallationDate: Installed on 2021-10-26 (98 days ago)
  InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210824)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04b4:6570 Cypress Semiconductor Corp. Unprogrammed 
CY7C65632/34 hub HX2VL
   Bus 001 Device 004: ID 0624:0402 Avocent Corp. Cisco Virtual Keyboard and 
Mouse
   Bus 001 Device 002: ID 05a6:0a00 Cisco Systems, Inc. Integrated Management 
Controller Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Cisco Systems Inc UCSC-C240-M5SX
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=

[Kernel-packages] [Bug 1959709] [NEW] Bionic update: upstream stable patchset 2022-02-01

2022-02-01 Thread 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 2022-02-01

Ported from the following upstream stable releases:
v4.14.262, v4.19.225

   from git://git.kernel.org/

tracing: Fix check for trace_percpu_buffer validity in get_trace_buf()
tracing: Tag trace_percpu_buffer as a percpu pointer
virtio_pci: Support surprise removal of virtio pci device
ieee802154: atusb: fix uninit value in atusb_set_extended_addr
RDMA/core: Don't infoleak GRH fields
mac80211: initialize variable have_higher_than_11mbit
i40e: fix use-after-free in i40e_sync_filters_subtask()
i40e: Fix incorrect netdev's real number of RX/TX queues
ipv6: Check attribute length for RTA_GATEWAY in multipath route
ipv6: Check attribute length for RTA_GATEWAY when deleting multipath route
sch_qfq: prevent shift-out-of-bounds in qfq_init_qdisc
power: reset: ltc2952: Fix use of floating point literals
rndis_host: support Hytera digital radios
phonet: refcount leak in pep_sock_accep
ipv6: Continue processing multipath route even if gateway attribute is invalid
ipv6: Do cleanup if attribute validation fails in multipath route
scsi: libiscsi: Fix UAF in iscsi_conn_get_param()/iscsi_conn_teardown()
ip6_vti: initialize __ip6_tnl_parm struct in vti6_siocdevprivate
net: udp: fix alignment problem in udp4_seq_show()
mISDN: change function names to avoid conflicts
usb: mtu3: fix interval value for intr and isoc
UBUNTU: upstream stable to v4.14.262, v4.19.225

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

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

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

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

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

** 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 2022-02-01
  
-upstream stable patchset 2022-02-01
-from git://git.kernel.org/
+ Ported from the following upstream stable releases:
+ v4.14.262, v4.19.225
+ 
+    from git://git.kernel.org/
+ 
+ tracing: Fix check for trace_percpu_buffer validity in get_trace_buf()
+ tracing: Tag trace_percpu_buffer as a percpu pointer
+ virtio_pci: Support surprise removal of virtio pci device
+ ieee802154: atusb: fix uninit value in atusb_set_extended_addr
+ RDMA/core: Don't infoleak GRH fields
+ mac80211: initialize variable have_higher_than_11mbit
+ i40e: fix use-after-free in i40e_sync_filters_subtask()
+ i40e: Fix incorrect netdev's real number of RX/TX queues
+ ipv6: Check attribute length for RTA_GATEWAY in multipath route
+ ipv6: Check attribute length for RTA_GATEWAY when deleting multipath route
+ sch_qfq: prevent shift-out-of-bounds in qfq_init_qdisc
+ power: reset: ltc2952: Fix use of floating point literals
+ rndis_host: support Hytera digital radios
+ phonet: refcount leak in pep_sock_accep
+ ipv6: Continue processing multipath route even if gateway attribute is invalid
+ ipv6: Do cleanup if attribute validation fails in multipath route
+ scsi: libiscsi: Fix UAF in iscsi_conn_get_param()/iscsi_conn_teardown()
+ ip6_vti: initialize __ip6_tnl_parm struct in

[Kernel-packages] [Bug 1959701] [NEW] Focal update: v5.4.173 upstream stable release

2022-02-01 Thread 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:

   v5.4.173 upstream stable release
   from git://git.kernel.org/

kbuild: Add $(KBUILD_HOSTLDFLAGS) to 'has_libelf' test
devtmpfs regression fix: reconfigure on each mount
orangefs: Fix the size of a memory allocation in orangefs_bufmap_alloc()
perf: Protect perf_guest_cbs with RCU
KVM: s390: Clarify SIGP orders versus STOP/RESTART
media: uvcvideo: fix division by zero at stream start
rtlwifi: rtl8192cu: Fix WARNING when calling local_irq_restore() with 
interrupts enabled
firmware: qemu_fw_cfg: fix sysfs information leak
firmware: qemu_fw_cfg: fix NULL-pointer deref on duplicate entries
firmware: qemu_fw_cfg: fix kobject leak in probe error path
KVM: x86: remove PMU FIXED_CTR3 from msrs_to_save_all
ALSA: hda/realtek - Fix silent output on Gigabyte X570 Aorus Master after 
reboot from Windows
mtd: fixup CFI on ixp4xx
ARM: 9025/1: Kconfig: CPU_BIG_ENDIAN depends on !LD_IS_LLD
Linux 5.4.173
UBUNTU: upstream stable to v5.4.173

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

** Affects: linux (Ubuntu Focal)
 Importance: Medium
 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 Focal)
   Importance: Undecided
   Status: New

** 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:
+    v5.4.173 upstream stable release
+    from git://git.kernel.org/
  
-v5.4.173 upstream stable release
-from git://git.kernel.org/
+ kbuild: Add $(KBUILD_HOSTLDFLAGS) to 'has_libelf' test
+ devtmpfs regression fix: reconfigure on each mount
+ orangefs: Fix the size of a memory allocation in orangefs_bufmap_alloc()
+ perf: Protect perf_guest_cbs with RCU
+ KVM: s390: Clarify SIGP orders versus STOP/RESTART
+ media: uvcvideo: fix division by zero at stream start
+ rtlwifi: rtl8192cu: Fix WARNING when calling local_irq_restore() with 
interrupts enabled
+ firmware: qemu_fw_cfg: fix sysfs information leak
+ firmware: qemu_fw_cfg: fix NULL-pointer deref on duplicate entries
+ firmware: qemu_fw_cfg: fix kobject leak in probe error path
+ KVM: x86: remove PMU FIXED_CTR3 from msrs_to_save_all
+ ALSA: hda/realtek - Fix silent output on Gigabyte X570 Aorus Master after 
reboot from Windows
+ mtd: fixup CFI on ixp4xx
+ ARM: 9025/1: Kconfig: CPU_BIG_ENDIAN depends on !LD_IS_LLD
+ Linux 5.4.173
+ UBUNTU: upstream stable to v5.4.173

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

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

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

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

Title:
  Focal update: v5.4.173 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  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:

     v5.4

[Kernel-packages] [Bug 1959698] [NEW] Focal update: v5.4.172 upstream stable release

2022-02-01 Thread 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:

   v5.4.172 upstream stable release
   from git://git.kernel.org/

workqueue: Fix unbind_workers() VS wq_worker_running() race
Bluetooth: btusb: fix memory leak in btusb_mtk_submit_wmt_recv_urb()
Bluetooth: bfusb: fix division by zero in send path
USB: core: Fix bug in resuming hub's handling of wakeup requests
USB: Fix "slab-out-of-bounds Write" bug in usb_hcd_poll_rh_status
mmc: sdhci-pci: Add PCI ID for Intel ADL
veth: Do not record rx queue hint in veth_xmit
mfd: intel-lpss: Fix too early PM enablement in the ACPI ->probe()
drivers core: Use sysfs_emit and sysfs_emit_at for show(device *...) functions
can: gs_usb: fix use of uninitialized variable, detach device on reception of 
invalid USB data
can: gs_usb: gs_can_start_xmit(): zero-initialize hf->{flags,reserved}
random: fix data race on crng_node_pool
random: fix data race on crng init time
random: fix crash on multiple early calls to add_bootloader_randomness()
media: Revert "media: uvcvideo: Set unique vdev name based in type"
staging: wlan-ng: Avoid bitwise vs logical OR warning in 
hfa384x_usb_throttlefn()
drm/i915: Avoid bitwise vs logical OR warning in snb_wm_latency_quirk()
staging: greybus: fix stack size warning with UBSAN
Linux 5.4.172
UBUNTU: upstream stable to v5.4.172

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

** Affects: linux (Ubuntu Focal)
 Importance: Medium
 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 Focal)
   Importance: Undecided
   Status: New

** 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:
+    v5.4.172 upstream stable release
+    from git://git.kernel.org/
  
-v5.4.172 upstream stable release
-from git://git.kernel.org/
+ workqueue: Fix unbind_workers() VS wq_worker_running() race
+ Bluetooth: btusb: fix memory leak in btusb_mtk_submit_wmt_recv_urb()
+ Bluetooth: bfusb: fix division by zero in send path
+ USB: core: Fix bug in resuming hub's handling of wakeup requests
+ USB: Fix "slab-out-of-bounds Write" bug in usb_hcd_poll_rh_status
+ mmc: sdhci-pci: Add PCI ID for Intel ADL
+ veth: Do not record rx queue hint in veth_xmit
+ mfd: intel-lpss: Fix too early PM enablement in the ACPI ->probe()
+ drivers core: Use sysfs_emit and sysfs_emit_at for show(device *...) functions
+ can: gs_usb: fix use of uninitialized variable, detach device on reception of 
invalid USB data
+ can: gs_usb: gs_can_start_xmit(): zero-initialize hf->{flags,reserved}
+ random: fix data race on crng_node_pool
+ random: fix data race on crng init time
+ random: fix crash on multiple early calls to add_bootloader_randomness()
+ media: Revert "media: uvcvideo: Set unique vdev name based in type"
+ staging: wlan-ng: Avoid bitwise vs logical OR warning in 
hfa384x_usb_throttlefn()
+ drm/i915: Avoid bitwise vs logical OR warning in snb_wm_latency_quirk()
+ staging: greybus: fix stack size warning with UBSAN
+ Linux 5.4.172
+ UBUNTU: upstream stable to v5.4.172

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

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

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

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

Title

[Kernel-packages] [Bug 1958679] Re: after suspend losing screen

2022-02-01 Thread go4heartbeat

Dear Ubuntu-Helpers!

The reason for my error message was the concern for the users like me
which ones cannot afford the modernest computers!

Why?
My concern was that all users of a computer like my computer Vaio with an 
Nvidia graphics card, supported by the graphics driver X.Org-X-Server (Nouveau) 
starting from problem kernels 5.13.0-27-generic on, will have problems in all 
future with such important functions like the suspend mode :-(

Contrary to expectations, this has now obsolet with the latest kernel,
because Suspend with the latest kernel 5.13.0-28-generic is now working
properly again!

Thank you very much and greetings

Elmar

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

Title:
  after suspend losing screen

Status in linux-hwe-5.13 package in Ubuntu:
  Incomplete

Bug description:
  After wake up after suspending my notebook I lost my screen with white
  and black bars on it!

  Technic:
  with the newest Kernel für Ubuntu 20.04:
  Ubuntu 20.04 mit Kernel 5.13.0-27-generic

  Notebook Sony Vaio with graphics driver:
  X.Org-X-Server (Nouveau)

  Now, with the older kernel (second kernel)
  uname -r
  5.11.0-46-generic
  all be alright

  So I currently have no problems, but I would like to point out
  problems with the kernel 5.13.0-27-generic and suspend.

  Thank you!

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


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

[Kernel-packages] [Bug 1959665] Re: linux-image-5.4.0-97.110 freezes by accessing cifs shares

```
Servers:
Number of credits: 185 Dialect 0x300
1) Name: a.b.c.d Uses: 1 Capability: 0x300067 Session Status: 1 TCP status: 
1 Instance: 1
Local Users To Server: 1 SecMode: 0x1 Req On Wire: 0 SessionId: 
0xc1be04000435
Shares:
0) IPC: \\xxx\IPC$ Mounts: 1 DevInfo: 0x0 Attributes: 0x0
PathComponentMax: 0 Status: 1 type: 0 Serial Number: 0x0
Share Capabilities: NoneShare Flags: 0x30
tid: 0x1Maximal Access: 0x11f01ff

1) \\xxx\yyy Mounts: 1 DevInfo: 0x60020 Attributes: 0xc700ff
PathComponentMax: 255 Status: 1 type: DISK Serial Number: 0xaaf791c3
Share Capabilities: DFS, Aligned, Partition Aligned, TRIM-support,  
Share Flags: 0x803
tid: 0x5Optimal sector size: 0x200  Maximal Access: 0x1200a9

MIDs:

Server interfaces: 1
0)  Speed: 100 bps
Capabilities: 
IPv4: e.f.g.h

 Debuginfo:

[  710.383873] kernel BUG at mm/slub.c:307!
[  710.384582] invalid opcode:  [#1] SMP PTI
[  710.385116] CPU: 1 PID: 3089 Comm: umount Not tainted 5.4.0-97-generic 
#110-Ubuntu
[  710.385775] Hardware name: VMware, Inc. VMware Virtual Platform/440BX 
Desktop Reference Platform, BIOS 6.00 12/12/2018
[  710.386903] RIP: 0010:__slab_free+0x199/0x360
[  710.387470] Code: 00 48 89 c7 fa 66 0f 1f 44 00 00 f0 49 0f ba 2c 24 00 72 
79 4d 3b 6c 24 20 74 11 49 0f ba 34 24 00 57 9d 0f 1f 44 00 00 eb 9f <0f> 0b 49 
3b 5c 24 28 75 e8 48 8b 44 24 28 49 89 4c 24 28 49 89 44
[  710.389229] RSP: 0018:b94541417ce0 EFLAGS: 00010246
[  710.389809] RAX: 90cfb5fab120 RBX: 8080007f RCX: 90cfb5fab120
[  710.390406] RDX: 90cfb5fab120 RSI: ec7d84d7eac0 RDI: 90cfbb003880
[  710.390993] RBP: b94541417d90 R08: 0001 R09: c08ed620
[  710.391574] R10: 90cfb5fab120 R11: 0001 R12: ec7d84d7eac0
[  710.392147] R13: 90cfb5fab120 R14: 90cfbb003880 R15: 
[  710.392709] FS:  7f7b219e5840() GS:90cfbba8() 
knlGS:
[  710.393274] CS:  0010 DS:  ES:  CR0: 80050033
[  710.393820] CR2: 55a3da30b9d0 CR3: 00012658a006 CR4: 007606e0
[  710.394545] PKRU: 5554
[  710.395093] Call Trace:
[  710.395760]  ? fscache_free_cookie+0x39/0x60 [fscache]
[  710.396480]  ? cifs_cleanup_volume_info_contents+0x30/0x60 [cifs]
[  710.397026]  kfree+0x231/0x250
[  710.397593]  cifs_cleanup_volume_info_contents+0x30/0x60 [cifs]
[  710.398159]  dfs_cache_del_vol+0xec/0x1a0 [cifs]
[  710.398720]  cifs_umount+0x9e/0xd0 [cifs]
[  710.399270]  cifs_kill_sb+0x1f/0x30 [cifs]
[  710.399807]  deactivate_locked_super+0x3b/0x80
[  710.400358]  deactivate_super+0x3e/0x50
[  710.400882]  cleanup_mnt+0x109/0x160
[  710.401403]  __cleanup_mnt+0x12/0x20
[  710.401919]  task_work_run+0x8f/0xb0
[  710.402456]  exit_to_usermode_loop+0x131/0x160
[  710.402956]  do_syscall_64+0x163/0x190
[  710.403448]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  710.403922] RIP: 0033:0x7f7b21c4a2cb
[  710.404380] Code: 8b 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 90 f3 0f 1e fa 
31 f6 e9 05 00 00 00 0f 1f 44 00 00 f3 0f 1e fa b8 a6 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d 95 8b 0c 00 f7 d8 64 89 01 48
[  710.405823] RSP: 002b:7fff6a6cdc28 EFLAGS: 0246 ORIG_RAX: 
00a6
[  710.406325] RAX:  RBX: 7f7b21d79204 RCX: 7f7b21c4a2cb
[  710.406811] RDX:  RSI:  RDI: 560106a71ae0
[  710.407317] RBP: 560106a6a890 R08:  R09: 7fff6a6cc9a0
[  710.407790] R10: 7f7b21d65339 R11: 0246 R12: 560106a71ae0
[  710.408249] R13:  R14: 560106a6a988 R15: 560106a6aaa0
[  710.408707] Modules linked in: md4 cmac nls_utf8 cifs libarc4 fscache libdes 
vmw_vsock_vmci_transport vsock dm_multipath scsi_dh_rdac scsi_dh_emc 
scsi_dh_alua intel_rapl_msr intel_rapl_common isst_if_mbox_msr isst_if_common 
nfit rapl vmw_balloon joydev input_leds serio_raw vmw_vmci mac_hid sch_fq_codel 
msr ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper vmwgfx ttm 
psmouse drm_kms_helper syscopyarea ahci sysfillrect sysimgblt vmw_pvscsi 
libahci fb_sys_fops vmxnet3 pata_acpi drm i2c_piix4
[  710.412749] ---[ end trace c3b4f6aeb4b07511 ]---
[  710.413274] RIP: 0010:__slab_free+0x199/0x360
[  710.413781] Code: 00 48 89 c7 fa 66 0f 1f 44 00 00 f0 49 0f ba 2c 24 00 72 
79 4d 3b 6c 24 20 74 11 49 0f ba 34 24 00 57 9d 0f 1f 44 00 00 eb 9f <0f> 0b 49 
3b 5c 24 28 75 e8 48 8b 44 24 28 49 89 4c 24 28 49 89 44
[  710.415405] RSP: 0018:b94541417ce0 EFLAGS: 00010246
[  710.415948] RAX: 90cfb5fab120 RBX: 8080007f RCX: 90cfb5fab120
[  710.416497] RDX: 90cfb5fab

[Kernel-packages] [Bug 1959665] Re: linux-image-5.4.0-97.110 freezes by accessing cifs shares

2022-02-01 Thread Sebastian Berner

** Summary changed:

- linux-image-9.4.0-97.110 freezes by accessing cifs shares
+ linux-image-5.4.0-97.110 freezes by accessing cifs shares

** Description changed:

- Ubuntu 20.04 with kernel image 9.4.0-97.110 randomly freezes when we
+ Ubuntu 20.04 with kernel image 5.4.0-97.110 randomly freezes when we
  access cifs shares. The system needs a hard reset after the freeze.
  
  The previous kernel image (5.4.0-96.109) does not show this behavior.
  Multiple Ubuntu 20.04 systems running on kernel image 9.4.0-97.110 are
  affected on our sites.
  
  The cifs shares are accessed via autofs using Kerberos authentication.
  
  The following info is the only error message we could actively catch on
  a different system before the system was frozen:
  
  general protection fault:  [#3] SMP PTI
  CPU: 0 PID: 21294 Comm: automount Tainted: G  DOE 
5.4.0-97-generic #110-Ubuntu
  Hardware name: Dell Inc. Precision 7530/03RV2M, BIOS 1.14.4 10/21/2020
  RIP: 0010:kmem_cache_alloc_trace+0x8c/0x240
  Code: 08 65 4c 03 05 1d e8 f7 6e 49 83 78 10 00 4d 8b 38 0f 84 92 01 00 00 4d 
85 ff 0f 84 89 01 00 00 41 8b 41 20 49 8b 39 4c 01 f8 <48> 8b 18 48 89 c1 49 33 
99 70 01 00 00 4c 89 f8 48 0f c9 48 31 cb
  RSP: 0018:a6ca860f7ba0 EFLAGS: 00010286
  RAX: fdd44d7c219190e1 RBX:  RCX: 
  RDX: d558 RSI: 0cc0 RDI: 00035060
  RBP: a6ca860f7bd0 R08: 99233c035060 R09: 992338c079c0
  R10: 0001 R11: 0004 R12: 0cc0
  R13: 000b R14: 992338c079c0 R15: fdd44d7c219190e1
  FS:  7fdc24e29700() GS:99233c00() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7f15a80ee010 CR3: 0007e36b2006 CR4: 003606f0
  Call Trace:
-  ? proc_self_get_link+0x70/0xd0
-  proc_self_get_link+0x70/0xd0
-  link_path_walk.part.0+0x478/0x550
-  ? trailing_symlink+0x1d1/0x280
-  path_openat+0xb7/0x290
-  do_filp_open+0x91/0x100
-  ? unuse_pde+0x30/0x30
-  do_sys_open+0x17e/0x290
-  __x64_sys_openat+0x20/0x30
-  __orig_openat+0x71/0xc0 [eset_rtp]
-  ? __switch_to_asm+0x40/0x70
-  ? __switch_to_asm+0x34/0x70
-  ? __switch_to_asm+0x40/0x70
-  ? __x64_sys_futex+0x13f/0x170
-  ? __switch_to_asm+0x34/0x70
-  ? __switch_to_asm+0x40/0x70
-  ? __switch_to_asm+0x34/0x70
-  ? __switch_to_asm+0x40/0x70
-  __x64_sys_ertp_openat+0x29/0x60 [eset_rtp]
-  do_syscall_64+0x57/0x190
-  entry_SYSCALL_64_after_hwframe+0x44/0xa9
+  ? proc_self_get_link+0x70/0xd0
+  proc_self_get_link+0x70/0xd0
+  link_path_walk.part.0+0x478/0x550
+  ? trailing_symlink+0x1d1/0x280
+  path_openat+0xb7/0x290
+  do_filp_open+0x91/0x100
+  ? unuse_pde+0x30/0x30
+  do_sys_open+0x17e/0x290
+  __x64_sys_openat+0x20/0x30
+  __orig_openat+0x71/0xc0 [eset_rtp]
+  ? __switch_to_asm+0x40/0x70
+  ? __switch_to_asm+0x34/0x70
+  ? __switch_to_asm+0x40/0x70
+  ? __x64_sys_futex+0x13f/0x170
+  ? __switch_to_asm+0x34/0x70
+  ? __switch_to_asm+0x40/0x70
+  ? __switch_to_asm+0x34/0x70
+  ? __switch_to_asm+0x40/0x70
+  __x64_sys_ertp_openat+0x29/0x60 [eset_rtp]
+  do_syscall_64+0x57/0x190
+  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  RIP: 0033:0x7fdc28a41f24
  Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 
48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 
44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44
  RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101
  RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24
-  ? unuse_pde+0x30/0x30
-  do_sys_open+0x17e/0x290
-  __x64_sys_openat+0x20/0x30
-  __orig_openat+0x71/0xc0 [eset_rtp]
-  ? __switch_to_asm+0x40/0x70
-  ? __switch_to_asm+0x34/0x70
-  ? __switch_to_asm+0x40/0x70
-  ? __x64_sys_futex+0x13f/0x170
-  ? __switch_to_asm+0x34/0x70
-  ? __switch_to_asm+0x40/0x70
-  ? __switch_to_asm+0x34/0x70
-  ? __switch_to_asm+0x40/0x70
-  __x64_sys_ertp_openat+0x29/0x60 [eset_rtp]
-  do_syscall_64+0x57/0x190
-  entry_SYSCALL_64_after_hwframe+0x44/0xa9
+  ? unuse_pde+0x30/0x30
+  do_sys_open+0x17e/0x290
+  __x64_sys_openat+0x20/0x30
+  __orig_openat+0x71/0xc0 [eset_rtp]
+  ? __switch_to_asm+0x40/0x70
+  ? __switch_to_asm+0x34/0x70
+  ? __switch_to_asm+0x40/0x70
+  ? __x64_sys_futex+0x13f/0x170
+  ? __switch_to_asm+0x34/0x70
+  ? __switch_to_asm+0x40/0x70
+  ? __switch_to_asm+0x34/0x70
+  ? __switch_to_asm+0x40/0x70
+  __x64_sys_ertp_openat+0x29/0x60 [eset_rtp]
+  do_syscall_64+0x57/0x190
+  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  RIP: 0033:0x7fdc28a41f24
  Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 
48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 
44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44
  RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101
  RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24
  RDX: 0008 RSI: 564d4410a8c8 RDI: ff9c
  RBP: 564d4410a8c8 R08: 0

[Kernel-packages] [Bug 1959685] [NEW] Kernel BUG with btrfs on linux 5.13

2022-02-01 Thread Maxim Kuvyrkov

Public bug reported:

I am hitting the below kernel oops every 2-5 days on my home server box.
RIP is always "0010:btrfs_evict_inode+0xa1/0x480 [btrfs]" and address is
always "0068".  I'm using btrfs in raid1 configuration for
general storage.

===
Feb  1 01:40:38 server kernel: [172867.493851] BUG: kernel NULL pointer 
dereference, address: 0068
Feb  1 01:40:38 server kernel: [172867.493885] #PF: supervisor write access in 
kernel mode
Feb  1 01:40:38 server kernel: [172867.493903] #PF: error_code(0x0002) - 
not-present page
Feb  1 01:40:38 server kernel: [172867.493920] PGD 0 P4D 0 
Feb  1 01:40:38 server kernel: [172867.493931] Oops: 0002 [#1] SMP PTI
Feb  1 01:40:38 server kernel: [172867.493946] CPU: 2 PID: 104 Comm: kswapd0 
Not tainted 5.13.0-27-generic #29~20.04.1-Ubuntu
Feb  1 01:40:38 server kernel: [172867.493972] Hardware name: Gigabyte 
Technology Co., Ltd. H67MA-D2H-B3/H67MA-D2H-B3, BIOS F1 02/11/2011
Feb  1 01:40:38 server kernel: [172867.493999] RIP: 
0010:btrfs_evict_inode+0xa1/0x480 [btrfs]
Feb  1 01:40:38 server kernel: [172867.494070] Code: fd ff ff e8 d1 b1 9f c8 65 
48 8b 04 25 c0 7b 01 00 48 89 45 b8 49 8b 84 24 f0 fd ff ff 48 85 c0 74 55 4d 
8b b4 24 f8 fd ff ff  41 80 66 68 fe f0 41 80 66 
68 f7 4c 89 f6 4c 89 ff e8 98 00 01
Feb  1 01:40:38 server kernel: [172867.494123] RSP: 0018:ab8dc042fad0 
EFLAGS: 00010202
Feb  1 01:40:38 server kernel: [172867.494141] RAX: 0004 RBX: 
8f01001251d8 RCX: 8f0100125040
Feb  1 01:40:38 server kernel: [172867.494163] RDX: 00ff RSI: 
 RDI: 8f01001251d0
Feb  1 01:40:38 server kernel: [172867.494185] RBP: ab8dc042fb28 R08: 
 R09: 
Feb  1 01:40:38 server kernel: [172867.494206] R10: 8f00c2ea6280 R11: 
0001 R12: 8f01001253c0
Feb  1 01:40:38 server kernel: [172867.494228] R13: 8f01001251d0 R14: 
 R15: 8f01001251b0
Feb  1 01:40:38 server kernel: [172867.494250] FS:  () 
GS:8f03cfa8() knlGS:
Feb  1 01:40:38 server kernel: [172867.494274] CS:  0010 DS:  ES:  CR0: 
80050033
Feb  1 01:40:38 server kernel: [172867.494293] CR2: 0068 CR3: 
000202810001 CR4: 000606e0
Feb  1 01:40:38 server kernel: [172867.494315] Call Trace:
Feb  1 01:40:38 server kernel: [172867.494328]  evict+0xd2/0x180
Feb  1 01:40:38 server kernel: [172867.494342]  dispose_list+0x39/0x50
Feb  1 01:40:38 server kernel: [172867.494356]  prune_icache_sb+0x5c/0x80
Feb  1 01:40:38 server kernel: [172867.494370]  super_cache_scan+0x132/0x1b0
Feb  1 01:40:38 server kernel: [172867.494386]  do_shrink_slab+0x144/0x2c0
Feb  1 01:40:38 server kernel: [172867.494402]  shrink_slab+0x215/0x2b0
Feb  1 01:40:38 server kernel: [172867.494416]  shrink_node+0x2dd/0x6f0
Feb  1 01:40:38 server kernel: [172867.494430]  balance_pgdat+0x322/0x5f0
Feb  1 01:40:38 server kernel: [172867.494445]  kswapd+0x1f8/0x380
Feb  1 01:40:38 server kernel: [172867.494458]  ? wait_woken+0x80/0x80
Feb  1 01:40:38 server kernel: [172867.494473]  ? balance_pgdat+0x5f0/0x5f0
Feb  1 01:40:38 server kernel: [172867.494487]  kthread+0x12b/0x150
Feb  1 01:40:38 server kernel: [172867.494501]  ? set_kthread_struct+0x40/0x40
Feb  1 01:40:38 server kernel: [172867.494516]  ret_from_fork+0x22/0x30
Feb  1 01:40:38 server kernel: [172867.494532] Modules linked in: xt_conntrack 
xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype 
iptable_filter iptable_nat nf_nat nf_conntrack nf_defra
g_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc aufs overlay 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio 
snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_code
c snd_hda_core snd_hwdep snd_pcm intel_rapl_msr snd_seq_midi snd_seq_midi_event 
mei_hdcp intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_rawmidi kvm_intel kvm snd_seq crct10dif_pclmul ghash_
clmulni_intel snd_seq_device cryptd i915 rapl snd_timer intel_cstate serio_raw 
joydev drm_kms_helper input_leds cec snd rc_core i2c_algo_bit fb_sys_fops 
syscopyarea sysfillrect sysimgblt video soundcore mei_me m
ei mac_hid sch_fq_codel msr parport_pc ppdev drm lp parport ip_tables x_tables 
autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c uas 
usb_storage hid_generic usbhid hid
Feb  1 01:40:38 server kernel: [172867.494581]  gpio_ich crc32_pclmul lpc_ich 
r8169 i2c_i801 ahci i2c_smbus xhci_pci realtek libahci xhci_pci_renesas
Feb  1 01:40:38 server kernel: [172867.497076] CR2: 0068
Feb  1 01:40:38 server kernel: [172867.497876] ---[ end trace 4ab76c62441acb52 
]---
Feb  1 01:40:38 server kernel: [172867.498695] RIP: 
0010:btrfs_evict_inode+0xa1/0x480 [btrfs]
Feb  1 01:40:38 server kernel: [172867.499556] Code: fd ff ff e8 d1 b1 9f c8 65 
48 8b 04 25 c0 7b 01 00 48 89 45 b8 49 8b 84 24 f0 fd ff ff 48 85 c0 74 55 4d 
8b b4 24 f8 fd ff ff  41 80 66

[Kernel-packages] [Bug 1959665] Re: linux-image-9.4.0-97.110 freezes by accessing cifs shares

I tried now also with kernel 5.4.0-96 #109. As Sebastian says: This also
works stable.

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

Title:
  linux-image-9.4.0-97.110 freezes by accessing cifs shares

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 20.04 with kernel image 9.4.0-97.110 randomly freezes when we
  access cifs shares. The system needs a hard reset after the freeze.

  The previous kernel image (5.4.0-96.109) does not show this behavior.
  Multiple Ubuntu 20.04 systems running on kernel image 9.4.0-97.110 are
  affected on our sites.

  The cifs shares are accessed via autofs using Kerberos authentication.

  The following info is the only error message we could actively catch
  on a different system before the system was frozen:

  general protection fault:  [#3] SMP PTI
  CPU: 0 PID: 21294 Comm: automount Tainted: G  DOE 
5.4.0-97-generic #110-Ubuntu
  Hardware name: Dell Inc. Precision 7530/03RV2M, BIOS 1.14.4 10/21/2020
  RIP: 0010:kmem_cache_alloc_trace+0x8c/0x240
  Code: 08 65 4c 03 05 1d e8 f7 6e 49 83 78 10 00 4d 8b 38 0f 84 92 01 00 00 4d 
85 ff 0f 84 89 01 00 00 41 8b 41 20 49 8b 39 4c 01 f8 <48> 8b 18 48 89 c1 49 33 
99 70 01 00 00 4c 89 f8 48 0f c9 48 31 cb
  RSP: 0018:a6ca860f7ba0 EFLAGS: 00010286
  RAX: fdd44d7c219190e1 RBX:  RCX: 
  RDX: d558 RSI: 0cc0 RDI: 00035060
  RBP: a6ca860f7bd0 R08: 99233c035060 R09: 992338c079c0
  R10: 0001 R11: 0004 R12: 0cc0
  R13: 000b R14: 992338c079c0 R15: fdd44d7c219190e1
  FS:  7fdc24e29700() GS:99233c00() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7f15a80ee010 CR3: 0007e36b2006 CR4: 003606f0
  Call Trace:
   ? proc_self_get_link+0x70/0xd0
   proc_self_get_link+0x70/0xd0
   link_path_walk.part.0+0x478/0x550
   ? trailing_symlink+0x1d1/0x280
   path_openat+0xb7/0x290
   do_filp_open+0x91/0x100
   ? unuse_pde+0x30/0x30
   do_sys_open+0x17e/0x290
   __x64_sys_openat+0x20/0x30
   __orig_openat+0x71/0xc0 [eset_rtp]
   ? __switch_to_asm+0x40/0x70
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   ? __x64_sys_futex+0x13f/0x170
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   __x64_sys_ertp_openat+0x29/0x60 [eset_rtp]
   do_syscall_64+0x57/0x190
   entry_SYSCALL_64_after_hwframe+0x44/0xa9
  RIP: 0033:0x7fdc28a41f24
  Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 
48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 
44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44
  RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101
  RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24
   ? unuse_pde+0x30/0x30
   do_sys_open+0x17e/0x290
   __x64_sys_openat+0x20/0x30
   __orig_openat+0x71/0xc0 [eset_rtp]
   ? __switch_to_asm+0x40/0x70
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   ? __x64_sys_futex+0x13f/0x170
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   __x64_sys_ertp_openat+0x29/0x60 [eset_rtp]
   do_syscall_64+0x57/0x190
   entry_SYSCALL_64_after_hwframe+0x44/0xa9
  RIP: 0033:0x7fdc28a41f24
  Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 
48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 
44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44
  RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101
  RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24
  RDX: 0008 RSI: 564d4410a8c8 RDI: ff9c
  RBP: 564d4410a8c8 R08:  R09: 0001
  R10:  R11: 0293 R12: 0008
  R13: 564d4410e28a R14: 7fdc24e25b40 R15: 7fdc24e28fc0
  Modules linked in: cmac nls_utf8 cifs fscache libdes ccm vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) eset_rtp(OE) xt_conntrack xt_MASQUERADE 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter 
iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ip>
   snd_seq_midi coretemp snd_seq_midi_event snd_rawmidi kvm_intel snd_seq kvm 
dell_wmi snd_seq_device rapl dell_smbios snd_timer dcdbas intel_cstate 
input_leds iwlwifi serio_raw snd intel_wmi_thunderbolt rtsx_pci_ms 
dell_wmi_descriptor wmi_bmof processor_thermal_device ucsi_acp>
   pinctrl_cannonlake video pinctrl_intel
  ---[ end trace 80828f22da45a19b ]---
  RIP: 0010:__slab_free+0x199/0x360
  Code: 00 48 89 c7 fa 66 0f 1f 44 00 00 f0 49 0f ba 2c 24 00 72 79 4d 3b 6c 24 
20 74 11 49 0f ba 34 24 00 57 9d 0f 1f 44 00 00 eb 9f <0f> 0b 49 3b 5c 24 28 75 
e8 48 8b 44

[Kernel-packages] [Bug 1959665] Re: linux-image-9.4.0-97.110 freezes by accessing cifs shares

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

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

Title:
  linux-image-9.4.0-97.110 freezes by accessing cifs shares

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 20.04 with kernel image 9.4.0-97.110 randomly freezes when we
  access cifs shares. The system needs a hard reset after the freeze.

  The previous kernel image (5.4.0-96.109) does not show this behavior.
  Multiple Ubuntu 20.04 systems running on kernel image 9.4.0-97.110 are
  affected on our sites.

  The cifs shares are accessed via autofs using Kerberos authentication.

  The following info is the only error message we could actively catch
  on a different system before the system was frozen:

  general protection fault:  [#3] SMP PTI
  CPU: 0 PID: 21294 Comm: automount Tainted: G  DOE 
5.4.0-97-generic #110-Ubuntu
  Hardware name: Dell Inc. Precision 7530/03RV2M, BIOS 1.14.4 10/21/2020
  RIP: 0010:kmem_cache_alloc_trace+0x8c/0x240
  Code: 08 65 4c 03 05 1d e8 f7 6e 49 83 78 10 00 4d 8b 38 0f 84 92 01 00 00 4d 
85 ff 0f 84 89 01 00 00 41 8b 41 20 49 8b 39 4c 01 f8 <48> 8b 18 48 89 c1 49 33 
99 70 01 00 00 4c 89 f8 48 0f c9 48 31 cb
  RSP: 0018:a6ca860f7ba0 EFLAGS: 00010286
  RAX: fdd44d7c219190e1 RBX:  RCX: 
  RDX: d558 RSI: 0cc0 RDI: 00035060
  RBP: a6ca860f7bd0 R08: 99233c035060 R09: 992338c079c0
  R10: 0001 R11: 0004 R12: 0cc0
  R13: 000b R14: 992338c079c0 R15: fdd44d7c219190e1
  FS:  7fdc24e29700() GS:99233c00() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7f15a80ee010 CR3: 0007e36b2006 CR4: 003606f0
  Call Trace:
   ? proc_self_get_link+0x70/0xd0
   proc_self_get_link+0x70/0xd0
   link_path_walk.part.0+0x478/0x550
   ? trailing_symlink+0x1d1/0x280
   path_openat+0xb7/0x290
   do_filp_open+0x91/0x100
   ? unuse_pde+0x30/0x30
   do_sys_open+0x17e/0x290
   __x64_sys_openat+0x20/0x30
   __orig_openat+0x71/0xc0 [eset_rtp]
   ? __switch_to_asm+0x40/0x70
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   ? __x64_sys_futex+0x13f/0x170
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   __x64_sys_ertp_openat+0x29/0x60 [eset_rtp]
   do_syscall_64+0x57/0x190
   entry_SYSCALL_64_after_hwframe+0x44/0xa9
  RIP: 0033:0x7fdc28a41f24
  Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 
48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 
44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44
  RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101
  RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24
   ? unuse_pde+0x30/0x30
   do_sys_open+0x17e/0x290
   __x64_sys_openat+0x20/0x30
   __orig_openat+0x71/0xc0 [eset_rtp]
   ? __switch_to_asm+0x40/0x70
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   ? __x64_sys_futex+0x13f/0x170
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   __x64_sys_ertp_openat+0x29/0x60 [eset_rtp]
   do_syscall_64+0x57/0x190
   entry_SYSCALL_64_after_hwframe+0x44/0xa9
  RIP: 0033:0x7fdc28a41f24
  Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 
48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 
44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44
  RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101
  RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24
  RDX: 0008 RSI: 564d4410a8c8 RDI: ff9c
  RBP: 564d4410a8c8 R08:  R09: 0001
  R10:  R11: 0293 R12: 0008
  R13: 564d4410e28a R14: 7fdc24e25b40 R15: 7fdc24e28fc0
  Modules linked in: cmac nls_utf8 cifs fscache libdes ccm vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) eset_rtp(OE) xt_conntrack xt_MASQUERADE 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter 
iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ip>
   snd_seq_midi coretemp snd_seq_midi_event snd_rawmidi kvm_intel snd_seq kvm 
dell_wmi snd_seq_device rapl dell_smbios snd_timer dcdbas intel_cstate 
input_leds iwlwifi serio_raw snd intel_wmi_thunderbolt rtsx_pci_ms 
dell_wmi_descriptor wmi_bmof processor_thermal_device ucsi_acp>
   pinctrl_cannonlake video pinctrl_intel
  ---[ end trace 80828f22da45a19b ]---
  RIP: 0010:__slab_free+0x199/0x360
  Code: 00 48 89 c7 fa 66 0f 1f 44 00 00 f0 49 0f ba 2c 24 00 72 79 4d 3b 6c 24 
20 74 11 49 0f ba 34 24 00 57 9d 0f 1f 44 00 0

[Kernel-packages] [Bug 1959681] Re: mic not working on HP-EliteBook-830-G7

2022-02-01 Thread Dariusz Gadomski

The packages I used for testing are available at ppa:dgadomski/firmware-
mic

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

Title:
  mic not working on HP-EliteBook-830-G7

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

Bug description:
  There is no audio input from the built-in mic available on Bionic &
  Focal on certain intel audio hw (00:1f.3 Multimedia audio controller
  [0401]: Intel Corporation Device [8086:02c8]) despite trying different
  kernel cmdline options (snd_hda_intel.dmic_detect=0 or
  snd_intel_dspcfg.dsp_driver=1).

  The behavior was similar on Bionic and Focal - no mic listed in 
alsa/pulseaudio mixers. Additionally the following can be found in the kernel 
log:
sof-audio-pci :00:1f.3: Digital mics found on Skylake+ platform, using 
SOF driver
sof-audio-pci :00:1f.3: enabling device ( -> 0002)
sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found

  The situation is different on impish - on this release the mic is
  available out of the box.

  I made a simple test of overwriting sof files inside Focal's linux-
  firmware package with the contents of firmware-sof-signed package from
  impish finding it solved the issue without any trace of errors in the
  logs.

  The same approach did not work on Bionic (despite similar kernel versions 
used in both 5.4.0) - due to HWE). These are some excerpts from Bionic 
launching impish SOF firmware:
   sof-audio-pci :00:1f.3: Firmware: ABI 3:17:0 Kernel ABI 3:10:0
   sof-audio-pci :00:1f.3: warn: FW ABI is more recent than kernel
   sof-audio-pci :00:1f.3: firmware boot complete
   sof-audio-pci :00:1f.3: Topology: ABI 3:17:0 Kernel ABI 3:10:0
   sof-audio-pci :00:1f.3: warn: topology ABI is more recent than kernel
   sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp3 Tx not handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name codec0_in not handled
   sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp2 Tx not handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name codec1_in not handled
   sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp1 Tx not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name codec0_out not 
handled
   sof-audio-pci :00:1f.3: warning: widget type 7 name Analog CPU Playback 
not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name codec1_out not 
handled
   sof-audio-pci :00:1f.3: warning: widget type 7 name Digital CPU Playback 
not handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name codec2_in not handled
   sof-audio-pci :00:1f.3: warning: widget type 7 name Alt Analog CPU 
Playback not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name codec2_out not 
handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name Analog CPU Capture 
not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp1_out not 
handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name Digital CPU Capture 
not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp2_out not 
handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name Alt Analog CPU 
Capture not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp3_out not 
handled

  [ Test Plan ]
  1. Launch Ubuntu desktop on affected hardware.
  2. Open audio mixer (e.g. pulsemixer).
  3. Look for built-in audio input (e.g. Built-in Audio Analog Stereo).

  Expected result:
  Built-in mic is available for use.

  Actual result:
  Built-in mic is missing.

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


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

[Kernel-packages] [Bug 1959681] [NEW] mic not working on HP-EliteBook-830-G7

2022-02-01 Thread Dariusz Gadomski

Public bug reported:

There is no audio input from the built-in mic available on Bionic &
Focal on certain intel audio hw (00:1f.3 Multimedia audio controller
[0401]: Intel Corporation Device [8086:02c8]) despite trying different
kernel cmdline options (snd_hda_intel.dmic_detect=0 or
snd_intel_dspcfg.dsp_driver=1).

The behavior was similar on Bionic and Focal - no mic listed in alsa/pulseaudio 
mixers. Additionally the following can be found in the kernel log:
  sof-audio-pci :00:1f.3: Digital mics found on Skylake+ platform, using 
SOF driver
  sof-audio-pci :00:1f.3: enabling device ( -> 0002)
  sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found

The situation is different on impish - on this release the mic is
available out of the box.

I made a simple test of overwriting sof files inside Focal's linux-
firmware package with the contents of firmware-sof-signed package from
impish finding it solved the issue without any trace of errors in the
logs.

The same approach did not work on Bionic (despite similar kernel versions used 
in both 5.4.0) - due to HWE). These are some excerpts from Bionic launching 
impish SOF firmware:
 sof-audio-pci :00:1f.3: Firmware: ABI 3:17:0 Kernel ABI 3:10:0
 sof-audio-pci :00:1f.3: warn: FW ABI is more recent than kernel
 sof-audio-pci :00:1f.3: firmware boot complete
 sof-audio-pci :00:1f.3: Topology: ABI 3:17:0 Kernel ABI 3:10:0
 sof-audio-pci :00:1f.3: warn: topology ABI is more recent than kernel
 sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp3 Tx not handled
 sof-audio-pci :00:1f.3: warning: widget type 0 name codec0_in not handled
 sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp2 Tx not handled
 sof-audio-pci :00:1f.3: warning: widget type 0 name codec1_in not handled
 sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp1 Tx not handled
 sof-audio-pci :00:1f.3: warning: widget type 1 name codec0_out not handled
 sof-audio-pci :00:1f.3: warning: widget type 7 name Analog CPU Playback 
not handled
 sof-audio-pci :00:1f.3: warning: widget type 1 name codec1_out not handled
 sof-audio-pci :00:1f.3: warning: widget type 7 name Digital CPU Playback 
not handled
 sof-audio-pci :00:1f.3: warning: widget type 0 name codec2_in not handled
 sof-audio-pci :00:1f.3: warning: widget type 7 name Alt Analog CPU 
Playback not handled
 sof-audio-pci :00:1f.3: warning: widget type 1 name codec2_out not handled
 sof-audio-pci :00:1f.3: warning: widget type 0 name Analog CPU Capture not 
handled
 sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp1_out not handled
 sof-audio-pci :00:1f.3: warning: widget type 0 name Digital CPU Capture 
not handled
 sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp2_out not handled
 sof-audio-pci :00:1f.3: warning: widget type 0 name Alt Analog CPU Capture 
not handled
 sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp3_out not handled

[ Test Plan ]
1. Launch Ubuntu desktop on affected hardware.
2. Open audio mixer (e.g. pulsemixer).
3. Look for built-in audio input (e.g. Built-in Audio Analog Stereo).

Expected result:
Built-in mic is available for use.

Actual result:
Built-in mic is missing.

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: linux-firmware (Ubuntu Bionic)
 Importance: Medium
 Status: New

** Affects: linux-firmware (Ubuntu Focal)
 Importance: Medium
 Status: New


** Tags: sts

** Changed in: linux-firmware (Ubuntu)
   Status: New => Fix Released

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

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

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

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

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

Title:
  mic not working on HP-EliteBook-830-G7

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

Bug description:
  There is no audio input from the built-in mic available on Bionic &
  Focal on certain intel audio hw (00:1f.3 Multimedia audio controller
  [0401]: Intel Corporation Device [8086:02c8]) despite trying different
  kernel cmdline options (snd_hda_intel.dmic_detect=0 or
  snd_intel_dspcfg.dsp_driver=1).

  The behavior was similar on Bionic and Focal - no mic listed in 
alsa/pulseaudio mixers. Additionally the following can be found in the kernel 
log:
sof-audio-pci :00:1f.3: Digital mics found on Skylake+ platform, using 
SOF driver
sof-audio-pci :00:1f.3: enabling device (

[Kernel-packages] [Bug 1959680] [NEW] Touchpad doesn't work at all

2022-02-01 Thread Kateryna

Public bug reported:

As in summary. Didn't work also during installation process. External mouse 
works fine.
/proc/bus/input/devices in attachments

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-42-generic 5.4.0-42.46
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  rozanovk   1749 F pulseaudio
 /dev/snd/controlC0:  rozanovk   1749 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb  1 16:11:39 2022
InstallationDate: Installed on 2022-02-01 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b6d9 Chicony Electronics Co., Ltd Integrated Camera
 Bus 001 Device 004: ID 0cf3:e500 Qualcomm Atheros Communications 
 Bus 001 Device 002: ID 1bcf:0005 Sunplus Innovation Technology Inc. Optical 
Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 81LK
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=1ff48e02-38c1-45a6-bfc8-2c3870cdd08e ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-42-generic N/A
 linux-backports-modules-5.4.0-42-generic  N/A
 linux-firmware1.187.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/13/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: BGCN30WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad L340-15IRH Gaming
dmi.modalias: 
dmi:bvnLENOVO:bvrBGCN30WW:bd05/13/2020:svnLENOVO:pn81LK:pvrIdeaPadL340-15IRHGaming:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPadL340-15IRHGaming:
dmi.product.family: IdeaPad L340-15IRH Gaming
dmi.product.name: 81LK
dmi.product.sku: LENOVO_MT_81LK_BU_idea_FM_IdeaPad L340-15IRH Gaming
dmi.product.version: IdeaPad L340-15IRH Gaming
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal third-party-packages

** Attachment added: "devices"
   https://bugs.launchpad.net/bugs/1959680/+attachment/5558602/+files/devices

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

Title:
  Touchpad doesn't work at all

Status in linux package in Ubuntu:
  New

Bug description:
  As in summary. Didn't work also during installation process. External mouse 
works fine.
  /proc/bus/input/devices in attachments

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rozanovk   1749 F pulseaudio
   /dev/snd/controlC0:  rozanovk   1749 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  1 16:11:39 2022
  InstallationDate: Installed on 2022-02-01 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b6d9 Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 001 Device 004: ID 0cf3:e500 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 1bcf:0005 Sunplus Innovation Technology Inc. Optical 
Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81LK
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=1ff48e02-38c1-45a6-bfc8-2c3870cdd08e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BGCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad L340-15IRH Gaming
  dmi.modalias: 
dmi:bvnLENOVO:bvrBGCN30WW:bd05/13/2020:svnLENOVO:pn81LK:pvrIdeaPadL340-15IRHGaming:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPadL

[Kernel-packages] [Bug 1959665] Re: linux-image-9.4.0-97.110 freezes by accessing cifs shares

After rolling back to 5.4.0-80 #90 (thanks to Puppet ;) the machines are
stable again.

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

Title:
  linux-image-9.4.0-97.110 freezes by accessing cifs shares

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 with kernel image 9.4.0-97.110 randomly freezes when we
  access cifs shares. The system needs a hard reset after the freeze.

  The previous kernel image (5.4.0-96.109) does not show this behavior.
  Multiple Ubuntu 20.04 systems running on kernel image 9.4.0-97.110 are
  affected on our sites.

  The cifs shares are accessed via autofs using Kerberos authentication.

  The following info is the only error message we could actively catch
  on a different system before the system was frozen:

  general protection fault:  [#3] SMP PTI
  CPU: 0 PID: 21294 Comm: automount Tainted: G  DOE 
5.4.0-97-generic #110-Ubuntu
  Hardware name: Dell Inc. Precision 7530/03RV2M, BIOS 1.14.4 10/21/2020
  RIP: 0010:kmem_cache_alloc_trace+0x8c/0x240
  Code: 08 65 4c 03 05 1d e8 f7 6e 49 83 78 10 00 4d 8b 38 0f 84 92 01 00 00 4d 
85 ff 0f 84 89 01 00 00 41 8b 41 20 49 8b 39 4c 01 f8 <48> 8b 18 48 89 c1 49 33 
99 70 01 00 00 4c 89 f8 48 0f c9 48 31 cb
  RSP: 0018:a6ca860f7ba0 EFLAGS: 00010286
  RAX: fdd44d7c219190e1 RBX:  RCX: 
  RDX: d558 RSI: 0cc0 RDI: 00035060
  RBP: a6ca860f7bd0 R08: 99233c035060 R09: 992338c079c0
  R10: 0001 R11: 0004 R12: 0cc0
  R13: 000b R14: 992338c079c0 R15: fdd44d7c219190e1
  FS:  7fdc24e29700() GS:99233c00() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7f15a80ee010 CR3: 0007e36b2006 CR4: 003606f0
  Call Trace:
   ? proc_self_get_link+0x70/0xd0
   proc_self_get_link+0x70/0xd0
   link_path_walk.part.0+0x478/0x550
   ? trailing_symlink+0x1d1/0x280
   path_openat+0xb7/0x290
   do_filp_open+0x91/0x100
   ? unuse_pde+0x30/0x30
   do_sys_open+0x17e/0x290
   __x64_sys_openat+0x20/0x30
   __orig_openat+0x71/0xc0 [eset_rtp]
   ? __switch_to_asm+0x40/0x70
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   ? __x64_sys_futex+0x13f/0x170
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   __x64_sys_ertp_openat+0x29/0x60 [eset_rtp]
   do_syscall_64+0x57/0x190
   entry_SYSCALL_64_after_hwframe+0x44/0xa9
  RIP: 0033:0x7fdc28a41f24
  Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 
48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 
44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44
  RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101
  RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24
   ? unuse_pde+0x30/0x30
   do_sys_open+0x17e/0x290
   __x64_sys_openat+0x20/0x30
   __orig_openat+0x71/0xc0 [eset_rtp]
   ? __switch_to_asm+0x40/0x70
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   ? __x64_sys_futex+0x13f/0x170
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   __x64_sys_ertp_openat+0x29/0x60 [eset_rtp]
   do_syscall_64+0x57/0x190
   entry_SYSCALL_64_after_hwframe+0x44/0xa9
  RIP: 0033:0x7fdc28a41f24
  Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 
48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 
44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44
  RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101
  RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24
  RDX: 0008 RSI: 564d4410a8c8 RDI: ff9c
  RBP: 564d4410a8c8 R08:  R09: 0001
  R10:  R11: 0293 R12: 0008
  R13: 564d4410e28a R14: 7fdc24e25b40 R15: 7fdc24e28fc0
  Modules linked in: cmac nls_utf8 cifs fscache libdes ccm vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) eset_rtp(OE) xt_conntrack xt_MASQUERADE 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter 
iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ip>
   snd_seq_midi coretemp snd_seq_midi_event snd_rawmidi kvm_intel snd_seq kvm 
dell_wmi snd_seq_device rapl dell_smbios snd_timer dcdbas intel_cstate 
input_leds iwlwifi serio_raw snd intel_wmi_thunderbolt rtsx_pci_ms 
dell_wmi_descriptor wmi_bmof processor_thermal_device ucsi_acp>
   pinctrl_cannonlake video pinctrl_intel
  ---[ end trace 80828f22da45a19b ]---
  RIP: 0010:__slab_free+0x199/0x360
  Code: 00 48 89 c7 fa 66 0f 1f 44 00 00 f0 49 0f ba 2c 24 00 72 79 4d 3b 6c 24 
20 74 11 49 0f ba 34 24 00 57 9d 0f 1f 44 00 00 eb 9f <0f> 0b 49 3b 5c 24 28 75 
e8 48 8b 44 24 28

[Kernel-packages] [Bug 1959665] Re: linux-image-9.4.0-97.110 freezes by accessing cifs shares

We can confirm that. Our machines (8 VMs on a VSphere cluster) also
freeze after the update to 5.4.0-97 #100.

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

Title:
  linux-image-9.4.0-97.110 freezes by accessing cifs shares

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 with kernel image 9.4.0-97.110 randomly freezes when we
  access cifs shares. The system needs a hard reset after the freeze.

  The previous kernel image (5.4.0-96.109) does not show this behavior.
  Multiple Ubuntu 20.04 systems running on kernel image 9.4.0-97.110 are
  affected on our sites.

  The cifs shares are accessed via autofs using Kerberos authentication.

  The following info is the only error message we could actively catch
  on a different system before the system was frozen:

  general protection fault:  [#3] SMP PTI
  CPU: 0 PID: 21294 Comm: automount Tainted: G  DOE 
5.4.0-97-generic #110-Ubuntu
  Hardware name: Dell Inc. Precision 7530/03RV2M, BIOS 1.14.4 10/21/2020
  RIP: 0010:kmem_cache_alloc_trace+0x8c/0x240
  Code: 08 65 4c 03 05 1d e8 f7 6e 49 83 78 10 00 4d 8b 38 0f 84 92 01 00 00 4d 
85 ff 0f 84 89 01 00 00 41 8b 41 20 49 8b 39 4c 01 f8 <48> 8b 18 48 89 c1 49 33 
99 70 01 00 00 4c 89 f8 48 0f c9 48 31 cb
  RSP: 0018:a6ca860f7ba0 EFLAGS: 00010286
  RAX: fdd44d7c219190e1 RBX:  RCX: 
  RDX: d558 RSI: 0cc0 RDI: 00035060
  RBP: a6ca860f7bd0 R08: 99233c035060 R09: 992338c079c0
  R10: 0001 R11: 0004 R12: 0cc0
  R13: 000b R14: 992338c079c0 R15: fdd44d7c219190e1
  FS:  7fdc24e29700() GS:99233c00() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7f15a80ee010 CR3: 0007e36b2006 CR4: 003606f0
  Call Trace:
   ? proc_self_get_link+0x70/0xd0
   proc_self_get_link+0x70/0xd0
   link_path_walk.part.0+0x478/0x550
   ? trailing_symlink+0x1d1/0x280
   path_openat+0xb7/0x290
   do_filp_open+0x91/0x100
   ? unuse_pde+0x30/0x30
   do_sys_open+0x17e/0x290
   __x64_sys_openat+0x20/0x30
   __orig_openat+0x71/0xc0 [eset_rtp]
   ? __switch_to_asm+0x40/0x70
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   ? __x64_sys_futex+0x13f/0x170
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   __x64_sys_ertp_openat+0x29/0x60 [eset_rtp]
   do_syscall_64+0x57/0x190
   entry_SYSCALL_64_after_hwframe+0x44/0xa9
  RIP: 0033:0x7fdc28a41f24
  Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 
48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 
44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44
  RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101
  RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24
   ? unuse_pde+0x30/0x30
   do_sys_open+0x17e/0x290
   __x64_sys_openat+0x20/0x30
   __orig_openat+0x71/0xc0 [eset_rtp]
   ? __switch_to_asm+0x40/0x70
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   ? __x64_sys_futex+0x13f/0x170
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   ? __switch_to_asm+0x34/0x70
   ? __switch_to_asm+0x40/0x70
   __x64_sys_ertp_openat+0x29/0x60 [eset_rtp]
   do_syscall_64+0x57/0x190
   entry_SYSCALL_64_after_hwframe+0x44/0xa9
  RIP: 0033:0x7fdc28a41f24
  Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 
48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 
44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44
  RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101
  RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24
  RDX: 0008 RSI: 564d4410a8c8 RDI: ff9c
  RBP: 564d4410a8c8 R08:  R09: 0001
  R10:  R11: 0293 R12: 0008
  R13: 564d4410e28a R14: 7fdc24e25b40 R15: 7fdc24e28fc0
  Modules linked in: cmac nls_utf8 cifs fscache libdes ccm vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) eset_rtp(OE) xt_conntrack xt_MASQUERADE 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter 
iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ip>
   snd_seq_midi coretemp snd_seq_midi_event snd_rawmidi kvm_intel snd_seq kvm 
dell_wmi snd_seq_device rapl dell_smbios snd_timer dcdbas intel_cstate 
input_leds iwlwifi serio_raw snd intel_wmi_thunderbolt rtsx_pci_ms 
dell_wmi_descriptor wmi_bmof processor_thermal_device ucsi_acp>
   pinctrl_cannonlake video pinctrl_intel
  ---[ end trace 80828f22da45a19b ]---
  RIP: 0010:__slab_free+0x199/0x360
  Code: 00 48 89 c7 fa 66 0f 1f 44 00 00 f0 49 0f ba 2c 24 00 72 79 4d 3b 6c 24 
20 74 11 49 0f ba 34 24 00 57 9d 0f 1f 44 00 00 eb 9f <0f> 0b 49 3b 5c 24 2

[Kernel-packages] [Bug 1909005] Re: Ubuntu does not resume (wake up) from suspend

2022-02-01 Thread Edoardo Fiocchi

Also affects my Dell Inspiron 5415, kernel version 5.13.0-28 (dual-booted with 
Windows).
In my case, after selecting "Sleep", the screen turns off immediately and the 
computer seems turned off. However, it will NOT wake up or reboot. In fact, I 
have tried to press and hold the power button for several seconds, trying to 
force-shutdown it, with no effects. Also tried the Alt+PrintScr+REISUB method 
with no results.
The only way for me to shut it down is to physically remove the battery and 
reinsert 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/1909005

Title:
  Ubuntu does not resume (wake up) from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Whenever Ubuntu gets into suspend state, I cannot wake it up. 
  -Keystrokes start the fans but screen does not turn on and Ubuntu still seems 
to be suspended because in my teamviewer account the computer is still offline.
  -Power button clicks do not help
  -I always have to turn off computer by holding power button and then turn it 
on again.

  The only kernel that works is the following: "linux-
  image-5.0.0-1070-oem-osp1". But with this old kernel I run into
  different problems.

  I have the latest BIOS version from Dell (released 2020-11-27) and the
  latest updates in Ubuntu 20.04.

  I will post logs during suspend and important logs (found in Logs gui
  tool)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-58-generic 5.4.0-58.64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philip 2340 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 22 13:59:14 2020
  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-20190418-59+beaver-osp1-loras+X18
  InstallationDate: Installed on 2019-12-04 (383 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3593
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep 
tsc=reliable quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-generic N/A
   linux-backports-modules-5.4.0-58-generic  N/A
   linux-firmware1.187.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago)
  dmi.bios.date: 11/13/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 04N9HV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3593
  dmi.product.sku: 0979
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1958289] Re: [amdgpu] Hang on shutdown: systemd-udevd ... Worker ... processing SEQNUM=... is taking a long time

2022-02-01 Thread Antonio Lo Pinto

Hi,

after the today's (02/01/22) updates my computer can shutdown again.

Thank you for your time!

The installed packages are listed below:

2022-02-01 07:44:37 startup archives unpack
2022-02-01 07:44:37 upgrade libsmbclient:amd64 2:4.13.14+dfsg-0ubuntu0.20.04.4 2
:4.13.17~dfsg-0ubuntu0.21.04.1
2022-02-01 07:44:37 status triggers-pending libc-bin:amd64 2.31-0ubuntu9.2
2022-02-01 07:44:37 status half-configured libsmbclient:amd64 2:4.13.14+dfsg-0ub
untu0.20.04.4
2022-02-01 07:44:37 status unpacked libsmbclient:amd64 2:4.13.14+dfsg-0ubuntu0.2
0.04.4
2022-02-01 07:44:37 status half-installed libsmbclient:amd64 2:4.13.14+dfsg-0ubu
ntu0.20.04.4
2022-02-01 07:44:37 status triggers-pending man-db:amd64 2.9.1-1
2022-02-01 07:44:37 status unpacked libsmbclient:amd64 2:4.13.17~dfsg-0ubuntu0.2
1.04.1
2022-02-01 07:44:37 upgrade libwbclient0:amd64 2:4.13.14+dfsg-0ubuntu0.20.04.4 2
:4.13.17~dfsg-0ubuntu0.21.04.1
2022-02-01 07:44:37 status half-configured libwbclient0:amd64 2:4.13.14+dfsg-0ub
untu0.20.04.4
2022-02-01 07:44:37 status unpacked libwbclient0:amd64 2:4.13.14+dfsg-0ubuntu0.2
0.04.4
2022-02-01 07:44:37 status half-installed libwbclient0:amd64 2:4.13.14+dfsg-0ubu
ntu0.20.04.4
2022-02-01 07:44:37 status unpacked libwbclient0:amd64 2:4.13.17~dfsg-0ubuntu0.2
1.04.1
2022-02-01 07:44:37 upgrade samba-libs:amd64 2:4.13.14+dfsg-0ubuntu0.20.04.4 2:4
.13.17~dfsg-0ubuntu0.21.04.1
2022-02-01 07:44:37 status half-configured samba-libs:amd64 2:4.13.14+dfsg-0ubun
tu0.20.04.4
2022-02-01 07:44:37 status unpacked samba-libs:amd64 2:4.13.14+dfsg-0ubuntu0.20.
04.4
2022-02-01 07:44:37 status half-installed samba-libs:amd64 2:4.13.14+dfsg-0ubunt
u0.20.04.4
2022-02-01 07:44:37 status unpacked samba-libs:amd64 2:4.13.17~dfsg-0ubuntu0.21.
04.1
2022-02-01 07:44:37 install linux-modules-5.13.0-28-generic:amd64  5.13.0-
28.31~20.04.1
2022-02-01 07:44:37 status half-installed linux-modules-5.13.0-28-generic:amd64 
5.13.0-28.31~20.04.1
2022-02-01 07:44:39 status unpacked linux-modules-5.13.0-28-generic:amd64 5.13.0
-28.31~20.04.1
2022-02-01 07:44:39 install linux-image-5.13.0-28-generic:amd64  5.13.0-28
.31~20.04.1
2022-02-01 07:44:39 status half-installed linux-image-5.13.0-28-generic:amd64 5.
13.0-28.31~20.04.1
2022-02-01 07:44:39 status unpacked linux-image-5.13.0-28-generic:amd64 5.13.0-2
8.31~20.04.1
2022-02-01 07:44:39 install linux-modules-extra-5.13.0-28-generic:amd64  5
.13.0-28.31~20.04.1
2022-02-01 07:44:39 status half-installed linux-modules-extra-5.13.0-28-generic:
amd64 5.13.0-28.31~20.04.1
2022-02-01 07:44:43 status unpacked linux-modules-extra-5.13.0-28-generic:amd64 
5.13.0-28.31~20.04.1
2022-02-01 07:44:43 upgrade linux-generic-hwe-20.04:amd64 5.13.0.27.29~20.04.13 
5.13.0.28.31~20.04.15
2022-02-01 07:44:43 status half-configured linux-generic-hwe-20.04:amd64 5.13.0.
27.29~20.04.13
2022-02-01 07:44:43 status unpacked linux-generic-hwe-20.04:amd64 5.13.0.27.29~2
0.04.13
2022-02-01 07:44:43 status half-installed linux-generic-hwe-20.04:amd64 5.13.0.2
7.29~20.04.13
2022-02-01 07:44:43 status unpacked linux-generic-hwe-20.04:amd64 5.13.0.28.31~2
0.04.15
2022-02-01 07:44:43 upgrade linux-image-generic-hwe-20.04:amd64 5.13.0.27.29~20.
04.13 5.13.0.28.31~20.04.15
2022-02-01 07:44:43 status half-configured linux-image-generic-hwe-20.04:amd64 5
.13.0.27.29~20.04.13
2022-02-01 07:44:43 status unpacked linux-image-generic-hwe-20.04:amd64 5.13.0.2
7.29~20.04.13
2022-02-01 07:44:43 status half-installed linux-image-generic-hwe-20.04:amd64 5.
13.0.27.29~20.04.13
2022-02-01 07:44:43 status unpacked linux-image-generic-hwe-20.04:amd64 5.13.0.2
8.31~20.04.15
2022-02-01 07:44:43 install linux-hwe-5.13-headers-5.13.0-28:all  5.13.0-2
8.31~20.04.1
2022-02-01 07:44:43 status half-installed linux-hwe-5.13-headers-5.13.0-28:all 5
.13.0-28.31~20.04.1
2022-02-01 07:44:46 status unpacked linux-hwe-5.13-headers-5.13.0-28:all 5.13.0-
28.31~20.04.1
2022-02-01 07:44:46 install linux-headers-5.13.0-28-generic:amd64  5.13.0-
28.31~20.04.1
2022-02-01 07:44:46 status half-installed linux-headers-5.13.0-28-generic:amd64 
5.13.0-28.31~20.04.1
2022-02-01 07:44:47 status unpacked linux-headers-5.13.0-28-generic:amd64 5.13.0
-28.31~20.04.1
2022-02-01 07:44:47 upgrade linux-headers-generic-hwe-20.04:amd64 5.13.0.27.29~2
0.04.13 5.13.0.28.31~20.04.15
2022-02-01 07:44:47 status half-configured linux-headers-generic-hwe-20.04:amd64
 5.13.0.27.29~20.04.13
2022-02-01 07:44:47 status unpacked linux-headers-generic-hwe-20.04:amd64 5.13.0
.27.29~20.04.13
2022-02-01 07:44:47 status half-installed linux-headers-generic-hwe-20.04:amd64 
5.13.0.27.29~20.04.13
2022-02-01 07:44:47 status unpacked linux-headers-generic-hwe-20.04:amd64 5.13.0
.28.31~20.04.15
2022-02-01 07:44:47 startup packages configure
2022-02-01 07:44:47 configure libwbclient0:amd64 2:4.13.17~dfsg-0ubuntu0.21.04.1
 
2022-02-01 07:44:47 status unpacked libwbclient0:amd64 2:4.13.17~dfsg-0ubuntu0.2
1.04.1
2022-02-01 07:44:47 status half-configured libwbclient0:amd64 2:4.13.17~dfsg-0ub
untu0.21.04.1
2022-02-

[Kernel-packages] [Bug 1958013] Re: System freeze during Shutdown, Restart, or Suspend

2022-02-01 Thread malbo

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

** This bug has been marked a duplicate of bug 1956467
   powerlight stays on after shutdown

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

Title:
  System freeze during Shutdown, Restart, or Suspend

Status in linux-hwe-5.11 package in Ubuntu:
  Confirmed

Bug description:
  Dear developers,
  My system freezes whenever I try to 1) shutdown, 2) restart, or 3) suspend it.

  System gets unresponsive (keyborad, mouse, network - ssh/ping from
  outside), screen turns black. However, non of the actions 1-3 gets
  finished, i.e. my system does not turn off, restart, or sleep. Hw
  reset needed after it.

  It is always reproducible and happens for kernels 
linux-image-5.11.0-41-generic and later.
  Does not happen for kernels linux-image-5.11.0-40-generic and earlier.

  Corresponding Journal sections (5.11.0-40 & 5.11.0-46) attached.

  Any other information or test you need, please let me know.
  Thank you!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  radek  1495 F pulseaudio
   /dev/snd/pcmC1D0p:   radek  1495 F...m pulseaudio
   /dev/snd/controlC0:  radek  1495 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=/dev/disk/by-label/SSD_LinuxSwap
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-46-generic 
root=UUID=1cc747ae-f2db-4733-aa04-be8d4bde050a ro ipv6.disable=1 net.ifnames=0 
nmi_watchdog=0 resume=LABEL=SSD_LinuxSwap no_console_suspend quiet
  ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-46-generic N/A
   linux-backports-modules-5.11.0-46-generic  N/A
   linux-firmware 1.187.25
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.11.0-46-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: False
  dmi.bios.date: 02/13/2019
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.20
  dmi.board.name: FM2A68M-HD+
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To be filled by O.E.M.
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.20:bd02/13/2019:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+: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-hwe-5.11/+bug/1958013/+subscriptions


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

[Kernel-packages] [Bug 1959593] Re: tcm_loop requires '-extras' for EKS optimised AMIs

Patch submitted: https://lists.ubuntu.com/archives/kernel-
team/2022-February/127635.html

** Description changed:

+ SRU Justification
+ 
+ [Impact]
+ 
  Hello,
  
  It seems that although the Azure kernel distribution includes the
  `tcm_loop` module by default, the EKS-optimised image's default kernel
  doesn't, instead including the module in the `linux-kernel-
  extras-$(uname -r)` package.
  
  `tcm_loop` is an incredibly useful package for any storage fabric
  software packages - eg. Ceph, Rook or Ondat. It would be very helpful to
  have it embedded into the default kernel distribution in order to reduce
  friction on installing 'storage fabric' type topologies.
  
  The Ubuntu on EKS images are all listed in https://cloud-
  images.ubuntu.com/docs/aws/eks/ - I'd be happy to provide any
  information necessary to help shave off this extra bit of work required
  to setup such images.
+ 
+ [Fix]
+ 
+ Add tcm_loop.ko to the inclusion list
+ 
+ [Test Case]
+ 
+ Check that linux-modules includes tcp_loop.ko
+ 
+ [Where things could go wrong]
+ 
+ Moving tcm_loop.ko from linux-modules-extra could impact proprietary
+ methods.

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

Title:
  tcm_loop requires '-extras' for EKS optimised AMIs

Status in cloud-images:
  New
Status in linux-aws package in Ubuntu:
  In Progress
Status in linux-aws source package in Focal:
  In Progress
Status in linux-aws source package in Impish:
  In Progress
Status in linux-aws source package in Jammy:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  Hello,

  It seems that although the Azure kernel distribution includes the
  `tcm_loop` module by default, the EKS-optimised image's default kernel
  doesn't, instead including the module in the `linux-kernel-
  extras-$(uname -r)` package.

  `tcm_loop` is an incredibly useful package for any storage fabric
  software packages - eg. Ceph, Rook or Ondat. It would be very helpful
  to have it embedded into the default kernel distribution in order to
  reduce friction on installing 'storage fabric' type topologies.

  The Ubuntu on EKS images are all listed in https://cloud-
  images.ubuntu.com/docs/aws/eks/ - I'd be happy to provide any
  information necessary to help shave off this extra bit of work
  required to setup such images.

  [Fix]

  Add tcm_loop.ko to the inclusion list

  [Test Case]

  Check that linux-modules includes tcp_loop.ko

  [Where things could go wrong]

  Moving tcm_loop.ko from linux-modules-extra could impact proprietary
  methods.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1959593/+subscriptions


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

[Kernel-packages] [Bug 1950720] Re: GSYNC bug regression in 495.44 Ubuntu 21.10

2022-02-01 Thread berglh

Bug persists in beta driver 510.39.01 from NVIDIA website.

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

Title:
GSYNC bug regression in 495.44 Ubuntu 21.10

Status in nvidia-graphics-drivers-470 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-495 package in Ubuntu:
Confirmed

Hardware is:
- NVIDIA GeForce RTX 2080 Super
- Dell 27" S2721DGF G-Sync Compatible monitor
- High quality DisplayPort cable (This was replaced previously under
suspicion)

This issue happens at all refresh rates: 60 Hz, 120 Hz, 144 Hz and 165
Hz.

Prior to upgrading to Ubuntu 21.10, I had upgraded to 495.44 on Ubuntu
21.04 and kernel 5.14.1, and this problem was not present.

I then upgraded to Ubuntu 21.10, and the problem didn't seem to be
present, but as of today I've noticed again.

Let me know if there are any tests you'd like me to try.

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

[Kernel-packages] [Bug 1959593] Re: tcm_loop requires '-extras' for EKS optimised AMIs