[Kernel-packages] [Bug 1952193] Re: NULL pointer dereference at _mod_memcg_state+0x14/0xb0

2021-11-24 Thread Sergey Borodavkin
Link to crash dump
https://drive.google.com/file/d/14FRxK0RKi7HFRYdkQRhyImnS7ZfNuVla/view

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

Title:
  NULL pointer dereference at _mod_memcg_state+0x14/0xb0

Status in linux-meta-hwe-5.4 package in Ubuntu:
  New

Bug description:
  Hello.

  We meet a randomly host kernel panics with same RIP and "BUG: kernel NULL 
pointer dereference".
  At current time affected kernel versions was from 5.4.0-53 to 5.4.0-84.
  For now i have a dmesg log and crash file, but no clue where what to do next.

  

  Environment:
Distributor ID: Ubuntu
Description:Ubuntu 18.04.6 LTS
Release:18.04
Codename:   bionic

  
  Crash report

KERNEL: usr/lib/debug/boot/vmlinux-5.4.0-84-generic  
  DUMPFILE: dump.202111240900  [PARTIAL DUMP]
  CPUS: 24
  DATE: Wed Nov 24 09:00:22 2021
UPTIME: 15 days, 23:17:07
  LOAD AVERAGE: 46.41, 37.67, 30.39
 TASKS: 3071
  NODENAME: cmp20
   RELEASE: 5.4.0-84-generic
   VERSION: #94~18.04.1-Ubuntu SMP Thu Aug 26 23:17:46 UTC 2021
   MACHINE: x86_64  (2299 Mhz)
MEMORY: 255.9 GB
 PANIC: "Oops:  [#1] SMP PTI" (check log for details)
   PID: 2239917
   COMMAND: "CPU 0/KVM"
  TASK: 9bbd9662  [THREAD_INFO: 9bbd9662]
   CPU: 14
 STATE: TASK_RUNNING (PANIC)

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


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


[Kernel-packages] [Bug 1952193] [NEW] NULL pointer dereference at _mod_memcg_state+0x14/0xb0

2021-11-24 Thread Sergey Borodavkin
Public bug reported:

Hello.

We meet a randomly host kernel panics with same RIP and "BUG: kernel NULL 
pointer dereference".
At current time affected kernel versions was from 5.4.0-53 to 5.4.0-84.
For now i have a dmesg log and crash file, but no clue where what to do next.



Environment:
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.6 LTS
  Release:18.04
  Codename:   bionic


Crash report

  KERNEL: usr/lib/debug/boot/vmlinux-5.4.0-84-generic  
DUMPFILE: dump.202111240900  [PARTIAL DUMP]
CPUS: 24
DATE: Wed Nov 24 09:00:22 2021
  UPTIME: 15 days, 23:17:07
LOAD AVERAGE: 46.41, 37.67, 30.39
   TASKS: 3071
NODENAME: cmp20
 RELEASE: 5.4.0-84-generic
 VERSION: #94~18.04.1-Ubuntu SMP Thu Aug 26 23:17:46 UTC 2021
 MACHINE: x86_64  (2299 Mhz)
  MEMORY: 255.9 GB
   PANIC: "Oops:  [#1] SMP PTI" (check log for details)
 PID: 2239917
 COMMAND: "CPU 0/KVM"
TASK: 9bbd9662  [THREAD_INFO: 9bbd9662]
 CPU: 14
   STATE: TASK_RUNNING (PANIC)

** Affects: linux-meta-hwe-5.4 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bionic

** Attachment added: "dmesg.202111240900"
   
https://bugs.launchpad.net/bugs/1952193/+attachment/5543242/+files/dmesg.202111240900

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

Title:
  NULL pointer dereference at _mod_memcg_state+0x14/0xb0

Status in linux-meta-hwe-5.4 package in Ubuntu:
  New

Bug description:
  Hello.

  We meet a randomly host kernel panics with same RIP and "BUG: kernel NULL 
pointer dereference".
  At current time affected kernel versions was from 5.4.0-53 to 5.4.0-84.
  For now i have a dmesg log and crash file, but no clue where what to do next.

  

  Environment:
Distributor ID: Ubuntu
Description:Ubuntu 18.04.6 LTS
Release:18.04
Codename:   bionic

  
  Crash report

KERNEL: usr/lib/debug/boot/vmlinux-5.4.0-84-generic  
  DUMPFILE: dump.202111240900  [PARTIAL DUMP]
  CPUS: 24
  DATE: Wed Nov 24 09:00:22 2021
UPTIME: 15 days, 23:17:07
  LOAD AVERAGE: 46.41, 37.67, 30.39
 TASKS: 3071
  NODENAME: cmp20
   RELEASE: 5.4.0-84-generic
   VERSION: #94~18.04.1-Ubuntu SMP Thu Aug 26 23:17:46 UTC 2021
   MACHINE: x86_64  (2299 Mhz)
MEMORY: 255.9 GB
 PANIC: "Oops:  [#1] SMP PTI" (check log for details)
   PID: 2239917
   COMMAND: "CPU 0/KVM"
  TASK: 9bbd9662  [THREAD_INFO: 9bbd9662]
   CPU: 14
 STATE: TASK_RUNNING (PANIC)

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


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


[Kernel-packages] [Bug 1950665] Re: Update the 470 NVIDIA driver to 470.86

2021-11-24 Thread Kevin Yeh
You can find test results at 
https://docs.google.com/spreadsheets/d/1bjCjuBFXykVvCb_NuxepUjJthqSiiiDQY854-Tqffyw/edit?usp=sharing
No regression were found.

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

Title:
  Update the 470 NVIDIA driver to 470.86

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Impish:
  Fix Committed

