apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/2109322/+attachment/5875230/+files/RfKill.txt
--
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/bug
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2109322/+attachment/5875231/+files/UdevDb.txt
--
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/bug
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2109322/+attachment/5875221/+files/Lspci.txt
--
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/
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2109322/+attachment/5875232/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2109322/+attachment/5875233/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.ne
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2109322/+attachment/5875227/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2109322/+attachment/5875228/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2109322/+attachment/5875225/+files/Lsusb-v.txt
--
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/
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2109322/+attachment/5875229/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2109322/+attachment/5875224/+files/Lsusb-t.txt
--
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/
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2109322/+attachment/5875222/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.ne
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2109322/+attachment/5875226/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2109322/+attachment/5875223/+files/Lsusb.txt
--
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/
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2109322/+attachment/5875219/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.laun
apport information
** Tags added: apport-collected noble
** Description changed:
Description:
On a laptop with a MediaTek MT7922 Wi-Fi card (driver mt7921e, firmware
00-20240219103337), I cannot obtain a global IPv6 address.
The system sends Router Solicitations (RS), but never re
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/2109322/+attachment/5875218/+files/CRDA.txt
--
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/21
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/2109322/+attachment/5875220/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.ne
Public bug reported:
Description:
On a laptop with a MediaTek MT7922 Wi-Fi card (driver mt7921e, firmware
00-20240219103337), I cannot obtain a global IPv6 address.
The system sends Router Solicitations (RS), but never receives Router
Advertisements (RA), so IPv6 autoconfiguration (SLAAC
It sounds like you're encountering an issue where the Nvidia drivers are
not properly loading, and the system defaults to using the `fbdev`
driver. To resolve this issue, follow these steps:
1. **Update the system:**
Make sure your system is fully up to date. Run the following commands to
upda
Public bug reported:
Summary:
Customer is reporting performance degradation from Bluefield Focal 5.4.0-1087
to 5.4.0-1088
They run iperf3 based performance test, and see performance drop around 10-15%.
Test scenarios:
===
1. Baseline: BF - BFB 3.9.8 (OFED Driver 5.8, FW 35.4
Also seeing this with a fresh install of jammy, kernel version
6.8.0-49-generic
Other details are the same or similar: Running as KVM/QEMU VM with USB
passthrough using C270 webcam. Using MS Teams rather than Zoom.
--
You received this bug notification because you are a member of Kernel
Package
: 2.28.1-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:william4798 F pipewire
/dev/snd/controlC0: william4802 F wireplumber
/dev/snd/controlC1: william4802 F wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
Date: Thu
Public bug reported:
Summary:
ip6tables --set-xmark failed on 1057.59
A degradation
Working version: 1053.55
bf-bundle-2.9.1-13_24.11_ubuntu-22.04_prod.bfb has kernel
5.15.0-1053.55.24.g9cc17fe-bluefield
root@r-qa-hbn00-host00-00:mgmt:/home/ubuntu# /usr/sbin/ip6tables -t
** Tags removed: verification-needed-jammy-linux-bluefield
--
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/2077887
Title:
Backport VFIO P2P patch for BlueField 5.15
Status in l
can we skip the verification?
this needs a very special setup to verify.
--
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/2077887
Title:
Backport VFIO P2P patch for BlueField 5.1
bisect shows
# first bad commit: [9c901808b3affa5b21bb146148ae2c39dfd732ee] drivers:
core: synchronize really_probe() and dev_uevent()
--
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/b
** Description changed:
* introduction
Found a regression on 5.15.0-1053, which worked OK on 5.15.0-1050
At DPU, when using the 5.15.0-1053-bluefield kernel, when the user-space
process uses the OFED driver to create 2000 of SF devices in a batch mode.
At host side, the ubuntu kernel w
Public bug reported:
* introduction
Found a regression on 5.15.0-1053, which worked OK on 5.15.0-1050
At DPU, when using the 5.15.0-1053-bluefield kernel, when the user-space
process uses the OFED driver to create 2000 of SF devices in a batch mode.
At host side, the ubuntu kernel will prevent t
also backport the two patches
---
net/sched: act_ct: Take per-cb reference to tcf_ct_flow_table
net: sched: call tcf_ct_params_free to free params in tcf_ct_init
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
ht
the original patch series for 6.0 kernel is herhe
https://patchwork.kernel.org/project/linux-rdma/cover/0-v2-472615b3877e+28f7-vfio_dma_buf_...@nvidia.com/
backport to 5.15 upstream kernel (not Bluefield)
https://github.com/torvalds/linux/compare/master...jgunthorpe:linux:for-william
v3 patch
Public bug reported:
* Intro
Got call trace RIP below, internal bug ID: 4059202
[ 747.269287] WARNING: CPU: 3 PID: 8360 at
include/net/netfilter/nf_flow_table.h:261
mlx5_tc_ct_del_ft_cb.part.0+0x17b/0x1c0 [mlx5_core]
* Solution
Need to backport
"sched: act_ct: take care of padding in struct
** Description changed:
* Summary
Current BF kernel doesn't support VFIO P2P, the following patches need
to backport, based on 6.0 kernel.
1.
https://patchwork.kernel.org/project/kvm/cover/0-v2-1bd95d72f298+e0e-vfio_pci_priv_...@nvidia.com/
2.
https://patchwork.kernel.org/project
Public bug reported:
* Summary
Current BF kernel doesn't support VFIO P2P, the following patches need
to backport, based on 6.0 kernel.
1.
https://patchwork.kernel.org/project/kvm/cover/0-v2-1bd95d72f298+e0e-vfio_pci_priv_...@nvidia.com/
2.
https://patchwork.kernel.org/project/kvm/cover/0-v2-0
Noob here. I readily admit I don't know what I'm doing.
390.157 seems to work now:
$ grep "X Driver" /var/log/Xorg.0.log
[38.313] (II) NVIDIA dlloader X Driver 390.157 Wed Oct 12 09:21:41 UTC
2022
Boot failed after an upgrade to kernel 6.5, but boot works now (no more
messing with grub c
Seems to work now under 6.8.0-40-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/2028165
Title:
nvidia-dkms-* FTBS with linux 6.5
Status in nvidia-graphics-
** Description changed:
* Explain the bug(s)
We run a simple CPU-only xor application.
int main(void) {
- long i;
- int count = 0;
- for (i=0; i< 100; i++) {
- count = count ^ i;
- }
- return 0;
+ long i;
+ in
Public bug reported:
* Explain the bug(s)
We run a simple CPU-only xor application.
int main(void) {
long i;
int count = 0;
for (i=0; i< 100; i++) {
count = count ^ i;
}
return 0;
}
tested on BlueField-2 and found consistent performa
** Description changed:
* Explain the bug(s)
We run a simple CPU-only xor application.
+ test.c
+ --
int main(void) {
long i;
int count = 0;
for (i=0; i< 100; i++) {
count = count ^ i;
}
return 0;
}
tested
root@c-237-155-120-p88-00-0-bf2:/boot# diff config-5.15.0-1043-bluefield
config-5.15.0-1044-bluefield
3c3
< # Linux/arm64 5.15.0-1043-bluefield Kernel Configuration
---
> # Linux/arm64 5.15.0-1044-bluefield Kernel Configuration
37c37
< CONFIG_VERSION_SIGNATURE="Ubuntu 5.15.0-1043.45-bluefield 5.15
Public bug reported:
intro
-
Our internal test triggers a kernel crash dump below
[ 888.690348] Sun Mar 24 23:51:59 2024: DriVerTest - Start Test
[ 888.691834]
[ 888.983912] mlx5_core 00
** Description changed:
Intro:
==
- When hit a kernel warning when using openvswitch kernel module. Digging into
the source code, we found it's due to the code snippet
- if (WARN_ON(i.cmd >= family->resv_start_op &&
-(i.doit.validate || i.dumpit.validate)))
-
Public bug reported:
Intro:
==
When hit a kernel warning when using openvswitch kernel module. Digging into
the source code, we found it's due to the code snippet
if (WARN_ON(i.cmd >= family->resv_start_op &&
(i.doit.validate || i.dumpit.validate)))
Public bug reported:
* intro
In bug 2053155 "Add DPLL and syncE support" below:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2053155
It requires using a yaml spec file, dpll.yaml, and a python script, cli.py, to
verify the correctness.
ex:
$ sudo ./tools/net/ynl/cli.py --spec
Public bug reported:
* intro
As IDR can't protect itself from the concurrent modification, place
idr_remove() under the protection of tp->lock.
* how to fix
need to backport the patch from Jianbo
"net/sched: flower: Add lock protection when remove filter handle"
https://git.kernel.org/pub/scm/lin
** Description changed:
* intro
Synchronous Ethernet, or SyncE, is an ITU-T standard for computer networking
that facilitates the transference of clock signals over the Ethernet physical
layer. It is used to pass timing from node to node and is particularly
important for mobile networks.
** Description changed:
* intro
Synchronous Ethernet, or SyncE, is an ITU-T standard for computer networking
that facilitates the transference of clock signals over the Ethernet physical
layer. It is used to pass timing from node to node and is particularly
important for mobile networks.
my first time sending pull request, do I make any mistake so it's
Invalid?
--
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/2053155
Title:
Add DPLL and syncE support
Status in l
Public bug reported:
* intro
Synchronous Ethernet, or SyncE, is an ITU-T standard for computer networking
that facilitates the transference of clock signals over the Ethernet physical
layer. It is used to pass timing from node to node and is particularly
important for mobile networks.
The DPLL
Using this reboot=acpi parameter does not work for me to resolve the
issue at all.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2032136
Title:
System reboot to BIOS boot
Public bug reported:
was trying to clan up the /boot
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-88-generic 5.15.0-88.98
ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126
Uname: Linux 5.15.0-88-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architectur
Hi Taihsiang,
cat /root@bu-lab6-oob:~# cat /etc/mlnx-release
DOCA_2.5.0_BSP_4.5.0_Ubuntu_22.04-1.20231116.dev
--
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/2021930
Title:
kdum
adding "-d" to kexec which shows debugging info. I did not see any error...
[ 441.468322] kdump-tools[7548]: arch_process_options:178: command_line:
BOOT_IMAGE=/boot/vmlinuz-5.15.0-1031-bluefield root=1
[ 441.468586] kdump-tools[7548]: arch_process_options:180: initrd:
/var/lib/kdump/initrd.im
I also tested it on 5.15.0-1031-bluefield and it also fails.
Configurations:
root@bu-oob:~# kdump-config show
DUMP_MODE: kdump
USE_KDUMP: 1
KDUMP_COREDIR: /var/crash
crashkernel addr: 0xbd00
/var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.15.0-10
I'm also seeing a variant of this bug (22.04 with kernel
6.2.0-36-generic) with amdgpu driving a dual-head setup.
The crash occurs for me consistently on system wake, and becomes
entirely unresponsive (I'm unable to drop to other runlevels to bring it
back).
Like the original report, the crash ap
Public bug reported:
Summary:
Machine hangs when loading OFED 2310 mlx5 driver at BlueField
How to reproduce:
# load the OFED driver
Reason:
BF got stuck and observed call trace "mlx5_sf_hw_table_init+0xf4/0x2d0
[mlx5_core]
dmesg from minicom:
[ 726.569928] INFO: task systemd-udevd:297 blocke
Public bug reported:
Summary:
Machine hangs when doing devlink reload
How to reproduce:
Host:
[root@bu-lab24v ~]# echo '2' > /sys/class/net/ens2f0np0/device/sriov_numvfs
Arm:
root@bu-lab24v-oob:~# uname -r
5.15.0-1027-bluefield
root@bu-lab24v-oob:~# devlink dev eswitch set pci/:03:00.0 mod
Public bug reported:
System locks up when inserting a Linux formatted CF card in the internal
USB reader.
A crash the other day, then 3 times in a row with rebooting before I could
mount the card.
Ubuntu 6.2.0-33.33-generic 6.2.16
ubuntu-bug linux
** Affects: linux (Ubuntu)
Importance: Und
add merge request
https://code.launchpad.net/~wtu/ubuntu/+source/linux-bluefield/+git/linux-bluefield/+merge/450806
--
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/2032378
Title:
** Also affects: linux-bluefield (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-bluefield (Ubuntu Impish)
** No longer affects: linux-bluefield (Ubuntu Kinetic)
** Changed in: linux-bluefield (Ubuntu)
Assignee: (unassigned) => William Tu (wtu)
** Chan
Public bug reported:
* Explain the bug(s)
when setting up conntrack offload with tcp pedit (test-ct-tcp-pedit.sh),
encounter kernel panic.
* brief explanation of fixes
In tc_setup_flow_action, need to properly assign action.
Which fixes previous commit ("UBUNTU: SAUCE: net/sched: Provide act to
Public bug reported:
* Explain the bug(s)
We've found that for Jammy 5.15 and also 5.4.0-1049 kernel running on
Bluefield, the kdump doesn't work when enabling secure boot[1].
* How to test
Make sure kernel config:
CONFIG_SECURITY_LOCKDOWN_LSM=y
CONFIG_SECURITY_LOCKDOWN_LSM_EARLY=y
CONFIG_LOCK_
With this fix, does kdump/kexec work with
CONFIG_SECURITY_LOCKDOWN_LSM=y?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2008523
Title:
Make kexec work by default on secureboot sys
Public bug reported:
fix race on port output
* Explain the bug(s)
there is a race condition on port output
* brief explanation of fixes
We found that upstream linux has the same issue and fix
commit 066b86787fa3d97b7aefb5ac0a99a22dad2d15f8
Author: Felix Huettner
Date: Wed Apr 5 07:53:41 20
** Description changed:
* Explain the bug(s)
While conntrack tuples are offloaded to hardware and conntrack packet
accounting is enabled, offloaded packets aren't counted.
* Brief explanation of fixes
Cherry-pick. No adaptation. First commit for SW, second commit of HW
offloade
Public bug reported:
* Explain the bug(s)
conntrack -D or conntrack -F doesn't delete offloaded tuples.
* brief explanation of fixes
Add support for to delete offloaded tuples via netlink interface and
userspace conntrack utility.
* How to test
Create OVS bridge with 2 devices mlx5 rep d
Public bug reported:
Support hardware stats for tc actions
* Explain the bug(s)
tc hardware stats are not offloaded from some offloaded actions (pedit, sample,
skbedit)
* brief explanation of fixes
Implement the necessary callbacks to report back stats for these actions.
* How to test
Public bug reported:
* Explain the bug(s)
Currently tc miss interface only supports resuming from a specific tc chain.
If a packet modification is done before a missable action such as CT and
there is a miss in CT after it, this may cause a miss match when resuming
re-executing the same chain in
** Changed in: linux-bluefield (Ubuntu Focal)
Status: Confirmed => In Progress
--
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/2008136
Title:
netfilter: flowtable: add co
** Changed in: linux-bluefield (Ubuntu Focal)
Status: In Progress => Confirmed
--
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/2008136
Title:
netfilter: flowtable: add co
** Description changed:
* Explain the bug(s)
When CT HW offload is enabled, the CT stats does not show the stats of the
offloaded flow.
Ex: using
cat /proc/net/nf_conntrack, or conntrack -L
shows only the software CT stats, not the offloaded CT stats
* Brief explanation of fixes
** Description changed:
* Explain the bug(s)
When CT HW offload is enabled, the CT stats does not show the stats of the
offloaded flow.
- Ex: using
+ Ex: using
cat /proc/net/nf_conntrack, or conntrack -L
shows only the software CT stats, not the offloaded CT stats
* Brief explana
Public bug reported:
* Explain the bug(s)
When CT HW offload is enabled, the CT stats does not show the stats of the
offloaded flow.
Ex: using
cat /proc/net/nf_conntrack, or conntrack -L
shows only the software CT stats, not the offloaded CT stats
* Brief explanation of fixes
Cherry-pick. No
** Tags added: foundations-triage-discuss
--
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 lin
Marking as Fix Released. During ubuntu-image testing I noticed this is
resolved with the latest kernel.
** Changed in: linux-raspi (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi
** Also affects: flash-kernel (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-raspi (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-raspi (Ubuntu Jammy)
Status: New => Invalid
** Changed in: flash-kernel (Ubuntu Jammy)
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/515937
Title:
Filesystems end up remounted read-only
Status in linux pa
Public bug reported:
USB devices are not working on the CM4. When running `lsusb` the hub is
detected, but devices are not.
```
ubuntu@ubuntu:~$ sudo dmesg | egrep -i "dwc2|usb"
[0.151915] usbcore: registered new interface driver usbfs
[0.151976] usbcore: registered new interface driver h
** Project changed: launchpad => ubuntu
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1957002
Title:
tp-link AC1300 not working in 21.10
S
** Attachment added: "kernel-5.4.0-90.boot.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950712/+attachment/5540475/+files/kernel-5.4.0-90.boot.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
Spoke with the other person, we are getting similar issues in bionic
after 4.15.0-154 for the same type of disk configuration
--
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/1950712
Title:
Public bug reported:
ESX 6.7
Ubuntu focal 20.04
While using ESX encryption for EAR, if the MV has a mixture of
encrypted/unencrypted disks assigned to it, it fails to boot right
around where the kernel is trying to init the disks.
I've attempted to boot with 5.11.0-40, same issue.
I heard from
I have confirmed that the kernel 5.13.0-20 in impish-proposed solves
this problem for me.
To confirm this, I performed the following steps:
On a ZFS installation:
1) boot from kernel 5.13.0-19.19
a) observe the boot failed with PANIC at zfs_node.c: 339:zfs_znode_sa_init
2) install kernel 5.13
** Also affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-raspi (Ubuntu)
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.laun
** Changed in: u-boot (Ubuntu Hirsute)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
S
The 1017 kernel from the kernel team PPA is reliably booting on my
hardware.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1934548
Title:
RISC-V: Illegal instruction
Status in li
I am also hitting this error. I think I've been having it for a little
while, but have just today started digging into it.
I tried the zfs_recover suggestion to get rid of the corrupted files,
but that did not work:
jawn-smith@desktop:~$ zfs version
zfs-2.0.3-8ubuntu7
zfs-kmod-2.0.2-1ubuntu5
jawn
I've downloaded the daily build from August 9, and have reproduced this
5 times out of 5 boot attempts. Attached is my serial output:
https://paste.ubuntu.com/p/gfpb8tmk9h/
I have the board revision ending in 3A0
--
You received this bug notification because you are a member of Kernel
Packages,
This was fixed previously in hirsute by an upstream merge that resulted
in bluez 5.56-0ubuntu1
** Changed in: bluez (Ubuntu Hirsute)
Status: New => Fix Released
** Changed in: bluez (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member
sil2100 sorry for the delayed response. I originally thought that the
verification-failed-hirsute tag was left over from a previous regression
we had in this package. I will investigate what is needed in hirsute.
--
You received this bug notification because you are a member of Kernel
Packages, w
The verification passed for focal. The daily images are building with
u-boot-menu-4.0.2ubuntu5~20.04.1. I have successfully booted these daily
images in qemu and Unmatched hardware.
Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-29-generic riscv64)
* Documentation: https://help.ubuntu.com
* Ma
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1934387/+attachment/5508491/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv-5.8 in Ubuntu.
https://bugs
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1934387/+attachment/5508493/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv-5.8 in Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1934387/+attachment/5508494/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv-5.8 in Ubuntu.
https://bugs.launchp
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1934387/+attachment/5508490/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv-5.8 in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1934387/+attachment/5508492/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv-5.8 in Ubuntu.
https://bugs.launc
apport information
** Tags added: apport-collected
** Description changed:
This doesn't happen every time a boot is attempted, but very frequently.
Log below:
[ 15.024548] Loaded X.509 cert 'Canonical Ltd. Live Patch Signing:
14df34d1a87cf37625abec039ef2bf521249b969'
[ 15.038870]
Public bug reported:
This doesn't happen every time a boot is attempted, but very frequently.
Log below:
[ 15.024548] Loaded X.509 cert 'Canonical Ltd. Live Patch Signing:
14df34d1a87cf37625abec039ef2bf521249b969'
[ 15.038870] Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing:
88f752e
** Changed in: u-boot-menu (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-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in q
This patch backports the changes from hirsute in u-boot-menu to focal.
** Changed in: u-boot-menu (Ubuntu Focal)
Status: Invalid => In Progress
** Changed in: u-boot-menu (Ubuntu Focal)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Patch added: "lp1923162_f
I am having the same problem. I did step 1. Did not work.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1931288
Title:
Touchpad doesn't work in 'Ideapad 5 14ALC05' after
1 - 100 of 437 matches
Mail list logo
