On 2019-05-21 05:28:18, Mark wrote:
> > If that doesn't work, can you try to boot with 'mitigations=off'
> > passed on the kernel command line?
>
> on the other hand, mitigations=off did cut it!
> I guess now we're to find which of the mitigations is causing it? Do
> you have a hint? Which are
PS,
#dmesg | grep microcode
#
returns nothing on the ubuntu hwe-edge kernel with mitigations=off
(=problematic ucode otherwise loaded)
Actually, is the microcode loaded at all?
# cat /sys/devices/system/cpu/cpu0/microcode/version
cat: /sys/devices/system/cpu/cpu0/microcode/version: No such
Tyler,
> Can you try to boot with the latest Ubuntu kernel, with the
problematic microcode, using 'mds=off' on the kernel command line? (Note
that it is 'off' instead of 'no')
I tried with mds=off, but no avail.
> If that doesn't work, can you try to boot with 'mitigations=off'
passed on the
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1829812
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
This test will failed to build on 5.0.0-16 Disco.
5.0.0-16 Disco + 5.0.0-15 source code - build OK
5.0.0-16 Disco + 5.0.0-16 source code - Failed
make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
gcc -o
Mark, one more request for now. You say that you can boot up a non-
Ubuntu kernel with the problematic microcode. Can you boot up one of
those kernels and then verify the microcode revision with the following
command:
$ sudo cat /sys/devices/system/cpu/cpu0/microcode/version
Please paste the
Simon, can you post the contents of /proc/cpuinfo as well? It'd help
with tracking down which processors might be affected by this. Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I found this issue on B-hwe 4.18, node "gonzo" (passed on another node
amaura)
--
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/1812988
Title:
ff76b0565523319d7c1c0b51d5a5a8915d33efab in
This is something that's failing for a while (was affected by bug
1802443, and then this one since 4.18.0-13.14~18.04.1)
--
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/1802495
Title:
Update: The patches have been merged to drm-tip:
https://cgit.freedesktop.org/drm-
tip/commit/?id=1a74fc0b3f49a0603f230b6f087da33bda3d7c66.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Someone probably needs to find a relevant upstream Xorg bug link to see
where/if it is being discussed there.
This is not the place where Xorg developers discuss such things.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
On Intel ICL-Y SDP(alpha):
Before patched
short idle: 13.46w
long idle: 12.94w
s2idle: 12.67w
After patched:
short idle: 13.45w
long idle: 13.06w
s2idle: 12.87w
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
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/1827967
Title:
There are 4 HDMI/Displayport audio
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-xenial
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
I'll point out that munbi is seeing this hit using the following CPU sig
and microcode revision:
sig=0x306c3, pf=0x10, revision=0x27
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hello and thanks for the bug report. We hate to hear that you're seeing
such a performance hit on your application when the MDS mitigations are
enabled. Unfortunately, we are simply following Intel's
recommendations[1] for mitigating MDS attacks. The kernel changes are
relatively simple and the
I have almost the same problem.
i run ubuntu 14.04 and for me its linux 4.4.0-146 that starts normal
148 only give the purple ubutu screen, but nothing after that
148 recovery stops after initial RAM disk
--
You received this bug notification because you are a member of Kernel
Packages, which
Take care, current kernel 4.15.0-1036.38 still not bootable with EFI.
** Changed in: linux-raspi2 (Ubuntu)
Status: Fix Committed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
Correct, the qrt script needed to catch up to the config changes that
have landed in the 4.4, 4.15, and 4.18 kernel branches. I've done this
in https://git.launchpad.net/qa-regression-
testing/commit/?id=fca40854ff8d65c1fb4a19f57a8e541e3655aab9 .
Closing tasks, thanks.
** Changed in:
$ grep BINFMT_AOUT /boot/config-4.18.0-2[01]-generic
/boot/config-4.18.0-20-generic:CONFIG_BINFMT_AOUT=m
/boot/config-4.18.0-21-generic:# CONFIG_BINFMT_AOUT is not set
Marking cosmic as verification-done.
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
Thank you for your reply and for looking into this issue. I will contact
Lenovo but I won't get my hopes up. Operating the dock w/o MAC
passthrough is luckily not a big deal for me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Mark, thanks for all the testing. Unfortunately, I asked Steve to have
you try the wrong 'mds=' option.
Can you try to boot with the latest Ubuntu kernel, with the problematic
microcode, using 'mds=off' on the kernel command line? (Note that it is
'off' instead of 'no')
If that doesn't work, can
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
--- Comment From hb...@us.ibm.com 2019-05-20 15:29 EDT---
We need this fix in 18.04.X. Without these patches, 842 compression is broken
which can affect zswap or other workloads that can exploit HW compression.
Simple fix which modifies only NX module
--
You received this bug
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
--- Comment From mranw...@us.ibm.com 2019-05-20 15:09 EDT---
I tried that kernel out and it works:
root@ltc-boston25:/home/ubuntu/comp_selftest# cat /proc/version
Linux version 4.15.0-51-generic (buildd@bos02-ppc64el-003) (gcc version 7.4.0
(Ubuntu 7.4.0-1ubuntu1~18.04))
PaulSchulz, the issue you are reporting is an upstream one. Could you
please report this problem following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing
list (TO Amitkumar Karwar, Nishant Sarmukadam, Ganapathi Bhat, and
Xinming Hu CC linux-wireless)?
> Also, do systems succesfully boot when 'mds=no' is passed on the
kernel command line with the problematic microcode in place?
no, this does not help
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi Steve,
no problem, thank you for digging into this!
> ith the affected processors report the output of:
iucode-tool -S
# iucode-tool -S
iucode-tool: system has processor(s) with signature 0x000806eb
> is it correct that you are *not* seeing this with 5.0 kernel from the
> linux-hwe-edge
TJ,
> An additional kernel command-line option that might reveal more would be
> remove "quiet splash" and add "debug early_print=XXX" where XXX is vga for
> BIOS-mode or efi for UEFI mode boots.
You may find "earlycon"
no info provided using these options, still stuck at the initrd line
Interesting, I see different behaviors in my setup:
4.4 on lvl1, 4.15 lvl2, trusty lvl1 qemu:
/proc/cpuinfo in lvl2 contains:
bugs: cpu_meltdown spectre_v1 spectre_v2 l1tf
(note missing mds, hence "Not Affected")
4.4 on lvl1, 4.15 lvl2, xenial lvl1 qemu:
/proc/cpuinfo in lvl2
Also, do systems succesfully boot when 'mds=no' is passed on the kernel
command line with the problematic microcode in place?
--
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/1829620
Title:
Is there any update on this?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu.
https://bugs.launchpad.net/bugs/1823516
Title:
Nvidia driver installed but X apps are using software rendering
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-xenial
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
Hi, sorry the intel-microcode update is causing problems. Could one of
you with the affected processors report the output of:
iucode-tool -S
Mark, is it correct that you are *not* seeing this with 5.0 kernel from
the linux-hwe-edge kernel? Can you report the output of 'dmesg | grep
microcode'
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in:
--- Comment From hbath...@in.ibm.com 2019-05-20 13:34 EDT---
(In reply to comment #61)
> Issue is now "Fix Released" everywhere except Xenial. Should this now be
> backported to Xenial or would that incur too much regression risk?
No regressions expected but would be better off taking
I think it's fine. It sounds like there will just be no way to override
package-installed blacklists any more. That's unfortunate, but it's a
very rare situation.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Won't Fix
** Changed in: linux (Ubuntu)
Status: Incomplete =>
Same problem with Fedora, starting there with kernel 5.0.14:
https://bugzilla.redhat.com/show_bug.cgi?id=1710185
** Bug watch added: Red Hat Bugzilla #1710185
https://bugzilla.redhat.com/show_bug.cgi?id=1710185
--
You received this bug notification because you are a member of Kernel
Mark:
An additional kernel command-line option that might reveal more would be
remove "quiet splash" and add "debug early_print=XXX" where XXX is vga
for BIOS-mode or efi for UEFI mode boots.
You may find "earlycon" added into the mix may also add more early
messages.
See
Marking as an SRU regression and assigning to the Security Team uploader
for follow-up.
** Tags added: regression-security regression-update
** No longer affects: cryptsetup (Ubuntu)
** Changed in: intel-microcode (Ubuntu)
Assignee: (unassigned) => Steve Beattie (sbeattie)
--
You
All three test kernels have passed 24+ hour testing.
** Tags added: verification-done-bionic
** Tags removed: verification-done-bionic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Andrea,
I have confirmed it is working as intended.
-kim
--
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/1819485
Title:
AMD Rome : Additional patches
Status in linux package in Ubuntu:
E.g. in /proc/cpuinfo the whole section is missing:
bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
mds
^^ this is not there when "Not affected" is reported
Separating kernels:
3.13 on both: Works
4.4 on lvl1, 3.13 on lvl2: Fail
3.13 on lvl1, 4.4 on lvl2: Works
So
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Confirmed
WORKAROUND 2: downgrade (and hold) intel-microcode to older version from
bionic/main
apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1
Q: How comes liquorix kernel boots with the current micorcode ok?
Problem scoped down to:
intel-microcode from HWE (18.04.2) causes
** Summary changed:
- linux-aws: -proposed tracker
+ linux-aws: 4.4.0-1045.48 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in:
** Changed in: kernel-sru-workflow/snap-release-to-beta
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/snap-release-to-candidate
Status: New => Confirmed
** Changed in: kernel-sru-workflow/snap-release-to-edge
Status: Confirmed => Fix Released
**
`sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.bckp`
`sudo apt install nvidia-driver-` (check in GUI "Additional Drivers",
mine is `430`)
everything works. Even the screen layout wasn't broken.
Thx to Dmitrii!
--
You received this bug notification because you are a member of Kernel
Packages,
** Tags removed: cryptsetup plymouth splash wayland-session
** Tags added: microcode
** Description changed:
Description:
- my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of
booting, after grub)
- does not even show the enter cryptsetup passphrase
- affected
Verified on 5.0.0-16, it works as expected, thank you Christian!
** Tags removed: verification-needed-disco
** Tags added: verification-done-disco
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1829620/+attachment/5265099/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Dell Precision 5520 freeze cuz of Nvidia confirmed.
`sudo apt purge 'nvidia*'` solved it. Let's see what happens after I install it
again.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1829620/+attachment/5265097/+files/Dependencies.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1829620/+attachment/5265098/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
> I'm wondering if the recent Intel microcode updates and related kernel
patches could be responsible? Can you tell us what CPU the system has?
And BINGO!
This was my suspicion too, I found a way to disable microcode updates to verify
this:
WORKAROUND: disable intel microcode updates
>From
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
+
ASUS zenbook ux433fn CPU info on machine hit by this bug.
** Attachment added: "/proc/cpuinfo"
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+attachment/5265096/+files/zenbook14_ux433fn_cpuinfo.txt
--
You received this bug notification because you are a member of
hi TJ, thank you very much for the helpful debug instructions!
> I just realised your report isn't about cryptsetup being the problem
and you never reach the initialramfs shell.
Yes, this is the case. Still, checked the lsinitramfs and the image
files are OK, with all the cryptsetup binaries.
I
> > Hardware
> We use a laptop Asus vivobook S15 (we both have the very same model)
This leads me to hypothesis: The bug affects only(?) ASUS with later
(Kaby lake) Intel CPUs ?
** Summary changed:
- cryptsetup stuck at loading initramfs
+ ASUS microcode/kernel stuck at loading initramfs
**
** Also affects: nvidia-settings (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: nvidia-settings (Ubuntu Disco)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: nvidia-settings (Ubuntu Disco)
Importance: Undecided => Medium
** Changed in:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1829196
Title:
linux-gcp:
I do wonder, if we can somehow arch-specify opal signing.
Cause it's opal for power, zipl for s390x, yet both just use kmodsign.
Just a different key.
Not sure if i want to copy all the methods, and tests.
--
You received this bug notification because you are a member of Kernel
Packages, which
Disabling the kernel system call tracing for the moment:
https://kernel.ubuntu.com/git/ubuntu/autotest-client-
tests.git/commit/?id=b1654ce9e8d7d744af76787b6d4a5ff7bcec387d
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1829196
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1829200
Title:
linux-gcp:
Course bisect, this does not work with stock upstream kernels since at
least 4.7-rc1. For now I'm going to disabled this part of the lttng
tests until I can get it to work again with stock 4.8+ kernels.
@Sam, am I missing something, but has this been failing for a while and
it's not been
Also have same symptoms following 19.04 upgrade.
--
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/1825499
Title:
Touchpad vertical sensitivity is much higher than horizontal
sensitivity
** Summary changed:
- linux-oracle: -proposed tracker
+ linux-oracle: 4.15.0-1014.16~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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/1827755
Title:
nx842 - CRB request time out (-110) when uninstall NX
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in:
** Changed in: kernel-sru-workflow/security-signoff
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
** Changed in: ubuntu-power-systems
Status: Triaged => Incomplete
--
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/1802233
Title:
hwclock test failed on Power9 due to 0.x sec
Andrea,
Thank you I will test.
Please IGNORE the CCP/PSP patches, we do not want them back ported. Look
at comment #17.
--kim
--
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/1819485
** Changed in: kernel-sru-workflow/security-signoff
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
** Changed in: kernel-sru-workflow/security-signoff
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
** Changed in: ubuntu-power-systems
Status: Triaged => Incomplete
--
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/1827755
Title:
nx842 - CRB request time out (-110) when uninstall
IBM is also working on a justification for this patch, that they are
planning to add to this bug.
--
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/1827755
Title:
nx842 - CRB request time
** Changed in: kernel-sru-workflow/security-signoff
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
Would a similar BMC firmware release from AMI fix this issue for Bostons
systems? and is there an ETA for when that will be available to us.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Mark
I just realised your report isn't about cryptsetup being the problem and
you never reach the initialramfs shell.
Your report that the last thing you see is "my system gets stuck at
"Booting, Loading initramfs" tells us the kernel isn't starting. Those
messages come from GRUB when it loads
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Mark
--
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/1829620
Title:
cryptsetup stuck at loading initramfs
Status in cryptsetup package in Ubuntu:
New
Status in linux package in
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1829196
1 - 100 of 252 matches
Mail list logo
