[Kernel-packages] [Bug 1968391] Re: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS

2022-08-25 Thread Kai-Heng Feng
clayg, the most easy way to find the offender is to do a kernel bisection:
https://wiki.ubuntu.com/Kernel/KernelBisection

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

Title:
  Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Using the current beta of Jammy, I no longer have stable WiFi after
  April 5, 2022 update of wpasupplicant from 2:2.10-2 to 2:2.10-6. There
  is a chance it may also be related to network-manager going from
  1.36.4-1ubuntu1 to 1.36.4-2ubuntu1, but the logs seems to point to
  wpasupplicant (see below)

  Wifi is stable often, but also often it fails to load webpages
  intermittently or fails to download the packages using apt for
  example, so it's not browser related.

  Example output of journalctl -xe -u wpasupplicant:
  Apr 08 19:26:28 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-CONNECTED - 
Connection to fc:34:97:23:4c:3c completed [id=0 id_str=]
  Apr 08 19:26:28 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE 
above=0 signal=-72 noise=-95 txrate=7200
  Apr 08 19:26:32 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS
  Apr 08 19:26:33 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS
  Apr 08 19:26:34 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS
  Apr 08 19:26:35 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS
  Apr 08 19:26:36 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS
  Apr 08 19:26:37 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS
  Apr 08 19:26:38 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS
  Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS
  Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-DISCONNECTED 
bssid=fc:34:97:23:4c:3c reason=4 locally_generated=1
  Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE 
init=CORE type=WORLD
  Apr 08 19:26:40 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE 
init=BEACON_HINT type=UNKNOWN
  Apr 08 19:26:40 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE 
init=BEACON_HINT type=UNKNOWN
  Apr 08 19:26:42 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE 
init=BEACON_HINT type=UNKNOWN
  Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE 
init=BEACON_HINT type=UNKNOWN
  Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: SME: Trying to 
authenticate with fc:34:97:23:4c:3c (SSID='CamplingVanDerKolk5G' freq=5260 MHz)
  Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: Trying to associate with 
fc:34:97:23:4c:3c (SSID='CamplingVanDerKolk5G' freq=5260 MHz)
  Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: Associated with 
fc:34:97:23:4c:3c
  Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: 
CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
  Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE 
init=COUNTRY_IE type=COUNTRY alpha2=CA
  Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: WPA: Key negotiation 
completed with fc:34:97:23:4c:3c [PTK=CCMP GTK=CCMP]
  Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-CONNECTED - 
Connection to fc:34:97:23:4c:3c completed [id=0 id_str=]
  Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE 
above=0 signal=-72 noise=-95 txrate=7200
  Apr 08 19:29:23 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE 
above=1 signal=-66 noise=-94 txrate=27
  Apr 08 19:49:04 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE 
above=0 signal=-73 noise=-95 txrate=27
  Apr 08 19:59:04 weasel wpa_supplicant[772]: wlp13s0: WPA: Group rekeying 
completed with fc:34:97:23:4c:3c [GTK=CCMP]
  Apr 08 20:00:23 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE 
above=1 signal=-66 noise=-95 txrate=243000

  
  Additional info:

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:Ubuntu Jammy Jellyfish (development branch)
  Release:22.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt-cache policy wpasupplicant 
  wpasupplicant:
Geïnstalleerd: 2:2.10-6
Kandidaat: 2:2.10-6
Versietabel:
   *** 2:2.10-6 500
  500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-6
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Apr  8 21:28:12 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-03-12 (27 days ago)
  Installa

[Kernel-packages] [Bug 1983468] Re: tx checksumming offload results in TCP/UDP packet drops (was Octavia amphora loadbalancer gets stuck at PENDING_CREATE status)

2022-08-25 Thread Marcelo Subtil Marcal
Update:

Using the Focal HWE kernel (5.15.0-46-generic #49~20.04.1-Ubuntu SMP),
this error does not happen.

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

Title:
  tx checksumming offload results in TCP/UDP packet drops (was Octavia
  amphora loadbalancer gets stuck at PENDING_CREATE status)

Status in OpenStack Octavia Charm:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In a new focal-yoga deployment, the creation of a loadbalancer gets
  stuck at PENDING_CREATE status.

  Checking the amphora we could see that it stays at BOOTING status:

  $ openstack loadbalancer amphora show ef48089d-ba40-46db-92e8-e369f764f017 
--format yaml
  id: ef48089d-ba40-46db-92e8-e369f764f017
  loadbalancer_id: dcd17d9e-6a27-43c5-9c3f-eb2b266d
  compute_id: 5efe11a8-93d8-4278-94c2-4efc8b015009
  lb_network_ip: fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa
  vrrp_ip: null
  ha_ip: null
  vrrp_port_id: null
  ha_port_id: null
  cert_expiration: '2022-09-01T20:27:05'
  cert_busy: false
  role: null
  status: BOOTING
  vrrp_interface: null
  vrrp_id: null
  vrrp_priority: null
  cached_zone: nova
  created_at: '2022-08-02T20:27:05'
  updated_at: '2022-08-02T20:30:13'
  image_id: 6c6cd911-197f-45d3-a6d5-4ff1789d4ee7
  compute_flavor: 638fa4c5-e81b-438f-a12b-1ef7faf81c3e

  
  /var/log/octavia/octavia-worker.log shows several warnings about connection 
failure to the amphora.

  2022-08-02 20:30:22.589 149659 WARNING
  octavia.amphorae.drivers.haproxy.rest_api_driver [-] Could not connect
  to instance. Retrying.: requests.exceptions.ConnectTimeout:
  HTTPSConnectionPool(host='fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa',
  port=9443): Max retries exceeded with url: // (Caused by
  ConnectTimeoutError(, 'Connection to
  fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa timed out. (connect
  timeout=10.0)'))

  
  It is possible to ping the amphora from an octavia unit:

  # ping -M do -s 1452 fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa
  PING 
fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa(fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa)
 1452 data bytes
  1460 bytes from fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa: icmp_seq=1 ttl=64 
time=2.45 ms
  1460 bytes from fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa: icmp_seq=2 ttl=64 
time=1.01 ms
  1460 bytes from fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa: icmp_seq=3 ttl=64 
time=0.532 ms
  1460 bytes from fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa: icmp_seq=4 ttl=64 
time=0.417 ms

  Also, the port tcp/22 is reacheable from the octavia unit:

  # telnet fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa 22
  Trying fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa...
  Connected to fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa.
  Escape character is '^]'.
  SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.5

  After running the config-changed hook as described at the bug
  https://bugs.launchpad.net/charm-octavia/+bug/1961088 , the creation
  of a loadbalancer ends with a ERROR provisioning_status.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-octavia/+bug/1983468/+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 1987699] Re: azure: CIFS Backport Updates to 5.15 Kernel

2022-08-25 Thread Tim Gardner
Test kernel at https://kernel.ubuntu.com/~rtg/jammy-azure-
cifs-5.19-sf00343105/5.15.0-1020.25~lp1987699.1

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

Title:
  azure: CIFS Backport Updates to 5.15 Kernel

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Jammy:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  Microsoft has requested updating CIFS to the 5.15 backport as
  published in 'git://git.samba.org/sfrench/cifs-2.6.git 5.15-backport'.

  [Test Plan]

  Microsoft tested

  [Where things could go wrong]

  CIFS network connections could misbehave

  [Other Info]

  SF: #00343105

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1987699/+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 1987699] [NEW] azure: CIFS Backport Updates to 5.15 Kernel

2022-08-25 Thread Tim Gardner
Public bug reported:

SRU Justification

[Impact]

Microsoft has requested updating CIFS to the 5.15 backport as published
in 'git://git.samba.org/sfrench/cifs-2.6.git 5.15-backport'.

[Test Plan]

Microsoft tested

[Where things could go wrong]

CIFS network connections could misbehave

[Other Info]

SF: #00343105

** Affects: linux-azure (Ubuntu)
 Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
 Status: Fix Released

** Affects: linux-azure (Ubuntu Jammy)
 Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

** Package changed: linux (Ubuntu) => linux-azure (Ubuntu)

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

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

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

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

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

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

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

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

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

Title:
  azure: CIFS Backport Updates to 5.15 Kernel

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Jammy:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  Microsoft has requested updating CIFS to the 5.15 backport as
  published in 'git://git.samba.org/sfrench/cifs-2.6.git 5.15-backport'.

  [Test Plan]

  Microsoft tested

  [Where things could go wrong]

  CIFS network connections could misbehave

  [Other Info]

  SF: #00343105

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1987699/+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 1981487] Re: kernel BUG/Oops errors from modprobe while the DRBG has not yet initialized (focal/fips-updates)

2022-08-25 Thread Mauricio Faria de Oliveira
** 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/1981487

Title:
  kernel BUG/Oops errors from modprobe while the DRBG has not yet
  initialized (focal/fips-updates)

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

