** Changed in: ubuntu-power-systems
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681909
Title:
kdump is not captured in remote host when kdump over ssh
This bug was fixed in the package makedumpfile -
1:1.6.5-1ubuntu1~18.04.3
---
makedumpfile (1:1.6.5-1ubuntu1~18.04.3) bionic; urgency=medium
[ Guilherme G. Piccoli ]
* Add kdump retry/delay mechanism when dumping over network (LP: #1681909)
[ Thadeu Lima de Souza Cascardo ]
This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu1.3
---
makedumpfile (1:1.6.5-1ubuntu1.3) disco; urgency=medium
[ Guilherme G. Piccoli ]
* Add kdump retry/delay mechanism when dumping over network (LP: #1681909)
[ Thadeu Lima de Souza Cascardo ]
* Use maxcpus
There is some reported regressions in autopkgtests for ppc64el and s390x, I'm
investigating.
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681909
Title:
kdump is not captured
Retested with Bionic-proposed version (1:1.6.5-1ubuntu1~18.04.3) and
Disco-proposed (1:1.6.5-1ubuntu1.3), both including the fix for this
bug.
All working fine. I've used the "droppkt" hack (see comment #24) to
simulate the problem, and it's fixed in the -proposed version.
Thanks,
Guilherme
**
Hello bugproxy, or anyone else affected,
Accepted makedumpfile into disco-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1.3 in
a few hours, and then in the -proposed repository.
Please help us by testing this new
Just a quick update, the package got a respin without the offending
patch, soon (after it got sponsored) it'll land into -proposed pocket.
Thanks,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Even though the bionic and disco verifications were successful (thanks
for verifying), these patches were bundled in a single submission with
other patches (from other bugs) which could not be successfully
verified. As a result, all patches have had to be removed.
Next step is to re-upload new
Tested with Bionic-proposed version (1:1.6.5-1ubuntu1~18.04.2) and
Disco-proposed (1:1.6.5-1ubuntu1.1), both including the fix for this bug.
All working fine. I've used the "droppkt" hack (see comment #24) in the Bionic
version, to simulate the problem, and it's fixed in the -proposed version.
** Tags removed: sts-sponsor-slashd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681909
Title:
kdump is not captured in remote host when kdump over ssh is configured
To manage notifications
** Changed in: ubuntu-power-systems
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681909
Title:
kdump is not captured in remote host when kdump over ssh
Hello bugproxy, or anyone else affected,
Accepted makedumpfile into bionic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1~18.04.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello bugproxy, or anyone else affected,
Accepted makedumpfile into disco-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new
Excellent news! Thanks Eric :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681909
Title:
kdump is not captured in remote host when kdump over ssh is configured
To manage notifications about
Hi Andrew Cloke,
Yes, I'm currently sponsoring D/B for cascardo/gpicolli.
Disco is already uploaded waiting for SRU team approval:
https://launchpad.net/ubuntu/disco/+queue?queue_state=1_text=makedumpfile
Bionic debdiff needs some rework before I do the final upload.
- Eric
--
You received
Next step is to consider backport feasibility for disco and bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681909
Title:
kdump is not captured in remote host when kdump over ssh is
This bug was fixed in the package makedumpfile - 1:1.6.6-2ubuntu1
---
makedumpfile (1:1.6.6-2ubuntu1) eoan; urgency=medium
[ Thadeu Lima de Souza Cascardo ]
* Merge from Debian unstable. Remaining changes:
- Bump amd64 crashkernel from 384M-:128M to 512M-:192M.
* Add kdump
** Branch linked: lp:~gpiccoli/britney/hints-ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681909
Title:
kdump is not captured in remote host when kdump over ssh is configured
To manage
Merge proposal to britney/hints-ubuntu submitted, to mark this test as
"badtest" for ppc64el: https://code.launchpad.net/~gpiccoli/britney
/hints-ubuntu/+merge/371479
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
After updating the package for eaon-proposed with the fix for ppc64 (thanks
Eric!), I've manually tested that version and it's working fine, being able to
collect the kernel crash dump.
The version I've tested is:
$ rmadison makedumpfile | grep eoan-proposed
makedumpfile | 1:1.6.6-2ubuntu1
** Tags added: sts-sponsor-slashd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681909
Title:
kdump is not captured in remote host when kdump over ssh is configured
To manage notifications about
makedumpfile merge to "1:1.6.6-2ubuntu1" sponsored in Eoan.
I appended the changelog to add the entry block[0] currently found in
eoan-proposed that was missing to keep track of everything that has been done
on the package:
Since it was made by cascardo before 1:1.6.5-1ubuntu3 exist.
Note:
- I
Eric, thanks for looking into the testing failure.
I was discussing with Cascardo today, and he was able to spot quickly the
problem.
First, the reason "makedumpfile" test passed in ppc64el before was that the
test was skipped; Cascardo changed "makedumpfile" to be part of the called "big
Quick update:
It seems to fail the same way with 1:1.6.5-1ubuntu2, so NOT introduced
by this SRU via 1:1.6.5-1ubuntu3
We still have to test the autopkgtest locally on ppc64el arch and
instrument/monitor the test to understand why no crash is found in
/var/crash at the end of the test.
--
You
Quick update
# excuses... page:
makedumpfile (1:1.6.5-1ubuntu2 to 1:1.6.5-1ubuntu3)
Maintainer: Louis Bouchard
0 days old
autopkgtest for kpatch/0.5.0-0ubuntu2: amd64: Ignored failure
autopkgtest for makedumpfile/1:1.6.5-1ubuntu3: amd64: Pass, arm64: Pass, armhf:
Pass, i386: Pass, ppc64el:
Thanks Eric for sponsoring this LP!
I'm marking Xenial as "Won't Fix" for now, since we had no issue reports
and it'll require a slightly more complex backport than Bionic. We'll
discuss about the SRU to Xenial in some time, specially if we have
reports of this failure in that release.
Cheers,
Sponsored for 'Eoan'.
We'll be able to start the SRU sponsoring as soon as it lands in
-releases.
Notes:
* Patch lands in debian unstable ~2 weeks ago :
https://salsa.debian.org/debian/makedumpfile/commit/d63ba95337988be1eac8c8c76d90825ff5c6d17f
* Patch have been "Signed-off-by" by a member of
** Description changed:
[Impact]
* Kdump over network (like NFS mount or SSH dump) relies on network-
online target from systemd. Even so, there are some NICs that report
"Link Up" state but aren't ready to transmit packets. This is a
generally bad behavior that is credited probably
Marking Cosmic as 'Won't fix'.
Ubuntu 18.10 (Cosmic Cuttlefish) End Of Life reached on July 18 2019.
** Changed in: makedumpfile (Ubuntu Cosmic)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Fix for eoan at my ppa. ppa:cascardo/kdump2.
Attaching SRU for disco and bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681909
Title:
kdump is not captured in remote host when kdump over
** Patch added: "SRU for disco"
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1681909/+attachment/5278173/+files/makedumpfile_1.6.5-1ubuntu1.1_disco.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "SRU for bionic"
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1681909/+attachment/5278174/+files/makedumpfile_1.6.5-1ubuntu1~18.04.2_bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The attachment "lp1681909_eoan.debdiff" seems to be a debdiff. The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag,
** Changed in: ubuntu-power-systems
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681909
Title:
kdump is not captured in remote host when kdump over ssh is
This is the debdiff with the retry/delay mechanism, for Eoan. I've
discussed with Cascardo and we agreed he will do the SRU to old releases
(X/B/C/D) after applying some other SRUs he's working now.
I'd like to thanks specially Hari, Murilo and Pavithra from IBM, that
reported, worked and
This is a mock reproducer of this issue by faking a 20s delay in virtio-
net after its link is up.
To enable that, user needs to build virtio-net with the hereby attached
patch, and insert:
"echo 1 > /sys/module/virtio_net/parameters/droppkt"
in the /usr/sbin/kdump-config before the network
** Changed in: ubuntu-power-systems
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681909
Title:
kdump is not captured in remote host when kdump over ssh is
It came to my attention that this issue still exists; an user report on
x84-64 machine confirms that it's not only a ppc64 issue, it's a generic
problem due to some NICs behavior; even with link up, they are really
not ready to xmit packets. So, I could reproduce this by modifying
virtio to mimic
38 matches
Mail list logo
