Given the options shown in firmware and switching to AHCI fixes things
as per xnox's comments; this is squarely a "kernel" issue -- one we
can't really fix in ubiquity in any case.
The kernel side, to support this new RAID or "Intel RST" mode comes with
its own set of problems, but I'll let the ke
Okay, this bug has absolutely nothing to do with grub or netplan.
Changing the renderer couldn't possibly affect the behavior of X, and
the grub configuration looks, at a glace, to be run-of-the mill; pretty
much default if you disregard that there is any number of different
installs on the system.
The system booted, so it's not a syslinux issue. Maybe kernel? I'm
unsure, as I didn't see anything obviously wrong (to me) in the attached
logs, but the mtrr messages are unusual and warrant some further
investigation.
Reassigning to linux.
** Package changed: syslinux (Ubuntu) => linux (Ubuntu)
I'll sponsor this patch.
Please follow the steps at
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure to update the bug
description for SRUing this to bionic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bu
Kees,
I the fix in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766052 sufficient
to address the situation? Do we still need to do more to systemd (note,
the GH issue was closed upstream following Dimitri's input)?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You
That's not /really/ helpful anyway. You'd have installed an extra
application, for a wholly unrelated issue, and still have to set the
profile to A2DP yourself.
Alistair, there are messages in your logs that seem to point to a firmware
issue:
Nov 26 16:56:25 albatross bluetoothd[1010]: Unable to
I'm uploading things now; let's keep them blocked in proposed just long
enough that I have the time for one last test before it reaches
everyone.
** Tags added: block-proposed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu
Public bug reported:
When attempting to load unsigned modules and the signatures are
enforced, a message shows in dmesg pointing to an inexistant manpage:
[...]
[5.154346] Adding 1003516k swap on /dev/mapper/10--3--99--105--vg-swap_1.
Priority:-2 extents:1 across:1003516k FS
[5.277619]
Verification-done on bionic:
ii dkms 2.3-3ubuntu9.1
all Dynamic Kernel Module Support Framework
ii virtualbox-dkms5.2.10-dfsg-6
all x86 virtualization solution - ker
** Description changed:
+ [Impact]
+ All Ubuntu users for whom Secure Boot is enabled.
+
+ [Test cases]
+ 1) install dkms module (use virtualbox-dkms for example)
+ 2) Upgrade kernel (for example, install 4.15.0-22-generic on top of
4.15.0-20-generic).
+ 3) Verify that the generated module for t
** Description changed:
+ [Impact]
+ All users of third-party modules on Ubuntu.
+
+ [Test cases]
+ 1) Install Ubuntu on an UEFI system
+ 2) Clear any files in /var/lib/shim-signed/mok: "sudo rm -rf
/var/lib/shim-signed/mok/*"
+ 3) Install virtualbox-dkms: "sudo apt install virtualbox-dkms"
+ 4)
** Description changed:
+ [SRU Justification]
+ Move to using self-signed keys for signing DKMS modules, along with the
wizard / guide to make this work properly, to let third-party modules be signed
and loaded by enforcing kernels, rather than disabling Secure Boot altogether.
+
+ [Test case]
** Description changed:
[SRU Justification]
Move to using self-signed keys for signing DKMS modules, along with the
wizard / guide to make this work properly, to let third-party modules be signed
and loaded by enforcing kernels, rather than disabling Secure Boot altogether.
[Test case]
Verification-done on xenial:
shim-signed/1.33.1~16.04.4
dkms/2.2.0.3-2ubuntu11.6
I've installed bbswitch on a test UEFI system, rebooted to disable
validation in shim; then upgraded to the new packages and could verify
that shim validation was re-enabled and a MOK was enrolled in the
firmware, as
Verification-done on trusty:
dkms/2.2.0.3-1.1ubuntu5.14.04.10
shim-signed/1.33.1~14.04.4
I've installed bbswitch on a test UEFI system, rebooted to disable
validation in shim; then upgraded to the new packages and could verify
that shim validation was re-enabled and a MOK was enrolled in the
firm
Verification-done on trusty:
dkms/2.2.0.3-1.1ubuntu5.14.04.10
I've installed bbswitch on a test UEFI system, upgraded the kernel to a
newer version (ie. linux-image-hwe-trusty-generic) and was still able to
load the module in; the module in the updates/dkms directory for the
kernel version is cle
Verification-done on xenial:
dkms 2.2.0.3-2ubuntu11.6
Upgraded kernel to hwe kernel, drivers can still be loaded from the
right versioned directory for the kernel and loads succesfully --
signature is validated fined as the kernel module is signed.
ubuntu@ubuntu:~$ dpkg -l shim-signed dkms | cat
Re-verified trusty since the previous trusty comment was imprecise:
dkms 2.2.0.3-1.1ubuntu5.14.04.10
Upgrading kernel and headers follows with a loadable, properly signed
module using the MOK generated previously.
ubuntu@ubuntu:~$ dpkg -l shim-signed dkms | cat
Desired=Unknown/Install/Remove/Pur
If you can still boot to Ubuntu with an older kernel (one that is
signed), here's what you can do:
1) Download http://archive.ubuntu.com/ubuntu/dists/xenial-
updates/main/uefi/grub2-amd64/2.02~beta2-36ubuntu3.20/grubx64.efi.signed.
2) Copy grubx64.efi.signed over /boot/efi/EFI/ubuntu/grubx64.efi:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1797975/+attachment/5201397/+files/CurrentDmesg.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
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1797975/+attachment/5201398/+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: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1797975/+attachment/5201400/+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
Public bug reported:
The follow error is shown in dmesg on my Raspberry Pi 2:
[4.380151] device-mapper: uevent: version 1.0.3
[4.388525] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised:
dm-de...@redhat.com
[4.396718] bcm2835-cpufreq: min=60 max=90
[4.407362] s
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1797975/+attachment/5201399/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1797975/+attachment/5201401/+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: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1797975/+attachment/5201402/+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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1797975/+attachment/5201403/+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/1797975
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1797975/+attachment/5201404/+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
There's a bit I don't understand:
"* Signature verification appears to be disabled, and cannot be enabled
again. It appeared to be enabled previously, as loading of unsigned
modules was failing, and `mokutil --enable-validation` runs without
incident; however, upon the next boot when attempting to
mic)
Importance: Undecided => Medium
** Changed in: shim (Ubuntu Cosmic)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
Is this still reproducible? We have changed the default gfx mode to stay
"text" on EFI.
--
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/1720197
Title:
Every second(?) boot fails to displa
Assigning to linux to we can investigate whether this is caused by a
kernel bug.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: grub2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Pa
How was this system installed? Was it installed in BIOS mode and then
changed to UEFI?
Is shim-signed correctly installed on the system? Without shim-signed
installed and present on the ESP partition
(/boot/efi/EFI/ubuntu/bootx64.efi); as well as listed as the BootEntry
to load (sudo efibootmgr -v
My guess is lodygin fails to boot from the network, and cycles all the
way to booting from Hard drive (0004), in which case, since shim and
everything really /are/ installed on disk, it gets run to recreate the
missing "ubuntu" entry.
Assuming you can reproduce this issue easily, can you check if
Not a kernel bug.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1790586
Title:
The proposed grub package in Trusty /
Seems like this is caused by nvidia drivers not liking s2idle or forcing
the use of 'deep' leads to reliable suspend/resume cycles. Properly
removing nvidia drivers leads to a working system.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
Get:1 http://archive.ubuntu.com/ubuntu cosmic/main amd64 libnl-3-200 amd64
3.4.0-1 [53.9 kB]
Get:2 http://archive.ubuntu.com/ubuntu cosmic/main amd64 libnl-genl-3-200 amd64
3.4.0-1 [11.1 kB]
Get:3 http://archive.ubuntu.com/ubuntu cosmic/main amd64 wireless-regdb all
2018.05
** 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/1800703
Title:
kernel packages die while running postinst scripts
Sta
Looks like it's depmod crashing; it's the only thing common between
linux-image and linux-modules postinst, and for linux-modules it's ||
true, thus we see the first "Killed" line but it doesn't fail the
package installation.
--
You received this bug notification because you are a member of Kern
Identified as the system running out of memory, this was a VM with only
1G RAM, and with 2G it's behaving fine. Closing as Invalid.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
Public bug reported:
Dell XPS 15 (9750); it might eventually manage to suspend when the lid
is closed, but more often than not will not wake up again when the lid
is opened. Waking up using the power button often results in a system
that is apparently frozen (graphics displayed are the last on scr
Public bug reported:
At some point after boot, the USB3 system stops working. Anything
plugged on it is unresponsive, my system however keeps responding to
everything else. If I move keyboard/mouse to USB2 ports, it works again,
but nothing replugged to USB3 ports works.
There are kernel error me
** Tags removed: verification-failed
--
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/1729573
Title:
netplan breaks Xen VIF driver
Status in linux package in Ubuntu:
Won't Fix
Status in
Assigning to security as per the description...
** Changed in: thunderbolt-tools (Ubuntu)
Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thunderbolt-tools in Ubuntu.
M
dkms changes in debdiff format. There didn't seem to be a code branch
for dkms specific to Ubuntu.
** Patch added: "dkms.debdiff"
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1748983/+attachment/5053788/+files/dkms.debdiff
--
You received this bug notification because you are a member
High
Assignee: Mathieu Trudel-Lapierre (cyphermox)
Status: In Progress
** Affects: shim-signed (Ubuntu)
Importance: High
Assignee: Mathieu Trudel-Lapierre (cyphermox)
Status: In Progress
** Also affects: dkms (Ubuntu)
Importance: Undecided
Status: New
** Chang
There are dkms changes and shim-signed changes for this. I'm linking
both.
--
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/1748983
Title:
Generate per-machine MOK for dkms signing
Status
https://code.launchpad.net/~ubuntu-core-dev/shim/+git/shim-signed/+ref
/self-signed
--
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/1748983
Title:
Generate per-machine MOK for dkms signing
This would be a kernel bug if anything, but will require more
information.
** Package changed: partman-efi (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/1237776
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: nplan (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: nplan (Ubuntu Xenial)
Importa
Public bug reported:
'/sbin/mdadm --examine --scan --config=partitions' hangs. This can be
trivially reproduced when updating a kernel or updating the initramfs,
or just running the program directly.
Relevant excerpt from stracing the process:
[...]
getdents(4, /* 0 entries */, 65536) = 0
cl
nplan (0.13) zesty; urgency=medium
[ Jonathan Cave ]
* Blacklist mwifiex_pcie from rebinds (work around LP: #1630285)
[ Martin Pitt ]
* Add support for nameservers (LP: #1626617)
** Changed in: nplan (Ubuntu)
Status: New => Fix Released
** Changed in: nplan (Ubuntu Yakkety)
Verification done for yakkety's multipath-tools SRU:
multipath-tools 0.5.0+git1.656f8865-5ubuntu7.3
I verified that multipath-tools correctly ships its new hook to include
dm-service-time and dm-queue-length, and the system with that update
boots successfully.
** Tags removed: verification-neede
Verification done for yakkety:
I have verified that the workaround for mwifiex is present in nplan
0.23~16.10. No further testing can be done due to the fact that I don't
have any hardware that uses the mwifiex driver.
** Tags removed: verification-needed
** Tags added: verification-done-yakkety
Closing the nplan xenial task as Fix Released since it already have
nplan 0.14~16.04; which contains the fix for mwifiex -- this was
released in 0.13; backported as 0.13~16.04 (which was landed prior, but
also included in 0.14~16.04 in xenial-updates).
** Changed in: nplan (Ubuntu Xenial)
S
Somehow this appears to have possibly landed in xenial without
undergoing the verification expected (which might explain why it was
still in New, rather than Fix Committed).
I have set this back to Fix Committed for xenial, and re-did the
verification. As above, verification was limited to making
Public bug reported:
Loading initial ramdisk ...
OF stdout device is: /vdevice/vty@7100
Preparing to boot Linux version 4.11.0-13-generic (buildd@bos01-ppc64el-022)
(gcc version 6.4.0 20170724 (Ubuntu 6.4.0-2ubuntu1) ) #19-Ubuntu SMP Thu Aug 3
15:11:49 UTC 2017 (Ubuntu 4.11.0-13.19-generic 4
Can't run apport-collect; looks like there's nothing to save the apport
data in this kind of case, so I can't transmit it anywhere. I'll see if
I can reproduce this on amd64, should make it easier.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug noti
** Package changed: debian-installer (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
Canonical Kernel (canonical-kernel)
** Changed in: ubuntu-power-systems
Assignee: Canonical Foundations Team (canonica
I can't run apport-collect in that environment, but this is trivial to
reproduce in any ppc64el qemu VM. Just use JFS as the filesystem for the
root partition.
I can provide scripts to help setting up the VM.
** Changed in: linux (Ubuntu)
Status: Triaged => Confirmed
--
You received this
This had already been identified and "fixed" on Wednesday, probably
around the time the bug was filed (I uploaded the main-menu update
around 11h30 EST). For posterity, I've captured relevant information at
http://people.canonical.com/~mtrudel/lp1694531/)
Unfortunately, it's just the kind of bug t
Moving to main-menu and closing the ubiquity task: ubiquity was
unaffected (it was an issue with a bad USB key, and ubiquity does not
use main-menu in any way). It's obviously also not a kernel issue.
Thanks for Joseph for the great debugging work!
** No longer affects: ubiquity (Ubuntu)
** Also
Public bug reported:
Jun 5 17:51:02 moloch kernel: [30492.554641] BUG: unable to handle kernel NULL
pointer dereference at 0018
Jun 5 17:51:02 moloch kernel: [30492.554769] IP:
gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
Jun 5 17:51:02 moloch kernel: [30492.554848
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1696009/+attachment/4889640/+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/1696009
Ti
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1696009/+attachment/4889643/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1696009/+attachment/4889647/+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: "PulseList.txt"
https://bugs.launchpad.net/bugs/1696009/+attachment/4889651/+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/
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1696009/+attachment/4889644/+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/1696009
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1696009/+attachment/4889642/+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/16
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1696009/+attachment/4889650/+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: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1696009/+attachment/4889639/+files/AlsaInfo.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/16
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1696009/+attachment/4889648/+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: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1696009/+attachment/4889645/+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/1696009
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1696009/+attachment/4889641/+files/CurrentDmesg.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
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1696009/+attachment/4889649/+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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1696009/+attachment/4889646/+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: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1696009/+attachment/4889654/+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/1696009/+attachment/4889653/+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/1696009
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1696009/+attachment/4889652/+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/1696009
** Also affects: nplan (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: nplan (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Yakkety)
Importance:
s: New
** Changed in: multipath-tools (Ubuntu)
Status: New => Triaged
** Changed in: multipath-tools (Ubuntu)
Importance: Undecided => Critical
** Changed in: multipath-tools (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: initramf
ct (Ubuntu)
Importance: Undecided
Status: New
** Changed in: hw-detect (Ubuntu)
Importance: Undecided => Critical
** Changed in: hw-detect (Ubuntu)
Status: New => Triaged
** Changed in: hw-detect (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cypher
** Description changed:
+ [Impact]
+ Multipath users using EMC XtremIO storage as boot device or at install time
may run into this issue. With the module unavailable the device is more often
than not unavailable. Any users changing path selector to 'queue-length' with
other storage devices may
AFAICT there wouldn't really be any change required to initramfs-tools
-- everything is contained in multipath-tools-boot.
** Changed in: initramfs-tools (Ubuntu)
Status: Triaged => Invalid
** Changed in: initramfs-tools (Ubuntu)
Milestone: ubuntu-17.03 => None
** Changed in: initramf
MIR approved.
** Changed in: linux-aws (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1672850
Title:
[MIR] linux-aws
Status in linux-aw
** Changed in: hw-detect (Ubuntu)
Status: Triaged => 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/1673350
Title:
dm-queue-length module is not included in installer/
The hw-detect change is uploaded, so once it's in the archive, installs
on hardware requiring dm-queue-length should work without issues.
We're still blocked on having the kernel include dm-queue-length and dm-
service-time for the installer for the hw-detect side of this SRU to
yakkety and xenial
** Changed in: hw-detect (Ubuntu Xenial)
Status: New => In Progress
** Changed in: hw-detect (Ubuntu Xenial)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: hw-detect (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: hw-detec
The update of shim, grub, mokutil and others to use signed kernels and
modules are mostly done; one further step that needs to happen is to
have grub enforce that kernels are properly signed, and refuse to load
unsigned kernels (rather than falling back from the linuxefi module
which checks signatu
No, it's not widely broken. Some things are broken on some hardware, and
it's not all broken in the same way, that's why I asked for logs -- so
we can know what the actual issue is.
I don't have all the hardware in the world, so I can't reproduce these
issues myself.
Dave, if you're still having
If os-prober is not running, I don't see what else might be poking the
disks to cause the warnings. We must ignore the other warning messages
that were listed from syslog earlier and look at it a different way. Is
the Redhat system showing the same write errors?
Is HTX doing raw writes to disk or
Setting back to 'linux', and leaving as Incomplete until we get a
response from the original submitter.
** Package changed: ubiquity (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.
Right, that's what I expected, but it's good to be sure.
The bug is assigned to the kernel team, they will want to look into it.
To further define the case, are these devices claimed by multipath or by
mdadm? What does 'sudo multipath -ll' show? Multipath or mdadm (or other
low-level storage serv
riaged
** Changed in: grub2 (Ubuntu)
Status: New => Triaged
** Changed in: dkms (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notificat
Reassigning to grub2, which seems more appropriate at a quick glance.
I'll look to reproduce this tomorrow.
** Package changed: linux (Ubuntu) => grub2 (Ubuntu)
--
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:
[Rationale]
Secure Boot is good. We want to be able to validate that as much as possible of
the boot process happens with signed binaries; from our shim (the part that is
loaded by the EFI firmware itself), down to grub2, the kernel, and even loaded
modules.
[Impact]
All o
This also needs a mokutil update, as the version in >=14.04 will not
work correctly with *-lts* kernels.
** Also affects: mokutil (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in
That should have read, any version of mokutil below 0.3.0-0ubuntu3~ will
not work correctly with lts kernels on the LTS releases.
--
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/1574727
Titl
** Also affects: efivar (Ubuntu)
Importance: Undecided
Status: New
** Also affects: grub2 (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: dkms (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: shim (Ubuntu Precise)
Importance
Status: Confirmed => Triaged
** Changed in: grub-installer (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
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/15
1 - 100 of 236 matches
Mail list logo