Bug description:
  [Impact]

   * The Focal FIPS kernel in fips-updates hits kernel BUG/Oops
     errors during boot with the FIPS OpenSSL library installed
     (but those don't cause issues), when it runs modprobe with
     request_module() when looking up crypto algorithms/modules.

   * The modprobe command happens to call the OpenSSL library,
     and the FIPS version of OpenSSL calls getrandom(),
     and the FIPS kernel calls the DRBG for that,
     BUT it's _not yet_ initialized that early during boot
     when the kernel can run modprobe via request_module().
     (e.g., IPv6 initialization time.)

   * The issue impacts the kernels in fips-updates only, per:
     "UBUNTU: SAUCE: random: Use Crypto API DRBG for urandom in FIPS mode"
     which exists in Focal, but not in Xenial/Bionic/Jammy.

   * The issue only happens with the crypto algorithms, even
     if they're built-in (i.e., modprobe is not needed).

  [Fix]

   * Fall back to CRNG while the DRBG is not yet initialized.
     (Marcelo Cerri confirmed it's OK per other discussions.)

   * The fix doesn't change the list and details of algorithms
     as in /proc/crypto (e.g., name, driver, module,  priority)
     by the time the DRBG is initialized / initramfs started,
     so even though behavior changes, the net effect doesn't.

   * (Note: it's not possible to just use an initcall level
  earlier than rootfs_initcall() so modprobe isn't there,
  because fips_drbg_init() must run _after_ module_init()
  level so that crypto_rng_reset() works, even though its
  required module is built-in too.

  [Test Steps]

   * Install the kernel and openssl from fips-updates,
     boot with fips=1, check dmesg for BUG/Oops errors:

     $ sudo apt install linux-image-fips libssl1.1 # fips-updates
     $ sudo vim /etc/default/grub # append fips=1 boot option
     $ sudo update-grub && sudo reboot
     $ sudo dmesg | grep BUG:

   * Check/store the /proc/crypto file for comparisons.
     You can boot with break=top as well, to check that
     as early as possible, and copy into /run/initramfs/
     then exit, to get it later in the rootfs.

  [Regression Potential]

   * The fix falls back to the regular CRNG for a while
     in early boot. The CRNG is used permanently in the
     non-FIPS kernels (and in FIPS kernels w/out fips=1),
     so the code path is exercised/tested frequently.

   * Regressions would most likely occur in calls to
     getrandom() before the DRBG is initialized, but
     that currently hits a BUG/Oops anyway.

  [Original Bug Description]

  $ sudo apt install --yes linux-image-fips # fips-updates
  $ sudo vim /etc/default/grub # fips=1
  $ sudo update-grub && sudo reboot

  $ uname -r
  5.4.0-1056-fips

  $ cat /proc/cmdline
  ... fips=1

  No errors with the original/non-FIPS openssl, because it does NOT call
  getrandom():

  $ dmesg | grep -c BUG:
  0

  $ dpkg -s libssl1.1 | grep ^Version:
  Version: 1.1.1f-1ubuntu2.15

  $ strace -e getrandom modprobe --version
  kmod version 27
  +ZSTD +XZ -ZLIB +LIBCRYPTO -EXPERIMENTAL
  +++ exited with 0 +++

  But if you install the FIPS openssl, it calls getrandom(), then
  BUG/Oops happen:

  $ sudo apt install libssl1.1 # updates initramfs

  $ dpkg -s libssl1.1 | grep ^Version:
  Version: 1.1.1f-1ubuntu2.fips.13.1

  $ strace -e getrandom modprobe --version
  getrandom("\xc4\x84\x26\x25\x6f\xd4\xed\x38\xdf\xa9\x67\xee\x15\x1c\xe3\x98", 
16, GRND_NONBLOCK) = 16
  getrandom("\xa1\xd6\x67\x3e\xe4\x90\xb3\x8b\xdf\xe6\x34\x2a\xa7\x50\xbc\x2f", 
16, GRND_NONBLOCK) = 16
  getrandom("\xf1\x3e\xe4\x27\x9d\x47\x8c\x4b\x8a\x39\x8c\xe1\x2e\xee\xfa\x45", 
16, GRND_NONBLOCK) = 16
  getrandom("\xfb\x34\x18\x44\xd8\x23\x4c\x87\x13\x2e\x6b\x03\x79\xa7\x99\xf8", 
16, 0) = 16
  getrandom("\xdd\x83\xa7\x02\x10\x51\x2b\x4f\x21\x6b\xc1\xf1\x0d\xe7\x44\xb7", 
16, 0) = 16
  kmod version 27
  +ZSTD +XZ -ZLIB +LIBCRYPTO -EXPERIMENTAL
  +++ exited with 0 +++

  $ sudo reboot

  $ dmesg | grep -c BUG:
  22

  $ dmesg
  ...
  [1.595759] NET: Registered protocol family 10
  [1.600256] BUG: kernel NULL pointer dereference, address: 0038
  ...
  [1.603829] CPU: 2 PID: 137 Comm: modprobe Not tainted 5.4.0-1056-fips 
#64-Ubuntu
  [1.603829] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.13.0-1ubuntu1.1 04/01/2014
  [1.603829] RIP: 0010:urandom_read+0x268/0x480
  ...
  [1.603829] Call Trace:
  [

[Kernel-packages] [Bug 1970965] Re: Wifi randomly disconnects [AR9462]

2022-08-25 Thread clayg
I believe this lp issue is related to another issue #1968391

For me the problem did I was seeing with wifi disconnects did NOT go
away when I installed 5.17.11, but my wifi is running stable for >24
hours with an *older* kernel:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968391/comments/13

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

Title:
  Wifi randomly disconnects [AR9462]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  my hardware : laptop Asus N751JK Network controller: Qualcomm Atheros
  AR9462 Wireless Network Adapter (rev 01) Subsystem: AzureWave AR9462
  Wireless Network Adapter

  I was runing Ubuntu 20.10, 21.04 up to Ubuntu 21.10 with Ubuntu Kernel 5.13.0 
without any problem.
  When migrated to Ubuntu 22.04 which installs Ubuntu Kernel 5.15.0.x (which 
corresponds to Mainline Kernel 5.15.5) then the problems started.

  The Mainline Kernel 5.15.4 corresponds to the Ubuntu Kernel 5.15.0-12.12 
(date 2021-11-21 13:32:06)
  The Mainline Kernel 5.15.5 corresponds to the Ubuntu Kernel 5.15.0-13.13 
(date 2021-11-25 09:35:53)

  I upgraded and tested unsuccessfully the following Mainline Kernels :
  5.15.28, 5.15.36, 5.16.14, 5.16.20, 5.17.4, 5.17.5

  I disabled the power save as explained at 
https://askubuntu.com/questions/1403773/22-04-wifi-keeps-disconnecting-for-a-few-seconds-frequently/1404471#1404471
  without improvement in any of the Kernels tested.
  Also the "intel_iommu=off" mentioned at 
https://groups.google.com/g/linux.debian.kernel/c/RFpPIp0cncA/m/v9ELDxLICgAJ 
Bug#994590 didn't help.

  I downgraded and currently running without any problem using the
  Ubuntu Kernels 5.13.19-051319-generic or Mainline Kernels 5.15.0 or
  5.15.4

  There is no problem in my airpoint (router) nor my internet access, I have 
other different computers and devices working correctly on wifi.
  In addition my N751JK works correctly when using the Ethernet adapter for the 
physical cable.

  seems to be something between Mainline Kernels 5.15.4 and 5.15.5 that
  is also propagated to 5.16.x and 5.17.x

  (started at https://bugzilla.kernel.org/show_bug.cgi?id=215918)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-02-21 (432 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  jammy
  Uname: Linux 5.15.5-051505-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970965/+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 1968391] Re: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS

2022-08-25 Thread clayg
I can confirm for my wifi adapter, the problem described in this issue
does not exist on an OLDER kernel version

clayg@banana:~/Workspace/SwiftStack-NG$ uname -a
Linux banana 5.15.0-051500-generic #202110312130 SMP Sun Oct 31 21:33:20 UTC 
2021 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Using the current beta of Jammy, I no longer have stable WiFi after
  April 5, 2022 update of wpasupplicant from 2:2.10-2 to 2:2.10-6. There
  is a chance it may also be related to network-manager going from
  1.36.4-1ubuntu1 to 1.36.4-2ubuntu1, but the logs seems to point to
  wpasupplicant (see below)

  Wifi is stable often, but also often it fails to load webpages
  intermittently or fails to download the packages using apt for
  example, so it's not browser related.

  Example output of journalctl -xe -u wpasupplicant:
  Apr 08 19:26:28 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-CONNECTED - 
Connection to fc:34:97:23:4c:3c completed [id=0 id_str=]
  Apr 08 19:26:28 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE 
above=0 signal=-72 noise=-95 txrate=7200
  Apr 08 19:26:32 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS
  Apr 08 19:26:33 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS
  Apr 08 19:26:34 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS
  Apr 08 19:26:35 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS
  Apr 08 19:26:36 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS
  Apr 08 19:26:37 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS
  Apr 08 19:26:38 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS
  Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS
  Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-DISCONNECTED 
bssid=fc:34:97:23:4c:3c reason=4 locally_generated=1
  Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE 
init=CORE type=WORLD
  Apr 08 19:26:40 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE 
init=BEACON_HINT type=UNKNOWN
  Apr 08 19:26:40 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE 
init=BEACON_HINT type=UNKNOWN
  Apr 08 19:26:42 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE 
init=BEACON_HINT type=UNKNOWN
  Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE 
init=BEACON_HINT type=UNKNOWN
  Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: SME: Trying to 
authenticate with fc:34:97:23:4c:3c (SSID='CamplingVanDerKolk5G' freq=5260 MHz)
  Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: Trying to associate with 
fc:34:97:23:4c:3c (SSID='CamplingVanDerKolk5G' freq=5260 MHz)
  Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: Associated with 
fc:34:97:23:4c:3c
  Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: 
CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
  Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE 
init=COUNTRY_IE type=COUNTRY alpha2=CA
  Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: WPA: Key negotiation 
completed with fc:34:97:23:4c:3c [PTK=CCMP GTK=CCMP]
  Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-CONNECTED - 
Connection to fc:34:97:23:4c:3c completed [id=0 id_str=]
  Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE 
above=0 signal=-72 noise=-95 txrate=7200
  Apr 08 19:29:23 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE 
above=1 signal=-66 noise=-94 txrate=27
  Apr 08 19:49:04 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE 
above=0 signal=-73 noise=-95 txrate=27
  Apr 08 19:59:04 weasel wpa_supplicant[772]: wlp13s0: WPA: Group rekeying 
completed with fc:34:97:23:4c:3c [GTK=CCMP]
  Apr 08 20:00:23 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE 
above=1 signal=-66 noise=-95 txrate=243000

  
  Additional info:

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:Ubuntu Jammy Jellyfish (development branch)
  Release:22.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt-cache policy wpasupplicant 
  wpasupplicant:
Geïnstalleerd: 2:2.10-6
Kandidaat: 2:2.10-6
Versietabel:
   *** 2:2.10-6 500
  500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-6
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckRe

[Kernel-packages] [Bug 1984004] Re: Linux Firmware drops AMD RX6650 XT Performance

2022-08-25 Thread Juerg Haefliger
** Changed in: linux-firmware (Ubuntu Jammy)
   Status: Triaged => In Progress

** Description changed:

+ [Impact]
+ 
+ In e.g. the Unigine benchmark, the linux-firmware packages drops the
+ performance of my AMD RX 6650 XT GPU from 98 FPS in 1080p-high down to
+ 23 FPS. That wasn't a problem in Mint 20.3 with kernel 5.15 (Ubuntu
+ 20.04 based).
+ 
+ Getting the firmware directly from git brings the performance back to about 
100 FPS:
+ git clone 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
+ cd linux-firmware
+ sudo make install
+ sudo update-initramfs -c -k all
+ 
+ [Fix]
+ 
+ Update amdgpu/dimgrey_cavefish_* firmware files to latest versions from
+ kernel.org.
+ 
+ [Test Case]
+ 
+ See original description.
+ 
+ [Where Problems Could Occur]
+ 
+ Isolated to AMD GPUs that use dimgrey_cavefish firmware blobs.
+ 
+ [Original Description]
+ 
  Kernel: 5.15.0-43-generic
  linux-firmware: 20220329.git681281e4-0ubuntu3.3
  Tested with: Mint 21 Cinnamon (Ubuntu 22.04 based)
  
  In e.g. the Unigine benchmark, the linux-firmware packages drops the
  performance of my AMD RX 6650 XT GPU from 98 FPS in 1080p-high down to
  23 FPS. That wasn't a problem in Mint 20.3 with kernel 5.15 (Ubuntu
  20.04 based).
  
  Getting the firmware directly from git brings the performance back to about 
100 FPS:
  git clone 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
  cd linux-firmware
  sudo make install
  sudo update-initramfs -c -k all
  
  Re-installing the linux-firmware package causes the performance to drop
  again. So there is a problem with the linux firmware at least for the RX
  6650 XT, maybe for the whole RX 6000 series.
  
  The linux-firmware package in Ubuntu 22.04 should be updated.
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC2:  daelach1352 F pulseaudio
-  /dev/snd/controlC0:  daelach1352 F pulseaudio
-  /dev/snd/controlC1:  daelach1352 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  daelach1352 F pulseaudio
+  /dev/snd/controlC0:  daelach1352 F pulseaudio
+  /dev/snd/controlC1:  daelach1352 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: X-Cinnamon
  Dependencies: firmware-sof-signed 2.0-1ubuntu3 [origin: Ubuntu]
  DistroRelease: Linux Mint 21
  InstallationDate: Installed on 2020-08-24 (714 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  IwConfig:
-  lono wireless extensions.
-  
-  enp6s0no wireless extensions.
+  lono wireless extensions.
+ 
+  enp6s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  PackageArchitecture: all
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=UUID=a4b18dd9-4989-4bf5-8107-e55b8f8f6df4 ro amd_iommu=on iommu=pt quiet 
loglevel=3 splash
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions:
-  linux-restricted-modules-5.15.0-43-generic N/A
-  linux-backports-modules-5.15.0-43-generic  N/A
-  linux-firmware 20220329.git681281e4-0ubuntu3.3
+  linux-restricted-modules-5.15.0-43-generic N/A
+  linux-backports-modules-5.15.0-43-generic  N/A
+  linux-firmware 20220329.git681281e4-0ubuntu3.3
  RfKill:
-  
+ 
  Tags: vanessa third-party-packages
  Uname: Linux 5.15.0-43-generic x86_64
  UnreportableReason: This does not seem to be an official Linux 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 cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/25/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4901
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4901:bd07/25/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

Title:
  Linux Firmware drops AMD RX6650 XT Performance

Status in linux-firmware 

[Kernel-packages] [Bug 1987595] Re: Support Intel IPU6 MIPI camera

2022-08-25 Thread You-Sheng Yang
This depends on bug 1972106 and bug 1972109 that imports intel ipu6/ivsc
dkms into Ubuntu archive.

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

Title:
  Support Intel IPU6 MIPI camera

Status in linux-oem-5.17 package in Ubuntu:
  New

Bug description:
  This is a follow-up for bug 1964983 but on different platforms that
  runs linux-oem-5.17 or newer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1987595/+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 1699942] Missing required logs.

2022-08-25 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 1699942

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

Title:
  network-manager fails to deprecate addresses

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New

Bug description:
  network manager does not properly deprecate autoconfigured temporary IP 
addresses when ValidLifetime for a prefix is 0 in router advertisements. This 
behaviour is non-compliant with RFC 4861 § 6.3.4, which reads:
  If the prefix is already present in the host's Prefix List as
  the result of a previously received advertisement, reset its
  invalidation timer to the Valid Lifetime value in the Prefix
  Information option.  If the new Lifetime value is zero, time-out
  the prefix immediately.

  The hosts instead continued to use temporary addresses configured
  until they reached their timeout, rather than immediately dropping the
  addresses. It further appears that it is generating new temporary
  addresses when the previous ones expire, but I have not been
  monitoring hosts closely enough to tell for sure---I will update on
  this when I have further information.

  This problem was discovered on Ubuntu Studio 16.04.2; it is not
  present on Ubuntu Server (which uses Debian networking scripts).

  Additional Info:

  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  $ apt-cache policy network-manager
  network-manager:
Installed: 1.2.6-0ubuntu0.16.04.1
Candidate: 1.2.6-0ubuntu0.16.04.1
Version table:
   *** 1.2.6-0ubuntu0.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.2.2-0ubuntu0.16.04.4 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   1.1.93-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699942/+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 1699942] Re: network-manager fails to deprecate addresses

2022-08-25 Thread Julian Andres Klode
We believe the kernel handles RAs itself, adding a task for it.

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

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

Title:
  network-manager fails to deprecate addresses

Status in linux package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New

Bug description:
  network manager does not properly deprecate autoconfigured temporary IP 
addresses when ValidLifetime for a prefix is 0 in router advertisements. This 
behaviour is non-compliant with RFC 4861 § 6.3.4, which reads:
  If the prefix is already present in the host's Prefix List as
  the result of a previously received advertisement, reset its
  invalidation timer to the Valid Lifetime value in the Prefix
  Information option.  If the new Lifetime value is zero, time-out
  the prefix immediately.

  The hosts instead continued to use temporary addresses configured
  until they reached their timeout, rather than immediately dropping the
  addresses. It further appears that it is generating new temporary
  addresses when the previous ones expire, but I have not been
  monitoring hosts closely enough to tell for sure---I will update on
  this when I have further information.

  This problem was discovered on Ubuntu Studio 16.04.2; it is not
  present on Ubuntu Server (which uses Debian networking scripts).

  Additional Info:

  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  $ apt-cache policy network-manager
  network-manager:
Installed: 1.2.6-0ubuntu0.16.04.1
Candidate: 1.2.6-0ubuntu0.16.04.1
Version table:
   *** 1.2.6-0ubuntu0.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.2.2-0ubuntu0.16.04.4 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   1.1.93-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699942/+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 1987670] Re: Add support for AMD PMF

2022-08-25 Thread Mario Limonciello
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Add support for AMD PMF

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Some upcoming platforms support for AMD-PMF.

  This will enable ACPI platform profiles and some automatic transitions.
  The first 11 patches are queued up for 6.1 and also available in an immutable 
branch.

  https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-
  drivers-x86.git/log/?h=platform-drivers-x86-amd-pmf

  Can you please merge these to OEM-6.0?

  We will have 3-5 more patches targeted later as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987670/+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 1987618] Re: [jammy mlx5] Slow outbound N/S TCP connections for instances on gateways

