date:20210730

All autopkgtests for the newly accepted linux-meta-oracle-5.4 
(5.4.0.1053.57~18.04.33) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

kpatch/0.5.0-0ubuntu1.1 (amd64)
lxc/3.0.3-0ubuntu1~18.04.1 (amd64, arm64)
virtualbox/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64)
virtualbox-hwe/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-meta-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1834771] Re: No HDMI-audio after kernel 4.15.-0.50

2021-07-30 Thread Gerry

Thanks Uriel Tunn, but that fix didn't work for me.

So, I followed your advice and tried an upgrande to another distro.
I tried... 
-> Linux Mint 20.2 Uma (Kernel 5.11)
-> MX Linux 19.4.1
-> Manjaro xfce 21.0.7-210614 (Kernel 5.10)
-> Endeavour-2021.04.17 (Kernel 5.11)
-> Pop_OS_21.04_amd64 
-> Fedora_Workstation_Live_x86_64_34-1.2
-> Ubuntu 21.04 desktop amd64 (Kernel 5.11)
-> Ubuntu 18.04 desktop amd64 (Kernel 5.4.0-42-generic)

None of the above work with a DVI/HDMI or Display Port/HDMI adapter.

HOWEVER, seeing as i had just installed Ubuntu 18.04, I started to
install some kernels on that build

Sure as hell
4.15.0-041500-generic - work perfectly, DVI/HDMI or Display Port/HDMI adapter 
listed as an options in Sound Settings
4.18.0-041800-generic - work perfectly, DVI/HDMI or Display Port/HDMI adapter 
listed as an options in Sound Settings
4.18.10-041810-generic - work perfectly, DVI/HDMI or Display Port/HDMI adapter 
listed as an options in Sound Settings
4.18.16-041816-generic - work perfectly, DVI/HDMI or Display Port/HDMI adapter 
listed as an options in Sound Settings
4.18.19-041819-generic - work perfectly, DVI/HDMI or Display Port/HDMI adapter 
listed as an options in Sound Settings

THEN
4.18.20-041820-generic - would not even boot with Ubuntu - had to use the 
recovery kernel option, and when i got into the main screen, i checked the 
sound settings, and sure as hell neither DVI/HMDI nor Display Port/HDMI were 
listed anymore!

Next I checked 
4.19.0-041900-generic - while this didn't give any problems booting, when i got 
into the main screen, i checked the sound settings, neither DVI/HMDI nor 
Display Port/HDMI were listed anymore.

So, yes, whatever happened in 4.18.20-041820 has broke the sound for my
HDMI adapters and never been fixed since.

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

Title:
  No HDMI-audio after kernel 4.15.-0.50

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've got no HDMI-audio. Latest kernel with working HDMI-audio is 4.15.-0.50. 
In pavucontrol HDMI-audio shows unplugged. And also internal audio shows 
unplugged, but it still works. I'm on linux mint 18.3.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jouni  1859 F pulseaudio
   /dev/snd/controlC1:  jouni  1859 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=9e8d7bf3-dc5f-4c72-b875-6dbe81a36c36
  InstallationDate: Installed on 2017-01-28 (883 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic 
root=UUID=f167a2b0-3b30-4a5a-907f-6b97c95b7a91 ro quiet iommu=soft splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-54-generic N/A
   linux-backports-modules-4.15.0-54-generic  N/A
   linux-firmware 1.157.21
  RfKill:
   
  Tags:  sylvia
  Uname: Linux 4.15.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 02/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FC
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 1936785] Re: Add support for AMD BCL DID

2021-07-30 Thread AceLan Kao

** Tags removed: verification-needed-focal
** Tags added: verification-done-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/1936785

Title:
  Add support for AMD BCL DID

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

Bug description:
  [Impact]
  AMD BCL APU shares same code as CZN/RN, but has another DID to be added to 
kernel.

  [Fix]
  Below commit adds the ID.
  https://lists.freedesktop.org/archives/amd-gfx/2021-July/066502.html

  [Test]
  We didn't receive h/w yet, just told by AMD that the new ID is required.

  [Where problems could occur]
  Adding a new ID should be pretty safe.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oracle/5.11.0.1015.16)

All autopkgtests for the newly accepted linux-meta-oracle (5.11.0.1015.16) for 
hirsute have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/247.3-3ubuntu3.4 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/hirsute/update_excuses.html#linux-meta-oracle

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1925421] Autopkgtest regression report (linux-meta-oracle/5.11.0.1015.16)

All autopkgtests for the newly accepted linux-meta-oracle (5.11.0.1015.16) for 
hirsute have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/247.3-3ubuntu3.4 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/hirsute/update_excuses.html#linux-meta-oracle

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  arm64 support

Status in linux-oracle package in Ubuntu:
  Fix Released
Status in linux-oracle-5.4 package in Ubuntu:
  New
Status in linux-oracle-5.8 package in Ubuntu:
  New
Status in linux-oracle source package in Bionic:
  Invalid
Status in linux-oracle-5.4 source package in Bionic:
  Fix Released
Status in linux-oracle-5.8 source package in Bionic:
  New
Status in linux-oracle source package in Focal:
  Fix Released
Status in linux-oracle-5.4 source package in Focal:
  Invalid
Status in linux-oracle-5.8 source package in Focal:
  Fix Released
Status in linux-oracle source package in Groovy:
  Fix Released
Status in linux-oracle-5.4 source package in Groovy:
  Invalid
Status in linux-oracle-5.8 source package in Groovy:
  Fix Committed

Bug description:
  See
  https://canonical.lightning.force.com/lightning/r/Case/5003z2BzFG4AAN/view
  for more info

  
  [Impact]
  No support for arm64 currently

  
  [Fix]
  Add arm64 support, including hardware support patches

  [Test]
  Confirm that it boots on desired arm64 hardware, as well as VMs

  [Regression Potential]
  This was never working on arm64 so there should be no risk of regression.
  The requested changes included some refactorings of early memory 
initialization code (all arches) so this presents a small risk. The changes 
were tested on arm64 as well amd64.

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


-- 
Mailing list: https://launchpad.net/~kernel-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

Thanks for reporting this. The patch does not yet land in mainline
kernel (5.14rc3), and the patch was submitted for review on July 29
(https://patchwork.kernel.org/project/linux-
input/patch/20210729010940.5752-1-phoe...@emc.com.tw/)

Once the patch lands in mainline it can be backport to Ubuntu 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/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 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count

