Will we see these fixes cherry-picked in a 5.15.0-24 kernel or so soon?
The linux-firmware package has been ready for a while now with the new
firmware
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
** Package changed: grub2 (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/1964626
Title:
Unable to launch 5.15.0-22-generic kernel (or its recovery mode)
Statu
Hi, this works, yes. 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/1962471
Title:
iwlwifi fails after suspend&resume (Failed to start RT ucode: -110)
Status in linux package in
*** This bug is a duplicate of bug 1962471 ***
https://bugs.launchpad.net/bugs/1962471
** This bug has been marked a duplicate of bug 1962471
iwlwifi fails after suspend&resume (Failed to start RT ucode: -110)
--
You received this bug notification because you are a member of Kernel
Packag
** Description changed:
See attachments.
- This is a regression from earlier kernel versions which worked fine.
+ This is a regression from earlier kernel versions which worked fine, but
+ I don't know at which point precisely it broke - with 5.15 perhaps?
+ Laptop was running 24/7 mostly in
Public bug reported:
See attachments.
This is a regression from earlier kernel versions which worked fine.
It's a ThinkPad T480s upgraded with an AX210 or AX211 (don't have
concrete product number)
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-22-generic 5.15.0-22.22
Dmesg with failure
** Attachment added: "LastBoot.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962472/+attachment/5564171/+files/LastBoot.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
Public bug reported:
See attachments.
This is a regression from earlier kernel versions which worked fine.
It's a ThinkPad T480s upgraded with an AX210 or AX211 (don't have
concrete product number)
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-22-generic 5.15.0-22.22
My side question is what prevents arm64 from having the amd64 approach
where AFAIUI the image is compressed but starts with a small stub that
decompresses it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
Public bug reported:
Compressed kernel images were introduced in bug 1384955 to work around
some limits on old u-boot systems. This in turn broke grub-check-
signatures, meaning that while cloud images booted in secure boot, you
could not upgrade grub or install new kernels on secure systems as th
Public bug reported:
system failed to suspend, see attached logs
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-19-generic 5.13.0-19.19
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl
Various dkms weirdness
"Error! The module acpi-call 1.1.0 is not currently installed."
But there are also like 3 services failing to start in the log, so maybe
the system is just misconfigured somewhere that affects all of them.
The bug also indicates that EFI variables are not supported by the
** Package changed: shim-signed (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/1941963
Title:
package shim-signed 1.40.7+15.4-0ubuntu9 failed to install/upgrad
There are three possible causes
- firmware bug
- kernel bug
- user error (read-only variables), though why does that give I/O rather than
ENOSPACE
I'm going to reassign this one to linux for a check on the kernel side,
but I suspect it's a firmware issue.
** Package changed: shim-signed (Ubuntu
cpu-checker (0.7-1.2) experimental; urgency=medium
will be synced shortly with those changes
** Changed in: cpu-checker (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to cpu-checker in Ubuntu.
Yes, of course if you don't install the fixed version you still have the
broken one.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu.
https://bugs.launchpad.net/bugs/1923150
Title:
unexpected error
Marking the packaging tags as invalid, as the bug is fixed in apt 2.0.4
which is in the 20.04.2 images. This bug was tracked as bug 1871268 back
when it was being fixed.
** Changed in: apt (Ubuntu)
Status: Incomplete => Invalid
** Changed in: nvidia-graphics-drivers-455 (Ubuntu)
Sta
I mean 2.0.4, of course, which is included in the current LTS images
(20.04.2); your image is the previous version (20.04.1)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu.
https://bugs.launchpad.net/
It seems you are not using libapt-pkg6.0 in version 2.1.10ubuntu0.2 or
later? This issue was fixed in that version.
** Changed in: apt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphi
I just want to point out that the last rebase in the kernel changelog
was 5.11, so aren't we also missing 5.11.{1,2,3,4,5,6}?
--
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/1919492
Title:
5.11.6 bad, 5.11.7 good
@juerg I think you are getting your kernels confused; 5.11.0-11 seems to
be based on 5.11 + some cherry-picks, not 5.11.7; 5.11.7 tracking bug is
bug 1919492, which is not yet fixed.
--
You received this bug notification because you are a member of Kernel
Packages, which
Reference 1 - Ubuntu kernel 5.11.0-11-generic:
jak@jak-t480s:~:master$ sudo lvcreate -L 1G -n foo ubuntu-vg
Logical volume "foo" created.
jak@jak-t480s:~:master$ sudo lvremove ubuntu-vg/foo
Do you really want to remove and DISCARD active logical volume ubuntu-vg/foo?
[y/n]: y
/dev/mapper/cry
Let me try 5.11.6 and 5.11.7 mainline then...
--
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/1920821
Title:
BLKDISCARD fails on LUKS volume hosting LVM PV
Status in Linux:
Fix Release
This seems to be https://bugzilla.kernel.org/show_bug.cgi?id=211167
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=211167
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
Should be fixed in 5.10.24, 5.11.7 and 5.12-rc3 according to the
internet
--
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/1920821
Title:
BLKDISCARD fails on LUKS volume hosting LVM PV
St
I verified that mainline ppa build 5.11.8-051108-generic works
--
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/1920821
Title:
BLKDISCARD fails on LUKS volume hosting LVM PV
Status in Lin
Public bug reported:
Creating a logical volume and destroying it fails to discard the volume,
on an encrypted installation. This can significantly increase wear on
SSDs when a lot of LVs are created and destroyed.
jak@jak-t480s:~:master$ sudo lvcreate -L 10G -n foo ubuntu-vg
** Package changed: grub2 (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/1885085
Title:
Suspend is not deep
Status in linux package in Ubuntu:
Confirmed
Bu
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1914279
Title:
linux from security may force reboots without complete d
It's possible you see a different bug, I'd suggest opening a new bug
report about it with ubuntu-bug so the kernel team actually has some
data about the system rather than just small comments.
I think we can all agree that the patch (well removal of patch :)) made
a vast improvement in terms of st
That's correct. 33 was a hot fix release for a data loss in 31 that did
not include the changes from 32. They'll come back in 34.
--
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/1896091
Tit
I think we've gotten enough (independent) verifications of this now to
mark it as done.
** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
Been running for 1d 15h sofar and it seems to be fine
--
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/1896091
Title:
[i915] Noise-like lines of graphics corruption when moving windows in
Given that it boots to the kernel, but the kernel can't setup the drm
device, I'm inclined to believe this is a kernel bug.
** Package changed: grub2 (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
Well it booted fine to the kernel so I'll reassign it there, some mode
setting going wrong ai assume.
** Package changed: grub2 (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.launc
It happened a lot more when docked (ext USB-C monitor) than on the
laptop itself.
Kernel 5.9.1 seems good so far. I've not seen the issue yet and my
uptime is 3 days 15 hours without any suspending in between, just screen
locked.
--
You received this bug notification because you are a member of
Oh, drmtip exists too, I thought you said drmnext which was stuck on
09-18 (and I tested 09-15 which was more stable but not perfect). I'm
currently just running the 5.9.1 mainline kernel for testing purposes,
which so far (2 days in seems stable), but might just break later today,
who knows.
--
Corrupt lines, red flashing across the top bar:
https://photos.app.goo.gl/TgYxkVHRnsrV5wCR9
I use Xorg, and almost exclusively see it on my external monitor. After
locking the screen and having it locked for a while. Saw it once on the
internal one in a week, but like daily on external.
--
You r
Also adding a gnome-shell task. This happens on 5.8.0-21-generic from
proposed too, and restarting gnome-shell stops the corruptions, so it's
possible this is a gnome issue.
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification be
Actually I did at
https://bugs.chromium.org/p/chromium/issues/detail?id=1136411 as I see
it too
--
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/1898797
Title:
[1006/183929.019360:ERROR:na
The bug report title is the start of a chrome error message, and I can't
see any bug in the dmesg output, so I don't see how this is a bug in the
kernel. I suggest you open an issue on the Chrome bug tracker
https://crbug.com/ for your Chrome issue.
** Changed in: linux (Ubuntu)
Status: Con
Public bug reported:
Okt 07 20:45:43 jak-t480s kernel: BUG: kernel NULL pointer dereference,
address: 002c
Okt 07 20:45:43 jak-t480s kernel: #PF: supervisor read access in kernel mode
Okt 07 20:45:43 jak-t480s kernel: #PF: error_code(0x) - not-present page
Okt 07 20:45:43 jak-t480
The corruption also happens in build
5.9.0-050900rc4drmintelnext20200915-generic but the error in dmesg does
not, and it's less, it only happens on window management actions (switch
window
Surprisingly with that, restarting gnome-shell actually fixes the issue
(it did not with normal kernel).
--
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411757/+files/ProcModules.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/b
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411758/+files/PulseList.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/
Attached dmesg from journalctl. To the best of my knowledge, this is all
that's missing, as apport now has no raw dmesg access anymore and missed
to upload the dmesg.
** Attachment added: "kernel.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896091/+attachment/5411763/+files/kerne
Attached dmesg from journalctl. To the best of my knowledge, this is all
that's missing, as apport now has no raw dmesg access anymore and missed
to upload the dmesg.
** Attachment added: "kernel.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896091/+attachment/5411764/+files/kerne
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411761/+files/WifiSyslog.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/bug
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411762/+files/acpidump.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/18
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411759/+files/RfKill.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/1896091
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411760/+files/UdevDb.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/1896091
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411749/+files/Lspci-vt.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/18
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411755/+files/ProcEnviron.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/b
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411754/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411750/+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/1896091
apport information
** Tags added: apport-collected
** Description changed:
I left my desktop (T480s thinkpad docked to ThinkVision P24h-10)
unattended for a while, and then got the error message and now have
funny lines on activity, e.g. red lines flashing on top of gnome-shell
bar when
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411751/+files/Lsusb-t.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/1896
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411746/+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/1896091
Ti
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411747/+files/IwConfig.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/18
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411753/+files/ProcCpuinfo.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/b
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411752/+files/Lsusb-v.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/1896
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411756/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411748/+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/1896091
That said, hmm, it took an hour or so after the backtrace for it to
cause visual distortion or I misremember, or it gets worse over time.
--
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/1896
Public bug reported:
I left my desktop (T480s thinkpad docked to ThinkVision P24h-10)
unattended for a while, and then got the error message and now have
funny lines on activity, e.g. red lines flashing on top of gnome-shell
bar when switching windows, or white blocks/lines around typing text.
Th
That's correct, the menu should not show automatically, you either
configure it to do so or you press Esc during boot. Marking as invalid.
** Changed in: casper (Ubuntu)
Status: New => Invalid
** Changed in: grub2 (Ubuntu)
Status: New => Opinion
** Changed in: zfs-linux (Ubuntu)
There were no changes in that grub update affecting normal boot, only
microcode loading was disabled for recovery boots and a feature to
reorder kernels was added.
** Package changed: grub2 (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packag
For example, the measurements on the X220 do not reflect situation on
modern Intel systems, as they scale differently from Skylake and newer,
as they do not have HWP.
A CPU with HWP (hardware P-states) behaves as you'd expect sort of - it
runs at close to max frequency all the time, and scales dow
Why are we looking at focal now? The change to systemd only happened
after the opening of groovy.
Data is tricky. There are a ton of different cpufreq drivers that are
affected, and they all have different behavior. pstates alone has
different behavior on newer intels that do pstates in hardware (
Removing bootloader tasks, as the kernel has loaded successfully.
** No longer affects: grub2 (Ubuntu)
** No longer affects: syslinux (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/bu
Removed spurious grub task.
** No longer affects: grub2 (Ubuntu)
** No longer affects: grub2 (Ubuntu Focal)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1850130
Title:
zpools fai
The proposed debdiff is wrong, it reverts a patch in the patch series by
adding a new patch. I think we can probably remove the vt-handoff.patch
from the patch series for groovy without much checking, but any SRU will
need to consult with flavours to check if they need the handoff.
--
You receive
@Colin: I agree with all of that.
Our kernel-side default is not powersave, but performance, across
generic and oem, at the very least:
$ grep CPU_FREQ_DEFAULT_GOV_.*=y /boot/config-5.*
/boot/config-5.4.0-26-generic:CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
/boot/config-5.4.0-42-generic:CONFIG_CP
XPS 13 (Core i5-10210U) with performance governor idles (0.2% usage) at
4 GHz instead of 900 MHz.
--
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/1838141
Title:
intel_pstate not working.
passing intel_pstate=disable_hwp on the kernel commandline causes the
kernel to scale the Core i5-8250U down to 1.6 GHz in performance mode,
but that's still a bit off from the 900 MHz it scales down to in
powersave mode.
I believe Windows also does not run the CPUs in performance mode by
default
The performance governor is the right choice for servers, but it's not
the right choice on non-server platforms, it's also not the default
kernel setting, it was set because we have the ondemand.service in
userspace that can change it back to ondemand (or well we have the
service because of that ch
Andreas, I've not gotten it more isolated, the minimum I had was running
debian/tests/gnome-desktop-testing in a flatpak-builder source tree (apt
source/pull-lp-source flatpak-builder).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** 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/1885730
Title:
@rbalint As said before the kernel messages and bugs are irrelevant and
wrong. They pretend like intel_pstate is different, when in fact it's
this script that is configuring it here. And yes, it needs OS config.
Nor do other distros not do this, but we do it differently. We set the
CONFIG_CPU_FREQ
Someone probably needs to look at non-pstate systems as I have no idea
about them.
--
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/1885730
Title:
Bring back ondemand.service or switch ker
Public bug reported:
In a recent merge from Debian we lost ondemand.service, meaning all CPUs
now run in Turbo all the time when idle, which is clearly suboptimal.
The discussion in bug 1806012 seems misleading, focusing on p-state vs
other drivers, when in fact, the script actually set the defau
** Changed in: grub2 (Ubuntu)
Status: New => Incomplete
** Changed in: grub2 (Ubuntu Bionic)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1880
Readding linux-oem
** Also affects: linux-oem (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1880663
Title:
Dell Latitude 7300 s
There are two things:
- On servers, ubuntu-server depends on mdadm, so removing mdadm also
removes ubuntu-server package, which means it's not really supported
- In general, the installers don't offer installing like that.
I don't know why we did not have a task for xenial.
** Description chang
That's certainly incorrect, lvm2 was fixed in focal (and hence groovy).
That only leaves xenial, but updating xenial close to its EOL for
something as unusual as this seems unneccessary. The supported
configuration for raid1 is mdadm after all, not removing mdadm and the
meta packages that depend o
eoan verified.
So, eoan is tougher. I installed it with subiquity and tried to follow
the steps, but failed to convert to raid1, apparently, subiquity created
the LV 1 PE larger than before or something, so it needed 1 free PE in
the original PV to be able to add the raid1 metadata, which it did n
The regressions in bionic seem unrelated to me adding the raid1 module
to the list of modules installed to the initramfs.
--
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/1509717
Title:
Wi
verified in bionic
Did all the steps (install vm, create pv, extend pv, remove dmadm,
upgrade).
It booted after the upgrade to 2.02.176-4.1ubuntu3.18.04.3, and it
failed again following a downgrade to the 2.02.176-4.1ubuntu3.18.04.2
from updates pocket.
** Tags removed: verification-needed-bioni
** Description changed:
[Impact]
system does not boot after converting lvm volume to raid1 w/o having mdadm
installed.
[Test case]
1. Install server with subiquity to LVM
2. Add second disk to it
3. Run pvcreate /dev/vdb
4. Run vgextend ubuntu-vg /dev/vdb
5. Run lvconvert -m
** Description changed:
[Impact]
system does not boot after converting lvm volume to raid1 w/o having mdadm
installed.
[Test case]
1. Install server with subiquity to LVM
- 2. Add second disk to it
- 3. Run pvcreate /dev/vdb
- 4. Run vgextend ubuntu-vg /dev/vdb
- 5. Run lvconvert -m
** Description changed:
[Impact]
system does not boot after converting lvm volume to raid1 w/o having mdadm
installed.
[Test case]
- 1. Install server with subiquity to VM
+ 1. Install server with subiquity to LVM
2. Add second disk to it
3. Run pvcreate /dev/vdb
4. Run vgextend
sorry, working on verifying it, got distracted by other stuff.
--
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/1509717
Title:
Wily LVM-RAID1 – md: personality for level 1 is not loaded
S
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1863898
Title:
More i915 fixes to cherry-pick
Status in linux package
Public bug reported:
The kernel is still a bit unstable, according to upstream this should
fix my recent hangs:
drm/i915/execlists: Always force a context reload when rewinding
RING_TAIL
https://gitlab.freedesktop.org/drm/intel/issues/1164
https://gitlab.freedesktop.org/drm/intel/issues/1150
A
** Changed in: lvm2 (Ubuntu Eoan)
Status: Triaged => In Progress
** Changed in: lvm2 (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs
** Description changed:
- After upgrading to Wily, raid1 LVs don't activate during the initrd
- phase. Since the root LV is also RAID1-mirrored, the system doesn't
- boot.
+ [Impact]
+ system does not boot after converting lvm volume to raid1 w/o having mdadm
installed.
+
+ [Test case]
+
+ 1. I
** Changed in: lvm2 (Ubuntu Disco)
Status: New => Won't Fix
--
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/1509717
Title:
Wily LVM-RAID1 – md: personality for level 1 is not loade
Disabling TPM makes it boot
FWIW, the logs are from 5.2, as 5.3 did not boot earlier (because TPM
was still enabled).
--
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/1844101
Title:
5.3.0
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1844101/+attachment/5288942/+files/WifiSyslog.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/bug
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1844101/+attachment/5288941/+files/UdevDb.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/1844101
101 - 200 of 318 matches
Mail list logo