** Changed in: atlas (Ubuntu)
Importance: Undecided => Low
--
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/1837525
Title:
[20.04 FEAT] Set Architecture Level (ALS) to z13
Status in Ub
linux_4.15.0-54.58.dsc -> cannot be built on eoan. and failed very
quckily.
linux_4.15.0-55.60.dsc -> builds for a very long time until my machine
runs out of disk space. And does get past the beginning of the build
where it fails.
** Tags removed: verification-needed-bionic
** Tags added: verifi
** Information type changed from Private to Public
--
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/1829027
Title:
[19.10 FEAT] Secure boot in kernel
Status in Ubuntu on IBM z Systems:
Public bug reported:
ppc64el does not support CONFIG_KERNEL_LZ4 yet it is now going to be
used by default on Ubuntu on x86 and s390 architectures.
Can CONFIG_KERNEL_LZ4 please be added upstream to the powerpc port?
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
Y
Please ignore the xenial verification request, as it was generated in
error. I can confirm this issue is resolved in bionic and up and calls
for no further actions. I apologise for any inconvenience caused.
--
You received this bug notification because you are a member of Kernel
Packages, which i
** Information type changed from Private to Public
--
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/1830731
Title:
[19.10 FEAT] Thin provisioning base support (kernel+390tools)
Status in
Public bug reported:
cherrypick has_sipl fix from the s390 maintainer tree
https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git/patch/?id=4df9a82549cfed5b52da21e7d007b79b2ea1769a
Otherwise, has_secure sysfs attribute is never correct.
** Affects: linux (Ubuntu)
Importance: Undeci
rom commit 4df9a82549cfed5b52da21e7d007b79b2ea1769a
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git)
Signed-off-by: Dimitri John Ledkov
---
drivers/s390/char/sclp_early.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/s390/char/sclp_early.c b/drivers/s390/char/sc
From: Philipp Rudo
BugLink: https://bugs.launchpad.net/bugs/1843961
Kernel lock down isn't initalized in common but in arch code. So
initialize it for s390 as well.
Signed-off-by: Philipp Rudo
Signed-off-by: Dimitri John Ledkov
---
arch/s390/kernel/setup.c | 2 ++
1 file chang
Public bug reported:
Kernel lock down isn't initalized in common but in arch code. So
initialize it for s390 as well.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Changed in: linux (Ubuntu)
Status: New => Triaged
--
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/1843961
Title:
s390/setup: Actually init kernel lock down
Status in linux pack
Open the ppa page: https://launchpad.net/~ubuntu-power-
triage/+archive/ubuntu/lp1758264/
Click on Technical details about this PPA
This will show you the URLs to the flat PPA http://ppa.launchpad.net
/ubuntu-power-triage/lp1758264/ubuntu/ from there you can download debs
from the pool by hand, a
@rrs
> BTW, does Ubuntu have the systemd/udevd mount propagation fix included ?
yes no maybe =
Added in debian at ed16ca8690eb69c248a0a741def5324eedc9149d
Removed from debian at d529d047752d8492d43e42e8b4223d6d37fa3dd3
Meaning it was for a while, if you mean the Debian bug linked to this bug
Please note, I'm not part of the release team.
Over the lifetime of bionic userspace it will be used on newer kernels,
or those that backport this particular feature.
Despite this being a "new" interface, I see this as actually a minor bug
and deficiency of Linux platform, given that other operat
Two things.
SCSI_SCAN_ASYNC=y is set from xenial to bionic.
If we believe this is what is causing the race here, we can try booting
d-i with a kernel parameter 'scsi_mod.scan=sync' specified. (or i can
rebuild d-i with such kernel cmdline built-in if required). And check if
that helps to resolve
Can somebody please test that booting d-i with `scsi_mod.scan=sync` on
the kernel command line, on the previously affected system, makes IPR
discovery work as expected, by the time one reaches the partitioning
menu without any mitigations required from the user?
--
You received this bug notificat
So my current feelings about this are as follows:
udev-udeb should ship /lib/modprobe.d/ directory
It should contain systemd.conf, just like the deb udev package, which
sets bonding max_bonds=0 and dummy numdummies=0.
It should also contain scsi-scan-sync.conf that that sets `options
scsi_mod sc
in: systemd (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: systemd (Ubuntu)
Importance: Undecided => Critical
** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-18.04
** Changed in: debian-installer (Ubuntu)
Milestone: later => ubuntu
I thought this was mentioned today and/or was being worked on. To check
with adam.
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Upgrading from 16.04 to
Last comments synced to launchpad indicated that migration of 18.04
guests, using 16.04 hypervisor is still not working.
And it would be nice, if it did.
So to me it looks like the bug is still present, even if you want to
close this ticket on your side.
ps. last comment we have synced prior to
** Information type changed from Private to Public
--
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/1776631
Title:
[18.10 FEAT] I/O device pre-configuration
Status in Ubuntu on IBM z Syst
** Changed in: s390-tools (Ubuntu)
Status: New => Fix Committed
--
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/1776631
Title:
[18.10 FEAT] I/O device pre-configuration
Status in
** Information type changed from Private to Public
--
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/1787898
Title:
[18.10 FEAT] Add kernel config option "CONFIG_SCLP_OFB"
Status in Ubuntu
** Description changed:
For successfully booting an IBM Secure Service Container Appliance in an s390
LPAR, we need to be able to send the OFB (Open for Business) message to the
Support Element to signal when the Appliance is fully up and running.
Basic support for OFB was added to the kerne
I think we want this in d-i, subiquity, curtin/MAAS, and backported to
bionic as well.
This is now in cosmic. Could you please install cosmic, upgrade to
latest s390-tools, enter things via HMC and reboot the instance to see
if it picks up and auto-activates devices specified via the HMC?
** Also
** Changed in: s390-tools (Ubuntu)
Status: Triaged => Confirmed
** Changed in: s390-tools (Ubuntu)
Importance: High => Critical
** Changed in: s390-tools (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are
** Changed in: s390-tools (Ubuntu)
Status: Confirmed => Fix Committed
--
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/1788314
Title:
Conflict between zfs-linux and s390-tools
This is all correct - thanks for testing.
This feature has currently only landed for the installed systems only; in
cosmic only at the moment.
On launchpad side, you can see that there are still tasks open to fix
this in bionic; and in the installers.
--
You received this bug notification bec
All commits listed apply cleanly, apart from a couple where git (at
least for me) gets confused about too many deletions. Forwarding to
kernel team for consideration into unstable tree.
** Information type changed from Private to Public
** Description changed:
- Provide support for next generati
What about calling it like this:
$ sudo systemd-run ./testcases/bin/msgstress03
Does that make it pass correctly?
Which resource in particular is exhausted? and can it be toggled somehow
using any of
https://www.freedesktop.org/software/systemd/man/systemd.directives.html
?
** Changed in: syste
Does this still fail with v239 which has now landed?
** Changed in: systemd (Ubuntu Cosmic)
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/1776654
Title:
Public bug reported:
22:17:19 DEBUG| Running 'git clone --depth 1
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/cosmic linux'
22:17:19 ERROR| [stderr] Cloning into 'linux'...
22:18:06 ERROR| [stderr] warning: You appear to have cloned an empty repository.
And later:
22:18:
Similarly:
08/29 22:16:44 DEBUG| utils:0116| Running 'git clone --depth 1
https://git.launchpad.net/qa-regression-testing'
08/29 22:16:44 ERROR| utils:0153| [stderr] Cloning into
'qa-regression-testing'...
08/29 22:17:06 ERROR| utils:0153| [stderr] warning: You appear to have
cloned
https://bileto.ubuntu.com/#/ticket/3394 should end up with autopkgtests
detailing what's happening.
--
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/1789774
Title:
linux s390x cosmic autop
what confuses me is why "https://"; protocol is used here, instead of
git:// protocol.
--
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/1789774
Title:
linux s390x cosmic autopkgtests fail
** Changed in: kexec-tools (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1783086
Title:
[18.10 FEAT] Enable kexec_file_load system
systemd-shutdown does use kexec tool, but it calls it with 'kexec --load' &
'kexec -e', it does not use 'kexec -s'.
Then again changing systemd shutdown, might be pre-mature, as we really don't
have things to use with 'kexec -s' yet.
--
You received this bug notification because you are a membe
** Changed in: linux (Ubuntu)
Milestone: None => ubuntu-18.10
--
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/1789934
Title:
[18.10 FEAT] Add kernel config options for SMC-R/D
Status
** Changed in: linux (Ubuntu)
Milestone: None => ubuntu-18.10
--
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/1784331
Title:
[18.10 FEAT] zcrypt DD: introduce APQN tags to support det
** Package changed: linux (Ubuntu) => network-manager (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/1790098
Title:
vlan created on bond fails auto activation on updating parent
Do you have swap?
Is the resume device correct?
$ sudo blkid | grep swap
$ grep RESUME -r /etc/initramfs-tools/
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Or maybe MCELOG should be disabled in the Ubuntu kernel config.
** Changed in: mcelog (Ubuntu)
Assignee: (unassigned) => Steve Langasek (vorlon)
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- No mcelog in bionic.
+ Missing mcelog userspace
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Kees Cook (kees)
--
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/1766052
Title:
Incorrect blacklist of bcm2835_wdt
Sta
Not sure if this raspbery pi is armhf or arm64.
Comparing armhf & arm64 blacklists, neither are changed between release
pocket and -proposed.
armhf does not have bcm2835_wdt listed, and arm64 does.
These are for the generic kernel.
$ grep bcm2835 *.conf
blacklist_linux_4.15.0-20-generic.conf:bl
I wonder if
grep -v '^bcm2835_wdt$$' | \
should actually be
grep -v '^bcm2835_wdt.ko$$' | \
given that next line strips .ko suffix:
sed -e 's/^/blacklist /' -e 's/.ko$$//' | \
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
I think this is actually fine. Ship it.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Cosmic)
Importance: Medium
Assignee: Kai-Heng Feng (kaihengfeng)
Status: Confirmed
** Description changed:
+ [Impact]
+
+ * Bogus keycode messages produced by the kernel / user annoyance
+ * rfkill keyboard shortcuts not working as intended on some Dell machines
+
+ [Test Case]
+
+ * check that there are no spurious kernel messages about unknown keys
+ in journalctl upon R
** Description changed:
[Impact]
- * Bogus keycode messages produced by the kernel / user annoyance
- * rfkill keyboard shortcuts not working as intended on some Dell machines
+ * Bogus keycode messages produced by the kernel / user annoyance
+ * rfkill keyboard shortcuts not working as i
Imho, we should ship all modules in udebs. Because missing a module in a
udeb is pain.
--
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/1503218
Title:
debian-installer: review our d-i conf
** Also affects: klibc (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Cosmic)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: Fix Released
** Also affects: systemd (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Cosmic)
Status: In Progress => Fix Committed
--
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/1760106
Title:
FFe: Enable configuring resume offset via
Removing systemd, as I believe there is nothing to be changed in systemd
for this fix to land.
Are the affected users fixed with the proposed kernel? Please test
proposed kernel asap! Otherwise the change will be dropped from the
kernel again on xenial =(
** No longer affects: systemd (Ubuntu)
*
** Changed in: systemd (Ubuntu Cosmic)
Status: New => Fix Committed
--
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/1762385
Title:
dell_wmi: Unknown key codes
Status in OEM Priori
** Description changed:
+ [Impact]
+
+ * Cannot hibernate & resume from a swapfile
+
+ [Test Case]
+
+ * Create or enlarge swapfile to be big enough for hibernation
+ * Attempt to hibernate and resume
+
+ [Regression Potential]
+
+ * Hibernation is not reliable technology in itself, and m
** Tags removed: verification-needed
** Tags added: verification-done
--
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/1762385
Title:
dell_wmi: Unknown key codes
Status in OEM Priority Pr
Hm I think I am confused on how this feature is supposed to work.
I've increased the swapfile size to cover my RAM and then some. However,
initramfs doesn't configure resume= nor resume_offset= thus after
hibernation, resume is not at all attempted. Should I specify
resume=/dev/vda1 or some su
Public bug reported:
As part of the makedumpfile autopkgtest, a test is done to make sure one can
dump the kernel.
The test executes
$ kdump-config status
and expects to find that it is ready to kdump, however it is not.
The check fails at:
$ cat /sys/kernel/kexec_crash_loaded
Previously it w
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
--
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/1790480
Title:
random oopses on s390 systems using NVMe
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
--
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/1790835
Title:
Ubuntu18.10 - crypto/vmx: Fix sleep-in-at
Staged for cosmic, in master-next.
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
so debug traces were added, and now they all pass (with and without
traces). le sigh.
I fear this may come back again.
--
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/1789774
Title:
linu
** Also affects: makedumpfile (Ubuntu Cosmic)
Importance: High
Assignee: Thadeu Lima de Souza Cascardo (cascardo)
Status: In Progress
** Also affects: makedumpfile (Ubuntu Bionic)
Importance: Undecided
Status: New
** Package changed: makedumpfile (Ubuntu Bionic) => kexec-
Maybe https://paste.ubuntu.com/p/QJXJyYQZCF/ has better formatting.
09/10 01:50:17 DEBUG| utils:0116| Running 'GIT_CURL_VERBOSE=1 GIT_TRACE=1
git clone --depth 1
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/cosmic linux'
09/10 01:50:17 ERROR| utils:0153| [stderr] 0
At that time there was a problem with the backend
2018-09-10 02:25:29+ [Uninitialized] Backend connection failed
Traceback (most recent call last):
Failure: twisted.internet.error.ConnectionRefusedError:
Connection was refused by other side: 111: Connection refused.
2018-
So which kernel is good and which one is bad?
you didn't mention at all which kernels are borked there has been no
mdadm updates lately.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mdadm (Ubuntu)
Status: New => Incomplete
** Changed in:
Public bug reported:
for zkey feature, check that all the required modules are in -image
package, not extras.
check that these are also shipped in udebs (probably like crypto-modules
udeb and/or disk drivers).
check that these modules are included in the initramfs as well.
** Affects: linux (Ub
** Summary changed:
- zkey - check required kernel modules
+ zkey - check and fix required kernel modules locations in debs, udebs, and
initramfs
** Summary changed:
- zkey - check and fix required kernel modules locations in debs, udebs, and
initramfs
+ check and fix zkey required kernel modu
This is not a duplicate, do not mark as duplicate. This appears to be
s390x specific zipl integration.
** This bug is no longer a duplicate of bug 1766176
initramfs-tools returns error while installing the proposed Bionic kernel
--
You received this bug notification because you are a member o
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1767172
Title:
Regression: /etc/modules checked against blackli
Looking at where the blacklists come from, it looks like kernel
autogenerates "blacklist_linux_4.15-0-15-generic.conf" files which have
a combination of OSS and watchdog blacklists.
this indeed is not very nice/easy to override.
I wonder if the "watchdog" like modules should be shipped in separat
** Description changed:
Impossible / hard to force the system to load a watchdog module because
it is blacklisted by the kernel auto-generated list of "watchdog"
modules.
/etc/modules used to "just work" before.
+ e.g. bcm2835_wdt module on arm64
+
===
-
- Before systemd-modul
Please note automatic blacklisting of watchdog modules was done to
prevent "accidental" watchdog misuse, resulting in "random" shutdowns of
production machines. See
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1432837 for more
details.
I'm not sure how to reconcile "blacklist as a precauti
** Summary changed:
- Regression: /etc/modules checked against blacklist
+ Regression: /etc/modules checked against blacklist or it's really hard to
load blacklisted watchdog modules when one really wants one
--
You received this bug notification because you are a member of Kernel
Packages, whi
The scan is forced to be done synchronously, however the ipr driver is
available and is loaded much earlier in the install process, thus it
should not significantly affect the overall install time.
One may be able to notice the difference a bit more with a fully-
automated preseed install.
** Cha
This patch set is still present, and is operating as expected in
237-3ubuntu10.2
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is s
This patch set is still present, and is operating as expected in
237-3ubuntu10.2
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is s
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
Is this critical for 18.04.1 release?
--
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/1783138
Title:
hinic interfaces aren't getting predictable names
Status in linux package in Ubuntu:
** Changed in: linux (Ubuntu)
Importance: High => Critical
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
--
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/
I still observe this bug in Cosmic with v4.17.0-5 kernel from cosmic-
proposed.
--
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/1780227
Title:
locking sockets broken due to missing AppArm
Ah, I need 2.12.1 apparmor as well, which is not in the archive yet.
--
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/1780227
Title:
locking sockets broken due to missing AppArmor socket m
** Tags added: block-proposed
--
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/1780227
Title:
locking sockets broken due to missing AppArmor socket mediation
patches
Status in apparmor
** Package changed: linux (Ubuntu) => ibm-java80 (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/1780735
Title:
[Comm] IBM JDK 8.0.5.17 integration into Ubuntu
Status in ibm-jav
Blocking launching (in useful ways) Debian testing & sid containers on
Ubuntu as well.
** Tags removed: block-proposed
--
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/1780227
Title:
lock
** No longer affects: s390-tools (Ubuntu Artful)
--
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/1777600
Title:
chzdev can't find modprobe
Status in Ubuntu on IBM z Systems:
In Progres
v4.15 kernel works for me, as proposed.
Would a similar thing be needed in the v4.17 kernel that is in cosmic-
proposed?
--
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/1780227
Title:
lo
** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
** No longer affects: ubuntu-z-systems
--
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/1784454
Title:
kernel panic on boot
For now reopening the states of this issue in launchpad as NEW and
UNDECIDED priority.
--
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/1709889
Title:
Ubuntu 17.04: Bug in cfq scheduler, I
This bug was closed in january 2018. Are you sure this is the same issue
/ right ticket? I see that you have recently marked some other bug as a
duplicate of this one. maybe you can sync that one? If not please
state what is happening on 18.04 since in january it was believed that
this issue wa
This bug report was closed more than a year ago, why is there activity
on the bug report? we see an updated to tags yet this issue should be
fully fixed released across all supported releases.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
Yes, 16.10, 17.04, 17.10 releases are end of life, but they should still
be accessible via http://old-releases.ubuntu.com/ubuntu (16.10, 17.04)
or regular archive mirrors (17.10, but it will at some point move to
old-releases).
So you could deploy 16.04 and dist-upgrade via old-releases.ubuntu.com
** Changed in: linux (Ubuntu)
Status: New => 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/1781038
Title:
KVM guest hash page table failed to allocate contiguous memory (
** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
** Changed in: ubuntu-z-systems
Status: Triaged => 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/1782085
Ti
But that new lp bug is sparse on details too can all comments be
pushed through on
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785081 ?
What exactly is happening with the bionic kernel, and what is the
expectation here?
The comments in this bug report from cking still stand imho. Un
$ git tag --contains dae55b6 Ubuntu-4.17.0-6.7
Ubuntu-4.17.0-6.7
And released.
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
$ git tag --contains fa89adba1941e4f3b213399b81732a5c12fd9131 Ubuntu-4.17.0-6.7
Ubuntu-4.17.0-6.7
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
in disco proposed with new systemd and v4.19 kernel it appears that
dmsetup / cryptsetup storage either got better or worse.
Devices take very long to activate, and sometimes remain in use during
test clean up.
This leads to udisks autopkgtest failing on ppc64le and systemd'
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Tags added: ubuntu-on-arm
--
You rece
@ Seth Forshee (sforshee)
the "crash" based bug got marked as dupicate of this bug. So surely this
bug report should not be "incomplete" status. What's the progress here?
Trivial to reproduce using libreoffice package in bionic i386 VM as seen
in autopkgtests all the time.
** Changed in: linux (
201 - 300 of 1816 matches
Mail list logo