2021-07-30 Thread Andreas Schildbach

I've got this issue on
```
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename:   focal
# uname -a
Linux ultima 5.4.0-80-generic #90-Ubuntu SMP Fri Jul 9 22:49:44 UTC 2021 x86_64 
x86_64 x86_64 GNU/Linux
```

The message is

```
kernel:[864004.039343] unregister_netdevice: waiting for lo to become free. 
Usage count = 1
```

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

Title:
  unregister_netdevice: waiting for lo to become free. Usage count

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Won't Fix
Status in linux-lts-xenial package in Ubuntu:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  Won't Fix
Status in linux source package in Vivid:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

  Users of kernels that utilize NFS may see the following messages when
  shutting down and starting containers:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  Setup multiple containers in parallel to mount and NFS share, create
  some traffic and shutdown. Eventually you will see the kernel message.

  Dave's script here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403152/comments/24

  [Fix]
  commit de84d89030fa4efa44c02c96c8b4a8176042c4ff upstream

  --

  I currently running trusty latest patches and i get on these hardware
  and software:

  Ubuntu 3.13.0-43.72-generic 3.13.11.11

  processor : 7
  vendor_id : GenuineIntel
  cpu family: 6
  model : 77
  model name: Intel(R) Atom(TM) CPU  C2758  @ 2.40GHz
  stepping  : 8
  microcode : 0x11d
  cpu MHz   : 2400.000
  cache size: 1024 KB
  physical id   : 0
  siblings  : 8
  core id   : 7
  cpu cores : 8
  apicid: 14
  initial apicid: 14
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 11
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm 
sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch 
arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
  bogomips  : 4799.48
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 36 bits physical, 48 bits virtual
  power management:

  somehow reproducable the subjected error, and lxc is working still but
  not more managable until a reboot.

  managable means every command hangs.

  I saw there are alot of bugs but they seams to relate to older version
  and are closed, so i decided to file a new one?

  I run alot of machine with trusty an lxc containers but only these kind of 
machines produces these errors, all
  other don't show these odd behavior.

  thx in advance

  meno

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


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

[Kernel-packages] [Bug 1938588] Re: Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to errata

2021-07-30 Thread Brian Murray

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

** Tags added: rls-ii-incoming

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

