This bug was fixed in the package makedumpfile - 1:1.5.9-7
---
makedumpfile (1:1.5.9-7) sid; urgency=medium
* [d/rules] Lower kexec-tools dependency to -2
The ubuntu merge will happen on an 1:2.0.10-2 version so it cannot
depends on -3.
-- Louis Bouchard
On 13.04.2016 [23:44:39 -], Dave Chiluk wrote:
> So it looks like this crashkernel argument is not resulting in any reserved
> memory.
> The correct crashkernel argument should look like this.
> crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@32M
>
> Additionally
So it looks like this crashkernel argument is not resulting in any reserved
memory.
The correct crashkernel argument should look like this.
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@32M
Additionally my earlier failures here were the result of no reserved
memory
On 12.04.2016 [21:13:40 -], Dave Chiluk wrote:
> With
> ubuntu@modoc:~$ cat /proc/cmdline
> root=/dev/mapper/mpath0-part2 ro console=hvc0
> crashkernel=2G-4G:320M@32M,4G-32G:512M@32M,32G-64G:1024M@32M,64G-128G:2048M@32M,128G-:4096M@32M
>
> I get the following console log
> [ 191.833046]
With
ubuntu@modoc:~$ cat /proc/cmdline
root=/dev/mapper/mpath0-part2 ro console=hvc0
crashkernel=2G-4G:320M@32M,4G-32G:512M@32M,32G-64G:1024M@32M,64G-128G:2048M@32M,128G-:4096M@32M
I get the following console log
[ 191.833046] SysRq : Trigger a crash
[ 191.833117] Unable to handle kernel
It turns out I was hitting issues related to the following bug.
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1569567
I will rerun my test
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567539
On 12.04.2016 [19:53:57 -], Dave Chiluk wrote:
> I can confirm that the following settings for crashkernel on powernv result
> in the following console log.
> crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
If I read that correctly, it failed to kdump at all? Can
I can confirm that the following settings for crashkernel on powernv result in
the following console log.
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
I will now test with @32M options.
modoc login: [ 1374.418348] SysRq : Trigger a crash
[ 1374.418424] Unable to
On 12.04.2016 [18:51:36 -], Dave Chiluk wrote:
> I received another update from the end user.
> "A fresh 14.04.4 DVD Ubuntu install with updates (3.16.0-69 kernel) in a
> diskful setup (no NFS, no aufs, 1T swap disk) also fails to kdump, either
> hangs or OOMS."
>
> My understanding is
I received another update from the end user.
"A fresh 14.04.4 DVD Ubuntu install with updates (3.16.0-69 kernel) in a
diskful setup (no NFS, no aufs, 1T swap disk) also fails to kdump, either hangs
or OOMS."
My understanding is that it OOMS on too little crashkernel assignment,
hangs if
** Changed in: makedumpfile (Ubuntu)
Status: New => Confirmed
** Changed in: makedumpfile (Ubuntu)
Importance: Undecided => High
** Changed in: makedumpfile (Ubuntu)
Assignee: (unassigned) => Louis Bouchard (louis-bouchard)
--
You received this bug notification because you are a
I honnestly think that this assignment should be removed from kexec-tool
& moved over to kdump-tools. I'd be happy to do it, which would
facilitate such hardware-specific customization.
I have another requirement for a similar tailoring on s390x so I could
joint them both.
Now I'd be happy to
On 08.04.2016 [11:04:47 -], Louis Bouchard wrote:
> Hello,
>
> Regarding nr_cpus=1, the equivalent maxcpus=1 is set in the kexec
> command (at least on default installs) :
Yep, you're right, sorry!
> Maybe disabling SMP alltogether by setting maxcpus=0 could be considered
> but that
Hello,
Regarding nr_cpus=1, the equivalent maxcpus=1 is set in the kexec
command (at least on default installs) :
$ kdump-config show
DUMP_MODE:kdump
USE_KDUMP:1
KDUMP_SYSCTL: kernel.panic_on_oops=1
KDUMP_COREDIR:/var/crash
crashkernel addr: 0x2b00
On 07.04.2016 [17:18:58 -], Dave Chiluk wrote:
> According to
> https://wiki.ubuntu.com/ppc64el/Recommendations#Crash_Kernel_recommendations
>
> it looks like the following should be used.
> crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
>
> These should be made
According to
https://wiki.ubuntu.com/ppc64el/Recommendations#Crash_Kernel_recommendations
it looks like the following should be used.
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
These should be made as defaults for crash on ppc64 at the very least.
--
You
Couple of thoughts, which we probably should get IBM's advice on:
I believe this is using: crashkernel=384M-:128M
128M reserved seems too small for so much memory, tbh.
Also, I see that all the CPUs are on in the crashkernel, when
realistically only 1 CPU is needed (and there have been issues
It was also suggested that
nr_cpus=1 and or kvm_cma_resv_ratio=0 should be considered for defaults for
the crash kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567539
Title:
Failure to
Other kernel combinations may also be affected.
** Description changed:
Test case
# sudo apt-get install linux-crashdump
set USE_KDUMP=1 in /etc/default/kdump-tools
+
+ # sudo shutdown -r now
+
echo 1 | sudo tee /proc/sys/kernel/sysrq
echo c | sudo tee /proc/sysrq-trigger
It
19 matches
Mail list logo