Bug description:
  Update the 470 NVIDIA series in Bionic, Focal, Hirsute, and Impish.

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 470 ==
    * New upstream release (LP: #1950665):
  - Fixed a regression which prevented DisplayPort and HDMI 2.1
    variable refresh rate (VRR) G-SYNC Compatible monitors from
    functioning correctly in variable refresh rate mode, resulting
    in issues such as flickering.

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


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


[Kernel-packages] [Bug 1938096] Re: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend

2021-11-24 Thread CLEsteamer
Can confirm same issue here when set to S3(Linux only). Same problem
also happens in windows - so this is a hardware issue.

I had strange issues when using a non-stock charger as well (lagged but
in a different way).

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

Title:
  [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after
  resume from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hardware: Thinkpad X1 Carbon, 9th generation
  Touchpad: SYNA8009:00 06CB:CE57

  Right after a clean reboot, the touchpad works fine. No issues
  whatsoever. But after resuming from even its first suspend after a
  clean boot, the touchpad feels less responsive, choppy or even laggy.

  I have tried removing and re-inserting some HID kernel modules,
  "psmouse", and setting i915.psr_enabled=0 in kernelstubs. Haven't
  found anything that fixes it yet. The trackpoint works flawlessly all
  the time, so that is the current backup when I don't have an external
  mouse connected.

  My installed OS is Pop!_Os 21.04, but I have tested and confirmed this
  on a live USB with Ubuntu 21.04 as well.

  I have also tried upgrading to the latest 5.13.5 and 5.14.0rc2 kernels
  from the mainline PPA, and tried bumping the libinput10 to 1.18.0 from
  the impish repos.

  To recreate:
  1. Reboot a X1C9 machine and see that the touchpad works fine
  2. Suspend it (to RAM, need to change a BiOS setting so it doesn't do a 
software suspend)
  3. Resume from suspend and see that touchpad acts differently and less 
responsive than right after a clean boot

  What is expected:
  1. Same responsive touchpad experience after resuming from suspend as right 
after a clean boot.

  
  ---

  
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: pop:GNOME
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroRelease: Pop!_OS 21.04
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo Iris Xe Graphics [17aa:22d5]
  MachineType: LENOVO 20XW005PMX
  Package: libinput10 1.18.0-1 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: 
initrd=\EFI\Pop_OS-e5934199-eb91-4da9-9e38-0ad1de1baeb2\initrd.img 
root=UUID=e5934199-eb91-4da9-9e38-0ad1de1baeb2 ro quiet 
systemd.show_status=false loglevel=0 splash
  Tags: hirsute third-party-packages ubuntu
  Uname: Linux 5.13.5-051305-generic x86_64
  UnreportableReason: This does not seem to be an official Pop!_OS package. 
Please retry after updating the indexes of available packages, if that does not 
work then remove related third party packages and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm lpadmin plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 06/15/2021
  dmi.bios.release: 1.42
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET66W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XW005PMX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.26
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET66W(1.42):bd06/15/2021:br1.42:efr1.26:svnLENOVO:pn20XW005PMX:pvrThinkPadX1CarbonGen9:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:rvnLENOVO:rn20XW005PMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XW005PMX
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2pop0~1624392450~21.04~6fbdfd2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-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-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


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


[Kernel-packages] [Bug 1881886] Re: When I turn off the computer, the keyboard and mouse do not turn off

2021-11-24 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  When I turn off the computer, the keyboard and mouse do not turn off

Status in linux package in Ubuntu:
  Expired

Bug description:
  When I turn off the computer, the keyboard and mouse do not turn off
  This bug is present in all Linux distributions. I think it's from the Linux 
kernel.
  The LED under the mouse is on, and the number lock button light should turn 
off when the computer is turned off, but they won't.
  I even disabled USB power settings in the BIOS, but it didn't work.

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


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


[Kernel-packages] [Bug 1948502] Re: TP-Link UB500 Bluetooth USB adapter not working properly

2021-11-24 Thread Kristiyan Katsarov
Can we expect this in 20.04.04?

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

Title:
  TP-Link UB500 Bluetooth USB adapter not working properly

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Released

Bug description:
  I have just bought a Tp-link bluetooth 5.0 usb adapter (UB500). According to 
this website https://usb-ids.gowdy.us/read/UD/2357/0604 the chip is Realtek 
RTL8761B. 
  It works just fine on Windows 10, but I'm having problems on Ubuntu. 

  I'm running Ubuntu 21.10 with the 5.14.14-051414-generic kernel

  The adapter seems to be correctly installed and properly working,
  however scanning does not pick up any bluetooth device. I've tried two
  headsets (that I know are properly working) and my phone, with no
  success. When performing a scan on my phone, the computer doesn't show
  up, even if I've set it to visible.

  (I'm sorry if the information is not complete, but ubuntu-bug is not
  working for me)

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


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


[Kernel-packages] [Bug 1952094] Re: CIFS mount error: iocharset utf8 not found

2021-11-24 Thread ayanamist
@timg-tpi Yes, the new version works fine now.

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

Title:
  CIFS mount error: iocharset utf8 not found

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

Bug description:
  After i apt upgrade from linux-image-5.4.0-89-generic to 
linux-image-5.4.0-90-generic, mount.cifs failed with dmesg "CIFS VFS: CIFS 
mount error: iocharset utf8 not found", and i rollback it and it restores.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 24 20:16 seq
   crw-rw 1 root audio 116, 33 Nov 24 20:16 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:
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-07 (109 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic 
root=UUID=fd942b77-19c9-4959-a01c-c8e3f7b583b6 ro
  ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-89-generic N/A
   linux-backports-modules-5.4.0-89-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 1425-2986-4285-1154-1589-7450-41
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd12/17/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.0
  dmi.sys.vendor: Microsoft Corporation

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


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


[Kernel-packages] [Bug 1952041] Re: Fix i915 TypeC disconnect problems for Intel ADL-P

2021-11-24 Thread Anthony Wong
** Changed in: linux (Ubuntu Focal)
   Status: Incomplete => Won't Fix

** Changed in: linux-oem-5.14 (Ubuntu Jammy)
   Status: New => Invalid

** Changed in: linux-oem-5.14 (Ubuntu Focal)
 Assignee: (unassigned) => Chris Chiu (mschiu77)

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Chris Chiu (mschiu77)

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

Title:
  Fix i915 TypeC disconnect problems for Intel ADL-P

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-hwe source package in Focal:
  New
Status in linux-oem-5.14 source package in Focal:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  When the ADL-P system connects the external display via TypeC port, it will 
hang after unplugging the TypeC connector. The system will never come back 
until reboot.

  [Fix]
  Intel has released a patch set to fix the TypeC PHY connect/disconnect logic. 
The shift for ownership of PHY and power domain will be handled correctly for 
ADL-P.

  [Test]
  The ADL-P system will no longer freeze and the ownership will shift correctly 
after disconnecting the external display connects via TypeC port.

  [Where problem could occur]
  It's kind of a big refactor for the i915 TypeC PHY handling logic. Don't know 
if there's any problems on older platforms. Targeting only on Unstable and 
latest OEM kernel for lower risk.


  == Original Bug Description ==
  [Summary]
  The system will hang on after unplug DA310 with external monitor (on-demand)
  Note:
  1. Build-in HDMI port cannot duplicate.
  2. VGA/HDMI/DP on DA310 to system all can duplicate.
  3. Unplug VGA/DP/HDMI from DA310, then unplug DA310 from the system cannot 
duplicate.

  [Steps to reproduce]
  1. Install dell-bto-focal-fossa-pypar-adl-X160-20210923-2.iso
  2. Plug DA310 to USB-C port
  3. Plug DP/VGA/HDMI to DA310
  4. Unplug DA310 > The system hangs on with black screen

  [Expected result]
  The system works well after unplug USB-C with external monitor

  [Actual result]
  The system hangs on blackscreen after unplug DA310 with external monitor

  [Failure rate]
  3/3

  [Additional information]
  SKU: SIF-MLK-DVT1-C1, SIF-MLK-DVT1-C5, SIF-MLK-DVT1-C6
  Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-pypar-adl+X160
  system-manufacturer: Dell Inc.
  system-product-name: Dell G15 5520
  bios-version: 0.2.9
  CPU: Genuine Intel(R)  (12x)
  GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:46a3]
  :01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device 
[10de:25e2] (rev a1)
  kernel-version: 5.14.0-9002-oem

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


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


[Kernel-packages] [Bug 1952041] Re: Fix i915 TypeC disconnect problems for Intel ADL-P

2021-11-24 Thread Chris Chiu
** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: Incomplete

** Also affects: linux-oem-5.14 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

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

Title:
  Fix i915 TypeC disconnect problems for Intel ADL-P

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-hwe source package in Focal:
  New
Status in linux-oem-5.14 source package in Focal:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  When the ADL-P system connects the external display via TypeC port, it will 
hang after unplugging the TypeC connector. The system will never come back 
until reboot.

  [Fix]
  Intel has released a patch set to fix the TypeC PHY connect/disconnect logic. 
The shift for ownership of PHY and power domain will be handled correctly for 
ADL-P.

  [Test]
  The ADL-P system will no longer freeze and the ownership will shift correctly 
after disconnecting the external display connects via TypeC port.

  [Where problem could occur]
  It's kind of a big refactor for the i915 TypeC PHY handling logic. Don't know 
if there's any problems on older platforms. Targeting only on Unstable and 
latest OEM kernel for lower risk.


  == Original Bug Description ==
  [Summary]
  The system will hang on after unplug DA310 with external monitor (on-demand)
  Note:
  1. Build-in HDMI port cannot duplicate.
  2. VGA/HDMI/DP on DA310 to system all can duplicate.
  3. Unplug VGA/DP/HDMI from DA310, then unplug DA310 from the system cannot 
duplicate.

  [Steps to reproduce]
  1. Install dell-bto-focal-fossa-pypar-adl-X160-20210923-2.iso
  2. Plug DA310 to USB-C port
  3. Plug DP/VGA/HDMI to DA310
  4. Unplug DA310 > The system hangs on with black screen

  [Expected result]
  The system works well after unplug USB-C with external monitor

  [Actual result]
  The system hangs on blackscreen after unplug DA310 with external monitor

  [Failure rate]
  3/3

  [Additional information]
  SKU: SIF-MLK-DVT1-C1, SIF-MLK-DVT1-C5, SIF-MLK-DVT1-C6
  Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-pypar-adl+X160
  system-manufacturer: Dell Inc.
  system-product-name: Dell G15 5520
  bios-version: 0.2.9
  CPU: Genuine Intel(R)  (12x)
  GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:46a3]
  :01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device 
[10de:25e2] (rev a1)
  kernel-version: 5.14.0-9002-oem

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


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


[Kernel-packages] [Bug 1952006] Re: [TGL][ADL] ACRN hypervisor support

2021-11-24 Thread Anthony Wong
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Alex Hung (alexhung)

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

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

Title:
  [TGL][ADL] ACRN hypervisor support

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

Bug description:
  [Impact]

  The driver enables the host to run ACRN hypervisor which is a
  flexible, lightweight reference hypervisor, built with real-time and
  safety-criticality in mind, optimized to streamline embedded
  development through an open-source platform.

  https://projectacrn.org/

  [Fix]

  Intel provides a list of patches to enable ACRN hypervisor

  [Test]

  This is requested by Intel.

  [Where problems could occur]

  Only applicable on Intel TigerLake/AlderLake. Further testing will be
  required.

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


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


[Kernel-packages] [Bug 1952132] Re: [ADL] Thermal Support

2021-11-24 Thread Anthony Wong
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Alex Hung (alexhung)

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

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

Title:
   [ADL] Thermal Support

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

Bug description:
  [Impact]

  The patches enable thermal supports.

  [Fix]

  Intel provides a list of patches to add new PCI driver which register
  a thermal zone and allows to get notification

  [Test]

  This is requested by Intel.

  [Where problems could occur]

  Only applicable on Intel AlderLake. Further testing will be required.

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


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


[Kernel-packages] [Bug 1952007] Re: [ADL] ITBM support for Hybrid platforms

2021-11-24 Thread Anthony Wong
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Alex Hung (alexhung)

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

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

Title:
   [ADL] ITBM support for Hybrid platforms

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

Bug description:
  [Impact]

  Need ITBM support for Hybrid platforms. Need to change the scheduling
  order from Core, HT, ATOM to Core, ATOM, HT.

  When using ITBM on systems that has a mixture of CPUs supporting 
Hyper-Threading and others not supporting it (even offlining HT siblings may 
cause the issue to be reproducible). Hybrid topologies meet the aforementioned 
condition. In such cases, threads will be consolidated on CPUs of high priority 
using got HT siblings, while CPUs of medium priority will remain idle.
  https://projectacrn.org/

  [Fix]

  Intel provides a list of patches to enable AlderLake

  [Test]

  This is requested by Intel.

  [Where problems could occur]

  Only applicable on Intel AlderLake. Further testing will be required.

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


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


[Kernel-packages] [Bug 1952153] Re: [EHL][TGL][ADL] power management controller driver enabling

2021-11-24 Thread Anthony Wong
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Alex Hung (alexhung)

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

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

Title:
   [EHL][TGL][ADL] power management controller driver enabling

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

Bug description:
  [Impact]

  The patches enable power management controller supports.

  [Fix]

  The driver is the Kernel gateway to the PMC hardware for Intel
  processors and it provides debug hooks to developers and end-users to
  quickly figure out why their platform is not entering a deeper idle
  state such as S0ix.

  [Test]

  This is requested by Intel.

  [Where problems could occur]

  Only applicable on Intel ElkhartLake / TigerLake / AlderLake. Further
  testing will be required.

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


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


[Kernel-packages] [Bug 1948351] Re: ppc64 BPF JIT mod by 1 will not return 0

2021-11-24 Thread Kelsey Skunberg
confirmed fixed on impish 5.13.0-22.22 and focal 5.4.0-91.102


https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/l/linux/20211109_160610_20083@/log.gz


https://autopkgtest.ubuntu.com/results/autopkgtest-
focal/focal/ppc64el/l/linux/2029_042322_b4551@/log.gz

** Tags removed: verification-needed-focal verification-needed-impish
** Tags added: verification-done-focal verification-done-impish

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

Title:
  ppc64 BPF JIT mod by 1 will not return 0

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  When doing MOD by 1 with a immediate/constant divisor on PPC, the JIT will 
produce code that returns the dividend, just like a division, instead of 0.

  Both eBPF and cBPF will fail as well when doing such operations.

  [Test case]
  $ cat bpf-mod1.c
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  #define ARRAY_SIZE(array) (sizeof(array)/sizeof(array[0]))

  static int pair[2];

  static int attach()
  {
  int r;

  struct sock_filter insn[] = {
  { BPF_LD | BPF_W | BPF_ABS, 0, 0, 0 },
  { BPF_ALU | BPF_MOD, 0, 0, 1 },
  { BPF_RET | BPF_A, 0, 0, 0 },
  };

  struct sock_fprog prog = {};
  prog.filter = insn;
  prog.len = ARRAY_SIZE(insn);

  socketpair(AF_UNIX, SOCK_DGRAM, 0, pair);
  setsockopt(pair[1], SOL_SOCKET, SO_ATTACH_FILTER, , 
sizeof(prog));
  return 0;
  }

  int main(int argc, char **argv)
  {
  int buf[5];
  int r;
  r = attach();
  if (r < 0) {
  err(1, "function will error out already");
  }
  write(pair[0], "hello", 5);
  r = recv(pair[1], buf, 5, MSG_DONTWAIT);
  if (r != -1 || errno != EAGAIN) {
  err(1, "program failed");
  }
  return 0;
  }
  $ gcc -o bpf-mod1 bpf-mod1.c
  $ ./bpf-mod1
  cbpf-mod1: program failed: Success

  After fix:
  $ ./bpf-mod1
  $ echo $?
  0

  [Potential regression]
  BPF programs might be misbehave on ppc64el.

  

  This is a scripted bug report about ADT failures while running linux
  tests for linux/5.4.0-90.101 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Consistently failing on Focal/linux 5.4.0-90.101

  13:15:26 DEBUG| [stdout] # selftests: net: test_bpf.sh
  13:15:27 DEBUG| [stdout] # test_bpf: [FAIL]
  13:15:27 DEBUG| [stdout] not ok 9 selftests: net: test_bpf.sh # exit=1

  Testing failed on:
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20211021_141544_eda49@/log.gz

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


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


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

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

apport-collect 1952155

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

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

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

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

** Tags added: hirsute

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

Title:
  5.13.0-21 startup failed  , show white noise  screen  (lenovo r9000x
  4800h nvidia 2060)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading kernel 5.13.0-21 startup failed. screen stays at white noise.
  laptop is lenovo r9000x , 
  os: Linux Mint 20.2 Cinnamon
  cpu : amd 4800h
  gpu : nvidia 2060 max

  [code]
  System:Kernel: 5.11.0-40-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.0.7 
 wm: muffin dm: LightDM Distro: Linux Mint 20.2 Uma base: Ubuntu 
20.04 focal 
  Machine:   Type: Laptop System: LENOVO product: 82HN v: Lenovo Legion R9000X 
2021 serial:  
 Chassis: type: 10 v: Lenovo Legion R9000X 2021 serial:  
 Mobo: LENOVO model: LNVNB161216 v: SDK0L77769WIN serial:  
UEFI: LENOVO 
 v: G1CN17WW date: 11/18/2020 
  Battery:   ID-1: BAT0 charge: 62.3 Wh condition: 64.0/71.0 Wh (90%) volts: 
15.4/N/A 
 model: Celxpert L19C4PC3 serial:  status: Unknown 
  CPU:   Topology: 8-Core model: AMD Ryzen 7 4800H with Radeon Graphics 
bits: 64 type: MT MCP 
 arch: Zen rev: 1 L2 cache: 4096 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 92630 
 Speed: 1327 MHz min/max: 1400/2900 MHz Core speeds (MHz): 1: 1289 
2: 1231 3: 1397 
 4: 1397 5: 1386 6: 1397 7: 1397 8: 1338 9: 2253 10: 2611 11: 1408 
12: 1633 13: 1484 
 14: 1397 15: 1392 16: 1397 
  Graphics:  Device-1: NVIDIA TU106 [GeForce RTX 2060] vendor: Lenovo driver: 
nvidia v: 460.106.00 
 bus ID: 01:00.0 chip ID: 10de:1f12 
 Device-2: AMD Renoir vendor: Lenovo driver: amdgpu v: kernel bus 
ID: 06:00.0 
 chip ID: 1002:1636 
 Display: x11 server: X.Org 1.20.11 driver: amdgpu,ati,nvidia 
 unloaded: fbdev,modesetting,nouveau,vesa resolution: 
1920x1080~60Hz, 1920x1080~144Hz 
 OpenGL: renderer: GeForce RTX 2060 with Max-Q Design/PCIe/SSE2 
 v: 4.6.0 NVIDIA 460.106.00 direct render: Yes 
  Audio: Device-1: NVIDIA TU106 High Definition Audio vendor: Lenovo 
driver: snd_hda_intel 
 v: kernel bus ID: 01:00.1 chip ID: 10de:10f9 
 Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor 
vendor: Lenovo driver: N/A 
 bus ID: 06:00.5 chip ID: 1022:15e2 
 Device-3: AMD Family 17h HD Audio vendor: Lenovo driver: 
snd_hda_intel v: kernel 
 bus ID: 06:00.6 chip ID: 1022:15e3 
 Sound Server: ALSA v: k5.11.0-40-generic 
  Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel port: 2000 
bus ID: 03:00.0 
 chip ID: 8086:2723 
 IF: wlp3s0 state: up mac:  
 Device-2: Realtek RTL8152 Fast Ethernet Adapter type: USB driver: 
r8152 bus ID: 5-1.4:6 
 chip ID: 0bda:8152 
 IF: enx00e04c36059b state: up speed: 100 Mbps duplex: full mac: 
 
 IF-ID-1: br-db36e140ddeb state: up speed: 1 Mbps duplex: 
unknown mac:  
 IF-ID-2: docker0 state: up speed: 1 Mbps duplex: unknown mac: 
 
 IF-ID-3: veth0 state: up speed: N/A duplex: N/A mac:  
 IF-ID-4: veth071d8bc state: up speed: 1 Mbps duplex: full mac: 
 
 IF-ID-5: veth260b138 state: up speed: 1 Mbps duplex: full mac: 
 
 IF-ID-6: veth405e95b state: up speed: 1 Mbps duplex: full mac: 
 
 IF-ID-7: veth4412542 state: up speed: 1 Mbps duplex: full mac: 
 
 IF-ID-8: veth56cd37a state: up speed: 1 Mbps duplex: full mac: 
 
 IF-ID-9: veth9c83b77 state: up speed: 1 Mbps duplex: full mac: 
 
 IF-ID-10: veth9dea6f7 state: up speed: 1 Mbps duplex: full 
mac:  
 IF-ID-11: vethae53fe1 state: up speed: 1 Mbps duplex: full 
mac:  
 IF-ID-12: vethdc074a2 state: up speed: 1 Mbps duplex: full 
mac:  
 IF-ID-13: vethf040e52 state: up speed: 1 Mbps duplex: full 
mac:  
  Drives:Local Storage: total: 1.82 TiB used: 758.93 GiB (40.7%) 
 ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB512HBJQ-000L2 size: 
476.94 GiB 
  

[Kernel-packages] [Bug 1952155] [NEW] 5.13.0-21 startup failed , show white noise screen (lenovo r9000x 4800h nvidia 2060)

2021-11-24 Thread icrazy4design
Public bug reported:

After upgrading kernel 5.13.0-21 startup failed. screen stays at white noise.
laptop is lenovo r9000x , 
os: Linux Mint 20.2 Cinnamon
cpu : amd 4800h
gpu : nvidia 2060 max

[code]
System:Kernel: 5.11.0-40-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.0.7 
   wm: muffin dm: LightDM Distro: Linux Mint 20.2 Uma base: Ubuntu 
20.04 focal 
Machine:   Type: Laptop System: LENOVO product: 82HN v: Lenovo Legion R9000X 
2021 serial:  
   Chassis: type: 10 v: Lenovo Legion R9000X 2021 serial:  
   Mobo: LENOVO model: LNVNB161216 v: SDK0L77769WIN serial:  
UEFI: LENOVO 
   v: G1CN17WW date: 11/18/2020 
Battery:   ID-1: BAT0 charge: 62.3 Wh condition: 64.0/71.0 Wh (90%) volts: 
15.4/N/A 
   model: Celxpert L19C4PC3 serial:  status: Unknown 
CPU:   Topology: 8-Core model: AMD Ryzen 7 4800H with Radeon Graphics bits: 
64 type: MT MCP 
   arch: Zen rev: 1 L2 cache: 4096 KiB 
   flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 92630 
   Speed: 1327 MHz min/max: 1400/2900 MHz Core speeds (MHz): 1: 1289 2: 
1231 3: 1397 
   4: 1397 5: 1386 6: 1397 7: 1397 8: 1338 9: 2253 10: 2611 11: 1408 
12: 1633 13: 1484 
   14: 1397 15: 1392 16: 1397 
Graphics:  Device-1: NVIDIA TU106 [GeForce RTX 2060] vendor: Lenovo driver: 
nvidia v: 460.106.00 
   bus ID: 01:00.0 chip ID: 10de:1f12 
   Device-2: AMD Renoir vendor: Lenovo driver: amdgpu v: kernel bus ID: 
06:00.0 
   chip ID: 1002:1636 
   Display: x11 server: X.Org 1.20.11 driver: amdgpu,ati,nvidia 
   unloaded: fbdev,modesetting,nouveau,vesa resolution: 1920x1080~60Hz, 
1920x1080~144Hz 
   OpenGL: renderer: GeForce RTX 2060 with Max-Q Design/PCIe/SSE2 
   v: 4.6.0 NVIDIA 460.106.00 direct render: Yes 
Audio: Device-1: NVIDIA TU106 High Definition Audio vendor: Lenovo driver: 
snd_hda_intel 
   v: kernel bus ID: 01:00.1 chip ID: 10de:10f9 
   Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor vendor: 
Lenovo driver: N/A 
   bus ID: 06:00.5 chip ID: 1022:15e2 
   Device-3: AMD Family 17h HD Audio vendor: Lenovo driver: 
snd_hda_intel v: kernel 
   bus ID: 06:00.6 chip ID: 1022:15e3 
   Sound Server: ALSA v: k5.11.0-40-generic 
Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel port: 2000 
bus ID: 03:00.0 
   chip ID: 8086:2723 
   IF: wlp3s0 state: up mac:  
   Device-2: Realtek RTL8152 Fast Ethernet Adapter type: USB driver: 
r8152 bus ID: 5-1.4:6 
   chip ID: 0bda:8152 
   IF: enx00e04c36059b state: up speed: 100 Mbps duplex: full mac: 
 
   IF-ID-1: br-db36e140ddeb state: up speed: 1 Mbps duplex: unknown 
mac:  
   IF-ID-2: docker0 state: up speed: 1 Mbps duplex: unknown mac: 
 
   IF-ID-3: veth0 state: up speed: N/A duplex: N/A mac:  
   IF-ID-4: veth071d8bc state: up speed: 1 Mbps duplex: full mac: 
 
   IF-ID-5: veth260b138 state: up speed: 1 Mbps duplex: full mac: 
 
   IF-ID-6: veth405e95b state: up speed: 1 Mbps duplex: full mac: 
 
   IF-ID-7: veth4412542 state: up speed: 1 Mbps duplex: full mac: 
 
   IF-ID-8: veth56cd37a state: up speed: 1 Mbps duplex: full mac: 
 
   IF-ID-9: veth9c83b77 state: up speed: 1 Mbps duplex: full mac: 
 
   IF-ID-10: veth9dea6f7 state: up speed: 1 Mbps duplex: full mac: 
 
   IF-ID-11: vethae53fe1 state: up speed: 1 Mbps duplex: full mac: 
 
   IF-ID-12: vethdc074a2 state: up speed: 1 Mbps duplex: full mac: 
 
   IF-ID-13: vethf040e52 state: up speed: 1 Mbps duplex: full mac: 
 
Drives:Local Storage: total: 1.82 TiB used: 758.93 GiB (40.7%) 
   ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB512HBJQ-000L2 size: 
476.94 GiB 
   speed: 31.6 Gb/s lanes: 4 serial:  
   ID-2: /dev/nvme1n1 vendor: Seagate model: FireCuda 510 SSD 
ZP2000GM30001 size: 1.82 TiB 
   speed: 31.6 Gb/s lanes: 4 serial:  
Partition: ID-1: / size: 1.02 TiB used: 758.90 GiB (72.6%) fs: ext4 dev: 
/dev/nvme1n1p5 
USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 chip ID: 
1d6b:0002 
   Hub: 2-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.1 chip ID: 
1d6b:0003 
   Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip ID: 
1d6b:0002 
   Device-1: 3-3:2 info: Intel type: Bluetooth driver: btusb rev: 2.0 
chip ID: 8087:0029 
   Device-2: 3-4:3 info: Shenzhen Goodix Goodix FingerPrint Device 
type:  
   driver: N/A rev: 2.0 chip ID: 27c6:55a4 
   Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip ID: 
1d6b:0003 
   Hub: 5-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip ID: 
1d6b:0002 
   Hub: 5-1:2 info: Terminus USB 2.0 Hub ports: 4 rev: 2.0 chip ID: 

[Kernel-packages] [Bug 1951784] Re: Can't read/write SD card after running CPU offline test in 5.11.0 and 5.13.0

2021-11-24 Thread Kai-Heng Feng
** Changed in: linux (Ubuntu)
   Status: Incomplete => In Progress

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

Title:
  Can't read/write SD card after running CPU offline test in 5.11.0 and
  5.13.0

Status in linux package in Ubuntu:
  In Progress
Status in linux-signed-hwe-5.11 package in Ubuntu:
  New
Status in linux-signed-hwe-5.13 package in Ubuntu:
  New

Bug description:
  [Summary]
  I'm reviewing SRU testing on Dell XPS 13 7390(201906-27131) and mediacard 
test always fails.
  I found that after CPU offline test, I can't read/write SD card.
  After checking dmesg, I got those error msgs.
  [  232.577510] __common_interrupt: 7.34 No irq handler for vector
  [  234.354327] mmc0: error -110 doing runtime resume

  I found the same issue on Dell Precision 3551(202002-27718) and Dell
  Precision 5530(201807-26342) in 5.13.0-21 and 5.11.0-36

  Before I didn't think it's a bug since I re-run mediacard test then
  it's pass. But this cycle there are more systems failed to the test, I
  just started digging into that.

  [Step to reproduce]
  1. install ubuntu-20.04.2/ubuntu-21.10/ubuntu-21.04
  2. sudo apt update; sudo apt dist-upgrade -y
  3. run cpu offline test via checkbox-cli or execute following command
     for ((i=1;i<=$(nproc --all) -1;i++));do sudo chcpu -d $i;sudo chcpu -e $i; 
done;
     cd $mount_point_of_sd_card
     sudo dd if=/dev/urandom of=test bs=1M count=10

  [Expected result]
  Can read/write SD card.

  [Actual result]
  Can't read/write SD card.

  [Failure rate]
  5/5

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-41-generic 5.11.0-41.45~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Nov 22 01:28:59 2021
  InstallationDate: Installed on 2020-08-03 (475 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Kernel-packages] [Bug 1933880] Re: systemd-logind crash when suspend with nvidia-suspend.service masked, bringing session down with it

2021-11-24 Thread apienk
For me, with nvidia-driver-495, the simple solution was to remove the
damaged symlinks from systemd. You most likely have them if you upgraded
from nvidia-driver-470 or nvidia-driver-465, because 470 still included
the .service files in /lib/systemd/system/. The files are no longer
included in 495 but the postinst script does not remove the symlinks.
So, remove them with:

sudo rm 
/etc/systemd/system/systemd-hibernate.service.requires/nvidia-resume.service
sudo rm 
/etc/systemd/system/systemd-hibernate.service.requires/nvidia-hibernate.service
sudo rm 
/etc/systemd/system/systemd-suspend.service.requires/nvidia-resume.service
sudo rm 
/etc/systemd/system/systemd-suspend.service.requires/nvidia-suspend.service

Works instantly, no need of rebooting or logging off.

According to user punyidea at
https://gist.github.com/bmcbm/375f14eaa17f88756b4bdbbebbcfd029, the
services are not needed on 470 either and may be safely removed.

Hope that will fix your problems as well.

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

Title:
  systemd-logind crash when suspend with nvidia-suspend.service masked,
  bringing session down with it

Status in nvidia-graphics-drivers-465 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Run `sudo apt install nvidia-driver-465`. Then, without a need for a 
restart, run `sudo apt autoremove nvidia-driver-465`.
  2. Leaving the terminal open, suspend the machine.

  Expected behavior: the machine suspend successfully and can be woken up 
successfully.
  Actual behavior: the machine doesn't suspend. It either:
  - hang with no respond other than SysRq+REISUB (or maybe network, but I 
didn't test), or
  - return you back to the login screen. Upon logging in, you'll notice that 
the terminal you opened is gone.

  Upon further inspection (on a session that doesn't hang), it's been
  found that X server died with:

  Fatal server error:
  [66.422] (EE) systemd-logind disappeared (stopped/restarted?)

  And checking journal for systemd-logind log, it said:

  Error during inhibitor-delayed operation (already returned success to
  client): Unit nvidia-suspend.service is masked.

  before the new process takes it place.

  The system is Ubuntu 20.04, X.org session.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.7
  ProcVersionSignature: Ubuntu 5.11.0-22.23~20.04.1-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 29 03:34:00 2021
  InstallationDate: Installed on 2021-03-15 (105 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=th_TH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=UUID=06f2a676-a62c-443a-8bc8-4e0eda4600f4 ro log_buf_len=2M quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/01/2021
  dmi.bios.release: 1.31
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN31WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55756 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.ec.firmware.release: 1.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN31WW:bd01/01/2021:br1.31:efr1.31:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55756WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.vendor: LENOVO

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


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


[Kernel-packages] [Bug 1943732] Re: cpufreq_boost from ubuntu_ltp.kernel_misc failed on P9 node baltar with Focal 5.4

2021-11-24 Thread Kelsey Skunberg
** Tags added: sru-20211018

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

Title:
  cpufreq_boost from ubuntu_ltp.kernel_misc failed on P9 node baltar
  with Focal 5.4

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

Bug description:
  Testcase cpufreq_boost from ubuntu_ltp.kernel_misc failed with
  focal/linux 5.4.0-85.95 on the P9 node baltar.

  13:50:50 DEBUG| [stdout] startup='Wed Sep  8 13:42:39 2021'
  13:50:50 DEBUG| [stdout] cpufreq_boost0  TINFO  :  found 'acpi_cpufreq' 
driver, sysfs knob '/sys
  /devices/system/cpu/cpufreq/boost'
  13:50:50 DEBUG| [stdout] cpufreq_boost0  TINFO  :  maximum speed is 
380 KHz
  13:50:50 DEBUG| [stdout] cpufreq_boost0  TINFO  :  load CPU0 with boost 
enabled
  13:50:50 DEBUG| [stdout] cpufreq_boost0  TINFO  :  elapsed time is 2006 ms
  13:50:50 DEBUG| [stdout] cpufreq_boost0  TINFO  :  load CPU0 with boost 
disabled
  13:50:50 DEBUG| [stdout] cpufreq_boost0  TINFO  :  elapsed time is 2027 ms
  13:50:50 DEBUG| [stdout] cpufreq_boost1  TFAIL  :  cpufreq_boost.c:189: 
compare time spent with 
  and without boost (-2%)
  13:50:50 DEBUG| [stdout] tag=cpufreq_boost stime=1631108559 dur=4 exit=exited 
stat=1 core=no cu=404 cs=2

  
  This is not a regression as it has been failing since older versions (at 
least since 5.4.0-75.84).

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


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


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

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

apport-collect 1952153

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

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

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

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

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

Title:
   [EHL][TGL][ADL] power management controller driver enabling

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

Bug description:
  [Impact]

  The patches enable power management controller supports.

  [Fix]

  The driver is the Kernel gateway to the PMC hardware for Intel
  processors and it provides debug hooks to developers and end-users to
  quickly figure out why their platform is not entering a deeper idle
  state such as S0ix.

  [Test]

  This is requested by Intel.

  [Where problems could occur]

  Only applicable on Intel ElkhartLake / TigerLake / AlderLake. Further
  testing will be required.

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


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


[Kernel-packages] [Bug 1936295] Re: Faulty Elantech Trackpoint firmware unusable as it causes sudden cursor jump to an edge/corner on Lenovo Thinkpad X13, T14s, A475 --> Apply kernel patch to mitigate

2021-11-24 Thread Eduardo Rojas Rodríguez
that's good to read, I hope this attract the attention of the kernel
team so they can backport to ubuntu, this is a really annoying bug.

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

Title:
  Faulty Elantech Trackpoint firmware unusable as it causes sudden
  cursor jump to an edge/corner on Lenovo Thinkpad X13, T14s, A475 -->
  Apply kernel patch to mitigate the FW bug

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  *Problem description:*
  On Lenovo Thinkpad T14s, X13, A475 (and probably more models) the Elantech 
Trackpoint firmware is defective. The trackpoint cursor often suddenly jumps to 
an edge/corner, because the hardware/firmware sometimes reports wrong 
coordinates / loses sync. Currently, the Trackpoint is barely usable and it's 
impossible to productively work using it.

  For a long while, Elantech has not yet put forward (nor confirmed) a
  firmware update. However, there is a Linux kernel patch mitigating the
  firmware bug. The kernel bugfix discards the wrongly reported packages
  by the Elantech hardware. This solves the problem for the user.

  *Solution:* Please apply existing kernel patch here.
  https://bugzilla.kernel.org/show_bug.cgi?id=209167 Bug entry in the Linux 
Kernel.org Bugzilla
  https://bugzilla.kernel.org/attachment.cgi?id=295733=diff Diff of 
bugfix

  
  *T14s and X13 are Ubuntu certified:*
  The Lenovo Thinkpad T14s and X13 are Ubuntu certified, but apparently this 
hardware issue has slipped the Ubuntu certification process! 
https://ubuntu.com/certified/202006-27978 and 
https://ubuntu.com/certified/202006-27979

  *Further information:*
  
https://forums.lenovo.com/t5/Fedora/T14s-AMD-Trackpoint-almost-unusable/m-p/5064952?page=1
 Discussion on the bug in the Lenovo forum. E.g. see comment 18 by Lenovo 
employee MarkRHPearson

  *My System:*
  Lenovo Thinkpad T14s (AMD) 20ujs00k00
  Ubuntu 21.04 and 20.04
  see entries in kernel.org bugzilla for logs.

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


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


[Kernel-packages] [Bug 1952153] [NEW] [EHL][TGL][ADL] power management controller driver enabling

2021-11-24 Thread Alex Hung
Public bug reported:

[Impact]

The patches enable power management controller supports.

[Fix]

The driver is the Kernel gateway to the PMC hardware for Intel
processors and it provides debug hooks to developers and end-users to
quickly figure out why their platform is not entering a deeper idle
state such as S0ix.

[Test]

This is requested by Intel.

[Where problems could occur]

Only applicable on Intel ElkhartLake / TigerLake / AlderLake. Further
testing will be required.

** Affects: hwe-next
 Importance: Undecided
 Status: New

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


** Tags: intel oem-priority originate-from-1943538

** Tags added: intel oem-priority originate-from-1943538

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

Title:
   [EHL][TGL][ADL] power management controller driver enabling

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

Bug description:
  [Impact]

  The patches enable power management controller supports.

  [Fix]

  The driver is the Kernel gateway to the PMC hardware for Intel
  processors and it provides debug hooks to developers and end-users to
  quickly figure out why their platform is not entering a deeper idle
  state such as S0ix.

  [Test]

  This is requested by Intel.

  [Where problems could occur]

  Only applicable on Intel ElkhartLake / TigerLake / AlderLake. Further
  testing will be required.

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


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


[Kernel-packages] [Bug 1952132] Re: [ADL] Thermal Support

2021-11-24 Thread Alex Hung
** Tags added: intel oem-priority originate-from-1943522

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

Title:
   [ADL] Thermal Support

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

Bug description:
  [Impact]

  The patches enable thermal supports.

  [Fix]

  Intel provides a list of patches to add new PCI driver which register
  a thermal zone and allows to get notification

  [Test]

  This is requested by Intel.

  [Where problems could occur]

  Only applicable on Intel AlderLake. Further testing will be required.

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


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


[Kernel-packages] [Bug 1952136] [NEW] Hirsute update: upstream stable patchset 2021-11-24

2021-11-24 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 2021-11-24

Ported from the following upstream stable releases:
v5.10.74, v5.14.13
v5.10.75, v5.14.14
v5.10.76, v5.14.15

   from git://git.kernel.org/

ext4: check and update i_disksize properly
ext4: correct the error path of ext4_write_inline_data_end()
ASoC: Intel: sof_sdw: tag SoundWire BEs as non-atomic
HID: apple: Fix logical maximum and usage maximum of Magic Keyboard JIS
netfilter: ip6_tables: zero-initialize fragment offset
HID: wacom: Add new Intuos BT (CTL-4100WL/CTL-6100WL) device IDs
ASoC: SOF: loader: release_firmware() on load failure to avoid batching
netfilter: nf_nat_masquerade: make async masq_inet6_event handling generic
netfilter: nf_nat_masquerade: defer conntrack walk to work queue
mac80211: Drop frames from invalid MAC address in ad-hoc mode
m68k: Handle arrivals of multiple signals correctly
hwmon: (ltc2947) Properly handle errors when looking for the external clock
net: prevent user from passing illegal stab size
mac80211: check return value of rhashtable_init
vboxfs: fix broken legacy mount signature checking
net: sun: SUNVNET_COMMON should depend on INET
drm/amdgpu: fix gart.bo pin_count leak
scsi: ses: Fix unsigned comparison with less than zero
scsi: virtio_scsi: Fix spelling mistake "Unsupport" -> "Unsupported"
perf/core: fix userpage->time_enabled of inactive events
sched: Always inline is_percpu_thread()
hwmon: (pmbus/ibm-cffps) max_power_out swap changes
ALSA: usb-audio: Unify mixer resume and reset_resume procedure
pinctrl: qcom: sc7280: Add PM suspend callbacks
io_uring: kill fasync
UBUNTU: upstream stable to v5.10.74, v5.14.13
ALSA: usb-audio: Add quirk for VF0770
ALSA: pcm: Workaround for a wrong offset in SYNC_PTR compat ioctl
ALSA: seq: Fix a potential UAF by wrong private_free call order
ALSA: hda/realtek: Enable 4-speaker output for Dell Precision 5560 laptop
ALSA: hda - Enable headphone mic on Dell Latitude laptops with ALC3254
ALSA: hda/realtek: Complete partial device name to avoid ambiguity
ALSA: hda/realtek: Add quirk for Clevo X170KM-G
ALSA: hda/realtek - ALC236 headset MIC recording issue
ALSA: hda/realtek: Add quirk for TongFang PHxTxX1
ALSA: hda/realtek: Fix the mic type detection issue for ASUS G551JW
nds32/ftrace: Fix Error: invalid operands (*UND* and *UND* sections) for `^'
s390: fix strrchr() implementation
clk: socfpga: agilex: fix duplicate s2f_user0_clk
csky: don't let sigreturn play with priveleged bits of status register
csky: Fixup regs.sr broken in ptrace
arm64/hugetlb: fix CMA gigantic page order for non-4K PAGE_SIZE
drm/msm: Avoid potential overflow in timeout_to_jiffies()
btrfs: unlock newly allocated extent buffer after error
btrfs: deal with errors when replaying dir entry during log replay
btrfs: deal with errors when adding inode reference during log replay
btrfs: check for error when looking up inode during dir entry replay
btrfs: update refs for any root except tree log roots
btrfs: fix abort logic in btrfs_replace_file_extents
x86/resctrl: Free the ctrlval arrays when domain_setup_mon_state() fails
mei: me: add Ice Lake-N device id.
USB: xhci: dbc: fix tty registration race
xhci: guard accesses to ep_state in xhci_endpoint_reset()
xhci: Fix command ring pointer corruption while aborting a command
xhci: Enable trust tx length quirk for Fresco FL11 USB controller
cb710: avoid NULL pointer subtraction
efi/cper: use stack buffer for error record decoding
efi: Change down_interruptible() in virt_efi_reset_system() to down_trylock()
usb: musb: dsps: Fix the probe error path
Input: xpad - add support for another USB ID of Nacon GC-100
USB: serial: qcserial: add EM9191 QDL support
USB: serial: option: add Quectel EC200S-CN module support
USB: serial: option: add Telit LE910Cx composition 0x1204
USB: serial: option: add prod. id for Quectel EG91
misc: fastrpc: Add missing lock before accessing find_vma()
EDAC/armada-xp: Fix output of uncorrectable error counter
nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells
x86/Kconfig: Do not enable AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT automatically
powerpc/xive: Discard disabled interrupts in get_irqchip_state()
iio: adc: aspeed: set driver data when adc probe.
drivers: bus: simple-pm-bus: Add support for probing simple bus only devices
driver core: Reject pointless SYNC_STATE_ONLY device links
iio: adc: ad7192: Add IRQ flag
iio: adc: ad7780: Fix IRQ flag
iio: adc: ad7793: Fix IRQ flag
iio: adc128s052: Fix the error 

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

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

apport-collect 1951289

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

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

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

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

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

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

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

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

Title:
  ubuntu_ltp_controllers:cpuset_sched_domains: tests 3,9,11,17,19,25
  report incorrect sched domain for cpu#32

Status in kunpeng920:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Focal:
  Incomplete
Status in linux source package in Hirsute:
  Incomplete

Bug description:
  On scobee-kernel(arm64) with hirsute:linux(5.11.0-41.45) for
  sru-20211108 there are several reports about the sched domain not
  covering the full range. The same does not happen on kuzzle. But 32 is
  a bit of a suspicious number.

Running tests...
cpuset_sched_domains 1 TINFO: CPUs are numbered continuously starting at 0 
(0-127)
cpuset_sched_domains 1 TINFO: Nodes are numbered continuously starting at 0 
(0-3)
cpuset_sched_domains 1 TINFO: root group load balance test
cpuset_sched_domains 1 TINFO:  sched load balance: 0
cpuset_sched_domains 1 TINFO: CPU hotplug:
cpuset_check_domains1  TPASS  :  check_sched_domains passed
cpuset_sched_domains 1 TPASS: partition sched domains succeeded.
cpuset_sched_domains 3 TINFO: root group load balance test
cpuset_sched_domains 3 TINFO:  sched load balance: 1
cpuset_sched_domains 3 TINFO: CPU hotplug:
cpuset_check_domains1  TFAIL  :  cpuset_sched_domains_check.c:110: 
cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95).
cpuset_sched_domains 3 TFAIL: partition sched domains failed.
cpuset_sched_domains 5 TINFO: root group load balance test
cpuset_sched_domains 5 TINFO:  sched load balance: 0
cpuset_sched_domains 5 TINFO: CPU hotplug:
cpuset_check_domains1  TPASS  :  check_sched_domains passed
cpuset_sched_domains 5 TPASS: partition sched domains succeeded.
cpuset_sched_domains 7 TINFO: root group load balance test
cpuset_sched_domains 7 TINFO:  sched load balance: 0
cpuset_sched_domains 7 TINFO: CPU hotplug:
cpuset_check_domains1  TPASS  :  check_sched_domains passed
cpuset_sched_domains 7 TPASS: partition sched domains succeeded.
cpuset_sched_domains 9 TINFO: root group load balance test
cpuset_sched_domains 9 TINFO:  sched load balance: 1
cpuset_sched_domains 9 TINFO: CPU hotplug:
cpuset_check_domains1  TFAIL  :  cpuset_sched_domains_check.c:110: 
cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95).
cpuset_sched_domains 9 TFAIL: partition sched domains failed.
cpuset_sched_domains 11 TINFO: root group load balance test
cpuset_sched_domains 11 TINFO:  sched load balance: 1
cpuset_sched_domains 11 TINFO: CPU hotplug:
cpuset_check_domains1  TFAIL  :  cpuset_sched_domains_check.c:110: 
cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95).
cpuset_sched_domains 11 TFAIL: partition sched domains failed.
cpuset_sched_domains 13 TINFO: general group load balance test
cpuset_sched_domains 13 TINFO: root group info:
cpuset_sched_domains 13 TINFO:  sched load balance: 0
cpuset_sched_domains 13 TINFO: general group info:
cpuset_sched_domains 13 TINFO:  cpus: -
cpuset_sched_domains 13 TINFO:  sched load balance: 1
cpuset_check_domains1  TPASS  :  check_sched_domains passed
cpuset_sched_domains 13 TPASS: partition sched domains succeeded.
cpuset_sched_domains 15 TINFO: general group load balance test
cpuset_sched_domains 15 TINFO: root group info:
cpuset_sched_domains 15 TINFO:  sched load balance: 0
cpuset_sched_domains 15 TINFO: general group info:
cpuset_sched_domains 15 TINFO:  cpus: 1
cpuset_sched_domains 15 TINFO:  sched load balance: 0
cpuset_check_domains1  TPASS  :  check_sched_domains passed
cpuset_sched_domains 15 TPASS: partition sched domains succeeded.
cpuset_sched_domains 17 TINFO: general group load balance test
cpuset_sched_domains 17 TINFO: root 

[Kernel-packages] [Bug 1951289] Re: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3, 9, 11, 17, 19, 25 report incorrect sched domain for cpu#32

2021-11-24 Thread dann frazier
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  ubuntu_ltp_controllers:cpuset_sched_domains: tests 3,9,11,17,19,25
  report incorrect sched domain for cpu#32

Status in kunpeng920:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Focal:
  New
Status in linux source package in Hirsute:
  New

Bug description:
  On scobee-kernel(arm64) with hirsute:linux(5.11.0-41.45) for
  sru-20211108 there are several reports about the sched domain not
  covering the full range. The same does not happen on kuzzle. But 32 is
  a bit of a suspicious number.

Running tests...
cpuset_sched_domains 1 TINFO: CPUs are numbered continuously starting at 0 
(0-127)
cpuset_sched_domains 1 TINFO: Nodes are numbered continuously starting at 0 
(0-3)
cpuset_sched_domains 1 TINFO: root group load balance test
cpuset_sched_domains 1 TINFO:  sched load balance: 0
cpuset_sched_domains 1 TINFO: CPU hotplug:
cpuset_check_domains1  TPASS  :  check_sched_domains passed
cpuset_sched_domains 1 TPASS: partition sched domains succeeded.
cpuset_sched_domains 3 TINFO: root group load balance test
cpuset_sched_domains 3 TINFO:  sched load balance: 1
cpuset_sched_domains 3 TINFO: CPU hotplug:
cpuset_check_domains1  TFAIL  :  cpuset_sched_domains_check.c:110: 
cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95).
cpuset_sched_domains 3 TFAIL: partition sched domains failed.
cpuset_sched_domains 5 TINFO: root group load balance test
cpuset_sched_domains 5 TINFO:  sched load balance: 0
cpuset_sched_domains 5 TINFO: CPU hotplug:
cpuset_check_domains1  TPASS  :  check_sched_domains passed
cpuset_sched_domains 5 TPASS: partition sched domains succeeded.
cpuset_sched_domains 7 TINFO: root group load balance test
cpuset_sched_domains 7 TINFO:  sched load balance: 0
cpuset_sched_domains 7 TINFO: CPU hotplug:
cpuset_check_domains1  TPASS  :  check_sched_domains passed
cpuset_sched_domains 7 TPASS: partition sched domains succeeded.
cpuset_sched_domains 9 TINFO: root group load balance test
cpuset_sched_domains 9 TINFO:  sched load balance: 1
cpuset_sched_domains 9 TINFO: CPU hotplug:
cpuset_check_domains1  TFAIL  :  cpuset_sched_domains_check.c:110: 
cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95).
cpuset_sched_domains 9 TFAIL: partition sched domains failed.
cpuset_sched_domains 11 TINFO: root group load balance test
cpuset_sched_domains 11 TINFO:  sched load balance: 1
cpuset_sched_domains 11 TINFO: CPU hotplug:
cpuset_check_domains1  TFAIL  :  cpuset_sched_domains_check.c:110: 
cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95).
cpuset_sched_domains 11 TFAIL: partition sched domains failed.
cpuset_sched_domains 13 TINFO: general group load balance test
cpuset_sched_domains 13 TINFO: root group info:
cpuset_sched_domains 13 TINFO:  sched load balance: 0
cpuset_sched_domains 13 TINFO: general group info:
cpuset_sched_domains 13 TINFO:  cpus: -
cpuset_sched_domains 13 TINFO:  sched load balance: 1
cpuset_check_domains1  TPASS  :  check_sched_domains passed
cpuset_sched_domains 13 TPASS: partition sched domains succeeded.
cpuset_sched_domains 15 TINFO: general group load balance test
cpuset_sched_domains 15 TINFO: root group info:
cpuset_sched_domains 15 TINFO:  sched load balance: 0
cpuset_sched_domains 15 TINFO: general group info:
cpuset_sched_domains 15 TINFO:  cpus: 1
cpuset_sched_domains 15 TINFO:  sched load balance: 0
cpuset_check_domains1  TPASS  :  check_sched_domains passed
cpuset_sched_domains 15 TPASS: partition sched domains succeeded.
cpuset_sched_domains 17 TINFO: general group load balance test
cpuset_sched_domains 17 TINFO: root group info:
cpuset_sched_domains 17 TINFO:  sched load balance: 1
cpuset_sched_domains 17 TINFO: general group info:
cpuset_sched_domains 17 TINFO:  cpus: -
cpuset_sched_domains 17 TINFO:  sched load balance: 1
cpuset_check_domains1  TFAIL  :  cpuset_sched_domains_check.c:110: 
cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95).
cpuset_sched_domains 17 TFAIL: partition sched domains failed.
cpuset_sched_domains 19 TINFO: general group load balance test
 

[Kernel-packages] [Bug 1951580] Re: backport-iwlwifi-dkms fails to build with kernel 5.15 jammy

2021-11-24 Thread Andrea Righi
It looks like this dkms is actually needed so ignore my previous
comment.

** Description changed:

+ [Impact]
+ 
+ backport-iwlwifi-dkms fails to build on the latest jammy kernel 5.15:
+ 
  CC [M]  
/tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.o
  In file included from 
/tmp/backport-iwlwifi-dkms/backport-include/asm-generic/bug.h:3,
-  from ./arch/x86/include/asm/bug.h:84,
-  from ./include/linux/bug.h:5,
-  from 
/tmp/backport-iwlwifi-dkms/backport-include/linux/bug.h:3,
-  from 
/tmp/backport-iwlwifi-dkms/backport-include/linux/kernel.h:4,
-  from ./include/linux/skbuff.h:13,
-  from 
/tmp/backport-iwlwifi-dkms/backport-include/linux/skbuff.h:3,
-  from ./include/linux/if_ether.h:19,
-  from 
/tmp/backport-iwlwifi-dkms/backport-include/linux/if_ether.h:3,
-  from ./include/linux/etherdevice.h:20,
-  from 
/tmp/backport-iwlwifi-dkms/backport-include/linux/etherdevice.h:3,
-  from 
/tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c:6:
+  from ./arch/x86/include/asm/bug.h:84,
+  from ./include/linux/bug.h:5,
+  from 
/tmp/backport-iwlwifi-dkms/backport-include/linux/bug.h:3,
+  from 
/tmp/backport-iwlwifi-dkms/backport-include/linux/kernel.h:4,
+  from ./include/linux/skbuff.h:13,
+  from 
/tmp/backport-iwlwifi-dkms/backport-include/linux/skbuff.h:3,
+  from ./include/linux/if_ether.h:19,
+  from 
/tmp/backport-iwlwifi-dkms/backport-include/linux/if_ether.h:3,
+  from ./include/linux/etherdevice.h:20,
+  from 
/tmp/backport-iwlwifi-dkms/backport-include/linux/etherdevice.h:3,
+  from 
/tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c:6:
  /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c: In 
function ‘iwl_mei_free_shared_mem’:
  
/tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c:243:17:
 error: implicit declaration of function ‘mei_cldev_dma_unmap’ 
[-Werror=implicit-function-declaration]
-   243 | WARN_ON(mei_cldev_dma_unmap(cldev));
-   | ^~~
+   243 | WARN_ON(mei_cldev_dma_unmap(cldev));
+   | ^~~
+ 
+ [Test case]
+ 
+ sudo apt install backport-iwlwifi-dkms
+ 
+ [Fix]
+ 
+ The driver assumes that kernels > 5.13 provide mei_cldev_dma_map/unmap()
+ when CONFIG_WLAN_VENDOR_INTEL_MEI is defined.
+ 
+ However these functions and the config option are not available at all
+ in recent kernels.
+ 
+ So instead of relying on the specific kernel version simply rely on the
+ availability of CONFIG_WLAN_VENDOR_INTEL_MEI to determine if the kernel
+ has the required functions defined, or if the driver needs to provide a
+ custom implementation of these functions.
+ 
+ [Regression potential]
+ 
+ We may see build errors in newer kernel if CONFIG_WLAN_VENDOR_INTEL_MEI
+ is merged upstream and these functions are actually provided by recent
+ kernels.

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

Title:
  backport-iwlwifi-dkms fails to build with kernel 5.15 jammy

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  [Impact]

  backport-iwlwifi-dkms fails to build on the latest jammy kernel 5.15:

  CC [M]  
/tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.o
  In file included from 
/tmp/backport-iwlwifi-dkms/backport-include/asm-generic/bug.h:3,
   from ./arch/x86/include/asm/bug.h:84,
   from ./include/linux/bug.h:5,
   from 
/tmp/backport-iwlwifi-dkms/backport-include/linux/bug.h:3,
   from 
/tmp/backport-iwlwifi-dkms/backport-include/linux/kernel.h:4,
   from ./include/linux/skbuff.h:13,
   from 
/tmp/backport-iwlwifi-dkms/backport-include/linux/skbuff.h:3,
   from ./include/linux/if_ether.h:19,
   from 
/tmp/backport-iwlwifi-dkms/backport-include/linux/if_ether.h:3,
   from ./include/linux/etherdevice.h:20,
   from 
/tmp/backport-iwlwifi-dkms/backport-include/linux/etherdevice.h:3,
   from 
/tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c:6:
  /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c: In 
function ‘iwl_mei_free_shared_mem’:
  
/tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c:243:17:
 error: implicit declaration of function ‘mei_cldev_dma_unmap’ 
[-Werror=implicit-function-declaration]
    243 | 

[Kernel-packages] [Bug 1950903] Re: kernel package does not build nvme-tcp module

2021-11-24 Thread Sagi
Hey, any progress with this? should be trivial to fix.

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

Title:
  kernel package does not build nvme-tcp module

Status in linux-aws package in Ubuntu:
  Confirmed

Bug description:
  linux-image-5.4.0-1059-aws does not build nvme-tcp kernel module so there is 
no option to use it.
  The fix is trivial, just add CONFIG_NVME_TCP=m in the kernel config file used 
to build the kernel image.

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


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


[Kernel-packages] [Bug 1949924] Re: yelp crashes in wayland session with NVIDIA 470

2021-11-24 Thread Bug Watch Updater
** Changed in: egl-wayland
   Status: New => Fix Released

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

Title:
  yelp crashes in wayland session with NVIDIA 470

Status in NVIDIA / egl-wayland:
  Fix Released
Status in egl-wayland package in Ubuntu:
  Fix Released
Status in yelp package in Ubuntu:
  Invalid

Bug description:
  $ yelp
  yelp: ../src/wayland-thread.c:87: wlExternalApiLock: Assertion `!"failed to 
lock pthread mutex"' failed.
  Aborted (core dumped)

  This does not happen in Debian testing, and it also works as expected
  in an Ubuntu on Xorg session.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: yelp 41.1-1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  5 02:51:43 2021
  InstallationDate: Installed on 2019-11-10 (725 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: yelp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/egl-wayland/+bug/1949924/+subscriptions


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


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

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

apport-collect 1842144

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

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

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

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

** Tags added: jammy

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

Title:
  [EHL] Quadrature Encoder Peripheral support

Status in intel:
  Fix Committed
Status in intel lookout-canyon series:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:
  Support a quadrature encoder peripheral (QEP) that is a peripheral designed 
to interface to a shaft encoder fitted to either a motor shaft or a user 
interface dial, as a means to measure rotational speed, direction, and 
optionally absolute angle of rotation.

  Commit ids: b711f687a1c1
  Target Release: 22.04
  Target Kernel: 5.14

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


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


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

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

apport-collect 1952132

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

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

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

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

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

Title:
   [ADL] Thermal Support

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

  The patches enable thermal supports.

  [Fix]

  Intel provides a list of patches to add new PCI driver which register
  a thermal zone and allows to get notification

  [Test]

  This is requested by Intel.

  [Where problems could occur]

  Only applicable on Intel AlderLake. Further testing will be required.

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


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


[Kernel-packages] [Bug 1952132] [NEW] [ADL] Thermal Support

2021-11-24 Thread Alex Hung
Public bug reported:

[Impact]

The patches enable thermal supports.

[Fix]

Intel provides a list of patches to add new PCI driver which register a
thermal zone and allows to get notification

[Test]

This is requested by Intel.

[Where problems could occur]

Only applicable on Intel AlderLake. Further testing will be required.

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

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

Title:
   [ADL] Thermal Support

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]

  The patches enable thermal supports.

  [Fix]

  Intel provides a list of patches to add new PCI driver which register
  a thermal zone and allows to get notification

  [Test]

  This is requested by Intel.

  [Where problems could occur]

  Only applicable on Intel AlderLake. Further testing will be required.

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


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


[Kernel-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

2021-11-24 Thread Sergio Durigan Junior
** Tags removed: server-todo

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  Invalid
Status in ethtool package in Ubuntu:
  Triaged
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  Fix Released
Status in ntp package in Ubuntu:
  Won't Fix
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  Fix Released
Status in openvpn package in Ubuntu:
  Confirmed
Status in openvswitch package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  Fix Released
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Kernel-packages] [Bug 1928387] Re: [EHL] Integrated TSN controller (stmmac) driver support

2021-11-24 Thread Ana Lasprilla
** Information type changed from Private to Public Security

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

Title:
  [EHL] Integrated TSN controller (stmmac) driver support

Status in intel:
  Fix Committed
Status in intel lookout-canyon series:
  Fix Released
Status in Ubuntu:
  Confirmed
Status in linux-intel package in Ubuntu:
  In Progress

Bug description:
  1. Feature Overview: Enable Integrated TSN controller (stmac) driver
  in Ubuntu

  2. Hardware: Elkhart Lake

  3. Upstream acceptance: Commit IDs see below

  4. External Links:
  IoTG EHL RDC#:606615

  5. Ubuntu target: Ubuntu 21.10 (and Ubuntu 20.04 IoTG)

  Commit ID List (Kernel merged)
  ab1c637cc6d8   stmmac: intel: Fix kernel crash due to wrong error path (5.7)
  29e0c2f39f98   stmmac: intel: Place object in the Makefile according to the 
order (5.8)
  ccacb703b0f8   stmmac: intel: Fix indentation to put on one line affected 
code (5.8)
  d5383b037664   stmmac: intel: Eliminate useless conditions and variables (5.8)
  52c1f7948454   stmmac: intel: Convert to use pci_alloc_irq_vectors() API (5.8)
  e578f043ffcf   stmmac: intel: Remove unnecessary loop for PCI BARs (5.8)
  09f012e64e4b   stmmac: intel: Fix clock handling on error and remove paths 
(5.8)
  801eb0501824   stmmac: intel: Fix kernel crash due to wrong error path (5.8)
  VLAN support: c89f44ff10fd net: stmmac: Add support for VLAN promiscuous mode 
(5.8)
  b9663b7ca6ff net: stmmac: Enable SERDES power up/down sequence (5.7)
  d63439f575dc net: stmmac: add EHL 2.5Gbps PCI info and PCI ID (5.7)
  67c08ac4140a net: stmmac: add EHL PSE0 & PSE1 1Gbps PCI info and PCI ID (5.7)
  58da0cfa6cf1 net: stmmac: create dwmac-intel.c to contain all Intel platform 
(5.7)
  VLAN support: ed64639bc1e0 net: stmmac: Add support for VLAN Rx filtering 
(5.7)
  3e07df430c2b   net: stmmac: Get rid of custom STMMAC_DEVICE() macro (5.7)
  909c1dde67c4 net: stmmac: update pci platform data to use phy_interface (5.6)
  2f633d5820e4 net: stmmac: xgmac: fix missing IFF_MULTICAST checki in 
dwxgmac2_set_filter (5.6)
  2ba31cd93784 net: stmmac: fix missing IFF_MULTICAST check in 
dwmac4_set_filter (5.6)
  VLAN support: 907a076881f1 net: stmmac: xgmac: fix incorrect XGMAC_VLAN_TAG 
register writing (5.6)
  VLAN support: 9eeeb3c9de4e net: stmmac: fix incorrect GMAC_VLAN_TAG register 
writting in GMAC4+ (5.6)
  c593642c8be0 treewide: Use sizeof_field() macro (5.5)
  8e5debed3901 net: stmmac: Use rtnl_lock/unlock on 
netif_set_real_num_rx_queues() call (5.10)
  785ff20bce2d stmmac: intel: Fix kernel panic on pci probe (5.10)
  388e201d41fa net: stmmac: Modify configuration method of EEE timers (5.9)
  b4c5f83ae3f3 stmmac: intel: Adding ref clock 1us tic for LPI cntr (5.10)
  ac322f86b56c net: stmmac: Fix clock handling on remove path (5.9_
  VLAN support: e0f9956a3862 net: stmmac: Add option for VLAN filter fail queue 
enable (5.10)
  d0ea5cbdc286 drivers/net/ethernet: clean up mis-targeted comments (5.10)
  7241c5a69747 net: stmmac: removed enabling eee in EEE set callback (5.9)
  aa042f60e496 net: stmmac: Add support to Ethtool get/set ring parameters 
(5.10)
  9f19306d1666 net: stmmac: use netif_tx_start|stop_all_queues() function (5.10)
  686cff3d7022 net: stmmac: Fix incorrect location to set real_num_rx|tx_queues 
(5.10)
  0366f7e06a6b net: stmmac: add ethtool support for get/set channels (5.10)
  9efc9b2b04c7 net: stmmac: Add dwmac-intel-plat for GBE driver (5.10)
  TSN support: 5a5586112b92   net: stmmac: support FPE link partner 
hand-shaking procedure (5.13)
  TSN support: 341f67e424e5   net: stmmac: Add hardware supported 
cross-timestamp (5.13)
  TSN support: 76da35dc99af   stmmac: intel: Add PSE and PCH PTP clock source 
selection (5.13)
  TSN support: 9f298959191b   net: stmmac: Add EST errors into ethtool 
statistic (5.13)
  TSN support: e49aa315cb01   net: stmmac: EST interrupts handling and error 
reporting (5.13)
  VLAN support: 0e039f5cf86c   net: stmmac: add RX frame steering based on VLAN 
priority in tc flower (5.13)
  VLAN support: bd0f670e7931   net: stmmac: restructure tc implementation for 
RX VLAN Priority steering (5.13)
  db2f2842e6f5   net: stmmac: add per-queue TX & RX coalesce ethtool support 
(5.13)
  TSN support: 3600be5f58c1   net: stmmac: add timestamp correction to rid CDC 
sync error (5.13)
  SGMII support: 7310fe538ea5   stmmac: intel: add pcs-xpcs for Intel mGbE 
controller (5.13)
  SGMII support: c62808e8105f   net: stmmac: ensure phydev is attached to 
phylink for C37 AN (5.13)
  SGMII support: e5e5b771f684   net: stmmac: make in-band AN mode parsing is 
supported for non-DT (5.13)
  TSN support: 8eb37ab7cc04   stmmac: intel: Fixes clock registration error 
seen for multiple interfaces (5.12)
  VLAN support: 9a7b3950c7e1   net: stmmac: Fix VLAN filter delete timeout 
issue in Intel mGBE SGMII (5.12)
  879c348c35bb   net: stmmac: fix incorrect DMA 

[Kernel-packages] [Bug 1842227] Re: [TGL] EDAC support for TGL(IoTG)

2021-11-24 Thread Ana Lasprilla
** Information type changed from Private 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/1842227

Title:
  [TGL] EDAC support for TGL(IoTG)

Status in intel:
  Fix Committed
Status in intel lookout-canyon series:
  Fix Released
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Description
  EDAC driver support on TGL(IoTG) for reporting ECC error and DIMM location

  Commit ids: 0b7338b27e82
  Target Release: 22.04
  Target Kernel: 5.14

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


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


[Kernel-packages] [Bug 1842144] Re: [EHL] Quadrature Encoder Peripheral support

2021-11-24 Thread Ana Lasprilla
** Information type changed from Private 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/1842144

Title:
  [EHL] Quadrature Encoder Peripheral support

Status in intel:
  Fix Committed
Status in intel lookout-canyon series:
  Fix Released
Status in linux package in Ubuntu:
  New

Bug description:
  Description:
  Support a quadrature encoder peripheral (QEP) that is a peripheral designed 
to interface to a shaft encoder fitted to either a motor shaft or a user 
interface dial, as a means to measure rotational speed, direction, and 
optionally absolute angle of rotation.

  Commit ids: b711f687a1c1
  Target Release: 22.04
  Target Kernel: 5.14

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


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


[Kernel-packages] [Bug 1948351] Re: ppc64 BPF JIT mod by 1 will not return 0

2021-11-24 Thread Kleber Sacilotto de Souza
Confirmed to be fixed on bionic/linux 4.15.0-163.171:

https://autopkgtest.ubuntu.com/results/autopkgtest-
bionic/bionic/ppc64el/l/linux/20211109_152821_48505@/log.gz

14:47:04 DEBUG| [stdout] selftests: test_bpf.sh
14:47:04 DEBUG| [stdout] 
14:47:07 DEBUG| [stdout] test_bpf: ok
14:47:07 DEBUG| [stdout] ok 1..8 selftests: test_bpf.sh [PASS]

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

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

Title:
  ppc64 BPF JIT mod by 1 will not return 0

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  When doing MOD by 1 with a immediate/constant divisor on PPC, the JIT will 
produce code that returns the dividend, just like a division, instead of 0.

  Both eBPF and cBPF will fail as well when doing such operations.

  [Test case]
  $ cat bpf-mod1.c
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  #define ARRAY_SIZE(array) (sizeof(array)/sizeof(array[0]))

  static int pair[2];

  static int attach()
  {
  int r;

  struct sock_filter insn[] = {
  { BPF_LD | BPF_W | BPF_ABS, 0, 0, 0 },
  { BPF_ALU | BPF_MOD, 0, 0, 1 },
  { BPF_RET | BPF_A, 0, 0, 0 },
  };

  struct sock_fprog prog = {};
  prog.filter = insn;
  prog.len = ARRAY_SIZE(insn);

  socketpair(AF_UNIX, SOCK_DGRAM, 0, pair);
  setsockopt(pair[1], SOL_SOCKET, SO_ATTACH_FILTER, , 
sizeof(prog));
  return 0;
  }

  int main(int argc, char **argv)
  {
  int buf[5];
  int r;
  r = attach();
  if (r < 0) {
  err(1, "function will error out already");
  }
  write(pair[0], "hello", 5);
  r = recv(pair[1], buf, 5, MSG_DONTWAIT);
  if (r != -1 || errno != EAGAIN) {
  err(1, "program failed");
  }
  return 0;
  }
  $ gcc -o bpf-mod1 bpf-mod1.c
  $ ./bpf-mod1
  cbpf-mod1: program failed: Success

  After fix:
  $ ./bpf-mod1
  $ echo $?
  0

  [Potential regression]
  BPF programs might be misbehave on ppc64el.

  

  This is a scripted bug report about ADT failures while running linux
  tests for linux/5.4.0-90.101 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Consistently failing on Focal/linux 5.4.0-90.101

  13:15:26 DEBUG| [stdout] # selftests: net: test_bpf.sh
  13:15:27 DEBUG| [stdout] # test_bpf: [FAIL]
  13:15:27 DEBUG| [stdout] not ok 9 selftests: net: test_bpf.sh # exit=1

  Testing failed on:
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20211021_141544_eda49@/log.gz

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


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


[Kernel-packages] [Bug 1934414] Re: test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153 i386 (Segmentation fault)

2021-11-24 Thread Kleber Sacilotto de Souza
Confirmed test_bpf.sh is now successfully on i386 with bionic/linux
4.15.0-163.171:

https://autopkgtest.ubuntu.com/results/autopkgtest-
bionic/bionic/i386/l/linux/2027_200907_95566@/log.gz

18:27:04 INFO | START   ubuntu_kernel_selftests.net:test_bpf.sh 
ubuntu_kernel_selftests.net:test_bpf.sh timestamp=1637173624timeout=1800
localtime=Nov 17 18:27:04   
18:27:04 DEBUG| Persistent state client._record_indent now set to 2
18:27:04 DEBUG| Persistent state client.unexpected_reboot now set to 
('ubuntu_kernel_selftests.net:test_bpf.sh', 
'ubuntu_kernel_selftests.net:test_bpf.sh')
18:27:04 DEBUG| Waiting for pid 10439 for 1800 seconds
18:27:04 DEBUG| Running 'make run_tests -C net TEST_PROGS=test_bpf.sh 
TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
18:27:04 DEBUG| [stdout] make: Entering directory 
'/tmp/autopkgtest.U5vLyA/build.Xnj/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
18:27:04 DEBUG| [stdout] make --no-builtin-rules ARCH=x86 -C ../../../.. 
headers_install
18:27:04 DEBUG| [stdout] make[1]: Entering directory 
'/tmp/autopkgtest.U5vLyA/build.Xnj/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
18:27:05 DEBUG| [stdout]   CHK include/generated/uapi/linux/version.h
18:27:05 DEBUG| [stdout] make[1]: Leaving directory 
'/tmp/autopkgtest.U5vLyA/build.Xnj/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
18:27:05 DEBUG| [stdout] TAP version 13
18:27:05 DEBUG| [stdout] selftests: test_bpf.sh
18:27:05 DEBUG| [stdout] 
18:27:28 DEBUG| [stdout] test_bpf: ok
18:27:28 DEBUG| [stdout] ok 1..1 selftests: test_bpf.sh [PASS]
18:27:28 DEBUG| [stdout] make: Leaving directory 
'/tmp/autopkgtest.U5vLyA/build.Xnj/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
18:27:28 INFO | GOODubuntu_kernel_selftests.net:test_bpf.sh 
ubuntu_kernel_selftests.net:test_bpf.sh timestamp=1637173648localtime=Nov 
17 18:27:28   completed successfully
18:27:28 INFO | END GOODubuntu_kernel_selftests.net:test_bpf.sh 
ubuntu_kernel_selftests.net:test_bpf.sh timestamp=1637173648localtime=Nov 
17 18:27:28   

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

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

Title:
  test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test
  failure with linux/4.15.0-149.153 i386 (Segmentation fault)

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  selftests net will fail on i386, requiring engineers time to investigate, or 
leading to new BPF failures to be ignored.

  [Fix]
  The fix is only to tests.

  [Test case]
  Run test_bpf.sh from tools/testing/selftests/net/.

  [Potential regression]
  Tests could fail on other architectures.

  
  

  
  This is a scripted bug report about ADT failures while running linux tests 
for linux/4.15.0-149.153 on bionic. Whether this is caused by the dep8 tests of 
the tested source or the kernel has yet to be determined.

  Testing failed on:
  i386: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210702_010055_445cd@/log.gz

  03:37:02 DEBUG| [stdout] selftests: test_bpf.sh
  03:37:02 DEBUG| [stdout] 
  03:37:03 ERROR| [stderr] Segmentation fault
  03:37:03 DEBUG| [stdout] test_bpf: [FAIL]
  03:37:03 DEBUG| [stdout] not ok 1..8 selftests:  test_bpf.sh [FAIL]
  03:37:03 DEBUG| [stdout] selftests: netdevice.sh
  03:37:03 DEBUG| [stdout] 

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


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


[Kernel-packages] [Bug 1928188] Re: Build libclc from llvm

2021-11-24 Thread Timo Aaltonen
** Changed in: llvm-toolchain-12 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Build libclc from llvm

Status in llvm-toolchain-12 package in Ubuntu:
  Fix Released
Status in llvm-toolchain-12 source package in Focal:
  Fix Released
Status in llvm-toolchain-12 source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  libclc source was merged to llvm upstream last year, and development
  happens there now. A future mesa release will require libclc from
  llvm-toolchain, but in order to migrate things one at a time, let's
  build libclc with "old" features first.

  
  [Test case]

  Build mesa with libclc-12 from llvm-toolchain-12.

  
  [Where problems could occur]

  Packaging might conflict with src:libclc, but that's already tested to
  be fine. There is also an autopkgtest to catch possible regressions
  with libclc-12.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-12/+bug/1928188/+subscriptions


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


[Kernel-packages] [Bug 1814295] Re: qa-regression-testing test_ulimit_stack_small fails on ppc64el/i386

2021-11-24 Thread Kleber Sacilotto de Souza
** Tags added: sru-20211108

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

Title:
  qa-regression-testing test_ulimit_stack_small fails on ppc64el/i386

Status in QA Regression Testing:
  Confirmed
Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-
  disco/disco/ppc64el/l/linux/20190201_153123_8340c@/log.gz

==
FAIL: test_ulimit_stack_small (__main__.KernelNonSecurityTest)
Ensure small stack limits are enforced
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 2847, in test_ulimit_stack_small
self.assertShellExitIn(expected, self._unpriv_cmd(["sh", "-c", "ulimit 
-s 1 && /bin/true"]))
  File 
"/tmp/autopkgtest.aOkL2y/build.mxm/src/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1151, in assertShellExitIn
self.assertIn(rc, expected, msg + result + report)
AssertionError: Got exit code 0, expected one of 139
Command: 'sudo', '-u', 'ubuntu', 'sh', '-c', 'ulimit -s 1 && /bin/true'
Output:


--

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1814295/+subscriptions


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


[Kernel-packages] [Bug 1837037] Re: memcg_move_charge_at_immigrate_test from controllers in ubuntu_ltp

2021-11-24 Thread Kleber Sacilotto de Souza
** Summary changed:

- memcg_move_charge_at_immigrate_test from controllers in ubuntu_ltp failed 
with i386
+ memcg_move_charge_at_immigrate_test from controllers in ubuntu_ltp

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

Title:
  memcg_move_charge_at_immigrate_test from controllers in ubuntu_ltp

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Won't Fix

Bug description:
  Similar to bug 1837035

  This memcg_move_charge_at_immigrate_test test failed on an i386 node
  "pepe" with Disco kernel.

  It failed with:
  memcg_move_charge_at_immigrate_test 5 TINFO: Warming up pid: 2192
  memcg_process: shmget() failed: Invalid argument
  /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No 
such process

  memcg_move_charge_at_immigrate_test 5 TFAIL: Process 2192 exited with
  1 after warm up

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

  memcg_move_charge_at_immigrate_test 5 TFAIL: Process 2192 exited with 1 after 
warm up
  memcg_move_charge_at_immigrate_test 6 TINFO: Starting test 3
  /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: 
echo: I/O error
  memcg_move_charge_at_immigrate_test 6 TINFO: set 
/dev/memcg/memory.use_hierarchy to 0 failed
  memcg_move_charge_at_immigrate_test 6 TINFO: Running memcg_process 
--mmap-anon --shm --mmap-file -s 135168
  memcg_move_charge_at_immigrate_test 6 TINFO: Warming up pid: 2207
  memcg_process: shmget() failed: Invalid argument
  /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No 
such process

  memcg_move_charge_at_immigrate_test 6 TFAIL: Process 2207 exited with 1 after 
warm up
  memcg_move_charge_at_immigrate_test 7 TINFO: Starting test 4
  /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: 
echo: I/O error
  memcg_move_charge_at_immigrate_test 7 TINFO: set 
/dev/memcg/memory.use_hierarchy to 0 failed
  memcg_move_charge_at_immigrate_test 7 TINFO: Running memcg_process 
--mmap-anon --shm -s 135168
  memcg_move_charge_at_immigrate_test 7 TINFO: Warming up pid: 
  memcg_process: shmget() failed: Invalid argument
  /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No 
such process

  memcg_move_charge_at_immigrate_test 7 TFAIL: Process  exited with 1 after 
warm up
  <<>>
  initiation_status="ok"
  duration=4 termination_type=exited termination_id=1 corefile=no
  cutime=9 cstime=2
  <<>>

  Steps to run this test:
    git clone --depth=1 https://github.com/linux-test-project/ltp.git
    cd ltp; make autotools; ./configure; make; sudo make install
    echo "memcg_move_charge_at_immigrate  
memcg_move_charge_at_immigrate_test.sh" > /tmp/jobs
    sudo /opt/ltp/runltp -f /tmp/jobs

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-21-generic 5.0.0-21.22
  ProcVersionSignature: User Name 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic i686
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 18 10:01 seq
   crw-rw 1 root audio 116, 33 Jul 18 10:01 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] 

[Kernel-packages] [Bug 1949924] Re: yelp crashes in wayland session with NVIDIA 470

2021-11-24 Thread Launchpad Bug Tracker
This bug was fixed in the package egl-wayland - 1:1.1.9-1.1

---
egl-wayland (1:1.1.9-1.1) unstable; urgency=medium

  * Non-maintainer upload
  * d/p/egl-wayland-retrieve-DRM-device-name-before-acquiring-.patch:
- Cherry picked upstream commit to fix lock issue (LP: #1949924)

 -- Gunnar Hjalmarsson   Wed, 24 Nov 2021 04:39:34
+0100

** Changed in: egl-wayland (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  yelp crashes in wayland session with NVIDIA 470

Status in NVIDIA / egl-wayland:
  New
Status in egl-wayland package in Ubuntu:
  Fix Released
Status in yelp package in Ubuntu:
  Invalid

Bug description:
  $ yelp
  yelp: ../src/wayland-thread.c:87: wlExternalApiLock: Assertion `!"failed to 
lock pthread mutex"' failed.
  Aborted (core dumped)

  This does not happen in Debian testing, and it also works as expected
  in an Ubuntu on Xorg session.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: yelp 41.1-1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  5 02:51:43 2021
  InstallationDate: Installed on 2019-11-10 (725 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: yelp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/egl-wayland/+bug/1949924/+subscriptions


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


[Kernel-packages] [Bug 1952094] Re: CIFS mount error: iocharset utf8 not found

2021-11-24 Thread Tim Gardner
There are 2 patches against fs/cifs in that interval:

git log --pretty=oneline Ubuntu-5.4.0-89.100..Ubuntu-5.4.0-90.101 -- fs/cifs/
bc3d24f536d5e79ba474f192280a18d060a4c33f cifs: fix wrong release in 
sess_alloc_buffer() failed path
3d5631a27ec4767ac80dbf553f9ae501b18e07e3 CIFS: Fix a potencially linear read 
overflow

The second patch touches fs/cifs/cifs_unicode.c which makes it a strong
candidate for having caused this regression. Please try the following
kernel which has that patch reverted:

wget 
https://kernel.ubuntu.com/~rtg/lp1952094/amd64/linux-image-unsigned-5.4.0-91-generic_5.4.0-91.102~lp1952094.1_amd64.deb
wget 
https://kernel.ubuntu.com/~rtg/lp1952094/amd64/linux-modules-5.4.0-91-generic_5.4.0-91.102~lp1952094.1_amd64.deb
wget 
https://kernel.ubuntu.com/~rtg/lp1952094/amd64/linux-modules-extra-5.4.0-91-generic_5.4.0-91.102~lp1952094.1_amd64.deb
sudo dpkg -i linux*.deb
sudo reboot


** 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: Incomplete => Invalid

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

Title:
  CIFS mount error: iocharset utf8 not found

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

Bug description:
  After i apt upgrade from linux-image-5.4.0-89-generic to 
linux-image-5.4.0-90-generic, mount.cifs failed with dmesg "CIFS VFS: CIFS 
mount error: iocharset utf8 not found", and i rollback it and it restores.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 24 20:16 seq
   crw-rw 1 root audio 116, 33 Nov 24 20:16 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:
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-07 (109 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic 
root=UUID=fd942b77-19c9-4959-a01c-c8e3f7b583b6 ro
  ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-89-generic N/A
   linux-backports-modules-5.4.0-89-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 1425-2986-4285-1154-1589-7450-41
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd12/17/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.0
  dmi.sys.vendor: Microsoft Corporation

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


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


[Kernel-packages] [Bug 1950239] Re: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS

2021-11-24 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-oem-5.10/5.10.0-1052.54
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

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

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


** Tags added: verification-needed-focal

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

Title:
  creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from
  ubuntu_ltp/cve failed with XFS

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem-5.10 source package in Bionic:
  Invalid
Status in linux-oem-5.14 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.10 source package in Focal:
  Fix Committed
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.14 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  Fix Released
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid

Bug description:
  [Impact]
  setgid files may be created on setgid directories owned by the directory
  group by users not belonging to that group. That is restricted to XFS.

  [Fix/Backport]
  The fix for 5.11 and 5.10 kernels is one simple commit with a minor
  backport conflict fixup on 5.10.

  5.4, on the other hand, required other 3 pre-requisites, which could be
  picked cleanly. On 4.15, however, they needed a lot of mangling and fixes.

  [Test case]
  creat09 LTP test case.

  [Potential regression]
  The creation of files on XFS may have the wrong attributes. Also, on 5.4
  and 4.15, the potential regression is larger, also affecting quota,
  statistics and other interfaces where uid, gid and projid are exposed.

  
  =

  These two tests, creat09 from ubuntu_ltp_syscalls and cve-2018-13405
  from ubuntu_ltp/cve are actually the same test.

  Issue found on F-oem-5.10.0-1051.53

  With LTP upstream head SHA1 2ac54d426

  This is not a regression, it's because of a recent update that enables this 
test on different filesystems:
  
https://github.com/linux-test-project/ltp/commit/433b6cf7ade3d5e3bd4b85ac89b164c53312e65a

  Test failed on XFS with:
  tst_test.c:1431: TINFO: Testing on xfs
  tst_test.c:932: TINFO: Formatting /dev/loop3 with xfs opts='' extra opts=''
  tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s
  creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534
  creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0)
  creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group
  creat09.c:92: TFAIL: mntpoint/testdir/creat.tmp: Setgid bit is set
  creat09.c:88: TPASS: mntpoint/testdir/open.tmp: Owned by correct group
  creat09.c:92: TFAIL: mntpoint/testdir/open.tmp: Setgid bit is set

  Test log:
  Checking for required user/group ids

  'nobody' user id and group found.
  'bin' user id and group found.
  'daemon' user id and group found.
  Users group found.
  Sys group found.
  Required users/groups exist.
  no big block device was specified on commandline.
  Tests which require a big block device are disabled.
  You can specify it with option -z
  INFO: Test start time: Mon Nov  8 10:00:06 UTC 2021
  COMMAND:/opt/ltp/bin/ltp-pan -q  -e -S   -a 61758 -n 61758  -f 
/tmp/ltp-shLYORuoRT/alltests -l /dev/null  -C /dev/null -T /dev/null
  LOG File: /dev/null
  FAILED COMMAND File: /dev/null
  TCONF COMMAND File: /dev/null
  Running tests...
  tst_device.c:88: TINFO: Found free device 3 '/dev/loop3'
  tst_supported_fs_types.c:88: TINFO: Kernel supports ext2
  tst_supported_fs_types.c:50: TINFO: mkfs.ext2 does exist
  tst_supported_fs_types.c:88: TINFO: Kernel supports ext3
  tst_supported_fs_types.c:50: TINFO: mkfs.ext3 does exist
  tst_supported_fs_types.c:88: TINFO: Kernel supports ext4
  tst_supported_fs_types.c:50: TINFO: mkfs.ext4 does exist
  tst_supported_fs_types.c:88: TINFO: Kernel supports xfs
  tst_supported_fs_types.c:50: TINFO: mkfs.xfs does exist
  tst_supported_fs_types.c:88: TINFO: Kernel supports btrfs
  tst_supported_fs_types.c:50: TINFO: mkfs.btrfs does exist
  

[Kernel-packages] [Bug 1869083] Re: pipe state doesn't match! [i915]

2021-11-24 Thread Leho Kraav
Yes, I can see this still in 5.15.1.

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

Title:
  pipe state doesn't match! [i915]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 7390 with Dell WD15 with 2 external screens (on HDMI and DP)
  Ubuntu 5.3.0-42.34-generic 5.3.18
  Description:  Ubuntu 19.10
  Release:  19.10

  Kernel crash while idling unattended:

  Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216046] [ cut here 
]
  Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216046] pipe state doesn't match!
  Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216094] WARNING: CPU: 6 PID: 
3714 at drivers/gpu/drm/i915/display/intel_display.c:13006 
verify_crtc_state+0x2ad/0x300 [i915]
  Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216094] Modules linked in: 
rfcomm binfmt_misc veth nft_masq nft_chain_nat bridge stp llc zfs(PO) 
zunicode(PO) zavl(PO) icp(PO) zlua(PO) zcommon(PO) znvpair(PO) spl(O) 
ebtable_filter ebtables ip6table_raw ip6table_mangle ip6table_nat ip6table_filte
  r ip6_tables iptable_raw iptable_mangle iptable_nat nf_nat nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c iptable_filter bpfilter nf_tables 
nfnetlink ccm typec_displayport cmac bnep nls_is
  o8859_1 sof_pci_dev snd_sof_intel_hda_common snd_hda_codec_hdmi 
snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof 
snd_sof_xtensa_dsp snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match 
snd_soc_acpi snd_soc_core snd_hda_codec_realtek snd_compress 
snd_hda_codec_generic ac97_bus snd_pcm_dmaengine joydev snd_hda_intel mei_hdcp 
snd_intel_nhlt snd_hda_codec snd_hda_core intel_rapl_msr snd_usb_audio 
snd_usbmidi_lib snd_hwdep snd_pcm x86_pkg_temp_thermal intel_powerclamp iwlmvm
  Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216108]  coretemp snd_seq_midi 
mac80211 snd_seq_midi_event kvm_intel libarc4 dell_laptop ledtrig_audio 
snd_rawmidi kvm snd_seq irqbypass dell_wmi intel_cstate dell_smbios 
intel_rapl_perf dcdbas uvcvideo iwlwifi snd_seq_device input_leds 
dell_wmi_descriptor snd_timer videobuf2_vmalloc cdc_ether serio_raw 
videobuf2_memops usbnet intel_wmi_thunderbolt videobuf2_v4l2 btusb r8152 btrtl 
videobuf2_common mii btbcm btintel snd videodev wmi_bmof bluetooth rtsx_pci_ms 
mc soundcore cfg80211 memstick mei_me ecdh_generic hid_multitouch mei ecc 
idma64 virt_dma processor_thermal_device intel_rapl_common intel_soc_dts_iosf 
ucsi_acpi typec_ucsi typec int3403_thermal int340x_thermal_zone mac_hid 
intel_hid acpi_tad int3400_thermal acpi_pad acpi_thermal_rel sparse_keymap 
sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt 
hid_generic uas usb_storage crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
rtsx_pci_sdmmc i915 aesni_intel aes_x86_64 crypto_simd cryptd glue_helper
  Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216123]  i2c_algo_bit 
drm_kms_helper psmouse syscopyarea sysfillrect nvme sysimgblt fb_sys_fops 
i2c_i801 thunderbolt nvme_core drm rtsx_pci intel_lpss_pci intel_lpss i2c_hid 
wmi hid pinctrl_cannonlake video pinctrl_intel
  Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216129] CPU: 6 PID: 3714 Comm: 
gnome-shell Tainted: PW  O  5.3.0-42-generic #34-Ubuntu
  Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216129] Hardware name: Dell Inc. 
XPS 13 7390/0G2D0W, BIOS 1.4.0 11/25/2019
  Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216144] RIP: 
0010:verify_crtc_state+0x2ad/0x300 [i915]
  Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216145] Code: b6 45 bf e9 8d fe 
ff ff 80 3d 55 0d 10 00 00 0f b6 f0 48 c7 c7 f0 93 92 c0 75 32 e8 9d d7 9d ff 
e9 1e fe ff ff e8 7e cf 04 e6 <0f> 0b e9 1b ff ff ff e8 72 cf 04 e6 0f 0b e9 85 
fe ff ff e8 66 cf
  Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216145] RSP: 
0018:af5cc5fa3ac8 EFLAGS: 00010282
  Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216146] RAX:  
RBX: 914b6b5e02b0 RCX: 0006
  Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216147] RDX: 0007 
RSI: 0086 RDI: 914b7e797440
  Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216147] RBP: af5cc5fa3b10 
R08: d967 R09: 0004
  Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216147] R10:  
R11: 0001 R12: 914b7bcd3000
  Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216148] R13: 914b6b5e02b8 
R14: 914b6b5e R15: 914b20336000
  Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216148] FS:  
7f0835d3ecc0() GS:914b7e78() knlGS:
  Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216149] CS:  0010 DS:  ES: 
 CR0: 80050033
  Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216149] CR2: 3b18df55a000 
CR3: 0003ee6f2005 CR4: 003606e0
  Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216150] 

[Kernel-packages] [Bug 1615405] Re: zfs share doesn't work

2021-11-24 Thread Aron Xu
Should be fixed at least since 20.04 LTS

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

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

Title:
  zfs share doesn't work

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  I'm testing on Ubuntu 16.04 with the included zol 0.6.5.

  I have also reported this bug here:
  https://github.com/zfsonlinux/zfs/issues/4999

  zfs share and zfs share -a just don't work. zfs set sharesmb=on
  pool/dataset works fine. I discovered that the shares are listed in
  /etc/dfs/sharetab but don't work. If I reboot or anything and try to
  share them again with zfs share, it will not work. net usershare list
  displays nothing. And of course because of this all shares are lost on
  every reboot.

  Despite a dataset having the sharesmb=on value set, it will not share
  with zfs share -a and if I use zfs share pool/dataset it says: cannot
  share 'pool/dataset': filesystem already shared, when net usershare
  list shows nothing**. Samba is running and the shares appear in
  /etc/dfs/sharetab, not that that is helping me.

  I've detailed a bunch of stuff at serverfault... if that's not good
  enough, I can bring some of it over here:

  http://serverfault.com/questions/797938/ubuntu-xenial-16-04-zfs-share-
  command-doesnt-work-for-smb-shares

  System/package informatiom

  zfsutils-linux:
Installed: 0.6.5.6-0ubuntu12
Candidate: 0.6.5.6-0ubuntu12
Version table:
   *** 0.6.5.6-0ubuntu12 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.6.5.6-0ubuntu8 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: zfsutils-linux 0.6.5.6-0ubuntu12
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Aug 21 12:11:47 2016
  InstallationDate: Installed on 2016-05-26 (87 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.zfs: [modified]
  mtime.conffile..etc.default.zfs: 2016-07-12T22:45:19.830513

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


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


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

2021-11-24 Thread ayanamist
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1952094/+attachment/5543072/+files/CurrentDmesg.txt

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

Title:
  CIFS mount error: iocharset utf8 not found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After i apt upgrade from linux-image-5.4.0-89-generic to 
linux-image-5.4.0-90-generic, mount.cifs failed with dmesg "CIFS VFS: CIFS 
mount error: iocharset utf8 not found", and i rollback it and it restores.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 24 20:16 seq
   crw-rw 1 root audio 116, 33 Nov 24 20:16 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:
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-07 (109 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic 
root=UUID=fd942b77-19c9-4959-a01c-c8e3f7b583b6 ro
  ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-89-generic N/A
   linux-backports-modules-5.4.0-89-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 1425-2986-4285-1154-1589-7450-41
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd12/17/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.0
  dmi.sys.vendor: Microsoft Corporation

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


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


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

2021-11-24 Thread ayanamist
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1952094/+attachment/5543077/+files/ProcModules.txt

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

Title:
  CIFS mount error: iocharset utf8 not found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After i apt upgrade from linux-image-5.4.0-89-generic to 
linux-image-5.4.0-90-generic, mount.cifs failed with dmesg "CIFS VFS: CIFS 
mount error: iocharset utf8 not found", and i rollback it and it restores.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 24 20:16 seq
   crw-rw 1 root audio 116, 33 Nov 24 20:16 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:
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-07 (109 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic 
root=UUID=fd942b77-19c9-4959-a01c-c8e3f7b583b6 ro
  ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-89-generic N/A
   linux-backports-modules-5.4.0-89-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 1425-2986-4285-1154-1589-7450-41
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd12/17/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.0
  dmi.sys.vendor: Microsoft Corporation

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


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


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

2021-11-24 Thread ayanamist
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1952094/+attachment/5543074/+files/ProcCpuinfo.txt

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

Title:
  CIFS mount error: iocharset utf8 not found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After i apt upgrade from linux-image-5.4.0-89-generic to 
linux-image-5.4.0-90-generic, mount.cifs failed with dmesg "CIFS VFS: CIFS 
mount error: iocharset utf8 not found", and i rollback it and it restores.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 24 20:16 seq
   crw-rw 1 root audio 116, 33 Nov 24 20:16 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:
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-07 (109 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic 
root=UUID=fd942b77-19c9-4959-a01c-c8e3f7b583b6 ro
  ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-89-generic N/A
   linux-backports-modules-5.4.0-89-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 1425-2986-4285-1154-1589-7450-41
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd12/17/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.0
  dmi.sys.vendor: Microsoft Corporation

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


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


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

2021-11-24 Thread ayanamist
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1952094/+attachment/5543076/+files/ProcInterrupts.txt

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

Title:
  CIFS mount error: iocharset utf8 not found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After i apt upgrade from linux-image-5.4.0-89-generic to 
linux-image-5.4.0-90-generic, mount.cifs failed with dmesg "CIFS VFS: CIFS 
mount error: iocharset utf8 not found", and i rollback it and it restores.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 24 20:16 seq
   crw-rw 1 root audio 116, 33 Nov 24 20:16 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:
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-07 (109 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic 
root=UUID=fd942b77-19c9-4959-a01c-c8e3f7b583b6 ro
  ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-89-generic N/A
   linux-backports-modules-5.4.0-89-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 1425-2986-4285-1154-1589-7450-41
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd12/17/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.0
  dmi.sys.vendor: Microsoft Corporation

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


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


[Kernel-packages] [Bug 1952094] HookError_ubuntu.txt

2021-11-24 Thread ayanamist
apport information

** Attachment added: "HookError_ubuntu.txt"
   
https://bugs.launchpad.net/bugs/1952094/+attachment/5543073/+files/HookError_ubuntu.txt

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

Title:
  CIFS mount error: iocharset utf8 not found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After i apt upgrade from linux-image-5.4.0-89-generic to 
linux-image-5.4.0-90-generic, mount.cifs failed with dmesg "CIFS VFS: CIFS 
mount error: iocharset utf8 not found", and i rollback it and it restores.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 24 20:16 seq
   crw-rw 1 root audio 116, 33 Nov 24 20:16 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:
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-07 (109 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic 
root=UUID=fd942b77-19c9-4959-a01c-c8e3f7b583b6 ro
  ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-89-generic N/A
   linux-backports-modules-5.4.0-89-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 1425-2986-4285-1154-1589-7450-41
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd12/17/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.0
  dmi.sys.vendor: Microsoft Corporation

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


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


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

2021-11-24 Thread ayanamist
apport information

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

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

Title:
  CIFS mount error: iocharset utf8 not found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After i apt upgrade from linux-image-5.4.0-89-generic to 
linux-image-5.4.0-90-generic, mount.cifs failed with dmesg "CIFS VFS: CIFS 
mount error: iocharset utf8 not found", and i rollback it and it restores.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 24 20:16 seq
   crw-rw 1 root audio 116, 33 Nov 24 20:16 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:
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-07 (109 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic 
root=UUID=fd942b77-19c9-4959-a01c-c8e3f7b583b6 ro
  ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-89-generic N/A
   linux-backports-modules-5.4.0-89-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 1425-2986-4285-1154-1589-7450-41
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd12/17/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.0
  dmi.sys.vendor: Microsoft Corporation

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


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


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

2021-11-24 Thread ayanamist
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1952094/+attachment/5543078/+files/UdevDb.txt

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

Title:
  CIFS mount error: iocharset utf8 not found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After i apt upgrade from linux-image-5.4.0-89-generic to 
linux-image-5.4.0-90-generic, mount.cifs failed with dmesg "CIFS VFS: CIFS 
mount error: iocharset utf8 not found", and i rollback it and it restores.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 24 20:16 seq
   crw-rw 1 root audio 116, 33 Nov 24 20:16 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:
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-07 (109 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic 
root=UUID=fd942b77-19c9-4959-a01c-c8e3f7b583b6 ro
  ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-89-generic N/A
   linux-backports-modules-5.4.0-89-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 1425-2986-4285-1154-1589-7450-41
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd12/17/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.0
  dmi.sys.vendor: Microsoft Corporation

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


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


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

2021-11-24 Thread ayanamist
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1952094/+attachment/5543075/+files/ProcCpuinfoMinimal.txt

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

Title:
  CIFS mount error: iocharset utf8 not found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After i apt upgrade from linux-image-5.4.0-89-generic to 
linux-image-5.4.0-90-generic, mount.cifs failed with dmesg "CIFS VFS: CIFS 
mount error: iocharset utf8 not found", and i rollback it and it restores.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 24 20:16 seq
   crw-rw 1 root audio 116, 33 Nov 24 20:16 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:
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-07 (109 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic 
root=UUID=fd942b77-19c9-4959-a01c-c8e3f7b583b6 ro
  ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-89-generic N/A
   linux-backports-modules-5.4.0-89-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 1425-2986-4285-1154-1589-7450-41
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd12/17/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.0
  dmi.sys.vendor: Microsoft Corporation

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


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


[Kernel-packages] [Bug 1952094] acpidump.txt

2021-11-24 Thread ayanamist
apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1952094/+attachment/5543080/+files/acpidump.txt

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

Title:
  CIFS mount error: iocharset utf8 not found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After i apt upgrade from linux-image-5.4.0-89-generic to 
linux-image-5.4.0-90-generic, mount.cifs failed with dmesg "CIFS VFS: CIFS 
mount error: iocharset utf8 not found", and i rollback it and it restores.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 24 20:16 seq
   crw-rw 1 root audio 116, 33 Nov 24 20:16 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:
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-07 (109 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic 
root=UUID=fd942b77-19c9-4959-a01c-c8e3f7b583b6 ro
  ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-89-generic N/A
   linux-backports-modules-5.4.0-89-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 12/17/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 1425-2986-4285-1154-1589-7450-41
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd12/17/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.0
  dmi.sys.vendor: Microsoft Corporation

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


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


[Kernel-packages] [Bug 1952094] Re: CIFS mount error: iocharset utf8 not found

2021-11-24 Thread ayanamist
apport information

** Tags added: apport-collected uec-images

** Description changed:

- After i apt upgrade from linux-image-5.4.0-89-generic to linux-
- image-5.4.0-90-generic, mount.cifs failed with dmesg "CIFS VFS: CIFS
- mount error: iocharset utf8 not found", and i rollback it and it
- restores.
+ After i apt upgrade from linux-image-5.4.0-89-generic to 
linux-image-5.4.0-90-generic, mount.cifs failed with dmesg "CIFS VFS: CIFS 
mount error: iocharset utf8 not found", and i rollback it and it restores.
+ --- 
+ ProblemType: Bug
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 Nov 24 20:16 seq
+  crw-rw 1 root audio 116, 33 Nov 24 20:16 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:
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2021-08-07 (109 days ago)
+ InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
+ Lspci:
+  
+ Lspci-vt: -[:00]-
+ Lsusb: Error: command ['lsusb'] failed with exit code 1:
+ Lsusb-t:
+  
+ Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
+ MachineType: Microsoft Corporation Virtual Machine
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  TERM=screen-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/zsh
+ ProcFB: 0 hyperv_fb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic 
root=UUID=fd942b77-19c9-4959-a01c-c8e3f7b583b6 ro
+ ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143
+ RelatedPackageVersions:
+  linux-restricted-modules-5.4.0-89-generic N/A
+  linux-backports-modules-5.4.0-89-generic  N/A
+  linux-firmwareN/A
+ RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
+ Tags:  focal uec-images
+ Uname: Linux 5.4.0-89-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lxd plugdev sudo
+ _MarkForUpload: True
+ dmi.bios.date: 12/17/2019
+ dmi.bios.vendor: Microsoft Corporation
+ dmi.bios.version: Hyper-V UEFI Release v4.0
+ dmi.board.asset.tag: None
+ dmi.board.name: Virtual Machine
+ dmi.board.vendor: Microsoft Corporation
+ dmi.board.version: Hyper-V UEFI Release v4.0
+ dmi.chassis.asset.tag: 1425-2986-4285-1154-1589-7450-41
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Microsoft Corporation
+ dmi.chassis.version: Hyper-V UEFI Release v4.0
+ dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd12/17/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
+ dmi.product.family: Virtual Machine
+ dmi.product.name: Virtual Machine
+ dmi.product.sku: None
+ dmi.product.version: Hyper-V UEFI Release v4.0
+ dmi.sys.vendor: Microsoft Corporation

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1952094/+attachment/5543071/+files/CRDA.txt

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

Title:
  CIFS mount error: iocharset utf8 not found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After i apt upgrade from linux-image-5.4.0-89-generic to 
linux-image-5.4.0-90-generic, mount.cifs failed with dmesg "CIFS VFS: CIFS 
mount error: iocharset utf8 not found", and i rollback it and it restores.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 24 20:16 seq
   crw-rw 1 root audio 116, 33 Nov 24 20:16 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:
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-07 (109 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic 

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

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

apport-collect 1952094

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

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

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

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

** Tags added: focal

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

Title:
  CIFS mount error: iocharset utf8 not found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After i apt upgrade from linux-image-5.4.0-89-generic to linux-
  image-5.4.0-90-generic, mount.cifs failed with dmesg "CIFS VFS: CIFS
  mount error: iocharset utf8 not found", and i rollback it and it
  restores.

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


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


[Kernel-packages] [Bug 1952094] [NEW] CIFS mount error: iocharset utf8 not found

2021-11-24 Thread ayanamist
Public bug reported:

After i apt upgrade from linux-image-5.4.0-89-generic to linux-
image-5.4.0-90-generic, mount.cifs failed with dmesg "CIFS VFS: CIFS
mount error: iocharset utf8 not found", and i rollback it and it
restores.

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

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

Title:
  CIFS mount error: iocharset utf8 not found

Status in linux package in Ubuntu:
  New

Bug description:
  After i apt upgrade from linux-image-5.4.0-89-generic to linux-
  image-5.4.0-90-generic, mount.cifs failed with dmesg "CIFS VFS: CIFS
  mount error: iocharset utf8 not found", and i rollback it and it
  restores.

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


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


[Kernel-packages] [Bug 1951997] Re: Bionic update: upstream stable patchset 2021-11-23

2021-11-24 Thread Stefan Bader
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  Bionic update: upstream stable patchset 2021-11-23

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  SRU Justification

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

     upstream stable patchset 2021-11-23

  Ported from the following upstream stable releases:
  v4.14.253, v4.19.214

     from git://git.kernel.org/

  btrfs: always wait on ordered extents at fsync time
  ARM: dts: at91: sama5d2_som1_ek: disable ISC node by default
  xtensa: xtfpga: use CONFIG_USE_OF instead of CONFIG_OF
  xtensa: xtfpga: Try software restart before simulating CPU reset
  NFSD: Keep existing listeners on portlist error
  netfilter: ipvs: make global sysctl readonly in non-init netns
  NIOS2: irqflags: rename a redefined register name
  can: rcar_can: fix suspend/resume
  can: peak_usb: pcan_usb_fd_decode_status(): fix back to ERROR_ACTIVE state 
notification
  can: peak_pci: peak_pci_remove(): fix UAF
  ocfs2: fix data corruption after conversion from inline format
  ocfs2: mount fails with buffer overflow in strlen
  elfcore: correct reference to CONFIG_UML
  ALSA: usb-audio: Provide quirk for Sennheiser GSP670 Headset
  ASoC: DAPM: Fix missing kctl change notifications
  nfc: nci: fix the UAF of rf_conn_info object
  isdn: cpai: check ctr->cnr to avoid array index out of bound
  netfilter: Kconfig: use 'default y' instead of 'm' for bool config option
  btrfs: deal with errors when checking if a dir entry exists during log replay
  net: stmmac: add support for dwmac 3.40a
  ARM: dts: spear3xx: Fix gmac node
  isdn: mISDN: Fix sleeping function called from invalid context
  platform/x86: intel_scu_ipc: Update timeout value in comment
  ALSA: hda: avoid write to STATESTS if controller is in reset
  tracing: Have all levels of checks prevent recursion
  ARM: 9122/1: select HAVE_FUTEX_CMPXCHG
  dma-debug: fix sg checks in debug_dma_map_sg()
  ASoC: wm8960: Fix clock configuration on slave mode
  lan78xx: select CRC32
  net: hns3: add limit ets dwrr bandwidth cannot be 0
  net: hns3: disable sriov before unload hclge layer
  ALSA: hda/realtek: Add quirk for Clevo PC50HS
  mm, slub: fix mismatch between reconstructed freelist depth and cnt
  gcc-plugins/structleak: add makefile var for disabling structleak
  UBUNTU: upstream stable to v4.14.253, v4.19.214

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


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


[Kernel-packages] [Bug 1951883] Re: Focal update: v5.4.157 upstream stable release

2021-11-24 Thread Stefan Bader
** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  Focal update: v5.4.157 upstream stable release

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

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.157 upstream stable release
     from git://git.kernel.org/

  ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned
  ARM: 9134/1: remove duplicate memcpy() definition
  ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype
  ARM: 9141/1: only warn about XIP address when not compile testing
  ipv6: use siphash in rt6_exception_hash()
  ipv4: use siphash instead of Jenkins in fnhe_hashfun()
  usbnet: sanity check for maxpacket
  usbnet: fix error return code in usbnet_probe()
  Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode"
  ata: sata_mv: Fix the error handling of mv_chip_id()
  nfc: port100: fix using -ERRNO as command type mask
  net/tls: Fix flipped sign in tls_err_abort() calls
  mmc: vub300: fix control-message timeouts
  mmc: cqhci: clear HALT state after CQE enable
  mmc: dw_mmc: exynos: fix the finding clock sample value
  mmc: sdhci: Map more voltage level to SDHCI_POWER_330
  mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning 
circuit
  cfg80211: scan: fix RCU in cfg80211_add_nontrans_list()
  net: lan78xx: fix division by zero in send path
  tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function
  IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields
  IB/hfi1: Fix abba locking issue with sc_disable()
  nvmet-tcp: fix data digest pointer calculation
  nvme-tcp: fix data digest pointer calculation
  RDMA/mlx5: Set user priority for DCT
  arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node
  regmap: Fix possible double-free in regcache_rbtree_exit()
  net: batman-adv: fix error handling
  net: Prevent infinite while loop in skb_tx_hash()
  RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string
  nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST
  net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume 
fails
  net: ethernet: microchip: lan743x: Fix dma allocation failure by using 
dma_set_mask_and_coherent
  net: nxp: lpc_eth.c: avoid hang when bringing interface down
  net/tls: Fix flipped sign in async_wait.err assignment
  phy: phy_ethtool_ksettings_get: Lock the phy for consistency
  phy: phy_start_aneg: Add an unlocked version
  sctp: use init_tag from inithdr for ABORT chunk
  sctp: fix the processing for INIT_ACK chunk
  sctp: fix the processing for COOKIE_ECHO chunk
  sctp: add vtag check in sctp_sf_violation
  sctp: add vtag check in sctp_sf_do_8_5_1_E_sa
  sctp: add vtag check in sctp_sf_ootb
  net: use netif_is_bridge_port() to check for IFF_BRIDGE_PORT
  cfg80211: correct bridge/4addr mode check
  KVM: s390: clear kicked_mask before sleeping again
  KVM: s390: preserve deliverable_mask in __airqs_kick_single_vcpu
  perf script: Check session->header.env.arch before using it
  Linux 5.4.157
  UBUNTU: upstream stable to v5.4.157

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


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


[Kernel-packages] [Bug 1951880] Re: Impish update: upstream stable patchset 2021-11-22

2021-11-24 Thread Stefan Bader
Skipped "virtio: write back F_VERSION_1 before validate" when applying
since that already had been applied for bug #1950144.

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

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

Title:
  Impish update: upstream stable patchset 2021-11-22

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Impish:
  Fix Committed

Bug description:
  SRU Justification

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

     upstream stable patchset 2021-11-22

  Ported from the following upstream stable releases:
  v5.10.74, v5.14.13
  v5.10.75, v5.14.14
  v5.10.76, v5.14.15

     from git://git.kernel.org/

  ext4: check and update i_disksize properly
  ext4: correct the error path of ext4_write_inline_data_end()
  ASoC: Intel: sof_sdw: tag SoundWire BEs as non-atomic
  HID: apple: Fix logical maximum and usage maximum of Magic Keyboard JIS
  netfilter: ip6_tables: zero-initialize fragment offset
  HID: wacom: Add new Intuos BT (CTL-4100WL/CTL-6100WL) device IDs
  ASoC: SOF: loader: release_firmware() on load failure to avoid batching
  netfilter: nf_nat_masquerade: make async masq_inet6_event handling generic
  netfilter: nf_nat_masquerade: defer conntrack walk to work queue
  mac80211: Drop frames from invalid MAC address in ad-hoc mode
  m68k: Handle arrivals of multiple signals correctly
  hwmon: (ltc2947) Properly handle errors when looking for the external clock
  net: prevent user from passing illegal stab size
  mac80211: check return value of rhashtable_init
  vboxfs: fix broken legacy mount signature checking
  net: sun: SUNVNET_COMMON should depend on INET
  drm/amdgpu: fix gart.bo pin_count leak
  scsi: ses: Fix unsigned comparison with less than zero
  scsi: virtio_scsi: Fix spelling mistake "Unsupport" -> "Unsupported"
  perf/core: fix userpage->time_enabled of inactive events
  sched: Always inline is_percpu_thread()
  hwmon: (pmbus/ibm-cffps) max_power_out swap changes
  ALSA: usb-audio: Unify mixer resume and reset_resume procedure
  KVM: arm64: nvhe: Fix missing FORCE for hyp-reloc.S build rule
  pinctrl: qcom: sc7280: Add PM suspend callbacks
  net: bgmac-platform: handle mac-address deferral
  scsi: qla2xxx: Fix excessive messages during device logout
  io_uring: kill fasync
  UBUNTU: upstream stable to v5.10.74, v5.14.13
  ALSA: usb-audio: Add quirk for VF0770
  ALSA: pcm: Workaround for a wrong offset in SYNC_PTR compat ioctl
  ALSA: seq: Fix a potential UAF by wrong private_free call order
  ALSA: hda/realtek: Enable 4-speaker output for Dell Precision 5560 laptop
  ALSA: hda - Enable headphone mic on Dell Latitude laptops with ALC3254
  ALSA: hda/realtek: Complete partial device name to avoid ambiguity
  ALSA: hda/realtek: Add quirk for Clevo X170KM-G
  ALSA: hda/realtek - ALC236 headset MIC recording issue
  ALSA: hda/realtek: Add quirk for TongFang PHxTxX1
  ALSA: hda/realtek: Fix the mic type detection issue for ASUS G551JW
  nds32/ftrace: Fix Error: invalid operands (*UND* and *UND* sections) for `^'
  s390: fix strrchr() implementation
  clk: socfpga: agilex: fix duplicate s2f_user0_clk
  csky: don't let sigreturn play with priveleged bits of status register
  csky: Fixup regs.sr broken in ptrace
  arm64/hugetlb: fix CMA gigantic page order for non-4K PAGE_SIZE
  drm/msm: Avoid potential overflow in timeout_to_jiffies()
  btrfs: unlock newly allocated extent buffer after error
  btrfs: deal with errors when replaying dir entry during log replay
  btrfs: deal with errors when adding inode reference during log replay
  btrfs: check for error when looking up inode during dir entry replay
  btrfs: update refs for any root except tree log roots
  btrfs: fix abort logic in btrfs_replace_file_extents
  x86/resctrl: Free the ctrlval arrays when domain_setup_mon_state() fails
  mei: me: add Ice Lake-N device id.
  USB: xhci: dbc: fix tty registration race
  xhci: guard accesses to ep_state in xhci_endpoint_reset()
  xhci: Fix command ring pointer corruption while aborting a command
  xhci: Enable trust tx length quirk for Fresco FL11 USB controller
  cb710: avoid NULL pointer subtraction
  efi/cper: use stack buffer for error record decoding
  efi: Change down_interruptible() in virt_efi_reset_system() to down_trylock()
  usb: musb: dsps: Fix the probe error path
  Input: xpad - add support for another USB 

[Kernel-packages] [Bug 1952077] Re: System time doesn't sync with RTC time on boot

2021-11-24 Thread Jesse Sung
** Description changed:

  == Impact ==
- Although we have CONFIG_RTC_HCTOSYS enabled and set CONFIG_RTC_HCTOSYS_DEVICE 
to "rtc0", system time would only be set if the RTC driver is built-in. This 
may not be an issue on most amd64 systems because CONFIG_RTC_DRV_CMOS is y for 
amd64, however it is an issue for other architectures since there may not be a 
proper RTC driver enabled as built-in. Also make every RTC driver that may be 
used as built-in is not a good option.
+ Although we have CONFIG_RTC_HCTOSYS enabled and set CONFIG_RTC_HCTOSYS_DEVICE 
to "rtc0", system time would only be set if the RTC driver is built-in. This 
may not be an issue on most amd64 systems because CONFIG_RTC_DRV_CMOS is y for 
amd64, however it is an issue for other architectures since there may not be a 
proper RTC driver enabled as built-in. Also making every RTC driver that may be 
used as built-in is not a good option.
  
  == Fix ==
  The commit is in mainline since v5.7:
  
  commit f9b2a4d6a5f18e0aaf715206a056565c56889d9f
  Author: Steve Muckle 
  Date:   Wed Nov 6 11:46:25 2019 -0800
  
- rtc: class: support hctosys from modular RTC drivers
- 
- Due to distribution constraints it may not be possible to statically
- compile the required RTC driver into the kernel.
- 
- Expand RTC_HCTOSYS support to cover all RTC devices (statically compiled
- or not) by checking at the end of RTC device registration whether the
- time should be synced.
- 
- Signed-off-by: Steve Muckle 
- Link: https://lore.kernel.org/r/20191106194625.116692-1-smuc...@google.com
- Signed-off-by: Alexandre Belloni 
+ rtc: class: support hctosys from modular RTC drivers
+ 
+ Due to distribution constraints it may not be possible to statically
+ compile the required RTC driver into the kernel.
+ 
+ Expand RTC_HCTOSYS support to cover all RTC devices (statically compiled
+ or not) by checking at the end of RTC device registration whether the
+ time should be synced.
+ 
+ Signed-off-by: Steve Muckle 
+ Link: https://lore.kernel.org/r/20191106194625.116692-1-smuc...@google.com
+ Signed-off-by: Alexandre Belloni 
  
  == Risk of Regression ==
  It's a clean cherry-pick for v5.4 and looks straight forward so risk should 
be low.

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

Title:
  System time doesn't sync with RTC time on boot

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

Bug description:
  == Impact ==
  Although we have CONFIG_RTC_HCTOSYS enabled and set CONFIG_RTC_HCTOSYS_DEVICE 
to "rtc0", system time would only be set if the RTC driver is built-in. This 
may not be an issue on most amd64 systems because CONFIG_RTC_DRV_CMOS is y for 
amd64, however it is an issue for other architectures since there may not be a 
proper RTC driver enabled as built-in. Also making every RTC driver that may be 
used as built-in is not a good option.

  == Fix ==
  The commit is in mainline since v5.7:

  commit f9b2a4d6a5f18e0aaf715206a056565c56889d9f
  Author: Steve Muckle 
  Date:   Wed Nov 6 11:46:25 2019 -0800

  rtc: class: support hctosys from modular RTC drivers

  Due to distribution constraints it may not be possible to statically
  compile the required RTC driver into the kernel.

  Expand RTC_HCTOSYS support to cover all RTC devices (statically compiled
  or not) by checking at the end of RTC device registration whether the
  time should be synced.

  Signed-off-by: Steve Muckle 
  Link: https://lore.kernel.org/r/20191106194625.116692-1-smuc...@google.com
  Signed-off-by: Alexandre Belloni 

  == Risk of Regression ==
  It's a clean cherry-pick for v5.4 and looks straight forward so risk should 
be low.

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


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


[Kernel-packages] [Bug 1952077] Re: System time doesn't sync with RTC time on boot

2021-11-24 Thread Jesse Sung
** Changed in: linux (Ubuntu)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Jesse Sung (wenchien)

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

Title:
  System time doesn't sync with RTC time on boot

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

Bug description:
  == Impact ==
  Although we have CONFIG_RTC_HCTOSYS enabled and set CONFIG_RTC_HCTOSYS_DEVICE 
to "rtc0", system time would only be set if the RTC driver is built-in. This 
may not be an issue on most amd64 systems because CONFIG_RTC_DRV_CMOS is y for 
amd64, however it is an issue for other architectures since there may not be a 
proper RTC driver enabled as built-in. Also make every RTC driver that may be 
used as built-in is not a good option.

  == Fix ==
  The commit is in mainline since v5.7:

  commit f9b2a4d6a5f18e0aaf715206a056565c56889d9f
  Author: Steve Muckle 
  Date:   Wed Nov 6 11:46:25 2019 -0800

  rtc: class: support hctosys from modular RTC drivers
  
  Due to distribution constraints it may not be possible to statically
  compile the required RTC driver into the kernel.
  
  Expand RTC_HCTOSYS support to cover all RTC devices (statically compiled
  or not) by checking at the end of RTC device registration whether the
  time should be synced.
  
  Signed-off-by: Steve Muckle 
  Link: https://lore.kernel.org/r/20191106194625.116692-1-smuc...@google.com
  Signed-off-by: Alexandre Belloni 

  == Risk of Regression ==
  It's a clean cherry-pick for v5.4 and looks straight forward so risk should 
be low.

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


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


[Kernel-packages] [Bug 1952041] Re: Fix i915 TypeC disconnect problems for Intel ADL-P

2021-11-24 Thread Chris Chiu
** Also affects: linux-hwe (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  Fix i915 TypeC disconnect problems for Intel ADL-P

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  New
Status in linux source package in Focal:
  Incomplete
Status in linux-hwe source package in Focal:
  New
Status in linux-oem-5.14 source package in Focal:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]
  When the ADL-P system connects the external display via TypeC port, it will 
hang after unplugging the TypeC connector. The system will never come back 
until reboot.

  [Fix]
  Intel has released a patch set to fix the TypeC PHY connect/disconnect logic. 
The shift for ownership of PHY and power domain will be handled correctly for 
ADL-P.

  [Test]
  The ADL-P system will no longer freeze and the ownership will shift correctly 
after disconnecting the external display connects via TypeC port.

  [Where problem could occur]
  It's kind of a big refactor for the i915 TypeC PHY handling logic. Don't know 
if there's any problems on older platforms. Targeting only on Unstable and 
latest OEM kernel for lower risk.


  == Original Bug Description ==
  [Summary]
  The system will hang on after unplug DA310 with external monitor (on-demand)
  Note:
  1. Build-in HDMI port cannot duplicate.
  2. VGA/HDMI/DP on DA310 to system all can duplicate.
  3. Unplug VGA/DP/HDMI from DA310, then unplug DA310 from the system cannot 
duplicate.

  [Steps to reproduce]
  1. Install dell-bto-focal-fossa-pypar-adl-X160-20210923-2.iso
  2. Plug DA310 to USB-C port
  3. Plug DP/VGA/HDMI to DA310
  4. Unplug DA310 > The system hangs on with black screen

  [Expected result]
  The system works well after unplug USB-C with external monitor

  [Actual result]
  The system hangs on blackscreen after unplug DA310 with external monitor

  [Failure rate]
  3/3

  [Additional information]
  SKU: SIF-MLK-DVT1-C1, SIF-MLK-DVT1-C5, SIF-MLK-DVT1-C6
  Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-pypar-adl+X160
  system-manufacturer: Dell Inc.
  system-product-name: Dell G15 5520
  bios-version: 0.2.9
  CPU: Genuine Intel(R)  (12x)
  GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:46a3]
  :01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device 
[10de:25e2] (rev a1)
  kernel-version: 5.14.0-9002-oem

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


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


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

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

apport-collect 1952077

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

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

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

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

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

Title:
  System time doesn't sync with RTC time on boot

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

Bug description:
  == Impact ==
  Although we have CONFIG_RTC_HCTOSYS enabled and set CONFIG_RTC_HCTOSYS_DEVICE 
to "rtc0", system time would only be set if the RTC driver is built-in. This 
may not be an issue on most amd64 systems because CONFIG_RTC_DRV_CMOS is y for 
amd64, however it is an issue for other architectures since there may not be a 
proper RTC driver enabled as built-in. Also make every RTC driver that may be 
used as built-in is not a good option.

  == Fix ==
  The commit is in mainline since v5.7:

  commit f9b2a4d6a5f18e0aaf715206a056565c56889d9f
  Author: Steve Muckle 
  Date:   Wed Nov 6 11:46:25 2019 -0800

  rtc: class: support hctosys from modular RTC drivers
  
  Due to distribution constraints it may not be possible to statically
  compile the required RTC driver into the kernel.
  
  Expand RTC_HCTOSYS support to cover all RTC devices (statically compiled
  or not) by checking at the end of RTC device registration whether the
  time should be synced.
  
  Signed-off-by: Steve Muckle 
  Link: https://lore.kernel.org/r/20191106194625.116692-1-smuc...@google.com
  Signed-off-by: Alexandre Belloni 

  == Risk of Regression ==
  It's a clean cherry-pick for v5.4 and looks straight forward so risk should 
be low.

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


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


[Kernel-packages] [Bug 1952077] [NEW] System time doesn't sync with RTC time on boot

2021-11-24 Thread Jesse Sung
Public bug reported:

== Impact ==
Although we have CONFIG_RTC_HCTOSYS enabled and set CONFIG_RTC_HCTOSYS_DEVICE 
to "rtc0", system time would only be set if the RTC driver is built-in. This 
may not be an issue on most amd64 systems because CONFIG_RTC_DRV_CMOS is y for 
amd64, however it is an issue for other architectures since there may not be a 
proper RTC driver enabled as built-in. Also make every RTC driver that may be 
used as built-in is not a good option.

== Fix ==
The commit is in mainline since v5.7:

commit f9b2a4d6a5f18e0aaf715206a056565c56889d9f
Author: Steve Muckle 
Date:   Wed Nov 6 11:46:25 2019 -0800

rtc: class: support hctosys from modular RTC drivers

Due to distribution constraints it may not be possible to statically
compile the required RTC driver into the kernel.

Expand RTC_HCTOSYS support to cover all RTC devices (statically compiled
or not) by checking at the end of RTC device registration whether the
time should be synced.

Signed-off-by: Steve Muckle 
Link: https://lore.kernel.org/r/20191106194625.116692-1-smuc...@google.com
Signed-off-by: Alexandre Belloni 

== Risk of Regression ==
It's a clean cherry-pick for v5.4 and looks straight forward so risk should be 
low.

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

** Affects: linux (Ubuntu Focal)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: In Progress

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

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Jesse Sung (wenchien)

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

Title:
  System time doesn't sync with RTC time on boot

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

Bug description:
  == Impact ==
  Although we have CONFIG_RTC_HCTOSYS enabled and set CONFIG_RTC_HCTOSYS_DEVICE 
to "rtc0", system time would only be set if the RTC driver is built-in. This 
may not be an issue on most amd64 systems because CONFIG_RTC_DRV_CMOS is y for 
amd64, however it is an issue for other architectures since there may not be a 
proper RTC driver enabled as built-in. Also make every RTC driver that may be 
used as built-in is not a good option.

  == Fix ==
  The commit is in mainline since v5.7:

  commit f9b2a4d6a5f18e0aaf715206a056565c56889d9f
  Author: Steve Muckle 
  Date:   Wed Nov 6 11:46:25 2019 -0800

  rtc: class: support hctosys from modular RTC drivers
  
  Due to distribution constraints it may not be possible to statically
  compile the required RTC driver into the kernel.
  
  Expand RTC_HCTOSYS support to cover all RTC devices (statically compiled
  or not) by checking at the end of RTC device registration whether the
  time should be synced.
  
  Signed-off-by: Steve Muckle 
  Link: https://lore.kernel.org/r/20191106194625.116692-1-smuc...@google.com
  Signed-off-by: Alexandre Belloni 

  == Risk of Regression ==
  It's a clean cherry-pick for v5.4 and looks straight forward so risk should 
be low.

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


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


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

2021-11-24 Thread Luiz Carlos Maciel Franco
/etc/default/grub

>> i915.force_probe=pci:v8086d4C9Asv*sd*bc03sc*i* (this is my i915 
>> driver module alias)
but, you can get PCI Device ID, with lspci -nnk command
>> i915.force_probe=PCI_Device_ID (no BusID)

update-grub

/etc/environment
>> export LIBGL_DRI2_DISABLE=true
>> export LIBGL_DRI3_DISABLE=true

reboot system

ps
My bios set mshybrid (optimus) and system is nvidia prime on-demand (offloading)
Intel iGPU and nvidia dGPU
Working external monitor, HDMI and typec (displayport)

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

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

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

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

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

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

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


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


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

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

apport-collect 1952061

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

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

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

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

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

Title:
  Bluetooth is not working. It is showing to connect with a Dongle.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I changed from windows to Ubuntu 20.04 version.

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


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


[Kernel-packages] [Bug 1952061] [NEW] Bluetooth is not working. It is showing to connect with a Dongle.

2021-11-24 Thread Anjan Kumar
Public bug reported:

I changed from windows to Ubuntu 20.04 version.

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

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

Title:
  Bluetooth is not working. It is showing to connect with a Dongle.

Status in linux package in Ubuntu:
  New

Bug description:
  I changed from windows to Ubuntu 20.04 version.

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


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