@Chris,
82609c7) it looks like refactoring but also contains codes to make passive
police 1 as default.
the kernel part is also SRUed, LP1966089.
for this bug and 1982073, i cherry-picked some,these are essential and make
jammy-2.4.9 and 2.5.0 are almost identical.
~~~
| * 7486cdf - Ensure
Ok.
Sorry for the delay in getting to this.
There's a lot of code churn between 2.4.9 in Jammy and the 2.5 release,
a bunch of which appears to be refactoring rather than straight bugfixes
or new hardware support. It also appears to drop support for setting
something(?) via a msr and will
Hi Colin,
It's ext4:
ubuntu@riscv64-kinetic:~$ df -Th
Filesystem Type Size Used Avail Use% Mounted on
tmpfs tmpfs 794M 468K 794M 1% /run
/dev/vda1 ext420G 8.0G 11G 43% /
tmpfs tmpfs 3.9G 4.0K 3.9G 1% /dev/shm
tmpfs tmpfs 5.0M 0 5.0M
Here it is
** Attachment added: "journal"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992998/+attachment/5624984/+files/journal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Here it is
** Attachment added: "journal"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992998/+attachment/5624983/+files/journal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Workaround coming in mutter 43.1?
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2652
** Changed in: mutter (Ubuntu)
Status: Invalid => Fix Committed
** Tags added: fixed-upstream
** Tags added: fixed-in-mutter-43.1 fixed-in-nvidia-525
--
You received this bug notification
After reboot after the freeze, please run `journalctl -b -1 -k` and
attach its output here, 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/1992998
Title:
Kernel crash minute
** Changed in: linux (Ubuntu Kinetic)
Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1988797
Title:
pcieport
Sorry I did not meant f934bf3f57769282c371c978eb9bbe3930f6ed35 was the
offending commit.
This is just where I am at testing with git bisect.
There should need about 3 others steps to find the offending commit.
--
You received this bug notification because you are a member of Kernel
Packages,
tecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 18 09:55:27 2022
InstallationDate: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
ProcEnviron:
TERM=xterm-256color
P
Date: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no username)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: zsys
UpgradeStatus
64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 18 09:55:27 2022
InstallationDate: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Ubuntu 22.10
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 18 09:55:27 2022
InstallationDate: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no username)
XDG_RUNTIME_DIR=
LANG=en
The commit isn't related to HDMI audio though...
Can you please try
$ git checkout f934bf3f57769282c371c978eb9bbe3930f6ed35 # then compile and test
$ git checkout f934bf3f57769282c371c978eb9bbe3930f6ed35^ # then compile
and test
So we are sure it's the offending commit?
--
You received this
e: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no username)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: zsys
UpgradeStatus: No upgr
paul@rabachi:~/colinKernels/new4.9.180/my4.9.180$ git bisect log
git bisect start
# bad: [a5f56b52c878585b12b8bc37f737dcce4a660c64] Linux 4.9.178
git bisect bad a5f56b52c878585b12b8bc37f737dcce4a660c64
# good: [8baec4ebdf084961516f17cadbad14cac082ee4e] Linux 4.9.177
git bisect good
InstallationDate: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no username)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: zsys
Upgrade
pportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 18 09:55:27 2022
InstallationDate: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
ProcEnviron:
022
InstallationDate: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no username)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: zsys
Upg
I installed encrypted zfs kinetic 20221018 iso build.
Shut down the VM and made a copy of it, such that I can "first boot" all
day long.
On first boot, I added break=bottom command, and changed journald.conf
to use Storage=volatile, such that all logs remain in /run/log without
any
pportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 18 09:55:27 2022
InstallationDate: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
ProcEnviron:
TERM=xte
0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 18 09:55:27 2022
InstallationDate: Installed on 2022-10-18 (0 days ago)
InstallationMe
09:55:27 2022
InstallationDate: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no username)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage:
3.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 18 09:55:27 2022
InstallationDate: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
ProcEnviron:
TERM=xterm-256colo
bug present (HDMI audio deactivated, off) in kernel 6.0.1 from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.0.1/amd64/linux-
modules-6.0.1-060001-generic_6.0.1-060001.202210120833_amd64.deb
--
You received this bug notification because you are a member of Kernel
Packages, which is
Fresh install of kinetic 20221018 Ubuntu image, first boot, I see:
$ zfs list | grep -c pool/ROOT/ubuntu_
16
$ mount | grep -c pool/ROOT/ubuntu_
7
$
So have the mount points are not mounted as they are supposed to be.
As I was trying to log in on first boot, I also found that gdm flickered
off
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1993217/+attachment/5624944/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1993217/+attachment/5624943/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1993217/+attachment/5624945/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
bug present in vmlinuz-5.15.0-50
I admit I did not try 6.x kernels.
Searching in 4.9, because doing a git-bisect to find the offending
commit in that version.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1993217/+attachment/5624947/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1993217/+attachment/5624948/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1993217/+attachment/5624949/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1993217/+attachment/5624946/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1993217/+attachment/5624942/+files/PaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1993217/+attachment/5624941/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1993217/+attachment/5624940/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1993217/+attachment/5624937/+files/Lspci.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/1993217
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1993217/+attachment/5624936/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1993217/+attachment/5624939/+files/Lsusb.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/1993217
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1993217/+attachment/5624938/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "HookError_ubuntu.txt"
https://bugs.launchpad.net/bugs/1993217/+attachment/5624935/+files/HookError_ubuntu.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1993217/+attachment/5624934/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected apport-hook-error vanessa
** Description changed:
This is on my friend laptop with his TV.
HDMI audio not available in pavucontrol (profile say unplugged, unavailable)
in kernel versions with bugs.
It is just shown as an audio output
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1993217/+attachment/5624933/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1993217
i think it is redudant red herring, as since that patch was applied in
debian/ubuntu different upstream solution was already merged that
filters out locked zvolumes.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
pportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 18 09:55:27 2022
InstallationDate: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
ProcEnviron:
TERM=xte
:GNOME
Date: Tue Oct 18 09:55:27 2022
InstallationDate: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no username)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHE
Same on 5.15.0-52.
--
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/1992679
Title:
Can not login after new kernel installed (nvidia driver crashed)
Status in linux package in Ubuntu:
** 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
+
zcommon znvpair
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 18 09:55:27 2022
InstallationDate: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
Proc
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
portVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 18 09:55:27 2022
InstallationDate: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
ProcEnviro
u:GNOME
Date: Tue Oct 18 09:55:27 2022
InstallationDate: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no username)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/
tVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 18 09:55:27 2022
InstallationDate: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
ProcEnviron:
TERM=xterm-2
zcommon znvpair
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 18 09:55:27 2022
InstallationDate: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
ProcEnviron:
u:GNOME
Date: Tue Oct 18 09:55:27 2022
InstallationDate: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no username)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1993331
Title:
Blocking entire network when
** Changed in: linux-azure (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1987699
Title:
azure: CIFS Backport Updates to
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1054.61
---
linux-oem-5.14 (5.14.0-1054.61) focal; urgency=medium
* Packaging resync (LP: #1786013)
- [Config] Add PAHOLE_HAS_SPLIT_BTF config
* CVE-2022-2602
- SAUCE: io_uring/af_unix: defer registered files gc
This bug was fixed in the package linux-azure - 5.4.0-1094.100
---
linux-azure (5.4.0-1094.100) focal; urgency=medium
[ Ubuntu: 5.4.0-131.147 ]
* CVE-2022-2602
- SAUCE: io_uring/af_unix: defer registered files gc to io_uring release
- SAUCE: io_uring/af_unix: fix memleak
This bug was fixed in the package linux-azure - 5.4.0-1094.100
---
linux-azure (5.4.0-1094.100) focal; urgency=medium
[ Ubuntu: 5.4.0-131.147 ]
* CVE-2022-2602
- SAUCE: io_uring/af_unix: defer registered files gc to io_uring release
- SAUCE: io_uring/af_unix: fix memleak
heckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 18 09:55:27 2022
InstallationDate: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no username)
XDG_RUNTIME_DIR=
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 18 09:55:27 2022
InstallationDate: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
Date: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no username)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: zsys
UpgradeStatus: No upgrade
The bug is present in 6.0 but appears fixed in 6.1-rc1 and the current
kernel Git head. I've run 6.1-rc1 for several hours and noticed no
problems or error messages in dmesg. If there is interest in backporting
the fix, I can do a reverse bisect to find it.
--
You received this bug notification
Public bug reported:
My Dell laptop was connected to a Dell docking station.
The docking station has wired LAN connected to router.
Wifi is connected to wifi AP - which is connected to same router.
I chose to suspend the system by:
1. mouse click top right area with the battery icon
2. click
The problem does seem to have (at least) two separate causes:
1) Failure (during installation and updates) to recognize the hardware
and install the right kernel module(s)
2) Adverse interaction between OS components such that the kernel can
see and use the hardware, but HDMI audio is
Public bug reported:
nvidia-graphics-drivers-418-server reached its EOL, however it is the
last driver supporting certain GPU families. For this reason, to give
users some time to transition to newer GPUs, we would like to move the
driver to multiverse for now.
The driver should also be patched
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 18 09:55:27
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided =>
19.7
Uname: Linux 5.19.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 18 09:55:27 2022
InstallationDate: Installed on 2022-10-
Public bug reported:
SRU Justification
[Impact]
Current code produces a warning as shown below when total characters
in the constituent block device names plus the slashes exceeds 200.
snprintf() returns the number of characters generated from the given
input, which could cause the expression
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1993312
Public bug reported:
We have 2 physical servers on Ubuntu 22.04 with all the latest updates,
running on kernel 5.15.0-50-generic - “s23” (iSCSI target), and “s24”
(iSCSI initiator).
On s23 we setup a large amount of iSCSI targets (1024) using tgtd:
#!/bin/bash
[[ -z $TARGETS ]] && TARGETS=1024
** Tags added: verification-done-jammy
** Description changed:
[Impact]
Request to include below mpt3sas driver bug fix patches in Ubuntu 22.04
kernel. These patches got accepted by the upstream and please find the
corresponding commit IDs as below,
5db207d66d mpt3sas: Fix incorrect
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1993311
Title:
Kernel oops in Aquantia
For ease of reference here is the Ooops in demsg:
[ 10.010046]
[ 10.010337] UBSAN: array-index-out-of-bounds in
/build/linux-lU2d47/linux-5.15.0/drivers/net/ethernet/aquantia/atlantic/aq_nic.c:1262:48
[
Public bug reported:
This is a fresh install of Ubuntu 22.04 on a new Ryzen 7950X CPU and an
ASUS Motherboard.
Stephen
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-50-generic 5.15.0-50.56
ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
Uname: Linux
$ rmadison -a source -s kinetic-proposed linux-unstable linux-meta-
unstable linux-signed-unstable linux-restricted-modules-unstable linux-
restricted-signatures-unstable
$ rmadison -a source -s kinetic linux-unstable linux-meta-unstable
linux-signed-unstable linux-restricted-modules-unstable
Reviewed all packages for the kernel "source set" which contained the
indicated package. Mostly these are not even coherent sets that would
be installable. All now removed as requested.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
$ rmadison -a source -s kinetic-proposed linux-raspi2-5.4 linux-meta-
raspi2-5.4
$ rmadison -a source -s kinetic linux-raspi2-5.4 linux-meta-raspi2-5.4
linux-meta-raspi2-5.4 | 5.4.0.1001.1 | kinetic/universe | source
$ remove-package -m "RM: unsupport kernel packages -- LP: #1993295" -s
$ rmadison -a source -s kinetic-proposed linux-raspi2 linux-meta-raspi2
$ rmadison -a source -s kinetic linux-raspi2 linux-meta-raspi2
linux-meta-raspi2 | 5.4.0.1006.6 | kinetic/universe | source
$ remove-package -m "RM: unsupport kernel packages -- LP: #1993295" -s kinetic
linux-meta-raspi2
$ rmadison -a source -s kinetic-proposed linux-intel-iotg
linux-meta-intel-iotg linux-signed-intel-iotg
linux-restricted-modules-intel-iotg linux-restricted-si
gnatures-intel-iotg
$ rmadison -a source -s kinetic linux-gke linux-meta-gke linux-signed-gke
linux-gke| 5.15.0-1003.3 | kinetic | source
linux-meta-gke | 5.15.0.1003.7 | kinetic | source
linux-signed-gke | 5.15.0-1003.3 | kinetic | source
$ remove-package -m "RM: unsupport kernel packages -- LP:
I've finished kernel bisect and identified
046d2e7c50e3087a32a85fd384c21f896dbccf83 ("mac80211: prepare sta
handling for MLO support") as the first bad commit.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug was fixed in the package linux-raspi - 5.19.0-1004.10
---
linux-raspi (5.19.0-1004.10) kinetic; urgency=medium
* kinetic/linux-raspi: 5.19.0-1004.10 -proposed tracker (LP: #1993133)
* armhf kernel compiled with gcc-12 fails to boot on pi 3/2 (LP: #1993120)
-
This bug was fixed in the package linux-raspi - 5.19.0-1004.10
---
linux-raspi (5.19.0-1004.10) kinetic; urgency=medium
* kinetic/linux-raspi: 5.19.0-1004.10 -proposed tracker (LP: #1993133)
* armhf kernel compiled with gcc-12 fails to boot on pi 3/2 (LP: #1993120)
-
This bug was fixed in the package linux-raspi - 5.19.0-1004.10
---
linux-raspi (5.19.0-1004.10) kinetic; urgency=medium
* kinetic/linux-raspi: 5.19.0-1004.10 -proposed tracker (LP: #1993133)
* armhf kernel compiled with gcc-12 fails to boot on pi 3/2 (LP: #1993120)
-
** Changed in: linux-gke (Ubuntu)
Status: New => In Progress
** Changed in: linux-gke (Ubuntu)
Assignee: (unassigned) => Andy Whitcroft (apw)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-raspi2 in Ubuntu.
** Description changed:
Remove unsupported kernels from kinetic
+
+ = LTS-only kernels not shipped in interim releases =
+ == kinetic-release ==
+
+ linux-gke
+ linux-signed-gke
+ linux-meta-gke
+
+ linux-intel-iotg
+ linux-signed-intel-iotg
+ linux-meta-intel-iotg
+
+ == kinetic-proposed
Public bug reported:
Remove unsupported kernels from kinetic, version v5.15 or lower, these
will not receive any security updates in kinetic.
= LTS-only kernels not shipped in interim releases =
== kinetic-release ==
linux-gke
linux-signed-gke
linux-meta-gke
linux-intel-iotg
so, feel free to test with packages from ppa:canonical-x/x-staging
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1992667
Title:
Application windows invisible (on DG2 graphics)
** Changed in: linux-bluefield (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/1991403
Title:
mlxbf_gige: fix
** Changed in: linux-bluefield (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/1991151
Title:
mlxbf_gige: need to
** Changed in: linux-bluefield (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/1991551
Title:
i2c-mlxbf.c: Sync up
After some more testing, I don't think these parameters matter.
Reloading the module (i.e. removing and inserting it again) sometimes
fixes the issue for some time, that's why I thought these settings fixed
the issue, but the behaviour after module reload is independent of these
parameters.
I
** Changed in: linux-bluefield (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/1991551
Title:
i2c-mlxbf.c: Sync up
** Description changed:
[Impact]
Ubuntu 22.04 does not support Intel DG2-based hw which is released later
this year.
[Fix]
Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1
or 22.2
- kernel: use a dkms provided by Intel and integrated in the OEM
Verify the package, the default setting on mixer 'Dmic0 Capture Switch'
will still be off, but 'Dmic0 Capture Volume' will set to 49 which can
confirm the initial command has applied. Therefore, I think the new ucm
is still valid.
I try to add below code, then Mic will turn on after.
1. $ sudo rm
1 - 100 of 127 matches
Mail list logo