2022-08-25 Thread Frode Nordahl
fwiw; the fix is somewhere to be found in these mainline commits:
b070e70381ee343dc10d2b1f0f3a6b1f940f0ae5
7843bd604081b5f005b31343cde1bb680bcc1776
2a829fe25d2809a33a6842359323bb139556c03d
a81283263bb0c38b52fce6d599c2434a8d232dd6
8300f225268be9ee2c0daf5a3f23929fcdcbf213
314e1105831b45a0fe3045411d7fec4997936e86
0610f8dc0309cd0ea017d129efb95a942325344d
d1a3138f7913014e0714cb1d3d44793d76fc38a1
bfbdd77ac52fecc198b049bff9574e84519ed9a5
7c5f940d264e4c3d4f4fdbb4dc84b9eca6d3ea43
4b5fba4a3ac790ad79bb4d36e7a4398702429b4d
1d5024f88dadb5949c9fd10876b3a9d2a202fc1e
b98d2d722f81b2043a4458adebfbe45e239d1f79
c1e80bf4ad3e91dd21a8ccdee129052e25ace7e6
9625bf39bd4140cebd60cc658846505f4ab6c8ca
71753b8ec103fd71d6ee90e522d797ccf978e4ed
3a9e5fff2ab0d6f4af701757d35b9453dc563b78
3c87aedd48997f9ab3afdeb2084f6b6163a21db8
ed5f9cf06b20f74c1098d6d62313e3e9af217fcb
62f7991feab69ed398ad6a03b911fa0ee0549516
3ab45777a27c5f53a55a2c353b70648449ca7a33
6b23f6ab86a4f3a608b9bfa98616e99a34bb650c
8bf30be75069d6080659de9a28565c048f6cef9b
17c84cb46e33fcd682d5d5d6180162374cb24a34
6ce204eac38723d3a24c7bf148221de933bba54d
d08c6e2a4d0308a7922d7ef3b1b3af45d4096aad
befa41771f9e07f0a95b4a4a0d6b77fd334f4e44
76c31e5f758596509fbab120b8d055bf927ed165
c27bd1718c06eb356a4ea0ab8588ad442d953947
9536923d3f353873e54d96769fbd2e7f867a73e1
60dc0ef674ecbc944e2c236c8a71ce26440cb1a9
8348b71ccd921d0bff21b6f480ecc1e3a5033359
a572c0a748e6f7e04fb56d65139edbece4cb113d
73a3f1bcab1e66206c2de4bf11083fb8ddd5f49c
84ba8062e383c4a4f8f6388d1cfc87328f2a6115
e5d4e1da65564bb8631ecf5f08f0b2960fb0bc78
efe6f961cd2e54aca4385c7fee1c997f7c286c73
eeed226ed110ed40598e60e29b66643012277be7
3b49a7edec1df4f7019b3b872124231197267205
ff99316700799b84e842f819a44db608557bae3e
8be9686d2479a12f986dfce2f792e33ab747ac0f
918ed7bf76267e43863205e0d61a949c301f367b
09bf97923224fea7f3633648b64867a934d627f2
df67ad625b9ef1c7400f3573df8ac36ab9f56260
c118ebc98233eb1383f1adfeea4fa8e59f635088
39542e234b5215dc267b425f8315747849c5e520

There appears to have been a major refactor of
drivers/net/ethernet/mellanox/mlx5/core/en_tc.c going on for the past
several kernel releases.

It is still not known if the fix is at the tip of that refactor or if it
will be isolated and easily backportable.

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

Title:
  [jammy mlx5] Slow outbound N/S TCP connections for instances on
  gateways

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Charmed OpenStack on Jammy.

  Hardware offloaded instances that reside on the hypervisor which is
  also the active OVN gateway for their network have degraded
  connectivity.

  $ time wget --debug -O /dev/null http://nova.clouds.archive.ubuntu.com/ubuntu/
  Setting --output-document (outputdocument) to /dev/null
  DEBUG output created by Wget 1.21.2 on linux-gnu.

  Reading HSTS entries from /home/ubuntu/.wget-hsts
  URI encoding = ‘UTF-8’
  --2022-08-25 07:16:54--  http://nova.clouds.archive.ubuntu.com/ubuntu/
  Resolving nova.clouds.archive.ubuntu.com (nova.clouds.archive.ubuntu.com)... 
91.189.91.121, 185.125.190.38, 185.125.190.41, ...
  Caching nova.clouds.archive.ubuntu.com => 91.189.91.121 185.125.190.38 
185.125.190.41 91.189.91.122 2001:67c:1562::29 2620:2d:4000:1::1b 
2620:2d:4000:1::18 2001:67c:1562::26
  Connecting to nova.clouds.archive.ubuntu.com 