Title:
  Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to
  errata

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  We have several factory-fresh Mitac industrial motherboards
  (https://www.mitacmct.com/IndustrialMotherboard_PH13FEI_PH13FEI) that
  we are unable to install Ubuntu Server 18.04.5 on.  When we boot from
  the installation media we get the following error and the installation
  hangs (see attached screenshot, I've transcribed the error below too)

  ```
  [0.00] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update 
microcode to version: 0x52 (or later)
  [0.157025] ACPI Exception: AE_BAD_PARAMETER, Could not install PciConfig 
handler for Root Bridge PCI0 (20170831/evrgnini-241)
  ```

  Googling the microcode bug, the normal advice appears to be "boot into
  an older, functioning kernel, update the `intel-microcode` package,
  and then reboot."  But in this situation there is no older kernel to
  boot into; there is no OS installed _at all_ on these boards yet.  I'm
  booting from a USB drive loaded with the latest version of Ubuntu
  Server 18.04.

  The only work-around I've found that works so far is to install Ubuntu
  Desktop 18.04, which can boot successfully on these boards, perform
  the minimal desktop installation, then use the desktop install to
  update the `intel-microcode` package, reboot, and then finally install
  Ubuntu Server.  This is obviously not convenient needing to install a
  complete desktop OS just so I can update the microcode, and then
  immediately wiping it to install what I wanted in the first place.

  I have not tried Ubuntu 20.x or 21.x; I need to use Ubuntu 18.04
  because these motherboards are being installed into robots that will
  be running ROS Melodic (ROS Noetic runs on 20.04, but these robots
  don't have Noetic support yet).

  I have tried the following to modify the Ubuntu Server ISO, without
  success:

  1- Adding the microcode to initrd
  ---

  I unpacked the contents of the Ubuntu Server ISO, decompressed
  install/initrd.gz, and used the bash script here
  https://www.kernel.org/doc/html/latest/x86/microcode.html to add the
  intel-microcode firmware to the image.  Then I recompressed initrd.gz,
  and rebuild the ISO using xorisso.  This did not have any effect:
  Ubuntu Server still encountered the same error when trying to install.

  
  2- Using initrd from Ubuntu Desktop 18.04.5
  --

  I downloaded & unpacked Ubuntu Desktop 18.04.5 and replaced Ubuntu
  Server's install/initrd.gz with Ubuntu Desktop's casper/initrd
  (updating txt.cfg and grub.cfg to load the uncompressed initrd instead
  of the .gz that Ubuntu Server normally uses).  Then I rebuilt the
  Ubuntu Server with xorisso again.

  The resulted in the system booting, but immediately dropping into an
  initramfs busybox shell, saying boot files were missing.  I assume
  this is because Ubuntu Server uses the `boot=casper` flag in order to
  boot into the live desktop session.

  
  At this point I'm running out of ideas for how to be able to make Ubuntu 
Server's installation media work with these boards.  Ubuntu Desktop has no 
problem booting on them, so it's obviously something specific to the Ubuntu 
Server image, but I'm not sure exactly what or how to fix it.

  If you need any additional information/logs/etc... please let me know
  and I'll be happy to provide them.

  Thanks!

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


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

[Kernel-packages] [Bug 1935034] Re: Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04

2021-07-30 Thread Michael Reed

Also typically when there is a driver update to a specific driver
version there is a patch updating the version.  There is an example for
37.101.00.00 in this patch set  "scsi: mpt3sas: Update driver version to
37.101.00.00"  but I do not see one for 38.100.00.00, nor do I see it in
linus' tree when I try to pull in the patches.  Can you verify that all
the patches needed are included in this listing?

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

Title:
  Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  New
Status in linux source package in Hirsute:
  New
Status in linux source package in Impish:
  Confirmed

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

  I could see both Ubuntu 21.10 and 20.04 HWE has mpt3sas driver
  v36.100.00.00, following are the commit ID's to update to 38.100.00.00

  8b3c803529 scsi: mpt3sas: Signedness bug in _base_get_diag_triggers()
  39718fe7ad scsi: mpt3sas: Fix spelling mistake in Kconfig "compatiblity" -> 
"compatibility"
  bfb3f00c06 scsi: mpt3sas: Simplify bool comparison
  d309ae0732 scsi: mpt3sas: Fix ReplyPostFree pool allocation
  664f0dce20 scsi: mpt3sas: Add support for shared host tagset for CPU hotplug
  688c1a0a13 scsi: mpt3sas: Additional diagnostic buffer query interface
  446b5f3d3f scsi: mpt3sas: Update driver version to 37.100.00.00

  8278807abd scsi: core: Add scsi_device_busy() wrapper
  020b0f0a31 scsi: core: Replace sdev->device_busy with sbitmap

  e015e0ded1 scsi: mpt3sas: Fix misspelling of _base_put_smid_default_atomic()
  2111ba8781 scsi: mpt3sas: Move a little data from the stack onto the heap
  cf9e575e62 scsi: mpt3sas: Fix a bunch of potential naming doc-rot
  54cb88dc30 scsi: mpt3sas: Fix a couple of misdocumented functions/params
  782a1ab33f scsi: mpt3sas: Fix some kernel-doc misnaming issues
  a50bd64616 scsi: mpt3sas: Do not use GFP_KERNEL in atomic context
  a1c4d77413 scsi: mpt3sas: Replace unnecessary dynamic allocation with a 
static one
  d6adc251dd scsi: mpt3sas: Force PCIe scatterlist allocations to be within 
same 4 GB region
  7dd847dae1 scsi: mpt3sas: Force chain buffer allocations to be within same 4 
GB region
  970ac2bb70 scsi: mpt3sas: Force sense buffer allocations to be within same 4 
GB region
  58501fd937 scsi: mpt3sas: Force reply buffer allocations to be within same 4 
GB region
  2e4e858732 scsi: mpt3sas: Force reply post buffer allocations to be within 
same 4 GB region
  c569de899b scsi: mpt3sas: Force reply post array allocations to be within 
same 4 GB region
  37067b9793 scsi: mpt3sas: Update driver version to 37.101.00.00

  a8d548b0b3 scsi: mpt3sas: Fix a few kernel-doc issues
  3401ecf7fc scsi: mpt3sas: Fix error return code of mpt3sas_base_attach()

   
  206a3afa94 scsi: mpt3sas: Fix a typo
  4c51f95696 scsi: mpt3sas: Only one vSES is present even when IOC has multi 
vSES
  c0629d70ca scsi: mpt3sas: Fix endianness for ActiveCablePowerRequirement
  3c8604691d scsi: mpt3sas: Block PCI config access from userspace during reset
  16660db3fc scsi: mpt3sas: Fix out-of-bounds warnings in _ctl_addnl_diag_query
  3ad0b1da0d scsi: mpt3sas: Fix two kernel-doc headers
  2910a4a9e9 scsi: mpt3sas: Documentation cleanup
  e2fac6c44a scsi: mpt3sas: Fix deadlock while cancelling the running firmware 
event
  19a622c39a scsi: mpt3sas: Handle firmware faults during first half of IOC init
  a0815c45c8 scsi: mpt3sas: Handle firmware faults during second half of IOC 
init

  f2b1e9c6f8 scsi: core: Introduce scsi_build_sense()

  84a84cc6af scsi: mpt3sas: Fix fall-through warnings for Clang
  cf750be8e6 scsi: mpt3sas: Fix Coverity reported issue
  d6c2ce435f scsi: mpt3sas: Fix error return value in _scsih_expander_add()

  
  Note:
  We have  already posted patch to update  driver version to 38.100.00.00
  Other patches are already available in upstream .

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


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

[Kernel-packages] [Bug 1938588] Re: Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to errata

2021-07-30 Thread Brian Murray

This is because the intel-microcode package is not included on the
server iso for Ubuntu 18.04 but it is for the desktop iso. This also
seems to be the case for Ubuntu 20.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/1938588

Title:
  Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to
  errata

Status in linux package in Ubuntu:
  New

Bug description:
  We have several factory-fresh Mitac industrial motherboards
  (https://www.mitacmct.com/IndustrialMotherboard_PH13FEI_PH13FEI) that
  we are unable to install Ubuntu Server 18.04.5 on.  When we boot from
  the installation media we get the following error and the installation
  hangs (see attached screenshot, I've transcribed the error below too)

  ```
  [0.00] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update 
microcode to version: 0x52 (or later)
  [0.157025] ACPI Exception: AE_BAD_PARAMETER, Could not install PciConfig 
handler for Root Bridge PCI0 (20170831/evrgnini-241)
  ```

  Googling the microcode bug, the normal advice appears to be "boot into
  an older, functioning kernel, update the `intel-microcode` package,
  and then reboot."  But in this situation there is no older kernel to
  boot into; there is no OS installed _at all_ on these boards yet.  I'm
  booting from a USB drive loaded with the latest version of Ubuntu
  Server 18.04.

  The only work-around I've found that works so far is to install Ubuntu
  Desktop 18.04, which can boot successfully on these boards, perform
  the minimal desktop installation, then use the desktop install to
  update the `intel-microcode` package, reboot, and then finally install
  Ubuntu Server.  This is obviously not convenient needing to install a
  complete desktop OS just so I can update the microcode, and then
  immediately wiping it to install what I wanted in the first place.

  I have not tried Ubuntu 20.x or 21.x; I need to use Ubuntu 18.04
  because these motherboards are being installed into robots that will
  be running ROS Melodic (ROS Noetic runs on 20.04, but these robots
  don't have Noetic support yet).

  I have tried the following to modify the Ubuntu Server ISO, without
  success:

  1- Adding the microcode to initrd
  ---

  I unpacked the contents of the Ubuntu Server ISO, decompressed
  install/initrd.gz, and used the bash script here
  https://www.kernel.org/doc/html/latest/x86/microcode.html to add the
  intel-microcode firmware to the image.  Then I recompressed initrd.gz,
  and rebuild the ISO using xorisso.  This did not have any effect:
  Ubuntu Server still encountered the same error when trying to install.

  
  2- Using initrd from Ubuntu Desktop 18.04.5
  --

  I downloaded & unpacked Ubuntu Desktop 18.04.5 and replaced Ubuntu
  Server's install/initrd.gz with Ubuntu Desktop's casper/initrd
  (updating txt.cfg and grub.cfg to load the uncompressed initrd instead
  of the .gz that Ubuntu Server normally uses).  Then I rebuilt the
  Ubuntu Server with xorisso again.

  The resulted in the system booting, but immediately dropping into an
  initramfs busybox shell, saying boot files were missing.  I assume
  this is because Ubuntu Server uses the `boot=casper` flag in order to
  boot into the live desktop session.

  
  At this point I'm running out of ideas for how to be able to make Ubuntu 
Server's installation media work with these boards.  Ubuntu Desktop has no 
problem booting on them, so it's obviously something specific to the Ubuntu 
Server image, but I'm not sure exactly what or how to fix it.

  If you need any additional information/logs/etc... please let me know
  and I'll be happy to provide them.

  Thanks!

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


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

[Kernel-packages] [Bug 1938588] Re: Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to errata

2021-07-30 Thread Chris Iverach-Brereton

If I boot off the ISO in a VM and use alt+Left I can get to a terminal.
`uname -a` reports:

```
Linux (none) 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 
x86_64 GNU/Linux
```

I couldn't find that specific kernel package with the search tool, so
please feel free to change the package as necessary to something more
specific than just "linux"

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

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

Title:
  Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to
  errata

Status in linux package in Ubuntu:
  New

Bug description:
  We have several factory-fresh Mitac industrial motherboards
  (https://www.mitacmct.com/IndustrialMotherboard_PH13FEI_PH13FEI) that
  we are unable to install Ubuntu Server 18.04.5 on.  When we boot from
  the installation media we get the following error and the installation
  hangs (see attached screenshot, I've transcribed the error below too)

  ```
  [0.00] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update 
microcode to version: 0x52 (or later)
  [0.157025] ACPI Exception: AE_BAD_PARAMETER, Could not install PciConfig 
handler for Root Bridge PCI0 (20170831/evrgnini-241)
  ```

  Googling the microcode bug, the normal advice appears to be "boot into
  an older, functioning kernel, update the `intel-microcode` package,
  and then reboot."  But in this situation there is no older kernel to
  boot into; there is no OS installed _at all_ on these boards yet.  I'm
  booting from a USB drive loaded with the latest version of Ubuntu
  Server 18.04.

  The only work-around I've found that works so far is to install Ubuntu
  Desktop 18.04, which can boot successfully on these boards, perform
  the minimal desktop installation, then use the desktop install to
  update the `intel-microcode` package, reboot, and then finally install
  Ubuntu Server.  This is obviously not convenient needing to install a
  complete desktop OS just so I can update the microcode, and then
  immediately wiping it to install what I wanted in the first place.

  I have not tried Ubuntu 20.x or 21.x; I need to use Ubuntu 18.04
  because these motherboards are being installed into robots that will
  be running ROS Melodic (ROS Noetic runs on 20.04, but these robots
  don't have Noetic support yet).

  I have tried the following to modify the Ubuntu Server ISO, without
  success:

  1- Adding the microcode to initrd
  ---

  I unpacked the contents of the Ubuntu Server ISO, decompressed
  install/initrd.gz, and used the bash script here
  https://www.kernel.org/doc/html/latest/x86/microcode.html to add the
  intel-microcode firmware to the image.  Then I recompressed initrd.gz,
  and rebuild the ISO using xorisso.  This did not have any effect:
  Ubuntu Server still encountered the same error when trying to install.

  
  2- Using initrd from Ubuntu Desktop 18.04.5
  --

  I downloaded & unpacked Ubuntu Desktop 18.04.5 and replaced Ubuntu
  Server's install/initrd.gz with Ubuntu Desktop's casper/initrd
  (updating txt.cfg and grub.cfg to load the uncompressed initrd instead
  of the .gz that Ubuntu Server normally uses).  Then I rebuilt the
  Ubuntu Server with xorisso again.

  The resulted in the system booting, but immediately dropping into an
  initramfs busybox shell, saying boot files were missing.  I assume
  this is because Ubuntu Server uses the `boot=casper` flag in order to
  boot into the live desktop session.

  
  At this point I'm running out of ideas for how to be able to make Ubuntu 
Server's installation media work with these boards.  Ubuntu Desktop has no 
problem booting on them, so it's obviously something specific to the Ubuntu 
Server image, but I'm not sure exactly what or how to fix it.

  If you need any additional information/logs/etc... please let me know
  and I'll be happy to provide them.

  Thanks!

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


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

[Kernel-packages] [Bug 1938588] [NEW] Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to errata

2021-07-30 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

We have several factory-fresh Mitac industrial motherboards
(https://www.mitacmct.com/IndustrialMotherboard_PH13FEI_PH13FEI) that we
are unable to install Ubuntu Server 18.04.5 on.  When we boot from the
installation media we get the following error and the installation hangs
(see attached screenshot, I've transcribed the error below too)

```
[0.00] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update 
microcode to version: 0x52 (or later)
[0.157025] ACPI Exception: AE_BAD_PARAMETER, Could not install PciConfig 
handler for Root Bridge PCI0 (20170831/evrgnini-241)
```

Googling the microcode bug, the normal advice appears to be "boot into
an older, functioning kernel, update the `intel-microcode` package, and
then reboot."  But in this situation there is no older kernel to boot
into; there is no OS installed _at all_ on these boards yet.  I'm
booting from a USB drive loaded with the latest version of Ubuntu Server
18.04.

The only work-around I've found that works so far is to install Ubuntu
Desktop 18.04, which can boot successfully on these boards, perform the
minimal desktop installation, then use the desktop install to update the
`intel-microcode` package, reboot, and then finally install Ubuntu
Server.  This is obviously not convenient needing to install a complete
desktop OS just so I can update the microcode, and then immediately
wiping it to install what I wanted in the first place.

I have not tried Ubuntu 20.x or 21.x; I need to use Ubuntu 18.04 because
these motherboards are being installed into robots that will be running
ROS Melodic (ROS Noetic runs on 20.04, but these robots don't have
Noetic support yet).

I have tried the following to modify the Ubuntu Server ISO, without
success:

1- Adding the microcode to initrd
---

I unpacked the contents of the Ubuntu Server ISO, decompressed
install/initrd.gz, and used the bash script here
https://www.kernel.org/doc/html/latest/x86/microcode.html to add the
intel-microcode firmware to the image.  Then I recompressed initrd.gz,
and rebuild the ISO using xorisso.  This did not have any effect: Ubuntu
Server still encountered the same error when trying to install.


2- Using initrd from Ubuntu Desktop 18.04.5
--

I downloaded & unpacked Ubuntu Desktop 18.04.5 and replaced Ubuntu
Server's install/initrd.gz with Ubuntu Desktop's casper/initrd (updating
txt.cfg and grub.cfg to load the uncompressed initrd instead of the .gz
that Ubuntu Server normally uses).  Then I rebuilt the Ubuntu Server
with xorisso again.

The resulted in the system booting, but immediately dropping into an
initramfs busybox shell, saying boot files were missing.  I assume this
is because Ubuntu Server uses the `boot=casper` flag in order to boot
into the live desktop session.


At this point I'm running out of ideas for how to be able to make Ubuntu 
Server's installation media work with these boards.  Ubuntu Desktop has no 
problem booting on them, so it's obviously something specific to the Ubuntu 
Server image, but I'm not sure exactly what or how to fix it.

If you need any additional information/logs/etc... please let me know
and I'll be happy to provide them.

Thanks!

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


** Tags: bot-comment intel-microcode kernel-bug ubuntu-server
-- 
Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to errata
https://bugs.launchpad.net/bugs/1938588
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1937897] Re: GPIO error logs in start and dmesg aftzer update of kernel

I don't have a system support this module but you can try to blacklist
it with

  $ echo "blacklist gpio-aaeon" | sudo tee -a
/etc/modprobe.d/blacklist.conf

** Summary changed:

- GPIO error logs in start and dmesg aftzer update of kernel
+ GPIO error logs in start and dmesg after update of kernel

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

Title:
  GPIO error logs in start and dmesg after update of kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After update from kernel 5.11.0-22 to 5.11.0-25 i see next logs error
  to gpio:

 5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with 
zero lines
  [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to 
register, -22
  [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22

  On pc:

  description: Desktop Computer
  product: System Product Name (SKU)
  vendor: ASUS
  version: System Version
  serial: System Serial Number
  width: 64 bits
  capabilities: smbios-3.3.0 dmi-3.3.0 smp vsyscall32
  configuration: boot=normal chassis=desktop family=To be filled by O.E.M. 
sku=SKU uuid=0ABCA172-BFA8-2AC5-FC37-3C7C3FD88FE4
*-core
 description: Motherboard
 product: TUF GAMING B550M-PLUS (WI-FI)
 vendor: ASUSTeK COMPUTER INC.
 physical id: 0
 version: Rev X.0x
 serial: 201176738701636
 slot: Default string
   *-firmware
description: BIOS
vendor: American Megatrends Inc.
physical id: 0
version: 2403
date: 06/16/2021
size: 64KiB
capacity: 16MiB
capabilities: pci apm upgrade shadowing cdboot bootselect 
socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen 
int9keyboard int14serial int17printer acpi usb biosbootspecification uefi
   *-memory

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


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

[Kernel-packages] [Bug 1937897] Re: GPIO error logs in start and dmesg aftzer update of kernel

gpio-aaeon was added into newer versions, ex.

$ git log Ubuntu-5.11.0-22.23..Ubuntu-5.11.0-25.27 -- 
./drivers/gpio/gpio-aaeon.c
commit 16c04b79bdc6e13a8f1c9b372b34c6f32f3806bb
Author: Kunyang_Fan 
Date:   Wed Jun 16 07:56:00 2021 +0200

UBUNTU: ODM: gpio: add driver for AAEON devices

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

This patch add support for the GPIO pins whose control are
transported to BIOS through ASUS WMI interface.

Signed-off-by: Kunyang_Fan 
Review-by: Kai-Heng Feng 
Review-by: Chia-Lin Kao (AceLan) 
Signed-off-by: Chia-Lin Kao (AceLan) 
Acked-by: Stefan Bader 
Acked-by: Kleber Sacilotto de Souza 
Signed-off-by: Stefan Bader 


Similarly, 

$ git log Ubuntu-5.8.0-59.66..Ubuntu-5.8.0-63.71 -- ./drivers/gpio/gpio-aaeon.c
commit 6811515eb04775991d42ee7f6aec5fbd6b69c5cb
Author: Kunyang_Fan 
Date:   Wed Jun 16 07:56:00 2021 +0200

UBUNTU: ODM: gpio: add driver for AAEON devices

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

This patch add support for the GPIO pins whose control are
transported to BIOS through ASUS WMI interface.

Signed-off-by: Kunyang_Fan 
Review-by: Kai-Heng Feng 
Review-by: Chia-Lin Kao (AceLan) 
Signed-off-by: Chia-Lin Kao (AceLan) 
Acked-by: Stefan Bader 
Acked-by: Kleber Sacilotto de Souza 
Signed-off-by: Stefan Bader 

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

Title:
  GPIO error logs in start and dmesg after update of kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After update from kernel 5.11.0-22 to 5.11.0-25 i see next logs error
  to gpio:

 5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with 
zero lines
  [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to 
register, -22
  [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22

  On pc:

  description: Desktop Computer
  product: System Product Name (SKU)
  vendor: ASUS
  version: System Version
  serial: System Serial Number
  width: 64 bits
  capabilities: smbios-3.3.0 dmi-3.3.0 smp vsyscall32
  configuration: boot=normal chassis=desktop family=To be filled by O.E.M. 
sku=SKU uuid=0ABCA172-BFA8-2AC5-FC37-3C7C3FD88FE4
*-core
 description: Motherboard
 product: TUF GAMING B550M-PLUS (WI-FI)
 vendor: ASUSTeK COMPUTER INC.
 physical id: 0
 version: Rev X.0x
 serial: 201176738701636
 slot: Default string
   *-firmware
description: BIOS
vendor: American Megatrends Inc.
physical id: 0
version: 2403
date: 06/16/2021
size: 64KiB
capacity: 16MiB
capabilities: pci apm upgrade shadowing cdboot bootselect 
socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen 
int9keyboard int14serial int17printer acpi usb biosbootspecification uefi
   *-memory

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


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

[Kernel-packages] [Bug 1935584] Re: Fix host to pod traffic with ovn cluster using ovs internal port and tc offload

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

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

Title:
  Fix host to pod traffic with ovn cluster using ovs internal port and
  tc offload

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

Bug description:
  * Explain the bug(s)

  When using ovs internal port with tc the redirect rules to internal port is 
back
  to ingress instead of egress.
  When we reinsert the skb we start from chain 0 but it could be ct state 
already
  set so matching rules on the internal port queue would miss.

  * brief explanation of fixes

  When reinserting skb back to ingress queue to restart tc
  classification then also reset ct.

  * How to test

  The setup was created by using ovn and testing iperf traffic from host 
container to VF pod.
  The result was ip set on the ovs bridge netdev (internal port)
  The rules were from rep to eventually the internal port and internal port to 
rep.
  The rules were with ct actions and chains tc-policy was set to skip-hw.
  Without the commit the traffic doesn’t work when hw-offload was true (offload 
to tc sw only) but
  does work with hw-offload false (ovs dp).

  * What it could break.

  Traffic not working in some cases using internal ports and CT.

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


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

[Kernel-packages] [Bug 1934304] Re: i2c-mlxbf.c: prevent stack overflow in mlxbf_i2c_smbus_start_transaction

2021-07-30 Thread Meriton Tuli

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

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

Title:
  i2c-mlxbf.c: prevent stack overflow in
  mlxbf_i2c_smbus_start_transaction

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

Bug description:
  SRU Justification:

  [Impact]

  There could be stack overflow in mlxbf_i2c_smbus_start_transaction().
  memcpy() is called in a loop while 'operation->length' upper bound is not
  checked and 'data_idx' also increments.

  More details:
  The operation length is verified by the caller functions so it cannot exceed 
I2C_SMBUS_BLOCK_MAX bytes (32 bytes) for each operation that is a part of the 
write. Data_desc array is 128 bytes in size. So potentially a request which 
consists of 4 writes, 32 bytes each can trigger an off-by-one or off-by-two 
overflow, because the first byte of data_desc is used by addr, effectively 
decreasing the available data_desc buffer size by one. Functions like 
mlx_smbus_i2c_block_func() that prepare the request also set the length of the 
first write operation to one and store the command id there, so the target 
buffer size again decreases data_desc by one, making it two bytes less than 
expected.

  [Fix]

  * Add a check for "operation->length" and data_idx and return error if
  reached upper bound.

  [Test Case]

  * Test the i2c-mlxbf.c driver using IPMB functionality.

  [Regression Potential]

  This fix returns a negative value to indicate that a transaction has
  failed. So it will catch more transactions failures.

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


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

[Kernel-packages] [Bug 1934819] Re: Fix err check for nf_conntrack_confirm

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

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

Title:
  Fix err check for nf_conntrack_confirm

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

Bug description:
  
  * Explain the bug(s)

  Conntrack confirm operation wasn't checked, this could result in
  accepting packet which should be dropped.

  * brief explanation of fixes

  Match behavior of ovs and netfilter. Drop the packets which are not
  accepted.

  * How to test

  First observe packets accepted with status of NF_DROP without the fix.
  Then observe packets are correctly dropped with the patch.

  * What it could break.

  Nothing breaks, but fixing security hole.

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


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

[Kernel-packages] [Bug 1934401] Re: Control netfilter flow table timeouts via sysctl

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

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

Title:
  Control netfilter flow table timeouts via sysctl

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

Bug description:
  * Explain the bug(s)
   
  TCP and UDP connections may be offloaded from nf conntrack to nf flow table.
  Offloaded connections are aged after 30 seconds of inactivity. 
  Once aged, ownership is returned to conntrack with a hard coded tcp/udp 
pickup time of 120/30 seconds, after which the connection may be deleted. 

  The current hard-coded pickup intervals may introduce a very
  aggressive aging policy. For example, offloaded tcp connections in
  established state will timeout from nf conntrack after just 150
  seconds of inactivity, instead of 5 days. In addition, the hard-coded
  30 second offload timeout period can significantly increase the
  hardware insertion rate requirements in some use cases.

  
  * Brief explanation of fixes
   
  This patchset provides the user with the ability to configure protocol 
specific offload timeout and pickup intervals via sysctl.

  The first and second patches revert the existing non-upstream solution.
  The next two patches introduce the sysctl configuration for tcp and udp 
protocols.
  The last patch modifies nf flow table aging mechanisms to use the configured 
time intervals. 
   
  * How to test

  Control tcp/udp connection timeout using the following sysctl parameters:
  net.netfilter.nf_flowtable_tcp_pickup = 120 
net.netfilter.nf_flowtable_tcp_timeout = 30 
net.netfilter.nf_flowtable_udp_pickup = 30 
net.netfilter.nf_flowtable_udp_timeout = 30 
   
  * What it could break.
   
  Existing configuration scripts – not kernel related

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


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

[Kernel-packages] [Bug 1934499] Re: New BPF helpers to query conntrack and to generate/validate SYN cookies

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

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

Title:
  New BPF helpers to query conntrack and to generate/validate SYN
  cookies

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

Bug description:
  Ticket for the patch series that adds new BPF helpers to query
  conntrack and to generate SYN cookies for forwarded connections.

  * Explain the bug(s)

  This patch series aims to accelerate iptables synproxy module with
  XDP. The stage that generates and checks SYN cookies is stateless and
  can be implemented in XDP.

  * Brief explanation of fixes

  The series first cherry picked multiple upstream patches from xdp/bpf to 
support
  the new BPF helpers.

  Then it adds new BPF helpers on top of those upstream patches.

  * bpf_ct_lookup_tcp to lookup CT status of a TCP connection.

  * bpf_tcp_raw_gen_syncookie to generate SYN cookies without a listening
  socket on the same host (to be used with iptables synproxy module).

  * bpf_tcp_raw_check_syncookie to check SYN cookies generated by the
  previos helper (to be used with iptables synproxy module).

  * bpf_tcp_raw_gen_tscookie to generate timestamp cookies, which encode
  additional information like SACK permission, ECN support, window scale.
  The format is compatible with iptables synproxy module.

  These new helpers allow to accelerate the iptables synproxy module. This
  series also includes some dependency patches backported from upstream.

  * How to test

  Use an XDP application that generates and checks SYN cookies,
  leveraging the new helpers.

  * What it could break.

  Nothing should be broken, only new functionality is added, and some
  patches are backported from upstream.

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


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

[Kernel-packages] [Bug 1934822] Re: Possible memory leak of flow_block_cb

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

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

Title:
  Possible memory leak of flow_block_cb

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

Bug description:
  * Explain the bug(s)

  When cleaning up the nf_table in tcf_ct_flow_table_cleanup_work
  there is no guarantee that the callback list, added to by
  nf_flow_table_offload_add_cb, is empty. This means that it is
  possible that the flow_block_cb memory allocated will be lost.

  
  * brief explanation of fixes

  Fix this by iterating the list and freeing the flow_block_cb entries
  before freeing the nf_table entry (via freeing ct_ft).

  * How to test

  With mlx5 driver registers flow block callback, cleaning up rule with action 
ct
  frees the ct_ft but with memory leak.

  * What it could break.

  Nothing breaks, memory leak is fixed.

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


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

[Kernel-packages] [Bug 1935034] Re: Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04

2021-07-30 Thread Michael Reed

If patches are missing can you add them please?   Currently this patch
set is not cherry picking cleanly.

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

Title:
  Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  New
Status in linux source package in Hirsute:
  New
Status in linux source package in Impish:
  Confirmed

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

  I could see both Ubuntu 21.10 and 20.04 HWE has mpt3sas driver
  v36.100.00.00, following are the commit ID's to update to 38.100.00.00

  8b3c803529 scsi: mpt3sas: Signedness bug in _base_get_diag_triggers()
  39718fe7ad scsi: mpt3sas: Fix spelling mistake in Kconfig "compatiblity" -> 
"compatibility"
  bfb3f00c06 scsi: mpt3sas: Simplify bool comparison
  d309ae0732 scsi: mpt3sas: Fix ReplyPostFree pool allocation
  664f0dce20 scsi: mpt3sas: Add support for shared host tagset for CPU hotplug
  688c1a0a13 scsi: mpt3sas: Additional diagnostic buffer query interface
  446b5f3d3f scsi: mpt3sas: Update driver version to 37.100.00.00

  8278807abd scsi: core: Add scsi_device_busy() wrapper
  020b0f0a31 scsi: core: Replace sdev->device_busy with sbitmap

  e015e0ded1 scsi: mpt3sas: Fix misspelling of _base_put_smid_default_atomic()
  2111ba8781 scsi: mpt3sas: Move a little data from the stack onto the heap
  cf9e575e62 scsi: mpt3sas: Fix a bunch of potential naming doc-rot
  54cb88dc30 scsi: mpt3sas: Fix a couple of misdocumented functions/params
  782a1ab33f scsi: mpt3sas: Fix some kernel-doc misnaming issues
  a50bd64616 scsi: mpt3sas: Do not use GFP_KERNEL in atomic context
  a1c4d77413 scsi: mpt3sas: Replace unnecessary dynamic allocation with a 
static one
  d6adc251dd scsi: mpt3sas: Force PCIe scatterlist allocations to be within 
same 4 GB region
  7dd847dae1 scsi: mpt3sas: Force chain buffer allocations to be within same 4 
GB region
  970ac2bb70 scsi: mpt3sas: Force sense buffer allocations to be within same 4 
GB region
  58501fd937 scsi: mpt3sas: Force reply buffer allocations to be within same 4 
GB region
  2e4e858732 scsi: mpt3sas: Force reply post buffer allocations to be within 
same 4 GB region
  c569de899b scsi: mpt3sas: Force reply post array allocations to be within 
same 4 GB region
  37067b9793 scsi: mpt3sas: Update driver version to 37.101.00.00

  a8d548b0b3 scsi: mpt3sas: Fix a few kernel-doc issues
  3401ecf7fc scsi: mpt3sas: Fix error return code of mpt3sas_base_attach()

   
  206a3afa94 scsi: mpt3sas: Fix a typo
  4c51f95696 scsi: mpt3sas: Only one vSES is present even when IOC has multi 
vSES
  c0629d70ca scsi: mpt3sas: Fix endianness for ActiveCablePowerRequirement
  3c8604691d scsi: mpt3sas: Block PCI config access from userspace during reset
  16660db3fc scsi: mpt3sas: Fix out-of-bounds warnings in _ctl_addnl_diag_query
  3ad0b1da0d scsi: mpt3sas: Fix two kernel-doc headers
  2910a4a9e9 scsi: mpt3sas: Documentation cleanup
  e2fac6c44a scsi: mpt3sas: Fix deadlock while cancelling the running firmware 
event
  19a622c39a scsi: mpt3sas: Handle firmware faults during first half of IOC init
  a0815c45c8 scsi: mpt3sas: Handle firmware faults during second half of IOC 
init

  f2b1e9c6f8 scsi: core: Introduce scsi_build_sense()

  84a84cc6af scsi: mpt3sas: Fix fall-through warnings for Clang
  cf750be8e6 scsi: mpt3sas: Fix Coverity reported issue
  d6c2ce435f scsi: mpt3sas: Fix error return value in _scsih_expander_add()

  
  Note:
  We have  already posted patch to update  driver version to 38.100.00.00
  Other patches are already available in upstream .

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


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

[Kernel-packages] [Bug 1937872] Re: Bluetooth is not working in Ubuntu 20.04

There are no hardware information or system logs attached so one can
only guess what's going on; however there were reports that disabling
fast startup in Windows is required for wifi and/or bluetooth to work
properly. Please give it a try.

I did a quick search and a tutorial shows how to disable it
https://help.uaudio.com/hc/en-us/articles/213195423-How-To-Disable-Fast-
Startup-in-Windows-10

** Summary changed:

- Bluetooth is not working in Ubuntu 20.04
+ Bluetooth is not working in Ubuntu 20.04 (dual boot Windows)

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

Title:
  Bluetooth is not working in Ubuntu 20.04 (dual boot Windows)

Status in linux package in Ubuntu:
  New

Bug description:
  I have dual OS in my Dell laptop, Bluetooth is working in Windows, but
  not working in Ubuntu 20.04

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-raspi/5.4.0.1042.77)

All autopkgtests for the newly accepted linux-meta-raspi (5.4.0.1042.77) for 
focal have finished running.
The following regressions have been reported in tests triggered by the package:

snapd/unknown (arm64)
xtables-addons/unknown (arm64)
evdi/unknown (arm64)
rtl8812au/unknown (arm64)
adv-17v35x/unknown (arm64)
dpdk/unknown (arm64)
dm-writeboost/unknown (arm64)
backport-iwlwifi-dkms/unknown (arm64)
systemd/unknown (arm64)
west-chamber/unknown (arm64)
fwts/unknown (arm64)
langford/unknown (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-raspi

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1932367] Re: Pixel format change broken for Elgato Cam Link 4K

2021-07-30 Thread Benjamin Drung

Installed linux 5.4.0-81.91 and verified that it is working.

** Tags removed: verification-needed-focal
** Tags added: verification-done-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/1932367

Title:
  Pixel format change broken for Elgato Cam Link 4K

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

Bug description:
  [Impact]

  The Elgato Cam Link 4K HDMI video capture card reports to support three
  different pixel formats, where the first format depends on the connected
  HDMI device.

  ```
  $ v4l2-ctl -d /dev/video0 --list-formats-ext
  ioctl: VIDIOC_ENUM_FMT
   Type: Video Capture

   [0]: 'NV12' (Y/CbCr 4:2:0)
    Size: Discrete 3840x2160
     Interval: Discrete 0.033s (29.970 fps)
   [1]: 'NV12' (Y/CbCr 4:2:0)
    Size: Discrete 3840x2160
     Interval: Discrete 0.033s (29.970 fps)
   [2]: 'YU12' (Planar YUV 4:2:0)
    Size: Discrete 3840x2160
     Interval: Discrete 0.033s (29.970 fps)
  ```

  Changing the pixel format to anything besides the first pixel format
  does not work:

  ```
  $ v4l2-ctl -d /dev/video0 --try-fmt-video pixelformat=YU12
  Format Video Capture:
   Width/Height  : 3840/2160
   Pixel Format  : 'NV12' (Y/CbCr 4:2:0)
   Field : None
   Bytes per Line: 3840
   Size Image: 12441600
   Colorspace: sRGB
   Transfer Function : Rec. 709
   YCbCr/HSV Encoding: Rec. 709
   Quantization  : Default (maps to Limited Range)
   Flags :
  ```

  User space applications like VLC might show an error message on the
  terminal in that case:

  ```
  libv4l2: error set_fmt gave us a different result than try_fmt!
  ```

  Depending on the error handling of the user space applications, they
  might display a distorted video, because they use the wrong pixel format
  for decoding the stream.

  [Fix]

  The Elgato Cam Link 4K responds to the USB video probe
  VS_PROBE_CONTROL/VS_COMMIT_CONTROL with a malformed data structure: The
  second byte contains bFormatIndex (instead of being the second byte of
  bmHint). The first byte is always zero. The third byte is always 1.

  The firmware bug was reported to Elgato on 2020-12-01 and it was
  forwarded by the support team to the developers as feature request.
  There is no firmware update available since then. The latest firmware
  for Elgato Cam Link 4K as of 2021-03-23 has MCU 20.02.19 and FPGA 67.

  Therefore correct the malformed data structure for this device. The
  change was successfully tested with VLC, OBS, and Chromium using
  different pixel formats (YUYV, NV12, YU12), resolutions (3840x2160,
  1920x1080), and frame rates (29.970 and 59.940 fps).

  [Test Case]

  Connect an input device to the Cam Link 4K and try all three pixel
  formats with VLC:

vlc v4l2:///dev/video0 --v4l2-chroma=NV12
vlc v4l2:///dev/video0 --v4l2-chroma=YU12

  [Other Info]

  The fix was reviewed and accepted by the subsystem maintainer and will
  be included upstream:
  
https://git.linuxtv.org/media_stage.git/commit/?id=4c6e0976295add7f0ed94d276c04a3d6f1ea8f83

  Attached a backported patch for Ubuntu. I successfully tested it with
  Linux 5.11 on Ubuntu 21.04 and Linux 5.8 on Ubuntu 20.10. It should
  work on older kernel versions as well.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-raspi-5.4/5.4.0.1042.45)

All autopkgtests for the newly accepted linux-meta-raspi-5.4 (5.4.0.1042.45) 
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

asic0x/unknown (arm64)
lxc/unknown (arm64)
r8168/unknown (arm64)
dpdk/unknown (arm64)
wireguard-linux-compat/unknown (arm64)
west-chamber/unknown (arm64)
ktap/unknown (arm64)
rtl8821ce/unknown (arm64)
systemd/unknown (arm64)
xtables-addons/unknown (arm64)
spl-linux/unknown (arm64)
rtl8812au/unknown (arm64)
bbswitch/unknown (arm64)
acpi-call/unknown (arm64)
fwts/unknown (arm64)
nat-rtsp/unknown (arm64)
langford/unknown (arm64)
zfs-linux/unknown (arm64)
lxd/unknown (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-meta-raspi-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-raspi/5.11.0.1016.14)

All autopkgtests for the newly accepted linux-meta-raspi (5.11.0.1016.14) for 
hirsute have finished running.
The following regressions have been reported in tests triggered by the package:

rtl8812au/unknown (arm64)
r8168/unknown (arm64)
rtl8821ce/unknown (arm64)
langford/unknown (arm64)
dm-writeboost/unknown (arm64)
ddcci-driver-linux/unknown (arm64)
openafs/unknown (arm64)
libvpoll-eventfd/unknown (arm64)
dpdk-kmods/unknown (arm64)
systemd/unknown (arm64)
west-chamber/unknown (arm64)
wireguard/unknown (arm64)
zfs-linux/unknown (arm64)
xtables-addons/unknown (arm64)
v4l2loopback/unknown (arm64)
snapd/unknown (arm64)
gost-crypto/unknown (arm64)
digimend-dkms/unknown (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/hirsute/update_excuses.html#linux-meta-raspi

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1925421] Re: arm64 support

2021-07-30 Thread Ubuntu Kernel Bot

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

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-hirsute

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

Title:
  arm64 support

Status in linux-oracle package in Ubuntu:
  Fix Released
Status in linux-oracle-5.4 package in Ubuntu:
  New
Status in linux-oracle-5.8 package in Ubuntu:
  New
Status in linux-oracle source package in Bionic:
  Invalid
Status in linux-oracle-5.4 source package in Bionic:
  Fix Released
Status in linux-oracle-5.8 source package in Bionic:
  New
Status in linux-oracle source package in Focal:
  Fix Released
Status in linux-oracle-5.4 source package in Focal:
  Invalid
Status in linux-oracle-5.8 source package in Focal:
  Fix Released
Status in linux-oracle source package in Groovy:
  Fix Released
Status in linux-oracle-5.4 source package in Groovy:
  Invalid
Status in linux-oracle-5.8 source package in Groovy:
  Fix Committed

Bug description:
  See
  https://canonical.lightning.force.com/lightning/r/Case/5003z2BzFG4AAN/view
  for more info

  
  [Impact]
  No support for arm64 currently

  
  [Fix]
  Add arm64 support, including hardware support patches

  [Test]
  Confirm that it boots on desired arm64 hardware, as well as VMs

  [Regression Potential]
  This was never working on arm64 so there should be no risk of regression.
  The requested changes included some refactorings of early memory 
initialization code (all arches) so this presents a small risk. The changes 
were tested on arm64 as well amd64.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/4.15.0.153.142)