I think the answer here is to stop passing "console=ttyS0". This is
something that is typically only done for debugging.
dmesg shows a 14 second delay between the "console [tty1] enabled" and
"console [ttyS0] enabled" messages. I suspect that because console=ttyS0
is passed the kernel is going to
I confirmed that 5.4.0-29 does not show the problem, and -31 does. Then
I built -31 with these three patches reverted:
UBUNTU: SAUCE: overlayfs: fix shitfs special-casing
UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay
UBUNTU: SAUCE: overlayfs: allow with shiftfs as
On the surface this seems like a reasonable thing to do. However I think
someone from foundations should weigh in on the topic too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879454
Title:
Set
Based on the video it looks like the first kernel messages which appear
on the screen have timestamps >20s, so it seems likely at least part of
the delay is in the kernel. If you can supply dmesg we might be able to
get some idea of where this delay is happening.
--
You received this bug
Sorry, I misread something before. I thought you were running 16.04 now.
You are running 14.04, so 3.13 is the correct kernel, it is not an "old"
kernel for that release.
Do you need to have casper installed? If not, the easiest thing to do
would be to uninstall casper, then run the upgrade
** Changed in: linux-firmware (Ubuntu Bionic)
Status: Fix Committed => In Progress
** Changed in: linux-firmware (Ubuntu Eoan)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I see two problems.
1. You have a very old kernel installed (3.13.0-38), which is causing
this message: "E: amd64-microcode: unsupported kernel version!" I'm not
sure if this is causing update-initramfs to fail, but if you don't need
this kernel you should just remove it.
2. These messages:
** Description changed:
+ SRU Justification
+
+ Impact: amdgpu references firmware files in modinfo which have not been
+ supplied to linux-firmware. This causes update-initramfs to generate
+ "Possible missing firmware" warnings.
+
+ Fix: Since the firmware is not available, all we can do is
AMD has not released this firmware to linux-firmware. For now all we can
do is remove the files from modinfo so that update-initramfs will stop
complaining.
** Package changed: linux-firmware (Ubuntu) => linux (Ubuntu)
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status:
** Changed in: linux-firmware (Ubuntu Bionic)
Status: New => Fix Committed
** Changed in: linux-firmware (Ubuntu Eoan)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-gcp (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-kvm (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oracle (Ubuntu)
Importance:
The firmware load messages are not unusual. The driver will try to load
a range of firmware versions, and often the "newest" version the driver
looks for has not been released by Intel. As long as it finds supported
firmware version (as indicated by the "loaded firmware version" message)
there's
Don't worry too much about what lspci says. It just has a database to
map PCI ids to names, and it currently considers anything with the id
8086:02f0 to be a 9462. The correct driver (iwlwifi) is being used, and
it identifies your wireless correctly, so that is what matters.
Can you please
The mailing list for i915 is intel-...@lists.freedesktop.org.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872760
Title:
i915 - after return from suspend display is flickering
To manage
** Description changed:
+ SRU Justification
+
+ Impact: CONFIG_RT_GROUP_SCHED was enabled in focal, except for the
+ lowlatency kernel since we expected most RT users to use that kernel.
+ However we are getting RT regressions with the generic kernel. Digging
+ deeper into this option, it seems
signed) => Seth Forshee (sforshee)
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Status: New => Confirmed
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received thi
I think the upstream i915 developers might be able to best help you,
since the issue still exists in 5.7. I checked and this report looks to
be the same problem:
https://gitlab.freedesktop.org/drm/intel/-/issues/347
I'd suggest trying to help the developers debug the problem there.
Looks like
Fix sent: https://lists.ubuntu.com/archives/kernel-
team/2020-April/109405.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873506
Title:
ubuntu/focal64 fails to mount Vagrant shared folders
To
** Description changed:
- Attempting to `vagrant up` using the `ubuntu/focal64` box fails to mount
- the `/vagrant` shared folder. `ubuntu/bionic64` works as expected. Here
- is the Vagrant error message:
+ SRU Justification
+
+ Impact: When our kernel packaging was updated to build the
Assignee: (unassigned) => Seth Forshee (sforshee)
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
I'm not sure that it's workload-specific, it could also be an issue with
a specific driver or any number of things. RCU is widely used in the
kernel, so at this point I'm looking for the proverbial needle in the
haystack. I am trying to uncover code paths that you might have been
exercising that I
nee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872964
Title:
Reliable crash in lowlatency kernel with LXD
To manage notifications about this bug go to:
Please disregard comment #2. These warnings are related to preempt rcu,
which is only used in the lowlatency kernel.
This seems likely to be caused by an unbalanced
rcu_read_lock()/rcu_read_unlock() happening somewhere before the task
schedules.
--
You received this bug notification because you
When you see this in -24, is that still the lowlatency kernel or had you
switched it out for generic like you mentioned in the description?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872964
Test build with the vsock options:
https://people.canonical.com/~sforshee/lp1873809/linux-
kvm-5.4.0-1008-kvm/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873809
Title:
Make linux-kvm bootable
Progress
** Changed in: linux-kvm (Ubuntu)
Assignee: (unassigned) => Seth Forshee (sforshee)
** Description changed:
+ SRU Justification
+
+ Impact: multipath-tools is installed by default in server images. With
+ the linux-kvm kernel, multipathd.service fails to start because we do
+
Public bug reported:
When doing a dist-upgrade in a vm running the linux-kvm kernel,
multipath-tools failed because multipathd.service failed to start.
Setting up multipath-tools (0.8.3-1ubuntu2) ...
Job
Because someone has to manually flip it once information has been
provided. Setting it to confirmed, buy you should also be able to do
that for your own bug.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of
are installed by linux-
modules at /lib/firmware//devcie-tree.
Regression Potential: Minimal. This should only impact parameters used
by drivers, and the parameters should now better match what is needed by
the hardware.
** Affects: linux-riscv (Ubuntu)
Importance: Undecided
Assignee: Seth Forshee
Can you try a vanilla 5.4.30 kernel from here, and see if it has the
same problem? That will let us know if any of the fixes we've applied on
top of 5.4 is responsible.
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.30/
Note that you will need to disable secure boot to boot into this
Actually there is something in the logs that I missed the first time:
[ 69.108687] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR*
CPU pipe A FIFO underrun
Do you know whether earlier 5.4 kernels in focal also had this same
issue? If not, do you know the last version you used which
Oh, no that is fine then. Sorry, on the other bug you said the system
was unusable after suspend so I assumed that you could not run apport-
collect in that state.
Unfortunately the logs don't show anything strange happening.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
The attached logs are from the current boot, which doesn't show anything
from when the corruption actually happened. Can you get logs from a
previous boot where you did see the corruption? For example, if you know
this happened the last time you booted, you can use 'journalctl -b -1',
or
@arno can you file a new bug for this please? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853044
Title:
5.3.0-23-generic causes fans to spin when idle
To manage notifications about this
I'm not finding much in the logs. There's some i915 splat which could
possibly be related to the corruption, but nothing to explain the hard
lockup.
The current focal-proposed kernel (5.4.0-24) has some fixes for
races/deadlocks in i915, so it's worth trying that out to see if it
helps. You can
@Anmar, I believe this issue should be fixed now. Can you confirm?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861462
Title:
Lenovo Thinkpad X1 Carbon 7th Gen doesn't suspend and resume
To
Confirmed that I'm no longer seeing the segfault. Thanks!
** Changed in: llvm-toolchain-10 (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
You rebuilt the package with a different compiler than what was used to
compute the signatures/checksums in the kernel build, so you get
different objects and mismatching checksums. This is expected.
** Changed in: linux-restricted-modules-oracle (Ubuntu)
Status: Confirmed => Invalid
--
You rebuilt the package with a different compiler than what was used to
compute the signatures/checksums in the kernel build, so you get
different objects and mismatching checksums. This is expected.
** Changed in: linux-restricted-modules-gcp (Ubuntu)
Status: Confirmed => Invalid
--
You
You rebuilt the package with a different compiler than what was used to
compute the signatures/checksums in the kernel build, so you get
different objects and mismatching checksums. This is expected.
** Changed in: linux-restricted-modules-aws (Ubuntu)
Status: Confirmed => Invalid
--
You
You rebuilt the package with a different compiler than what was used to
compute the signatures/checksums in the kernel build, so you get
different objects and mismatching checksums. This is expected.
** Changed in: linux-restricted-modules-azure (Ubuntu)
Status: Confirmed => Invalid
--
Thanks for testing. I've applied the patches to focal/master-next.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866909
Thanks for testing. I've applied the patches to focal/master-next.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855668
Title:
lockdown on power
To manage notifications about this bug go to:
New test build with the updated patch in the same ppa.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855668
Title:
lockdown on power
To manage notifications about this bug go to:
Test build is done now, in the same location. It has the above patch and
also the updated patch from bug 1855668.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866909
Title:
Ubuntu Kernel Support
Based on some quick googling, I think there's some localization set up
on raspbian that must also cause it to set the regulatory domain.
https://www.raspberrypi.org/documentation/configuration/wireless/desktop.md
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Generally speaking we don't know what country a device is operating in,
so we default to the world domain which should be safe throughout the
world. The AP may send a hint to the client as to what regulatory domain
to use, but many APs do not do this.
Also note that on many desktop systems now
Oh but PPC_SECURE_BOOT depends on IMA_ARCH_POLICY. For now I'm going to
make it depend on that or LOCK_DOWN_IN_SECURE_BOOT to get the test build
going. I think this makes sense because lockdown enforces signatures for
module loading and kexec (plus a number of other restrictions), which I
think is
Um, off rather.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866909
Title:
Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot
To manage notifications about this bug go to:
I'll get a test kernel uploaded with IMA_ARCH_POLICY up, will let you
know when it's ready for testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866909
Title:
Ubuntu Kernel Support for
Afaict the ppc ima arch policy is about ensuring that signature
verification is done for module loading and kexec, which in our kernel
will be enforced by automatically turning on lockdown integrity mode
under secure boot. So my conclusion is that CONFIG_MODULE_SIG_FORCE
should stay off and
I'm suddenly having a major sense of deja vu about this. I think we hit
very similar issues on x86, and after discussions with Mimi we decided
that CONFIG_IMA_ARCH_POLICY should be disabled for us. I think this may
be the right solution here too.
--
You received this bug notification because you
Our policy is to require module signatures only under lockdown.
CONFIG_MODULE_SIG_FORCE requires modules to be signed unconditionally,
which makes dkms impossible on systems which have no mechanism for
importing keys from firmware.
--
You received this bug notification because you are a member
This is noted on the other bug, but I'll also note it here. This kernel
is *not* signed with the archive key. The public half of the key pair
used to sign this build can be found in this tarball:
http://ppa.launchpad.net/sforshee/lp1866909/ubuntu/dists/focal/main/signed
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867588
Patch one is included on the test build for bug 1866909 in
https://launchpad.net/~sforshee/+archive/ubuntu/lp1866909/+packages. I
incorporated the config changes in with those requested for that bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Build is done now, version 5.4.0-21.25+lp1866909v202004020814 in
https://launchpad.net/~sforshee/+archive/ubuntu/lp1866909/+packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866909
Title:
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867587
Title:
[sas-0316]sync mainline kernel 5.6rc1 roce patchset into
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869947
Title:
Revert "nvme_fc: add module to ops template to allow module
Note that it is still building, should be ready in a few hours. I'll
post an update when it is done.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866909
Title:
Ubuntu Kernel Support for OpenPOWER
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856900
Title:
stress-ng sysinfo stressor fails on ppc64el with linux
I don't see that the sysinfo stressor runs at all in the logs for
5.4.0-21:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/ppc64el/l/linux/20200331_002447_e28f4@/log.gz
--
You received this bug notification because you are a
@knossos456 thanks, the fix release status though is for when the
package has been released. I've added the verification-done-eoan tag.
** Changed in: linux-firmware (Ubuntu Eoan)
Status: Fix Released => Fix Committed
** Tags added: verification-done-eoan
--
You received this bug
On Mon, Mar 30, 2020 at 02:06:16PM -, knossos456 wrote:
> To do this i need a eoan iso with embedded proposed package -> to build a usb
> boot stick. So I can test on my hardware. I haven't room on my HDD sorry.
> Did you know where i can find this?
Also no one has verified the -proposed package on eoan yet. Is anyone
affected running eoan and able to verify the fix there?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865130
Title:
On Sun, Mar 29, 2020 at 06:35:08AM -, knossos456 wrote:
> Question to maintainer :
> 1.173.17 proposed (main)
> When will this release go to real updates, 7 days are gone.
We generally don't release SRU updates over weekends (including Friday),
so it will probably get released today.
Applied the patches from linux-next, plus one additional fix I saw,
"sysfs: fix static inline declaration of sysfs_groups_change_owner()".
@Christian, please let me know if there are any other fixes we need to
grab.
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug notification be
Also I'll add, you can use this ppa to test the -proposed kernels
without enabling all of -proposed.
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/proposed/
These are kernels copied from the -proposed pocked, after we've built
signed packages in -proposed.
--
You received this
Lockdown is enabled in focal, and the default mode when booted without
any secure boot scheme is NONE.
When booted under a secure boot scheme, we had previously forced the
CONFIDENTIALITY mode for lockdown. But we have now scaled that back, and
the kernel in focal-proposed sets the mode to
Public bug reported:
I started seeing this in the testing for 5.4.0-20. Only happening on
arm64/armhf.
--
FAIL: pwd/tst-getpw
original exit status 223
PASS: NULL buffer returns -1 and sets errno to EINVAL.
PASS: Read a password line given a uid.
FAIL: Did not find even one invalid uid.
Still seeing this with the current focal-proposed kernel:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/s390x/l/linux/20200325_012616_7d5a5@/log.gz
** Changed in: llvm-toolchain-10 (Ubuntu)
Status: Incomplete =>
** Package changed: linux-5.4 (Ubuntu Focal) => linux (Ubuntu Focal)
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860697
Title:
Sound doesn't work on Lenovo X1 Carbon 7th with 20.04
To manage
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861053
Title:
no fatrace output in focal
To manage notifications about this bug
The focal-proposed kernel is now released, so marking this bug fix
released.
** Package changed: linux-5.4 (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: linux-azure (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863951
Title:
[linux-azure] Missing user mode io driver -
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868217
Title:
Make Dell WD19 dock more reliable after suspend
To
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864484
Title:
Update SmartPQI driver in Focal to 1.2.10-025
To manage
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836030
Title:
enable realtek ethernet device ASPM function
To manage
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867790
Title:
update-version-dkms doesn't add a BugLink
To manage
** Changed in: kunpeng920/ubuntu-20.04
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864442
Title:
dmaengine: hisilicon: Add Kunpeng DMA engine support
** Changed in: linux (Ubuntu Focal)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780590
Title:
Add support for Realtek 8723DE wireless adapter
To manage
Patches applied for focal.
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835531
Title:
[20.04 FEAT] Base KVM setup for secure
** Changed in: linux-meta (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867656
Title:
Remove linux-firmware dependency from kernel meta
Config changes applied for focal.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867753
Title:
[Ubuntu 20.04] Unset
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865130
Title:
[drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to
reset the VCPU!!!
To
This should be fixed in focal now. I've uploaded packages for bionic and
eoan too, those are waiting to be approved and built.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860697
Title:
Sound
Let me just double check with you about disabling CONFIG_PM, as it also
supports runtime power management of devices. If CONFIG_PM is disabled
devices will not be put into low power states when idle.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags added: regression-testing-passed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866484
Title:
focal/linux-azure: 5.4.0-1006.6 -proposed tracker
To manage notifications about this bug go
** Package changed: linux-firmware (Ubuntu) => linux-meta (Ubuntu)
** Changed in: linux-meta (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux-meta (Ubuntu)
Status: New => Confirmed
** Summary changed:
- The need for the linux-firmware package on s390x
+ Remove
@laney: Shouldn't udisks2 prefer in-kernel filesystem support if
available, then fallback to a fuse driver? We also have a fuseext2
package, but if I have that installed I would still expect an ext2
formatted thumb drive to be mounted using the kernel's driver when I
insert it rather than the fuse
Yes, sorry, I was blocked from uploading new linux-firmware packages for
various reasons. All of the blocking issues are cleared up now, so I
will upload new packages today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: regression-testing-passed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866483
Title:
focal/linux-aws: 5.4.0-1005.5 -proposed tracker
To manage notifications about this bug go to:
** Tags added: regression-testing-passed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866486
Title:
focal/linux-kvm: 5.4.0-1004.4 -proposed tracker
To manage notifications about this bug go to:
** Tags added: regression-testing-passed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866485
Title:
focal/linux-gcp: 5.4.0-1005.5 -proposed tracker
To manage notifications about this bug go to:
** Tags added: regression-testing-passed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866487
Title:
focal/linux-oracle: 5.4.0-1005.5 -proposed tracker
To manage notifications about this bug go
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee
(sforshee)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866
** Changed in: linux (Ubuntu Focal)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857409
Title:
alsa/sof: load different firmware on different platforms
Added reproduction steps to the description.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866882
Title:
segfault in libllvm-10 when building kernel bpf selftests on s390
To manage notifications
201 - 300 of 5875 matches
Mail list logo