(nova.clouds.archive.ubuntu.com)|91.189.91.121|:80... connected.
  Created socket 4.
  Releasing 0x55ef05654490 (new refcount 1).

  ---request begin---
  GET /ubuntu/ HTTP/1.1
  Host: nova.clouds.archive.ubuntu.com
  User-Agent: Wget/1.21.2
  Accept: */*
  Accept-Encoding: identity
  Connection: Keep-Alive

  ---request end---
  HTTP request sent, awaiting response... 
  ---response begin---
  HTTP/1.1 200 OK
  Date: Thu, 25 Aug 2022 07:16:54 GMT
  Server: Apache/2.4.29 (Ubuntu)
  Vary: Accept-Encoding
  Content-Length: 1779
  Keep-Alive: timeout=5, max=100
  Connection: Keep-Alive
  Content-Type: text/html;charset=UTF-8

  ---response end---
  200 OK
  Registered socket 4 for persistent reuse.
  URI content encoding = ‘UTF-8’
  Length: 1779 (1.7K) [text/html]
  Saving to: ‘/dev/null’

  /dev/null
  
100%[>]
  1.74K  --.-KB/sin 0.07s

  2022-08-25 07:16:59 (24.3 KB/s) - ‘/dev/null’ saved [1779/1779]

  
  real  0m5.591s
  user  0m0.000s
  sys   0m0.005s

  $ sudo tcpdump -nevi ens3 not port 22
  07:16:54.017265 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 
(0x0800), length 74: (tos 0x0, ttl 64, id 50207, offset 0, flags [DF], proto 
TCP (6), length 60)
  10.42.1.8.43060 > 91.189.91.121.80: Flags [S], cksum 0xc296 (incorrect -> 
0x4190), seq 2905559525, win 62314, options [mss 8902,sackOK,TS val 4081686695 
ecr 0,nop,wscale 7], length 0
  07:16:54.091378 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 
(0x0800

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

2022-08-25 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 1987670

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

Title:
  Add support for AMD PMF

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Some upcoming platforms support for AMD-PMF.

  This will enable ACPI platform profiles and some automatic transitions.
  The first 11 patches are queued up for 6.1 and also available in an immutable 
branch.

  https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-
  drivers-x86.git/log/?h=platform-drivers-x86-amd-pmf

  Can you please merge these to OEM-6.0?

  We will have 3-5 more patches targeted later as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987670/+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 1987670] [NEW] Add support for AMD PMF

2022-08-25 Thread Mario Limonciello
Public bug reported:

Some upcoming platforms support for AMD-PMF.

This will enable ACPI platform profiles and some automatic transitions.
The first 11 patches are queued up for 6.1 and also available in an immutable 
branch.

https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-
drivers-x86.git/log/?h=platform-drivers-x86-amd-pmf

Can you please merge these to OEM-6.0?

We will have 3-5 more patches targeted later as well.

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


** Tags: originate-from-1978727

** Tags added: originate-from-1978727

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

Title:
  Add support for AMD PMF

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Some upcoming platforms support for AMD-PMF.

  This will enable ACPI platform profiles and some automatic transitions.
  The first 11 patches are queued up for 6.1 and also available in an immutable 
branch.

  https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-
  drivers-x86.git/log/?h=platform-drivers-x86-amd-pmf

  Can you please merge these to OEM-6.0?

  We will have 3-5 more patches targeted later as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987670/+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 1986520] Re: There are libvirtd errors in /var/log/syslog when powering on or off virtual machine in Ubuntu 22.04 LTS

2022-08-25 Thread conie chang
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  There are libvirtd errors in /var/log/syslog when powering on or off
  virtual machine in Ubuntu 22.04 LTS

Status in libvirt package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hardware Configuration:
  Server MTM: Bona POR SE450
  OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso)
  BMC Version: 1.40 (Build ID: USX311E)
  UEFI Version: 1.03 (Build ID: CME105C)
  LXPM Version: 3.19 (Build ID: CML103A)
  CPU: Xeon Silver 4314 16C 135W 2.4GHz
  DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; 
HMA84GR7CJR4N-XNT4
  DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2
  IO Config:
  RAID: Intel VROC (VMD NVMe RAID) Premium
  SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 
Ethernet Adapter
  SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter
  Storage:
  DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 
Trayless SSD
  PSU1: CFFv4 AC 1100W (Delta) 110V
  PSU2: CFFv4 AC 1100W (Delta) 110V
  M/B build version: PASS5 MB

  Steps:
  1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk.
  2. Install KVM features and desktop GUI.
  3. Run "apt upgrade" to update packages.
  4. Create a namespace on BPS DIMM App Direct Not Interleaved mode.
  5. Run "virt-manager" then install Windows Server 2022 on the namespace.
  6. Reboot Guest OS and Host OS to check if there is any unexpected error in 
system logs. (=> failed, there are libvirtd errors in /var/log/syslog when 
booting into OS or powering on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.] )

  Expected behaviors:
  There are no any unexpected errors in system logs.

  Current behaviors:
  There are libvirtd errors in /var/log/syslog when booting into OS or powering 
on/off the virtual machine:
  libvirtd: internal error: A field data length violates the resource length 
boundary.
  libvirtd: message repeated 3 times: [internal error: A field data length 
violates the resource length boundary.]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220816)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894
   Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Lenovo ThinkEdge SE450
  Package: linux (not installed)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  RfKill:
   
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: Lenovo
  dmi.bios.version: CME105F-1.23
  dmi.board.asset.tag: none
  dmi.board.name: 7D8TCTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLenovo:bvrCME105F-1.23:bd08/08/2022:br1.23:efr1.40:svnLenovo:pnThinkEdgeSE450:pvr05:rvnLenovo:rn7D8TCTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7D8TCTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkEdge SE450
  dmi.product.sku: 7D8TCTO1WW
  dmi.product.version: 05
  dmi.sys.vendor: Lenovo

T

[Kernel-packages] [Bug 1983436] Re: BUG:soft lockup - CPU#0 stuck for 36s! rcu_core_si kernel/rcu/tree.c:2807

2022-08-25 Thread saltf1sh
@sdeziel,thanks for your prompt. Today I have reproduced the bug in kernel 
version 5.4 and kernel version 5.15 respectively. The experiment proves that 
the bug still exists.
I use this command:
"./syz-execprog -executor=./syz-executor -repeat=0 -procs=8 -cover=0 
-threaded=0 -collide=0 ./SyzReproRcu".
Crash can still be triggered in the kernel.
You can download CReproducerRcu.c. Locally through "gcc CReproducerRcu.c -o 
CReproducerRcu" gets the file CReproducerRcu. Run "./CReproducerRcu" locally 
and wait for about one minute. You can see the message "rcu: INFO: rcu_sched 
self-detected stall on CPU". I'm not sure if this is a bug.
You can use vm_5dot4.log and vm_5dot15.log to view each step of my operation in 
QEMU. According to stack trace, the problem may be rcu_sched_clock_irq? I'm not 
sure which file in the kernel corresponds to the bug.
==
The following are links related to kernel 5.4:
Description: rcu: INFO: rcu_sched self-detected stall on CPU
Kernel version: 5.4
Kernel config: 
https://github.com/LancyRiver/SoftLockup/blob/master/rcu_core_si/v5.4/.config
C reproducer: 
https://github.com/LancyRiver/SoftLockup/blob/master/rcu_core_si/v5.4/CReproducerRcu.c
Crash log: 
https://github.com/LancyRiver/SoftLockup/blob/master/rcu_core_si/v5.4/CrashLog.txt
Syz repro: 
https://github.com/LancyRiver/SoftLockup/blob/master/rcu_core_si/v5.4/SyzReproRcu
Vm.log: 
https://github.com/LancyRiver/SoftLockup/blob/master/rcu_core_si/v5.4/vm_5dot4.log

Crash log:
[   65.129421] audit: type=1400 audit(1661428172.369:15): avc:  denied  { 
execmem } for  pid=360 comm="CReproducerRcu" 
scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 
tcontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tclass=process 
permissive=1
[   79.840127] hrtimer: interrupt took 14052 ns
[  104.359596] rcu: INFO: rcu_sched self-detected stall on CPU
[  104.368030] rcu: 0-: (20995 ticks this GP) 
idle=eee/1/0x4004 softirq=3077/3077 fqs=4694 
[  104.373374]  (t=21000 jiffies g=4473 q=220481)
[  104.375926] NMI backtrace for cpu 0
[  104.378133] CPU: 0 PID: 12886 Comm: CReproducerRcu Not tainted 5.4.192 #1
[  104.381887] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.13.0-1ubuntu1.1 04/01/2014
[  104.387042] Call Trace:
[  104.388557]  
[  104.390225]  dump_stack+0x95/0xc8
[  104.392112]  nmi_cpu_backtrace.cold+0x55/0x94
[  104.394758]  ? lapic_can_unplug_cpu+0x70/0x70
[  104.397442]  nmi_trigger_cpumask_backtrace+0x15a/0x1b0
[  104.400354]  rcu_dump_cpu_stacks+0x15d/0x1a7
[  104.402749]  rcu_sched_clock_irq.cold+0x4c8/0x90b
[  104.405510]  ? hrtimer_run_queues+0x1d/0x310
[  104.407876]  update_process_times+0x24/0x60
[  104.410279]  tick_sched_handle+0x10f/0x150
[  104.412622]  tick_sched_timer+0x41/0x120
[  104.414804]  __hrtimer_run_queues+0x308/0x7c0
[  104.417218]  ? tick_sched_do_timer+0x160/0x160
[  104.419750]  ? enqueue_hrtimer+0x230/0x230
[  104.422074]  ? kvm_clock_get_cycles+0xd/0x10
[  104.424437]  ? ktime_get_update_offsets_now+0x17d/0x250
[  104.427363]  hrtimer_interrupt+0x2c9/0x6c0
[  104.429693]  smp_apic_timer_interrupt+0xd4/0x380
[  104.432226]  apic_timer_interrupt+0xf/0x20
[  104.434517] RIP: 0010:clocksource_watchdog+0xa/0x8b0
[  104.437264] Code: 48 c7 c7 48 ed 37 bd e8 34 11 2e 00 e9 74 ff ff ff 66 66 
2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 41 57 41 56 41 55 41 54 55 53 <48> 83 ec 
50 e8 9d 30 0b 00 48 c7 c7 40 7d ca bd e8 91 e5 22 02 8b
[  104.447427] RSP: 0018:88806d209d88 EFLAGS: 0206 ORIG_RAX: 
ff13
[  104.451622] RAX: b9e945c0 RBX: 88806d209e80 RCX: b9e7fe19
[  104.455952] RDX: 0100 RSI: b9e945c0 RDI: bdca7d80
[  104.460191] RBP: 0100 R08: 0001 R09: ed100da45aae
[  104.464058] R10: ed100da45aad R11: 88806d22d56f R12: bdca7d80
[  104.467990] R13: fffcaa29 R14: fffcaa29 R15: 88806d22d540
[  104.471933]  ? apic_timer_interrupt+0xa/0x20
[  104.474346]  ? __clocksource_unstable+0x170/0x170
[  104.476956]  ? call_timer_fn+0x39/0x2b0
[  104.479082]  ? __clocksource_unstable+0x170/0x170
[  104.481732]  call_timer_fn+0x45/0x2b0
[  104.483781]  ? __clocksource_unstable+0x170/0x170
[  104.486381]  ? __clocksource_unstable+0x170/0x170
[  104.488998]  run_timer_softirq+0x53b/0x1230
[  104.491289]  ? call_timer_fn+0x2b0/0x2b0
[  104.493461]  ? apic_timer_interrupt+0xa/0x20
[  104.495802]  __do_softirq+0x17c/0x627
[  104.497954]  irq_exit+0x114/0x140
[  104.499798]  smp_apic_timer_interrupt+0xde/0x380
[  104.502340]  apic_timer_interrupt+0xf/0x20
[  104.504607]  
==
The following are links related to kernel 5.15:
Description: rcu: INFO: rcu_sched self-detected stall on CPU
Kernel version: hwe-5.15
Kernel config: 
https://github.com/LancyRiver/SoftLockup/blob/master/rcu_core_si/v5.15/.config
C reproducer: 
https://github.com/LancyRiver/SoftLock

[Kernel-packages] [Bug 1983436] Re: BUG:soft lockup - CPU#0 stuck for 36s! rcu_core_si kernel/rcu/tree.c:2807

2022-08-25 Thread saltf1sh
@sdeziel,thanks for your prompt. Today I have reproduced the bug in kernel 
version 5.4 and kernel version 5.15 respectively. The experiment proves that 
the bug still exists.
I use this command:
"./syz-execprog -executor=./syz-executor -repeat=0 -procs=8 -cover=0 
-threaded=0 -collide=0 ./SyzReproRcu".
Crash can still be triggered in the kernel.
You can download CReproducerRcu.c. Locally through "gcc CReproducerRcu.c -o 
CReproducerRcu" gets the file CReproducerRcu. Run "./CReproducerRcu" locally 
and wait for about one minute. You can see the message "rcu: INFO: rcu_sched 
self-detected stall on CPU". I'm not sure if this is a bug.
You can use vm_5dot4.log and vm_5dot15.log to view each step of my operation in 
QEMU. According to stack trace, the problem may be rcu_sched_clock_irq? I'm not 
sure which file in the kernel corresponds to the bug.
==
The following are links related to kernel 5.4:
Description: rcu: INFO: rcu_sched self-detected stall on CPU
Kernel version: 5.4
Kernel config: 
https://github.com/LancyRiver/SoftLockup/blob/master/rcu_core_si/v5.4/.config
C reproducer: 
https://github.com/LancyRiver/SoftLockup/blob/master/rcu_core_si/v5.4/CReproducerRcu.c
Crash log: 
https://github.com/LancyRiver/SoftLockup/blob/master/rcu_core_si/v5.4/CrashLog.txt
Syz repro: 
https://github.com/LancyRiver/SoftLockup/blob/master/rcu_core_si/v5.4/SyzReproRcu
Vm.log: 
https://github.com/LancyRiver/SoftLockup/blob/master/rcu_core_si/v5.4/vm_5dot4.log

Crash log:
[   65.129421] audit: type=1400 audit(1661428172.369:15): avc:  denied  { 
execmem } for  pid=360 comm="CReproducerRcu" 
scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 
tcontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tclass=process 
permissive=1
[   79.840127] hrtimer: interrupt took 14052 ns
[  104.359596] rcu: INFO: rcu_sched self-detected stall on CPU
[  104.368030] rcu: 0-: (20995 ticks this GP) 
idle=eee/1/0x4004 softirq=3077/3077 fqs=4694 
[  104.373374]  (t=21000 jiffies g=4473 q=220481)
[  104.375926] NMI backtrace for cpu 0
[  104.378133] CPU: 0 PID: 12886 Comm: CReproducerRcu Not tainted 5.4.192 #1
[  104.381887] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.13.0-1ubuntu1.1 04/01/2014
[  104.387042] Call Trace:
[  104.388557]  
[  104.390225]  dump_stack+0x95/0xc8
[  104.392112]  nmi_cpu_backtrace.cold+0x55/0x94
[  104.394758]  ? lapic_can_unplug_cpu+0x70/0x70
[  104.397442]  nmi_trigger_cpumask_backtrace+0x15a/0x1b0
[  104.400354]  rcu_dump_cpu_stacks+0x15d/0x1a7
[  104.402749]  rcu_sched_clock_irq.cold+0x4c8/0x90b
[  104.405510]  ? hrtimer_run_queues+0x1d/0x310
[  104.407876]  update_process_times+0x24/0x60
[  104.410279]  tick_sched_handle+0x10f/0x150
[  104.412622]  tick_sched_timer+0x41/0x120
[  104.414804]  __hrtimer_run_queues+0x308/0x7c0
[  104.417218]  ? tick_sched_do_timer+0x160/0x160
[  104.419750]  ? enqueue_hrtimer+0x230/0x230
[  104.422074]  ? kvm_clock_get_cycles+0xd/0x10
[  104.424437]  ? ktime_get_update_offsets_now+0x17d/0x250
[  104.427363]  hrtimer_interrupt+0x2c9/0x6c0
[  104.429693]  smp_apic_timer_interrupt+0xd4/0x380
[  104.432226]  apic_timer_interrupt+0xf/0x20
[  104.434517] RIP: 0010:clocksource_watchdog+0xa/0x8b0
[  104.437264] Code: 48 c7 c7 48 ed 37 bd e8 34 11 2e 00 e9 74 ff ff ff 66 66 
2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 41 57 41 56 41 55 41 54 55 53 <48> 83 ec 
50 e8 9d 30 0b 00 48 c7 c7 40 7d ca bd e8 91 e5 22 02 8b
[  104.447427] RSP: 0018:88806d209d88 EFLAGS: 0206 ORIG_RAX: 
ff13
[  104.451622] RAX: b9e945c0 RBX: 88806d209e80 RCX: b9e7fe19
[  104.455952] RDX: 0100 RSI: b9e945c0 RDI: bdca7d80
[  104.460191] RBP: 0100 R08: 0001 R09: ed100da45aae
[  104.464058] R10: ed100da45aad R11: 88806d22d56f R12: bdca7d80
[  104.467990] R13: fffcaa29 R14: fffcaa29 R15: 88806d22d540
[  104.471933]  ? apic_timer_interrupt+0xa/0x20
[  104.474346]  ? __clocksource_unstable+0x170/0x170
[  104.476956]  ? call_timer_fn+0x39/0x2b0
[  104.479082]  ? __clocksource_unstable+0x170/0x170
[  104.481732]  call_timer_fn+0x45/0x2b0
[  104.483781]  ? __clocksource_unstable+0x170/0x170
[  104.486381]  ? __clocksource_unstable+0x170/0x170
[  104.488998]  run_timer_softirq+0x53b/0x1230
[  104.491289]  ? call_timer_fn+0x2b0/0x2b0
[  104.493461]  ? apic_timer_interrupt+0xa/0x20
[  104.495802]  __do_softirq+0x17c/0x627
[  104.497954]  irq_exit+0x114/0x140
[  104.499798]  smp_apic_timer_interrupt+0xde/0x380
[  104.502340]  apic_timer_interrupt+0xf/0x20
[  104.504607]  
==
The following are links related to kernel 5.15:
Description: rcu: INFO: rcu_sched self-detected stall on CPU
Kernel version: hwe-5.15
Kernel config: 
https://github.com/LancyRiver/SoftLockup/blob/master/rcu_core_si/v5.15/.config
C reproducer: 
https://github.com/LancyRiver/SoftLock

[Kernel-packages] [Bug 1983436] Re: BUG:soft lockup - CPU#0 stuck for 36s! rcu_core_si kernel/rcu/tree.c:2807

2022-08-25 Thread saltf1sh
@sdeziel,thanks for your prompt. Today I have reproduced the bug in kernel 
version 5.4 and kernel version 5.15 respectively. The experiment proves that 
the bug still exists.
I use this command:
"./syz-execprog -executor=./syz-executor -repeat=0 -procs=8 -cover=0 
-threaded=0 -collide=0 ./SyzReproRcu".
Crash can still be triggered in the kernel.
You can download CReproducerRcu.c. Locally through "gcc CReproducerRcu.c -o 
CReproducerRcu" gets the file CReproducerRcu. Run "./CReproducerRcu" locally 
and wait for about one minute. You can see the message "rcu: INFO: rcu_sched 
self-detected stall on CPU". I'm not sure if this is a bug.
You can use vm_5dot4.log and vm_5dot15.log to view each step of my operation in 
QEMU. According to stack trace, the problem may be rcu_sched_clock_irq? I'm not 
sure which file in the kernel corresponds to the bug.
==
The following are links related to kernel 5.4:
Description: rcu: INFO: rcu_sched self-detected stall on CPU
Kernel version: 5.4
Kernel config: 
https://github.com/LancyRiver/SoftLockup/blob/master/rcu_core_si/v5.4/.config
C reproducer: 
https://github.com/LancyRiver/SoftLockup/blob/master/rcu_core_si/v5.4/CReproducerRcu.c
Crash log: 
https://github.com/LancyRiver/SoftLockup/blob/master/rcu_core_si/v5.4/CrashLog.txt
Syz repro: 
https://github.com/LancyRiver/SoftLockup/blob/master/rcu_core_si/v5.4/SyzReproRcu
Vm.log: 
https://github.com/LancyRiver/SoftLockup/blob/master/rcu_core_si/v5.4/vm_5dot4.log

Crash log:
[   65.129421] audit: type=1400 audit(1661428172.369:15): avc:  denied  { 
execmem } for  pid=360 comm="CReproducerRcu" 
scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 
tcontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tclass=process 
permissive=1
[   79.840127] hrtimer: interrupt took 14052 ns
[  104.359596] rcu: INFO: rcu_sched self-detected stall on CPU
[  104.368030] rcu: 0-: (20995 ticks this GP) 
idle=eee/1/0x4004 softirq=3077/3077 fqs=4694 
[  104.373374]  (t=21000 jiffies g=4473 q=220481)
[  104.375926] NMI backtrace for cpu 0
[  104.378133] CPU: 0 PID: 12886 Comm: CReproducerRcu Not tainted 5.4.192 #1
[  104.381887] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.13.0-1ubuntu1.1 04/01/2014
[  104.387042] Call Trace:
[  104.388557]  
[  104.390225]  dump_stack+0x95/0xc8
[  104.392112]  nmi_cpu_backtrace.cold+0x55/0x94
[  104.394758]  ? lapic_can_unplug_cpu+0x70/0x70
[  104.397442]  nmi_trigger_cpumask_backtrace+0x15a/0x1b0
[  104.400354]  rcu_dump_cpu_stacks+0x15d/0x1a7
[  104.402749]  rcu_sched_clock_irq.cold+0x4c8/0x90b
[  104.405510]  ? hrtimer_run_queues+0x1d/0x310
[  104.407876]  update_process_times+0x24/0x60
[  104.410279]  tick_sched_handle+0x10f/0x150
[  104.412622]  tick_sched_timer+0x41/0x120
[  104.414804]  __hrtimer_run_queues+0x308/0x7c0
[  104.417218]  ? tick_sched_do_timer+0x160/0x160
[  104.419750]  ? enqueue_hrtimer+0x230/0x230
[  104.422074]  ? kvm_clock_get_cycles+0xd/0x10
[  104.424437]  ? ktime_get_update_offsets_now+0x17d/0x250
[  104.427363]  hrtimer_interrupt+0x2c9/0x6c0
[  104.429693]  smp_apic_timer_interrupt+0xd4/0x380
[  104.432226]  apic_timer_interrupt+0xf/0x20
[  104.434517] RIP: 0010:clocksource_watchdog+0xa/0x8b0
[  104.437264] Code: 48 c7 c7 48 ed 37 bd e8 34 11 2e 00 e9 74 ff ff ff 66 66 
2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 41 57 41 56 41 55 41 54 55 53 <48> 83 ec 
50 e8 9d 30 0b 00 48 c7 c7 40 7d ca bd e8 91 e5 22 02 8b
[  104.447427] RSP: 0018:88806d209d88 EFLAGS: 0206 ORIG_RAX: 
ff13
[  104.451622] RAX: b9e945c0 RBX: 88806d209e80 RCX: b9e7fe19
[  104.455952] RDX: 0100 RSI: b9e945c0 RDI: bdca7d80
[  104.460191] RBP: 0100 R08: 0001 R09: ed100da45aae
[  104.464058] R10: ed100da45aad R11: 88806d22d56f R12: bdca7d80
[  104.467990] R13: fffcaa29 R14: fffcaa29 R15: 88806d22d540
[  104.471933]  ? apic_timer_interrupt+0xa/0x20
[  104.474346]  ? __clocksource_unstable+0x170/0x170
[  104.476956]  ? call_timer_fn+0x39/0x2b0
[  104.479082]  ? __clocksource_unstable+0x170/0x170
[  104.481732]  call_timer_fn+0x45/0x2b0
[  104.483781]  ? __clocksource_unstable+0x170/0x170
[  104.486381]  ? __clocksource_unstable+0x170/0x170
[  104.488998]  run_timer_softirq+0x53b/0x1230
[  104.491289]  ? call_timer_fn+0x2b0/0x2b0
[  104.493461]  ? apic_timer_interrupt+0xa/0x20
[  104.495802]  __do_softirq+0x17c/0x627
[  104.497954]  irq_exit+0x114/0x140
[  104.499798]  smp_apic_timer_interrupt+0xde/0x380
[  104.502340]  apic_timer_interrupt+0xf/0x20
[  104.504607]  
==
The following are links related to kernel 5.15:
Description: rcu: INFO: rcu_sched self-detected stall on CPU
Kernel version: hwe-5.15
Kernel config: 
https://github.com/LancyRiver/SoftLockup/blob/master/rcu_core_si/v5.15/.config
C reproducer: 
https://github.com/LancyRiver/SoftLock

[Kernel-packages] [Bug 1985901] Re: kernel hang when connecting monitor

2022-08-25 Thread Stefan Bader
Dropping from Jammy for now. Thanks Mario.

** Changed in: linux (Ubuntu Jammy)
   Status: Fix Committed => Triaged

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

Title:
  kernel hang when connecting monitor

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Triaged
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  When I connected the ThinkVision 24i monitor on ThinkPad L14, we found
  below issue.

  Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ...
   kernel:[   77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! 
[Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - 
CPU#0 stuck for 50s! [Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm 
cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr 
intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul 
ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e 
snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd 
btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi 
bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg 
videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev 
snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic 
serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram 
platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof 
firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 
snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore 
amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev 
lp parport ip_tables x_tables
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  autofs4 btrfs blake2b_generic 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu iommu_v2 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm 
sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core 
realtek wmi video
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg 
Tainted: G L5.14.0-1048-oem #55-Ubuntu
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 
4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 
0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 
3b af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 
08 00 00 45 8b 6d 00  12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 
c5 66 90
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 
EFLAGS: 0282
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 
9ab39d00 RCX: 
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX:  RSI: 
6741 RDI: 9ab39d00
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 
9ab39d00 R09: 1140
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10:  R11: 
9ab389c9c400 R12: 6741
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13:  R14: 
0008 R15: 9ab389c9d400
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS:  7f9d97924a40() 
GS:9ab466e0() knlGS:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 
00010c878000 CR4: 00750ef0
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  amdgpu_device_rreg+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_cgs_read_register+0x14/0x20 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dm_read_reg_func+0x3e/0xa0 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_dm_dmub_reg_read+0x23/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_dcn20_get_inbox1_rptr+0x20/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_srv_wait_for_idle.part.0+0x26/0x60 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dmub_srv_wait_for_idle+0x17/0x20 
[amdgpu]
  

[Kernel-packages] [Bug 1976533] Comment bridged from LTC Bugzilla

2022-08-25 Thread bugproxy
--- Comment From boris.m...@de.ibm.com 2022-08-25 08:34 EDT---
Required patch landed in focal (20.04), therefore we can close this bug.
Thanks everybody for your work!

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

Title:
  [UBUNTU 20.04] s390/DASD: Fix data corruption for ESE devices

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  Description:   s390/dasd: Fix data corruption for ESE devices

  Symptom:   Filesystem errors and data inconsistency.
  Problem:   Wrong tracks are formatted or the same track is formatted 
twice.

 1. For ESE devices we get an error when accessing an 
unformatted
 track. The handling of this error will return zero data for 
read
 requests and format the track on demand before writing to it. 
To
 do this the code needs to distinguish between read and write
 requests. This is done with data from the blocklayer request. A
 pointer to the blocklayer request is stored in the CQR.

 If there is an error on the device an ERP request is built to 
do
 error recovery. While the ERP request is mostly a copy of the
 original CQR the pointer to the blocklayer request is not 
copied
 to not accidentally pass it back to the blocklayer without
 cleanup.

 This leads to the error that during ESE handling after an ERP
 request was built it is not possible to determine the IO
 direction. This leads to the formatting of a track for read
 requests which might in turn lead to data corruption.

 2. When using alias devices a track might be accessed by
 multiple requests simultaneously and there is a race window 
that
 a track gets formatted twice resulting in data loss.

  Solution:  1. Return the callback data of the original request in case
 there are ERP requests build on top of it and thus determine 
the
 correct IO direction.
 2. Prevent the double format by remembering the amount of
 formatted tracks when starting a request and comparing this
 number before actually formatting a track on the fly. If the
 number has changed there is a chance that the current track was
 finally formatted in between. As a result do not format the
 track and restart the current IO to check.
  Reproduction:  Prepare an ESE DASD device using dasdfmt and fdasd. Install any
 filesystem on the prepared partitions and issue regular I/O
 using dd or any other tool while Alias DASD devices are set
 online as well.

  Upstream-ID:   5b53a405e4658580e1faf7c217db3f55a21ba849
 71f3871657370dbbaf942a1c758f64e49a36c70f

  Problem-ID:198418

  Preventive:yes

  Date:  2022-06-01
  Author:hoepp...@linux.ibm.com
  Component: kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1976533/+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 1962373] Re: Cannot resume from suspend

2022-08-25 Thread Rob Owens
This problem is fixed in Ubuntu 22.04.

$ cat /proc/acpi/wakeup 
Device  S-state   Status   Sysfs node
GPP1  S4*disabled
GP17  S4*enabled   pci::00:08.1
GPP0  S4*disabled

$ uname -a
Linux pavilion 5.15.0-46-generic #49-Ubuntu SMP Thu Aug 4 18:03:25 UTC 2022 
x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -rd
Description:Ubuntu 22.04.1 LTS
Release:22.04

$ lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root 
Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne IOMMU
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host 
Bridge
00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP 
Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host 
Bridge
00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP 
Bridge
00:02.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP 
Bridge
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host 
Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP 
Bridge to Bus
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 51)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: 
Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: 
Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: 
Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: 
Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: 
Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: 
Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: 
Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: 
Function 7
01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI 
Express Card Reader (rev 01)
02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8852AE 802.11ax 
PCIe Wireless Network Adapter
03:00.0 Non-Volatile memory controller: Sandisk Corp WD Blue SN550 NVMe SSD 
(rev 01)
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Lucienne (rev c2)
04:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High 
Definition Audio Controller
04:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 10h-1fh) Platform Security Processor
04:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 
3.1
04:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 
3.1
04:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] 
Raven/Raven2/FireFlight/Renoir Audio Processor (rev 01)
04:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 
10h-1fh) HD Audio Controller

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

Title:
  Cannot resume from suspend

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

Bug description:
  New HP Pavilion 15z-eh100

  I am able to suspend via the power menu or by closing the laptop lid.
  However, I am unable to resume from suspend.  Opening the lid does not
  do it.  Hitting the power button does not do it.  I have hit every key
  on the keyboard as well as clicked the touchpad.  The power button has
  a slowly pulsing light, indicating it is suspended.  Pressing and
  holding the power button for several seconds, causing the laptop to
  power off, is the only way I have found to get out of this state.

  $ cat /proc/acpi/wakeup 
  DeviceS-state   Status   Sysfs node
  GPP1S4*disabled
  GP17S4*enabled   pci::00:08.1
  GPP0S4*disabled

  $ uname -a
  Linux pavilion 5.13.0-30-generic #33~20.04.1-Ubuntu SMP Mon Feb 7 14:25:10 
UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  $ lspci
  00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Root Complex
  00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Renoir IOMMU
  00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy 
Host Bridge
  00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
  00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy 
Host Bridge
  00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
  00:02.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
  00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy 
Host Bridge
  00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe 
GPP Bridge to Bus
  

[Kernel-packages] [Bug 1976533] Re: [UBUNTU 20.04] s390/DASD: Fix data corruption for ESE devices

2022-08-25 Thread Frank Heimes
Now Fix Released for focal according to LP#1979566.

** Changed in: linux (Ubuntu Focal)
   Status: Fix Committed => Fix Released

** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

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

Title:
  [UBUNTU 20.04] s390/DASD: Fix data corruption for ESE devices

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  Description:   s390/dasd: Fix data corruption for ESE devices

  Symptom:   Filesystem errors and data inconsistency.
  Problem:   Wrong tracks are formatted or the same track is formatted 
twice.

 1. For ESE devices we get an error when accessing an 
unformatted
 track. The handling of this error will return zero data for 
read
 requests and format the track on demand before writing to it. 
To
 do this the code needs to distinguish between read and write
 requests. This is done with data from the blocklayer request. A
 pointer to the blocklayer request is stored in the CQR.

 If there is an error on the device an ERP request is built to 
do
 error recovery. While the ERP request is mostly a copy of the
 original CQR the pointer to the blocklayer request is not 
copied
 to not accidentally pass it back to the blocklayer without
 cleanup.

 This leads to the error that during ESE handling after an ERP
 request was built it is not possible to determine the IO
 direction. This leads to the formatting of a track for read
 requests which might in turn lead to data corruption.

 2. When using alias devices a track might be accessed by
 multiple requests simultaneously and there is a race window 
that
 a track gets formatted twice resulting in data loss.

  Solution:  1. Return the callback data of the original request in case
 there are ERP requests build on top of it and thus determine 
the
 correct IO direction.
 2. Prevent the double format by remembering the amount of
 formatted tracks when starting a request and comparing this
 number before actually formatting a track on the fly. If the
 number has changed there is a chance that the current track was
 finally formatted in between. As a result do not format the
 track and restart the current IO to check.
  Reproduction:  Prepare an ESE DASD device using dasdfmt and fdasd. Install any
 filesystem on the prepared partitions and issue regular I/O
 using dd or any other tool while Alias DASD devices are set
 online as well.

  Upstream-ID:   5b53a405e4658580e1faf7c217db3f55a21ba849
 71f3871657370dbbaf942a1c758f64e49a36c70f

  Problem-ID:198418

  Preventive:yes

  Date:  2022-06-01
  Author:hoepp...@linux.ibm.com
  Component: kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1976533/+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 1951055] Re: Reinstate ACPI S5 for reboot

2022-08-25 Thread Anthony Wong
** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

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

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

Title:
  Reinstate ACPI S5 for reboot

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

Bug description:
  [Impact]
  On some systems, Intel WiFi device may stop working after reboot.

  [Fix]
  Use ACPI S5 for reboot.

  [Test]
  2000 times of reboot stress, and Intel WiFi continues work on affected
  system.

  [Where problems could occur]
  There was a bug introduced by this patch, but the user didn't want to
  find the root cause. Since we have more control on Ubuntu kernel, we'll
  fix the root cause properly this time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1951055/+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 1976184] Re: Linux PV device frontends vulnerable to attacks by backends

2022-08-25 Thread Timo Aaltonen
oem-5.14 will be eol soon

** Changed in: linux-oem-5.14 (Ubuntu)
   Status: New => Won't 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/1976184

Title:
  Linux PV device frontends vulnerable to attacks by backends

Status in linux-aws package in Ubuntu:
  New
Status in linux-aws-5.13 package in Ubuntu:
  New
Status in linux-aws-5.4 package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-azure-4.15 package in Ubuntu:
  New
Status in linux-azure-5.13 package in Ubuntu:
  New
Status in linux-azure-5.4 package in Ubuntu:
  New
Status in linux-bluefield package in Ubuntu:
  New
Status in linux-dell300x package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp-4.15 package in Ubuntu:
  New
Status in linux-gcp-5.13 package in Ubuntu:
  New
Status in linux-gcp-5.4 package in Ubuntu:
  New
Status in linux-gke package in Ubuntu:
  New
Status in linux-gke-5.4 package in Ubuntu:
  New
Status in linux-gkeop package in Ubuntu:
  New
Status in linux-gkeop-5.4 package in Ubuntu:
  New
Status in linux-hwe-5.13 package in Ubuntu:
  New
Status in linux-hwe-5.4 package in Ubuntu:
  New
Status in linux-ibm package in Ubuntu:
  New
Status in linux-ibm-5.4 package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux-oem-5.14 package in Ubuntu:
  Won't Fix
Status in linux-oracle package in Ubuntu:
  New
Status in linux-oracle-5.13 package in Ubuntu:
  New
Status in linux-oracle-5.4 package in Ubuntu:
  New
Status in linux-raspi package in Ubuntu:
  New
Status in linux-raspi-5.4 package in Ubuntu:
  New
Status in linux-riscv package in Ubuntu:
  New
Status in linux-snapdragon package in Ubuntu:
  New

Bug description:
  The packages listed above are vulnerable to the CVEs below in at least
  one Ubuntu release, as stated in the Ubuntu CVE Tracker, except for
  linux-azure-4.15, linux-dell300x, linux-gcp-4.15 and linux-snapdragon,
  that are only vulnerable to CVE-2022-23041.

  Please release fixed packages.

  Xen released a security advisory on March 10.

  (I was informed by the security team that it does not track security
  issues via Launchpad bugs, but in the Ubuntu CVE Tracker. However, the
  issue is unpatched for over 2.5 months and marked as needed for these
  combinations of source package and Ubuntu version in the Tracker, and
  therefore I am filing this bug.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1976184/+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 1976181] Re: CVE-2021-28711 and CVE-2021-28712

2022-08-25 Thread Timo Aaltonen
oem-5.14 will be eol soon

** Changed in: linux-oem-5.14 (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  CVE-2021-28711 and CVE-2021-28712

Status in linux-oem-5.14 package in Ubuntu:
  Won't Fix

Bug description:
  The version in Focal is vulnerable to CVE-2021-28711 and
  CVE-2021-28712.

  Please release patched versions.

  Xen released a security advisory on December 20:
  https://xenbits.xen.org/xsa/advisory-391.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1976181/+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 1980621] Re: [SRU][OEM-5.14/Jammy/OEM-5.17][PATCH 0/1] Fix blank screen on Thinkpad ADL 4K+ panel

2022-08-25 Thread Timo Aaltonen
** Changed in: linux-oem-5.14 (Ubuntu)
   Status: In Progress => Won't Fix

** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Status: In Progress => Won't Fix

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

Title:
  [SRU][OEM-5.14/Jammy/OEM-5.17][PATCH 0/1] Fix blank screen on Thinkpad
  ADL 4K+ panel

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

Bug description:
  [Impact]
  Set screen off on ThinkPad P1G5 with 4k+ panel.
  The screen will never be back.

  [Fix]
  It's a upstream kernel regression.
  And reverted by upstream.

  [Test]
  Verified on hardware, screen on/off 20 times OK.

  [Where problems could occur]
  Low risk, it reverts a regression and may break i915 driver.

  On 5.14-oem and Jammy kernel, This commit was claimed to backport
  commit 73867c8709b5 ("drm/i915/display: Remove check for low voltage sku for 
max dp source rate")
  But it's not kind of it.
  So revert it instead.

  On 5.17 kernel, revert it by upstream commit.

  Unstable kernel already got it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1980621/+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 1954773] Re: New fix for jack detection after resume on CS8409 sound driver

2022-08-25 Thread Timo Aaltonen
** Changed in: linux-oem-5.14 (Ubuntu)
   Status: New => Invalid

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

Title:
  New fix for jack detection after resume on CS8409 sound driver

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux-oem-5.14 source package in Impish:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  On some platforms with Cirrus CS8409 audio codec, the external headset will 
fail to be detected after system resume.

  [Fix]
  Cirrus released a new fix commit 65cc4ad62a9e ('ALSA: hda/cs8409: Set PMSG_ON 
earlier inside cs8409 driver'). It sets the power_state to ON before the 
unsolicited event arrives to make sure the jack detection can be invoked after 
resume.

  [Test]
  Plug-in an external headset in front headset port, suspend/resume the system 
then check whether the headset function works as expected.

  [Where problem could occur]
  Low. It only affect the platforms with Cirrus codec CS8409 which used to have 
problem.

  == Original Bug Description ==

  [Summary] System can't detect external headset after suspend

  [Steps to reproduce]
  1. install manifest and boot into OS
  2. plug-in an external headset in front headset port
  3. un-plug external headset
  4. suspend system
  5. resume system from suspend
  6. plug-in an external headset

  [Expected result]
  System could detect external headset after suspend

  [Actual result]
  System can't detect external headset after suspend

  [Failure rate]
  3/3

  [Additional information]
  CID: 202110-29567
  SKU: DLPV-SFF-DVT-C1
  Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-davos-adl+X152
  system-manufacturer: Dell Inc.
  system-product-name: Vostro 3710
  bios-version: 0.13.73
  CPU: 12th Gen Intel(R) Core(TM) i7-12700 (20x)
  GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:4680] (rev 0c)
  kernel-version: 5.13.0-1019-oem

  [Stage]
  Issue reported and logs collected right after it happened

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1954773/+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 1960287] Re: Blutooth mouse loses connection with the 1022 several times after login, not with the 1005.

2022-08-25 Thread Timo Aaltonen
oel-5.14 will be eol soon


** Changed in: linux-oem-5.14 (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Blutooth mouse loses connection with the 1022 several times after
  login, not with the 1005.

Status in linux-oem-5.14 package in Ubuntu:
  Won't Fix

Bug description:
  To be more precise, after logging in I normally press a button on the
  mouse, then the Blutooth icon shows me the connection as active in the
  bar. After 5-10 seconds it is gone again. The mouse no longer reacts.
  It takes about 20 seconds, then I have a connection again for about
  5-10 seconds.

  The whole thing happens 2-4 times. After that it remains stable.
  I will set the timeout to 0.

  I did not notice this under 1005

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1960287/+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 1972990] Re: Focal update: upstream stable patchset 2022-05-11

2022-08-25 Thread Timo Aaltonen
** Changed in: linux-oem-5.14 (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Focal update: upstream stable patchset 2022-05-11

Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Released

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 2022-05-11
 from git://git.kernel.org/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1972990/+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 1955632] Re: [i915] TV connected by VGA is flickering or going black

2022-08-25 Thread Timo Aaltonen
oem-5.14 will be eol soon

** Changed in: linux-oem-5.14 (Ubuntu)
   Status: New => Won't Fix

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

Title:
  [i915] TV connected by VGA is flickering or going black

Status in linux-oem-5.14 package in Ubuntu:
  Won't Fix

Bug description:
  I've been using Ubuntu 20.04 for a long time now and have had no problems. 
Then suddenly the screen started flickering. I tried PCLinuxOS but the screen 
just goes black. I found, on Ubuntu, installing brightness-controller and 
putting the screen brightness down below half way and the setting to Clear Blue 
Sky helps quite a lot but is hard to see. It still flickers once in awhile. And 
I cannot create a file in /sys/class/backlight to make the change permanent on 
boot. The only major change I can think of is setting LivePatch up that could 
have caused the flickering.
  Thank you, I hope you find the fix as no Linux distros will work on my 
ThinkCentre desktop PC.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.14.0-1011.11-oem 5.14.17
  Uname: Linux 5.14.0-1011-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 23 01:52:31 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8821CU, 5.4.1, 5.11.0-43-generic, x86_64: installed
   rtl8821CU, 5.4.1, 5.14.0-1011-oem, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics 
Controller [17aa:3083]
  InstallationDate: Installed on 2021-10-16 (68 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 3227K45
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1011-oem 
root=UUID=e7536889-191e-4640-ba6f-6e940cb65228 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2018
  dmi.bios.release: 0.6
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT9CAUS
  dmi.board.asset.tag: 640688
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 PRO
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT9CAUS:bd12/11/2018:br0.6:svnLENOVO:pn3227K45:pvrThinkCentreM92P:rvnLENOVO:rnMAHOBAY:rvr0B98401PRO:cvnLENOVO:ct3:cvrNone:skuLENOVO_MT_3227:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 3227K45
  dmi.product.sku: LENOVO_MT_3227
  dmi.product.version: ThinkCentre M92P
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1955632/+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 1969892] Re: Focal update: upstream stable patchset 2022-04-22

2022-08-25 Thread Timo Aaltonen
** Changed in: linux-oem-5.14 (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Focal update: upstream stable patchset 2022-04-22

Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Released

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 2022-04-22
 from git://git.kernel.org/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1969892/+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 1980340] Re: Focal update: upstream stable patchset 2022-06-30

2022-08-25 Thread Timo Aaltonen
** Changed in: linux-oem-5.14 (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Focal update: upstream stable patchset 2022-06-30

Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Released

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 2022-06-30
 from git://git.kernel.org/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1980340/+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 1977835] Re: Focal update: upstream stable patchset 2022-06-07

2022-08-25 Thread Timo Aaltonen
** Changed in: linux-oem-5.14 (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Focal update: upstream stable patchset 2022-06-07

Status in HWE Next:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Released

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 2022-06-07
 from git://git.kernel.org/

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1977835/+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 1981773] Re: Make cm32181 sensor work after system suspend

2022-08-25 Thread Timo Aaltonen
** Changed in: linux-oem-5.14 (Ubuntu)
   Status: New => Invalid

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

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

Title:
  Make cm32181 sensor work after system suspend

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  cm32181 ambient light sensor stops working after system suspend.

  [Fix]
  Add PM support for cm32181 so it can work after system suspend.

  [Test]
  The sysfs in_illuminance_input continues to change after system suspend.

  [Where problems could occur]
  This changeset is limited to a specific device, and it already lacks PM
  support - so the worst case is that it stops working after resume like
  it always has been.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1981773/+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 1952568] Re: AMD GPU kernel driver unload error

2022-08-25 Thread Timo Aaltonen
oem-5.14 will be eol soon

** Changed in: linux-oem-5.14 (Ubuntu)
   Status: New => Won't Fix

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

Title:
  AMD GPU kernel driver unload error

Status in linux-oem-5.14 package in Ubuntu:
  Won't Fix

Bug description:
  
ubuntu20.04でカーネルを5.14.0-1005から5.14.0-1007に更新した後、次のコマンドでドライバーをアンロードすると、コマンドが強制的に終了し、ドライバーをアンロードできなくなります。
  5.14.0-1005で問題なくアンロードできます

  sudo modprob -s -r amdgpu

  ドライバの情報ではlsmod 
  - 
  sudoのはlsmod | grepをamdgpu 
  amdgpu 7049216 -1 
  iommu_v2 24576 1 amdgpu 
  gpu_sched 36864 1 amdgpu 
  drm_ttm_helper 16384 1 amdgpu 
  TTM 73728 2 amdgpu、drm_ttm_ヘルパー
  258048は1 amdgpu drm_kms_helper 
  DRM 557056 6 gpu_sched、drm_kms_ヘルパー、amdgpu 、drm_ttm_ヘルパー、ttm 
  i2c_algo_bit 16384 2 igb、amdgpu 
  -

  ProblemType:Bug 
  DistroRelease:Ubuntu 20.04 
  Package:linux-modules- 5.14.0- 1007-oem 5.14.0-1007.7 
  ProcVersionSign ature :Ubuntu 5.14.0-1007.7-oem 5.14.14 
  Uname:Linux 5.14.0-1007-oem x86_64 
  ApportVersion:2.20.11-0ubuntu27 。21
  アーキテクチャ:amd64 
  CasperMD5CheckR esult:skip 
  CurrentDesktop:LXQt 
  Date:Mon Nov 29 13:46:48 2021 
  InstallationDate:Installed on 2019-07-24(858日前)
  InstallationMedia:Ubuntu-Server 19.04 "Disco Dingo" -Release amd64( 
20190416.1)
  SourcePackage:linux-oem-5.14 
  UpgradeStatus:2020-05-02にフォーカルにアップグレードされました(575日前)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1952568/+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 1984011] Re: [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal

2022-08-25 Thread Stefan Bader
** Changed in: linux (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal

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

Bug description:
  [Impact]

  fNIC driver controls print messages based on the flag fnic_log_level. 
shost_printk is not controlled via this flag. This issue is resolved by using 
some of the print macros that have been defined in fnic. This has negligible 
impact.
  The resid was being set irrespective of whether we saw an underflow or not. 
It needs to be set only when we see an underflow. The impact here is negligible.
  When we don't receive link events, we could go into a loop before sending fw 
reset. The patch for the issue resolves this, and we break out of the loop.
  Prior to checking the remote port, fnic driver must check if the io_req is 
valid. If not, there could be a crash. The patch resolves this issue.

  [Fix]
  The following patches need to be pulled from upstream to update the fnic 
driver to 1.6.0.53:

  https://marc.info/?l=linux-scsi&m=160591061813369&w=2
  https://marc.info/?l=linux-scsi&m=160592183315837&w=2
  https://marc.info/?l=linux-scsi&m=160592283315997&w=2
  https://marc.info/?l=linux-scsi&m=160592363016122&w=2
  https://marc.info/?l=linux-scsi&m=160592616516616&w=2

  Here's a description of each issue:

  1. https://marc.info/?l=linux-scsi&m=160591061813369&w=2

  FNIC_FCS_DBG print is controlled by fnic_log_level flag. Replace
  shost_printk in fnic_fip_handler_timer with this print so that it can
  be controlled.

  2. https://marc.info/?l=linux-scsi&m=160592183315837&w=2

  When fnic is in TRANS ETH state, and when there are no link events, we
  must not loop before sending fw reset.

  3. https://marc.info/?l=linux-scsi&m=160592283315997&w=2

  FNIC_MAIN_DBG print is controlled by fnic_log_level flag. Replace
  shost_printk in fnic_handle_link with this print so that it can be
  controlled.

  4. https://marc.info/?l=linux-scsi&m=160592363016122&w=2

  Fix to set scsi_set_resid() only if FCPIO_ICMND_CMPL_RESID_UNDER is
  set.

  5. https://marc.info/?l=linux-scsi&m=160592616516616&w=2

  Check for a valid io_req before we check other data.

  [Test Plan]

  Runnings IOs with multiple link flaps would be a good test case to
  validate all the patches above. It is suggested to run these IOs with
  a data integrity check. We do this as a standard practice.

  [Where problems could occur]

  The print messages are innocuous. It is not expected to run into any issues.
  Problems could occur with storage arrays that have a non-standard response.
  If the sanity test fails, there could be issues in the scsi midlayer or fnic 
driver.

  All the patches present low regression risk.

  [Other Info]
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/fnic_cisco_ver3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984011/+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 1978986] Re: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance

2022-08-25 Thread Stefan Bader
** Changed in: linux-oem-5.14 (Ubuntu Jammy)
   Importance: Undecided => Medium

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

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

Title:
  [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-
  average luminance

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Confirmed
Status in linux-oem-5.14 source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  In Progress

Bug description:
  [Impact]
  The brightness is not changed obviously during 200 to 255 on AMD
  or 400 to 512 on Intel..

  [Fix]
  Read HDR meta to detect the max and min luminance.
  max_cll defines the content light luminance for individual pixel.
  max_fall defines frame-average level luminance.
  Use max_fall value instead of max_cll as a limit for brightness control.

  [Test]
  Verified on AMD Cezanne, Barcelo, Rembrandt and Intel ADL, also on LCD panel 
and OLED panel. The brightness is changed more obivously on OLED panel, and
  no affect on LCD panel.

  [Where problems could occur]
  Low risk, It may cause the max brightness can't be set.

  All 3 patches are in drm-misc tree.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1978986/+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 1985901] Re: kernel hang when connecting monitor

2022-08-25 Thread Stefan Bader
** Changed in: linux (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

Title:
  kernel hang when connecting monitor

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  When I connected the ThinkVision 24i monitor on ThinkPad L14, we found
  below issue.

  Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ...
   kernel:[   77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! 
[Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - 
CPU#0 stuck for 50s! [Xorg:1829]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm 
cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr 
intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul 
ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e 
snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd 
btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi 
bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg 
videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev 
snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic 
serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram 
platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof 
firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 
snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore 
amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev 
lp parport ip_tables x_tables
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  autofs4 btrfs blake2b_generic 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu iommu_v2 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm 
sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core 
realtek wmi video
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg 
Tainted: G L5.14.0-1048-oem #55-Ubuntu
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 
4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 
0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 
3b af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 
08 00 00 45 8b 6d 00  12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 
c5 66 90
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 
EFLAGS: 0282
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 
9ab39d00 RCX: 
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX:  RSI: 
6741 RDI: 9ab39d00
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 
9ab39d00 R09: 1140
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10:  R11: 
9ab389c9c400 R12: 6741
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13:  R14: 
0008 R15: 9ab389c9d400
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS:  7f9d97924a40() 
GS:9ab466e0() knlGS:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 
00010c878000 CR4: 00750ef0
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace:
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  amdgpu_device_rreg+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_cgs_read_register+0x14/0x20 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dm_read_reg_func+0x3e/0xa0 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
amdgpu_dm_dmub_reg_read+0x23/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_dcn20_get_inbox1_rptr+0x20/0x30 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  
dmub_srv_wait_for_idle.part.0+0x26/0x60 [amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:  dmub_srv_wait_for_idle+0x17/0x20 
[amdgpu]
  8月 12 17:12:20 u-ThinkPad-L14-Gen-

[Kernel-packages] [Bug 1983498] Re: Jammy: Add OVS Internal Port HW Offload to mlx5 driver

2022-08-25 Thread Stefan Bader
** Changed in: linux (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

Title:
  Jammy: Add OVS Internal Port HW Offload to mlx5 driver

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

Bug description:
  SRU Justification

  [Impact]

  A request has been made, originating from
  https://bugs.launchpad.net/bugs/1980730, to add support for OVS
  internal port offload for the mlx5 driver. This feature takes care of
  certain traffic workloads that are not currently being offloaded to
  the hardware.

  [Test Case]

  Tested by the requester.

  [Where things could go wrong]

  These changes could potentially introduce regressions in behavior of
  the mlx5 driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983498/+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 1987623] [NEW] RM llvm-toolchain-12 from kinetic

2022-08-25 Thread Simon Chopin
Public bug reported:

This package blocks the glibc 2.36 transition due to breakage of
libsanitizer that isn't observed on later versions of LLVM. Plus, it has
already been removed from Debian testing due to this bug:

https://bugs.debian.org/1012193


❯ reverse-depends src:llvm-toolchain-12
Reverse-Recommends
* libmkl-dev [amd64](for libomp-12-dev)
* libmkl-rt [amd64] (for libomp-12-dev)

Reverse-Depends
* libllvmspirvlib12 (for libllvm12)
* libopencl-clang12 (for libclang-cpp12)
* libopencl-clang12 (for libllvm12)
* libpocl2 [amd64 arm64 armhf]
* libpocl2 [amd64 arm64 armhf]
* libpocl2 [amd64 arm64 armhf]
* llvm-spirv-12 (for libllvm12)
* nvidia-cuda-toolkit [amd64 arm64 ppc64el]

❯ reverse-depends -a source src:llvm-toolchain-12
Reverse-Build-Depends
* opencl-clang-12   (for libclang-cpp12-dev)
* opencl-clang-12   (for libclang-12-dev)
* opencl-clang-12   (for llvm-12-dev)
* opencl-clang-12   (for clang-12)
* pocl  (for clang-12)
* pocl  (for libclang-cpp12-dev)
* pocl  (for llvm-12-dev)
* pocl  (for libclang-12-dev)
* spirv-llvm-translator-12  (for llvm-12-dev)
* spirv-llvm-translator-12  (for libclang-12-dev)
* thunderbird   (for llvm-12-dev)
* thunderbird   (for libclang-12-dev)
* thunderbird   (for clang-12)

In the case of libmkl-* and thunderbird, the dependencies are in OR
clauses with later versions of LLVM, so there shouldn't be any breakage.

pocl is fixed in -proposed, and is waiting on AA resolution of
https://bugs.launchpad.net/ubuntu/+source/pocl/+bug/1987621

nvidia-cuda-toolkit has clang-12 as part of a g++-11 | clang-12 | g++-10
| clang-11 | ... clause, with g++-11 the preferred dependency

Finally, I propose to remove src:opencl-clang-12 and src:spirv-llvm-
translator-12, seeing as:

❯ reverse-depends -a source src:opencl-clang-12
No reverse dependencies found

❯ reverse-depends src:opencl-clang-12 
No reverse dependencies found

❯ reverse-depends -a source src:spirv-llvm-translator-12
Reverse-Build-Depends
* opencl-clang-12   (for libllvmspirvlib-12-dev)

❯ reverse-depends src:spirv-llvm-translator-12   
Reverse-Depends
* libopencl-clang12 (for libllvmspirvlib12)

** Affects: llvm-toolchain-12 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: update-excuse

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

Title:
  RM llvm-toolchain-12 from kinetic

Status in llvm-toolchain-12 package in Ubuntu:
  New

Bug description:
  This package blocks the glibc 2.36 transition due to breakage of
  libsanitizer that isn't observed on later versions of LLVM. Plus, it
  has already been removed from Debian testing due to this bug:

  https://bugs.debian.org/1012193


  ❯ reverse-depends src:llvm-toolchain-12
  Reverse-Recommends
  * libmkl-dev [amd64](for libomp-12-dev)
  * libmkl-rt [amd64] (for libomp-12-dev)

  Reverse-Depends
  * libllvmspirvlib12 (for libllvm12)
  * libopencl-clang12 (for libclang-cpp12)
  * libopencl-clang12 (for libllvm12)
  * libpocl2 [amd64 arm64 armhf]
  * libpocl2 [amd64 arm64 armhf]
  * libpocl2 [amd64 arm64 armhf]
  * llvm-spirv-12 (for libllvm12)
  * nvidia-cuda-toolkit [amd64 arm64 ppc64el]

  ❯ reverse-depends -a source src:llvm-toolchain-12
  Reverse-Build-Depends
  * opencl-clang-12   (for libclang-cpp12-dev)
  * opencl-clang-12   (for libclang-12-dev)
  * opencl-clang-12   (for llvm-12-dev)
  * opencl-clang-12   (for clang-12)
  * pocl  (for clang-12)
  * pocl  (for libclang-cpp12-dev)
  * pocl  (for llvm-12-dev)
  * pocl  (for libclang-12-dev)
  * spirv-llvm-translator-12  (for llvm-12-dev)
  * spirv-llvm-translator-12  (for libclang-12-dev)
  * thunderbird   (for llvm-12-dev)
  * thunderbird   (for libclang-12-dev)
  * thunderbird   (for clang-12)

  In the case of libmkl-* and thunderbird, the dependencies are in OR
  clauses with later versions of LLVM, so there shouldn't be any
  breakage.

  pocl is fixed in -proposed, and is waiting on AA resolution of
  https://bugs.launchpad.net/ubuntu/+source/pocl/+bug/1987621

  nvidia-cuda-toolkit has clang-12 as part of a g++-11 | clang-12 |
  g++-10 | clang-11 | ... clause, with g++-11 the preferred dependency

  Finally, I propose to remove src:opencl-clang-12 and src:spirv-llvm-
  translator-12, seeing as:

  ❯ reverse-depends -a source src:opencl-clang-12
  No reverse dependencies found

  ❯ re

[Kernel-packages] [Bug 1973434] Re: massive performance issues since 22.04 upgrade

2022-08-25 Thread Urban Engberg
@c-edward-hamer: It is interesting that you mention the issue with
getting 15 of the same letter while typing. Two days ago I switched to
Wayland (from Xorg) to see if that had any impact. There, I had this
problem constantly and switched back to Xorg as a consequence, where I
don't see this. I believe it must be different symptoms of the same
problem, and it definitely seems kernel-related to me...

I am curious why this problem is not affecting more people and getting a
top priority?

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

Title:
  massive performance issues since 22.04 upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  After upgrading to 22.04 i had to fight with massive performance issues.

  Browsers appeared to hang every other minute, youtube videos being
  laggy and hang in between, applications in a virtualbox VM where slow
  and also hanging every other minute to a level of not being useable.
  On a pretty recent and powerful system just 2 years old.

  I noticed CPU jumps in top, but also somehow thought it could be a graphics 
issue so invested some time installing nvidia drivers properly.
  Also I wondered if it might be the lowlatency kernel I normally use because I 
do audio stuff, and switched to generic. But nothing helped.

  ThenI had the idea it could be a kernel/scheduler issue because the
  system wasn't always slow, but it appeared certain things kept hanging
  when other processed had a lot of cpu for a few seconds.

  So I got a recent mainline kernel, configured it with my last running
  config from 21.10 before the update, made the debs and installed them,
  and now can tell that a mainline kernel 5.17.7 with all the dkms
  modules that i had before which got compiled automatically at
  installation brings back a "normal" performance.

  I can browse the web, run multiple youtube vids at once, even in
  another browser, have thunderbird running, and a virtualbox machine
  open with another browser for some web app testing and everything runs
  fine and smooth, no lagging.

  Not sure yet what the real reason is - either the kernel version, or a
  patch in the ubuntu version, or the 22.04 kernel config so far, or
  some configuration made in 21.10 that isn't good with 22.04 and it's
  kernel anymore.

  I will go ahead tomorrow and see if I can build a vanilla kernel with
  the config from the ubuntu 22.04 kernel and "make oldconfig", then I
  will be able to tell if only the config is making the difference.

  Please let me know of there is anything I should test to further
  analyze this issue, or any ideas I can try to solve it without having
  to run a mainline manually installed kernel.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic 5.15.0.30.33
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  henning6198 F pulseaudio
   /dev/snd/controlC1:  henning6198 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 14 23:02:38 2022
  InstallationDate: Installed on 2020-04-12 (761 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QV00CEGE
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic 
root=/dev/mapper/vgubuntu-root ro
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago)
  dmi.bios.date: 12/06/2021
  dmi.bios.release: 1.42
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET55W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QV00CEGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T08861 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.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET55W(1.42):bd12/06/2021:br1.42:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd:
  dmi.product.family: ThinkPad X1 Extreme 2nd
  dmi.product.name: 20QV00CEGE
  dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd
  dmi.product.version: ThinkPad X1 Extreme 2nd
  dmi.sys.vendor: LENOVO

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


-- 
Mailing list: https://launchpad.net/~kernel

[Kernel-packages] [Bug 1987620] [NEW] kmod v30 missing new modules.builtin.modinfo file

2022-08-25 Thread Lukas Märdian
Public bug reported:

depmod: WARNING: could not open modules.builtin.modinfo at
/tmp/autopkgtest.tKMBKb/autopkgtest_tmp/mkinitramfs_uvT4BW/lib/modules/5.15.0-27-generic:
No such file or directory

https://autopkgtest.ubuntu.com/results/autopkgtest-
kinetic/kinetic/amd64/i/initramfs-tools/20220823_075538_8b7f5@/log.gz

We probably need to install the corresponding linux-modules-* package to
get that file.

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: update-excuse

** Also affects: initramfs-tools (Ubuntu)
   Importance: Undecided
   Status: New

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

** Tags added: update-excuse

** Summary changed:

- kmod missing new modules.builtin.modinfo file
+ kmod v30 missing new modules.builtin.modinfo file

** No longer affects: linux (Ubuntu)

** Description changed:

  depmod: WARNING: could not open modules.builtin.modinfo at
  
/tmp/autopkgtest.tKMBKb/autopkgtest_tmp/mkinitramfs_uvT4BW/lib/modules/5.15.0-27-generic:
  No such file or directory
  
- I think this is probably something that needs to be shipped by the
- kernel package.
+ https://autopkgtest.ubuntu.com/results/autopkgtest-
+ kinetic/kinetic/amd64/i/initramfs-tools/20220823_075538_8b7f5@/log.gz
+ 
+ We probably need to install the corresponding linux-modules-* package to
+ get that file.

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

Title:
  kmod v30 missing new modules.builtin.modinfo file

Status in initramfs-tools package in Ubuntu:
  New
Status in kmod package in Ubuntu:
  New

Bug description:
  depmod: WARNING: could not open modules.builtin.modinfo at
  
/tmp/autopkgtest.tKMBKb/autopkgtest_tmp/mkinitramfs_uvT4BW/lib/modules/5.15.0-27-generic:
  No such file or directory

  https://autopkgtest.ubuntu.com/results/autopkgtest-
  kinetic/kinetic/amd64/i/initramfs-tools/20220823_075538_8b7f5@/log.gz

  We probably need to install the corresponding linux-modules-* package
  to get that file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1987620/+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 1987618] Missing required logs.

2022-08-25 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 1987618

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

Title:
  [jammy mlx5] Slow outbound N/S TCP connections for instances on
  gateways

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Charmed OpenStack on Jammy.

  Hardware offloaded instances that reside on the hypervisor which is
  also the active OVN gateway for their network have degraded
  connectivity.

  $ time wget --debug -O /dev/null http://nova.clouds.archive.ubuntu.com/ubuntu/
  Setting --output-document (outputdocument) to /dev/null
  DEBUG output created by Wget 1.21.2 on linux-gnu.

  Reading HSTS entries from /home/ubuntu/.wget-hsts
  URI encoding = ‘UTF-8’
  --2022-08-25 07:16:54--  http://nova.clouds.archive.ubuntu.com/ubuntu/
  Resolving nova.clouds.archive.ubuntu.com (nova.clouds.archive.ubuntu.com)... 
91.189.91.121, 185.125.190.38, 185.125.190.41, ...
  Caching nova.clouds.archive.ubuntu.com => 91.189.91.121 185.125.190.38 
185.125.190.41 91.189.91.122 2001:67c:1562::29 2620:2d:4000:1::1b 
2620:2d:4000:1::18 2001:67c:1562::26
  Connecting to nova.clouds.archive.ubuntu.com 
(nova.clouds.archive.ubuntu.com)|91.189.91.121|:80... connected.
  Created socket 4.
  Releasing 0x55ef05654490 (new refcount 1).

  ---request begin---
  GET /ubuntu/ HTTP/1.1
  Host: nova.clouds.archive.ubuntu.com
  User-Agent: Wget/1.21.2
  Accept: */*
  Accept-Encoding: identity
  Connection: Keep-Alive

  ---request end---
  HTTP request sent, awaiting response... 
  ---response begin---
  HTTP/1.1 200 OK
  Date: Thu, 25 Aug 2022 07:16:54 GMT
  Server: Apache/2.4.29 (Ubuntu)
  Vary: Accept-Encoding
  Content-Length: 1779
  Keep-Alive: timeout=5, max=100
  Connection: Keep-Alive
  Content-Type: text/html;charset=UTF-8

  ---response end---
  200 OK
  Registered socket 4 for persistent reuse.
  URI content encoding = ‘UTF-8’
  Length: 1779 (1.7K) [text/html]
  Saving to: ‘/dev/null’

  /dev/null
  
