Re: [PATCH 00/14] alpha: cleanups for 6.10
From: Arnd Bergmann
Date: Mon May 06 2024 - 06:11:40 EST
On Mon, May 6, 2024, at 11:16, Michael Cree wrote:
> On Fri, May 03, 2024 at 10:15:10PM +0200, Arnd Bergmann wrote:
>> On Fri, May 3, 2024, at 18:06, Matt Turner wrote:
>> > On Fri, May 3, 2024 at 4:12 AM Arnd Bergmann <arnd@xxxxxxxxxx> wrote:
>> >>
>> >> Al Viro did another series for alpha to address all the known build
>> >> issues. I rebased his patches without any further changes and included
>> >> it as a baseline for my work here to avoid conflicts.
>>
>> I've pushed out the series with the additional Acks to
>> https://git.kernel.org/pub/scm/linux/kernel/git/arnd/asm-generic.git/log/?h=alpha-cleanup-6.9
>> and merged it into the main asm-generic branch for 6.10.
>>
>> Can you give this a quick test on one of your machines to make
>> sure I didn't introduce a stupid regression somewhere?
>
> I built a dp264 specific kernel and its working fine on an XP1000
> (EV67 arch). Just built a generic kernel (as that's probably a more
> important test) and that is also working fine on the XP1000.
Thanks a lot for testing!
> I also built a titan specific kernel to test on an ES45 (SMP EV68
> arch) but that OOPSes early in the boot process with a kernel null
> pointer access. I suspect that has nothing to do with your patches
> as I have a recollection that I have seen that OOPS before.
Ok
> So I tried the same generic kernel that I have running on the XP1000
> but that fails to unpack at the initial boot stage (!) with:
Just to be sure: this is not a regression from my patches either,
right? I would expect that any EV6 (or later) target specific
kernel didn't change much at all from my patches, while the
generic kernel changing from -march=ev4 to -march=ev56 is
certainly meant to be different (in a good way, with smaller
size and faster execution).
Arnd