So, this is a multipath disk, whose parent is the nvme-subsys0 device,
not nvme0 device. The latter is a PCI device, but the former is a
virtual one. Some code to add slaves/holders relationships was added,
but reverted. I will investigate any further discussion about this
upstream, or look into
I managed to download the lp1778844_sys.tar.gz from FTP in time. It has
some huge resource files, so I have to play a little with the tarball.
It looks like some symlinks were tarred as empty files, so maybe I'll
miss something, but I am investigating right now. I'll let you know if I
need any
** Changed in: ubuntu-power-systems
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778844
Title:
ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
** Changed in: ubuntu-power-systems
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778844
Title:
ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
Ah, I see what you meant about the PHB. The two new attached logs are
not at all similar to the original ones, maybe pointing to an unrelated
problem.
As for the sosreport, the /sys/ directory is missing almost everything
that I would need to debug this. So, I need any other form of collecting
Hi, Hari.
The sosreport should be enough. I sent that message without an updated
view of the bug, so did not notice the attachments. They came on the
same day I asked. Just realized now that they are present. Let me look
at them.
Now, if kdump works with MODULES=most, then the PHB initialization
Can you run apport-collect -p linux 1778844 ?
Thank you.
Cascardo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778844
Title:
ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
** Tags removed: triage-a
** Tags added: triage-g
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778844
Title:
ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
crash,kdump is not
** Changed in: makedumpfile (Ubuntu)
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided
** Changed in: ubuntu-power-systems
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778844
Title:
ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
** Changed in: ubuntu-power-systems
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778844
Title:
ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
I have managed to test kdump and initramfs with MODULES=dep on an
emulated nvme, using qemu. Both worked just fine. The sysfs tree seems
reasonable too, in respect to how initramfs finds the necessary modules.
So, I would really need the specific details on that failure case, that
is, the sysfs
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: makedumpfile (Ubuntu)
Importance: Undecided
Status: New
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
As we use MODULES=dep for kdump initrd, that might fail to include the
proper modules. It would be a bug on initramfs-tools-core.
Can you change /etc/initramfs-tools/initramfs.conf to have MODULES=dep
instead of MODULES=most and run mkinitramfs -o /tmp/initrd.img `uname
-r`, then send me output?
I will look at this later today. Will send updates on it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778844
Title:
ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
crash,kdump is
Kernel team, looks like the root cause identified by IBM (taken from
description of the bug) is:
== Comment: #8 - Hari Krishna Bathini <> - 2018-06-26 06:06:13 ==
The dump target (/var/crash) is on NVMe device (also, the root disk).
But the kdump initrd is not being built with nvme driver
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
Canonical Kernel Team (canonical-kernel-team)
** Changed in: ubuntu-power-systems
Importance: High => Critical
**
** Changed in: ubuntu-power-systems
Status: New => Triaged
** Tags added: kernel-key
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
** Tags added: p9 triage-g
** Changed in: ubuntu-power-systems
Importance: Undecided => High
--
19 matches
Mail list logo