100%[>]
  1.74K  --.-KB/sin 0.07s

  2022-08-25 07:16:59 (24.3 KB/s) - ‘/dev/null’ saved [1779/1779]

  
  real  0m5.591s
  user  0m0.000s
  sys   0m0.005s

  $ sudo tcpdump -nevi ens3 not port 22
  07:16:54.017265 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 
(0x0800), length 74: (tos 0x0, ttl 64, id 50207, offset 0, flags [DF], proto 
TCP (6), length 60)
  10.42.1.8.43060 > 91.189.91.121.80: Flags [S], cksum 0xc296 (incorrect -> 
0x4190), seq 2905559525, win 62314, options [mss 8902,sackOK,TS val 4081686695 
ecr 0,nop,wscale 7], length 0
  07:16:54.091378 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 
(0x0800), length 74: (tos 0x0, ttl 58, id 0, offset 0, flags [DF], proto TCP 
(6), length 60)
  91.189.91.121.80 > 10.42.1.8.43060: Flags [S.], cksum 0x809d (correct), 
seq 3404088064, ack 2905559526, win 65160, options [mss 1460,sackOK,TS val 
932285789 ecr 4081686695,nop,wscale 7], length 0
  07:16:54.091402 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 
(0x0800), length 66: (tos 0x0, ttl 64, id 50208, offset 0, flags [DF], proto 
TCP (6), length 52)
  10.42.1.8.43060 > 91.189.91.121.80: Flags [.], cksum 0xc28e (incorrect -> 
0xabc0), ack 1, win 487, options [nop,nop,TS val 4081686770 ecr 932285789], 
length 0
  07:16:54.091512 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 
