** Description changed:
[Impact]
* A kexec/crash kernel might get stuck and fail to boot
(for crash kernel, kdump fails to collect a crashdump)
if a PCI device is buggy/stuck/looping and triggers a
continuous flood of MSI(X) interrupts (that the kernel
does not yet know
** Description changed:
[Impact]
* A kexec/crash kernel might get stuck and fail to boot
(for crash kernel, kdump fails to collect a crashdump)
if a PCI device is buggy/stuck/looping and triggers a
continuous flood of MSI(X) interrupts (that the kernel
does not yet know
** Description changed:
+ [Impact]
+
+ * A kexec/crash kernel might get stuck and fail to boot
+(for crash kernel, kdump fails to collect a crashdump)
+if a PCI device is buggy/stuck/looping and triggers a
+continuous flood of MSI(X) interrupts (that the kernel
+does not yet know
Verification successful on xenial-proposed.
Updated verification tags.
Steps
=
Setup 1) Enable xenial-proposed and install the iproute2 package:
---
$ echo 'deb http://archive.ubuntu.com/ubuntu xenial-proposed main restricted' |
sudo tee /etc/apt/sources.list.d/xenial-proposed.list
deb htt
Hi Eric,
This is the v3 debdiff with the patches updated to apply with no offset
messages per your request.
Thanks,
Mauricio
--
Applying patch debian/patches/1008-vf_trust_dddf1b44126e.patch
patching file include/linux/if_link.h
Applying patch debian/patches/1009-vf_trust_b6d77d9ee312.patch
pa
Hi Eric,
Thanks for reviewing.
This is the debdiff v2, addressing the points you brought up (numbered patches,
bug-ubuntu dep3 tag).
cheers,
Mauricio
** Patch removed: "iproute2_xenial_vf-trust.debdiff"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1800877/+attachment/5207579/+fil
** Patch added: "iproute2_xenial_vf-trust.debdiff"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1800877/+attachment/5207579/+files/iproute2_xenial_vf-trust.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in
Public bug reported:
[Impact]
* An VM's VF cannot receive IPv6 multicast traffic
from other VMs' VFs in the same Mellanox adapter
_if_ its VF trust setting is not enabled, and on
Xenial currently iproute2 _cannot_ enable it.
* This breaks IPv6 NDP (Neighbor Discovery Protocol)
in t
Verification successful with the kernel in xenial-proposed.
Updating verification tags.
Details
===
Guest:
---
root@mfo-sf194614:~# apt-cache madison linux-image-4.4.0-139-generic
linux-image-4.4.0-139-generic | 4.4.0-139.165 |
http://archive.ubuntu.com/ubuntu/ xenial-proposed/main amd64 Pa
Verification successful on Cosmic.
---
$ apt-cache madison linux-image-4.18.0-11-generic
linux-image-4.18.0-11-generic | 4.18.0-11.12 | http://archive.ubuntu.com/ubuntu
cosmic-proposed/main amd64 Packages
$ sudo apt-get install -y linux-image-4.18.0-11-generic=4.18.0-11.12
$ sudo reboot
$ uname
Verification successful on Bionic.
---
$ apt-cache madison linux-image-4.15.0-39-generic
linux-image-4.15.0-39-generic | 4.15.0-39.42 | http://archive.ubuntu.com/ubuntu
bionic-proposed/main amd64 Packages
$ sudo apt-get install -y linux-image-4.15.0-39-generic=4.15.0-39.42
$ sudo reboot
$ uname
Synthetic Test Case
===
Create a Xenial KVM guest
---
mfo@rotom:~$ uvt-simplestreams-libvirt sync release=xenial arch=amd64
mfo@rotom:~$ uvt-kvm create --mem 4096 --cpu 2 --disk 16 mfo-sf194614
release=xenial arch=amd64
Modify the virsh XML to add a virtio-scsi controller + disk
Organic Testcase
set -x
instancename=USER-trusty
firstdevice=sdb
seconddevice=sdc
diskname=USER-disk-1
gcloud compute --project "PROJECT" ssh --zone "ZONE" "$instancename" --command
'(tar -C /var/issue/first -cf - .) | (tar -C /var/issue/second -xpf -)'
gcloud compute --project "
Patches posted to kernel-team mailing list [1].
[1] https://lists.ubuntu.com/archives/kernel-team/2018-October/096072.html
[SRU Xenial][PATCH 0/2] Improve our SAUCE for virtio-scsi reqs counter (fix
CPU soft lockup)
** Description changed:
[Impact]
- * Detaching virtio-scsi disk in Xe
Organic Testcase:
It usually reproduces the problem in the 1st or 2nd iteration.
With the fix the problem did not reproduce in 35 iterations.
** Description changed:
- (I'll add the SRU template + testing steps and post to ML shortly.)
+ [Impact]
+
+ * Detaching virtio-scsi disk in Xenial gues
Problem Analysis
The dmesg log 'crash/201809061748/dmesg.201809061748' shows the CPU soft lockup
occurs 25 seconds after the 'sdb' virtio-scsi drive is removed.
This seems to indicate the events are related (there's usually an extra 2s-3s
between an event and the report of the 2
Public bug reported:
(I'll add the SRU template + testing steps and post to ML shortly.)
A customer reported a CPU soft lockup on Trusty HWE kernel from Xenial
when detaching a virtio-scsi drive, and provided a crashdump that shows
2 things:
1) The soft locked up CPU is waiting for another CPU t
test on Bionic
--
original:
$ uname -a
Linux mfo-sf194734 4.15.0-37-generic #40-Ubuntu SMP Tue Oct 2 15:36:54 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
$ bridge fdb show
33:33:00:00:00:01 dev ens3 self permanent
01:00:5e:00:00:01 dev ens3 self permanent
33:33:f
** 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/1796748
Title:
regression in 'ip --family bridge neigh' since linux v4
** Description changed:
[Impact]
- * Netlink RTM_GETNEIGH requests for PF_BRIDGE are broken since linux
+ * Netlink RTM_GETNEIGH requests for PF_BRIDGE are broken since linux
v4.12.
- * Users, tools (e.g., iproute2), and libraries (e.g., go netlink) that use
-such request/family c
** Summary changed:
- regression in 'ip --family bridge neigh' since linux v4.12+
+ regression in 'ip --family bridge neigh' since linux v4.12
--
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
test on unstable:
-
original:
$ uname -a
Linux mfo-sf194734 4.19.0-1-generic #2 SMP Mon Oct 8 14:38:01 -03 2018
x86_64 x86_64 x86_64 GNU/Linux
$ bridge fdb show
33:33:00:00:00:01 dev ens3 self permanent
01:00:5e:00:00:01 dev ens3 self permanent
33:33:ff:e
test on Cosmic
--
original:
$ uname -a
Linux mfo-sf194734 4.18.0-9-generic #10-Ubuntu SMP Fri Oct 5 16:49:44 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
$ bridge fdb show
33:33:00:00:00:01 dev ens3 self permanent
01:00:5e:00:00:01 dev ens3 self permanent
33:33:ff
Public bug reported:
[Impact]
* Netlink RTM_GETNEIGH requests for PF_BRIDGE are broken since linux
v4.12.
* Users, tools (e.g., iproute2), and libraries (e.g., go netlink) that use
such request/family currently receive nothing back in the kernel response.
* The upstream fix resolves the
SRU Verification: all 3 stable releases successfully survive the disk
probe/partition scan of the disk image with corrupted AIX partition
table.
Updating verification tags. Thanks!
Trusty:
---
$ uname -a
Linux trusty 3.13.0-159-generic #209-Ubuntu SMP Wed Sep 12 10:01:59 UTC 2018
x86_64 x86_64
The debian-installer images in trusty-proposed work correctly; changing
verification tags to done.
I tested in the following platforms, with plain and LVM partitioning (details
in comment #10).
- amd64 bare-metal & qemu-kvm guest
- i386 qemu-kvm guest
- arm64 qemu guest
- ppc64el qemu guest
The
The secure boot packages on trusty-proposed are now correct (LP: #1708245),
and the d-i rebuild on amd64 is in progress (verified successfully on PPA).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
@slashd thanks for the pointers.
Yesterday/today I worked on understanding and providing a workaround for this,
but a more complete solution (more updates to secure-boot related packages)
is already in the works (in cyphermox's PPAs) and should be rolled out soon,
according to him.
Once that hits
This is the patch for trusty debian-installer to pick up this new xenial
hwe kernel.
It's been tested by the customer with the SF 8000 series NICs on amd64
bare metal (back when using test packages from their private PPA), so
the netboot install works on that NIC model.
I built it on PPA for the
The logs and kernel version provided in the test comments should be sufficient
to understand/confirm the problem and affected versions.
Changing the status of the bug to Confirmed.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because
Public bug reported:
[Impact]
* Users with disks/LUNs used for AIX operating system installations
previously, which possibly undergone overwrites/corruption on the
partition table, might hit kernel failures during partition scan
of such disk/LUN, and possibly hang the system (seen with
Test on Trusty
Before:
$ uname -a
Linux bionic 3.13.0-155-generic #205-Ubuntu SMP Fri Aug 10 15:53:26 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
$ echo 9 | sudo tee /proc/sys/kernel/printk
9
$ sudo losetup --find --show --partscan rlv_grkgld.1mb
[
Test on Cosmic:
Before:
$ uname -a
Linux bionic 4.17.0-7-generic #8-Ubuntu SMP Fri Aug 3 15:55:36 UTC 2018 x86_64
x86_64 x86_64 GNU/Linux
$ echo 9 | sudo tee /proc/sys/kernel/printk
9
$ sudo losetup --find --show --partscan rlv_grkgld.1mb
[ 37.274451] partition (null) (20 pp's found) is not
Test on Bionic
Before:
$ uname -a
Linux bionic 4.15.0-32-generic #35-Ubuntu SMP Fri Aug 10 17:58:07 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
$ echo 9 | sudo tee /proc/sys/kernel/printk
9
$ sudo losetup --find --show --partscan rlv_grkgld.1mb
[ 48.192538] partition (null) (5 pp's found) is not
Test on Xenial
Before:
Last login: Wed Aug 15 19:29:38 2018 from 192.168.122.1
$ uname -a
Linux bionic 4.4.0-133-generic #159-Ubuntu SMP Fri Aug 10 07:31:43 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
$ echo 9 | sudo tee /proc/sys/kernel/printk
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
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/1783152
Title:
Enable basic support for Solarflare 8000
I should read the bot comments more attentively.
Setting bug status to Confirmed.
** 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
Reverting linux's status from Incomplete to New, as the problem has been
already diagnosed and fixes submitted.
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
ernal default)
Sep 20 20:07:36 | sdai: checker timeout = 30 ms (internal default)
Sep 20 20:07:36 | io_setup failed
Sep 20 20:07:36 | sdai: checker init failed
== Comment: #7 - Mauricio Faria De Oliveira -
2016-09-27 18:32:57 ==
The function is failing at the io_setup() system call.
@
Sep 20 20:07:36 | sdai: get_state
Sep 20 20:07:36 | sdai: path_checker = directio (internal default)
Sep 20 20:07:36 | sdai: checker timeout = 30 ms (internal default)
Sep 20 20:07:36 | io_setup failed
Sep 20 20:07:36 | sdai: checker init failed
== Comment: #7 - Mauricio Faria De Oliveir
Patch set v2 submitted [1].
[1] https://lists.ubuntu.com/archives/kernel-
team/2017-October/087858.html
--
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/1721070
Title:
powerpc/64s: Add wo
** Summary changed:
- powerpc/64s: Add workaround for P9 vector CI load issuenext
+ powerpc/64s: Add workaround for P9 vector CI load issue
--
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/1
Joseph,
Again, thanks.
I had a few suggestions on the submitted backports, and observed a subtle
problem in one of them.
If you prefer, I can submit the ones I have here, if that saves you some cycles.
cheers,
Mauricio
--
You received this bug notification because you are a member of Kernel
P
Hi @jsalisbury
> I also built a 4.10 based test kernel(16.04.3). [snip]
Thanks.
> Can you test this kernel and see if it resolves this bug?
Yes, it does.
I have verified both the patched one (4.10.0-35.39~lp1721070), which passes,
and its original version (4.10.0-35.39), which fails; so the pa
Bug description updated w/ SRU template.
Patch submitted to kernel-team mailing list.
[SRU Z/X][PATCH] scsi: ipr: do not set DID_PASSTHROUGH on CHECK CONDITION
https://lists.ubuntu.com/archives/kernel-team/2017-August/086518.html
Requested for
- Zesty/17.04 (target 16.04.3 HWE kernel / v4.10-ba
le
- port0 --> Seagate
#1-B I/O module
-
- Ubuntu 16.04.2:
- ===
-
- - Running with new kernel Ubuntu 4.8.0-520-generic #550~16.04.1+bz154734
- from Mauricio Faria De Oliveira.
Problem Description:
- In this Bri
16.04.2:
===
- Running with new kernel Ubuntu 4.8.0-520-generic #550~16.04.1+bz154734
from Mauricio Faria De Oliveira.
Problem Description:
In this Briggs system, I'm running with new Ubuntu 4.8.0-520-generic
#550~16.04.1+bz154734 that has fix f
O module
Ubuntu 16.04.2:
===
- Running with new kernel Ubuntu 4.8.0-520-generic #550~16.04.1+bz154734
from Mauricio Faria De Oliveira.
Problem Description:
In this Briggs system, I'm running with new Ubuntu 4.8.0-520-generic
#550~16.04.1+bz154734 t
Thanks, @cyphermox and @smb.
--
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/initramfs
Status in hw-detect package in U
*** This bug is a duplicate of bug 1670490 ***
https://bugs.launchpad.net/bugs/1670490
Thanks for the report/request for Power.
This commit has been requested on LP #1670490.
Marking as a duplicate.
cheers,
** This bug has been marked a duplicate of bug 1670490
FC Adapter (LPe32000-base
The patch in the kernel-team mailing list:
https://lists.ubuntu.com/archives/kernel-team/2017-March/082822.html
--
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/1669153
Title:
Add Use-Afte
> If, due to the nature of the issue you have encountered, you are unable
> to run this command, please add a comment stating that fact and change
> the bug status to 'Confirmed'.
Right.
This is just a request for adding the patch which fixes a potential problem in
an applied patch.
Changing bug
Posted patch to kernel-t...@lists.ubuntu.com .
$ git send-email --to kernel-t...@lists.ubuntu.com use-after-free.patch
use-after-free.patch
<...>
From: Mauricio Faria de Oliveira
To: kernel-t...@lists.ubuntu.com
Subject: [SRU][Xenial][Yakkety] 8250_pci: Fix potential use-after-free in
Public bug reported:
On LP1646857, patch [1] was applied (Zesty, Yakkety, Xenial).
However, this patch [2] fixes a use-after-free problem on it, and it's not yet
applied (Yakkety, Xenial), only applied on Zesty so far.
Please apply patch [2] for Yakkety and Xenial HWE.
Thank you.
[1]
http://g
irmware is FW840.20 (SC840_100) (t) FW840.10 (SC840_079)
(p) FW840.20 (SC840_100) (b)
Version of PFW is 14492016042881CF0681
== Comment: #4 - Mauricio Faria De Oliveira -
2016-10-13 10:16:40 ==
Hi Canonical,
This patch series that resolves this problem made linux mainline in the 4.9
me
Thanks for marking this bug as verified.
It looks good -- I've checked the patch is there, and change is trivial,
but couldn't get a response from the test team in time. Sorry for that.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
temp/ausratsrv5Node01/server1/TeamEAR/cqweb.war/dmesg1.txt
on 2016-03-21 14:47:26
== Comment: #2 - Application Cdeadmin -
2016-03-21 15:55:16 ==
== Comment: #12 - Mauricio Faria De Oliveira -
2016-04-04 14:09:48 ==
Info from Mike on ST.
Assigned the adapter in the drawer to the LPAR, it
bug bridge and it merged 2 bugs.)
This is about including these 2 upstream commits for the lpfc driver:
Mauricio Faria De Oliveira 2016-05-11 08:37:31 BRT
Hi Canonical,
The 2 upstream commits that resolve this problem are:
0290217ad830f2813bb9ed5f51af686c0c591f28 lpfc: Correct loss
commits for the lpfc driver:
Mauricio Faria De Oliveira 2016-05-11 08:37:31 BRT
Hi Canonical,
The 2 upstream commits that resolve this problem are:
0290217ad830f2813bb9ed5f51af686c0c591f28 lpfc: Correct loss of target
discovery after cable swap.
be6bb94100dc6803a530e20aad05360e626
esg Log: dmesg1.txt
mlfield (mlfi...@us.ibm.com) added native attachment
/opt/IBM/WebSphere/AppServer/profiles/cqweb/temp/ausratsrv5Node01/server1/TeamEAR/cqweb.war/dmesg1.txt
on 2016-03-21 14:47:26
== Comment: #2 - Application Cdeadmin -
2016-03-21 15:55:16 ==
== Comment: #12 - Maurici
*** This bug is a duplicate of bug 1572624 ***
https://bugs.launchpad.net/bugs/1572624
Hi,
Apologies for the confusion w/ the bug bridge; it has been reported.
LP 1580557 and LP 1580560 are the same bug (previously marked as a dup,
but removed later).
It seems the invalidation of this one d
uot; of LP #1580557 comment #1 (yes, a comment).
(It seems there was a problem in the bug bridge and it merged 2 bugs.)
This is about including these 2 upstream commits for the lpfc driver:
Mauricio Faria De Oliveira 2016-05-11 08:37:31 BRT
Hi Canonical,
The 2 upstream commits that re
Public bug reported:
Hi Canonical,
This a "duplicate" of LP #1580557 comment #1 (yes, a comment).
(It seems there was a problem in the bug bridge and it merged 2 bugs.)
This is about including these 2 upstream commits for the lpfc driver:
Mauricio Faria De Oliveira 2016-05-11 08:37
** 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/1497966
Title:
ISST-KVM:R3-0:Firestone:Ubuntu14043:beng2:Cannot reach ne
Tim,
This looks like the same deal w/ the other bug today; closed as unreproducible,
which was not reflected here.
I'll pass this on to the bug bridge team.
This has been posted as an internal (hm.) comment:
> This issue is not getting re-created with recent ubuntu build.
** Changed in: linux
Hi Tim,
Sorry, this has been closed as unreproducible on the LTC side, and not
reflected here.
Marking this bug as Invalid.
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
itle:
scsi-firmware udeb does not include ql2500_fw.bin
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Trusty:
Fix Committed
Status in linux-firmware source package in Xenial:
Fix Released
Bug description:
== Comment: #0 - Mauricio Faria
Hey,
Marking this bug as Invalid.
It has come to my attention that PowerVM support requires a HWE kernel (it's
not supported w/ the 3.13 series), which includes the LE commit of interest.
Apologies for the noise.
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received thi
For documentation purposes, that commit eventually made mainline
(a30c2a3bf8571c6748dd16edc10b32d45ed71a72).
Note the issue could not be reproduced w/ 14.04.3 anyway.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
** 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/1429959
Title:
Auto Error Recovery is failing after error injected f
There's been difficulty in reproducing this problem. Closing as invalid
for now. Thanks!
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
Verification done, the kernel in -proposed solves the problem.
Tag updated.
Thanks!
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
@arges
I'll check if qlogic may review/reply to continue some activity.
I'm not experienced w/ the review/commit process for this subsystem, so if it's
someone else who should reply, please let me know.
Thanks for your attention on this one.
--
You received this bug notification because you are
Public bug reported:
Hi Canonical,
Please apply this kernel commit for Trusty SRU / 14.04.x (already in 14.10,
15.04, and later):
- 27f344eb15dd0da80ebec80c7245e8c85043f841 lpfc: Add iotag memory barrier
Tested on top of linux 3.13.0-55.94 (applies cleanly; cherrypick)
It fixes the this issue
The kernel packages in -proposed solves the problem.
The ibmvfc module is present on scsi-modules for both trusty and utopic.
Trusty:
3.13.0-49.81 proposed (main)
$ wget -q
http://ports.ubuntu.com/ubuntu-ports/pool/main/l/linux/scsi-modules-3.13.0-49-generic-di_3.13.0-49.81_p
This has been committed in Trusty and Utopic.
Thanks @apw and @arges!
@henry-szablicki
It should be released with the next kernel package.
It will later hit the netboot installer (watch this changelog [1]), and
eventually the next install media (14.04.3).
References:
[1] https://launchpad.net/
Sent request to kernel-team mailing list (SRU for Trusty/Utopic).
--
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/1416001
Title:
ISST-LTE: ubuntu15.04 installer is missing ibmvfc driver
Hi, @arges @apw
Can this be pushed to Trusty and Utopic as well? (per comment #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/1416001
Title:
ISST-LTE: ubuntu15.04 installer is missi
Heheh, indeed.
By the way, I reported that issue here a few days ago.
Hopefully the bug mirroring team will get that fixed.
--
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/1400411
Title:
Adding tag 'verification-done-utopic' as requested in comment 13.
Verification done internally, but the bug mirroring didn't fully did the tags.
** Tags added: verification-done-utopic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
@apw thanks, Andy.
--
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/1413646
Title:
15.04: incomplete debug symbols package - please disable
CONFIG_DEBUG_INFO_SPLIT or package the .dwo fi
*** This bug is a duplicate of bug 1413646 ***
https://bugs.launchpad.net/bugs/1413646
** Changed in: crash (Ubuntu)
Status: New => Confirmed
** This bug has been marked a duplicate of bug 1413646
15.04: incomplete debug symbols package - please disable
CONFIG_DEBUG_INFO_SPLIT or p
Public bug reported:
The kernel option CONFIG_DEBUG_INFO_SPLIT has been enabled in vivid
(commit bb5f2d940954fb389f16a0f7ad05b5a53a7e5227).
It moves debuginfo to .dwo files, using gcc -split-dwarf.
The kernel packaging received no updates to include the .dwo files, AFAICT.
This results in gdb
@arges
Ok! Thanks for letting us know.
--
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/1352056
Title:
linux: kdump on Ubuntu 14.04 is not generating a dump.
Status in “linux” package in
Hi Chris,
Thanks for fixing this out.
One question:
> [Test Case]
> Taken from:
> https://wiki.ubuntu.com/Kernel/CrashdumpRecipe
> [...]
> 2) increase crashdump size:
> sudo vim /etc/default/grub.d/kexec-tools.cfg
> set crashkernel=1024M
Is there any possibility to make this value something 'pe
Hi Chris & Laurent,
Aren't these other 2 ppc64el-specific patches required too?
- kexec/ppc64: Handle reserved memory ranges exported by OPAL firmware.
- kexec/ppc64: Fix up ELF header and dt for PowerNV platform.
I'm not knowledgeable in kexec, but I see those upstream post-2.0.6 as
well.
--
Thanks, Chris!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1324544
Title:
makedumpfile: kdump-config load fails with vmlinux kernel (vs.
vmlinuz)
Status in “makedumpfile” pa
Marking as confirmed since this is hit / mentioned as part of LP
#1352056 and LP #1350443
** Changed in: makedumpfile (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https:/
** Patch added: "makedumpfile-vmlinux-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1324544/+attachment/4203116/+files/makedumpfile-vmlinux-trusty.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ma
** Patch added: "makedumpfile-vmlinux-utopic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1324544/+attachment/4203115/+files/makedumpfile-vmlinux-utopic.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ma
Attaching debdiffs for Utopic and Trusty.
The patch fixes this issue:
$ sudo kdump-config load
Cannot open `/boot/vmlinuz-3.16.0-14-generic': No such file or directory
* failed to load kdump kernel
Test OK on Utopic:
$ sudo kdump-config load
Modified cmd
AFAICT from the long description,
this bug needs the patches from these 2 open bugs:
LP #1324544
LP #1349994
Both in 'New' state, so meaning those patches haven't been
committed/released in packages.
--
You received this bug notification because you are a member of Kernel
Packages, which is su
> Except that OPAL/petitboot cannot boot a zImage ... FAIL !~
Epic fail.
Really sorry about that (and the effort involved).
Apologies, everyone.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
Thanks for all the effort involved. :)
--
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/1358920
Title:
Switch kernel to vmlinuz (from vmlinux) on ppc64el
Status in “debian-installer” pack
Thanks.
For the record, I'll file bugs upstream for the userpace tools failing
(discussed on irc).
--
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/1358920
Title:
Swith kernel to vmlinuz
** Patch added: "ppc64el-vmlinuz-d-i.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358920/+attachment/4181881/+files/ppc64el-vmlinuz-d-i.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
Public bug reported:
Hi,
May we discuss/implement switching the kernel image type/filename on
ppc64el from vmlinu*x* to vmlinu*z* ?
Problem:
In the current situation, some issues occur because of 1) or 2):
1) the presence of /boot/vmlinu*x* w/ no debug symbols (vmlinux
conventi
The packages in proposed fix it.
Thanks.
$ ARCH=powerpc make -C /usr/src/linux-headers-`uname -r` M=`pwd` clean modules
2>&1 | fgrep Wsign-compare
include/linux/bitops.h:77:3641: warning: signed and unsigned type in
conditional expression [-Wsign-compare]
include/linux/cpumask.h:603:26: warning:
For the record:
$ uname -r
3.13.0-32-generic
--
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/1321791
Title:
Warnings when building out-of-tree module with -Wsign-compare
Status in “linu
... guy is blazing fast; commits in master-next.
--
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/1321791
Title:
Warnings when building out-of-tree module with -Wsign-compare
Status in “l
601 - 700 of 718 matches
Mail list logo
