** 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
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
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
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
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
** 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
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
** 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
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
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]
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
** 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
This debdiff corrects the accidentally left in debug statement and adds
`optimize=-lto` to DEB_BUILD_MAINT_OPTIONS. Tests are succeeding again.
** Patch added: "lp1912371_v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1912371/+attachment/5498808/+files/lp1912371_v2.debdiff
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => William Wilson (jawn-smith)
--
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/1910965
Title:
riscv: backport support
** Changed in: linux (Ubuntu Focal)
Assignee: William Wilson (jawn-smith) => (unassigned)
--
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/1910965
Title:
riscv: backport support
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986836
Apparently I had not created the bug report correctly the first time.
** Bug watch added: Debian Bug tracker #986836
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986836
--
You received this bug notification because you are a membe
The verification passed for focal.
* On Pi 400 **
ubuntu@ubuntu:~$ apt-cache policy bluez pi-bluetooth linux-firmware-raspi2
bluez:
Installed: 5.53-0ubuntu3
Candidate: 5.53-0ubuntu3.1
Version table:
5.53-0ubuntu3.1 500
500 http://ports.ubuntu.com/ubuntu-ports foc
** Changed in: linux-firmware-raspi2 (Ubuntu Focal)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: linux-firmware-raspi2 (Ubuntu Groovy)
Assignee: (unassigned) => William Wilson (jawn-smith)
--
You received this bug notification because you are a member of
** Description changed:
[SRU Information]
- Needs completing. See comment 5 below.
+ [Impact]
+
+ The same file was provided by two packages, causing errors when
+ upgrading.
+
+ [Test Case]
+
+ * Boot an ubuntu image on a Raspberry Pi.
+ * "sudo apt update"
+ * "sudo apt upgrade"
+ * Inst
The verification passed for groovy.
ubuntu@ubuntu:~$ apt-cache policy linux-firmware-raspi2
linux-firmware-raspi2:
Installed: 2-0ubuntu2
Candidate: 4-0ubuntu0~20.10.1
Version table:
4-0ubuntu0~20.10.1 500
500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted
armhf
The verification passed for focal:
ubuntu@ubuntu:~$ apt-cache policy linux-firmware-raspi2
linux-firmware-raspi2:
Installed: 3-0ubuntu2~20.04.1
Candidate: 4-0ubuntu0~20.04.1
Version table:
4-0ubuntu0~20.04.1 500
500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse
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
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
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
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,
** Changed in: bluez (Ubuntu Groovy)
Assignee: Dave Jones (waveform) => William Wilson (jawn-smith)
** Changed in: bluez (Ubuntu Hirsute)
Assignee: Dave Jones (waveform) => William Wilson (jawn-smith)
--
You received this bug notification because you are a member of Kernel
Pa
Attached is a patch to SRU for focal.
** Patch added: "Focal SRU"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+attachment/5477287/+files/lp1903048_focal.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
@seb128 it turns out Dave had already forwarded the patches, so I
included the URLs in this new debdiff
@vanvugt I set the version to ubuntu3.1 rather than ubuntu4
** Patch added: "Focal SRU"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+attachment/5477676/+files/lp1903048_foc
Public bug reported:
In the case of upgrading bluez on certain raspberry pi devices, a reboot
may be required to apply the changes. We should add a check for this
scenario in the postinst script.
** Affects: bluez (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
Attached is a patch for Hirsute. If this is accepted I will SRU to focal
and groovy.
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Patch added: "Hirsute Patch"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1922792/+attac
Seb,
A reboot is needed in this case because the bluetooth device on the
raspberry pi has to be initialized at boot time. Restarting the service
will not cause the device to be brought up.
The hardcoded addresses are the approach used in the pi-bluetooth
package, and recommended by waveform.
As
** Description changed:
- In the case of upgrading bluez on certain raspberry pi devices, a reboot
- may be required to apply the changes. We should add a check for this
- scenario in the postinst script.
+ In the case of upgrading or installing bluez for the first time on
+ certain raspberry pi d
I have submitted a Debian bug report with the patch suggested, and
updated the bug description.
bluez is pre-installed on the desktop images, but not the server images.
This warning would be very useful for server users that want to install
bluez for the first time.
--
You received this bug noti
[Summary]
This package is safe to include in main.
This does need a security review, so I'll assign ubuntu-security
List of specific binary packages to be promoted to main:
* ftdi-eeprom
* libftdi1-2
* libftdi1-dev
* libftdi1-doc
* libftdipp1-3
* libftdipp1-dev
* python3-ftdi1
[Dupli
I have reviewed flashrom along with fwupd and I don't see anything that
looks like it will cause problems. The flashrom documentation recommends
using vendors' flashing utilities when possible for laptops, and there
is a link to that page of the documentation in the manpage.
I have attached a debd
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
** 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
** 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)
41 matches
Mail list logo