(0x0800), length 218: (tos 0x0, ttl 64, id 50209, offset 0, flags [DF], proto 
TCP (6), length 204)
  10.42.1.8.43060 > 91.189.91.121.80: Flags [P.], cksum 0xc326 (incorrect 
-> 0x7d0c), seq 1:153, ack 1, win 487, options [nop,nop,TS val 4081686770 ecr 
932285789], length 152: HTTP, length: 152
GET /ubuntu/ HTTP/1.1
Host: nova.clouds.archive.ubuntu.com
User-Agent: Wget/1.21.2
Accept: */*
Accept-Encoding: identity
Connection: Keep-Alive

  07:16:54.166170 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 
(0x0800), length 66: (tos 0x0, ttl 58, id 15660, offset 0, flags [DF], proto 
TCP (6), length 52)
  91.189.91.121.80 > 10.42.1.8.43060: Flags [.], cksum 0xaac7 (correct), 
ack 153, win 508, options [nop,nop,TS val 932285865 ecr 4081686770], length 0
  07:16:59.171924 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 
(0x

[Kernel-packages] [Bug 1973037] Re: llvm-toolchain-13: please backport upstream D115098 for rust

2022-08-25 Thread Launchpad Bug Tracker
This bug was fixed in the package llvm-toolchain-13 -
1:13.0.1-2ubuntu2.1

---
llvm-toolchain-13 (1:13.0.1-2ubuntu2.1) jammy; urgency=medium

  * Backport D115098 for Rust 1.59 (LP: #1973037)
  * d/p/risc/riscv-insn-support.patch: Backport assembler .insn support on 
riscv64
for rustc 1.59.0 (LP: #1973041)

 -- Simon Chopin   Tue, 31 May 2022 10:35:52 +0200

** Changed in: llvm-toolchain-13 (Ubuntu Jammy)
   Status: New => Fix Released

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

Title:
  llvm-toolchain-13: please backport upstream D115098 for rust

Status in llvm-toolchain-13 package in Ubuntu:
  New
Status in llvm-toolchain-13 source package in Jammy:
  Fix Released
Status in llvm-toolchain-13 source package in Kinetic:
  New
Status in llvm-toolchain-13 package in Debian:
  Fix Released

Bug description:
  Imported from Debian bug http://bugs.debian.org/1010150:

  Source: llvm-toolchain-13
  Version: 1:13.0.1-3
  Severity: normal
  Tags: patch upstream
  Control: affects + rustc

  Dear Maintainer,

  Please backport upstream https://reviews.llvm.org/D115098

  It is needed for rust 1.59, otherwise a certain test fails on all
  architectures.

  Thanks,
  X

  -- System Information:
  Debian Release: bookworm/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-security'), (300, 'unstable'), (100, 
'experimental'), (1, 'experimental-debug')
  Architecture: amd64 (x86_64)
  Foreign Architectures: i386

  Kernel: Linux 5.16.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
  Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
  Shell: /bin/sh linked to /bin/dash
  Init: systemd (via /run/systemd/system)
  LSM: AppArmor: enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-13/+bug/1973037/+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 1973041] Re: llvm-toolchain-13: please backport Risc-V .insn directive support

2022-08-25 Thread Launchpad Bug Tracker
This bug was fixed in the package llvm-toolchain-13 -
1:13.0.1-2ubuntu2.1

---
llvm-toolchain-13 (1:13.0.1-2ubuntu2.1) jammy; urgency=medium

  * Backport D115098 for Rust 1.59 (LP: #1973037)
  * d/p/risc/riscv-insn-support.patch: Backport assembler .insn support on 
riscv64
for rustc 1.59.0 (LP: #1973041)

 -- Simon Chopin   Tue, 31 May 2022 10:35:52 +0200

** Changed in: llvm-toolchain-13 (Ubuntu Jammy)
   Status: New => Fix Released

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

Title:
  llvm-toolchain-13: please backport Risc-V .insn directive support

Status in llvm-toolchain-13 package in Ubuntu:
  Fix Committed
Status in llvm-toolchain-13 source package in Jammy:
  Fix Released
Status in llvm-toolchain-13 source package in Kinetic:
  Fix Committed

Bug description:
  See https://github.com/rust-lang/llvm-project/pull/121

  This is required for rustc 1.59, which in turn is required for Firefox
  100 and related tunderbird.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-13/+bug/1973041/+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 1987618] [NEW] [jammy mlx5] Slow outbound N/S TCP connections for instances on gateways

2022-08-25 Thread Frode Nordahl
Public bug reported:

Charmed OpenStack on Jammy.

Hardware offloaded instances that reside on the hypervisor which is also
the active OVN gateway for their network have degraded connectivity.

$ time wget --debug -O /dev/null http://nova.clouds.archive.ubuntu.com/ubuntu/
Setting --output-document (outputdocument) to /dev/null
DEBUG output created by Wget 1.21.2 on linux-gnu.

Reading HSTS entries from /home/ubuntu/.wget-hsts
URI encoding = ‘UTF-8’
--2022-08-25 07:16:54--  http://nova.clouds.archive.ubuntu.com/ubuntu/
Resolving nova.clouds.archive.ubuntu.com (nova.clouds.archive.ubuntu.com)... 
91.189.91.121, 185.125.190.38, 185.125.190.41, ...
Caching nova.clouds.archive.ubuntu.com => 91.189.91.121 185.125.190.38 
185.125.190.41 91.189.91.122 2001:67c:1562::29 2620:2d:4000:1::1b 
2620:2d:4000:1::18 2001:67c:1562::26
Connecting to nova.clouds.archive.ubuntu.com 
(nova.clouds.archive.ubuntu.com)|91.189.91.121|:80... connected.
Created socket 4.
Releasing 0x55ef05654490 (new refcount 1).

---request begin---
GET /ubuntu/ HTTP/1.1
Host: nova.clouds.archive.ubuntu.com
User-Agent: Wget/1.21.2
Accept: */*
Accept-Encoding: identity
Connection: Keep-Alive

