date:20230310

The requested change is now upstream (v6.3-rc1) as

commit 60675225ebeecea248035fd3a0efc82ae9038a98
Author: Srinivas Pandruvada 
Date:   Tue Feb 21 22:45:26 2023 -0800

cpufreq: intel_pstate: Adjust balance_performance EPP for Sapphire
Rapids


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

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

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

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Stefan Bader (smb)

** Description changed:

  [Feature Description]
  Ubuntu uses powersave governor as the default.While the powersave governor 
has much lower power, the performance is lower than +25% for several workloads 
compared to performance governor.
  
  Report is published: www.Phoronix.com showing difference of 37%
  
  The goal here is to keep mean performance delta of powersave governor
  from performance governor around 10% to 12% by running wide variety
  of server workloads. For some bursty workload, this delta can be still
  large, as ramp up of frequency will still lag with powersave governor
  irrespective of EPP setting. The performance governor always requests
  maximum frequency.
  
  Based on experiments, EPP of 0x00, 0x10, 0x20, the performance delta for
  powersave governor is around 12%. But the EPP 0x20 has 18% lower average
  power.
  
  Also experiments are done by raising intel_pstate sysfs min_perf_pct as
  high as 50%. This didn't bring in any additional improvements compared
  to just changing EPP.
  
  Target Kernel: 6.3
  Target Release: 22.04 (5.15 kernel)
  
  [HW/SW Information]
  Sapphire Rapids
  
  [Business Justification]
  Performance Improvements
  
  Upstream: Merged 6.3
- Commit ID: To be added
+ Commit ID: 60675225ebeecea248035fd3a0efc82ae9038a98

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

Title:
  cpufreq: intel_pstate: Update Balance performance EPP for Sapphire
  Rapids

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  In Progress

Bug description:
  [Feature Description]
  Ubuntu uses powersave governor as the default.While the powersave governor 
has much lower power, the performance is lower than +25% for several workloads 
compared to performance governor.

  Report is published: www.Phoronix.com showing difference of 37%

  The goal here is to keep mean performance delta of powersave governor
  from performance governor around 10% to 12% by running wide variety
  of server workloads. For some bursty workload, this delta can be still
  large, as ramp up of frequency will still lag with powersave governor
  irrespective of EPP setting. The performance governor always requests
  maximum frequency.

  Based on experiments, EPP of 0x00, 0x10, 0x20, the performance delta for
  powersave governor is around 12%. But the EPP 0x20 has 18% lower average
  power.

  Also experiments are done by raising intel_pstate sysfs min_perf_pct as
  high as 50%. This didn't bring in any additional improvements compared
  to just changing EPP.

  Target Kernel: 6.3
  Target Release: 22.04 (5.15 kernel)

  [HW/SW Information]
  Sapphire Rapids

  [Business Justification]
  Performance Improvements

  Upstream: Merged 6.3
  Commit ID: 60675225ebeecea248035fd3a0efc82ae9038a98

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/2008519/+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 1837543] Re: crypto_user02 in crypto from ubuntu_ltp failed

2023-03-10 Thread Po-Hsu Lin

** Tags added: sru-20230227

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

Title:
  crypto_user02 in crypto from ubuntu_ltp failed

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-aws source package in Bionic:
  Confirmed

Bug description:
  This is a new test, test will fail with:

  <<>>
  tag=crypto_user02 stime=1563881396
  cmdline="crypto_user02"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
  crypto_user02.c:59: INFO: Starting crypto_user larval deletion test.  May 
crash buggy kernels.
  crypto_user02.c:91: BROK: unexpected error from tst_crypto_del_alg(): EBUSY

  Summary:
  passed   0
  failed   0
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=2 corefile=no
  cutime=0 cstime=0
  <<>>

  
  Nothing interesting in syslog:
  Jul 23 11:29:20 amaura systemd[1]: Started Session 1 of user ubuntu.
  Jul 23 11:29:56 amaura kernel: [  619.646330] LTP: starting crypto_user02
  Jul 23 11:30:23 amaura kernel: [  646.554403] cfg80211: Loading compiled-in 
X.509 certificates for regulatory database

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

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-21-generic 5.0.0-21.22
  ProcVersionSignature: User Name 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 23 11:19 seq
   crw-rw 1 root audio 116, 33 Jul 23 11:19 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Jul 23 11:30:15 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-21-generic N/A
   linux-backports-modules-5.0.0-21-generic  N/A
   linux-firmware1.178.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 
  dmi.board.name: S1200RP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G62254-407
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: S1200RP
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837543/+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 2008519] Re: cpufreq: intel_pstate: Update Balance performance EPP for Sapphire Rapids

** Also affects: linux (Ubuntu Lunar)
   Importance: Undecided
   Status: Incomplete

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

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

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

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

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

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

Title:
  cpufreq: intel_pstate: Update Balance performance EPP for Sapphire
  Rapids

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  In Progress
Status in linux source package in Lunar:
  In Progress

Bug description:
  [Feature Description]
  Ubuntu uses powersave governor as the default.While the powersave governor 
has much lower power, the performance is lower than +25% for several workloads 
compared to performance governor.

  Report is published: www.Phoronix.com showing difference of 37%

  The goal here is to keep mean performance delta of powersave governor
  from performance governor around 10% to 12% by running wide variety
  of server workloads. For some bursty workload, this delta can be still
  large, as ramp up of frequency will still lag with powersave governor
  irrespective of EPP setting. The performance governor always requests
  maximum frequency.

  Based on experiments, EPP of 0x00, 0x10, 0x20, the performance delta for
  powersave governor is around 12%. But the EPP 0x20 has 18% lower average
  power.

  Also experiments are done by raising intel_pstate sysfs min_perf_pct as
  high as 50%. This didn't bring in any additional improvements compared
  to just changing EPP.

  Target Kernel: 6.3
  Target Release: 22.04 (5.15 kernel)

  [HW/SW Information]
  Sapphire Rapids

  [Business Justification]
  Performance Improvements

  Upstream: Merged 6.3
  Commit ID: 60675225ebeecea248035fd3a0efc82ae9038a98

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/2008519/+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 2009594] Re: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE)

2023-03-10 Thread DUFOUR Olivier

#
# The tested workaround
# 

Current workaround on ovn-chassis with is to override 
systemd-networkd-wait-online.service to extend the timeout, here to 4 minutes :
(The 2 lines of ExecStart are mandatory, this is not a typo)

```
juju run --model openstack --app ovn-chassis \
"sudo mkdir /etc/systemd/system/systemd-networkd-wait-online.service.d
sudo tee 
/etc/systemd/system/systemd-networkd-wait-online.service.d/override.conf  
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Mar 07 05:24:56 nova-1 kernel: task:kworker/0:1 state:D stack:0 pid:  
 19 ppid: 2 flags:0x4000
  Mar 07 05:24:56 nova-1 kernel: Workqueue: events work_for_cpu_fn
  Mar 07 05:24:56 nova-1 kernel: Call Trace:
  Mar 07 05:24:56 nova-1 kernel:  
  Mar 07 05:24:56 nova-1 kernel:  __schedule+0x257/0x5d0
  Mar 07 05:24:56 nova-1 kernel:  schedule+0x68/0x110
  Mar 07 05:24:56 nova-1 kernel:  schedule_preempt_disabled+0x15/0x30
  Mar 07 05:24:56 nova-1 kernel:  __mutex_lock.constprop.0+0x4f1/0x750
  Mar 07 05:24:56 nova-1 kernel:  __mutex_lock_slowpath+0x13/0x20
  Mar 07 05:24:56 nova-1 kernel:  mutex_lock+0x3e/0x50
  Mar 07 05:24:56 nova-1 kernel:  mlx5_register_device+0x1c/0xb0 [mlx5_core]
  Mar 07 05:24:56 nova-1 kernel:  mlx5_init_one+0xe4/0x110 [mlx5_core]
  Mar 07 05:24:56 nova-1 kernel:  probe_one+0xcb/0x120 [mlx5_core]
  Mar 07 05:24:56 nova-1 kernel:  local_pci_probe+0x4b/0x90
  Mar 07 05:24:56 nova-1 kernel:  work_for_cpu_fn+0x1a/0x30
  Mar 07 05:24:56 nova-1 kernel:  process_one_work+0x21f/0x400
  Mar 07 05:24:56 nova-1 kernel:  worker_thread+0x200/0x3f0
  Mar 07 05:24:56 nova-1 kernel:  ? rescuer_thread+0x3a0/0x3a0
  Mar 07 05:24:56 nova-1 kernel:  kthread+0xee/0x120
  Mar 07 05:24:56 nova-1 kernel:  ? kthread_complete_and_exit+0x20/0x20
  Mar 07 05:24:56 nova-1 kernel:  ret_from_fork+0x22/0x30
  Mar 07 05:24:56 nova-1 kernel:  

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ovn-chassis/+bug/2009594/+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 2009594] Re: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE)

2023-03-10 Thread DUFOUR Olivier

After more investigations, I've found the root cause that triggers the
issue.

#
# The TL,DR:
#
With many VFs to initialise, systemd-networkd-wait-online.service's timeout of
2 minutes is reached.
Meaning services like Nova, Neutron and OVN/OVS will start while the kernel is
still creating and activating VFs.
systemd-networkd-wait-online.service needs to be overrided to increase the
default timeout to something like 5 or 10 minutes.

#
# The lenghty explanation:
#
When looking at the global logs of the servers, I noticed all failing boots on
servers had one thing in common.
Systemd-networkd-wait-online.service was timing out after spending more than 2
minutes.
On success boots, this error would not be seen. And this is interesting because
systemd waits for network this service to succeed before starting other
services after the network target.

When allocating 24 VFs on 2 interfaces, it still worked most of the time. But
after inspection, it appears it was getting pretty close to the 2 minutes limit.
In the attached file systemd-networkd-wait-24VFs.txt we can see the network
initialisation is fairly inconsistent and vary a lot in term of timing.

After testing again at 32 VFs, I could see frequently the network taking longer
than 2 minutes to be set up and all remaining services on the host were being
started while the kernel was still working on VFs.
I decided to override systemd-networkd-wait-online service to extend the
default timeout to 4 minutes.

Here is the test on the same server with 32 VFs :
```
# before override in systemd unit
2min 127ms systemd-networkd-wait-online.service --> timed out
--> has the kernel failing

# reboot after override
2min 33.617s systemd-networkd-wait-online.service
--> works fine

