@rtg
Please check if
http://git.kernel.org/cgit/linux/kernel/git/s390/linux.git/log/?h
=kernel-messages suitable to pull the kernel-messages from. Please note,
it may require repulls with later milestones (e.g. rc4 or later).
** Changed in: linux (Ubuntu)
Status: Fix Committed => Confirmed
Installed lpar onto 154d dasd drive, using LVM automatic partitioning recipe.
After installation and reipl, I did the following:
$ sudo chzdev -e 254d
ECKD DASD 0.0.254d configured
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.4.0-60-generic
W: mdadm: /etc/mdadm/mdadm
On 18 January 2017 at 15:39, bugproxy wrote:
> --- Comment From ma...@de.ibm.com 2017-01-18 10:36 EDT---
> (In reply to comment #21)
>> Installed lpar onto 154d dasd drive, using LVM automatic partitioning recipe.
>> After installation and reipl, I did the following:
>
>> $ sudo update-ini
On 30 January 2017 at 01:06, PetrolPC wrote:
> I'm experiencing this bug when attempting to install Linux Mint 17.3 64 bit,
> Ubuntu 14.04 LTS 64 bit and Debian 8.7.1 64 bit. The issue does not arise
> when installing the 32 bit versions.
> My Macbook specs can be found here:
> http://www.everym
Public bug reported:
CONFIG_NUMA is not set in the 4.8 kernels (16.10 & linux-edge) when it
should have been, on s390x.
It is set in 4.4 (xenial) and 4.9 (zesty).
This is regression of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1557690
https://bugs.launchpad.net/ubuntu/+source/linux/+
** Tags added: regression-release regression-update
--
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/1661620
Title:
CONFIG_NUMA is missing from the 4.8 kernels on s390x
Status in linux pa
Using strace and friends is a bit too low level to debug execution of
bash scripts =)
You can try:
$ sudo bash -x update-initramfs -u -v
And attaching log of that. And you can use also add "set -x" in the
hooks that are called (and/or are hung); and attaching a log of that to
see where/when it i
Please attach sosreport from the system.
--
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/1662187
Title:
apt-get upgrade hung when it comes to update initramfs
Status in Ubuntu on IBM z S
This is getting more interesting.
One can add
"set -x" near the top of /usr/share/initramfs-tools/hooks/mdadm
but based on your previous messages it's probably going to hang at
mkconf.
E.g. I am suspecting below will also hung
$ sudo bash -x /usr/share/mdadm/mkconf
Which ultimately calls into:
If mdadm is hung examining partitions, all I can recommend is to reboot
and check if problem goes away.
--
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/1662187
Title:
apt-get upgrade hung
Can you attach, as an attachment, the syslog?
--
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/1662187
Title:
apt-get upgrade hung when it comes to update initramfs
Status in Ubuntu on IB
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: ubuntu-z-systems
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/1662187
Title:
a
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: linux (Ubuntu)
Milestone: None => ubuntu-17.02
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
$ apt-cache search ^linux-generic
linux-generic - Complete Generic Linux kernel and headers
linux-generic-hwe-16.04 - Complete Generic Linux kernel and headers
linux-generic-hwe-16.04-edge - Complete Generic Linux kernel and headers
How about
$ apt-cache search ^linux-generic
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** 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://bug
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
** 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.
http
** Information type changed from Private to Public
** Changed in: linux (Ubuntu)
Status: New => Fix Released
--
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/1655909
Title:
[17.04
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
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/1644537
Title:
[17.04 FEAT] DASD channel-path aware error recovery
** Changed in: linux (Ubuntu)
Status: In Progress => Incomplete
** Changed in: ubuntu-z-systems
Status: In Progress => 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/bu
If resume completed - e.g. there is some evidence that it was not a cold
boot, but actually previous system session did come back up somewhat -
systemd has probably finished its job.
Graphical glitches are possibly kernel drivers and/or udev/quirk
integration.
Assigning to linux for further inves
Frank could you please reverse proxy this bug back to IBM engineering,
to make kernel report "Unknown" line speeds for qeth devices under Z/VM?
For reference, there are also confusion/requests w.r.t. this on
linux-s390 maryst mailing list.
Regards,
Dimitri.
** Package changed: linux-hwe (Ubuntu
Hi,
Is the system fully updated since installing, or only selectively? I ask
this, because i would expect the interface name to have been renamed and
migrated to encf5f0 -> shorter prefix, and leading zeros stripped as of
systemd 228-4ubuntu2. Installation was done with systemd just before
that o
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** 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/1552788
Title:
The following config changes will be fixed soon:
CONFIG_NUMA
CONFIG_REGMAP
CONFIG_NET_VENDOR_EMULEX
CONFIG_BE2NET
CONFIG_BE2NET_VXLAN
CONFIG_NET_VENDOR_SYNOPSYS
CONFIG_NVMEM
The requests below two keys are currently out of scope, with the generic kernel
config policy for Ubuntu:
CONFIG_PREEMPT_NO
Public bug reported:
[s390x] /dev/hwrng present, yet not usable
# cat /dev/hwrng
cat: /dev/hwrng: No such device
# ls -latr /dev/hwrng
crw--- 1 root root 10, 183 Mar 8 10:28 /dev/hwrng
# modprobe ap
modprobe: ERROR: could not insert 'ap': No such device
# lszcrypt -VV
lszcrypt: error -
@brad-figg
How can this bug report be missing log files, if it was filed with
ubuntu-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/1554498
Title:
[s390x] /dev/hwrng present, yet n
@Gary Gaydos
Please do not assign skipper screener bugs to packages, instead please
let canonical / skeeper screeners to assign them to the correct
packages.
** Package changed: kexec-tools (Ubuntu) => zipl-installer (Ubuntu)
** Also affects: s390-tools (Ubuntu)
Importance: Undecided
S
I presume you mean that "parameters =" in /etc/zipl.conf should have
crashkernel=auto set.
Note that on ubuntu, we do not enable crashkernel by default, but we do
enable it upon installing kdump packages.
On the other hand, unlike other architectures we do not actually re-
generate /etc/zipl.conf
** Also affects: linux-meta (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-meta (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchp
** Changed in: makedumpfile (Ubuntu)
Assignee: (unassigned) => Louis Bouchard (louis-bouchard)
--
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/1555159
Title:
Crashkernel parameter is
@tim
Sure, however that makes zero sense here, as this is not a KVM virtual
machine. It is a z/VM - which for linux purposes has little differences
from an LPAR.
I can load and unload virtio-rng module.
With or without virtio-rng module there is still /dev/hwrng, and still unusable.
--
You rece
** Tags added: s390x
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1555244
Title:
crash fails to load with 4.4+ kernels
Status in crash package in Ubuntu:
New
Bug description:
Whe
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
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/1555344
Title:
Public bug reported:
$ dmesg | grep '\.509'
[ 11.950518] Loading compiled-in X.509 certificates
[ 11.951343] Problem loading in-kernel X.509 certificate (-74)
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-12-generic 4.4.0-12.28
ProcVersionSignature: Ubuntu 4.4.0-12.2
** Changed in: linux-lts-utopic (Ubuntu)
Status: New => Invalid
** Changed in: linux-lts-utopic (Ubuntu Trusty)
Status: Fix Released => Invalid
** Changed in: linux (Ubuntu Wily)
Status: Fix Released => Invalid
** Changed in: linux (Ubuntu Vivid)
Status: Fix Released
I do not believe this is a regression.
--
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/1557250
Title:
linux fails to load x.509 built-in certificate
Status in linux package in Ubuntu:
@TIM this has nothing to do with PPC. this is s390x request. STFLE
sounds like a little-endian symbol name whereas s390x is big-endian,
no?
--
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
** Changed in: s390-tools (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: systemd (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: linux (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Kernel
Packages, whic
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/xenial/commit/?h=master-
next&id=62d95836921d417373ab0b7674f9d8b5f929857b
--
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/
The permissions on the device are correct, as far as kernel is
concerned. s390-tools documentation suggests that in practice it should
be 0444. Thus s390-tools should ship such a udev rule, or such udev rule
should be contributed upstream to systemd udev component.
** Also affects: s390-tools (Ubu
@Tim,
Imho 9P can/should be =y on all arches, cause then one can use 9P as
root/boot device. And it opens the interesting posibility of e.g.
"booting" an lxd container in kvm, and the like.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
New d-i based installations will receive crash-kernel parameter by
default, via zipl-installer changes.
** Changed in: zipl-installer (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: makedumpfile (Ubuntu)
S
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Wishlist
--
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/1558624
Title:
s390/pci: backport upstream commits since v4.4
St
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Wishlist
--
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/1557690
Title:
s390/kconfig: CONFIG_NUMA without CONFIG_NUMA_EMU
s390-tools package will upgrade existing installs to gain the
crashkernel parameter, as a one time upgrade only. E.g. subsequently a
system administrator is free to add/remove/modify the parameter to their
liking.
** Changed in: s390-tools (Ubuntu)
Status: Confirmed => Fix Committed
--
Yo
As far as I can see: Fedora, RHEL, z/KVM, Debian, and Ubuntu ship
SCAN_ASYNC on s390x. Thank you for your comments.
--
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/1557692
Title:
s390/kco
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Wishlist
--
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/1557994
Title:
s390/kconfig: setting for CONFIG...9P
Status
** Package changed: 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/1559194
Title:
Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device
driver
# ./debian/tests/kernel-smoke-test
kernel smoke test, create and destroy pool, 2x2 mirror: PASSED
kernel smoke test, create and destroy pool, 4x1 mirror: PASSED
kernel smoke test, create and destroy pool, nested raidz3: PASSED
kernel smoke test, create and destroy pool, raidz1: PASSED
kernel smoke
** Changed in: linux (Ubuntu)
Status: New => Won't Fix
** Changed in: linux (Ubuntu)
Importance: Undecided => Wishlist
--
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/1557692
Tit
https://github.com/zfsonlinux/spl/pull/537
--
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/1519814
Title:
spl/zfs fails to build on s390x
Status in linux package in Ubuntu:
In Progress
mplete
** Changed in: s390-tools (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Wishlist
--
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/1558625
Title:
s390/pci: enforce fmb page boundary rule
Status i
** Patch added: "0001-UBUNTU-Config-s390x-patch-spl-and-re-enable-zfs.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519814/+attachment/4601526/+files/0001-UBUNTU-Config-s390x-patch-spl-and-re-enable-zfs.patch
** Changed in: linux (Ubuntu Xenial)
Status: Triaged => In Prog
For example, KVM for IBM z Systems 1.1.0 (Z) is also affected, and the
device has following permissions:
# ls -latr /dev/prandom
crw--- 1 root root 10, 57 Mar 17 13:41 /dev/prandom
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
@christian rund
no =) linux-lts-xenial is not the right package. that is a backport
kernel to trusty and there is no s390x support in trusty.
** Package changed: linux-lts-xenial (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, wh
Sorry for the noise, adjusted wrong bug tab =)
--
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/1557692
Title:
s390/kconfig: do not set CONFIG_SCSI_SCAN_ASYNC
Status in linux package in U
Cool, reopening the bug task for linux package then, and setting it to
incomplete.
Once there is an accepted patch for this, do drop a line here to ping
the kernel team to get this included.
Regards,
Dimitri.
** Changed in: linux (Ubuntu)
Status: Invalid => Incomplete
** Changed in: s39
This is s390x architecture specific. s390x architecture is only present
in Xenial and nowhere else. And only in generic flavour. No Security
update is needed in any other kernel flavour, nor in any other release
series.
** No longer affects: linux (Ubuntu Precise)
** No longer affects: linux (Ubu
** 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/1558275
Title:
wrong/missing permissions for device file /dev/prandom (p
I do not want to increase it beyond 128MB by default, as this amount of
memory is reserved by default on all installations big or small. And
there will always be newer kernel (that reserves more memory) or more
devices that require higher values. Adjusting kernel args in
/etc/zipl.conf is well-know
128MB is just a sensible default enabled by default everywhere, if in
your case you need more do adjust it accordingly in /etc/zipl.conf and
execute `sudo zipl` and then reboot.
There is no dynamic sizing / computation of zipl.conf and/or crashkernel
paramemter on Ubuntu, and on all architectures
"Ok, if we go with the 128M default our current assumption is that on
all LPARs kdump for Ubuntu will fail." -> well, that doesn't sound good
either, cause then essentially we take away 128M of RAM away without
actually providing anything to the LPAR installations =(
--
You received this bug noti
On 1 April 2016 at 12:22, Louis Bouchard wrote:
> If there is a way to determine if we're on a zVM or Lpar, I could adapt
> kdump-config to add the appropriate crashkernel=value pair in
> /etc/zipl.conf and re-run zipl upon installation of kdump-tools, which
> is required in order to capture a dum
Setting to incomplete for now, pending more information.
** 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/1559194
Title:
Bad
Please note, that given that this is for s390x architecture only, it is
only needed in xenial kernel, and is not required for SRU into any
previous kernels.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
Public bug reported:
apw symlinks bug
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-6-generic 4.4.0-6.21
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USE
I'm not sure what needs doing here, unassigning myself.
** Changed in: edk2 (Ubuntu)
Assignee: Dimitri John Ledkov (xnox) => Steve Langasek (vorlon)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubunt
** Changed in: dmidecode (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: dmidecode (Ubuntu Precise)
Assignee: Dimitri John Ledkov (xnox) => (unassigned)
** Changed in: dmidecode (Ubuntu Trusty)
Assignee: Dimitri John Ledkov (xnox) => (unassigned)
** C
s390x is only available in xenial (and later releases). Please do not
open bugs for irrelevant series.
** Changed in: linux (Ubuntu Wily)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubunt
Discussing with s390x upstream developers, we should check if zpl/zfs
code supports any other 64bit big-endian platforms (e.g. SPARC64) and
then check if s390x support can be trivially enabled similarly to e.g.
sparc64 port.
--
You received this bug notification because you are a member of Kernel
New kernel upload has entered xenial-proposed, and is being tested
before migrating to release component
For full changelog see:
https://launchpad.net/ubuntu/+source/linux/4.4.0-9.24
Kernel release process workflow bug for this kernel is at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1
New kernel upload has entered xenial-proposed, and is being tested
before migrating to release component
For full changelog see:
https://launchpad.net/ubuntu/+source/linux/4.4.0-9.24
Kernel release process workflow bug for this kernel is at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1
** Tags added: s390x
--
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/1531327
Title:
Various failures of kernel_security suite on Xenial kernel on s390x
arch
Status in QA Regression Tes
Public bug reported:
On s390x,
./lib/modules/4.4.0-10-generic/kernel/drivers/s390/scsi/zfcp.ko
should be available in scsi-modules udeb, eg.:
scsi-modules-4.4.0-10-generic-di_4.4.0-10.25_s390x.udeb
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Tim Gardner (timg-tpi)
Priliminary patches for this posted at http://people.canonical.com/~xnox
/live-installer/
** Description changed:
should be able to do live-installer installs from mirrors, and cdrom
pool over the network
+
+ with live-installer patches this works.
+
+ however on s390x currently this result
.
-- Dimitri John Ledkov Wed, 16 Dec 2015 18:10:55
+
** Changed in: live-installer (Ubuntu Xenial)
Status: New => Fix Released
--
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
link_in_boot is required as yes for s390x, and currently it seems like
cloud-image generation is broken for s390x.
Manually, upgrading from an older cloudimage (3.3 -6- version) I had to
do a small dpkg remove surgery to drop all the packages, and reinstall
new metapackages.
What I found interest
Hm, i don't think update-initramfs does the right thing:
linux-image-*)
if [ -z "$INITRAMFS_TOOLS_KERNEL_HOOK" ]; then
# kernel maintainer script called us directly; ignore
# it and let the hook script handle it instead
echo "update-initramfs
Unpacking linux-generic (4.3.0.7.8) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up linux-image-4.3.0-7-generic (4.3.0-7.18) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
/bin/cp: cannot stat '/boot/initrd.img-4.3.0-7-generic': No such file or
direc
** Patch added: "linux-postinst.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536810/+attachment/4560470/+files/linux-postinst.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
Looking at the postinst script, it calls update-initramfs -u and expects
it to do somethin, i.e. create the initramfs.
However, it can choose to not do so, and deffer the update. And thus not
create an initramfs. However, when we are upgrading to a new kernel
image, we expect to generate an initra
however, as per irc, that will kill the benefit of deffered initramfs
generation.
Identified to cherrypick
https://anonscm.debian.org/cgit/kernel/linux.git/commit/?id=373d086904305699561b1eb505c33b010c24de9b
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738707
** Bug watch added: Debian Bug
should not be called when -$flavor-extra is removed, cause the
next action after that would be to remove just generated initramfs.
related to http://irclogs.ubuntu.com/2015/06/19/%23ubuntu-
devel.html#t18:04
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Dimitri John Ledkov
** Package changed: linux (Ubuntu) => 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/1539642
Title:
Integrate zfcp HBA API library 2.1.1
Status in Ubuntu:
New
Bug description:
** Changed in: makedumpfile (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: makedumpfile (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Dimitri John
Ledkov (xnox)
--
You received this bug notification because you are a member of Kernel
Packages,
For LPAR -> it's a valid test to verity max speed and actual speeds
For z/VM -> the cards are virtualised on the host, thus any test of max &
actual speeds is bogus
For z/KVM -> the cards are virtualised on the host, thus any test of max &
actual speeds is bogus
Comparing z/VM and z/KVM with othe
@bugproxy
Kernel with this bug fix is available for testing from xenial-proposed
pocket. See https://wiki.ubuntu.com/Testing/EnableProposed for more
details how to enable and install packages from -proposed. Note
-proposed is not to be used for day-to-day production systems, and only
for selective
Public bug reported:
cryptop/arc4.ko appears to be in both nic-moudles and crypto-modules.
Unpacking nic-modules-4.4.0-22-generic-di (4.4.0-22.40) ...
dpkg: warning: overriding problem because --force enabled:
dpkg: warning: trying to overwrite
'/lib/modules/4.4.0-22-generic/kernel/crypto/arc4.k
** Changed in: ubuntu-z-systems
Status: Incomplete => 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/1544978
Title:
PCI Call Traces hw csum failure in dmesg with 4
Public bug reported:
So to do virtual machine / cloudy stuff things in the kernel config, are
not how one would expect them to be. Whilst investigating that I've went
ahead to compare all our kernel configs.
amd64/config.common.amd64:CONFIG_VIRTIO_BLK=y
amd64/config.common.amd64:CONFIG_VIRTIO_NET
I can confirm the proposed image works great for VIRTIO_BLK/_NET stuff.
Thank you.
--
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/1532886
Title:
s390x kernels are inconsistent for cloud
Public bug reported:
If VIRTIO_BLK and VIRTIO_NET become =m, instead of current =y the
following should happen:
VIRTIO_NET should be in the nic-modules udeb, and seeded into the d-i
builds.
VIRTIO_BLK can stay in block-modules-udeb, and in general is not needed
in the d-i build, as it can be fet
xnox: Why did you add block-modules to generic/s390x.cfg?
xnox: "Add block-modules (depends on virtio-modules) for s390x"
seems pointless with the kernel change to make those builtin. I think I'll
revert that commit.
xnox: Or was there some other reason?
* infinity shrugs and leaves it there
Public bug reported:
Hello,
to use qemu one needs vm.allocate_pgste = 1, on kernels that support that
setting e.g. s390x.
I'm now setting it with a sysctl.d snippet in procps package, however I was
wondering if it could be set by default.
Or not.
** Affects: linux (Ubuntu)
Importance: W
Public bug reported:
Symlinks are not managed correctly.
Last installed and configured kernel, prior to purging -5- was -6-, yet
symlinks were not updated to -6- when that happened.
root@devac03:~# apt-get remove --purge linux-headers-4.3.0-5
linux-headers-4.3.0-5-generic linux-image-4.3.0-5-ge
http://paste.ubuntu.com/14495976/
--
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/1534162
Title:
symlinks are not updated on s390x
Status in linux package in Ubuntu:
New
Bug descripti
Ok, here is a better scenario
I have purged -6, and installed -5.
Then i have installed -6 and expected for symlinks to change from -5 ->
-6, however they did not.
http://paste.ubuntu.com/14496011/
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
** Tags added: s390x
--
You
i am an idiot.
symlinks are updated in /
yet my zipl is using weird symlinks in /boot/
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Summary changed:
- symlinks are not updated on s390x
+ symlinks managed by kernel postinst are different from zipl-installer and
livefs-rootfs
Aha
# cat /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
link_in_boot = yes
--
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
601 - 700 of 1816 matches
Mail list logo