---request end---
HTTP request sent, awaiting response... 
---response begin---
HTTP/1.1 200 OK
Date: Thu, 25 Aug 2022 07:16:54 GMT
Server: Apache/2.4.29 (Ubuntu)
Vary: Accept-Encoding
Content-Length: 1779
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html;charset=UTF-8

---response end---
200 OK
Registered socket 4 for persistent reuse.
URI content encoding = ‘UTF-8’
Length: 1779 (1.7K) [text/html]
Saving to: ‘/dev/null’

/dev/null
100%[>]
1.74K  --.-KB/sin 0.07s

2022-08-25 07:16:59 (24.3 KB/s) - ‘/dev/null’ saved [1779/1779]


real0m5.591s
user0m0.000s
sys 0m0.005s

$ sudo tcpdump -nevi ens3 not port 22
07:16:54.017265 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800), 
length 74: (tos 0x0, ttl 64, id 50207, offset 0, flags [DF], proto TCP (6), 
length 60)
10.42.1.8.43060 > 91.189.91.121.80: Flags [S], cksum 0xc296 (incorrect -> 
0x4190), seq 2905559525, win 62314, options [mss 8902,sackOK,TS val 4081686695 
ecr 0,nop,wscale 7], length 0
07:16:54.091378 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 (0x0800), 
length 74: (tos 0x0, ttl 58, id 0, offset 0, flags [DF], proto TCP (6), length 
60)
91.189.91.121.80 > 10.42.1.8.43060: Flags [S.], cksum 0x809d (correct), seq 
3404088064, ack 2905559526, win 65160, options [mss 1460,sackOK,TS val 
932285789 ecr 4081686695,nop,wscale 7], length 0
07:16:54.091402 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800), 
length 66: (tos 0x0, ttl 64, id 50208, offset 0, flags [DF], proto TCP (6), 
length 52)
10.42.1.8.43060 > 91.189.91.121.80: Flags [.], cksum 0xc28e (incorrect -> 
0xabc0), ack 1, win 487, options [nop,nop,TS val 4081686770 ecr 932285789], 
length 0
07:16:54.091512 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800), 
length 218: (tos 0x0, ttl 64, id 50209, offset 0, flags [DF], proto TCP (6), 
length 204)
10.42.1.8.43060 > 91.189.91.121.80: Flags [P.], cksum 0xc326 (incorrect -> 
0x7d0c), seq 1:153, ack 1, win 487, options [nop,nop,TS val 4081686770 ecr 
932285789], length 152: HTTP, length: 152
GET /ubuntu/ HTTP/1.1
Host: nova.clouds.archive.ubuntu.com
User-Agent: Wget/1.21.2
Accept: */*
Accept-Encoding: identity
Connection: Keep-Alive

07:16:54.166170 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 (0x0800), 
length 66: (tos 0x0, ttl 58, id 15660, offset 0, flags [DF], proto TCP (6), 
length 52)
91.189.91.121.80 > 10.42.1.8.43060: Flags [.], cksum 0xaac7 (correct), ack 
153, win 508, options [nop,nop,TS val 932285865 ecr 4081686770], length 0
07:16:59.171924 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 (0x0800), 
length 66: (tos 0x0, ttl 58, id 15669, offset 0, flags [DF], proto TCP (6), 
length 52)
91.189.91.121.80 > 10.42.1.8.43060: Flags [F.], cksum 0x8f61 (correct), seq 
2008, ack 153, win 508, options [nop,nop,TS val 932290871 ecr 4081686770], 
length 0
07:16:59.171956 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 (0x0800), 
length 78: (tos 0x0, ttl 64, id 50210, offset 0, flags [DF], proto TCP (6), 
length 64)
10.42.1.8.43060 > 91.189.91.121.80: Flags [.], cksum 0xc29a (incorrect -> 
0x356e), ack 1, win 487, options [nop,nop,TS val 4081691850 ecr 
932285865,nop,nop,sack 1 {2008:2009}], length 0
07:16:59.531552 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 (0x0800), 
length 1440: (tos 0x0, ttl 58, id 15671, offset 0, flags [DF], proto TCP (6), 
length 1426)
91.189.91.121.80 > 10.42.1.8.43060: Flags [.], cksum 0x0d7c (correct), seq 
1:1375, ack 153, win 508, options [nop,nop,TS val 932291230 ecr 4081691850], 
length 1374: HTTP, length: 1374
HTTP/1.1 200 OK

[Kernel-packages] [Bug 1987200] Re: 22.04 is unstabile

2022-08-25 Thread Timo Kangas
CPU usage is probably more than earlier mentioned. These warnings are
based on IP-communication. They are more or less using laptop useless,
eating CPU capacity and battery. Is this also reason for Akonadi not
working. Looks like that I have to serous consider to go back to
20.4.

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

Title:
  22.04 is unstabile

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded yesterday from 20.04 to 22.05. System came very unstabile, 
especially when I', using a lots of communication application. Typically I have 
Telegram, Skype, Thunderbird and Chromium on all of the time. Especially 
Thunderbird seems to create issues, Communicaton apps will give "no reponse 
from... Force quit or wait" message. Ocationally GUI will freeze. I have seen 
two o/s crashes as well, one when Impress presentation on. (crash when writing 
this report)
  I upgraded yesterday from 20.04 to 22.05. System came very unstabile, 
especially when I', using a lots of communication application. Typically I have 
Telegram, Skype, Thunderbird and Chromium on all of the time. Especially 
Thunderbird seems to create issues, Communicaton apps will give "no reponse 
from... Force quit or wait" message. Ocationally GUI will freeze. I have seen 
two o/s crashes as well, one when Impress presentation on. (crash when writing 
this report)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-46-generic 5.15.0-46.49
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  timo   2219 F pulseaudio
   /dev/snd/controlC0:  timo   2219 F pulseaudio
   /dev/snd/controlC1:  timo   2219 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 21 13:01:46 2022
  HibernationDevice: RESUME=UUID=21e5e306-bb15-4ad7-904f-e7d2f5d39861
  MachineType: HP HP Notebook
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=7da986a5-81ea-4ede-83aa-5c5798c46c56 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-08-20 (0 days ago)
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 15.16
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81DF
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 70.12
  dmi.chassis.asset.tag: 5CG6294Q15
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 70.12
  dmi.modalias: 
dmi:bvnInsyde:bvrF.10:bd05/18/2016:br15.16:efr70.12:svnHP:pnHPNotebook:pvrCNB1:rvnHP:rn81DF:rvrKBCVersion70.12:cvnHP:ct10:cvrChassisVersion:skuY0B49EA#UUW:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: Y0B49EA#UUW
  dmi.product.version: CNB1
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987200/+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