Hi Geert,
On Mon, Feb 27, 2023 at 01:31:23PM +0100, Geert Uytterhoeven wrote:
> Hi Mike,
>
> On Mon, Feb 27, 2023 at 12:34 PM Mike Rapoport wrote:
> > On Mon, Feb 27, 2023 at 10:42:34PM +1300, Michael Schmitz wrote:
> > > Am 27.02.2023 um 21:26 schrieb Geert Uytterhoeven:
> > > > > On Mon, 27 Fe
Hi Mike,
On Mon, Feb 27, 2023 at 12:34 PM Mike Rapoport wrote:
> On Mon, Feb 27, 2023 at 10:42:34PM +1300, Michael Schmitz wrote:
> > Am 27.02.2023 um 21:26 schrieb Geert Uytterhoeven:
> > > FTR, here is the diff of the dmesg between good and bad:
> > >
> > > +initrd: 07f61166 - 0800
> >
Hi,
On Mon, Feb 27, 2023 at 10:42:34PM +1300, Michael Schmitz wrote:
> Hi Geert,
>
> adding Mike Rapoport to the recipient list who would know whether
> memblock_reserve() relies on paging_init() having run.
>
> Cheers,
>
> Michael
>
> Am 27.02.2023 um 21:26 schrieb Geert Uytterhoeven:
>
Eero,
that issue (kernel running from TT-RAM) was fixed quite a few years ago
(but maybe not in 2013), in the sense that ST-RAM could be used for
drivers (SCSI, atafb). Using ST-RAM as normal VM should have been made a
lot easier by changing to memblock, but AFAIR there are still some bits
mi
Hi Geert,
adding Mike Rapoport to the recipient list who would know whether
memblock_reserve() relies on paging_init() having run.
Cheers,
Michael
Am 27.02.2023 um 21:26 schrieb Geert Uytterhoeven:
Hi Finn,
FTR, here is the diff of the dmesg between good and bad:
+initrd: 07f6
Hi,
On 27.2.2023 9.19, Michael Schmitz wrote:
Am 27.02.2023 um 18:55 schrieb Finn Thain:
On Mon, 27 Feb 2023, Michael Schmitz wrote:
Bisected to commit 376e3fdecb0dcae2 ("m68k: Enable memtest
functionality") in v5.17-rc1. Reverting that on top of latest fixes
the issue.
Yes, I'm sorry to
Hi Finn,
FTR, here is the diff of the dmesg between good and bad:
+initrd: 07f61166 - 0800
This is wrong (note the 6 trailing zeros), as phys_to_virt() is not
working correctly yet (module_fixup() is called from paging_init()).
Zone ranges:
DMA [mem 0x0740-0
On Mon, 27 Feb 2023, I wrote:
> On Mon, 27 Feb 2023, Michael Schmitz wrote:
>
> >
> > I wonder whether Finn's memtest patch merely exposed another MM bug
> >
>
> A kernel patch may be easier than a bootloader patch (even if this is a
> bootloader bug) particularly if it affects multiple pl
Hi Finn,
Am 27.02.2023 um 18:55 schrieb Finn Thain:
On Mon, 27 Feb 2023, Michael Schmitz wrote:
Bisected to commit 376e3fdecb0dcae2 ("m68k: Enable memtest
functionality") in v5.17-rc1. Reverting that on top of latest fixes
the issue.
Yes, I'm sorry to say that was the only likely candidate
On Mon, 27 Feb 2023, Michael Schmitz wrote:
>
> I wonder whether Finn's memtest patch merely exposed another MM bug
>
A kernel patch may be easier than a bootloader patch (even if this is a
bootloader bug) particularly if it affects multiple platforms.
A partial revert of my patch (below) wi
On Mon, 27 Feb 2023, Michael Schmitz wrote:
> >
> > Bisected to commit 376e3fdecb0dcae2 ("m68k: Enable memtest
> > functionality") in v5.17-rc1. Reverting that on top of latest fixes
> > the issue.
>
> Yes, I'm sorry to say that was the only likely candidate. Can't see why
> though - are Macs
Hi Geert,
Am 27.02.2023 um 01:52 schrieb Geert Uytterhoeven:
On Sun, Feb 26, 2023 at 12:02 PM Geert Uytterhoeven
wrote:
On Tue, Feb 21, 2023 at 4:53 PM John Paul Adrian Glaubitz
wrote:
On Tue, 2023-02-21 at 15:55 +0100, Geert Uytterhoeven wrote:
Looks surprisingly similar to the issue repor
Hi Geert, Stephen,
Am 27.02.2023 um 01:52 schrieb Geert Uytterhoeven:
On Sun, Feb 26, 2023 at 12:02 PM Geert Uytterhoeven
wrote:
On Tue, Feb 21, 2023 at 4:53 PM John Paul Adrian Glaubitz
wrote:
On Tue, 2023-02-21 at 15:55 +0100, Geert Uytterhoeven wrote:
Looks surprisingly similar to the is
On Sun, Feb 26, 2023 at 12:02 PM Geert Uytterhoeven
wrote:
> On Tue, Feb 21, 2023 at 4:53 PM John Paul Adrian Glaubitz
> wrote:
> > On Tue, 2023-02-21 at 15:55 +0100, Geert Uytterhoeven wrote:
> > > Looks surprisingly similar to the issue reported by Stan.
> > > Do the mitigations given in
> > >
Hi Michael,
> that's apparently been corrected in later versions. Commit
> ca831f29f8f25c97182e726429b38c0802200c8f (in from 5.17).
>
> I doubt this would lead to different code generated.
>
> Which was the first broken version you tried? That would narrow down
> the search range considerably..
Hi Adrian,
On Tue, Feb 21, 2023 at 4:53 PM John Paul Adrian Glaubitz
wrote:
> On Tue, 2023-02-21 at 15:55 +0100, Geert Uytterhoeven wrote:
> > Looks surprisingly similar to the issue reported by Stan.
> > Do the mitigations given in
> > https://lore.kernel.org/all/camuhmdutkr2zvzijflxvs9d_injbkts
Hi Adrian,
Am 25.02.2023 um 08:49 schrieb John Paul Adrian Glaubitz:
Hi Michael!
On Sat, 2023-02-25 at 08:39 +1300, Michael Schmitz wrote:
the only commits to hit arch/m68k/mm between 5.15 and now are:
29f28f8b826d m68k: fix livelock in uaccess
6d0b92254510 m68k/mm: enable ARCH_HAS_VM_GET_PAG
Hi Michael!
On Sat, 2023-02-25 at 08:39 +1300, Michael Schmitz wrote:
> the only commits to hit arch/m68k/mm between 5.15 and now are:
>
> 29f28f8b826d m68k: fix livelock in uaccess
> 6d0b92254510 m68k/mm: enable ARCH_HAS_VM_GET_PAGE_PROT
> d92725256b4f mm: avoid unnecessary page fault retires on
Hi Stephen, Adrian
the only commits to hit arch/m68k/mm between 5.15 and now are:
29f28f8b826d m68k: fix livelock in uaccess
6d0b92254510 m68k/mm: enable ARCH_HAS_VM_GET_PAGE_PROT
d92725256b4f mm: avoid unnecessary page fault retires on shared memory types
f95a387cdeb3 m68k: coldfire: drop ISA_D
Hi Stephen,
that's apparently been corrected in later versions. Commit
ca831f29f8f25c97182e726429b38c0802200c8f (in from 5.17).
I doubt this would lead to different code generated.
Which was the first broken version you tried? That would narrow down the
search range considerably...
Cheers,
FYI:
Just caught this trying a re-compile of kernel 5.15.2 from kernel org,
under debbootstrap/sbuild and qemu-system-m68k both produce this issue:
CC mm/process_vm_access.o
CC mm/page_alloc.o
mm/page_alloc.c: In function ‘mem_init_print_info’:
mm/page_alloc.c:8163:27: warning: com
Hi Adrian,
On Tue, 21 Feb 2023 15:50:52 +0100
John Paul Adrian Glaubitz wrote:
> Will try earlier kernels until I found the one where the breakage was
> introduced. Currently known latest kernel to work is 5.10.5.
From my testing last year trying to boot my Amiga 3000, the break
happens sometim
Correcting myself again...
On 22/02/23 13:53, Michael Schmitz wrote:
Hi Adrian,
On 22/02/23 10:46, John Paul Adrian Glaubitz wrote:
Hi Michael!
On Wed, 2023-02-22 at 10:09 +1300, Michael Schmitz wrote:
a1 is just before the end of your RAM chunk. If that's a longword
Actually it isn't tha
Hi Adrian,
On 22/02/23 10:46, John Paul Adrian Glaubitz wrote:
Hi Michael!
On Wed, 2023-02-22 at 10:09 +1300, Michael Schmitz wrote:
a1 is just before the end of your RAM chunk. If that's a longword
Actually it isn't that close - if I read the stack correctly, we're
comparing 0xc bytes fro
Hi Michael!
On Wed, 2023-02-22 at 10:09 +1300, Michael Schmitz wrote:
> a1 is just before the end of your RAM chunk. If that's a longword
> access, you'd fall over the edge :) Can you disassemble the code snippet
> (or memcmp()) so we can see what's happening?
Here you go:
00201d14 :
201d14
Hi Adrian,
On 22/02/23 04:53, John Paul Adrian Glaubitz wrote:
Hi Geert!
On Tue, 2023-02-21 at 15:55 +0100, Geert Uytterhoeven wrote:
Looks surprisingly similar to the issue reported by Stan.
Do the mitigations given in
https://lore.kernel.org/all/camuhmdutkr2zvzijflxvs9d_injbktsnqqqfo1oxnjhze
Hi Geert!
On Tue, 2023-02-21 at 15:55 +0100, Geert Uytterhoeven wrote:
> Looks surprisingly similar to the issue reported by Stan.
> Do the mitigations given in
> https://lore.kernel.org/all/camuhmdutkr2zvzijflxvs9d_injbktsnqqqfo1oxnjhzeoy...@mail.gmail.com
> help?
The kernel actually crashes wit
Hi Adrian,
On Tue, Feb 21, 2023 at 3:51 PM John Paul Adrian Glaubitz
wrote:
> I tested Debian's most recent m68k kernels from the 6.0.x and 6.1.x series and
Thanks for testing!
> neither of these boot on my Amiga 4000/060. Both get stuck at the ABCDGHIJK
> message.
Looks surprisingly similar t
Hi!
I tested Debian's most recent m68k kernels from the 6.0.x and 6.1.x series and
neither of these boot on my Amiga 4000/060. Both get stuck at the ABCDGHIJK
message.
Will try earlier kernels until I found the one where the breakage was
introduced.
Currently known latest kernel to work is 5.10.
29 matches
Mail list logo