1min 55.140s systemd-networkd-wait-online.service
--> works fine
```

Although the kernel is an issue as well, I think it seriously needs to
be considered, from ovn-chassis' charm point of view, to extend the
default timeout on systemd-networkd-wait-online.service, especially
since probably other softwares depending on network connectivity can
probably into error or other unknown bugs.

And this is failing with only the initialisation of 64 VFs in total. In
scenarios where current network cards can handle 1000 VFs on a single
port or having many network cards, the initialisation of VFs can take a
while. May be having a configuration option to choose the timeout value
for systemd-networkd-wait-online.service could be useful.

** Changed in: charm-ovn-chassis
Status: Invalid => New

** Attachment added: "systemd-networkd-wait-24VFs.txt"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009594/+attachment/5653427/+files/systemd-networkd-wait-24VFs.txt

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

Title:
Mlx5 kworker blocked Kernel 5.19 (Jammy HWE)

Status in charm-ovn-chassis:
New
Status in linux package in Ubuntu:
Confirmed

Bug description:
This is seen on particular with :
* Charmed Openstack with Jammy Yoga
* 5.19.0-35-generic (linux-generic-hwe-22.04/jammy-updates)
* Mellanox Connectx-6 card with mlx5_core module being used
* SR-IOV is being used with VF-LAG for the use of OVN hardware offloading

The servers enter into very high load (around 75~100) quickly during the boot
with all process relying on network communication with the Mellanox network
card being stuck or extremely slow.
Kernel logs are being displayed about kworkers being blocked for more than
120 seconds

The number of SR-IOV devices configured both from the firmware and the kernel
seems to have a serious correlation with the likeliness of this bug to occur.
Having enabled more VF seems to hugely increase the risk for this bug to
arise.

This does not happen systematically at every boot, but with 32 VFs on each
PF, it occurs about 40% of the time.
To recover the server, a cold reboot is required.

Look at a quick sample of the trace, this seems to involve directly
the mlx5 driver within the kernel :

Mar 07 05:24:56 nova-1 kernel: INFO: task kworker/0:1:19 blocked for more
than 120 seconds.
Mar 07 05:24:56 nova-1 kernel: Tainted: P OE
5.19.0-35-generic #36~22.04.1-Ubuntu
Mar 07 05:24:56 nova-1 kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Mar 07 05:24:56 nova-1 kernel: task:kworker/0:1 state:D stack:0 pid:
19 ppid: 2 flags:0x4000
Mar 07 05:24:56 nova-1 kernel: Workqueue: events work_for_cpu_fn
Mar 07 05:24:56 nova-1 kernel: Call Trace:
Mar 07 05:24:56 nova-1 kernel:
Mar 07 05:24:56 nova-1 kernel: __schedule+0x257/0x5d0
Mar 07 05:24:56 nova-1 kernel: schedule+0x68/0x110
Mar 07 05:24:56 nova-1 kernel: schedule_preempt_disabled+0x15/0x30
Mar 07 05:24:56 nova-1 kernel: __mutex_lock.constprop.0+0x4f1/0x750
Mar 07

[Kernel-packages] [Bug 2008519] Re: cpufreq: intel_pstate: Update Balance performance EPP for Sapphire Rapids

** Description changed:

+ [SRU Justification]
+ 
+ == Impact ==
+ See original description. The goal is to adjust the behavior of the balanced 
governor for certain Xeon CPUs (those are CPUs rather seen in servers so there 
should be no impact on laptop users). While the initial request was Jammy/5.15 
only we should do this to Kinetic and Lunar as well so the experience is the 
same regardless of release.
+ 
+ == Fix ==
+ This picks one change from v6.3-rc1 which tweaks the intel_idle driver for a 
specific CPU model.
+ 
+ == Test case ==
+ 
+ 
+ == Regression Potential ==
+ The change modifies how quickly CPUs scale up (and probably down) depending 
on workload. Power usage unlikely is of that much concern in server space. 
Maybe increased heat would be observed.
+ 
+ == Original description ==
+ 
  [Feature Description]
  Ubuntu uses powersave governor as the default.While the powersave governor 
has much lower power, the performance is lower than +25% for several workloads 
compared to performance governor.
  
  Report is published: www.Phoronix.com showing difference of 37%
  
  The goal here is to keep mean performance delta of powersave governor
  from performance governor around 10% to 12% by running wide variety
  of server workloads. For some bursty workload, this delta can be still
  large, as ramp up of frequency will still lag with powersave governor
  irrespective of EPP setting. The performance governor always requests
  maximum frequency.
  
  Based on experiments, EPP of 0x00, 0x10, 0x20, the performance delta for
  powersave governor is around 12%. But the EPP 0x20 has 18% lower average
  power.
  
  Also experiments are done by raising intel_pstate sysfs min_perf_pct as
  high as 50%. This didn't bring in any additional improvements compared
  to just changing EPP.
  
  Target Kernel: 6.3
  Target Release: 22.04 (5.15 kernel)
  
  [HW/SW Information]
  Sapphire Rapids
  
  [Business Justification]
  Performance Improvements
  
  Upstream: Merged 6.3
  Commit ID: 60675225ebeecea248035fd3a0efc82ae9038a98

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

Title:
  cpufreq: intel_pstate: Update Balance performance EPP for Sapphire
  Rapids

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  In Progress
Status in linux source package in Lunar:
  In Progress

Bug description:
  [SRU Justification]

  == Impact ==
  See original description. The goal is to adjust the behavior of the balanced 
governor for certain Xeon CPUs (those are CPUs rather seen in servers so there 
should be no impact on laptop users). While the initial request was Jammy/5.15 
only we should do this to Kinetic and Lunar as well so the experience is the 
same regardless of release.

  == Fix ==
  This picks one change from v6.3-rc1 which tweaks the intel_idle driver for a 
specific CPU model.

  == Test case ==
  

  == Regression Potential ==
  The change modifies how quickly CPUs scale up (and probably down) depending 
on workload. Power usage unlikely is of that much concern in server space. 
Maybe increased heat would be observed.

  == Original description ==

  [Feature Description]
  Ubuntu uses powersave governor as the default.While the powersave governor 
has much lower power, the performance is lower than +25% for several workloads 
compared to performance governor.

  Report is published: www.Phoronix.com showing difference of 37%

  The goal here is to keep mean performance delta of powersave governor
  from performance governor around 10% to 12% by running wide variety
  of server workloads. For some bursty workload, this delta can be still
  large, as ramp up of frequency will still lag with powersave governor
  irrespective of EPP setting. The performance governor always requests
  maximum frequency.

  Based on experiments, EPP of 0x00, 0x10, 0x20, the performance delta for
  powersave governor is around 12%. But the EPP 0x20 has 18% lower average
  power.

  Also experiments are done by raising intel_pstate sysfs min_perf_pct as
  high as 50%. This didn't bring in any additional improvements compared
  to just changing EPP.

  Target Kernel: 6.3
  Target Release: 22.04 (5.15 kernel)

  [HW/SW Information]
  Sapphire Rapids

  [Business Justification]
  Performance Improvements

  Upstream: Merged 6.3
  Commit ID: 60675225ebeecea248035fd3a0efc82ae9038a98

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/2008519/+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 2008519] Re: cpufreq: intel_pstate: Update Balance performance EPP for Sapphire Rapids

@Pragyansri, if you could point out one of the test loads usable to
check the difference we would have it documented here. Right now not
sure whether we have access to a Sapphire Rapids directly. But best to
have all details in one place.

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

Title:
  cpufreq: intel_pstate: Update Balance performance EPP for Sapphire
  Rapids

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  In Progress
Status in linux source package in Lunar:
  In Progress

Bug description:
  [SRU Justification]

  == Impact ==
  See original description. The goal is to adjust the behavior of the balanced 
governor for certain Xeon CPUs (those are CPUs rather seen in servers so there 
should be no impact on laptop users). While the initial request was Jammy/5.15 
only we should do this to Kinetic and Lunar as well so the experience is the 
same regardless of release.

  == Fix ==
  This picks one change from v6.3-rc1 which tweaks the intel_idle driver for a 
specific CPU model.

  == Test case ==
  

  == Regression Potential ==
  The change modifies how quickly CPUs scale up (and probably down) depending 
on workload. Power usage unlikely is of that much concern in server space. 
Maybe increased heat would be observed.

  == Original description ==

  [Feature Description]
  Ubuntu uses powersave governor as the default.While the powersave governor 
has much lower power, the performance is lower than +25% for several workloads 
compared to performance governor.

  Report is published: www.Phoronix.com showing difference of 37%

  The goal here is to keep mean performance delta of powersave governor
  from performance governor around 10% to 12% by running wide variety
  of server workloads. For some bursty workload, this delta can be still
  large, as ramp up of frequency will still lag with powersave governor
  irrespective of EPP setting. The performance governor always requests
  maximum frequency.

  Based on experiments, EPP of 0x00, 0x10, 0x20, the performance delta for
  powersave governor is around 12%. But the EPP 0x20 has 18% lower average
  power.

  Also experiments are done by raising intel_pstate sysfs min_perf_pct as
  high as 50%. This didn't bring in any additional improvements compared
  to just changing EPP.

  Target Kernel: 6.3
  Target Release: 22.04 (5.15 kernel)

  [HW/SW Information]
  Sapphire Rapids

  [Business Justification]
  Performance Improvements

  Upstream: Merged 6.3
  Commit ID: 60675225ebeecea248035fd3a0efc82ae9038a98

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/2008519/+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 2009594] Re: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE)

2023-03-10 Thread Frode Nordahl

Excellent work on finding more information about the cause and a
workaround, thank you for that!

I think it would be appropriate to tackle this as part of the resolution
of netplan.io bug 1988018 though, so the charm task would still be
invalid unfortunately.

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

Title:
  Mlx5 kworker blocked Kernel 5.19 (Jammy HWE)

Status in charm-ovn-chassis:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is seen on particular with :
  * Charmed Openstack with Jammy Yoga
  * 5.19.0-35-generic (linux-generic-hwe-22.04/jammy-updates)
  * Mellanox Connectx-6 card with mlx5_core module being used 
  * SR-IOV is being used with VF-LAG for the use of OVN hardware offloading

  The servers enter into very high load (around 75~100) quickly during the boot 
with all process relying on network communication with the Mellanox network 
card being stuck or extremely slow.
  Kernel logs are being displayed about kworkers being blocked for more than 
120 seconds

  The number of SR-IOV devices configured both from the firmware and the kernel 
seems to have a serious correlation with the likeliness of this bug to occur.
  Having enabled more VF seems to hugely increase the risk for this bug to 
arise.

  This does not happen systematically at every boot, but with 32 VFs on each 
PF, it occurs about 40% of the time.
  To recover the server, a cold reboot is required.

  Look at a quick sample of the trace, this seems to involve directly
  the mlx5 driver within the kernel :

  Mar 07 05:24:56 nova-1 kernel: INFO: task kworker/0:1:19 blocked for more 
than 120 seconds.
  Mar 07 05:24:56 nova-1 kernel:   Tainted: P   OE 
5.19.0-35-generic #36~22.04.1-Ubuntu
  Mar 07 05:24:56 nova-1 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Mar 07 05:24:56 nova-1 kernel: task:kworker/0:1 state:D stack:0 pid:  
 19 ppid: 2 flags:0x4000
  Mar 07 05:24:56 nova-1 kernel: Workqueue: events work_for_cpu_fn
  Mar 07 05:24:56 nova-1 kernel: Call Trace:
  Mar 07 05:24:56 nova-1 kernel:  
  Mar 07 05:24:56 nova-1 kernel:  __schedule+0x257/0x5d0
  Mar 07 05:24:56 nova-1 kernel:  schedule+0x68/0x110
  Mar 07 05:24:56 nova-1 kernel:  schedule_preempt_disabled+0x15/0x30
  Mar 07 05:24:56 nova-1 kernel:  __mutex_lock.constprop.0+0x4f1/0x750
  Mar 07 05:24:56 nova-1 kernel:  __mutex_lock_slowpath+0x13/0x20
  Mar 07 05:24:56 nova-1 kernel:  mutex_lock+0x3e/0x50
  Mar 07 05:24:56 nova-1 kernel:  mlx5_register_device+0x1c/0xb0 [mlx5_core]
  Mar 07 05:24:56 nova-1 kernel:  mlx5_init_one+0xe4/0x110 [mlx5_core]
  Mar 07 05:24:56 nova-1 kernel:  probe_one+0xcb/0x120 [mlx5_core]
  Mar 07 05:24:56 nova-1 kernel:  local_pci_probe+0x4b/0x90
  Mar 07 05:24:56 nova-1 kernel:  work_for_cpu_fn+0x1a/0x30
  Mar 07 05:24:56 nova-1 kernel:  process_one_work+0x21f/0x400
  Mar 07 05:24:56 nova-1 kernel:  worker_thread+0x200/0x3f0
  Mar 07 05:24:56 nova-1 kernel:  ? rescuer_thread+0x3a0/0x3a0
  Mar 07 05:24:56 nova-1 kernel:  kthread+0xee/0x120
  Mar 07 05:24:56 nova-1 kernel:  ? kthread_complete_and_exit+0x20/0x20
  Mar 07 05:24:56 nova-1 kernel:  ret_from_fork+0x22/0x30
  Mar 07 05:24:56 nova-1 kernel:  

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ovn-chassis/+bug/2009594/+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 2008519] Re: cpufreq: intel_pstate: Update Balance performance EPP for Sapphire Rapids

** Description changed:

  [SRU Justification]
  
  == Impact ==
  See original description. The goal is to adjust the behavior of the balanced 
governor for certain Xeon CPUs (those are CPUs rather seen in servers so there 
should be no impact on laptop users). While the initial request was Jammy/5.15 
only we should do this to Kinetic and Lunar as well so the experience is the 
same regardless of release.
  
  == Fix ==
- This picks one change from v6.3-rc1 which tweaks the intel_idle driver for a 
specific CPU model.
+ This picks one change from v6.3-rc1 which tweaks the intel_idle driver for a 
specific CPU model. For Jammy/5.15 this requires one additional change 
+ which introduces the EPP tweak for Alderlake.
  
  == Test case ==
  
  
  == Regression Potential ==
  The change modifies how quickly CPUs scale up (and probably down) depending 
on workload. Power usage unlikely is of that much concern in server space. 
Maybe increased heat would be observed.
+ For Jammy there is the additional risk of havind a different power usage
+ on Alderlake which is a Laptop CPU. However that change is part of v5.17
+ and thus would already be in effect with current 22.04 HWE.
  
  == Original description ==
  
  [Feature Description]
  Ubuntu uses powersave governor as the default.While the powersave governor 
has much lower power, the performance is lower than +25% for several workloads 
compared to performance governor.
  
  Report is published: www.Phoronix.com showing difference of 37%
  
  The goal here is to keep mean performance delta of powersave governor
  from performance governor around 10% to 12% by running wide variety
  of server workloads. For some bursty workload, this delta can be still
  large, as ramp up of frequency will still lag with powersave governor
  irrespective of EPP setting. The performance governor always requests
  maximum frequency.
  
  Based on experiments, EPP of 0x00, 0x10, 0x20, the performance delta for
  powersave governor is around 12%. But the EPP 0x20 has 18% lower average
  power.
  
  Also experiments are done by raising intel_pstate sysfs min_perf_pct as
  high as 50%. This didn't bring in any additional improvements compared
  to just changing EPP.
  
  Target Kernel: 6.3
  Target Release: 22.04 (5.15 kernel)
  
  [HW/SW Information]
  Sapphire Rapids
  
  [Business Justification]
  Performance Improvements
  
  Upstream: Merged 6.3
  Commit ID: 60675225ebeecea248035fd3a0efc82ae9038a98

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

Title:
  cpufreq: intel_pstate: Update Balance performance EPP for Sapphire
  Rapids

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  In Progress
Status in linux source package in Lunar:
  In Progress

Bug description:
  [SRU Justification]

  == Impact ==
  See original description. The goal is to adjust the behavior of the balanced 
governor for certain Xeon CPUs (those are CPUs rather seen in servers so there 
should be no impact on laptop users). While the initial request was Jammy/5.15 
only we should do this to Kinetic and Lunar as well so the experience is the 
same regardless of release.

  == Fix ==
  This picks one change from v6.3-rc1 which tweaks the intel_idle driver for a 
specific CPU model. For Jammy/5.15 this requires one additional change 
  which introduces the EPP tweak for Alderlake.

  == Test case ==
  

  == Regression Potential ==
  The change modifies how quickly CPUs scale up (and probably down) depending 
on workload. Power usage unlikely is of that much concern in server space. 
Maybe increased heat would be observed.
  For Jammy there is the additional risk of havind a different power usage
  on Alderlake which is a Laptop CPU. However that change is part of v5.17
  and thus would already be in effect with current 22.04 HWE.

  == Original description ==

  [Feature Description]
  Ubuntu uses powersave governor as the default.While the powersave governor 
has much lower power, the performance is lower than +25% for several workloads 
compared to performance governor.

  Report is published: www.Phoronix.com showing difference of 37%

  The goal here is to keep mean performance delta of powersave governor
  from performance governor around 10% to 12% by running wide variety
  of server workloads. For some bursty workload, this delta can be still
  large, as ramp up of frequency will still lag with powersave governor
  irrespective of EPP setting. The performance governor always requests
  maximum frequency.

  Based on experiments, EPP of 0x00, 0x10, 0x20, the performance delta for
  powersave governor is around 12%. But the EPP 0x20 has 18% lower average
  power.

  Also experiments are done by raising intel_pstate sysfs min_perf_pct as
  high as 50%. This didn'

[Kernel-packages] [Bug 2002314] Re: nouveau 0000:59:00.0: timeout in nvkm_falcon_v1_wait_for_halt

2023-03-10 Thread Islam

Why the importance of that bug has not been set yet?
This is a very serious issue because I cannot lock my screen at all if I need 
to walk away from the laptop as this will trigger the bug.
Every time I must put the laptop to sleep.

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

Title:
  nouveau :59:00.0: timeout in nvkm_falcon_v1_wait_for_halt

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a Hybrid graphics laptop with Ubuntu 22.10 (also happened with
  22.04) and xserver-xorg-video-nouveau version 1.0.17-2build1.

  After locking the screen manually or automatically after the specified 
timeout, the whole laptop freeze or behave extremely slow, either ways a hard 
reset is a must by holding the power button to bring it back to life.
  This can happen right after the locking or after a while, but it doesn't 
happen if I suspended the laptop and wake it up.

  This doesn't happen if the nvidia proprietary driver is used.

  Right after a fresh boot, you can see the nouveau error in the
  attached dmesg.txt file.

  Sometimes while trying to unlock or switching to tty it shows such
  errors:

  4010.649752) rcus INFO: rcu preempt detected stalls on CPUs/tasks:
  4010.649766) rcus $0-...1: (1 GPs behind) idle-a58/0/0x0
  softirq=30921/30922 fqs=0 (false positive?)

  4010.649774) rout $2-... (0 ticks this GP) idle-4dc/0/0x0
  softirq-26935/26935 fas-0 (false positive?) 4010.649776) rcut $3-...:
  (0 ticks this GP) idle-8ce/0/0x0 softirq-27111/27111 fqs=0 (false
  positive?)

  4010.649777) rcus $4-...1: (1 GPs behind) idle-340/0/0x0
  softirq-28041/28042 fqs=0 (false positive?) 4010.649779) rcus $6-...11
  (0 ticks this GP) idle-86a/0/0x0 softirq-33526/33526 fas=0 (false
  positive?)

  4010.649780) rous $7-... (1 GPs behind) idle=c01/1/0x4000
  softirq-29455/29456 fqs=0 3115.864965) watchdog: BUG: soft lockup
  CPU#4 stuck for 515s! [Timer:5288)

  3115.864972) 1915 :00:02.0: [drm] ERROR [CRTC:98:pipe A) filp.done
  timed out 3115.865030) watchdog: BUG: soft lockup- CPUW7 stuck for
  515s! [Socket Thread:4856]

  3115.865034) watchdog: BUG: soft lockup CPUW2 stuck for 515s!
  [snapd:5977)

  3115.865046) watchdog: BUG: soft lockup- CPUW3 stuck for 515s!
  (openvpn:4633]

  3115.865080) watchdog: BUG: soft lockup- CPU#6 stuck for $15s!
  [HebExtensions:5140)

  And:

  [2639.153118] NMI watchdog: Watchdog detected hard LOCKUP on cpu 7
  [2661.862757] NHI watchdog: Watchdog detected hard LOCKUP on cpu 0

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xserver-xorg-video-nouveau 1:1.0.17-2build1
  ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17
  Uname: Linux 5.19.0-28-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  9 15:59:37 2023
  DistUpgraded: Fresh install
  DistroCodename: kinetic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.38, 5.19.0-26-generic, x86_64: installed
   virtualbox/6.1.38, 5.19.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics] 
[1043:1e6f]
     Subsystem: ASUSTeK Computer Inc. TU117M [GeForce MX450] [1043:1e6f]
  InstallationDate: Installed on 2023-01-04 (4 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-28-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX435EG.315
  dmi.board.asset.tag:
  dmi.board.name: UX435EG
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX435EG_UX435EG
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input

[Kernel-packages] [Bug 2009283] Re: linux: CONFIG_SERIAL_8250_MID=y

2023-03-10 Thread Dimitri John Ledkov

I understand that having it in the root filesystem is too late.

However, I would have thought it would be good enough to have it early
in the initrd, or do you also require output prior to initrd starting?
having it built-in trades wasting RAM for all billions of Ubuntu
instances, and the module in question is large.

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

Title:
  linux: CONFIG_SERIAL_8250_MID=y

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Starting from 5.19 HWE kernel, this option became as dedicated module instead 
of being compiled into the kernel.
  5.19 hwe-next also has CONFIG_SERIAL_8250_MID=m
  On 5.15 it was OK

  ~$ uname -r
  5.19.0-32-generic
  $ cat /boot/config-5.19.0-32-generic  | grep 8250_MID
  CONFIG_SERIAL_8250_MID=m

  Please make it CONFIG_SERIAL_8250_MID=y for all the future kernels.

  Previous ticket: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967338
  Some discussion: 
https://lists.ubuntu.com/archives/kernel-team/2022-March/128690.html

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009283/+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 2009952] [NEW] Screen flickering/ tearing on 6.1 kernel

2023-03-10 Thread Roemer Claasen

Public bug reported:

After upgrading from kernel 5.19.0-35-generic to 6.1.0-1007-oem there is
occasional screen flicker/ tear. It happens around every minute; it
seems connected to window/ pointer movement, but I have no clear way of
reproducing. Disruption is minor,  but annoying.

I'm running 22.04 LTS on a new Thinkpad T14s with AMD Ryzen 6850u. The
system is fully functional. No crashes, nothing breaks.

Background on the use of 6.1.0-1007-oem: 5.19.0-35-generic breaks
suspend/ resume on my laptop, see
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718.

In a way, running 6.1 is a 'flight forward', since 5.15.0-67-generic
(previous 22.04.1 LTS kernel) works well, with working suspend/ resume,
and without screen flicker. But that's an 'old' kernel now, missing some
nice improvements for the newer Ryzen APUs.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-oem-22.04c 6.1.0.1007.7
ProcVersionSignature: Ubuntu 6.1.0-1007.7-oem 6.1.6
Uname: Linux 6.1.0-1007-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 10 13:09:20 2023
InstallationDate: Installed on 2023-02-06 (31 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
SourcePackage: linux-meta-oem-6.1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-meta-oem-6.1 (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  Screen flickering/ tearing on  6.1 kernel

Status in linux-meta-oem-6.1 package in Ubuntu:
  New

Bug description:
  After upgrading from kernel 5.19.0-35-generic to 6.1.0-1007-oem there
  is occasional screen flicker/ tear. It happens around every minute; it
  seems connected to window/ pointer movement, but I have no clear way
  of reproducing. Disruption is minor,  but annoying.

  I'm running 22.04 LTS on a new Thinkpad T14s with AMD Ryzen 6850u. The
  system is fully functional. No crashes, nothing breaks.

  Background on the use of 6.1.0-1007-oem: 5.19.0-35-generic breaks
  suspend/ resume on my laptop, see
  https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718.

  In a way, running 6.1 is a 'flight forward', since 5.15.0-67-generic
  (previous 22.04.1 LTS kernel) works well, with working suspend/
  resume, and without screen flicker. But that's an 'old' kernel now,
  missing some nice improvements for the newer Ryzen APUs.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-oem-22.04c 6.1.0.1007.7
  ProcVersionSignature: Ubuntu 6.1.0-1007.7-oem 6.1.6
  Uname: Linux 6.1.0-1007-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 10 13:09:20 2023
  InstallationDate: Installed on 2023-02-06 (31 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: linux-meta-oem-6.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-6.1/+bug/2009952/+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 2009283] Re: linux: CONFIG_SERIAL_8250_MID=y

2023-03-10 Thread Kleber Sacilotto de Souza

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

Title:
  linux: CONFIG_SERIAL_8250_MID=y

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Starting from 5.19 HWE kernel, this option became as dedicated module instead 
of being compiled into the kernel.
  5.19 hwe-next also has CONFIG_SERIAL_8250_MID=m
  On 5.15 it was OK

  ~$ uname -r
  5.19.0-32-generic
  $ cat /boot/config-5.19.0-32-generic  | grep 8250_MID
  CONFIG_SERIAL_8250_MID=m

  Please make it CONFIG_SERIAL_8250_MID=y for all the future kernels.

  Previous ticket: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967338
  Some discussion: 
https://lists.ubuntu.com/archives/kernel-team/2022-March/128690.html

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009283/+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 2007718] Re: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen CPUs

2023-03-10 Thread Roemer Claasen

Screen flickering/ tear bug filed in
https://bugs.launchpad.net/ubuntu/+source/linux-meta-
oem-6.1/+bug/2009952.

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

Title:
  HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen CPUs

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

Bug description:
  After 22.04 LTS upgraded the linux-generic-hwe kernel to 5.19.0.32
  (from 5.15.0.60) suspend/wake up is broken on my laptop.

  The system refuses to wake up in about 50% of the cases, seemingly
  random. The only "solution" is a forced system power down.

  Reverting back to 5.15.0.60 resolves this issue immediately.

  I suspect some patch was not re-applied to 5.19, since there are many
  postings on Reddit (for instance) about sleep problems with newer AMD
  CPUs, but 5.15 was running beautifully.

  My machine is a Lenovo Thinkpad T14s AMD Gen 3, AMD 6850u CPU.

  UPDATE:

  See attached log. This may not be a case of the laptop failing to
  resume, but a case of the laptop not suspending properly!

  What happened was the following. When packing in my things,  I closed
  the laptop and put it in my bag. At home I picked it up again, and
  immediately noticed how unusually hot it was. The laptop didn't resume
  properly on opening the lid, but was frozen as before.

  So this might actually be a case of the laptop FAILING TO SUSPEND
  properly, instead of failing to wake up.

  UPDATE:

  I just noticed the battery was down to the low 40% from at least 80%.
  Given the temperature on opening the laption I suspect the CPU has
  been working hard during "sleep time".

  EDIT:

  Changed title after confirmation for earlier Ryzen 5000 CPU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718/+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 2009283] Re: linux: CONFIG_SERIAL_8250_MID=y

2023-03-10 Thread Renato Botelho

Hello Dimitri!

Unfortunately, if it's not built-in we have no console and system cannot
be installed.  Same change was made on debian years ago to solve the
same problem, as you can see at:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864368

https://salsa.debian.org/kernel-
team/linux/-/commit/7618511643be57b5587f66729e1c0121eb4617f6

** Bug watch added: Debian Bug tracker #864368
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864368

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

Title:
  linux: CONFIG_SERIAL_8250_MID=y

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Starting from 5.19 HWE kernel, this option became as dedicated module instead 
of being compiled into the kernel.
  5.19 hwe-next also has CONFIG_SERIAL_8250_MID=m
  On 5.15 it was OK

  ~$ uname -r
  5.19.0-32-generic
  $ cat /boot/config-5.19.0-32-generic  | grep 8250_MID
  CONFIG_SERIAL_8250_MID=m

  Please make it CONFIG_SERIAL_8250_MID=y for all the future kernels.

  Previous ticket: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967338
  Some discussion: 
https://lists.ubuntu.com/archives/kernel-team/2022-March/128690.html

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009283/+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 2009283] Re: linux: CONFIG_SERIAL_8250_MID=y

2023-03-10 Thread Renato Botelho

I also found this:

To use a serial port as console you need to compile the support into
your kernel - by default it is not compiled in. For PC style serial
ports it’s the config option next to menu option:

Character devices ‣ Serial drivers ‣ 8250/16550 and compatible serial
support ‣ Console on 8250/16550 and compatible serial port

You must compile serial support into the kernel and not as a module.

at https://www.kernel.org/doc/html/latest/admin-guide/serial-
console.html

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

Title:
  linux: CONFIG_SERIAL_8250_MID=y

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Starting from 5.19 HWE kernel, this option became as dedicated module instead 
of being compiled into the kernel.
  5.19 hwe-next also has CONFIG_SERIAL_8250_MID=m
  On 5.15 it was OK

  ~$ uname -r
  5.19.0-32-generic
  $ cat /boot/config-5.19.0-32-generic  | grep 8250_MID
  CONFIG_SERIAL_8250_MID=m

  Please make it CONFIG_SERIAL_8250_MID=y for all the future kernels.

  Previous ticket: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967338
  Some discussion: 
https://lists.ubuntu.com/archives/kernel-team/2022-March/128690.html

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009283/+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 1997908] Re: Wi-Fi 6E does not work in Canada with Intel AX210

2023-03-10 Thread Juerg Haefliger

** Changed in: linux-firmware (Ubuntu Kinetic)
   Status: Incomplete => Confirmed

** Description changed:

+ [Impact]
+ 
  Intel has been adding support for Wi-Fi 6E (6GHz band) to additional
  countries as they get regulatory approval.
  
  With the base install of Ubuntu 22.10, I do not have 6GHz support while
  in Canada, and have confirmed with 'iw reg get'.
  
  Intel has released an updated pnvm file to support more countries:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-ty-a0-gf-a0.pnvm?id=20d9516de4cdc041e2aa83009e5b0464b1c3ed81
  
  After copying the latest iwlwifi-ty-a0-gf-a0-72.ucode and iwlwifi-
  ty-a0-gf-a0.pnvm from
  git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git and rebooting I now have full support:
  
  $ iw reg get
  
  [...]
  
  (5945 - 5965 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, PASSIVE-SCAN
  (5965 - 5985 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, PASSIVE-SCAN
  (5985 - 6005 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, PASSIVE-SCAN
  (6005 - 6025 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, PASSIVE-SCAN
  (6025 - 6045 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, PASSIVE-SCAN
  (6045 - 6065 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, PASSIVE-SCAN
  (6065 - 6085 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, PASSIVE-SCAN
  (6085 - 6105 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, PASSIVE-SCAN
  (6105 - 6125 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, PASSIVE-SCAN
  (6125 - 6145 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, PASSIVE-SCAN
  (6145 - 6165 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, PASSIVE-SCAN
  (6165 - 6185 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, PASSIVE-SCAN
  (6185 - 6205 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, PASSIVE-SCAN
  (6205 - 6225 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, PASSIVE-SCAN
  (6225 - 6245 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, PASSIVE-SCAN
  (6245 - 6265 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, PASSIVE-SCAN
  (6265 - 6285 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, PASSIVE-SCAN
  (6285 - 6305 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, PASSIVE-SCAN
  (6305 - 6325 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, PASSIVE-SCAN
  (6325 - 6345 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, PASSIVE-SCAN
  (6345 - 6365 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, PASSIVE-SCAN
  
  Can we update the linux-firmware package for kinetic to include the
  latest pnmv and core 72 firmware?
+ 
+ [Fix]
+ 
+ See above.
+ 
+ [Test Case]
+ 
+ See above.
+ 
+ [Where Problems Could Occur]
+ 
+ Networking issues, stack traces, kernel crashes on machines with NICs
+ that load this firmware.

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

Title:
  Wi-Fi 6E does not work in Canada with Intel AX210

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Kinetic:
  Confirmed
Status in linux-firmware source package in Lunar:
  Fix Released

Bug description:
  [Impact]

  Intel has been adding support for Wi-Fi 6E (6GHz band) to additional
  countries as they get regulatory approval.

  With the base install of Ubuntu 22.10, I do not have 6GHz support
  while in Canada, and have confirmed with 'iw reg get'.

  Intel has released an updated pnvm file to support more countries:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-ty-a0-gf-a0.pnvm?id=20d9516de4cdc041e2aa83009e5b0464b1c3ed81

  After copying the latest iwlwifi-ty-a0-gf-a0-72.ucode and iwlwifi-
  ty-a0-gf-a0.pnvm from
  git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git and rebooting I now have full support:

  $ iw reg get

  [...]

  (5945 - 5965 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, PASSIVE-SCAN
  (5965 - 5985 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, PASSIVE-SCAN
  (5985 - 6005 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, PASSIVE-SCAN
  (6005 - 6025 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, PASSIVE-SCAN
  (6025 - 6045 @ 1180), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, PASSIVE-SCAN
  (

[Kernel-packages] [Bug 2003348] Re: [23.04] Kernel 6.2 does not boot on s390x

This was fixed during the regular rebase with upstream. We can close
this one now.

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

** Changed in: linux (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/2003348

Title:
  [23.04] Kernel 6.2 does not boot on s390x

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  The kernel team created a first kernel 6.2 for testing purposes.

  linux-unstable 6.2.0-4.4 ia available in ppa:canonical-kernel-
  team/bootstrap

  However this kernel does not boot on s390x and crashes:

  https://pastebin.canonical.com/p/qXj4g4bgGH/

  or:
  ...
  Ý0.408281¨ md: Waiting for all devices to be available before autodetect
  Ý0.408283¨ md: If you don't use raid, use raid=noautodetect
  Ý0.408285¨ md: Autodetecting RAID arrays.
  Ý0.408287¨ md: autorun ...
  Ý0.408288¨ md: ... autorun DONE.
  Ý0.408405¨ /dev/root: Can't open blockdev
  Ý0.408409¨ VFS: Cannot open root device "disk/by-path/ccw-0.0.0400-part1" 
or
   unknown-block(0,0): error -6
  Ý0.408412¨ Please append a correct "root=" boot option; here are the 
availa
  le partitions:
  Ý0.408415¨ Kernel panic - not syncing: VFS: Unable to mount root fs on 
unkno
  wn-block(0,0)
  Ý0.408418¨ CPU: 2 PID: 1 Comm: swapper/0 Not tainted 6.2.0-4-generic 
#4-Ubun
  tu
  Ý0.408421¨ Hardware name: IBM 2964 N63 400 (z/VM 6.4.0)
  Ý0.408423¨ Call Trace:
  Ý0.408425¨  Ý¨ dump_stack_lvl+0x62/0x90
  Ý0.408433¨  Ý¨ panic+0x174/0x360
  Ý0.408438¨  Ý¨ mount_block_root+0x16e/0x210
  Ý0.408444¨  Ý¨ prepare_namespace+0x168/0x1e0
  Ý0.408448¨  Ý¨ kernel_init_freeable+0x1de/0x1f0
  Ý0.408451¨  Ý¨ kernel_init+0x2e/0x1a0
  Ý0.408455¨  Ý¨ __ret_from_fork+0x40/0x60
  Ý0.408459¨  Ý¨ ret_from_fork+0xa/0x40
  02: HCPGIR450W CP entered; disabled wait PSW 00020001 8000  
B50E215E

  or:
  [8.693187] /dev/root: Can't open blockdev
  [8.693191] VFS: Cannot open root device "disk/by-path/ccw-0.0.260b-part1" 
or unknown-block(0,0): error -6
  [8.693194] Please append a correct "root=" boot option; here are the 
available partitions:
  [8.693198] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)

  Initially we thought it might be related to LVM/DM, but it's not,
  since it happens also on single DASD disk installation without LVM and also 
on NVMe disks.
  It also happens on z15 and on z13.

  Messages indicate that either the "root=" argument is wrong or not there.
  I can check /proc/cmdline since the system ends up in a crash for me.

  However, installing and using 6.1.0-9 works fine.
  _

  Steps to re-create:
  - Install Ubuntu lunar using:

https://cdimage.ubuntu.com/ubuntu-server/daily-live/current/lunar-live-server-s390x.iso
or:

https://cdimage.ubuntu.com/ubuntu-server/daily-live/pending/lunar-live-server-s390x.iso
  (- get it updated:
sudo apt -y -q update && sudo apt -y -q full-upgrade && sudo apt autoremove 
--purge )
  - sudo add-apt-repository --yes ppa:canonical-kernel-team/bootstrap
  - $ sudo apt update
  - $ sudo apt install --yes linux-image-6.2.0-4-generic 
linux-modules-6.2.0-4-generic linux-modules-extra-6.2.0-4-generic 
linux-headers-6.2.0-4-generic
  - $ sudo reboot
  - open the console (e.g. Operating Systems Messages) and monitor the boot/IPL 
process, it's fail like above

  Do the same with kernel 6.1:
  sudo apt install --yes linux-image-6.1.0-9-generic 
linux-modules-6.1.0-9-generic linux-modules-extra-6.1.0-9-generic 
linux-headers-6.1.0-9-generic
  and the system reboots successfully.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003348/+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 2009283] Re: linux: CONFIG_SERIAL_8250_MID=y

** Also affects: linux (Ubuntu Lunar)
   Importance: Undecided
   Status: Confirmed

** Also affects: linux (Ubuntu Kinetic)
   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/2009283

Title:
  linux: CONFIG_SERIAL_8250_MID=y

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Kinetic:
  New
Status in linux source package in Lunar:
  Confirmed

Bug description:
  Starting from 5.19 HWE kernel, this option became as dedicated module instead 
of being compiled into the kernel.
  5.19 hwe-next also has CONFIG_SERIAL_8250_MID=m
  On 5.15 it was OK

  ~$ uname -r
  5.19.0-32-generic
  $ cat /boot/config-5.19.0-32-generic  | grep 8250_MID
  CONFIG_SERIAL_8250_MID=m

  Please make it CONFIG_SERIAL_8250_MID=y for all the future kernels.

  Previous ticket: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967338
  Some discussion: 
https://lists.ubuntu.com/archives/kernel-team/2022-March/128690.html

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009283/+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 2009594] Re: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE)

2023-03-10 Thread Frode Nordahl

However, it will probably take some time to resolve bug 1988018 so we
should probably look into what interim solutions the charm could provide
until we get there.

** Changed in: charm-ovn-chassis
   Status: New => Triaged

** Changed in: charm-ovn-chassis
   Importance: Undecided => High

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

Title:
  Mlx5 kworker blocked Kernel 5.19 (Jammy HWE)

Status in charm-ovn-chassis:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is seen on particular with :
  * Charmed Openstack with Jammy Yoga
  * 5.19.0-35-generic (linux-generic-hwe-22.04/jammy-updates)
  * Mellanox Connectx-6 card with mlx5_core module being used 
  * SR-IOV is being used with VF-LAG for the use of OVN hardware offloading

  The servers enter into very high load (around 75~100) quickly during the boot 
with all process relying on network communication with the Mellanox network 
card being stuck or extremely slow.
  Kernel logs are being displayed about kworkers being blocked for more than 
120 seconds

  The number of SR-IOV devices configured both from the firmware and the kernel 
seems to have a serious correlation with the likeliness of this bug to occur.
  Having enabled more VF seems to hugely increase the risk for this bug to 
arise.

  This does not happen systematically at every boot, but with 32 VFs on each 
PF, it occurs about 40% of the time.
  To recover the server, a cold reboot is required.

  Look at a quick sample of the trace, this seems to involve directly
  the mlx5 driver within the kernel :

  Mar 07 05:24:56 nova-1 kernel: INFO: task kworker/0:1:19 blocked for more 
than 120 seconds.
  Mar 07 05:24:56 nova-1 kernel:   Tainted: P   OE 
5.19.0-35-generic #36~22.04.1-Ubuntu
  Mar 07 05:24:56 nova-1 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Mar 07 05:24:56 nova-1 kernel: task:kworker/0:1 state:D stack:0 pid:  
 19 ppid: 2 flags:0x4000
  Mar 07 05:24:56 nova-1 kernel: Workqueue: events work_for_cpu_fn
  Mar 07 05:24:56 nova-1 kernel: Call Trace:
  Mar 07 05:24:56 nova-1 kernel:  
  Mar 07 05:24:56 nova-1 kernel:  __schedule+0x257/0x5d0
  Mar 07 05:24:56 nova-1 kernel:  schedule+0x68/0x110
  Mar 07 05:24:56 nova-1 kernel:  schedule_preempt_disabled+0x15/0x30
  Mar 07 05:24:56 nova-1 kernel:  __mutex_lock.constprop.0+0x4f1/0x750
  Mar 07 05:24:56 nova-1 kernel:  __mutex_lock_slowpath+0x13/0x20
  Mar 07 05:24:56 nova-1 kernel:  mutex_lock+0x3e/0x50
  Mar 07 05:24:56 nova-1 kernel:  mlx5_register_device+0x1c/0xb0 [mlx5_core]
  Mar 07 05:24:56 nova-1 kernel:  mlx5_init_one+0xe4/0x110 [mlx5_core]
  Mar 07 05:24:56 nova-1 kernel:  probe_one+0xcb/0x120 [mlx5_core]
  Mar 07 05:24:56 nova-1 kernel:  local_pci_probe+0x4b/0x90
  Mar 07 05:24:56 nova-1 kernel:  work_for_cpu_fn+0x1a/0x30
  Mar 07 05:24:56 nova-1 kernel:  process_one_work+0x21f/0x400
  Mar 07 05:24:56 nova-1 kernel:  worker_thread+0x200/0x3f0
  Mar 07 05:24:56 nova-1 kernel:  ? rescuer_thread+0x3a0/0x3a0
  Mar 07 05:24:56 nova-1 kernel:  kthread+0xee/0x120
  Mar 07 05:24:56 nova-1 kernel:  ? kthread_complete_and_exit+0x20/0x20
  Mar 07 05:24:56 nova-1 kernel:  ret_from_fork+0x22/0x30
  Mar 07 05:24:56 nova-1 kernel:  

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ovn-chassis/+bug/2009594/+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 2009597] Re: Kerberized NFS mounts not working on Raspberry PI

2023-03-10 Thread Juerg Haefliger

** Description changed:

+ [Impact]
+ 
  Kerberized NFS mounts stopped working on Raspberry Pi starting with Ubuntu 
21.10. In 22.10 the issue still exists.
  The reason is that the kernel module rpcsec_gss_krb5 which is needed for 
establishing a kerberos protected NFS connection to the server has been removed 
from the kernel image and put to the linux-modules-extra package instead.
  In my particular case it was:
  linux-image-5.19.0-1011-raspi
  Trying to mount the NFS share resulted in the following error message:
  
  mount.nfs: an incorrect mount option was specified
  
  I did not find any documentation stating that the linux-modules-extra
  package needs to be installed and the kernel module has to be loaded
  manually.
  
  So my expectation would be either to update the documentation or to move
  rpcsec_gss_krb5 back to the kernel image.
+ 
+ [Fix]
+ 
+ Include modules in linux-modules.
+ 
+ [Where Problems Could Occur]
+ 
+ Just moving existing modules between packages.

** Also affects: linux-raspi (Ubuntu Lunar)
   Importance: Undecided
   Status: Confirmed

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

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

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

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

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

Title:
  Kerberized NFS mounts not working on Raspberry PI

Status in linux-raspi package in Ubuntu:
  Confirmed
Status in linux-raspi source package in Jammy:
  Confirmed
Status in linux-raspi source package in Kinetic:
  Confirmed
Status in linux-raspi source package in Lunar:
  Confirmed

Bug description:
  [Impact]

  Kerberized NFS mounts stopped working on Raspberry Pi starting with Ubuntu 
21.10. In 22.10 the issue still exists.
  The reason is that the kernel module rpcsec_gss_krb5 which is needed for 
establishing a kerberos protected NFS connection to the server has been removed 
from the kernel image and put to the linux-modules-extra package instead.
  In my particular case it was:
  linux-image-5.19.0-1011-raspi
  Trying to mount the NFS share resulted in the following error message:

  mount.nfs: an incorrect mount option was specified

  I did not find any documentation stating that the linux-modules-extra
  package needs to be installed and the kernel module has to be loaded
  manually.

  So my expectation would be either to update the documentation or to
  move rpcsec_gss_krb5 back to the kernel image.

  [Fix]

  Include modules in linux-modules.

  [Where Problems Could Occur]

  Just moving existing modules between packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2009597/+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 1939966] Re: [Asus TUF Gaming FA506IV] Random system stops

2023-03-10 Thread Popa Adrian Marius

seems to be a nouveau issue , please install nvidia official drivers
from ubuntu repos and  blacklist nouveau driver at boot

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

Title:
  [Asus TUF Gaming FA506IV] Random system stops

Status in linux-hwe-5.11 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  Every once in a while (it's been three times this week), the entire
  system will just stop. There's still electricity running. The keyboard
  is lit up, and the monitor is black (electricity-running black, and
  not shutdown-black). There's no picture and no sound. Just immediately
  before it does, I know it's about to happen because whatever audio is
  playing at the time will begin repeating, and then the computer goes
  down. I don't actually know if it's an Xorg problem. It just sounded
  like the closest possibility, based on the way the computer actually
  behaves.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.57.02  Tue Jul 13 
16:14:05 UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Aug 14 19:34:11 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed
   nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed
   virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed
   virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1e21]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21]
  InstallationDate: Installed on 2021-03-20 (147 days ago)
  InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210204)
  MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA506IV.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FA506IV
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.9
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF Gaming FA506IV
  dmi.product.name: TUF Gaming FA506IV_TUF506IV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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-hwe-5.11/+bug/1939966/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to :

[Kernel-packages] [Bug 2000778] Re: pmtu.sh in net from ubunut_kernel_selftests crash SUT with K-5.19

2023-03-10 Thread Francis Ginther

Still failing on baltar.ppc64el.9 during 2023.02.27 sru cycle. The
kuzzle and scobee (another arm64 server) passed.

** Tags added: sru-20230227

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

Title:
  pmtu.sh in net from ubunut_kernel_selftests crash SUT with K-5.19

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

Bug description:
  Issue found with Kinetic 5.19.0-27.28 and 5.19.0-28.29 in this cycle 
(20221114) on these SUTs
   * P9 baltar
   * ARM64 kuzzle
   * ARM64 howzit-kernel

  This should not be considered as a regression as the net test cannot
  be built in 5.19.0-24.25

  
  Test log:
  
ubuntu@baltar:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$
 sudo ./pmtu.sh
  TEST: ipv4: PMTU exceptions [ OK ]
  TEST: ipv4: PMTU exceptions - nexthop objects   [ OK ]
  TEST: ipv6: PMTU exceptions [ OK ]
  TEST: ipv6: PMTU exceptions - nexthop objects   [ OK ]
  TEST: ICMPv4 with DSCP and ECN: PMTU exceptions [ OK ]
  TEST: ICMPv4 with DSCP and ECN: PMTU exceptions - nexthop objects   [ OK ]
  'socat' command not found; skipping tests
  TEST: UDPv4 with DSCP and ECN: PMTU exceptions  [SKIP]
  TEST: IPv4 over vxlan4: PMTU exceptions [ OK ]
  TEST: IPv4 over vxlan4: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv6 over vxlan4: PMTU exceptions [ OK ]
  TEST: IPv6 over vxlan4: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv4 over vxlan6: PMTU exceptions [ OK ]
  TEST: IPv4 over vxlan6: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv6 over vxlan6: PMTU exceptions [ OK ]
  TEST: IPv6 over vxlan6: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv4 over geneve4: PMTU exceptions[ OK ]
  TEST: IPv4 over geneve4: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv6 over geneve4: PMTU exceptions[ OK ]
  TEST: IPv6 over geneve4: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv4 over geneve6: PMTU exceptions[ OK ]
  TEST: IPv4 over geneve6: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv6 over geneve6: PMTU exceptions[ OK ]
  TEST: IPv6 over geneve6: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv4, bridged vxlan4: PMTU exceptions [ OK ]
  TEST: IPv4, bridged vxlan4: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv6, bridged vxlan4: PMTU exceptions [ OK ]
  TEST: IPv6, bridged vxlan4: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv4, bridged vxlan6: PMTU exceptions [ OK ]
  TEST: IPv4, bridged vxlan6: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv6, bridged vxlan6: PMTU exceptions [ OK ]
  TEST: IPv6, bridged vxlan6: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv4, bridged geneve4: PMTU exceptions[ OK ]
  TEST: IPv4, bridged geneve4: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv6, bridged geneve4: PMTU exceptions[ OK ]
  TEST: IPv6, bridged geneve4: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv4, bridged geneve6: PMTU exceptions[ OK ]
  TEST: IPv4, bridged geneve6: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv6, bridged geneve6: PMTU exceptions[ OK ]
  TEST: IPv6, bridged geneve6: PMTU exceptions - nexthop objects  [ OK ]
ovs_bridge not supported
  TEST: IPv4, OVS vxlan4: PMTU exceptions [SKIP]
ovs_bridge not supported
  TEST: IPv6, OVS vxlan4: PMTU exceptions [SKIP]
ovs_bridge not supported
  TEST: IPv4, OVS vxlan6: PMTU exceptions [SKIP]
ovs_bridge not supported
  TEST: IPv6, OVS vxlan6: PMTU exceptions [SKIP]
ovs_bridge not supported
  TEST: IPv4, OVS geneve4: PMTU exceptions[SKIP]
ovs_bridge not supported
  TEST: IPv6, OVS geneve4: PMTU exceptions[SKIP]
ovs_bridge not supported
  TEST: IPv4, OVS geneve6: PMTU exceptions[SKIP]
ovs_bridge not supported
  TEST: IPv6, OVS geneve6: PMTU exceptions[SKIP]
  TEST: IPv4 over fou4: PMTU exceptions   [ OK ]
  TEST: IPv4 over fou4: PMTU exceptions - nexthop objects [ OK ]
  TEST: IPv6 ove

[Kernel-packages] [Bug 2009963] [NEW] Ubuntu 20.04.5 Touchpad not recognized with Lenovo ThinkPad P1

You have been subscribed to a public bug:

I updated Ubuntu on my Lenovo Thinkpad P1 to 20.04.5 and suddenly, by
touchpad does not work anymore. The hardware is fine. I can use it when
running Windows 11 on my laptop. But when I run "cat
/proc/bus/input/devices" or "xinput list" I do not see any sign for the
touchpad. Before it was working perfectly.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.15.0-60-generic 5.15.0-60.66~20.04.1
ProcVersionSignature: Ubuntu 5.15.0-60.66~20.04.1-generic 5.15.78
Uname: Linux 5.15.0-60-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.25
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 10 15:16:03 2023
InstallationDate: Installed on 2022-06-17 (266 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
SourcePackage: linux-signed-hwe-5.15
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal
-- 
Ubuntu 20.04.5 Touchpad not recognized with Lenovo ThinkPad P1
https://bugs.launchpad.net/bugs/2009963
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-signed-hwe-5.15 in Ubuntu.

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

[Kernel-packages] [Bug 2009594] Re: Mlx5 kworker blocked Kernel 5.19 (Jammy HWE)

2023-03-10 Thread Billy Olsen

The work-around identified in comment #9 can be used to bypass this. It
delays further services from starting up an attempting to interact with
the mlnx cards which appears to cause kernel hung tasks due to the
kernel hung task timeout of 120 seconds. I'm not convinced at this
moment in time that managing the systemd service files from the charm is
the correct thing to do here. Notably, this would likely be a general
problem on Ubuntu with VFs etc. It may end up being that increasing the
timeout is a longer term solution rather than a work around, however we
need to understand the problem better in order to address the problem in
the right space.

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

Title:
  Mlx5 kworker blocked Kernel 5.19 (Jammy HWE)

Status in charm-ovn-chassis:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is seen on particular with :
  * Charmed Openstack with Jammy Yoga
  * 5.19.0-35-generic (linux-generic-hwe-22.04/jammy-updates)
  * Mellanox Connectx-6 card with mlx5_core module being used 
  * SR-IOV is being used with VF-LAG for the use of OVN hardware offloading

  The servers enter into very high load (around 75~100) quickly during the boot 
with all process relying on network communication with the Mellanox network 
card being stuck or extremely slow.
  Kernel logs are being displayed about kworkers being blocked for more than 
120 seconds

  The number of SR-IOV devices configured both from the firmware and the kernel 
seems to have a serious correlation with the likeliness of this bug to occur.
  Having enabled more VF seems to hugely increase the risk for this bug to 
arise.

  This does not happen systematically at every boot, but with 32 VFs on each 
PF, it occurs about 40% of the time.
  To recover the server, a cold reboot is required.

  Look at a quick sample of the trace, this seems to involve directly
  the mlx5 driver within the kernel :

  Mar 07 05:24:56 nova-1 kernel: INFO: task kworker/0:1:19 blocked for more 
than 120 seconds.
  Mar 07 05:24:56 nova-1 kernel:   Tainted: P   OE 
5.19.0-35-generic #36~22.04.1-Ubuntu
  Mar 07 05:24:56 nova-1 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Mar 07 05:24:56 nova-1 kernel: task:kworker/0:1 state:D stack:0 pid:  
 19 ppid: 2 flags:0x4000
  Mar 07 05:24:56 nova-1 kernel: Workqueue: events work_for_cpu_fn
  Mar 07 05:24:56 nova-1 kernel: Call Trace:
  Mar 07 05:24:56 nova-1 kernel:  
  Mar 07 05:24:56 nova-1 kernel:  __schedule+0x257/0x5d0
  Mar 07 05:24:56 nova-1 kernel:  schedule+0x68/0x110
  Mar 07 05:24:56 nova-1 kernel:  schedule_preempt_disabled+0x15/0x30
  Mar 07 05:24:56 nova-1 kernel:  __mutex_lock.constprop.0+0x4f1/0x750
  Mar 07 05:24:56 nova-1 kernel:  __mutex_lock_slowpath+0x13/0x20
  Mar 07 05:24:56 nova-1 kernel:  mutex_lock+0x3e/0x50
  Mar 07 05:24:56 nova-1 kernel:  mlx5_register_device+0x1c/0xb0 [mlx5_core]
  Mar 07 05:24:56 nova-1 kernel:  mlx5_init_one+0xe4/0x110 [mlx5_core]
  Mar 07 05:24:56 nova-1 kernel:  probe_one+0xcb/0x120 [mlx5_core]
  Mar 07 05:24:56 nova-1 kernel:  local_pci_probe+0x4b/0x90
  Mar 07 05:24:56 nova-1 kernel:  work_for_cpu_fn+0x1a/0x30
  Mar 07 05:24:56 nova-1 kernel:  process_one_work+0x21f/0x400
  Mar 07 05:24:56 nova-1 kernel:  worker_thread+0x200/0x3f0
  Mar 07 05:24:56 nova-1 kernel:  ? rescuer_thread+0x3a0/0x3a0
  Mar 07 05:24:56 nova-1 kernel:  kthread+0xee/0x120
  Mar 07 05:24:56 nova-1 kernel:  ? kthread_complete_and_exit+0x20/0x20
  Mar 07 05:24:56 nova-1 kernel:  ret_from_fork+0x22/0x30
  Mar 07 05:24:56 nova-1 kernel:  

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ovn-chassis/+bug/2009594/+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 2009963] Re: Ubuntu 20.04.5 Touchpad not recognized with Lenovo ThinkPad P1

2023-03-10 Thread Ubuntu Foundations Team Bug Bot

** Package changed: ubuntu => linux-signed-hwe-5.15 (Ubuntu)

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

Title:
  Ubuntu 20.04.5 Touchpad not recognized with Lenovo ThinkPad P1

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

Bug description:
  I updated Ubuntu on my Lenovo Thinkpad P1 to 20.04.5 and suddenly, by
  touchpad does not work anymore. The hardware is fine. I can use it
  when running Windows 11 on my laptop. But when I run "cat
  /proc/bus/input/devices" or "xinput list" I do not see any sign for
  the touchpad. Before it was working perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-60-generic 5.15.0-60.66~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-60.66~20.04.1-generic 5.15.78
  Uname: Linux 5.15.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 10 15:16:03 2023
  InstallationDate: Installed on 2022-06-17 (266 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  SourcePackage: linux-signed-hwe-5.15
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-nvidia/5.15.0-1018.18)

All autopkgtests for the newly accepted linux-restricted-modules-nvidia 
(5.15.0-1018.18) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-nvidia

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2007798] Re: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while

2023-03-10 Thread Ubuntu Kernel Bot

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

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

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


** Tags added: kernel-spammed-jammy-linux-gkeop

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

Title:
  [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a
  while

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

Bug description:
  == SRU Justification ==
  [Impact]
  Audio playback becomes silent on some Intel SoF systems.

  [Fix]
  Revert offending commit.

  [Test]
  The speaker can always play sound after the commit gets reverted.

  [Where problems could occur]
  Audio on linux 5.15 has been working fine without the patch for a long
  time, so this only restore it to where it was.

  == Original Bug Report ==
  [Summary]
  During the kernel SRU testing on focal-hwe, I found the audio output of some 
machines are broken.
  I've tested some of machine on Jammy using same kernel(5.15.0-66-generic) and 
haven't seen this happened.

  The volume bars in settings react to what sound is played correctly
  and device is detected as well.

  [Reproduce steps]
  1. install focal
  2. enable -proposed
  3. run apt dist-upgrade.
  4. reboot.
  5. press fn keys to volume up then volume down or play a short youtube video.
  6. after a while can't hear any sound from the speaker.

  [Failure rate]
  10/10

  [Additional info]
  If I run "sudo alsa force-reload" can make audio work again, but after a 
while it breaks again.
  These are machines that impacted by this bug:
  https://certification.canonical.com/hardware/202007-28045/
  https://certification.canonical.com/hardware/201906-27109/
  https://certification.canonical.com/hardware/201903-26881/
  https://certification.canonical.com/hardware/202007-28047/
  https://certification.canonical.com/hardware/202007-28055/
  https://certification.canonical.com/hardware/202005-27899/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.15.0-66.73~20.04.1-generic 5.15.85
  Uname: Linux 5.15.0-66-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1303 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sun Feb 19 21:24:59 2023
  InstallationDate: Installed on 2020-08-03 (930 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: Feb 19 20:53:23 
dell-inspiron-7591-nebula-n15a-c2-201903-26881 dbus-daemon[985]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.34' (uid=1000 pid=1303 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
  Symptom_Type: Sound works for a while, then breaks
  Title: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd11/06/2019:br1.5:svnDellInc.:pnInspiron7590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0922:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7590
  dmi.product.sku: 0922
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007798/+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 2007798] Re: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while

2023-03-10 Thread Ubuntu Kernel Bot

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

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

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


** Tags added: kernel-spammed-jammy-linux-gke

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

Title:
  [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a
  while

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

Bug description:
  == SRU Justification ==
  [Impact]
  Audio playback becomes silent on some Intel SoF systems.

  [Fix]
  Revert offending commit.

  [Test]
  The speaker can always play sound after the commit gets reverted.

  [Where problems could occur]
  Audio on linux 5.15 has been working fine without the patch for a long
  time, so this only restore it to where it was.

  == Original Bug Report ==
  [Summary]
  During the kernel SRU testing on focal-hwe, I found the audio output of some 
machines are broken.
  I've tested some of machine on Jammy using same kernel(5.15.0-66-generic) and 
haven't seen this happened.

  The volume bars in settings react to what sound is played correctly
  and device is detected as well.

  [Reproduce steps]
  1. install focal
  2. enable -proposed
  3. run apt dist-upgrade.
  4. reboot.
  5. press fn keys to volume up then volume down or play a short youtube video.
  6. after a while can't hear any sound from the speaker.

  [Failure rate]
  10/10

  [Additional info]
  If I run "sudo alsa force-reload" can make audio work again, but after a 
while it breaks again.
  These are machines that impacted by this bug:
  https://certification.canonical.com/hardware/202007-28045/
  https://certification.canonical.com/hardware/201906-27109/
  https://certification.canonical.com/hardware/201903-26881/
  https://certification.canonical.com/hardware/202007-28047/
  https://certification.canonical.com/hardware/202007-28055/
  https://certification.canonical.com/hardware/202005-27899/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.15.0-66.73~20.04.1-generic 5.15.85
  Uname: Linux 5.15.0-66-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1303 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sun Feb 19 21:24:59 2023
  InstallationDate: Installed on 2020-08-03 (930 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: Feb 19 20:53:23 
dell-inspiron-7591-nebula-n15a-c2-201903-26881 dbus-daemon[985]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.34' (uid=1000 pid=1303 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
  Symptom_Type: Sound works for a while, then breaks
  Title: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2019
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd11/06/2019:br1.5:svnDellInc.:pnInspiron7590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0922:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7590
  dmi.product.sku: 0922
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007798/+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 2009355] Re: linux-libc-dev is no longer multi-arch safe

It looks like this problem has been introduce by this commit:

a5ddd0de7d8b ("UBUNTU: [Packaging] install headers to debian/linux-libc-
dev directly")

https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/lunar/commit/?id=a5ddd0de7d8b2159fc5f8df55527e0e447328953

It seems to include temporary files (*.cmd and binaries) to linux-libc-
dev, causing this regression.

I've reverted this patch in lunar/linux, so this should be fixed in the
next kernel that we're going to upload.

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

Title:
  linux-libc-dev is no longer multi-arch safe

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://autopkgtest.ubuntu.com/results/autopkgtest-
  lunar/lunar/i386/b/binutils/20230305_112702_eba45@/log.gz

  dpkg: error processing archive 
/tmp/apt-dpkg-install-9IkDRS/098-linux-libc-dev_6.1.0-16.16_i386.deb (--unpack):
   trying to overwrite shared 
'/arch/x86/include/generated/asm/.syscalls_32.h.cmd', which is different from 
other instances of package linux-libc-dev:i386

  I'm not sure why linux-libc-dev_6.1.0-16.16 has files in /arch
  /install /scripts. But these files are different on different arch (or
  different build, since it embeds build path)

  ==> amd64/arch/x86/include/generated/asm/.syscalls_32.h.cmd <==
  cmd_arch/x86/include/generated/asm/syscalls_32.h := sh 
/build/linux-1t584m/linux-6.1.0/scripts/syscalltbl.sh --abis i386 
/build/linux-1t584m/linux-6.1.0/arch/x86/entry/syscalls/syscall_32.tbl 
arch/x86/include/generated/asm/syscalls_32.h

  ==> i386/arch/x86/include/generated/asm/.syscalls_32.h.cmd <==
  cmd_arch/x86/include/generated/asm/syscalls_32.h := sh 
/build/linux-f194dh/linux-6.1.0/scripts/syscalltbl.sh --abis i386 
/build/linux-f194dh/linux-6.1.0/arch/x86/entry/syscalls/syscall_32.tbl 
arch/x86/include/generated/asm/syscalls_32.h

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009355/+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 2009283] Re: linux: CONFIG_SERIAL_8250_MID=y

I've applied this change to lunar. Next lunar 6.2 kernel will have
CONFIG_SERIAL_8250_MID=y.

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

Title:
  linux: CONFIG_SERIAL_8250_MID=y

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Kinetic:
  New
Status in linux source package in Lunar:
  Confirmed

Bug description:
  Starting from 5.19 HWE kernel, this option became as dedicated module instead 
of being compiled into the kernel.
  5.19 hwe-next also has CONFIG_SERIAL_8250_MID=m
  On 5.15 it was OK

  ~$ uname -r
  5.19.0-32-generic
  $ cat /boot/config-5.19.0-32-generic  | grep 8250_MID
  CONFIG_SERIAL_8250_MID=m

  Please make it CONFIG_SERIAL_8250_MID=y for all the future kernels.

  Previous ticket: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967338
  Some discussion: 
https://lists.ubuntu.com/archives/kernel-team/2022-March/128690.html

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009283/+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 1998244] Re: kselftest net/fib_nexthop_nongw.sh fails

2023-03-10 Thread Andrei Gherzan

I have validated this fix for kinetic:linux-kvm - from proposed:

# selftests: net: fib_nexthop_nongw.sh
# TEST: nexthop: get route with nexthop without gw[ OK ]
# TEST: nexthop: ping through nexthop without gw  [ OK ]
ok 1 selftests: net: fib_nexthop_nongw.sh

Linux ubuntu-kinetic 5.19.0-1019-kvm #20-Ubuntu SMP Fri Feb 10 11:54:33
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux


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

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

Title:
  kselftest net/fib_nexthop_nongw.sh fails

Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-kvm source package in Jammy:
  Fix Released
Status in linux-kvm source package in Kinetic:
  Fix Committed
Status in linux-kvm source package in Lunar:
  Confirmed

Bug description:
  18272 03:33:07 DEBUG| Persistent state client._record_indent 
now set to 2
    18273   03:33:07 DEBUG| Persistent state 
client.unexpected_reboot now set to 
('ubuntu_kernel_selftests.net:fib_nexthop_nongw.sh', 
'ubuntu_kernel_selftests.net:fib_nexthop_nongw.sh')
    18274   03:33:07 DEBUG| Waiting for pid 58525 for 2700 seconds
    18275   03:33:07 WARNI| System python is too old, crash 
handling disabled
    18276   03:33:07 DEBUG| Running 'make run_tests -C net 
TEST_PROGS=fib_nexthop_nongw.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
    18277   03:33:07 DEBUG| [stdout] make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
    18278   03:33:07 DEBUG| [stdout] make --no-builtin-rules 
ARCH=x86 -C ../../../.. headers_install
    18279   03:33:07 DEBUG| [stdout] make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
    18280   03:33:08 DEBUG| [stdout]   INSTALL ./usr/include
    18281   03:33:08 DEBUG| [stdout] make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
    18282   03:33:08 DEBUG| [stdout] TAP version 13
    18283   03:33:08 DEBUG| [stdout] 1..1
    18284   03:33:08 DEBUG| [stdout] # selftests: net: 
fib_nexthop_nongw.sh
    18285   03:33:08 DEBUG| [stdout] # Error: Unknown device type.
    18286   03:33:08 DEBUG| [stdout] # Cannot find device "eth0"
    18287   03:33:08 DEBUG| [stdout] # Cannot find device "eth0"
    18288   03:33:08 DEBUG| [stdout] # TEST: nexthop: get route 
with nexthop without gw[ OK ]
    18289   03:33:18 DEBUG| [stdout] # TEST: nexthop: ping through 
nexthop without gw  [FAIL]
    18290   03:33:18 DEBUG| [stdout] not ok 1 selftests: net: 
fib_nexthop_nongw.sh # exit=1
    18291   03:33:18 DEBUG| [stdout] make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'

  --

  SRU Justification:

  [Impact]

  * Without Kernel support for the Dummy net driver, it is not possible
  to successfully run selftests that use it. This includes as per this
  bug net/fib_nexthop_nongw.sh, but also could potentially include other
  such as rtnetlink.sh, fib_rule_tests.sh, forwarding/* etc.

  [Fix]

  * Custom patch to enable CONFIG_DUMMY=m

  [Test Plan]

  * Before the fix, the net/fib_nexthop_nongw.sh script will fail in the
  specific line which does

  $ ip -n h1 link add name eth0 type dummy
  Error: Unknown device type.

  After the fix it does not fail.

  [Where problems could occur]

  * The regression can be considered as low, since we are adding
  functionality not previously present.

  [Other Info]

  * There does not seem to be a historical reason for removing it from
  linux-kvm.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1998244/+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 2009355] Re: linux-libc-dev is no longer multi-arch safe

** Also affects: linux (Ubuntu Lunar)
   Importance: Critical
   Status: 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/2009355

Title:
  linux-libc-dev is no longer multi-arch safe

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

Bug description:
  https://autopkgtest.ubuntu.com/results/autopkgtest-
  lunar/lunar/i386/b/binutils/20230305_112702_eba45@/log.gz

  dpkg: error processing archive 
/tmp/apt-dpkg-install-9IkDRS/098-linux-libc-dev_6.1.0-16.16_i386.deb (--unpack):
   trying to overwrite shared 
'/arch/x86/include/generated/asm/.syscalls_32.h.cmd', which is different from 
other instances of package linux-libc-dev:i386

  I'm not sure why linux-libc-dev_6.1.0-16.16 has files in /arch
  /install /scripts. But these files are different on different arch (or
  different build, since it embeds build path)

  ==> amd64/arch/x86/include/generated/asm/.syscalls_32.h.cmd <==
  cmd_arch/x86/include/generated/asm/syscalls_32.h := sh 
/build/linux-1t584m/linux-6.1.0/scripts/syscalltbl.sh --abis i386 
/build/linux-1t584m/linux-6.1.0/arch/x86/entry/syscalls/syscall_32.tbl 
arch/x86/include/generated/asm/syscalls_32.h

  ==> i386/arch/x86/include/generated/asm/.syscalls_32.h.cmd <==
  cmd_arch/x86/include/generated/asm/syscalls_32.h := sh 
/build/linux-f194dh/linux-6.1.0/scripts/syscalltbl.sh --abis i386 
/build/linux-f194dh/linux-6.1.0/arch/x86/entry/syscalls/syscall_32.tbl 
arch/x86/include/generated/asm/syscalls_32.h

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009355/+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 2009283] Re: linux: CONFIG_SERIAL_8250_MID=y

** Description changed:

+ [Impact]
+ 
+ CONFIG_SERIAL_8250_MID=y is required to properly use the serial console
+ on some platforms that are using the "mid" serial driver (such as some
+ Intel SoC platforms).
+ 
+ The generic kernel should build this driver statically to make sure we
+ properly support these platforms.
+ 
+ [Test case]
+ 
+ Boot the Ubuntu generic kernel on a system that is using the "mid"
+ serial driver (e.g, no PCI serial).
+ 
+ [Fix]
+ 
+ Enable CONFIG_SERIAL_8250_MID=y.
+ 
+ [Regression potential]
+ 
+ Kernel footprint is increased a bit with this change (around +9K), so we
+ may see little performance regressions at boot time in really small
+ platforms (additional memory usage is probably negligible), but it is
+ worth it, otherwise we won't be able to properly support these
+ platforms.
+ 
+ NOTE: we may want to disable this option in the could kernels and
+ derivatives and keep it only for the generic.
+ 
+ [Original bug report]
+ 
  Starting from 5.19 HWE kernel, this option became as dedicated module instead 
of being compiled into the kernel.
  5.19 hwe-next also has CONFIG_SERIAL_8250_MID=m
  On 5.15 it was OK
  
  ~$ uname -r
  5.19.0-32-generic
  $ cat /boot/config-5.19.0-32-generic  | grep 8250_MID
  CONFIG_SERIAL_8250_MID=m
  
  Please make it CONFIG_SERIAL_8250_MID=y for all the future kernels.
  
  Previous ticket: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967338
  Some discussion: 
https://lists.ubuntu.com/archives/kernel-team/2022-March/128690.html
  
  Thanks!

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

Title:
  linux: CONFIG_SERIAL_8250_MID=y

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Kinetic:
  New
Status in linux source package in Lunar:
  Confirmed

Bug description:
  [Impact]

  CONFIG_SERIAL_8250_MID=y is required to properly use the serial
  console on some platforms that are using the "mid" serial driver (such
  as some Intel SoC platforms).

  The generic kernel should build this driver statically to make sure we
  properly support these platforms.

  [Test case]

  Boot the Ubuntu generic kernel on a system that is using the "mid"
  serial driver (e.g, no PCI serial).

  [Fix]

  Enable CONFIG_SERIAL_8250_MID=y.

  [Regression potential]

  Kernel footprint is increased a bit with this change (around +9K), so
  we may see little performance regressions at boot time in really small
  platforms (additional memory usage is probably negligible), but it is
  worth it, otherwise we won't be able to properly support these
  platforms.

  NOTE: we may want to disable this option in the could kernels and
  derivatives and keep it only for the generic.

  [Original bug report]

  Starting from 5.19 HWE kernel, this option became as dedicated module instead 
of being compiled into the kernel.
  5.19 hwe-next also has CONFIG_SERIAL_8250_MID=m
  On 5.15 it was OK

  ~$ uname -r
  5.19.0-32-generic
  $ cat /boot/config-5.19.0-32-generic  | grep 8250_MID
  CONFIG_SERIAL_8250_MID=m

  Please make it CONFIG_SERIAL_8250_MID=y for all the future kernels.

  Previous ticket: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967338
  Some discussion: 
https://lists.ubuntu.com/archives/kernel-team/2022-March/128690.html

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009283/+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 1988836] Autopkgtest regression report (linux-restricted-modules-aws/5.15.0-1032.36)

All autopkgtests for the newly accepted linux-restricted-modules-aws 
(5.15.0-1032.36) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-aws

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

Thank you!

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

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-aws/5.15.0-1032.36)

All autopkgtests for the newly accepted linux-restricted-modules-aws 
(5.15.0-1032.36) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-aws

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

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

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

lttng-modules/2.13.1-1ubuntu0.22.04.3 (amd64, arm64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2007001] Re: Blank console display with aarch64 kernel 5.19.0-31

2023-03-10 Thread Paul Rockwell

Kernel logging shows that the vmwgfx driver encounters an error when
loading. The error indicates that a memory range could not be acquired
by the driver. The error is eerily similar to
https://bugzilla.kernel.org/show_bug.cgi?id=215678 which was fixed in
kernel source in 5.19.

The behavior seen in this kernel is a regression to past kernel version
behavior. Is there anyone at Ubuntu that would care to look at this
issue? It's been crickets for over a month.

** Bug watch added: Linux Kernel Bug Tracker #215678
   https://bugzilla.kernel.org/show_bug.cgi?id=215678

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

Title:
  Blank console display with aarch64 kernel 5.19.0-31

Status in linux package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-5.19 package in Ubuntu:
  New

Bug description:
  Upgraded the kernel on 22.10 aarch64 (running in a VM on VMware Fusion
  13.0.1 on Apple Silicon_ from 5.19.0-29 to 5.19.0-31. After the
  upgrade and after rebooting the VM no text or graphical console
  appears on the VM.

  The VM is running and can be accessed through SSH.

  Rebooting the VM with kernel 5.19.0-29 - everything is working as
  expected. Text and graphical consoles now display properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-31-generic 5.19.0-31.32
  ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17
  Uname: Linux 5.19.0-31-generic aarch64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: arm64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Sat Feb 11 13:04:22 2023
  InstallationDate: Installed on 2022-09-11 (153 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha arm64 (20220911)
  IwConfig:
   lono wireless extensions.
   
   ens160no wireless extensions.
  MachineType: VMware, Inc. VMware20,1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic 
root=UUID=5e9795ee-63e3-4df1-93e9-c36cd88c726c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-31-generic N/A
   linux-backports-modules-5.19.0-31-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2022
  dmi.bios.vendor: VMware, Inc.
  dmi.bios.version: VMW201.00V.20904234.BA64.2212051119
  dmi.board.name: VBSA
  dmi.board.vendor: VMware, Inc.
  dmi.board.version: 1
  dmi.chassis.type: 1
  dmi.chassis.vendor: VMware, Inc.
  dmi.chassis.version: VMware20,1
  dmi.modalias: 
dmi:bvnVMware,Inc.:bvrVMW201.00V.20904234.BA64.2212051119:bd12/05/2022:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001:
  dmi.product.family: VMware
  dmi.product.name: VMware20,1
  dmi.product.sku: 0001
  dmi.product.version: 1
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007001/+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 2010997] [NEW] Pull-Request to address USB and PWM cooling fan issues with Orin HW

2023-03-10 Thread Brad Figg

Public bug reported:

 [Impact]
Adding this patch addresses a specific audio issue with the nvidia-tegra 
kernel.

https://bugs.launchpad.net/riverside/+bug/2009867
https://bugs.launchpad.net/riverside/+bug/2002173

 [Fix]
The PR is made up of a revert of one commit and the application of 4 new 
patches from upstream to address the indicated issues.

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

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

Title:
  Pull-Request to address USB and PWM cooling fan issues with Orin HW

Status in linux-nvidia package in Ubuntu:
  New

Bug description:
   [Impact]
  Adding this patch addresses a specific audio issue with the nvidia-tegra 
kernel.

  https://bugs.launchpad.net/riverside/+bug/2009867
  https://bugs.launchpad.net/riverside/+bug/2002173

   [Fix]
  The PR is made up of a revert of one commit and the application of 4 new 
patches from upstream to address the indicated issues.

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


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

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

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

linux-nvidia/5.15.0-1018.18 (amd64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-aws/5.15.0-1032.36+1)

All autopkgtests for the newly accepted linux-restricted-modules-aws 
(5.15.0-1032.36+1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-aws

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2011226] [NEW] Focal update: v5.4.231 upstream stable release

2023-03-10 Thread Luke Nowakowski-Krijger

Public bug reported:

SRU Justification

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

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

clk: generalize devm_clk_get() a bit
clk: Provide new devm_clk helpers for prepared and enabled clocks
memory: atmel-sdramc: Fix missing clk_disable_unprepare in atmel_ramc_probe()
memory: mvebu-devbus: Fix missing clk_disable_unprepare in mvebu_devbus_probe()
ARM: dts: imx6qdl-gw560x: Remove incorrect 'uart-has-rtscts'
ARM: imx27: Retrieve the SYSCTRL base address from devicetree
ARM: imx31: Retrieve the IIM base address from devicetree
ARM: imx35: Retrieve the IIM base address from devicetree
ARM: imx: add missing of_node_put()
HID: intel_ish-hid: Add check for ishtp_dma_tx_map
EDAC/highbank: Fix memory leak in highbank_mc_probe()
tomoyo: fix broken dependency on *.conf.default
RDMA/core: Fix ib block iterator counter overflow
IB/hfi1: Reject a zero-length user expected buffer
IB/hfi1: Reserve user expected TIDs
IB/hfi1: Fix expected receive setup error exit issues
affs: initialize fsdata in affs_truncate()
amd-xgbe: TX Flow Ctrl Registers are h/w ver dependent
amd-xgbe: Delay AN timeout during KR training
bpf: Fix pointer-leak due to insufficient speculative store bypass mitigation
phy: rockchip-inno-usb2: Fix missing clk_disable_unprepare() in 
rockchip_usb2phy_power_on()
net: nfc: Fix use-after-free in local_cleanup()
net: wan: Add checks for NULL for utdm in undo_uhdlc_init and unmap_si_regs
gpio: mxc: Always set GPIOs used as interrupt source to INPUT mode
net/sched: sch_taprio: fix possible use-after-free
net: fix a concurrency bug in l2tp_tunnel_register()
l2tp: Serialize access to sk_user_data with sk_callback_lock
l2tp: Don't sleep and disable BH under writer-side sk_callback_lock
net: usb: sr9700: Handle negative len
net: mdio: validate parameter addr in mdiobus_get_phy()
HID: check empty report_list in hid_validate_values()
HID: check empty report_list in bigben_probe()
net: stmmac: fix invalid call to mdiobus_get_phy()
HID: revert CHERRY_MOUSE_000C quirk
usb: gadget: f_fs: Prevent race during ffs_ep0_queue_wait
usb: gadget: f_fs: Ensure ep0req is dequeued before free_request
net: mlx5: eliminate anonymous module_init & module_exit
drm/panfrost: fix GENERIC_ATOMIC64 dependency
dmaengine: Fix double increment of client_count in dma_chan_get()
net: macb: fix PTP TX timestamp failure due to packet padding
HID: betop: check shape of output reports
dmaengine: xilinx_dma: use devm_platform_ioremap_resource()
dmaengine: xilinx_dma: Fix devm_platform_ioremap_resource error handling
dmaengine: xilinx_dma: call of_node_put() when breaking out of 
for_each_child_of_node()
tcp: avoid the lookup process failing to get sk in ehash table
w1: fix deadloop in __w1_remove_master_device()
w1: fix WARNING after calling w1_process()
driver core: Fix test_async_probe_init saves device in wrong array
net: dsa: microchip: ksz9477: port map correction in ALU table entry register
tcp: fix rate_app_limited to default to 1
cpufreq: Add Tegra234 to cpufreq-dt-platdev blocklist
ASoC: fsl_micfil: Correct the number of steps on SX controls
drm: Add orientation quirk for Lenovo ideapad D330-10IGL
s390/debug: add _ASM_S390_ prefix to header guard
cpufreq: armada-37xx: stop using 0 as NULL pointer
ASoC: fsl_ssi: Rename AC'97 streams to avoid collisions with AC'97 CODEC
ASoC: fsl-asoc-card: Fix naming of AC'97 CODEC widgets
spi: spidev: remove debug messages that access spidev->spi without locking
KVM: s390: interrupt: use READ_ONCE() before cmpxchg()
scsi: hisi_sas: Set a port invalid only if there are no devices attached when 
refreshing port id
platform/x86: touchscreen_dmi: Add info for the CSL Panther Tab HD
platform/x86: asus-nb-wmi: Add alternate mapping for KEY_SCREENLOCK
lockref: stop doing cpu_relax in the cmpxchg loop
mmc: sdhci-esdhc-imx: clear pending interrupt and halt cqhci
mmc: sdhci-esdhc-imx: disable the CMD CRC check for standard tuning
mmc: sdhci-esdhc-imx: correct the tuning start tap and step setting
netfilter: conntrack: do not renew entry stuck in tcp SYN_SENT state
fs: reiserfs: remove useless new_opts in reiserfs_remount
Bluetooth: hci_sync: cancel cmd_timer if hci_open failed
scsi: hpsa: Fix allocation size for scsi_host_alloc()
module: Don't wait for GOING modules
tracing: Make sure trace_printk() can output as soon as it can be used
trace_events_hist: add check for return value of 'create_hist_field'
ftrace/scripts: Update the instructions for ftrace-bisect.sh
cifs: Fix oops due to uncleared server->smbd_conn in reconnect
KVM: x86/vmx: Do not skip segment attributes

[Kernel-packages] [Bug 2011226] Re: Focal update: v5.4.231 upstream stable release

2023-03-10 Thread Luke Nowakowski-Krijger

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v5.4.231 upstream stable release
+    from git://git.kernel.org/
  
-v5.4.231 upstream stable release
-from git://git.kernel.org/
+ clk: generalize devm_clk_get() a bit
+ clk: Provide new devm_clk helpers for prepared and enabled clocks
+ memory: atmel-sdramc: Fix missing clk_disable_unprepare in atmel_ramc_probe()
+ memory: mvebu-devbus: Fix missing clk_disable_unprepare in 
mvebu_devbus_probe()
+ ARM: dts: imx6qdl-gw560x: Remove incorrect 'uart-has-rtscts'
+ ARM: imx27: Retrieve the SYSCTRL base address from devicetree
+ ARM: imx31: Retrieve the IIM base address from devicetree
+ ARM: imx35: Retrieve the IIM base address from devicetree
+ ARM: imx: add missing of_node_put()
+ HID: intel_ish-hid: Add check for ishtp_dma_tx_map
+ EDAC/highbank: Fix memory leak in highbank_mc_probe()
+ tomoyo: fix broken dependency on *.conf.default
+ RDMA/core: Fix ib block iterator counter overflow
+ IB/hfi1: Reject a zero-length user expected buffer
+ IB/hfi1: Reserve user expected TIDs
+ IB/hfi1: Fix expected receive setup error exit issues
+ affs: initialize fsdata in affs_truncate()
+ amd-xgbe: TX Flow Ctrl Registers are h/w ver dependent
+ amd-xgbe: Delay AN timeout during KR training
+ bpf: Fix pointer-leak due to insufficient speculative store bypass mitigation
+ phy: rockchip-inno-usb2: Fix missing clk_disable_unprepare() in 
rockchip_usb2phy_power_on()
+ net: nfc: Fix use-after-free in local_cleanup()
+ net: wan: Add checks for NULL for utdm in undo_uhdlc_init and unmap_si_regs
+ gpio: mxc: Always set GPIOs used as interrupt source to INPUT mode
+ net/sched: sch_taprio: fix possible use-after-free
+ net: fix a concurrency bug in l2tp_tunnel_register()
+ l2tp: Serialize access to sk_user_data with sk_callback_lock
+ l2tp: Don't sleep and disable BH under writer-side sk_callback_lock
+ net: usb: sr9700: Handle negative len
+ net: mdio: validate parameter addr in mdiobus_get_phy()
+ HID: check empty report_list in hid_validate_values()
+ HID: check empty report_list in bigben_probe()
+ net: stmmac: fix invalid call to mdiobus_get_phy()
+ HID: revert CHERRY_MOUSE_000C quirk
+ usb: gadget: f_fs: Prevent race during ffs_ep0_queue_wait
+ usb: gadget: f_fs: Ensure ep0req is dequeued before free_request
+ net: mlx5: eliminate anonymous module_init & module_exit
+ drm/panfrost: fix GENERIC_ATOMIC64 dependency
+ dmaengine: Fix double increment of client_count in dma_chan_get()
+ net: macb: fix PTP TX timestamp failure due to packet padding
+ HID: betop: check shape of output reports
+ dmaengine: xilinx_dma: use devm_platform_ioremap_resource()
+ dmaengine: xilinx_dma: Fix devm_platform_ioremap_resource error handling
+ dmaengine: xilinx_dma: call of_node_put() when breaking out of 
for_each_child_of_node()
+ tcp: avoid the lookup process failing to get sk in ehash table
+ w1: fix deadloop in __w1_remove_master_device()
+ w1: fix WARNING after calling w1_process()
+ driver core: Fix test_async_probe_init saves device in wrong array
+ net: dsa: microchip: ksz9477: port map correction in ALU table entry register
+ tcp: fix rate_app_limited to default to 1
+ cpufreq: Add Tegra234 to cpufreq-dt-platdev blocklist
+ ASoC: fsl_micfil: Correct the number of steps on SX controls
+ drm: Add orientation quirk for Lenovo ideapad D330-10IGL
+ s390/debug: add _ASM_S390_ prefix to header guard
+ cpufreq: armada-37xx: stop using 0 as NULL pointer
+ ASoC: fsl_ssi: Rename AC'97 streams to avoid collisions with AC'97 CODEC
+ ASoC: fsl-asoc-card: Fix naming of AC'97 CODEC widgets
+ spi: spidev: remove debug messages that access spidev->spi without locking
+ KVM: s390: interrupt: use READ_ONCE() before cmpxchg()
+ scsi: hisi_sas: Set a port invalid only if there are no devices attached when 
refreshing port id
+ platform/x86: touchscreen_dmi: Add info for the CSL Panther Tab HD
+ platform/x86: asus-nb-wmi: Add alternate mapping for KEY_SCREENLOCK
+ lockref: stop doing cpu_relax in the cmpxchg loop
+ mmc: sdhci-esdhc-imx: clear pending interrupt and halt cqhci
+ mmc: sdhci-esdhc-

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

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

lttng-modules/2.13.1-1ubuntu0.22.04.3 (amd64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2008142] Re: bcmwl driver not installed

2023-03-10 Thread Brian Murray

If that (not being able to use the new desktop installer with bcmwl) is
the case then we should document this in the release notes for Lunar
Lobster.

** Also affects: ubuntu-release-notes
   Importance: Undecided
   Status: New

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

Title:
  bcmwl driver not installed

Status in ubuntu-desktop-installer:
  New
Status in Release Notes for Ubuntu:
  New
Status in broadcom-sta package in Ubuntu:
  New
Status in subiquity package in Ubuntu:
  New
Status in broadcom-sta source package in Lunar:
  New
Status in subiquity source package in Lunar:
  Won't Fix

Bug description:
  I was testing an installation in qemu and shared a broadcom wireless
  device with the virtual machine and the drivers for it were not
  installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ubuntu-desktop-installer (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.24.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 22 16:23:38 2023
  InstallationDate: Installed on 2023-02-23 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230221)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-desktop-installer
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2008142/+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 2010997] Re: Pull-Request to address USB and PWM cooling fan issues with Orin HW

2023-03-10 Thread Brad Figg

** Description changed:

-  [Impact]
- Adding this patch addresses a specific audio issue with the nvidia-tegra 
kernel.
+ [Impact]
+ Adding this patch addresses USB and PWM cooling fan issues as described 
in the following bugs:
  
- https://bugs.launchpad.net/riverside/+bug/2009867
- https://bugs.launchpad.net/riverside/+bug/2002173
+ https://bugs.launchpad.net/riverside/+bug/2009867
+ https://bugs.launchpad.net/riverside/+bug/2002173
  
-  [Fix]
- The PR is made up of a revert of one commit and the application of 4 new 
patches from upstream to address the indicated issues.
+  [Fix]
+ The PR is made up of a revert of one commit and the application of 4 new 
patches from upstream to address the indicated issues.

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

Title:
  Pull-Request to address USB and PWM cooling fan issues with Orin HW

Status in linux-nvidia package in Ubuntu:
  New

Bug description:
  [Impact]
  Adding this patch addresses USB and PWM cooling fan issues as described 
in the following bugs:

  https://bugs.launchpad.net/riverside/+bug/2009867
  https://bugs.launchpad.net/riverside/+bug/2002173

   [Fix]
  The PR is made up of a revert of one commit and the application of 4 new 
patches from upstream to address the indicated issues.

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


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

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

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

linux-gke/5.15.0-1029.34 (amd64, arm64)
lttng-modules/2.13.1-1ubuntu0.22.04.3 (amd64, arm64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 1991285] Re: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

2023-03-10 Thread Steve Langasek

To proceed with this SRU, I would like to have some analysis of what
makes this an armhf-only failure.  Is it to do with the fact that armhf
autopkgtests run in a container and others do not?  If so, it seems to
me that a more correct fix for the test is to detect that we're running
in a container instead of querying the arch.

** Changed in: systemd (Ubuntu Focal)
   Status: Triaged => 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/1991285

Title:
  systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  New
Status in systemd source package in Focal:
  Incomplete

Bug description:
  [Impact]
  The armhf autopkgtests currently fail in Focal due to this, and failures are 
not marked as regressions. This limits our ability to catch other regressions 
on armhf.

  [Test Plan]
  The boot-and-services autopkgtest should not fail on armhf. Specifically, the 
test_no_failed test should ignore systemd-remount-fs.service failures on armhf 
only.

  [Where problems could occur]
  The fix is limited to the boot-and-services autopkgtest, so there is limited 
risk. Any bugs would show up in that test.

  [Original Description]

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

  Testing failed on:
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+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 2010924] [NEW] MT7921K --> BLE funktion don't working

You have been subscribed to a public bug:

Hi,
i have MT7921K BT chip that BLE function is not working with linux, but normal 
BT is working.
I try several distros and some live-iso and get same effect. BLE just not 
working with this device.
I have other BT adapters and BLE is working for them.
This is a probe for my PC:
https://linux-hardware.org/?probe=969ab4279f

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


** Tags: bot-comment
-- 
MT7921K --> BLE funktion don't working
https://bugs.launchpad.net/bugs/2010924
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to bluez in Ubuntu.

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

[Kernel-packages] [Bug 2010924] Re: MT7921K --> BLE funktion don't working

2023-03-10 Thread death

It's the kernel driver itself: mt7921
It's missing BLE support for this device.
On Windows BLE is working.

I really don't know witch one is the driver for bluetooth function for this 
device, because it's Wi-fi + BT 5.2 combo. Found in AMD Wi-Fi 6E RZ608 
(MediaTek MT7921K)
In this MB: X570S AORUS ELITE AX (rev. 1.1) 
And this wi-fi + BT combo are found in all new MB with integrated wi-fi + BT 
combos.

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

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

Title:
  MT7921K --> BLE funktion don't working

Status in bluez package in Ubuntu:
  New

Bug description:
  Hi,
  i have MT7921K BT chip that BLE function is not working with linux, but 
normal BT is working.
  I try several distros and some live-iso and get same effect. BLE just not 
working with this device.
  I have other BT adapters and BLE is working for them.
  This is a probe for my PC:
  https://linux-hardware.org/?probe=969ab4279f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2010924/+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 1914774] Re: Some derivative kernel tools packages don't depend on linux-tools-common

2023-03-10 Thread Ubuntu Kernel Bot

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

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

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


** Tags added: kernel-spammed-bionic-linux-hwe-5.4 verification-needed-bionic

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

Title:
  Some derivative kernel tools packages don't depend on linux-tools-
  common

Status in linux-hwe-5.4 package in Ubuntu:
  Invalid
Status in linux-ibm package in Ubuntu:
  Invalid
Status in linux-ibm-5.4 package in Ubuntu:
  Invalid
Status in linux-hwe-5.4 source package in Bionic:
  Fix Committed
Status in linux-ibm-5.4 source package in Bionic:
  Fix Committed
Status in linux-ibm source package in Focal:
  Fix Committed
Status in linux-ibm source package in Jammy:
  Fix Released
Status in linux-ibm source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  Installing the tools package for some kernels, like linux-tools-
  generic-hwe-18.04, does not install linux-tools-common because of a
  missing dependency. This results in missing /usr/bin/* wrapper scripts
  that call the version dependent binaries (like cpupower).

  [Test Case]

  Install like linux-tools-generic-hwe-18.04 on bionic and:
  $ cpupower
  cpupower: command not found

  
  [Fix]

  Add linux-tools-common as a dependency.

  
  [Regression Potential]

  The fix results in an additional package being installed. If something
  goes wrong this would manifest itself as a package installation error.

  
  [Original Description]

  While running kernel 5.4.0-64 today on bionic I noticed that Canonical
  kernel team does not provide a linux-hwe-5.4-tools package.  Is that a
  deliberate choice?  If so, would you please share the reason?

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


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

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

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

dm-writeboost/2.2.13-1ubuntu2 (amd64, arm64)
systemd/249.11-0ubuntu3.7 (arm64)
dpdk-kmods/0~20220111+git-1ubuntu1~22.04.1 (amd64, arm64)
rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu17~22.04.1 (amd64, arm64)
lttng-modules/2.13.1-1ubuntu0.22.04.3 (amd64, arm64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2002253] Re: 5.15.0-57

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

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

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

Title:
  5.15.0-57

Status in linux package in Ubuntu:
  Expired

Bug description:
  Can't shutdown. Restart after a few seconds...Linux Mint 21.1

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

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

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

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

Title:
  5.4.0.136

Status in linux package in Ubuntu:
  Expired

Bug description:
  Can't shutdown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002191/+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 2002105] Re: 5.15.0-57 update breaks arrow (mouse) movement in some games (steam through proton)

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

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

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

Title:
  5.15.0-57 update breaks arrow (mouse) movement in some games (steam
  through proton)

Status in linux package in Ubuntu:
  Expired

Bug description:
  Since this update 5.15.0-57 the cursor movement in some of the games I
  play is broken. For example in Supreme Commander 2 the arrow vanishes
  for a split second and reappears in the next split second, while
  moving the mouse.

  The problem is not there when I revert to 5.15.0-56.

  I can't give any other information to help.

  I didn't noticed this behavior in desktop apps at the moment.

  My system info: https://docs.google.com/document/d/1yYK4Rx4Mu-
  XeaO9YiiDxI79BS17ge_5pYAdPank6K84/edit?usp=sharing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002105/+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 2001724] Re: No sound output from internal speaker of HP HP ENVY x360 2-in-1 Laptop 13-bf0xxx

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

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

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

Title:
  No sound output from internal speaker of HP HP ENVY x360 2-in-1 Laptop
  13-bf0xxx

Status in linux package in Ubuntu:
  Expired

Bug description:
  No sound output from internal speakers but Headphones works fine. No 
crackling nothing comes out of internal speakers.
  It's a dualboot system with Windows 11, on windows speakers works fine.

  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  
  lspic -v
  Audio Device:
  00:1f.3 Multimedia audio controller: Intel Corporation Device 51cc (rev 01)
Subsystem: Hewlett-Packard Company Device 8a28
Flags: bus master, fast devsel, latency 32, IRQ 190, IOMMU group 19
Memory at 603e19 (64-bit, non-prefetchable) [size=16K]
Memory at 603e00 (64-bit, non-prefetchable) [size=1M]
Capabilities: [50] Power Management version 3
Capabilities: [80] Vendor Specific Information: Len=14 
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Kernel driver in use: sof-audio-pci-intel-tgl
Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0

  inxi -Aaz
  Audio:
Device-1: Intel vendor: Hewlett-Packard driver: intel-ipu6
  alternate: intel_ipu6,intel_ipu6_isys,intel_ipu6_psys bus-ID: 00:05.0
  chip-ID: 8086:465d class-ID: 0480
Device-2: Intel vendor: Hewlett-Packard driver: sof-audio-pci-intel-tgl
  alternate: snd_hda_intel,snd_sof_pci_intel_tgl bus-ID: 00:1f.3
  chip-ID: 8086:51cc class-ID: 0401
Sound Server-1: ALSA v: k5.15.0-56-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes


  sudo dmesg | grep "audio"

  [3.459050] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI 
class/subclass/prog-if info 0x040100
  [3.459073] sof-audio-pci-intel-tgl :00:1f.3: Digital mics found on 
Skylake+ platform, using SOF driver
  [3.459093] sof-audio-pci-intel-tgl :00:1f.3: enabling device ( -> 
0002)
  [3.459336] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI 
class/subclass/prog-if 0x040100
  [4.121423] Modules linked in: btusb(+) btrtl btbcm btintel bluetooth 
ecdh_generic ecc overlay snd_soc_dmic snd_sof_pci_intel_tgl 
snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation 
soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof 
snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi 
soundwire_bus ledtrig_audio intel_ipu6_psys snd_soc_core intel_tcc_cooling 
snd_compress ac97_bus x86_pkg_temp_thermal snd_pcm_dmaengine intel_powerclamp 
coretemp snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec 
intel_ipu6_isys snd_hda_core videobuf2_dma_contig kvm_intel snd_hwdep joydev 
videobuf2_memops binfmt_misc videobuf2_v4l2 kvm videobuf2_common mei_hdcp 
intel_rapl_msr snd_pcm i915(+) crct10dif_pclmul ghash_clmulni_intel 
snd_seq_midi aesni_intel snd_seq_midi_event iwlmvm crypto_simd cryptd rapl 
snd_rawmidi ttm hid_sensor_gyro_3d input_leds hp_wmi hid_sensor_rotation 
hid_sensor_custom_intel_hinge hid_sensor_als
  [5.545603] sof-audio-pci-intel-tgl :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [5.622395] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode
  [5.655171] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 5
  [5.655175] sof-audio-pci-intel-tgl :00:1f.3: using HDA machine driver 
skl_hda_dsp_generic now
  [5.655180] sof-audio-pci-intel-tgl :00:1f.3: DMICs detected in NHLT 
tables: 2
  [5.656008] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 
2:0:0-b678a
  [5.656011] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:20:0 
Kernel ABI 3:18:0
  [5.656014] sof-audio-pci-intel-tgl :00:1f.3: warn: FW ABI is more 
recent than kernel
  [5.656018] sof-audio-pci-intel-tgl :00:1f.3: unknown sof_ext_man 
header type 3 size 0x30
  [5.768068] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 
2:0:0-b678a
  [5.768072] sof-audio-pci-inte

[Kernel-packages] [Bug 2001545] Re: i915: repetable Kernel Oops after resuming from standby

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

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

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

Title:
  i915: repetable Kernel Oops after resuming from standby

Status in linux package in Ubuntu:
  Expired

Bug description:
  I have an Intel i915 Haswell system which - after upgrading from
  Ubuntu 20.04 to 22.04 - experiences repeated crashes when resuming
  from hibernation.

  Unfortunately, "ubuntu-bug" claims my kernel package is "not an
  official package" (which is untrue, at least to my knowledge - I
  installed from the official sources) so I cannot use 'ubuntu-bug'.

  $ cat /proc/version_signature 
  Ubuntu 5.15.0-56.62-generic 5.15.64

  I will attach the lspci output.

  This is the dmesg trace:

  Jan  3 17:16:33 linuxkiste kernel: [164294.599802] BUG: unable to handle page 
fault for address: e2fc5108
  Jan  3 17:16:33 linuxkiste kernel: [164294.599809] #PF: supervisor read 
access in kernel mode
  Jan  3 17:16:33 linuxkiste kernel: [164294.599811] #PF: error_code(0x) - 
not-present page
  Jan  3 17:16:33 linuxkiste kernel: [164294.599813] PGD 0 P4D 0
  Jan  3 17:16:33 linuxkiste kernel: [164294.599815] Oops:  [#1] SMP PTI
  Jan  3 17:16:33 linuxkiste kernel: [164294.599818] CPU: 1 PID: 93586 Comm: 
chrome Tainted: G   OE 5.15.0-56-generic #62-Ubuntu
  Jan  3 17:16:33 linuxkiste kernel: [164294.599820] Hardware name: MSI 
MS-7817/CSM-B85M-E45 (MS-7817), BIOS V10.9 04/21/2015
  Jan  3 17:16:33 linuxkiste kernel: [164294.599822] RIP: 0010:kfree+0x68/0x250
  Jan  3 17:16:33 linuxkiste kernel: [164294.599827] Code: 80 49 01 dc 0f 82 f2 
01 00 00 48 c7 c0 00 00 00 80 48 2b 05 42 63 39 01 49 01 c4 49 c1 ec 0c 49 c1 
e4 06 4c 03 25 20 63 39 01 <49> 8b 44 24 08 48 8d 50 ff a8 01 4c 0f 45 e2 49 8b 
54 24 08 48 8d
  Jan  3 17:16:33 linuxkiste kernel: [164294.599829] RSP: 0018:b98e88c47930 
EFLAGS: 00010286
  Jan  3 17:16:33 linuxkiste kernel: [164294.599831] RAX: 6bf38000 RBX: 
40c0 RCX: 00392c14
  Jan  3 17:16:33 linuxkiste kernel: [164294.599833] RDX: b98e8000 RSI: 
a04d669e RDI: 40c0
  Jan  3 17:16:33 linuxkiste kernel: [164294.599834] RBP: b98e88c47970 R08: 
 R09: 
  Jan  3 17:16:33 linuxkiste kernel: [164294.599835] R10: 940e24fc1000 R11: 
940e090c5ad4 R12: e2fc5100
  Jan  3 17:16:33 linuxkiste kernel: [164294.599836] R13: 000a R14: 
 R15: 0230
  Jan  3 17:16:33 linuxkiste kernel: [164294.599837] FS:  
7f3c96764340() GS:94100ea8() knlGS:
  Jan  3 17:16:33 linuxkiste kernel: [164294.599839] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  3 17:16:33 linuxkiste kernel: [164294.599840] CR2: e2fc5108 CR3: 
0001f49d8001 CR4: 001706e0
  Jan  3 17:16:33 linuxkiste kernel: [164294.599842] Call Trace:
  Jan  3 17:16:33 linuxkiste kernel: [164294.599843]  
  Jan  3 17:16:33 linuxkiste kernel: [164294.599845]  kvfree+0x2e/0x40
  Jan  3 17:16:33 linuxkiste kernel: [164294.599850]  
eb_relocate_parse_slow+0x133/0x470 [i915]
  Jan  3 17:16:33 linuxkiste kernel: [164294.599937]  
eb_relocate_parse+0x129/0x1b0 [i915]
  Jan  3 17:16:33 linuxkiste kernel: [164294.69]  
i915_gem_do_execbuffer+0x373/0xba0 [i915]
  Jan  3 17:16:33 linuxkiste kernel: [164294.600083]  ? 
__alloc_pages+0x311/0x330
  Jan  3 17:16:33 linuxkiste kernel: [164294.600088]  ? 
i915_memcpy_init_early+0x40/0x40 [i915]
  Jan  3 17:16:33 linuxkiste kernel: [164294.600140]  
i915_gem_execbuffer2_ioctl+0x12e/0x280 [i915]
  Jan  3 17:16:33 linuxkiste kernel: [164294.600200]  ? 
i915_gem_do_execbuffer+0xba0/0xba0 [i915]
  Jan  3 17:16:33 linuxkiste kernel: [164294.600256]  
drm_ioctl_kernel+0xb3/0x100 [drm]
  Jan  3 17:16:33 linuxkiste kernel: [164294.600290]  drm_ioctl+0x268/0x4b0 
[drm]
  Jan  3 17:16:33 linuxkiste kernel: [164294.600308]  ? 
i915_gem_do_execbuffer+0xba0/0xba0 [i915]
  Jan  3 17:16:33 linuxkiste kernel: [164294.600367]  ? 
__check_object_size.part.0+0x3a/0x150
  Jan  3 17:16:33 linuxkiste kernel: [164294.600372]  ? __fget_files+0x86/0xc0
  Jan  3 17:16:33 linuxkiste kernel: [164294.600376]  __x64_sys_ioctl+0x95/0xd0
  Jan  3 17:16:33 linuxkiste kernel: [164294.600379]  do_syscall_64+0x5c/0xc0
  Jan  3 17:16:33 linuxkiste kernel: [164294.600383]  ? __fget_files+0x86/0xc0
  Jan  3 17:16:33 linuxkiste kernel: [164294.600386]  ? fput+0x13/0x20
  Jan  3 17:16:33 linuxkiste kernel: [164294.600388]  ? 
exit_to_user_mode_prepare+0x37/0xb0
  Jan  3 17:16:33 linuxkiste kernel: [164294.600392]  ? 
syscall_exit_to_user_mode+0x27/0x50
  Jan  3 17:16:33 linuxkiste kernel: [164294.600395]  ? do_syscall_64+0x69/0xc0
  Jan  3 17:16:33 linuxkiste kernel: [164294.600397]  ? irqentry_exit+0x1d/0x

[Kernel-packages] [Bug 2000089] Re: Emulex FC driver fails to start HBA

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

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

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

Title:
  Emulex FC driver fails to start HBA

Status in linux package in Ubuntu:
  Expired

Bug description:
  Starting from linux hwe 5.15.0-53-generic ( and newer ) emulex FC (
  lpfc ) is no longer able to start the fibre channel on HPE ProLiant
  BL460c Gen10/ProLiant BL460c Gen10, BIOS I41 07/14/2022:

  [Wed Dec 14 21:32:01 2022] Call Trace:
  [Wed Dec 14 21:32:01 2022]  
  [Wed Dec 14 21:32:01 2022]  __const_udelay+0x40/0x50
  [Wed Dec 14 21:32:01 2022]  lpfc_sli4_wait_bmbx_ready+0x58/0x80 [lpfc]
  [Wed Dec 14 21:32:01 2022]  lpfc_sli4_post_sync_mbox+0xd4/0x4c0 [lpfc]
  [Wed Dec 14 21:32:01 2022]  ? __kmalloc+0x1ab/0x4b0
  [Wed Dec 14 21:32:01 2022]  lpfc_sli_issue_mbox_s4+0x58a/0x7d0 [lpfc]
  [Wed Dec 14 21:32:01 2022]  lpfc_sli_issue_mbox+0xf/0x20 [lpfc]
  [Wed Dec 14 21:32:01 2022]  lpfc_pci_function_reset+0xb9/0x270 [lpfc]
  [Wed Dec 14 21:32:01 2022]  ? raw_pci_write+0x27/0x50
  [Wed Dec 14 21:32:01 2022]  lpfc_sli4_brdreset+0x120/0x220 [lpfc]
  [Wed Dec 14 21:32:01 2022]  lpfc_sli_brdrestart_s4+0x4a/0x160 [lpfc]
  [Wed Dec 14 21:32:01 2022]  lpfc_sli_brdrestart+0x12/0x20 [lpfc]
  [Wed Dec 14 21:32:01 2022]  lpfc_reset_hba+0x3c/0xa0 [lpfc]
  [Wed Dec 14 21:32:01 2022]  lpfc_mbox_timeout_handler.cold+0x13f/0x14e [lpfc]
  [Wed Dec 14 21:32:01 2022]  lpfc_work_done+0x1c3/0x830 [lpfc]
  [Wed Dec 14 21:32:01 2022]  lpfc_do_work+0x5b/0x1a0 [lpfc]
  [Wed Dec 14 21:32:01 2022]  ? wait_woken+0x60/0x60
  [Wed Dec 14 21:32:01 2022]  ? lpfc_work_done+0x830/0x830 [lpfc]
  [Wed Dec 14 21:32:01 2022]  kthread+0x127/0x150
  [Wed Dec 14 21:32:01 2022]  ? set_kthread_struct+0x50/0x50
  [Wed Dec 14 21:32:01 2022]  ret_from_fork+0x1f/0x30
  [Wed Dec 14 21:32:01 2022]  
  [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: start 7 end 79 cnt 72
  [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 7: [   44.922753] 0:(0):0248 
Cancel Discovery Timer state x0 Data: x90010 x0 x0
  [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 8: [   44.922758] 0:(0):0339 
Abort xri x0, original iotag x800, abort cmd iotag x7ff retval x0
  [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 9: [   44.922761] 0:(0):0248 
Cancel Discovery Timer state x0 Data: x90010 x0 x0
  [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 10: [   44.922764] 0:(0):0011 
Free RPI x0 on ndlp: x9fb44f3be800 did xfe
  [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 11: [   44.922768] 0:(0):0211 
DSM in event xc on NPort xfe in state 0 rpi x Data: x0 x4
  [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 12: [   44.922770] 0:(0):0212 
DSM out state 0 on NPort xfe rpi x Data: x0 x4
  [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 13: [   44.922772] 0:(0):0211 
DSM in event xb on NPort xfe in state 0 rpi x Data: x0 x4
  [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 14: [   44.922775] 0:(0):0212 
DSM out state 255 on NPort xfe rpi x Data: x0 x4
  [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 15: [   45.030383] 0:(0):0248 
Cancel Discovery Timer state x0 Data: x90010 x0 x0
  [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 16: [   45.030396] 0:(0):0248 
Cancel Discovery Timer state x0 Data: x90010 x0 x0
  [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 17: [   45.030397] 0:0460 Bring 
Adapter offline
  [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 18: [   45.030399] 0:(0):0248 
Cancel Discovery Timer state x0 Data: x90010 x0 x0
  [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 19: [   45.046420] 0:1236 
Moving 66 buffers from pbl_pool[0] TO PUT list
  [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 20: [   45.046430] 0:1237 
Moving 0 buffers from pvt_pool[0] TO PUT list
  [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 21: [   45.046432] 0:1236 
Moving 66 buffers from pbl_pool[1] TO PUT list
  [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 22: [   45.046442] 0:1237 
Moving 0 buffers from pvt_pool[1] TO PUT list
  [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 23: [   45.046444] 0:1236 
Moving 66 buffers from pbl_pool[2] TO PUT list
  [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 24: [   45.046454] 0:1237 
Moving 0 buffers from pvt_pool[2] TO PUT list
  [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 25: [   45.046455] 0:1236 
Moving 66 buffers from pbl_pool[3] TO PUT list
  [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 26: [   45.046465] 0:1237 
Moving 0 buffers from pvt_pool[3] TO PUT list
  [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 27: [   45.046466] 0:1236 
Moving 66 buffers from pbl_pool[4] TO PUT list
  [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 28: [   45.046476] 0:1237 
Moving 0 buffers from pvt_pool[4] TO PUT list
  [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 29: [   45.046477] 0:1236 
Moving 66 buffers from pbl_pool[5] TO PUT list
  [Wed Dec 1

[Kernel-packages] [Bug 1999229] Re: mlx5 VF LAG flapping