Re: [PATCH v2] crash, powerpc: Default to CRASH_DUMP=n on PPC_BOOK3S_32

2024-11-12 Thread Dave Vasilevsky
On 2024-09-17 12:37, Dave Vasilevsky wrote: > Fixes boot failures on 6.9 on PPC_BOOK3S_32 machines using > Open Firmware. On these machines, the kernel refuses to boot > from non-zero PHYSICAL_START, which occurs when CRASH_DUMP is on. Hi Eric, and other kexec people, Is there anywhe

[PATCH v2] crash, powerpc: Default to CRASH_DUMP=n on PPC_BOOK3S_32

2024-09-17 Thread Dave Vasilevsky
some other mechanism can still turn it on explicitly. Does not change the default on any other architectures for the time being. Signed-off-by: Dave Vasilevsky Reported-by: Reimar Döffinger Closes: https://lists.debian.org/debian-powerpc/2024/07/msg1.html Fixes: 75bc255a7444 ("crash:

Re: [PATCH] crash: Default to CRASH_DUMP=n when support for it is unlikely

2024-09-08 Thread Dave Vasilevsky
I received a notification from Patchwork that my patch is now in the state "Handled Elsewhere".[0] Does that mean someone merged it somewhere? Or that I should be using a different mailing list? Or something else? I'd appreciate some guidance. Thanks, Dave [0] http://patchwork.ozlabs.org/pro

Re: [PATCH] crash: Default to CRASH_DUMP=n when support for it is unlikely

2024-08-30 Thread Dave Vasilevsky
On 2024-08-30 02:35, Baoquan He wrote: > The overrall looks good to me except of the CRASH_DUMP=n on sh, do you > have a comment about the reasoning since you have discussed with John? > Is it because of below config items? I don't yet know why John asked to turn this off by default on sh, though

Re: [PATCH] crash: Default to CRASH_DUMP=n when support for it is unlikely

2024-08-29 Thread Dave Vasilevsky
On 2024-08-29 23:15, Baoquan He wrote: >> +config ARCH_DEFAULT_CRASH_DUMP >> +def_bool n > > If we don't add ARCH_DEFAULT_CRASH_DUMP at all in sh arch, the > CRASH_DUMP will be off by default according to the below new definition > of CRASH_DUMP? Yes, that's true. But if we don't add it at al

Re: [PATCH] crash: Default to CRASH_DUMP=n when support for it is unlikely

2024-08-25 Thread Dave Vasilevsky
On 2024-08-26 01:38, John Paul Adrian Glaubitz wrote: > On Mon, 2024-08-26 at 12:02 +1000, Michael Ellerman wrote: >> So IMHO having it enabled by default in upstream does make sense, >> because it more closely matches what distros/users actually run. > > Well, at least Debian did not enable it by

[PATCH] crash: Default to CRASH_DUMP=n when support for it is unlikely

2024-08-23 Thread Dave Vasilevsky
some other mechanism can still turn it on explicitly. Also defaults to CRASH_DUMP=n on sh. Signed-off-by: Dave Vasilevsky Reported-by: Reimar Döffinger Closes: https://lists.debian.org/debian-powerpc/2024/07/msg1.html Fixes: 75bc255a7444 ("crash: clean up kdump related config

Re: [PATCH linux-next v3 05/14] crash: clean up kdump related config items

2024-08-23 Thread Dave Vasilevsky
On 2024-08-23 07:58, Dave Vasilevsky wrote: > On 2024-08-23 03:16, John Paul Adrian Glaubitz wrote: >> It should be disabled on m68k and sh by default as well. > > Sure, I can change that. What's the reasoning, so I can explain in my commit > message? Oh I do

Re: [PATCH linux-next v3 05/14] crash: clean up kdump related config items

2024-08-23 Thread Dave Vasilevsky
On 2024-08-23 03:16, John Paul Adrian Glaubitz wrote: > It should be disabled on m68k and sh by default as well. Sure, I can change that. What's the reasoning, so I can explain in my commit message? -Dave

Re: [PATCH linux-next v3 05/14] crash: clean up kdump related config items

2024-08-22 Thread Dave Vasilevsky
e a look at this patch: >From d6e5fe3a45f46f1aa01914648c443291d956de9e Mon Sep 17 00:00:00 2001 From: Dave Vasilevsky Date: Thu, 22 Aug 2024 20:13:46 -0400 Subject: [PATCH] powerpc: Default to CRASH_DUMP=n when Open Firmware boot is likely MIME-Version: 1.0 Content-Type: text/plain; charset=UT